Regenerate

(This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e)
author: Jelmer Vernooij <jelmer@samba.org> 2003-02-18 22:14:04 +0000
committer: Jelmer Vernooij <jelmer@samba.org> 2003-02-18 22:14:04 +0000
commit: ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 (patch)
tree: deda0311c634bd433278a352e1a9daece40ff0f6 /docs/htmldocs/Samba-HOWTO-Collection.html
parent: 4668623d62b3a7b133e26dd1397b956c4ddac335 (diff)
download: samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.gz
samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.bz2
samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.zip
1 files changed, 4116 insertions, 3728 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index 2bb324d9f3..d758fbbe11 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -5,7 +5,7 @@
 >SAMBA Project Documentation</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77+"></HEAD
 ><BODY
 CLASS="BOOK"
 BGCOLOR="#FFFFFF"
@@ -45,7 +45,7 @@ CLASS="emphasis"
 CLASS="EMPHASIS"
 >Last Update</I
 ></SPAN
-> : Thu Aug 15 12:48:45 CDT 2002</P
+> : Wed Jan 15</P
 ><P
 >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 <A
 HREF="mailto:jerry@samba.org"
 TARGET="_top"
 >jerry@samba.org</A
+> or 
+<A
+HREF="mailto:jelmer@samba.org"
+TARGET="_top"
+>jelmer@samba.org</A
 >.</P
 ><P
 >This documentation is distributed under the GNU General Public License (GPL) 
@@ -79,7 +84,7 @@ CLASS="TOC"
 ></DT
 ><DT
 >I. <A
-HREF="#AEN18"
+HREF="#INTRODUCTION"
 >General installation</A
 ></DT
 ><DD
@@ -93,27 +98,27 @@ HREF="#INSTALL"
 ><DL
 ><DT
 >1.1. <A
-HREF="#AEN25"
+HREF="#AEN26"
 >Read the man pages</A
 ></DT
 ><DT
 >1.2. <A
-HREF="#AEN35"
+HREF="#AEN36"
 >Building the Binaries</A
 ></DT
 ><DT
 >1.3. <A
-HREF="#AEN63"
+HREF="#AEN64"
 >The all important step</A
 ></DT
 ><DT
 >1.4. <A
-HREF="#AEN67"
+HREF="#AEN68"
 >Create the smb configuration file.</A
 ></DT
 ><DT
 >1.5. <A
-HREF="#AEN81"
+HREF="#AEN82"
 >Test your config file with 
 	<B
 CLASS="COMMAND"
@@ -122,171 +127,118 @@ CLASS="COMMAND"
 ></DT
 ><DT
 >1.6. <A
-HREF="#AEN89"
+HREF="#AEN90"
 >Starting the smbd and nmbd</A
 ></DT
 ><DT
 >1.7. <A
-HREF="#AEN144"
+HREF="#AEN145"
 >Try listing the shares available on your 
 	server</A
 ></DT
 ><DT
 >1.8. <A
-HREF="#AEN153"
+HREF="#AEN154"
 >Try connecting with the unix client</A
 ></DT
 ><DT
 >1.9. <A
-HREF="#AEN169"
+HREF="#AEN170"
 >Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</A
 ></DT
 ><DT
 >1.10. <A
-HREF="#AEN183"
+HREF="#AEN184"
 >What If Things Don't Work?</A
 ></DT
 ></DL
 ></DD
 ><DT
 >2. <A
-HREF="#IMPROVED-BROWSING"
->Improved browsing in samba</A
+HREF="#BROWSING-QUICK"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
 ></DT
 ><DD
 ><DL
 ><DT
 >2.1. <A
-HREF="#AEN228"
->Overview of browsing</A
+HREF="#AEN230"
+>Discussion</A
 ></DT
 ><DT
 >2.2. <A
-HREF="#AEN232"
->Browsing support in samba</A
+HREF="#AEN238"
+>Use of the "Remote Announce" parameter</A
 ></DT
 ><DT
 >2.3. <A
-HREF="#AEN241"
->Problem resolution</A
+HREF="#AEN252"
+>Use of the "Remote Browse Sync" parameter</A
 ></DT
 ><DT
 >2.4. <A
-HREF="#AEN248"
->Browsing across subnets</A
+HREF="#AEN257"
+>Use of WINS</A
 ></DT
 ><DT
 >2.5. <A
-HREF="#AEN288"
->Setting up a WINS server</A
+HREF="#AEN268"
+>Do NOT use more than one (1) protocol on MS Windows machines</A
 ></DT
 ><DT
 >2.6. <A
-HREF="#AEN307"
->Setting up Browsing in a WORKGROUP</A
-></DT
-><DT
->2.7. <A
-HREF="#AEN325"
->Setting up Browsing in a DOMAIN</A
-></DT
-><DT
->2.8. <A
-HREF="#AEN335"
->Forcing samba to be the master</A
-></DT
-><DT
->2.9. <A
-HREF="#AEN344"
->Making samba the domain master</A
-></DT
-><DT
->2.10. <A
-HREF="#AEN362"
->Note about broadcast addresses</A
-></DT
-><DT
->2.11. <A
-HREF="#AEN365"
->Multiple interfaces</A
+HREF="#AEN274"
+>Name Resolution Order</A
 ></DT
 ></DL
 ></DD
 ><DT
 >3. <A
-HREF="#OPLOCKS"
->Oplocks</A
+HREF="#PASSDB"
+>User information database</A
 ></DT
 ><DD
 ><DL
 ><DT
 >3.1. <A
-HREF="#AEN377"
->What are oplocks?</A
-></DT
-></DL
-></DD
-><DT
->4. <A
-HREF="#BROWSING-QUICK"
->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="#AEN392"
->Discussion</A
-></DT
-><DT
->4.2. <A
-HREF="#AEN400"
->Use of the "Remote Announce" parameter</A
-></DT
-><DT
->4.3. <A
-HREF="#AEN414"
->Use of the "Remote Browse Sync" parameter</A
+HREF="#AEN324"
+>Introduction</A
 ></DT
 ><DT
->4.4. <A
-HREF="#AEN419"
->Use of WINS</A
+>3.2. <A
+HREF="#AEN331"
+>Important Notes About Security</A
 ></DT
 ><DT
->4.5. <A
-HREF="#AEN430"
->Do NOT use more than one (1) protocol on MS Windows machines</A
+>3.3. <A
+HREF="#AEN357"
+>The smbpasswd Command</A
 ></DT
 ><DT
->4.6. <A
-HREF="#AEN436"
->Name Resolution Order</A
+>3.4. <A
+HREF="#AEN388"
+>Plain text</A
 ></DT
-></DL
-></DD
 ><DT
->5. <A
-HREF="#PWENCRYPT"
->LanMan and NT Password Encryption in Samba</A
+>3.5. <A
+HREF="#AEN393"
+>TDB</A
 ></DT
-><DD
-><DL
 ><DT
->5.1. <A
-HREF="#AEN472"
->Introduction</A
+>3.6. <A
+HREF="#AEN396"
+>LDAP</A
 ></DT
 ><DT
->5.2. <A
-HREF="#AEN477"
->Important Notes About Security</A
+>3.7. <A
+HREF="#AEN614"
+>MySQL</A
 ></DT
 ><DT
->5.3. <A
-HREF="#AEN512"
->The smbpasswd Command</A
+>3.8. <A
+HREF="#AEN662"
+>Passdb XML plugin</A
 ></DT
 ></DL
 ></DD
@@ -294,169 +246,174 @@ HREF="#AEN512"
 ></DD
 ><DT
 >II. <A
-HREF="#AEN544"
+HREF="#TYPE"
 >Type of installation</A
 ></DT
 ><DD
 ><DL
 ><DT
->6. <A
+>4. <A
+HREF="#SECURITYLEVELS"
+>User and Share security level (for servers not in a domain)</A
+></DT
+><DT
+>5. <A
 HREF="#SAMBA-PDC"
->How to Configure Samba as a NT4 Primary Domain Controller</A
+>Samba as a NT4 or Win2k Primary Domain Controller</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.1. <A
-HREF="#AEN566"
+>5.1. <A
+HREF="#AEN722"
 >Prerequisite Reading</A
 ></DT
 ><DT
->6.2. <A
-HREF="#AEN572"
+>5.2. <A
+HREF="#AEN728"
 >Background</A
 ></DT
 ><DT
->6.3. <A
-HREF="#AEN611"
+>5.3. <A
+HREF="#AEN767"
 >Configuring the Samba Domain Controller</A
 ></DT
 ><DT
->6.4. <A
-HREF="#AEN654"
+>5.4. <A
+HREF="#AEN810"
 >Creating Machine Trust Accounts and Joining Clients to the
 Domain</A
 ></DT
 ><DT
->6.5. <A
-HREF="#AEN738"
+>5.5. <A
+HREF="#AEN894"
 >Common Problems and Errors</A
 ></DT
 ><DT
->6.6. <A
-HREF="#AEN786"
+>5.6. <A
+HREF="#AEN942"
 >System Policies and Profiles</A
 ></DT
 ><DT
->6.7. <A
-HREF="#AEN830"
+>5.7. <A
+HREF="#AEN986"
 >What other help can I get?</A
 ></DT
 ><DT
->6.8. <A
-HREF="#AEN944"
+>5.8. <A
+HREF="#AEN1100"
 >Domain Control for Windows 9x/ME</A
 ></DT
 ><DT
->6.9. <A
-HREF="#AEN1082"
->DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
+>5.9. <A
+HREF="#AEN1238"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control &amp; Samba</A
 ></DT
 ></DL
 ></DD
 ><DT
->7. <A
+>6. <A
 HREF="#SAMBA-BDC"
 >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.1. <A
-HREF="#AEN1118"
+>6.1. <A
+HREF="#AEN1274"
 >Prerequisite Reading</A
 ></DT
 ><DT
->7.2. <A
-HREF="#AEN1122"
+>6.2. <A
+HREF="#AEN1278"
 >Background</A
 ></DT
 ><DT
->7.3. <A
-HREF="#AEN1130"
+>6.3. <A
+HREF="#AEN1286"
 >What qualifies a Domain Controller on the network?</A
 ></DT
 ><DT
->7.4. <A
-HREF="#AEN1139"
->Can Samba be a Backup Domain Controller?</A
+>6.4. <A
+HREF="#AEN1295"
+>Can Samba be a Backup Domain Controller to an NT PDC?</A
 ></DT
 ><DT
->7.5. <A
-HREF="#AEN1143"
+>6.5. <A
+HREF="#AEN1300"
 >How do I set up a Samba BDC?</A
 ></DT
 ></DL
 ></DD
 ><DT
->8. <A
+>7. <A
 HREF="#ADS"
 >Samba as a ADS domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->8.1. <A
-HREF="#AEN1178"
+>7.1. <A
+HREF="#AEN1339"
 >Installing the required packages for Debian</A
 ></DT
 ><DT
->8.2. <A
-HREF="#AEN1184"
+>7.2. <A
+HREF="#AEN1346"
 >Installing the required packages for RedHat</A
 ></DT
 ><DT
->8.3. <A
-HREF="#AEN1193"
+>7.3. <A
+HREF="#AEN1356"
 >Compile Samba</A
 ></DT
 ><DT
->8.4. <A
-HREF="#AEN1205"
+>7.4. <A
+HREF="#AEN1371"
 >Setup your /etc/krb5.conf</A
 ></DT
 ><DT
->8.5. <A
-HREF="#AEN1215"
+>7.5. <A
+HREF="#AEN1381"
 >Create the computer account</A
 ></DT
 ><DT
->8.6. <A
-HREF="#AEN1231"
+>7.6. <A
+HREF="#AEN1393"
 >Test your server setup</A
 ></DT
 ><DT
->8.7. <A
-HREF="#AEN1236"
+>7.7. <A
+HREF="#AEN1398"
 >Testing with smbclient</A
 ></DT
 ><DT
->8.8. <A
-HREF="#AEN1239"
+>7.8. <A
+HREF="#AEN1401"
 >Notes</A
 ></DT
 ></DL
 ></DD
 ><DT
->9. <A
+>8. <A
 HREF="#DOMAIN-SECURITY"
->Samba as a NT4 domain member</A
+>Samba as a NT4 or Win2k domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->9.1. <A
-HREF="#AEN1261"
->Joining an NT Domain with Samba 2.2</A
+>8.1. <A
+HREF="#AEN1423"
+>Joining an NT Domain with Samba 3.0</A
 ></DT
 ><DT
->9.2. <A
-HREF="#AEN1325"
+>8.2. <A
+HREF="#AEN1478"
 >Samba and Windows 2000 Domains</A
 ></DT
 ><DT
->9.3. <A
-HREF="#AEN1330"
+>8.3. <A
+HREF="#AEN1481"
 >Why is this better than security = server?</A
 ></DT
 ></DL
@@ -465,101 +422,101 @@ HREF="#AEN1330"
 ></DD
 ><DT
 >III. <A
-HREF="#AEN1346"
+HREF="#OPTIONAL"
 >Optional configuration</A
 ></DT
 ><DD
 ><DL
 ><DT
->10. <A
+>9. <A
 HREF="#INTEGRATE-MS-NETWORKS"
 >Integrating MS Windows networks with Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.1. <A
-HREF="#AEN1362"
+>9.1. <A
+HREF="#AEN1513"
 >Agenda</A
 ></DT
 ><DT
->10.2. <A
-HREF="#AEN1384"
+>9.2. <A
+HREF="#AEN1535"
 >Name Resolution in a pure Unix/Linux world</A
 ></DT
 ><DT
->10.3. <A
-HREF="#AEN1447"
+>9.3. <A
+HREF="#AEN1598"
 >Name resolution as used within MS Windows networking</A
 ></DT
 ><DT
->10.4. <A
-HREF="#AEN1492"
+>9.4. <A
+HREF="#AEN1643"
 >How browsing functions and how to deploy stable and 
 dependable browsing using Samba</A
 ></DT
 ><DT
->10.5. <A
-HREF="#AEN1502"
+>9.5. <A
+HREF="#AEN1653"
 >MS Windows security options and how to configure 
 Samba for seemless integration</A
 ></DT
 ><DT
->10.6. <A
-HREF="#AEN1572"
+>9.6. <A
+HREF="#AEN1723"
 >Conclusions</A
 ></DT
 ></DL
 ></DD
 ><DT
->11. <A
+>10. <A
 HREF="#UNIX-PERMISSIONS"
 >UNIX Permission Bits and Windows NT Access Control Lists</A
 ></DT
 ><DD
 ><DL
 ><DT
->11.1. <A
-HREF="#AEN1593"
+>10.1. <A
+HREF="#AEN1744"
 >Viewing and changing UNIX permissions using the NT 
 	security dialogs</A
 ></DT
 ><DT
->11.2. <A
-HREF="#AEN1602"
+>10.2. <A
+HREF="#AEN1748"
 >How to view file security on a Samba share</A
 ></DT
 ><DT
->11.3. <A
-HREF="#AEN1613"
+>10.3. <A
+HREF="#AEN1759"
 >Viewing file ownership</A
 ></DT
 ><DT
->11.4. <A
-HREF="#AEN1633"
+>10.4. <A
+HREF="#AEN1779"
 >Viewing file or directory permissions</A
 ></DT
 ><DT
->11.5. <A
-HREF="#AEN1669"
+>10.5. <A
+HREF="#AEN1815"
 >Modifying file or directory permissions</A
 ></DT
 ><DT
->11.6. <A
-HREF="#AEN1691"
+>10.6. <A
+HREF="#AEN1837"
 >Interaction with the standard Samba create mask 
 	parameters</A
 ></DT
 ><DT
->11.7. <A
-HREF="#AEN1755"
+>10.7. <A
+HREF="#AEN1901"
 >Interaction with the standard Samba file attribute 
 	mapping</A
 ></DT
 ></DL
 ></DD
 ><DT
->12. <A
+>11. <A
 HREF="#PAM"
 >Configuring PAM for distributed but centrally 
 managed authentication</A
@@ -567,350 +524,301 @@ managed authentication</A
 ><DD
 ><DL
 ><DT
->12.1. <A
-HREF="#AEN1776"
+>11.1. <A
+HREF="#AEN1922"
 >Samba and PAM</A
 ></DT
 ><DT
->12.2. <A
-HREF="#AEN1820"
+>11.2. <A
+HREF="#AEN1966"
 >Distributed Authentication</A
 ></DT
 ><DT
->12.3. <A
-HREF="#AEN1827"
+>11.3. <A
+HREF="#AEN1973"
 >PAM Configuration in smb.conf</A
 ></DT
 ></DL
 ></DD
 ><DT
->13. <A
+>12. <A
 HREF="#MSDFS"
 >Hosting a Microsoft Distributed File System tree on Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->13.1. <A
-HREF="#AEN1847"
+>12.1. <A
+HREF="#AEN1993"
 >Instructions</A
 ></DT
 ></DL
 ></DD
 ><DT
->14. <A
+>13. <A
 HREF="#PRINTING"
 >Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.1. <A
-HREF="#AEN1908"
+>13.1. <A
+HREF="#AEN2054"
 >Introduction</A
 ></DT
 ><DT
->14.2. <A
-HREF="#AEN1930"
+>13.2. <A
+HREF="#AEN2076"
 >Configuration</A
 ></DT
 ><DT
->14.3. <A
-HREF="#AEN2038"
+>13.3. <A
+HREF="#AEN2184"
 >The Imprints Toolset</A
 ></DT
 ><DT
->14.4. <A
-HREF="#AEN2081"
+>13.4. <A
+HREF="#AEN2227"
 >Diagnosis</A
 ></DT
 ></DL
 ></DD
 ><DT
->15. <A
-HREF="#SECURITYLEVELS"
->Security levels</A
-></DT
-><DD
-><DL
-><DT
->15.1. <A
-HREF="#AEN2186"
->Introduction</A
-></DT
-><DT
->15.2. <A
-HREF="#AEN2197"
->More complete description of security levels</A
-></DT
-></DL
-></DD
-><DT
->16. <A
+>14. <A
 HREF="#WINBIND"
 >Unified Logons between Windows NT and UNIX using Winbind</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.1. <A
-HREF="#AEN2249"
+>14.1. <A
+HREF="#AEN2360"
 >Abstract</A
 ></DT
 ><DT
->16.2. <A
-HREF="#AEN2253"
+>14.2. <A
+HREF="#AEN2364"
 >Introduction</A
 ></DT
 ><DT
->16.3. <A
-HREF="#AEN2266"
+>14.3. <A
+HREF="#AEN2377"
 >What Winbind Provides</A
 ></DT
 ><DT
->16.4. <A
-HREF="#AEN2277"
+>14.4. <A
+HREF="#AEN2388"
 >How Winbind Works</A
 ></DT
 ><DT
->16.5. <A
-HREF="#AEN2317"
+>14.5. <A
+HREF="#AEN2431"
 >Installation and Configuration</A
 ></DT
 ><DT
->16.6. <A
-HREF="#AEN2566"
+>14.6. <A
+HREF="#AEN2680"
 >Limitations</A
 ></DT
 ><DT
->16.7. <A
-HREF="#AEN2576"
+>14.7. <A
+HREF="#AEN2690"
 >Conclusion</A
 ></DT
 ></DL
 ></DD
 ><DT
->17. <A
-HREF="#PDB-MYSQL"
->Passdb MySQL plugin</A
+>15. <A
+HREF="#IMPROVED-BROWSING"
+>Improved browsing in samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->17.1. <A
-HREF="#AEN2590"
->Building</A
-></DT
-><DT
->17.2. <A
-HREF="#AEN2596"
->Configuring</A
-></DT
-><DT
->17.3. <A
-HREF="#AEN2611"
->Using plaintext passwords or encrypted password</A
-></DT
-><DT
->17.4. <A
-HREF="#AEN2616"
->Getting non-column data from the table</A
+>15.1. <A
+HREF="#AEN2700"
+>Overview of browsing</A
 ></DT
-></DL
-></DD
 ><DT
->18. <A
-HREF="#PDB-XML"
->Passdb XML plugin</A
+>15.2. <A
+HREF="#AEN2704"
+>Browsing support in samba</A
 ></DT
-><DD
-><DL
 ><DT
->18.1. <A
-HREF="#AEN2635"
->Building</A
+>15.3. <A
+HREF="#AEN2713"
+>Problem resolution</A
 ></DT
 ><DT
->18.2. <A
-HREF="#AEN2641"
->Usage</A
+>15.4. <A
+HREF="#AEN2720"
+>Browsing across subnets</A
 ></DT
-></DL
-></DD
 ><DT
->19. <A
-HREF="#SAMBA-LDAP-HOWTO"
->Storing Samba's User/Machine Account information in an LDAP Directory</A
+>15.5. <A
+HREF="#AEN2760"
+>Setting up a WINS server</A
 ></DT
-><DD
-><DL
 ><DT
->19.1. <A
-HREF="#AEN2664"
->Purpose</A
+>15.6. <A
+HREF="#AEN2779"
+>Setting up Browsing in a WORKGROUP</A
 ></DT
 ><DT
->19.2. <A
-HREF="#AEN2684"
->Introduction</A
+>15.7. <A
+HREF="#AEN2797"
+>Setting up Browsing in a DOMAIN</A
 ></DT
 ><DT
->19.3. <A
-HREF="#AEN2713"
->Supported LDAP Servers</A
+>15.8. <A
+HREF="#AEN2807"
+>Forcing samba to be the master</A
 ></DT
 ><DT
->19.4. <A
-HREF="#AEN2718"
->Schema and Relationship to the RFC 2307 posixAccount</A
+>15.9. <A
+HREF="#AEN2816"
+>Making samba the domain master</A
 ></DT
 ><DT
->19.5. <A
-HREF="#AEN2730"
->Configuring Samba with LDAP</A
+>15.10. <A
+HREF="#AEN2834"
+>Note about broadcast addresses</A
 ></DT
 ><DT
->19.6. <A
-HREF="#AEN2777"
->Accounts and Groups management</A
+>15.11. <A
+HREF="#AEN2837"
+>Multiple interfaces</A
 ></DT
+></DL
+></DD
 ><DT
->19.7. <A
-HREF="#AEN2782"
->Security and sambaAccount</A
+>16. <A
+HREF="#VFS"
+>Stackable VFS modules</A
 ></DT
+><DD
+><DL
 ><DT
->19.8. <A
-HREF="#AEN2802"
->LDAP specials attributes for sambaAccounts</A
+>16.1. <A
+HREF="#AEN2855"
+>Introduction and configuration</A
 ></DT
 ><DT
->19.9. <A
-HREF="#AEN2872"
->Example LDIF Entries for a sambaAccount</A
+>16.2. <A
+HREF="#AEN2864"
+>Included modules</A
 ></DT
 ><DT
->19.10. <A
-HREF="#AEN2880"
->Comments</A
+>16.3. <A
+HREF="#AEN2918"
+>VFS modules available elsewhere</A
 ></DT
 ></DL
 ></DD
 ><DT
->20. <A
+>17. <A
 HREF="#CVS-ACCESS"
->HOWTO Access Samba source code via CVS</A
+>Access Samba source code via CVS</A
 ></DT
 ><DD
 ><DL
 ><DT
->20.1. <A
-HREF="#AEN2891"
+>17.1. <A
+HREF="#AEN2942"
 >Introduction</A
 ></DT
 ><DT
->20.2. <A
-HREF="#AEN2896"
+>17.2. <A
+HREF="#AEN2947"
 >CVS Access to samba.org</A
 ></DT
 ></DL
 ></DD
 ><DT
->21. <A
+>18. <A
 HREF="#GROUPMAPPING"
 >Group mapping HOWTO</A
 ></DT
 ><DT
->22. <A
+>19. <A
 HREF="#SPEED"
 >Samba performance issues</A
 ></DT
 ><DD
 ><DL
 ><DT
->22.1. <A
-HREF="#AEN2982"
+>19.1. <A
+HREF="#AEN3033"
 >Comparisons</A
 ></DT
 ><DT
->22.2. <A
-HREF="#AEN2988"
->Oplocks</A
-></DT
-><DT
->22.3. <A
-HREF="#AEN3008"
+>19.2. <A
+HREF="#AEN3039"
 >Socket options</A
 ></DT
 ><DT
->22.4. <A
-HREF="#AEN3015"
+>19.3. <A
+HREF="#AEN3046"
 >Read size</A
 ></DT
 ><DT
->22.5. <A
-HREF="#AEN3020"
+>19.4. <A
+HREF="#AEN3051"
 >Max xmit</A
 ></DT
 ><DT
->22.6. <A
-HREF="#AEN3025"
->Locking</A
-></DT
-><DT
->22.7. <A
-HREF="#AEN3029"
->Share modes</A
-></DT
-><DT
->22.8. <A
-HREF="#AEN3034"
+>19.5. <A
+HREF="#AEN3056"
 >Log level</A
 ></DT
 ><DT
->22.9. <A
-HREF="#AEN3037"
->Wide lines</A
-></DT
-><DT
->22.10. <A
-HREF="#AEN3040"
+>19.6. <A
+HREF="#AEN3059"
 >Read raw</A
 ></DT
 ><DT
->22.11. <A
-HREF="#AEN3045"
+>19.7. <A
+HREF="#AEN3064"
 >Write raw</A
 ></DT
 ><DT
->22.12. <A
-HREF="#AEN3049"
->Read prediction</A
+>19.8. <A
+HREF="#AEN3068"
+>Slow Clients</A
 ></DT
 ><DT
->22.13. <A
-HREF="#AEN3056"
->Memory mapping</A
+>19.9. <A
+HREF="#AEN3072"
+>Slow Logins</A
 ></DT
 ><DT
->22.14. <A
-HREF="#AEN3061"
->Slow Clients</A
+>19.10. <A
+HREF="#AEN3075"
+>Client tuning</A
 ></DT
+></DL
+></DD
 ><DT
->22.15. <A
-HREF="#AEN3065"
->Slow Logins</A
+>20. <A
+HREF="#GROUPPROFILES"
+>Creating Group Profiles</A
 ></DT
+><DD
+><DL
 ><DT
->22.16. <A
-HREF="#AEN3068"
->Client tuning</A
+>20.1. <A
+HREF="#AEN3123"
+>Windows '9x</A
+></DT
+><DT
+>20.2. <A
+HREF="#AEN3132"
+>Windows NT 4</A
 ></DT
 ><DT
->22.17. <A
-HREF="#AEN3100"
->My Results</A
+>20.3. <A
+HREF="#AEN3170"
+>Windows 2000/XP</A
 ></DT
 ></DL
 ></DD
@@ -918,138 +826,138 @@ HREF="#AEN3100"
 ></DD
 ><DT
 >IV. <A
-HREF="#AEN3106"
+HREF="#APPENDIXES"
 >Appendixes</A
 ></DT
 ><DD
 ><DL
 ><DT
->23. <A
+>21. <A
 HREF="#PORTABILITY"
 >Portability</A
 ></DT
 ><DD
 ><DL
 ><DT
->23.1. <A
-HREF="#AEN3115"
+>21.1. <A
+HREF="#AEN3251"
 >HPUX</A
 ></DT
 ><DT
->23.2. <A
-HREF="#AEN3121"
+>21.2. <A
+HREF="#AEN3257"
 >SCO Unix</A
 ></DT
 ><DT
->23.3. <A
-HREF="#AEN3125"
+>21.3. <A
+HREF="#AEN3261"
 >DNIX</A
 ></DT
 ><DT
->23.4. <A
-HREF="#AEN3154"
+>21.4. <A
+HREF="#AEN3290"
 >RedHat Linux Rembrandt-II</A
 ></DT
 ></DL
 ></DD
 ><DT
->24. <A
+>22. <A
 HREF="#OTHER-CLIENTS"
 >Samba and other CIFS clients</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.1. <A
-HREF="#AEN3175"
+>22.1. <A
+HREF="#AEN3311"
 >Macintosh clients?</A
 ></DT
 ><DT
->24.2. <A
-HREF="#AEN3184"
+>22.2. <A
+HREF="#AEN3320"
 >OS2 Client</A
 ></DT
 ><DT
->24.3. <A
-HREF="#AEN3224"
+>22.3. <A
+HREF="#AEN3360"
 >Windows for Workgroups</A
 ></DT
 ><DT
->24.4. <A
-HREF="#AEN3245"
+>22.4. <A
+HREF="#AEN3381"
 >Windows '95/'98</A
 ></DT
 ><DT
->24.5. <A
-HREF="#AEN3261"
+>22.5. <A
+HREF="#AEN3397"
 >Windows 2000 Service Pack 2</A
 ></DT
 ></DL
 ></DD
 ><DT
->25. <A
+>23. <A
 HREF="#BUGREPORT"
 >Reporting Bugs</A
 ></DT
 ><DD
 ><DL
 ><DT
->25.1. <A
-HREF="#AEN3285"
+>23.1. <A
+HREF="#AEN3421"
 >Introduction</A
 ></DT
 ><DT
->25.2. <A
-HREF="#AEN3295"
+>23.2. <A
+HREF="#AEN3431"
 >General info</A
 ></DT
 ><DT
->25.3. <A
-HREF="#AEN3301"
+>23.3. <A
+HREF="#AEN3437"
 >Debug levels</A
 ></DT
 ><DT
->25.4. <A
-HREF="#AEN3318"
+>23.4. <A
+HREF="#AEN3454"
 >Internal errors</A
 ></DT
 ><DT
->25.5. <A
-HREF="#AEN3328"
+>23.5. <A
+HREF="#AEN3464"
 >Attaching to a running process</A
 ></DT
 ><DT
->25.6. <A
-HREF="#AEN3331"
+>23.6. <A
+HREF="#AEN3467"
 >Patches</A
 ></DT
 ></DL
 ></DD
 ><DT
->26. <A
+>24. <A
 HREF="#DIAGNOSIS"
 >Diagnosing your samba server</A
 ></DT
 ><DD
 ><DL
 ><DT
->26.1. <A
-HREF="#AEN3354"
+>24.1. <A
+HREF="#AEN3490"
 >Introduction</A
 ></DT
 ><DT
->26.2. <A
-HREF="#AEN3359"
+>24.2. <A
+HREF="#AEN3495"
 >Assumptions</A
 ></DT
 ><DT
->26.3. <A
-HREF="#AEN3369"
+>24.3. <A
+HREF="#AEN3505"
 >Tests</A
 ></DT
 ><DT
->26.4. <A
-HREF="#AEN3479"
+>24.4. <A
+HREF="#AEN3615"
 >Still having troubles?</A
 ></DT
 ></DL
@@ -1061,7 +969,7 @@ HREF="#AEN3479"
 ><DIV
 CLASS="PART"
 ><A
-NAME="AEN18"
+NAME="INTRODUCTION"
 ></A
 ><DIV
 CLASS="TITLEPAGE"
@@ -1071,7 +979,7 @@ CLASS="TITLE"
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN20"
+NAME="AEN21"
 ></A
 ><H1
 >Introduction</H1
@@ -1096,27 +1004,27 @@ HREF="#INSTALL"
 ><DL
 ><DT
 >1.1. <A
-HREF="#AEN25"
+HREF="#AEN26"
 >Read the man pages</A
 ></DT
 ><DT
 >1.2. <A
-HREF="#AEN35"
+HREF="#AEN36"
 >Building the Binaries</A
 ></DT
 ><DT
 >1.3. <A
-HREF="#AEN63"
+HREF="#AEN64"
 >The all important step</A
 ></DT
 ><DT
 >1.4. <A
-HREF="#AEN67"
+HREF="#AEN68"
 >Create the smb configuration file.</A
 ></DT
 ><DT
 >1.5. <A
-HREF="#AEN81"
+HREF="#AEN82"
 >Test your config file with 
 	<B
 CLASS="COMMAND"
@@ -1125,75 +1033,75 @@ CLASS="COMMAND"
 ></DT
 ><DT
 >1.6. <A
-HREF="#AEN89"
+HREF="#AEN90"
 >Starting the smbd and nmbd</A
 ></DT
 ><DD
 ><DL
 ><DT
 >1.6.1. <A
-HREF="#AEN99"
+HREF="#AEN100"
 >Starting from inetd.conf</A
 ></DT
 ><DT
 >1.6.2. <A
-HREF="#AEN128"
+HREF="#AEN129"
 >Alternative: starting it as a daemon</A
 ></DT
 ></DL
 ></DD
 ><DT
 >1.7. <A
-HREF="#AEN144"
+HREF="#AEN145"
 >Try listing the shares available on your 
 	server</A
 ></DT
 ><DT
 >1.8. <A
-HREF="#AEN153"
+HREF="#AEN154"
 >Try connecting with the unix client</A
 ></DT
 ><DT
 >1.9. <A
-HREF="#AEN169"
+HREF="#AEN170"
 >Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</A
 ></DT
 ><DT
 >1.10. <A
-HREF="#AEN183"
+HREF="#AEN184"
 >What If Things Don't Work?</A
 ></DT
 ><DD
 ><DL
 ><DT
 >1.10.1. <A
-HREF="#AEN188"
+HREF="#AEN189"
 >Diagnosing Problems</A
 ></DT
 ><DT
 >1.10.2. <A
-HREF="#AEN192"
+HREF="#AEN193"
 >Scope IDs</A
 ></DT
 ><DT
 >1.10.3. <A
-HREF="#AEN195"
+HREF="#AEN196"
 >Choosing the Protocol Level</A
 ></DT
 ><DT
 >1.10.4. <A
-HREF="#AEN204"
+HREF="#AEN205"
 >Printing from UNIX to a Client PC</A
 ></DT
 ><DT
 >1.10.5. <A
-HREF="#AEN209"
+HREF="#AEN210"
 >Locking</A
 ></DT
 ><DT
 >1.10.6. <A
-HREF="#AEN218"
+HREF="#AEN219"
 >Mapping Usernames</A
 ></DT
 ></DL
@@ -1202,169 +1110,199 @@ HREF="#AEN218"
 ></DD
 ><DT
 >2. <A
-HREF="#IMPROVED-BROWSING"
->Improved browsing in samba</A
+HREF="#BROWSING-QUICK"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
 ></DT
 ><DD
 ><DL
 ><DT
 >2.1. <A
-HREF="#AEN228"
->Overview of browsing</A
+HREF="#AEN230"
+>Discussion</A
 ></DT
 ><DT
 >2.2. <A
-HREF="#AEN232"
->Browsing support in samba</A
+HREF="#AEN238"
+>Use of the "Remote Announce" parameter</A
 ></DT
 ><DT
 >2.3. <A
-HREF="#AEN241"
->Problem resolution</A
+HREF="#AEN252"
+>Use of the "Remote Browse Sync" parameter</A
 ></DT
 ><DT
 >2.4. <A
-HREF="#AEN248"
->Browsing across subnets</A
-></DT
-><DD
-><DL
-><DT
->2.4.1. <A
-HREF="#AEN253"
->How does cross subnet browsing work ?</A
+HREF="#AEN257"
+>Use of WINS</A
 ></DT
-></DL
-></DD
 ><DT
 >2.5. <A
-HREF="#AEN288"
->Setting up a WINS server</A
+HREF="#AEN268"
+>Do NOT use more than one (1) protocol on MS Windows machines</A
 ></DT
 ><DT
 >2.6. <A
-HREF="#AEN307"
->Setting up Browsing in a WORKGROUP</A
+HREF="#AEN274"
+>Name Resolution Order</A
 ></DT
+></DL
+></DD
 ><DT
->2.7. <A
-HREF="#AEN325"
->Setting up Browsing in a DOMAIN</A
+>3. <A
+HREF="#PASSDB"
+>User information database</A
 ></DT
+><DD
+><DL
 ><DT
->2.8. <A
-HREF="#AEN335"
->Forcing samba to be the master</A
+>3.1. <A
+HREF="#AEN324"
+>Introduction</A
 ></DT
 ><DT
->2.9. <A
-HREF="#AEN344"
->Making samba the domain master</A
+>3.2. <A
+HREF="#AEN331"
+>Important Notes About Security</A
 ></DT
+><DD
+><DL
 ><DT
->2.10. <A
-HREF="#AEN362"
->Note about broadcast addresses</A
+>3.2.1. <A
+HREF="#AEN346"
+>Advantages of SMB Encryption</A
 ></DT
 ><DT
->2.11. <A
-HREF="#AEN365"
->Multiple interfaces</A
+>3.2.2. <A
+HREF="#AEN351"
+>Advantages of non-encrypted passwords</A
 ></DT
 ></DL
 ></DD
 ><DT
->3. <A
-HREF="#OPLOCKS"
->Oplocks</A
+>3.3. <A
+HREF="#AEN357"
+>The smbpasswd Command</A
 ></DT
-><DD
-><DL
 ><DT
->3.1. <A
-HREF="#AEN377"
->What are oplocks?</A
+>3.4. <A
+HREF="#AEN388"
+>Plain text</A
 ></DT
-></DL
-></DD
 ><DT
->4. <A
-HREF="#BROWSING-QUICK"
->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
+>3.5. <A
+HREF="#AEN393"
+>TDB</A
+></DT
+><DT
+>3.6. <A
+HREF="#AEN396"
+>LDAP</A
 ></DT
 ><DD
 ><DL
 ><DT
->4.1. <A
-HREF="#AEN392"
->Discussion</A
+>3.6.1. <A
+HREF="#AEN398"
+>Introduction</A
 ></DT
 ><DT
->4.2. <A
-HREF="#AEN400"
->Use of the "Remote Announce" parameter</A
+>3.6.2. <A
+HREF="#AEN418"
+>Introduction</A
 ></DT
 ><DT
->4.3. <A
-HREF="#AEN414"
->Use of the "Remote Browse Sync" parameter</A
+>3.6.3. <A
+HREF="#AEN447"
+>Supported LDAP Servers</A
 ></DT
 ><DT
->4.4. <A
-HREF="#AEN419"
->Use of WINS</A
+>3.6.4. <A
+HREF="#AEN452"
+>Schema and Relationship to the RFC 2307 posixAccount</A
 ></DT
 ><DT
->4.5. <A
-HREF="#AEN430"
->Do NOT use more than one (1) protocol on MS Windows machines</A
+>3.6.5. <A
+HREF="#AEN464"
+>Configuring Samba with LDAP</A
 ></DT
 ><DT
->4.6. <A
-HREF="#AEN436"
->Name Resolution Order</A
+>3.6.6. <A
+HREF="#AEN511"
+>Accounts and Groups management</A
+></DT
+><DT
+>3.6.7. <A
+HREF="#AEN516"
+>Security and sambaAccount</A
+></DT
+><DT
+>3.6.8. <A
+HREF="#AEN536"
+>LDAP specials attributes for sambaAccounts</A
+></DT
+><DT
+>3.6.9. <A
+HREF="#AEN606"
+>Example LDIF Entries for a sambaAccount</A
 ></DT
 ></DL
 ></DD
 ><DT
->5. <A
-HREF="#PWENCRYPT"
->LanMan and NT Password Encryption in Samba</A
+>3.7. <A
+HREF="#AEN614"
+>MySQL</A
 ></DT
 ><DD
 ><DL
 ><DT
->5.1. <A
-HREF="#AEN472"
->Introduction</A
+>3.7.1. <A
+HREF="#AEN616"
+>Building</A
 ></DT
 ><DT
->5.2. <A
-HREF="#AEN477"
->Important Notes About Security</A
+>3.7.2. <A
+HREF="#AEN622"
+>Creating the database</A
 ></DT
-><DD
-><DL
 ><DT
->5.2.1. <A
-HREF="#AEN496"
->Advantages of SMB Encryption</A
+>3.7.3. <A
+HREF="#AEN632"
+>Configuring</A
 ></DT
 ><DT
->5.2.2. <A
-HREF="#AEN503"
->Advantages of non-encrypted passwords</A
+>3.7.4. <A
+HREF="#AEN649"
+>Using plaintext passwords or encrypted password</A
+></DT
+><DT
+>3.7.5. <A
+HREF="#AEN654"
+>Getting non-column data from the table</A
 ></DT
 ></DL
 ></DD
 ><DT
->5.3. <A
-HREF="#AEN512"
->The smbpasswd Command</A
+>3.8. <A
+HREF="#AEN662"
+>Passdb XML plugin</A
+></DT
+><DD
+><DL
+><DT
+>3.8.1. <A
+HREF="#AEN664"
+>Building</A
+></DT
+><DT
+>3.8.2. <A
+HREF="#AEN670"
+>Usage</A
 ></DT
 ></DL
 ></DD
 ></DL
+></DD
+></DL
 ></DIV
 ></DIV
 ><DIV
@@ -1379,7 +1317,7 @@ CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN25"
+NAME="AEN26"
 ></A
 >1.1. Read the man pages</H2
 ><P
@@ -1421,7 +1359,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN35"
+NAME="AEN36"
 ></A
 >1.2. Building the Binaries</H2
 ><P
@@ -1520,7 +1458,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN63"
+NAME="AEN64"
 ></A
 >1.3. The all important step</H2
 ><P
@@ -1537,7 +1475,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN67"
+NAME="AEN68"
 ></A
 >1.4. Create the smb configuration file.</H2
 ><P
@@ -1593,7 +1531,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN81"
+NAME="AEN82"
 ></A
 >1.5. Test your config file with 
 	<B
@@ -1623,7 +1561,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN89"
+NAME="AEN90"
 ></A
 >1.6. Starting the smbd and nmbd</H2
 ><P
@@ -1663,7 +1601,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN99"
+NAME="AEN100"
 ></A
 >1.6.1. Starting from inetd.conf</H3
 ><P
@@ -1767,7 +1705,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN128"
+NAME="AEN129"
 ></A
 >1.6.2. Alternative: starting it as a daemon</H3
 ><P
@@ -1824,7 +1762,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN144"
+NAME="AEN145"
 ></A
 >1.7. Try listing the shares available on your 
 	server</H2
@@ -1865,7 +1803,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN153"
+NAME="AEN154"
 ></A
 >1.8. Try connecting with the unix client</H2
 ><P
@@ -1928,7 +1866,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN169"
+NAME="AEN170"
 ></A
 >1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</H2
@@ -1977,7 +1915,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN183"
+NAME="AEN184"
 ></A
 >1.10. What If Things Don't Work?</H2
 ><P
@@ -2000,7 +1938,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN188"
+NAME="AEN189"
 ></A
 >1.10.1. Diagnosing Problems</H3
 ><P
@@ -2017,7 +1955,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN192"
+NAME="AEN193"
 ></A
 >1.10.2. Scope IDs</H3
 ><P
@@ -2033,7 +1971,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN195"
+NAME="AEN196"
 ></A
 >1.10.3. Choosing the Protocol Level</H3
 ><P
@@ -2074,7 +2012,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN204"
+NAME="AEN205"
 ></A
 >1.10.4. Printing from UNIX to a Client PC</H3
 ><P
@@ -2095,7 +2033,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN209"
+NAME="AEN210"
 ></A
 >1.10.5. Locking</H3
 ><P
@@ -2155,7 +2093,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN218"
+NAME="AEN219"
 ></A
 >1.10.6. Mapping Usernames</H3
 ><P
@@ -2169,802 +2107,9 @@ NAME="AEN218"
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="IMPROVED-BROWSING"
-></A
->Chapter 2. Improved browsing in samba</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN228"
-></A
->2.1. Overview of browsing</H2
-><P
->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.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN232"
-></A
->2.2. Browsing support in samba</H2
-><P
->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)).</P
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-><P
->[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].</P
-><P
->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.</P
-><P
->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.  </P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN241"
-></A
->2.3. Problem resolution</H2
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-><P
->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)</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN248"
-></A
->2.4. Browsing across subnets</H2
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN253"
-></A
->2.4.1. How does cross subnet browsing work ?</H3
-><P
->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.</P
-><P
->Consider a network set up as follows :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->                                   (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)</PRE
-></P
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-><P
->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'.</P
-><P
->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).</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->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</PRE
-></P
-><P
->Note that at this point all the subnets are separate, no
-machine is seen across any of the subnets.</P
-><P
->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&gt;1B&lt;.  This name was registerd by the Domain master
-browser (N1_C) with the WINS server as soon as it was booted.</P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->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.</PRE
-></P
-><P
->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.</P
-><P
->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.</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->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.</PRE
-></P
-><P
->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.</P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->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.</PRE
-></P
-><P
->Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.</P
-><P
->If either router R1 or R2 fails the following will occur:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->	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.
-	</P
-></LI
-><LI
-><P
->	Attempts to connect to these inaccessible computers will fail, but the
-	names will not be removed from the network neighbourhood lists.
-	</P
-></LI
-><LI
-><P
->	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.
-	</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN288"
-></A
->2.5. Setting up a WINS server</H2
-><P
->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 </P
-><P
-><B
-CLASS="COMMAND"
->		wins support = yes</B
-></P
-><P
->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.</P
-><P
->Machines with "<B
-CLASS="COMMAND"
->wins support = yes</B
->" will keep a list of 
-all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P
-><P
->You should set up only ONE wins server.  Do NOT set the
-"<B
-CLASS="COMMAND"
->wins support = yes</B
->" option on more than one Samba 
-server.</P
-><P
->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-&#62;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.</P
-><P
->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-&#62;Network-&#62;Protocols-&#62;TCP-&#62;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 :</P
-><P
-><B
-CLASS="COMMAND"
->wins server = &gt;name or IP address&lt;</B
-></P
-><P
->where &gt;name or IP address&lt; is either the DNS name of the WINS server
-machine or its IP address.</P
-><P
->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
-"<B
-CLASS="COMMAND"
->wins support = yes</B
->" option and the 
-"<B
-CLASS="COMMAND"
->wins server = &gt;name&lt;</B
->" option then
-nmbd will fail to start.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN307"
-></A
->2.6. Setting up Browsing in a WORKGROUP</H2
-><P
->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.</P
-><P
->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 :</P
-><P
-><B
-CLASS="COMMAND"
->domain master = yes</B
-></P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        domain master = yes
-        local master = yes
-        preferred master = yes
-        os level = 65</PRE
-></P
-><P
->The domain master browser may be the same machine as the WINS
-server, if you require.</P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        domain master = no
-        local master = yes
-        preferred master = yes
-        os level = 65</PRE
-></P
-><P
->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.</P
-><P
->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.</P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0</PRE
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN325"
-></A
->2.7. Setting up Browsing in a DOMAIN</H2
-><P
->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&gt;1B&lt;) with WINS instead of the PDC.</P
-><P
->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 :</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        domain master = no
-        local master = yes
-        preferred master = yes
-        os level = 65</PRE
-></P
-><P
->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.</P
-><P
->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 :</P
-><P
-><B
-CLASS="COMMAND"
->        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0</B
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN335"
-></A
->2.8. Forcing samba to be the master</H2
-><P
->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.</P
-><P
->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!)</P
-><P
->A "os level" of 2 would make it beat WfWg and Win95, but not NTAS.  A
-NTAS domain controller uses level 32.</P
-><P
->The maximum os level is 255</P
-><P
->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.</P
-><P
->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.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN344"
-></A
->2.9. Making samba the domain master</H2
-><P
->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.</P
-><P
->Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain.</P
-><P
->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.</P
-><P
->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.</P
-><P
->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:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->	your local master browsers will be unable to find a domain master
-	browser, as it will only be looking on the local subnet.
-	</P
-></LI
-><LI
-><P
->	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.
-	</P
-></LI
-></OL
-><P
->If, however, both samba and your clients are using a WINS server, then:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->	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.
-	</P
-></LI
-><LI
-><P
->	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.  
-	</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN362"
-></A
->2.10. Note about broadcast addresses</H2
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN365"
-></A
->2.11. Multiple interfaces</H2
-><P
->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.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="OPLOCKS"
-></A
->Chapter 3. Oplocks</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN377"
-></A
->3.1. What are oplocks?</H2
-><P
->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.</P
-><P
->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.</P
-><P
->"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.</P
-><P
->"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.</P
-><P
->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.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
 NAME="BROWSING-QUICK"
 ></A
->Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
+>Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
 ><P
 >This document should be read in conjunction with Browsing and may
 be taken as the fast track guide to implementing browsing across subnets
@@ -2976,9 +2121,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN392"
+NAME="AEN230"
 ></A
->4.1. Discussion</H2
+>2.1. Discussion</H2
 ><P
 >Firstly, all MS Windows networking is based on SMB (Server Message
 Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
@@ -3022,9 +2167,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN400"
+NAME="AEN238"
 ></A
->4.2. Use of the "Remote Announce" parameter</H2
+>2.2. Use of the "Remote Announce" parameter</H2
 ><P
 >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.
@@ -3073,16 +2218,16 @@ name resolution problems and should be avoided.</P
 ></DD
 ></DL
 ></DIV
->&#13;</P
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN414"
+NAME="AEN252"
 ></A
->4.3. Use of the "Remote Browse Sync" parameter</H2
+>2.3. Use of the "Remote Browse Sync" parameter</H2
 ><P
 >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
@@ -3090,9 +2235,10 @@ Samba LMB. It works ONLY if the Samba server that has this option is
 simultaneously the LMB on it's network segment.</P
 ><P
 >The syntax of the "remote browse  sync" parameter is:
+
 <PRE
 CLASS="PROGRAMLISTING"
->	remote browse sync = a.b.c.d</PRE
+>remote browse sync = a.b.c.d</PRE
 >
 
 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.</P
@@ -3102,9 +2248,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN419"
+NAME="AEN257"
 ></A
->4.4. Use of WINS</H2
+>2.4. Use of WINS</H2
 ><P
 >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
@@ -3164,9 +2310,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN430"
+NAME="AEN268"
 ></A
->4.5. Do NOT use more than one (1) protocol on MS Windows machines</H2
+>2.5. Do NOT use more than one (1) protocol on MS Windows machines</H2
 ><P
 >A very common cause of browsing problems results from installing more than
 one protocol on an MS Windows machine.</P
@@ -3194,14 +2340,14 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN436"
+NAME="AEN274"
 ></A
->4.6. Name Resolution Order</H2
+>2.6. Name Resolution Order</H2
 ><P
 >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:
-<P
+are:</P
+><P
 ></P
 ><TABLE
 BORDER="0"
@@ -3222,10 +2368,9 @@ BORDER="0"
 ></TABLE
 ><P
 ></P
-></P
 ><P
->Alternative means of name resolution includes:
-<P
+>Alternative means of name resolution includes:</P
+><P
 ></P
 ><TABLE
 BORDER="0"
@@ -3242,24 +2387,23 @@ BORDER="0"
 ></TABLE
 ><P
 ></P
-></P
 ><P
 >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:
 <PRE
 CLASS="PROGRAMLISTING"
->	name resolve order = wins lmhosts bcast host</PRE
+>name resolve order = wins lmhosts bcast host</PRE
 >
 _or_
 <PRE
 CLASS="PROGRAMLISTING"
->	name resolve order = wins lmhosts  	(eliminates bcast and host)</PRE
+>name resolve order = wins lmhosts  	(eliminates bcast and host)</PRE
 >
 The default is:
 <PRE
 CLASS="PROGRAMLISTING"
->	name  resolve order = host lmhost wins bcast</PRE
+>name  resolve order = host lmhost wins bcast</PRE
 >.
 where "host" refers the the native methods used by the Unix system
 to implement the gethostbyname() function call. This is normally
@@ -3279,28 +2423,45 @@ CLASS="FILENAME"
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="PWENCRYPT"
+NAME="PASSDB"
 ></A
->Chapter 5. LanMan and NT Password Encryption in Samba</H1
+>Chapter 3. User information database</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN472"
+NAME="AEN324"
 ></A
->5.1. Introduction</H2
+>3.1. Introduction</H2
+><P
+>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.
+	</P
 ><P
->Newer windows clients send encrypted passwords over 
+>	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.</P
+	passwords, unless their registry is tweaked.
+	</P
 ><P
 >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 <B
+	somewhere else. </P
+><P
+>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 
+	<B
 CLASS="COMMAND"
 >passdb backend = </B
 > parameter.
@@ -3311,9 +2472,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN477"
+NAME="AEN331"
 ></A
->5.2. Important Notes About Security</H2
+>3.2. Important Notes About Security</H2
 ><P
 >The unix and SMB password encryption techniques seem similar 
 	on the surface. This similarity is, however, only skin deep. The unix 
@@ -3325,7 +2486,8 @@ NAME="AEN477"
 	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 
+	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.</P
 ><P
@@ -3347,7 +2509,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TD
@@ -3372,26 +2534,31 @@ CLASS="EMPHASIS"
 		this behavior includes</P
 ><P
 ></P
-><UL
-><LI
-><P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
 >MS DOS Network client 3.0 with 
-			the basic network redirector installed</P
-></LI
-><LI
-><P
+			the basic network redirector installed</TD
+></TR
+><TR
+><TD
 >Windows 95 with the network redirector 
-			update installed</P
-></LI
-><LI
-><P
->Windows 98 [se]</P
-></LI
-><LI
+			update installed</TD
+></TR
+><TR
+><TD
+>Windows 98 [se]</TD
+></TR
+><TR
+><TD
+>Windows 2000</TD
+></TR
+></TBODY
+></TABLE
 ><P
->Windows 2000</P
-></LI
-></UL
+></P
 ><P
 ><SPAN
 CLASS="emphasis"
@@ -3413,59 +2580,69 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN496"
+NAME="AEN346"
 ></A
->5.2.1. Advantages of SMB Encryption</H3
+>3.2.1. Advantages of SMB Encryption</H3
 ><P
 ></P
-><UL
-><LI
-><P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
 >plain text passwords are not passed across 
 			the network. Someone using a network sniffer cannot just 
-			record passwords going to the SMB server.</P
-></LI
-><LI
-><P
+			record passwords going to the SMB server.</TD
+></TR
+><TR
+><TD
 >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.
-			</P
-></LI
-></UL
+			</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN503"
+NAME="AEN351"
 ></A
->5.2.2. Advantages of non-encrypted passwords</H3
+>3.2.2. Advantages of non-encrypted passwords</H3
 ><P
 ></P
-><UL
-><LI
-><P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
 >plain text passwords are not kept 
-			on disk. </P
-></LI
-><LI
-><P
+			on disk. </TD
+></TR
+><TR
+><TD
 >uses same password file as other unix 
-			services such as login and ftp</P
-></LI
-><LI
-><P
+			services such as login and ftp</TD
+></TR
+><TR
+><TD
 >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.</P
-></LI
-></UL
+			such a big deal.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
 ></DIV
 ></DIV
 ><DIV
@@ -3473,36 +2650,32 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN512"
+NAME="AEN357"
 ></A
->5.3. The smbpasswd Command</H2
+>3.3. The smbpasswd Command</H2
 ><P
->The smbpasswd command maintains the two 32 byte password fields 
-	in the smbpasswd file. If you wish to make it similar to the unix 
+>The smbpasswd utility is a utility similar to the 
 	<B
 CLASS="COMMAND"
 >passwd</B
 > or <B
 CLASS="COMMAND"
 >yppasswd</B
-> programs, 
-	install it in <TT
-CLASS="FILENAME"
->/usr/local/samba/bin/</TT
-> (or your 
-	main Samba binary directory).</P
+> programs.
+	It maintains the two 32 byte password fields 
+	in the passdb backend. </P
 ><P
 ><B
 CLASS="COMMAND"
 >smbpasswd</B
-> now works in a client-server mode 
+> 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.</P
 ><P
 ><B
 CLASS="COMMAND"
 >smbpasswd</B
-> now has the capability 
+> 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).</P
@@ -3584,12 +2757,1184 @@ CLASS="COMMAND"
 > refer 
 	to the man page which will always be the definitive reference.</P
 ></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN388"
+></A
+>3.4. Plain text</H2
+><P
+>Older versions of samba retrieved user information from the unix user database 
+and eventually some other fields from the file <TT
+CLASS="FILENAME"
+>/etc/samba/smbpasswd</TT
+>
+or <TT
+CLASS="FILENAME"
+>/etc/smbpasswd</TT
+>. When password encryption is disabled, no 
+data is stored at all.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN393"
+></A
+>3.5. TDB</H2
+><P
+>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.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN396"
+></A
+>3.6. LDAP</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN398"
+></A
+>3.6.1. Introduction</H3
+><P
+>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.</P
+><P
+></P
+><UL
+><LI
+><P
+>OpenLDAP - <A
+HREF="http://www.openldap.org/"
+TARGET="_top"
+>http://www.openldap.org/</A
+></P
+></LI
+><LI
+><P
+>iPlanet Directory Server - <A
+HREF="http://iplanet.netscape.com/directory"
+TARGET="_top"
+>http://iplanet.netscape.com/directory</A
+></P
+></LI
+></UL
+><P
+>Note that <A
+HREF="http://www.ora.com/"
+TARGET="_top"
+>O'Reilly Publishing</A
+> is working on
+a guide to LDAP for System Administrators which has a planned release date of
+early summer, 2002.</P
+><P
+>Two additional Samba resources which may prove to be helpful are</P
+><P
+></P
+><UL
+><LI
+><P
+>The <A
+HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html"
+TARGET="_top"
+>Samba-PDC-LDAP-HOWTO</A
+>
+	maintained by Ignacio Coupeau.</P
+></LI
+><LI
+><P
+>The NT migration scripts from <A
+HREF="http://samba.idealx.org/"
+TARGET="_top"
+>IDEALX</A
+> that are
+	geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
+	</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN418"
+></A
+>3.6.2. Introduction</H3
+><P
+>Traditionally, when configuring <A
+HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
+TARGET="_top"
+>"encrypt
+passwords = yes"</A
+> in Samba's <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file, user account
+information such as username, LM/NT password hashes, password change times, and account
+flags have been stored in the <TT
+CLASS="FILENAME"
+>smbpasswd(5)</TT
+> file.  There are several
+disadvantages to this approach for sites with very large numbers of users (counted
+in the thousands).</P
+><P
+></P
+><UL
+><LI
+><P
+>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.</P
+></LI
+><LI
+><P
+>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 <B
+CLASS="COMMAND"
+>rsync(1)</B
+> and <B
+CLASS="COMMAND"
+>ssh(1)</B
+>
+and wrote custom, in-house scripts.</P
+></LI
+><LI
+><P
+>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).</P
+></LI
+></UL
+><P
+>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. <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+> or
+<TT
+CLASS="PARAMETER"
+><I
+>--with-tdbsam</I
+></TT
+>) requires compile time support.</P
+><P
+>When compiling Samba to include the <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+> 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.</P
+><P
+>There are a few points to stress about what the <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+>
+does not provide.  The LDAP support referred to in the this documentation does not
+include:</P
+><P
+></P
+><UL
+><LI
+><P
+>A means of retrieving user account information from
+	an Windows 2000 Active Directory server.</P
+></LI
+><LI
+><P
+>A means of replacing /etc/passwd.</P
+></LI
+></UL
+><P
+>The second item can be accomplished by using LDAP NSS and PAM modules.  LGPL
+versions of these libraries can be obtained from PADL Software
+(<A
+HREF="http://www.padl.com/"
+TARGET="_top"
+>http://www.padl.com/</A
+>).  However,
+the details of configuring these packages are beyond the scope of this document.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN447"
+></A
+>3.6.3. Supported LDAP Servers</H3
+><P
+>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
+<A
+HREF="samba-patches@samba.org"
+TARGET="_top"
+>samba-patches@samba.org</A
+> and
+<A
+HREF="jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN452"
+></A
+>3.6.4. Schema and Relationship to the RFC 2307 posixAccount</H3
+><P
+>Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
+<TT
+CLASS="FILENAME"
+>examples/LDAP/samba.schema</TT
+>.  The sambaAccount objectclass is given here:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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 ))</PRE
+></P
+><P
+>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 <A
+HREF="jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+></P
+><P
+>Just as the smbpasswd file is mean to store information which supplements a
+user's <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry, so is the sambaAccount object
+meant to supplement the UNIX user account information.  A sambaAccount is a
+<TT
+CLASS="CONSTANT"
+>STRUCTURAL</TT
+> 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.</P
+><P
+>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.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN464"
+></A
+>3.6.5. Configuring Samba with LDAP</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN466"
+></A
+>3.6.5.1. OpenLDAP configuration</H4
+><P
+>To include support for the sambaAccount object in an OpenLDAP directory
+server, first copy the samba.schema file to slapd's configuration directory.</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>cp samba.schema /etc/openldap/schema/</B
+></P
+><P
+>Next, include the <TT
+CLASS="FILENAME"
+>samba.schema</TT
+> file in <TT
+CLASS="FILENAME"
+>slapd.conf</TT
+>.
+The sambaAccount object contains two attributes which depend upon other schema
+files.  The 'uid' attribute is defined in <TT
+CLASS="FILENAME"
+>cosine.schema</TT
+> and
+the 'displayName' attribute is defined in the <TT
+CLASS="FILENAME"
+>inetorgperson.schema</TT
+>
+file.  Both of these must be included before the <TT
+CLASS="FILENAME"
+>samba.schema</TT
+> file.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## /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
+
+....</PRE
+></P
+><P
+>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).</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+># 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</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN483"
+></A
+>3.6.5.2. Configuring Samba</H4
+><P
+>The following parameters are available in smb.conf only with <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+>
+was included with compiling Samba.</P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSSL"
+TARGET="_top"
+>ldap ssl</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSERVER"
+TARGET="_top"
+>ldap server</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPADMINDN"
+TARGET="_top"
+>ldap admin dn</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSUFFIX"
+TARGET="_top"
+>ldap suffix</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPFILTER"
+TARGET="_top"
+>ldap filter</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPPORT"
+TARGET="_top"
+>ldap port</A
+></P
+></LI
+></UL
+><P
+>These are described in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+> man
+page and so will not be repeated here.  However, a sample smb.conf file for
+use with an LDAP directory could appear as</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## /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 <TT
+CLASS="REPLACEABLE"
+><I
+>secretpw</I
+></TT
+>' 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 = "(&amp;(uid=%u)(objectclass=sambaAccount))"</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN511"
+></A
+>3.6.6. Accounts and Groups management</H3
+><P
+>As users accounts are managed thru the sambaAccount objectclass, you should
+modify you existing administration tools to deal with sambaAccount attributes.</P
+><P
+>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).</P
+><P
+>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).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN516"
+></A
+>3.6.7. Security and sambaAccount</H3
+><P
+>There are two important points to remember when discussing the security
+of sambaAccount entries in the directory.</P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Never</I
+></SPAN
+> retrieve the lmPassword or
+	ntPassword attribute values over an unencrypted LDAP session.</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Never</I
+></SPAN
+> allow non-admin users to
+	view the lmPassword or ntPassword attribute values.</P
+></LI
+></UL
+><P
+>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 <A
+HREF="ENCRYPTION.html"
+TARGET="_top"
+>ENCRYPTION chapter</A
+> of the Samba-HOWTO-Collection.</P
+><P
+>To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
+to require an encrypted session (<B
+CLASS="COMMAND"
+>ldap ssl = on</B
+>) 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
+(<B
+CLASS="COMMAND"
+>ldap ssl = off</B
+>).</P
+><P
+>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.</P
+><P
+>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 <TT
+CLASS="FILENAME"
+>slapd.conf</TT
+>:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## 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</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN536"
+></A
+>3.6.8. LDAP specials attributes for sambaAccounts</H3
+><P
+>The sambaAccount objectclass is composed of the following attributes:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmPassword</TT
+>: the LANMAN password 16-byte hash stored as a character
+	representation of a hexidecimal string.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>ntPassword</TT
+>: the NT password hash 16-byte stored as a character
+	representation of a hexidecimal string.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdLastSet</TT
+>: The integer time in seconds since 1970 when the
+	<TT
+CLASS="CONSTANT"
+>lmPassword</TT
+> and <TT
+CLASS="CONSTANT"
+>ntPassword</TT
+> attributes were last set.
+	</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>acctFlags</TT
+>: string of 11 characters surrounded by square brackets []
+	representing account flags such as U (user), W(workstation), X(no password expiration), and
+	D(disabled).</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>logonTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>logoffTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>kickoffTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdCanChange</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdMustChange</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>homeDrive</TT
+>: 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.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>scriptPath</TT
+>: 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.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>profilePath</TT
+>: 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.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>smbHome</TT
+>: 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.
+	</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>userWorkstation</TT
+>: character string value currently unused.
+	</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>rid</TT
+>: the integer representation of the user's relative identifier
+	(RID).</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>primaryGroupID</TT
+>: the relative identifier (RID) of the primary group
+	of the user.</P
+></LI
+></UL
+><P
+>The majority of these parameters are only used when Samba is acting as a PDC of
+a domain (refer to the <A
+HREF="Samba-PDC-HOWTO.html"
+TARGET="_top"
+>Samba-PDC-HOWTO</A
+> 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:</P
+><P
+></P
+><UL
+><LI
+><P
+>smbHome</P
+></LI
+><LI
+><P
+>scriptPath</P
+></LI
+><LI
+><P
+>logonPath</P
+></LI
+><LI
+><P
+>homeDrive</P
+></LI
+></UL
+><P
+>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 <B
+CLASS="COMMAND"
+>logon home = \\%L\%u</B
+> was defined in
+its <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. When a user named "becky" logons to the domain,
+the <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+> 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 <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+> 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).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN606"
+></A
+>3.6.9. Example LDIF Entries for a sambaAccount</H3
+><P
+>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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</PRE
+></P
+><P
+>The following is an LDIF entry for using both the sambaAccount and
+posixAccount objectclasses:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN614"
+></A
+>3.7. MySQL</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN616"
+></A
+>3.7.1. Building</H3
+><P
+>To build the plugin, run <B
+CLASS="COMMAND"
+>make bin/pdb_mysql.so</B
+>
+in the <TT
+CLASS="FILENAME"
+>source/</TT
+> directory of samba distribution. </P
+><P
+>Next, copy pdb_mysql.so to any location you want. I 
+strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN622"
+></A
+>3.7.2. Creating the database</H3
+><P
+>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 <TT
+CLASS="FILENAME"
+>examples/pdb/mysql/mysql.dump</TT
+> 
+contains the correct queries to create the required tables. Use the command :
+
+<B
+CLASS="COMMAND"
+>mysql -u<TT
+CLASS="REPLACEABLE"
+><I
+>username</I
+></TT
+> -h<TT
+CLASS="REPLACEABLE"
+><I
+>hostname</I
+></TT
+> -p<TT
+CLASS="REPLACEABLE"
+><I
+>password</I
+></TT
+> <TT
+CLASS="REPLACEABLE"
+><I
+>databasename</I
+></TT
+> &#60; <TT
+CLASS="FILENAME"
+>/path/to/samba/examples/pdb/mysql/mysql.dump</TT
+></B
+>&#13;</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN632"
+></A
+>3.7.3. Configuring</H3
+><P
+>This plugin lacks some good documentation, but here is some short info:</P
+><P
+>Add a the following to the <B
+CLASS="COMMAND"
+>passdb backend</B
+> variable in your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>:
+<PRE
+CLASS="PROGRAMLISTING"
+>passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE
+></P
+><P
+>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!</P
+><P
+>Additional options can be given thru the smb.conf file in the [global] section.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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</PRE
+></P
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>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.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Names of the columns in this table(I've added column types those columns should have first):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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</PRE
+></P
+><P
+>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. </P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN649"
+></A
+>3.7.4. Using plaintext passwords or encrypted password</H3
+><P
+>I strongly discourage the use of plaintext passwords, however, you can use them:</P
+><P
+>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. </P
+><P
+>If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN654"
+></A
+>3.7.5. Getting non-column data from the table</H3
+><P
+>It is possible to have not all data in the database and making some 'constant'.</P
+><P
+>For example, you can set 'identifier:fullname column' to : 
+<B
+CLASS="COMMAND"
+>CONCAT(First_name,' ',Sur_name)</B
+></P
+><P
+>Or, set 'identifier:workstations column' to :
+<B
+CLASS="COMMAND"
+>NULL</B
+></P
+><P
+>See the MySQL documentation for more language constructs.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN662"
+></A
+>3.8. Passdb XML plugin</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN664"
+></A
+>3.8.1. Building</H3
+><P
+>This module requires libxml2 to be installed.</P
+><P
+>To build pdb_xml, run: <B
+CLASS="COMMAND"
+>make bin/pdb_xml.so</B
+> in 
+the directory <TT
+CLASS="FILENAME"
+>source/</TT
+>. </P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN670"
+></A
+>3.8.2. Usage</H3
+><P
+>The usage of pdb_xml is pretty straightforward. To export data, use:
+
+<B
+CLASS="COMMAND"
+>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B
+>
+
+(where filename is the name of the file to put the data in)</P
+><P
+>To import data, use:
+<B
+CLASS="COMMAND"
+>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B
+>
+
+Where filename is the name to read the data from and current-pdb to put it in.</P
+></DIV
+></DIV
 ></DIV
 ></DIV
 ><DIV
 CLASS="PART"
 ><A
-NAME="AEN544"
+NAME="TYPE"
 ></A
 ><DIV
 CLASS="TITLEPAGE"
@@ -3599,14 +3944,13 @@ CLASS="TITLE"
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN546"
+NAME="AEN678"
 ></A
 ><H1
 >Introduction</H1
 ><P
->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.</P
+>Samba can operate in various SMB networks. This part contains information on configuring samba 
+for various environments.</P
 ></DIV
 ><DIV
 CLASS="TOC"
@@ -3616,228 +3960,238 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->6. <A
+>4. <A
+HREF="#SECURITYLEVELS"
+>User and Share security level (for servers not in a domain)</A
+></DT
+><DT
+>5. <A
 HREF="#SAMBA-PDC"
->How to Configure Samba as a NT4 Primary Domain Controller</A
+>Samba as a NT4 or Win2k Primary Domain Controller</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.1. <A
-HREF="#AEN566"
+>5.1. <A
+HREF="#AEN722"
 >Prerequisite Reading</A
 ></DT
 ><DT
->6.2. <A
-HREF="#AEN572"
+>5.2. <A
+HREF="#AEN728"
 >Background</A
 ></DT
 ><DT
->6.3. <A
-HREF="#AEN611"
+>5.3. <A
+HREF="#AEN767"
 >Configuring the Samba Domain Controller</A
 ></DT
 ><DT
->6.4. <A
-HREF="#AEN654"
+>5.4. <A
+HREF="#AEN810"
 >Creating Machine Trust Accounts and Joining Clients to the
 Domain</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.4.1. <A
-HREF="#AEN673"
+>5.4.1. <A
+HREF="#AEN829"
 >Manual Creation of Machine Trust Accounts</A
 ></DT
 ><DT
->6.4.2. <A
-HREF="#AEN714"
+>5.4.2. <A
+HREF="#AEN870"
 >"On-the-Fly" Creation of Machine Trust Accounts</A
 ></DT
 ><DT
->6.4.3. <A
-HREF="#AEN723"
+>5.4.3. <A
+HREF="#AEN879"
 >Joining the Client to the Domain</A
 ></DT
 ></DL
 ></DD
 ><DT
->6.5. <A
-HREF="#AEN738"
+>5.5. <A
+HREF="#AEN894"
 >Common Problems and Errors</A
 ></DT
 ><DT
->6.6. <A
-HREF="#AEN786"
+>5.6. <A
+HREF="#AEN942"
 >System Policies and Profiles</A
 ></DT
 ><DT
->6.7. <A
-HREF="#AEN830"
+>5.7. <A
+HREF="#AEN986"
 >What other help can I get?</A
 ></DT
 ><DT
->6.8. <A
-HREF="#AEN944"
+>5.8. <A
+HREF="#AEN1100"
 >Domain Control for Windows 9x/ME</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.8.1. <A
-HREF="#AEN970"
+>5.8.1. <A
+HREF="#AEN1126"
 >Configuration Instructions:	Network Logons</A
 ></DT
 ><DT
->6.8.2. <A
-HREF="#AEN989"
+>5.8.2. <A
+HREF="#AEN1145"
 >Configuration Instructions:	Setting up Roaming User Profiles</A
 ></DT
 ></DL
 ></DD
 ><DT
->6.9. <A
-HREF="#AEN1082"
->DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
+>5.9. <A
+HREF="#AEN1238"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control &amp; Samba</A
 ></DT
 ></DL
 ></DD
 ><DT
->7. <A
+>6. <A
 HREF="#SAMBA-BDC"
 >How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.1. <A
-HREF="#AEN1118"
+>6.1. <A
+HREF="#AEN1274"
 >Prerequisite Reading</A
 ></DT
 ><DT
->7.2. <A
-HREF="#AEN1122"
+>6.2. <A
+HREF="#AEN1278"
 >Background</A
 ></DT
 ><DT
->7.3. <A
-HREF="#AEN1130"
+>6.3. <A
+HREF="#AEN1286"
 >What qualifies a Domain Controller on the network?</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.3.1. <A
-HREF="#AEN1133"
+>6.3.1. <A
+HREF="#AEN1289"
 >How does a Workstation find its domain controller?</A
 ></DT
 ><DT
->7.3.2. <A
-HREF="#AEN1136"
+>6.3.2. <A
+HREF="#AEN1292"
 >When is the PDC needed?</A
 ></DT
 ></DL
 ></DD
 ><DT
->7.4. <A
-HREF="#AEN1139"
->Can Samba be a Backup Domain Controller?</A
+>6.4. <A
+HREF="#AEN1295"
+>Can Samba be a Backup Domain Controller to an NT PDC?</A
 ></DT
 ><DT
->7.5. <A
-HREF="#AEN1143"
+>6.5. <A
+HREF="#AEN1300"
 >How do I set up a Samba BDC?</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.5.1. <A
-HREF="#AEN1160"
+>6.5.1. <A
+HREF="#AEN1317"
 >How do I replicate the smbpasswd file?</A
 ></DT
+><DT
+>6.5.2. <A
+HREF="#AEN1321"
+>Can I do this all with LDAP?</A
+></DT
 ></DL
 ></DD
 ></DL
 ></DD
 ><DT
->8. <A
+>7. <A
 HREF="#ADS"
 >Samba as a ADS domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->8.1. <A
-HREF="#AEN1178"
+>7.1. <A
+HREF="#AEN1339"
 >Installing the required packages for Debian</A
 ></DT
 ><DT
->8.2. <A
-HREF="#AEN1184"
+>7.2. <A
+HREF="#AEN1346"
 >Installing the required packages for RedHat</A
 ></DT
 ><DT
->8.3. <A
-HREF="#AEN1193"
+>7.3. <A
+HREF="#AEN1356"
 >Compile Samba</A
 ></DT
 ><DT
->8.4. <A
-HREF="#AEN1205"
+>7.4. <A
+HREF="#AEN1371"
 >Setup your /etc/krb5.conf</A
 ></DT
 ><DT
->8.5. <A
-HREF="#AEN1215"
+>7.5. <A
+HREF="#AEN1381"
 >Create the computer account</A
 ></DT
 ><DD
 ><DL
 ><DT
->8.5.1. <A
-HREF="#AEN1219"
+>7.5.1. <A
+HREF="#AEN1385"
 >Possible errors</A
 ></DT
 ></DL
 ></DD
 ><DT
->8.6. <A
-HREF="#AEN1231"
+>7.6. <A
+HREF="#AEN1393"
 >Test your server setup</A
 ></DT
 ><DT
->8.7. <A
-HREF="#AEN1236"
+>7.7. <A
+HREF="#AEN1398"
 >Testing with smbclient</A
 ></DT
 ><DT
->8.8. <A
-HREF="#AEN1239"
+>7.8. <A
+HREF="#AEN1401"
 >Notes</A
 ></DT
 ></DL
 ></DD
 ><DT
->9. <A
+>8. <A
 HREF="#DOMAIN-SECURITY"
->Samba as a NT4 domain member</A
+>Samba as a NT4 or Win2k domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->9.1. <A
-HREF="#AEN1261"
->Joining an NT Domain with Samba 2.2</A
+>8.1. <A
+HREF="#AEN1423"
+>Joining an NT Domain with Samba 3.0</A
 ></DT
 ><DT
->9.2. <A
-HREF="#AEN1325"
+>8.2. <A
+HREF="#AEN1478"
 >Samba and Windows 2000 Domains</A
 ></DT
 ><DT
->9.3. <A
-HREF="#AEN1330"
+>8.3. <A
+HREF="#AEN1481"
 >Why is this better than security = server?</A
 ></DT
 ></DL
@@ -3849,17 +4203,117 @@ HREF="#AEN1330"
 CLASS="CHAPTER"
 ><HR><H1
 ><A
+NAME="SECURITYLEVELS"
+></A
+>Chapter 4. User and Share security level (for servers not in a domain)</H1
+><P
+>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. </P
+><P
+>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:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>the username/password</P
+></LI
+><LI
+><P
+>the machine that the client is coming from</P
+></LI
+></OL
+><P
+>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". </P
+><P
+>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)</P
+><P
+>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".</P
+><P
+>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.</P
+><P
+>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". </P
+><P
+>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.</P
+><P
+>"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.</P
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
 NAME="SAMBA-PDC"
 ></A
->Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller</H1
+>Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN566"
+NAME="AEN722"
 ></A
->6.1. Prerequisite Reading</H2
+>5.1. Prerequisite Reading</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN572"
+NAME="AEN728"
 ></A
->6.2. Background</H2
+>5.2. Background</H2
 ><DIV
 CLASS="NOTE"
 ><P
@@ -3902,7 +4356,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -4037,9 +4491,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN611"
+NAME="AEN767"
 ></A
->6.3. Configuring the Samba Domain Controller</H2
+>5.3. Configuring the Samba Domain Controller</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN654"
+NAME="AEN810"
 ></A
->6.4. Creating Machine Trust Accounts and Joining Clients to the
+>5.4. Creating Machine Trust Accounts and Joining Clients to the
 Domain</H2
 ><P
 >A machine trust account is a Samba account that is used to
@@ -4323,9 +4777,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN673"
+NAME="AEN829"
 ></A
->6.4.1. Manual Creation of Machine Trust Accounts</H3
+>5.4.1. Manual Creation of Machine Trust Accounts</H3
 ><P
 >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"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -4513,9 +4967,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN714"
+NAME="AEN870"
 ></A
->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H3
+>5.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H3
 ><P
 >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.</P
 ><PRE
 CLASS="PROGRAMLISTING"
 >[global]
-   # &#60;...remainder of parameters...&#62;
+   # &lt;...remainder of parameters...&gt;
    add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE
 ></P
 ></DIV
@@ -4550,9 +5004,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN723"
+NAME="AEN879"
 ></A
->6.4.3. Joining the Client to the Domain</H3
+>5.4.3. Joining the Client to the Domain</H3
 ><P
 >The procedure for joining a client to the domain varies with the
 version of Windows.</P
@@ -4618,9 +5072,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN738"
+NAME="AEN894"
 ></A
->6.5. Common Problems and Errors</H2
+>5.5. Common Problems and Errors</H2
 ><P
 ></P
 ><P
@@ -4828,9 +5282,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN786"
+NAME="AEN942"
 ></A
->6.6. System Policies and Profiles</H2
+>5.6. System Policies and Profiles</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN830"
+NAME="AEN986"
 ></A
->6.7. What other help can I get?</H2
+>5.7. What other help can I get?</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN944"
+NAME="AEN1100"
 ></A
->6.8. Domain Control for Windows 9x/ME</H2
+>5.8. Domain Control for Windows 9x/ME</H2
 ><DIV
 CLASS="NOTE"
 ><P
@@ -5442,7 +5896,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -5504,7 +5958,7 @@ TYPE="1"
 ><LI
 ><P
 >	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&#60;1c&#62; at the
+	a NetLogon request. This is sent to the NetBIOS name DOMAIN&lt;1c&gt; 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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN970"
+NAME="AEN1126"
 ></A
->6.8.1. Configuration Instructions:	Network Logons</H3
+>5.8.1. Configuration Instructions:	Network Logons</H3
 ><P
 >The main difference between a PDC and a Windows 9x logon 
 server configuration is that</P
@@ -5594,7 +6048,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -5665,9 +6119,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN989"
+NAME="AEN1145"
 ></A
->6.8.2. Configuration Instructions:	Setting up Roaming User Profiles</H3
+>5.8.2. Configuration Instructions:	Setting up Roaming User Profiles</H3
 ><DIV
 CLASS="WARNING"
 ><P
@@ -5682,7 +6136,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TD
@@ -5718,9 +6172,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN997"
+NAME="AEN1153"
 ></A
->6.8.2.1. Windows NT Configuration</H4
+>5.8.2.1. Windows NT Configuration</H4
 ><P
 >To support WinNT clients, in the [global] section of smb.conf set the
 following (for example):</P
@@ -5749,7 +6203,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -5769,9 +6223,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1005"
+NAME="AEN1161"
 ></A
->6.8.2.2. Windows 9X Configuration</H4
+>5.8.2.2. Windows 9X Configuration</H4
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1013"
+NAME="AEN1169"
 ></A
->6.8.2.3. Win9X and WinNT Configuration</H4
+>5.8.2.3. Win9X and WinNT Configuration</H4
 ><P
 >You can support profiles for both Win9X and WinNT clients by setting both the
 "logon home" and "logon path" parameters. For example:</P
@@ -5826,7 +6280,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -5845,9 +6299,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1020"
+NAME="AEN1176"
 ></A
->6.8.2.4. Windows 9X Profile Setup</H4
+>5.8.2.4. Windows 9X Profile Setup</H4
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1056"
+NAME="AEN1212"
 ></A
->6.8.2.5. Windows NT Workstation 4.0</H4
+>5.8.2.5. Windows NT Workstation 4.0</H4
 ><P
 >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"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -6084,7 +6538,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -6119,9 +6573,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1069"
+NAME="AEN1225"
 ></A
->6.8.2.6. Windows NT Server</H4
+>5.8.2.6. Windows NT Server</H4
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1072"
+NAME="AEN1228"
 ></A
->6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4
+>5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H4
 ><DIV
 CLASS="WARNING"
 ><P
@@ -6150,7 +6604,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -6202,7 +6656,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TD
@@ -6226,9 +6680,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1082"
+NAME="AEN1238"
 ></A
->6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</H2
+>5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control &amp; Samba</H2
 ><DIV
 CLASS="WARNING"
 ><P
@@ -6243,7 +6697,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -6365,15 +6819,15 @@ CLASS="CHAPTER"
 ><A
 NAME="SAMBA-BDC"
 ></A
->Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
+>Chapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1118"
+NAME="AEN1274"
 ></A
->7.1. Prerequisite Reading</H2
+>6.1. Prerequisite Reading</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1122"
+NAME="AEN1278"
 ></A
->7.2. Background</H2
+>6.2. Background</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1130"
+NAME="AEN1286"
 ></A
->7.3. What qualifies a Domain Controller on the network?</H2
+>6.3. What qualifies a Domain Controller on the network?</H2
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1133"
+NAME="AEN1289"
 ></A
->7.3.1. How does a Workstation find its domain controller?</H3
+>6.3.1. How does a Workstation find its domain controller?</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1136"
+NAME="AEN1292"
 ></A
->7.3.2. When is the PDC needed?</H3
+>6.3.2. When is the PDC needed?</H3
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1139"
+NAME="AEN1295"
 ></A
->7.4. Can Samba be a Backup Domain Controller?</H2
+>6.4. Can Samba be a Backup Domain Controller to an NT PDC?</H2
 ><P
 >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.</P
 ><P
+>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.</P
+><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1143"
+NAME="AEN1300"
 ></A
->7.5. How do I set up a Samba BDC?</H2
+>6.5. How do I set up a Samba BDC?</H2
 ><P
 >Several things have to be done:</P
 ><P
@@ -6571,9 +7029,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1160"
+NAME="AEN1317"
 ></A
->7.5.1. How do I replicate the smbpasswd file?</H3
+>6.5.1. How do I replicate the smbpasswd file?</H3
 ><P
 >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.</P
 ></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1321"
+></A
+>6.5.2. Can I do this all with LDAP?</H3
+><P
+>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).</P
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -6595,15 +7068,14 @@ CLASS="CHAPTER"
 ><A
 NAME="ADS"
 ></A
->Chapter 8. Samba as a ADS domain member</H1
+>Chapter 7. Samba as a ADS domain member</H1
+><P
+>This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
+Windows2000 KDC. </P
+><P
+>Pieces you need before you begin:</P
 ><P
->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.</P
 ><P
->Pieces you need before you begin:
-<P
 ></P
 ><TABLE
 BORDER="0"
@@ -6634,12 +7106,13 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1178"
+NAME="AEN1339"
 ></A
->8.1. Installing the required packages for Debian</H2
+>7.1. Installing the required packages for Debian</H2
+><P
+>On Debian you need to install the following packages:</P
+><P
 ><P
->On Debian you need to install the following packages:
-<P
 ></P
 ><TABLE
 BORDER="0"
@@ -6663,12 +7136,13 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1184"
+NAME="AEN1346"
 ></A
->8.2. Installing the required packages for RedHat</H2
+>7.2. Installing the required packages for RedHat</H2
+><P
+>On RedHat this means you should have at least: </P
+><P
 ><P
->On RedHat this means you should have at least: 
-<P
 ></P
 ><TABLE
 BORDER="0"
@@ -6701,14 +7175,15 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1193"
+NAME="AEN1356"
 ></A
->8.3. Compile Samba</H2
+>7.3. Compile Samba</H2
 ><P
 >If your kerberos libraries are in a non-standard location then
   remember to add the configure option --with-krb5=DIR.</P
 ><P
->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:</P
 ><P
 ><PRE
@@ -6727,17 +7202,27 @@ CLASS="PROGRAMLISTING"
 ><PRE
 CLASS="PROGRAMLISTING"
 >  realm = YOUR.KERBEROS.REALM
-  ads server = your.kerberos.server
   security = ADS
   encrypt passwords = yes</PRE
 ></P
 ><P
->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.</P
+>In case samba can't figure out your ads server using your realm name, use the 
+<B
+CLASS="COMMAND"
+>ads server</B
+> option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>:
+<PRE
+CLASS="PROGRAMLISTING"
+>  ads server = your.kerberos.server</PRE
+></P
 ><P
->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.</P
 ></DIV
@@ -6746,15 +7231,15 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1205"
+NAME="AEN1371"
 ></A
->8.4. Setup your /etc/krb5.conf</H2
+>7.4. Setup your /etc/krb5.conf</H2
 ><P
 >The minimal configuration for krb5.conf is:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->	[realms]
+>[realms]
     YOUR.KERBEROS.REALM = {
 	kdc = your.kerberos.server
     }</PRE
@@ -6778,20 +7263,18 @@ to join the realm.</P
 ><P
 >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.</P
+support for smbd and winbindd.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1215"
+NAME="AEN1381"
 ></A
->8.5. Create the computer account</H2
+>7.5. Create the computer account</H2
 ><P
->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:
 <B
 CLASS="COMMAND"
@@ -6802,9 +7285,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1219"
+NAME="AEN1385"
 ></A
->8.5.1. Possible errors</H3
+>7.5.1. Possible errors</H3
 ><P
 ><P
 ></P
@@ -6812,12 +7295,6 @@ NAME="AEN1219"
 CLASS="VARIABLELIST"
 ><DL
 ><DT
->"bash: kinit: command not found"</DT
-><DD
-><P
->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)</P
-></DD
-><DT
 >"ADS support not compiled in"</DT
 ><DD
 ><P
@@ -6833,9 +7310,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1231"
+NAME="AEN1393"
 ></A
->8.6. Test your server setup</H2
+>7.6. Test your server setup</H2
 ><P
 >On a Windows 2000 client try <B
 CLASS="COMMAND"
@@ -6853,9 +7330,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1236"
+NAME="AEN1398"
 ></A
->8.7. Testing with smbclient</H2
+>7.7. Testing with smbclient</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1239"
+NAME="AEN1401"
 ></A
->8.8. Notes</H2
+>7.8. Notes</H2
 ><P
 >You must change administrator password at least once after DC install,
  to create the right encoding types</P
@@ -6883,21 +7360,21 @@ CLASS="CHAPTER"
 ><A
 NAME="DOMAIN-SECURITY"
 ></A
->Chapter 9. Samba as a NT4 domain member</H1
+>Chapter 8. Samba as a NT4 or Win2k domain member</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1261"
+NAME="AEN1423"
 ></A
->9.1. Joining an NT Domain with Samba 2.2</H2
+>8.1. Joining an NT Domain with Samba 3.0</H2
 ><P
->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 
 	<TT
 CLASS="CONSTANT"
 >SERV1</TT
-> and are joining an NT domain called
+> and are joining an or Win2k NT domain called
 	<TT
 CLASS="CONSTANT"
 >DOM</TT
@@ -6915,107 +7392,7 @@ CLASS="CONSTANT"
 	</TT
 >.</P
 ><P
->In order to join the domain, first stop all Samba daemons 
-	and run the command:</P
-><P
-><TT
-CLASS="PROMPT"
->root# </TT
-><TT
-CLASS="USERINPUT"
-><B
->smbpasswd -j DOM -r DOMPDC
-	-U<TT
-CLASS="REPLACEABLE"
-><I
->Administrator%password</I
-></TT
-></B
-></TT
-></P
-><P
->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 <TT
-CLASS="REPLACEABLE"
-><I
->Administrator%password</I
-></TT
-> 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:</P
-><P
-><TT
-CLASS="COMPUTEROUTPUT"
->smbpasswd: Joined domain DOM.</TT
->
-	</P
-><P
->in your terminal window. See the <A
-HREF="smbpasswd.8.html"
-TARGET="_top"
->	smbpasswd(8)</A
-> man page for more details.</P
-><P
->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.</P
-><P
->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 :</P
-><P
-><TT
-CLASS="FILENAME"
->/usr/local/samba/private</TT
-></P
-><P
->In Samba 2.0.x, the filename looks like this:</P
-><P
-><TT
-CLASS="FILENAME"
-><TT
-CLASS="REPLACEABLE"
-><I
->&lt;NT DOMAIN NAME&gt;</I
-></TT
->.<TT
-CLASS="REPLACEABLE"
-><I
->&lt;Samba 
-	Server Name&gt;</I
-></TT
->.mac</TT
-></P
-><P
->The <TT
-CLASS="FILENAME"
->.mac</TT
-> suffix stands for machine account 
-	password file. So in our example above, the file would be called:</P
-><P
-><TT
-CLASS="FILENAME"
->DOM.SERV1.mac</TT
-></P
-><P
->In Samba 2.2, this file has been replaced with a TDB 
-	(Trivial Database) file named <TT
-CLASS="FILENAME"
->secrets.tdb</TT
->.
-	</P
-><P
->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.</P
-><P
->Now, before restarting the Samba daemons you must 
-	edit your <A
+>Firstly, you must edit your <A
 HREF="smb.conf.5.html"
 TARGET="_top"
 ><TT
@@ -7040,7 +7417,12 @@ CLASS="PARAMETER"
 ><B
 CLASS="COMMAND"
 >security = domain</B
-></P
+> or
+	<B
+CLASS="COMMAND"
+>security = ads</B
+> depending on if the PDC is
+	NT4 or running Active Directory respectivly.</P
 ><P
 >Next change the <A
 HREF="smb.conf.5.html#WORKGROUP"
@@ -7107,11 +7489,77 @@ CLASS="COMMAND"
 >password server = *</B
 ></P
 ><P
->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.</P
 ><P
+>In order to actually join the domain, you must run this
+        command:</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>net join -S DOMPDC
+	-U<TT
+CLASS="REPLACEABLE"
+><I
+>Administrator%password</I
+></TT
+></B
+></TT
+></P
+><P
+>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 <TT
+CLASS="REPLACEABLE"
+><I
+>Administrator%password</I
+></TT
+> 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:</P
+><P
+><TT
+CLASS="COMPUTEROUTPUT"
+>Joined domain DOM.</TT
+>
+	or <TT
+CLASS="COMPUTEROUTPUT"
+>Joined 'SERV1' to realm 'MYREALM'</TT
+>
+	</P
+><P
+>in your terminal window. See the <A
+HREF="net.8.html"
+TARGET="_top"
+>	net(8)</A
+> man page for more details.</P
+><P
+>This process joins the server to thedomain
+	without having to create the machine trust account on the PDC
+	beforehand.</P
+><P
+>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 :</P
+><P
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/private/secrets.tdb</TT
+></P
+><P
+>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.</P
+><P
 >Finally, restart your Samba daemons and get ready for 
 	clients to begin using domain security!</P
 ></DIV
@@ -7120,34 +7568,23 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1325"
+NAME="AEN1478"
 ></A
->9.2. Samba and Windows 2000 Domains</H2
+>8.2. Samba and Windows 2000 Domains</H2
 ><P
 >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.</P
-><P
->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.</P
-><P
->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.</P
+2000 domain operating in mixed or native mode.  The steps above apply
+to both NT4 and Windows 2000.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1330"
+NAME="AEN1481"
 ></A
->9.3. Why is this better than security = server?</H2
+>8.3. Why is this better than security = server?</H2
 ><P
 >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.</P
+	as the user SID, the list of NT groups the user belongs to, etc. </P
 ><P
 ><SPAN
 CLASS="emphasis"
@@ -7235,7 +7666,7 @@ TARGET="_top"
 ><DIV
 CLASS="PART"
 ><A
-NAME="AEN1346"
+NAME="OPTIONAL"
 ></A
 ><DIV
 CLASS="TITLEPAGE"
@@ -7245,7 +7676,7 @@ CLASS="TITLE"
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN1348"
+NAME="AEN1499"
 ></A
 ><H1
 >Introduction</H1
@@ -7261,51 +7692,51 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->10. <A
+>9. <A
 HREF="#INTEGRATE-MS-NETWORKS"
 >Integrating MS Windows networks with Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.1. <A
-HREF="#AEN1362"
+>9.1. <A
+HREF="#AEN1513"
 >Agenda</A
 ></DT
 ><DT
->10.2. <A
-HREF="#AEN1384"
+>9.2. <A
+HREF="#AEN1535"
 >Name Resolution in a pure Unix/Linux world</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.2.1. <A
-HREF="#AEN1400"
+>9.2.1. <A
+HREF="#AEN1551"
 ><TT
 CLASS="FILENAME"
 >/etc/hosts</TT
 ></A
 ></DT
 ><DT
->10.2.2. <A
-HREF="#AEN1416"
+>9.2.2. <A
+HREF="#AEN1567"
 ><TT
 CLASS="FILENAME"
 >/etc/resolv.conf</TT
 ></A
 ></DT
 ><DT
->10.2.3. <A
-HREF="#AEN1427"
+>9.2.3. <A
+HREF="#AEN1578"
 ><TT
 CLASS="FILENAME"
 >/etc/host.conf</TT
 ></A
 ></DT
 ><DT
->10.2.4. <A
-HREF="#AEN1435"
+>9.2.4. <A
+HREF="#AEN1586"
 ><TT
 CLASS="FILENAME"
 >/etc/nsswitch.conf</TT
@@ -7314,140 +7745,140 @@ CLASS="FILENAME"
 ></DL
 ></DD
 ><DT
->10.3. <A
-HREF="#AEN1447"
+>9.3. <A
+HREF="#AEN1598"
 >Name resolution as used within MS Windows networking</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.3.1. <A
-HREF="#AEN1459"
+>9.3.1. <A
+HREF="#AEN1610"
 >The NetBIOS Name Cache</A
 ></DT
 ><DT
->10.3.2. <A
-HREF="#AEN1464"
+>9.3.2. <A
+HREF="#AEN1615"
 >The LMHOSTS file</A
 ></DT
 ><DT
->10.3.3. <A
-HREF="#AEN1472"
+>9.3.3. <A
+HREF="#AEN1623"
 >HOSTS file</A
 ></DT
 ><DT
->10.3.4. <A
-HREF="#AEN1477"
+>9.3.4. <A
+HREF="#AEN1628"
 >DNS Lookup</A
 ></DT
 ><DT
->10.3.5. <A
-HREF="#AEN1480"
+>9.3.5. <A
+HREF="#AEN1631"
 >WINS Lookup</A
 ></DT
 ></DL
 ></DD
 ><DT
->10.4. <A
-HREF="#AEN1492"
+>9.4. <A
+HREF="#AEN1643"
 >How browsing functions and how to deploy stable and 
 dependable browsing using Samba</A
 ></DT
 ><DT
->10.5. <A
-HREF="#AEN1502"
+>9.5. <A
+HREF="#AEN1653"
 >MS Windows security options and how to configure 
 Samba for seemless integration</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.5.1. <A
-HREF="#AEN1530"
+>9.5.1. <A
+HREF="#AEN1681"
 >Use MS Windows NT as an authentication server</A
 ></DT
 ><DT
->10.5.2. <A
-HREF="#AEN1538"
+>9.5.2. <A
+HREF="#AEN1689"
 >Make Samba a member of an MS Windows NT security domain</A
 ></DT
 ><DT
->10.5.3. <A
-HREF="#AEN1555"
+>9.5.3. <A
+HREF="#AEN1706"
 >Configure Samba as an authentication server</A
 ></DT
 ></DL
 ></DD
 ><DT
->10.6. <A
-HREF="#AEN1572"
+>9.6. <A
+HREF="#AEN1723"
 >Conclusions</A
 ></DT
 ></DL
 ></DD
 ><DT
->11. <A
+>10. <A
 HREF="#UNIX-PERMISSIONS"
 >UNIX Permission Bits and Windows NT Access Control Lists</A
 ></DT
 ><DD
 ><DL
 ><DT
->11.1. <A
-HREF="#AEN1593"
+>10.1. <A
+HREF="#AEN1744"
 >Viewing and changing UNIX permissions using the NT 
 	security dialogs</A
 ></DT
 ><DT
->11.2. <A
-HREF="#AEN1602"
+>10.2. <A
+HREF="#AEN1748"
 >How to view file security on a Samba share</A
 ></DT
 ><DT
->11.3. <A
-HREF="#AEN1613"
+>10.3. <A
+HREF="#AEN1759"
 >Viewing file ownership</A
 ></DT
 ><DT
->11.4. <A
-HREF="#AEN1633"
+>10.4. <A
+HREF="#AEN1779"
 >Viewing file or directory permissions</A
 ></DT
 ><DD
 ><DL
 ><DT
->11.4.1. <A
-HREF="#AEN1648"
+>10.4.1. <A
+HREF="#AEN1794"
 >File Permissions</A
 ></DT
 ><DT
->11.4.2. <A
-HREF="#AEN1662"
+>10.4.2. <A
+HREF="#AEN1808"
 >Directory Permissions</A
 ></DT
 ></DL
 ></DD
 ><DT
->11.5. <A
-HREF="#AEN1669"
+>10.5. <A
+HREF="#AEN1815"
 >Modifying file or directory permissions</A
 ></DT
 ><DT
->11.6. <A
-HREF="#AEN1691"
+>10.6. <A
+HREF="#AEN1837"
 >Interaction with the standard Samba create mask 
 	parameters</A
 ></DT
 ><DT
->11.7. <A
-HREF="#AEN1755"
+>10.7. <A
+HREF="#AEN1901"
 >Interaction with the standard Samba file attribute 
 	mapping</A
 ></DT
 ></DL
 ></DD
 ><DT
->12. <A
+>11. <A
 HREF="#PAM"
 >Configuring PAM for distributed but centrally 
 managed authentication</A
@@ -7455,39 +7886,39 @@ managed authentication</A
 ><DD
 ><DL
 ><DT
->12.1. <A
-HREF="#AEN1776"
+>11.1. <A
+HREF="#AEN1922"
 >Samba and PAM</A
 ></DT
 ><DT
->12.2. <A
-HREF="#AEN1820"
+>11.2. <A
+HREF="#AEN1966"
 >Distributed Authentication</A
 ></DT
 ><DT
->12.3. <A
-HREF="#AEN1827"
+>11.3. <A
+HREF="#AEN1973"
 >PAM Configuration in smb.conf</A
 ></DT
 ></DL
 ></DD
 ><DT
->13. <A
+>12. <A
 HREF="#MSDFS"
 >Hosting a Microsoft Distributed File System tree on Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->13.1. <A
-HREF="#AEN1847"
+>12.1. <A
+HREF="#AEN1993"
 >Instructions</A
 ></DT
 ><DD
 ><DL
 ><DT
->13.1.1. <A
-HREF="#AEN1882"
+>12.1.1. <A
+HREF="#AEN2028"
 >Notes</A
 ></DT
 ></DL
@@ -7495,130 +7926,130 @@ HREF="#AEN1882"
 ></DL
 ></DD
 ><DT
->14. <A
+>13. <A
 HREF="#PRINTING"
 >Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.1. <A
-HREF="#AEN1908"
+>13.1. <A
+HREF="#AEN2054"
 >Introduction</A
 ></DT
 ><DT
->14.2. <A
-HREF="#AEN1930"
+>13.2. <A
+HREF="#AEN2076"
 >Configuration</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.2.1. <A
-HREF="#AEN1938"
+>13.2.1. <A
+HREF="#AEN2084"
 >Creating [print$]</A
 ></DT
 ><DT
->14.2.2. <A
-HREF="#AEN1973"
+>13.2.2. <A
+HREF="#AEN2119"
 >Setting Drivers for Existing Printers</A
 ></DT
 ><DT
->14.2.3. <A
-HREF="#AEN1989"
+>13.2.3. <A
+HREF="#AEN2135"
 >Support a large number of printers</A
 ></DT
 ><DT
->14.2.4. <A
-HREF="#AEN2000"
+>13.2.4. <A
+HREF="#AEN2146"
 >Adding New Printers via the Windows NT APW</A
 ></DT
 ><DT
->14.2.5. <A
-HREF="#AEN2030"
+>13.2.5. <A
+HREF="#AEN2176"
 >Samba and Printer Ports</A
 ></DT
 ></DL
 ></DD
 ><DT
->14.3. <A
-HREF="#AEN2038"
+>13.3. <A
+HREF="#AEN2184"
 >The Imprints Toolset</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.3.1. <A
-HREF="#AEN2042"
+>13.3.1. <A
+HREF="#AEN2188"
 >What is Imprints?</A
 ></DT
 ><DT
->14.3.2. <A
-HREF="#AEN2052"
+>13.3.2. <A
+HREF="#AEN2198"
 >Creating Printer Driver Packages</A
 ></DT
 ><DT
->14.3.3. <A
-HREF="#AEN2055"
+>13.3.3. <A
+HREF="#AEN2201"
 >The Imprints server</A
 ></DT
 ><DT
->14.3.4. <A
-HREF="#AEN2059"
+>13.3.4. <A
+HREF="#AEN2205"
 >The Installation Client</A
 ></DT
 ></DL
 ></DD
 ><DT
->14.4. <A
-HREF="#AEN2081"
+>13.4. <A
+HREF="#AEN2227"
 >Diagnosis</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.4.1. <A
-HREF="#AEN2083"
+>13.4.1. <A
+HREF="#AEN2229"
 >Introduction</A
 ></DT
 ><DT
->14.4.2. <A
-HREF="#AEN2099"
+>13.4.2. <A
+HREF="#AEN2245"
 >Debugging printer problems</A
 ></DT
 ><DT
->14.4.3. <A
-HREF="#AEN2108"
+>13.4.3. <A
+HREF="#AEN2254"
 >What printers do I have?</A
 ></DT
 ><DT
->14.4.4. <A
-HREF="#AEN2116"
+>13.4.4. <A
+HREF="#AEN2262"
 >Setting up printcap and print servers</A
 ></DT
 ><DT
->14.4.5. <A
-HREF="#AEN2144"
+>13.4.5. <A
+HREF="#AEN2290"
 >Job sent, no output</A
 ></DT
 ><DT
->14.4.6. <A
-HREF="#AEN2155"
+>13.4.6. <A
+HREF="#AEN2301"
 >Job sent, strange output</A
 ></DT
 ><DT
->14.4.7. <A
-HREF="#AEN2167"
+>13.4.7. <A
+HREF="#AEN2313"
 >Raw PostScript printed</A
 ></DT
 ><DT
->14.4.8. <A
-HREF="#AEN2170"
+>13.4.8. <A
+HREF="#AEN2316"
 >Advanced Printing</A
 ></DT
 ><DT
->14.4.9. <A
-HREF="#AEN2173"
+>13.4.9. <A
+HREF="#AEN2319"
 >Real debugging</A
 ></DT
 ></DL
@@ -7626,273 +8057,268 @@ HREF="#AEN2173"
 ></DL
 ></DD
 ><DT
->15. <A
-HREF="#SECURITYLEVELS"
->Security levels</A
-></DT
-><DD
-><DL
-><DT
->15.1. <A
-HREF="#AEN2186"
->Introduction</A
-></DT
-><DT
->15.2. <A
-HREF="#AEN2197"
->More complete description of security levels</A
-></DT
-></DL
-></DD
-><DT
->16. <A
+>14. <A
 HREF="#WINBIND"
 >Unified Logons between Windows NT and UNIX using Winbind</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.1. <A
-HREF="#AEN2249"
+>14.1. <A
+HREF="#AEN2360"
 >Abstract</A
 ></DT
 ><DT
->16.2. <A
-HREF="#AEN2253"
+>14.2. <A
+HREF="#AEN2364"
 >Introduction</A
 ></DT
 ><DT
->16.3. <A
-HREF="#AEN2266"
+>14.3. <A
+HREF="#AEN2377"
 >What Winbind Provides</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.3.1. <A
-HREF="#AEN2273"
+>14.3.1. <A
+HREF="#AEN2384"
 >Target Uses</A
 ></DT
 ></DL
 ></DD
 ><DT
->16.4. <A
-HREF="#AEN2277"
+>14.4. <A
+HREF="#AEN2388"
 >How Winbind Works</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.4.1. <A
-HREF="#AEN2282"
+>14.4.1. <A
+HREF="#AEN2393"
 >Microsoft Remote Procedure Calls</A
 ></DT
 ><DT
->16.4.2. <A
-HREF="#AEN2286"
+>14.4.2. <A
+HREF="#AEN2397"
+>Microsoft Active Directory Services</A
+></DT
+><DT
+>14.4.3. <A
+HREF="#AEN2400"
 >Name Service Switch</A
 ></DT
 ><DT
->16.4.3. <A
-HREF="#AEN2302"
+>14.4.4. <A
+HREF="#AEN2416"
 >Pluggable Authentication Modules</A
 ></DT
 ><DT
->16.4.4. <A
-HREF="#AEN2310"
+>14.4.5. <A
+HREF="#AEN2424"
 >User and Group ID Allocation</A
 ></DT
 ><DT
->16.4.5. <A
-HREF="#AEN2314"
+>14.4.6. <A
+HREF="#AEN2428"
 >Result Caching</A
 ></DT
 ></DL
 ></DD
 ><DT
->16.5. <A
-HREF="#AEN2317"
+>14.5. <A
+HREF="#AEN2431"
 >Installation and Configuration</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.5.1. <A
-HREF="#AEN2324"
+>14.5.1. <A
+HREF="#AEN2438"
 >Introduction</A
 ></DT
 ><DT
->16.5.2. <A
-HREF="#AEN2337"
+>14.5.2. <A
+HREF="#AEN2451"
 >Requirements</A
 ></DT
 ><DT
->16.5.3. <A
-HREF="#AEN2351"
+>14.5.3. <A
+HREF="#AEN2465"
 >Testing Things Out</A
 ></DT
 ></DL
 ></DD
 ><DT
->16.6. <A
-HREF="#AEN2566"
+>14.6. <A
+HREF="#AEN2680"
 >Limitations</A
 ></DT
 ><DT
->16.7. <A
-HREF="#AEN2576"
+>14.7. <A
+HREF="#AEN2690"
 >Conclusion</A
 ></DT
 ></DL
 ></DD
 ><DT
->17. <A
-HREF="#PDB-MYSQL"
->Passdb MySQL plugin</A
+>15. <A
+HREF="#IMPROVED-BROWSING"
+>Improved browsing in samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->17.1. <A
-HREF="#AEN2590"
->Building</A
-></DT
-><DT
->17.2. <A
-HREF="#AEN2596"
->Configuring</A
+>15.1. <A
+HREF="#AEN2700"
+>Overview of browsing</A
 ></DT
 ><DT
->17.3. <A
-HREF="#AEN2611"
->Using plaintext passwords or encrypted password</A
+>15.2. <A
+HREF="#AEN2704"
+>Browsing support in samba</A
 ></DT
 ><DT
->17.4. <A
-HREF="#AEN2616"
->Getting non-column data from the table</A
+>15.3. <A
+HREF="#AEN2713"
+>Problem resolution</A
 ></DT
-></DL
-></DD
 ><DT
->18. <A
-HREF="#PDB-XML"
->Passdb XML plugin</A
+>15.4. <A
+HREF="#AEN2720"
+>Browsing across subnets</A
 ></DT
 ><DD
 ><DL
 ><DT
->18.1. <A
-HREF="#AEN2635"
->Building</A
-></DT
-><DT
->18.2. <A
-HREF="#AEN2641"
->Usage</A
+>15.4.1. <A
+HREF="#AEN2725"
+>How does cross subnet browsing work ?</A
 ></DT
 ></DL
 ></DD
 ><DT
->19. <A
-HREF="#SAMBA-LDAP-HOWTO"
->Storing Samba's User/Machine Account information in an LDAP Directory</A
+>15.5. <A
+HREF="#AEN2760"
+>Setting up a WINS server</A
 ></DT
-><DD
-><DL
 ><DT
->19.1. <A
-HREF="#AEN2664"
->Purpose</A
+>15.6. <A
+HREF="#AEN2779"
+>Setting up Browsing in a WORKGROUP</A
 ></DT
 ><DT
->19.2. <A
-HREF="#AEN2684"
->Introduction</A
+>15.7. <A
+HREF="#AEN2797"
+>Setting up Browsing in a DOMAIN</A
 ></DT
 ><DT
->19.3. <A
-HREF="#AEN2713"
->Supported LDAP Servers</A
+>15.8. <A
+HREF="#AEN2807"
+>Forcing samba to be the master</A
 ></DT
 ><DT
->19.4. <A
-HREF="#AEN2718"
->Schema and Relationship to the RFC 2307 posixAccount</A
+>15.9. <A
+HREF="#AEN2816"
+>Making samba the domain master</A
 ></DT
 ><DT
->19.5. <A
-HREF="#AEN2730"
->Configuring Samba with LDAP</A
+>15.10. <A
+HREF="#AEN2834"
+>Note about broadcast addresses</A
+></DT
+><DT
+>15.11. <A
+HREF="#AEN2837"
+>Multiple interfaces</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
+HREF="#VFS"
+>Stackable VFS modules</A
 ></DT
 ><DD
 ><DL
 ><DT
->19.5.1. <A
-HREF="#AEN2732"
->OpenLDAP configuration</A
+>16.1. <A
+HREF="#AEN2855"
+>Introduction and configuration</A
 ></DT
 ><DT
->19.5.2. <A
-HREF="#AEN2749"
->Configuring Samba</A
+>16.2. <A
+HREF="#AEN2864"
+>Included modules</A
 ></DT
-></DL
-></DD
+><DD
+><DL
 ><DT
->19.6. <A
-HREF="#AEN2777"
->Accounts and Groups management</A
+>16.2.1. <A
+HREF="#AEN2866"
+>audit</A
 ></DT
 ><DT
->19.7. <A
-HREF="#AEN2782"
->Security and sambaAccount</A
+>16.2.2. <A
+HREF="#AEN2874"
+>recycle</A
 ></DT
 ><DT
->19.8. <A
-HREF="#AEN2802"
->LDAP specials attributes for sambaAccounts</A
+>16.2.3. <A
+HREF="#AEN2911"
+>netatalk</A
 ></DT
+></DL
+></DD
 ><DT
->19.9. <A
-HREF="#AEN2872"
->Example LDIF Entries for a sambaAccount</A
+>16.3. <A
+HREF="#AEN2918"
+>VFS modules available elsewhere</A
 ></DT
+><DD
+><DL
 ><DT
->19.10. <A
-HREF="#AEN2880"
->Comments</A
+>16.3.1. <A
+HREF="#AEN2922"
+>DatabaseFS</A
+></DT
+><DT
+>16.3.2. <A
+HREF="#AEN2930"
+>vscan</A
 ></DT
 ></DL
 ></DD
+></DL
+></DD
 ><DT
->20. <A
+>17. <A
 HREF="#CVS-ACCESS"
->HOWTO Access Samba source code via CVS</A
+>Access Samba source code via CVS</A
 ></DT
 ><DD
 ><DL
 ><DT
->20.1. <A
-HREF="#AEN2891"
+>17.1. <A
+HREF="#AEN2942"
 >Introduction</A
 ></DT
 ><DT
->20.2. <A
-HREF="#AEN2896"
+>17.2. <A
+HREF="#AEN2947"
 >CVS Access to samba.org</A
 ></DT
 ><DD
 ><DL
 ><DT
->20.2.1. <A
-HREF="#AEN2899"
+>17.2.1. <A
+HREF="#AEN2950"
 >Access via CVSweb</A
 ></DT
 ><DT
->20.2.2. <A
-HREF="#AEN2904"
+>17.2.2. <A
+HREF="#AEN2955"
 >Access via cvs</A
 ></DT
 ></DL
@@ -7900,120 +8326,114 @@ HREF="#AEN2904"
 ></DL
 ></DD
 ><DT
->21. <A
+>18. <A
 HREF="#GROUPMAPPING"
 >Group mapping HOWTO</A
 ></DT
 ><DT
->22. <A
+>19. <A
 HREF="#SPEED"
 >Samba performance issues</A
 ></DT
 ><DD
 ><DL
 ><DT
->22.1. <A
-HREF="#AEN2982"
+>19.1. <A
+HREF="#AEN3033"
 >Comparisons</A
 ></DT
 ><DT
->22.2. <A
-HREF="#AEN2988"
->Oplocks</A
-></DT
-><DD
-><DL
-><DT
->22.2.1. <A
-HREF="#AEN2990"
->Overview</A
-></DT
-><DT
->22.2.2. <A
-HREF="#AEN2998"
->Level2 Oplocks</A
+>19.2. <A
+HREF="#AEN3039"
+>Socket options</A
 ></DT
 ><DT
->22.2.3. <A
-HREF="#AEN3004"
->Old 'fake oplocks' option - deprecated</A
+>19.3. <A
+HREF="#AEN3046"
+>Read size</A
 ></DT
-></DL
-></DD
 ><DT
->22.3. <A
-HREF="#AEN3008"
->Socket options</A
+>19.4. <A
+HREF="#AEN3051"
+>Max xmit</A
 ></DT
 ><DT
->22.4. <A
-HREF="#AEN3015"
->Read size</A
+>19.5. <A
+HREF="#AEN3056"
+>Log level</A
 ></DT
 ><DT
->22.5. <A
-HREF="#AEN3020"
->Max xmit</A
+>19.6. <A
+HREF="#AEN3059"
+>Read raw</A
 ></DT
 ><DT
->22.6. <A
-HREF="#AEN3025"
->Locking</A
+>19.7. <A
+HREF="#AEN3064"
+>Write raw</A
 ></DT
 ><DT
->22.7. <A
-HREF="#AEN3029"
->Share modes</A
+>19.8. <A
+HREF="#AEN3068"
+>Slow Clients</A
 ></DT
 ><DT
->22.8. <A
-HREF="#AEN3034"
->Log level</A
+>19.9. <A
+HREF="#AEN3072"
+>Slow Logins</A
 ></DT
 ><DT
->22.9. <A
-HREF="#AEN3037"
->Wide lines</A
+>19.10. <A
+HREF="#AEN3075"
+>Client tuning</A
 ></DT
+></DL
+></DD
 ><DT
->22.10. <A
-HREF="#AEN3040"
->Read raw</A
+>20. <A
+HREF="#GROUPPROFILES"
+>Creating Group Profiles</A
 ></DT
+><DD
+><DL
 ><DT
->22.11. <A
-HREF="#AEN3045"
->Write raw</A
+>20.1. <A
+HREF="#AEN3123"
+>Windows '9x</A
 ></DT
 ><DT
->22.12. <A
-HREF="#AEN3049"
->Read prediction</A
+>20.2. <A
+HREF="#AEN3132"
+>Windows NT 4</A
 ></DT
+><DD
+><DL
 ><DT
->22.13. <A
-HREF="#AEN3056"
->Memory mapping</A
+>20.2.1. <A
+HREF="#AEN3155"
+>Side bar Notes</A
 ></DT
 ><DT
->22.14. <A
-HREF="#AEN3061"
->Slow Clients</A
+>20.2.2. <A
+HREF="#AEN3159"
+>Mandatory profiles</A
 ></DT
 ><DT
->22.15. <A
-HREF="#AEN3065"
->Slow Logins</A
+>20.2.3. <A
+HREF="#AEN3162"
+>moveuser.exe</A
 ></DT
 ><DT
->22.16. <A
-HREF="#AEN3068"
->Client tuning</A
+>20.2.4. <A
+HREF="#AEN3165"
+>Get SID</A
 ></DT
+></DL
+></DD
 ><DT
->22.17. <A
-HREF="#AEN3100"
->My Results</A
+>20.3. <A
+HREF="#AEN3170"
+>Windows 2000/XP</A
 ></DT
 ></DL
 ></DD
@@ -8026,15 +8446,15 @@ CLASS="CHAPTER"
 ><A
 NAME="INTEGRATE-MS-NETWORKS"
 ></A
->Chapter 10. Integrating MS Windows networks with Samba</H1
+>Chapter 9. Integrating MS Windows networks with Samba</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1362"
+NAME="AEN1513"
 ></A
->10.1. Agenda</H2
+>9.1. Agenda</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1384"
+NAME="AEN1535"
 ></A
->10.2. Name Resolution in a pure Unix/Linux world</H2
+>9.2. Name Resolution in a pure Unix/Linux world</H2
 ><P
 >The key configuration files covered in this section are:</P
 ><P
@@ -8141,9 +8561,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1400"
+NAME="AEN1551"
 ></A
->10.2.1. <TT
+>9.2.1. <TT
 CLASS="FILENAME"
 >/etc/hosts</TT
 ></H3
@@ -8222,9 +8642,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1416"
+NAME="AEN1567"
 ></A
->10.2.2. <TT
+>9.2.2. <TT
 CLASS="FILENAME"
 >/etc/resolv.conf</TT
 ></H3
@@ -8260,9 +8680,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1427"
+NAME="AEN1578"
 ></A
->10.2.3. <TT
+>9.2.3. <TT
 CLASS="FILENAME"
 >/etc/host.conf</TT
 ></H3
@@ -8289,9 +8709,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1435"
+NAME="AEN1586"
 ></A
->10.2.4. <TT
+>9.2.4. <TT
 CLASS="FILENAME"
 >/etc/nsswitch.conf</TT
 ></H3
@@ -8358,9 +8778,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1447"
+NAME="AEN1598"
 ></A
->10.3. Name resolution as used within MS Windows networking</H2
+>9.3. Name resolution as used within MS Windows networking</H2
 ><P
 >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.</P
 ><PRE
 CLASS="PROGRAMLISTING"
 >	Unique NetBIOS Names:
-		MACHINENAME&#60;00&#62;	= Server Service is running on MACHINENAME
-		MACHINENAME&#60;03&#62; = Generic Machine Name (NetBIOS name)
-		MACHINENAME&#60;20&#62; = LanMan Server service is running on MACHINENAME
-		WORKGROUP&#60;1b&#62; = Domain Master Browser
+		MACHINENAME&lt;00&gt;	= Server Service is running on MACHINENAME
+		MACHINENAME&lt;03&gt; = Generic Machine Name (NetBIOS name)
+		MACHINENAME&lt;20&gt; = LanMan Server service is running on MACHINENAME
+		WORKGROUP&lt;1b&gt; = Domain Master Browser
 
 	Group Names:
-		WORKGROUP&#60;03&#62; = Generic Name registered by all members of WORKGROUP
-		WORKGROUP&#60;1c&#62; = Domain Controllers / Netlogon Servers
-		WORKGROUP&#60;1d&#62; = Local Master Browsers
-		WORKGROUP&#60;1e&#62; = Internet Name Resolvers</PRE
+		WORKGROUP&lt;03&gt; = Generic Name registered by all members of WORKGROUP
+		WORKGROUP&lt;1c&gt; = Domain Controllers / Netlogon Servers
+		WORKGROUP&lt;1d&gt; = Local Master Browsers
+		WORKGROUP&lt;1e&gt; = Internet Name Resolvers</PRE
 ></P
 ><P
 >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 *&#60;1c&#62;. A logon request is then sent to each 
+registered the name type *&lt;1c&gt;. 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.</P
 ><P
@@ -8443,9 +8863,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1459"
+NAME="AEN1610"
 ></A
->10.3.1. The NetBIOS Name Cache</H3
+>9.3.1. The NetBIOS Name Cache</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1464"
+NAME="AEN1615"
 ></A
->10.3.2. The LMHOSTS file</H3
+>9.3.2. The LMHOSTS file</H3
 ><P
 >This file is usually located in MS Windows NT 4.0 or 
 2000 in <TT
@@ -8573,9 +8993,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1472"
+NAME="AEN1623"
 ></A
->10.3.3. HOSTS file</H3
+>9.3.3. HOSTS file</H3
 ><P
 >This file is usually located in MS Windows NT 4.0 or 2000 in 
 <TT
@@ -8595,9 +9015,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1477"
+NAME="AEN1628"
 ></A
->10.3.4. DNS Lookup</H3
+>9.3.4. DNS Lookup</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1480"
+NAME="AEN1631"
 ></A
->10.3.5. WINS Lookup</H3
+>9.3.5. WINS Lookup</H3
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1492"
+NAME="AEN1643"
 ></A
->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</H2
 ><P
 >As stated above, MS Windows machines register their NetBIOS names 
@@ -8725,9 +9145,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1502"
+NAME="AEN1653"
 ></A
->10.5. MS Windows security options and how to configure 
+>9.5. MS Windows security options and how to configure 
 Samba for seemless integration</H2
 ><P
 >MS Windows clients may use encrypted passwords as part of a 
@@ -8862,9 +9282,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1530"
+NAME="AEN1681"
 ></A
->10.5.1. Use MS Windows NT as an authentication server</H3
+>9.5.1. Use MS Windows NT as an authentication server</H3
 ><P
 >This method involves the additions of the following parameters 
 in the smb.conf file:</P
@@ -8898,9 +9318,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1538"
+NAME="AEN1689"
 ></A
->10.5.2. Make Samba a member of an MS Windows NT security domain</H3
+>9.5.2. Make Samba a member of an MS Windows NT security domain</H3
 ><P
 >This method involves additon of the following paramters in the smb.conf file:</P
 ><P
@@ -8961,9 +9381,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1555"
+NAME="AEN1706"
 ></A
->10.5.3. Configure Samba as an authentication server</H3
+>9.5.3. Configure Samba as an authentication server</H3
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1562"
+NAME="AEN1713"
 ></A
->10.5.3.1. Users</H4
+>9.5.3.1. Users</H4
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN1567"
+NAME="AEN1718"
 ></A
->10.5.3.2. MS Windows NT Machine Accounts</H4
+>9.5.3.2. MS Windows NT Machine Accounts</H4
 ><P
 >These are required only when Samba is used as a domain 
 controller.  Refer to the Samba-PDC-HOWTO for more details.</P
@@ -9042,9 +9462,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1572"
+NAME="AEN1723"
 ></A
->10.6. Conclusions</H2
+>9.6. Conclusions</H2
 ><P
 >Samba provides a flexible means to operate as...</P
 ><P
@@ -9080,15 +9500,15 @@ CLASS="CHAPTER"
 ><A
 NAME="UNIX-PERMISSIONS"
 ></A
->Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1
+>Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1593"
+NAME="AEN1744"
 ></A
->11.1. Viewing and changing UNIX permissions using the NT 
+>10.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs</H2
 ><P
 >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.</P
-><P
->In Samba 2.0.4 and above the default value of the 
-	parameter <A
-HREF="smb.conf.5.html#NTACLSUPPORT"
-TARGET="_top"
-><TT
-CLASS="PARAMETER"
-><I
->	nt acl support</I
-></TT
-></A
-> has been changed from 
-	<TT
-CLASS="CONSTANT"
->false</TT
-> to <TT
-CLASS="CONSTANT"
->true</TT
->, so 
- 	manipulation of permissions is turned on by default.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1602"
+NAME="AEN1748"
 ></A
->11.2. How to view file security on a Samba share</H2
+>10.2. How to view file security on a Samba share</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1613"
+NAME="AEN1759"
 ></A
->11.3. Viewing file ownership</H2
+>10.3. Viewing file ownership</H2
 ><P
 >Clicking on the <B
 CLASS="COMMAND"
@@ -9289,9 +9689,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1633"
+NAME="AEN1779"
 ></A
->11.4. Viewing file or directory permissions</H2
+>10.4. Viewing file or directory permissions</H2
 ><P
 >The third button is the <B
 CLASS="COMMAND"
@@ -9351,9 +9751,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1648"
+NAME="AEN1794"
 ></A
->11.4.1. File Permissions</H3
+>10.4.1. File Permissions</H3
 ><P
 >The standard UNIX user/group/world triple and 
 		the corresponding "read", "write", "execute" permissions 
@@ -9413,9 +9813,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1662"
+NAME="AEN1808"
 ></A
->11.4.2. Directory Permissions</H3
+>10.4.2. Directory Permissions</H3
 ><P
 >Directories on an NT NTFS file system have two 
 		different sets of permissions. The first set of permissions 
@@ -9445,9 +9845,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1669"
+NAME="AEN1815"
 ></A
->11.5. Modifying file or directory permissions</H2
+>10.5. Modifying file or directory permissions</H2
 ><P
 >Modifying file and directory permissions is as simple 
 	as changing the displayed permissions in the dialog box, and 
@@ -9543,9 +9943,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1691"
+NAME="AEN1837"
 ></A
->11.6. Interaction with the standard Samba create mask 
+>10.6. Interaction with the standard Samba create mask 
 	parameters</H2
 ><P
 >Note that with Samba 2.0.5 there are four new parameters 
@@ -9820,9 +10220,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1755"
+NAME="AEN1901"
 ></A
->11.7. Interaction with the standard Samba file attribute 
+>10.7. Interaction with the standard Samba file attribute 
 	mapping</H2
 ><P
 >Samba maps some of the DOS attribute bits (such as "read 
@@ -9869,16 +10269,16 @@ CLASS="CHAPTER"
 ><A
 NAME="PAM"
 ></A
->Chapter 12. Configuring PAM for distributed but centrally 
+>Chapter 11. Configuring PAM for distributed but centrally 
 managed authentication</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1776"
+NAME="AEN1922"
 ></A
->12.1. Samba and PAM</H2
+>11.1. Samba and PAM</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1820"
+NAME="AEN1966"
 ></A
->12.2. Distributed Authentication</H2
+>11.2. Distributed Authentication</H2
 ><P
 >The astute administrator will realize from this that the 
 combination of <TT
@@ -10123,9 +10523,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1827"
+NAME="AEN1973"
 ></A
->12.3. PAM Configuration in smb.conf</H2
+>11.3. PAM Configuration in smb.conf</H2
 ><P
 >There is an option in smb.conf called <A
 HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
@@ -10165,15 +10565,15 @@ CLASS="CHAPTER"
 ><A
 NAME="MSDFS"
 ></A
->Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1
+>Chapter 12. Hosting a Microsoft Distributed File System tree on Samba</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1847"
+NAME="AEN1993"
 ></A
->13.1. Instructions</H2
+>12.1. Instructions</H2
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1882"
+NAME="AEN2028"
 ></A
->13.1.1. Notes</H3
+>12.1.1. Notes</H3
 ><P
 ></P
 ><UL
@@ -10354,15 +10754,15 @@ CLASS="CHAPTER"
 ><A
 NAME="PRINTING"
 ></A
->Chapter 14. Printing Support</H1
+>Chapter 13. Printing Support</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1908"
+NAME="AEN2054"
 ></A
->14.1. Introduction</H2
+>13.1. Introduction</H2
 ><P
 >Beginning with the 2.2.0 release, Samba supports 
 the native Windows NT printing mechanisms implemented via 
@@ -10443,9 +10843,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1930"
+NAME="AEN2076"
 ></A
->14.2. Configuration</H2
+>13.2. Configuration</H2
 ><DIV
 CLASS="WARNING"
 ><P
@@ -10460,7 +10860,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -10509,9 +10909,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1938"
+NAME="AEN2084"
 ></A
->14.2.1. Creating [print$]</H3
+>13.2.1. Creating [print$]</H3
 ><P
 >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"
 ><IMG
-SRC="/docbook-dsssl/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
 ALT="Note"></TD
 ><TH
@@ -10661,7 +11061,7 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/docbook-dsssl/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
 ALT="Warning"></TD
 ><TH
@@ -10732,9 +11132,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1973"
+NAME="AEN2119"
 ></A
->14.2.2. Setting Drivers for Existing Printers</H3
+>13.2.2. Setting Drivers for Existing Printers</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1989"
+NAME="AEN2135"
 ></A
->14.2.3. Support a large number of printers</H3
+>13.2.3. Support a large number of printers</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2000"
+NAME="AEN2146"
 ></A
->14.2.4. Adding New Printers via the Windows NT APW</H3
+>13.2.4. Adding New Printers via the Windows NT APW</H3
 ><P
 >By default, Samba offers all printer shares defined in <TT
 CLASS="FILENAME"
@@ -11013,8 +11413,8 @@ echo "  :sd=/var/spool/lpd/$2:\\" 			&#62;&#62; $PRINTCAP
 echo "  :mx=0:ml=0:sh:\\" 				&#62;&#62; $PRINTCAP
 echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	&#62;&#62; $PRINTCAP
 
-touch "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&#38;1
-chown $LP "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&#38;1
+touch "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&amp;1
+chown $LP "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&amp;1
 
 mkdir /var/spool/lpd/$2
 chmod 700 /var/spool/lpd/$2
@@ -11039,9 +11439,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2030"
+NAME="AEN2176"
 ></A
->14.2.5. Samba and Printer Ports</H3
+>13.2.5. Samba and Printer Ports</H3
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2038"
+NAME="AEN2184"
 ></A
->14.3. The Imprints Toolset</H2
+>13.3. The Imprints Toolset</H2
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2042"
+NAME="AEN2188"
 ></A
->14.3.1. What is Imprints?</H3
+>13.3.1. What is Imprints?</H3
 ><P
 >Imprints is a collection of tools for supporting the goals 
 		of</P
@@ -11126,9 +11526,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2052"
+NAME="AEN2198"
 ></A
->14.3.2. Creating Printer Driver Packages</H3
+>13.3.2. Creating Printer Driver Packages</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2055"
+NAME="AEN2201"
 ></A
->14.3.3. The Imprints server</H3
+>13.3.3. The Imprints server</H3
 ><P
 >The Imprints server is really a database server that 
 		may be queried via standard HTTP mechanisms.  Each printer 
@@ -11166,9 +11566,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2059"
+NAME="AEN2205"
 ></A
->14.3.4. The Installation Client</H3
+>13.3.4. The Installation Client</H3
 ><P
 >More information regarding the Imprints installation client 
 		is available in the <TT
@@ -11260,17 +11660,17 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2081"
+NAME="AEN2227"
 ></A
->14.4. Diagnosis</H2
+>13.4. Diagnosis</H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2083"
+NAME="AEN2229"
 ></A
->14.4.1. Introduction</H3
+>13.4.1. Introduction</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2099"
+NAME="AEN2245"
 ></A
->14.4.2. Debugging printer problems</H3
+>13.4.2. Debugging printer problems</H3
 ><P
 >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 &#62;/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&#62;&#62;&#38;/tmp/tmp.print</PRE
+    /usr/bin/lpr -r -P$1 $2 2&#62;&#62;&amp;/tmp/tmp.print</PRE
 ></P
 ><P
 >Then you print a file and try removing it.  You may find that the
@@ -11400,9 +11800,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2108"
+NAME="AEN2254"
 ></A
->14.4.3. What printers do I have?</H3
+>13.4.3. What printers do I have?</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2116"
+NAME="AEN2262"
 ></A
->14.4.4. Setting up printcap and print servers</H3
+>13.4.4. Setting up printcap and print servers</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2144"
+NAME="AEN2290"
 ></A
->14.4.5. Job sent, no output</H3
+>13.4.5. Job sent, no output</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2155"
+NAME="AEN2301"
 ></A
->14.4.6. Job sent, strange output</H3
+>13.4.6. Job sent, strange output</H3
 ><P
 >Once you have the job printing, you can then start worrying about
 making it print nicely.</P
@@ -11604,9 +12004,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2167"
+NAME="AEN2313"
 ></A
->14.4.7. Raw PostScript printed</H3
+>13.4.7. Raw PostScript printed</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2170"
+NAME="AEN2316"
 ></A
->14.4.8. Advanced Printing</H3
+>13.4.8. Advanced Printing</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2173"
+NAME="AEN2319"
 ></A
->14.4.9. Real debugging</H3
+>13.4.9. Real debugging</H3
 ><P
 >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.</P
@@ -11648,165 +12048,17 @@ the bug guns, system tracing. See Tracing.txt in this directory.</P
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="SECURITYLEVELS"
-></A
->Chapter 15. Security levels</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN2186"
-></A
->15.1. Introduction</H2
-><P
->Samba supports the following options to the global smb.conf parameter</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
-<A
-HREF="smb.conf.5.html#SECURITY"
-TARGET="_top"
-><TT
-CLASS="PARAMETER"
-><I
->security</I
-></TT
-></A
-> = [share|user(default)|server|domain|ads]</PRE
-></P
-><P
->Please refer to the smb.conf man page for usage information and to the document
-<A
-HREF="DOMAIN_MEMBER.html"
-TARGET="_top"
->DOMAIN_MEMBER.html</A
-> for further background details
-on domain mode security.  The Windows 2000 Kerberos domain security model
-(security = ads) is described in the <A
-HREF="ADS-HOWTO.html"
-TARGET="_top"
->ADS-HOWTO.html</A
->.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2197"
-></A
->15.2. More complete description of security levels</H2
-><P
->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. </P
-><P
->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:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->the username/password</P
-></LI
-><LI
-><P
->the machine that the client is coming from</P
-></LI
-></OL
-><P
->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". </P
-><P
->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)</P
-><P
->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".</P
-><P
->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.</P
-><P
->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". </P
-><P
->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.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
 NAME="WINBIND"
 ></A
->Chapter 16. Unified Logons between Windows NT and UNIX using Winbind</H1
+>Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2249"
+NAME="AEN2360"
 ></A
->16.1. Abstract</H2
+>14.1. Abstract</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2253"
+NAME="AEN2364"
 ></A
->16.2. Introduction</H2
+>14.2. Introduction</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2266"
+NAME="AEN2377"
 ></A
->16.3. What Winbind Provides</H2
+>14.3. What Winbind Provides</H2
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2273"
+NAME="AEN2384"
 ></A
->16.3.1. Target Uses</H3
+>14.3.1. Target Uses</H3
 ><P
 >Winbind is targeted at organizations that have an 
 		existing NT based domain infrastructure into which they wish 
@@ -11951,9 +12203,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2277"
+NAME="AEN2388"
 ></A
->16.4. How Winbind Works</H2
+>14.4. How Winbind Works</H2
 ><P
 >The winbind system is designed around a client/server 
 	architecture. A long running <B
@@ -11971,11 +12223,11 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2282"
+NAME="AEN2393"
 ></A
->16.4.1. Microsoft Remote Procedure Calls</H3
+>14.4.1. Microsoft Remote Procedure Calls</H3
 ><P
->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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2286"
+NAME="AEN2397"
+></A
+>14.4.2. Microsoft Active Directory Services</H3
+><P
+>                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.  
+                </P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2400"
 ></A
->16.4.2. Name Service Switch</H3
+>14.4.3. Name Service Switch</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2302"
+NAME="AEN2416"
 ></A
->16.4.3. Pluggable Authentication Modules</H3
+>14.4.4. Pluggable Authentication Modules</H3
 ><P
 >Pluggable Authentication Modules, also known as PAM, 
 		is a system for abstracting authentication and authorization 
@@ -12126,9 +12397,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2310"
+NAME="AEN2424"
 ></A
->16.4.4. User and Group ID Allocation</H3
+>14.4.5. User and Group ID Allocation</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2314"
+NAME="AEN2428"
 ></A
->16.4.5. Result Caching</H3
+>14.4.6. Result Caching</H3
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2317"
+NAME="AEN2431"
 ></A
->16.5. Installation and Configuration</H2
+>14.5. Installation and Configuration</H2
 ><P
 >Many thanks to John Trostel <A
 HREF="mailto:jtrostel@snapserver.com"
@@ -12202,9 +12473,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2324"
+NAME="AEN2438"
 ></A
->16.5.1. Introduction</H3
+>14.5.1. Introduction</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2337"
+NAME="AEN2451"
 ></A
->16.5.2. Requirements</H3
+>14.5.2. Requirements</H3
 ><P
 >If you have a samba configuration file that you are currently 
 using... <SPAN
@@ -12331,9 +12602,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2351"
+NAME="AEN2465"
 ></A
->16.5.3. Testing Things Out</H3
+>14.5.3. Testing Things Out</H3
 ><P
 >Before starting, it is probably best to kill off all the SAMBA 
 related daemons running on your server.  Kill off all <B
@@ -12376,9 +12647,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2362"
+NAME="AEN2476"
 ></A
->16.5.3.1. Configure and compile SAMBA</H4
+>14.5.3.1. Configure and compile SAMBA</H4
 ><P
 >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#</TT
 > <B
 CLASS="COMMAND"
->./configure --with-winbind</B
+>./configure</B
 >
 <TT
 CLASS="PROMPT"
@@ -12442,9 +12713,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2381"
+NAME="AEN2495"
 ></A
->16.5.3.2. Configure <TT
+>14.5.3.2. Configure <TT
 CLASS="FILENAME"
 >nsswitch.conf</TT
 > and the 
@@ -12547,9 +12818,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2414"
+NAME="AEN2528"
 ></A
->16.5.3.3. Configure smb.conf</H4
+>14.5.3.3. Configure smb.conf</H4
 ><P
 >Several parameters are needed in the smb.conf file to control 
 the behavior of <B
@@ -12574,7 +12845,7 @@ include the following entries in the [global] section:</P
 ><PRE
 CLASS="PROGRAMLISTING"
 >[global]
-     &#60;...&#62;
+     &lt;...&gt;
      # separate domain and username with '+', like DOMAIN+username
      <A
 HREF="winbindd.8.html#WINBINDSEPARATOR"
@@ -12622,9 +12893,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2430"
+NAME="AEN2544"
 ></A
->16.5.3.4. Join the SAMBA server to the PDC domain</H4
+>14.5.3.4. Join the SAMBA server to the PDC domain</H4
 ><P
 >Enter the following command to make the SAMBA server join the 
 PDC domain, where <TT
@@ -12646,7 +12917,7 @@ CLASS="PROMPT"
 >root#</TT
 > <B
 CLASS="COMMAND"
->/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B
+>/usr/local/samba/bin/net join -S PDC -U Administrator</B
 ></P
 ><P
 >The proper response to the command should be: "Joined the domain 
@@ -12668,9 +12939,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2441"
+NAME="AEN2555"
 ></A
->16.5.3.5. Start up the winbindd daemon and test it!</H4
+>14.5.3.5. Start up the winbindd daemon and test it!</H4
 ><P
 >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"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2477"
+NAME="AEN2591"
 ></A
->16.5.3.6. Fix the init.d startup scripts</H4
+>14.5.3.6. Fix the init.d startup scripts</H4
 ><DIV
 CLASS="SECT4"
 ><H5
 CLASS="SECT4"
 ><A
-NAME="AEN2479"
+NAME="AEN2593"
 ></A
->16.5.3.6.1. Linux</H5
+>14.5.3.6.1. Linux</H5
 ><P
 >The <B
 CLASS="COMMAND"
@@ -12858,7 +13129,7 @@ CLASS="PROGRAMLISTING"
         daemon /usr/local/samba/bin/winbindd
         RETVAL3=$?
         echo
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &#38;&#38; touch /var/lock/subsys/smb || \
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; touch /var/lock/subsys/smb || \
            RETVAL=1
         return $RETVAL
 }</PRE
@@ -12884,7 +13155,7 @@ CLASS="PROGRAMLISTING"
         echo -n $"Shutting down $KIND services: "
         killproc winbindd
         RETVAL3=$?
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &#38;&#38; rm -f /var/lock/subsys/smb
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; rm -f /var/lock/subsys/smb
         echo ""
         return $RETVAL
 }</PRE
@@ -12895,9 +13166,9 @@ CLASS="SECT4"
 ><HR><H5
 CLASS="SECT4"
 ><A
-NAME="AEN2496"
+NAME="AEN2610"
 ></A
->16.5.3.6.2. Solaris</H5
+>14.5.3.6.2. Solaris</H5
 ><P
 >On solaris, you need to modify the 
 <TT
@@ -12926,7 +13197,7 @@ killproc() {            # kill the named process(es)
         pid=`/usr/bin/ps -e |
              /usr/bin/grep -w $1 |
              /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
-        [ "$pid" != "" ] &#38;&#38; kill $pid
+        [ "$pid" != "" ] &amp;&amp; kill $pid
 }
  
 # Start/stop processes required for samba server
@@ -12966,9 +13237,9 @@ CLASS="SECT4"
 ><HR><H5
 CLASS="SECT4"
 ><A
-NAME="AEN2503"
+NAME="AEN2617"
 ></A
->16.5.3.6.3. Restarting</H5
+>14.5.3.6.3. Restarting</H5
 ><P
 >If you restart the <B
 CLASS="COMMAND"
@@ -12990,9 +13261,9 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN2509"
+NAME="AEN2623"
 ></A
->16.5.3.7. Configure Winbind and PAM</H4
+>14.5.3.7. Configure Winbind and PAM</H4
 ><P
 >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"
 ><HR><H5
 CLASS="SECT4"
 ><A
-NAME="AEN2526"
+NAME="AEN2640"
 ></A
->16.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5
+>14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H5
 ><P
 >The <TT
 CLASS="FILENAME"
@@ -13177,9 +13448,9 @@ CLASS="SECT4"
 ><HR><H5
 CLASS="SECT4"
 ><A
-NAME="AEN2559"
+NAME="AEN2673"
 ></A
->16.5.3.7.2. Solaris-specific configuration</H5
+>14.5.3.7.2. Solaris-specific configuration</H5
 ><P
 >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.</P
 ><P
->Now restart your Samba &#38; try connecting through your application that you
+>Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.</P
 ></DIV
 ></DIV
@@ -13264,9 +13535,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2566"
+NAME="AEN2680"
 ></A
->16.6. Limitations</H2
+>14.6. Limitations</H2
 ><P
 >Winbind has a number of limitations in its current 
 	released version that we hope to overcome in future 
@@ -13277,7 +13548,7 @@ NAME="AEN2566"
 ><LI
 ><P
 >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
@@ -13296,7 +13567,8 @@ NAME="AEN2566"
 ><P
 >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.</P
+		that may be been set for Windows NT users, this is
+		instead up to the PDC to enforce.</P
 ></LI
 ></UL
 ></DIV
@@ -13305,9 +13577,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2576"
+NAME="AEN2690"
 ></A
->16.7. Conclusion</H2
+>14.7. Conclusion</H2
 ><P
 >The winbind system, through the use of the Name Service 
 	Switch, Pluggable Authentication Modules, and appropriate 
@@ -13321,1081 +13593,991 @@ NAME="AEN2576"
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="PDB-MYSQL"
+NAME="IMPROVED-BROWSING"
 ></A
->Chapter 17. Passdb MySQL plugin</H1
+>Chapter 15. Improved browsing in samba</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2590"
+NAME="AEN2700"
 ></A
->17.1. Building</H2
+>15.1. Overview of browsing</H2
 ><P
->To build the plugin, run <B
-CLASS="COMMAND"
->make bin/pdb_mysql.so</B
->
-in the <TT
-CLASS="FILENAME"
->source/</TT
-> directory of samba distribution. </P
+>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.</P
 ><P
->Next, copy pdb_mysql.so to any location you want. I 
-strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P
+>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.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2596"
+NAME="AEN2704"
 ></A
->17.2. Configuring</H2
-><P
->This plugin lacks some good documentation, but here is some short info:</P
+>15.2. Browsing support in samba</H2
 ><P
->Add a the following to the <B
-CLASS="COMMAND"
->passdb backend</B
-> variable in your <TT
-CLASS="FILENAME"
->smb.conf</TT
->:
-<PRE
-CLASS="PROGRAMLISTING"
->passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE
-></P
+>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)).</P
 ><P
->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!</P
+>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.</P
 ><P
->Additional options can be given thru the smb.conf file in the [global] section.</P
+>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.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->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</PRE
-></P
+>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.</P
 ><P
->Names of the columns in this table(I've added column types those columns should have first):</P
+>[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].</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->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</PRE
-></P
+>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.</P
 ><P
->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. </P
+>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.  </P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2611"
+NAME="AEN2713"
 ></A
->17.3. Using plaintext passwords or encrypted password</H2
+>15.3. Problem resolution</H2
 ><P
->I strongly discourage the use of plaintext passwords, however, you can use them:</P
+>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.</P
+><P
+>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.</P
 ><P
->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. </P
+>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.</P
 ><P
->If you use encrypted passwords, set the 'identifier:plaintext pass column' to 'NULL' (without the quotes). This is the default.</P
+>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.</P
+><P
+>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)</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2616"
+NAME="AEN2720"
 ></A
->17.4. Getting non-column data from the table</H2
+>15.4. Browsing across subnets</H2
 ><P
->It is possible to have not all data in the database and making some 'constant'.</P
-><P
->For example, you can set 'identifier:fullname column' to : 
-<B
-CLASS="COMMAND"
->CONCAT(First_name,' ',Sur_name)</B
-></P
+>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.</P
 ><P
->Or, set 'identifier:workstations column' to :
-<B
-CLASS="COMMAND"
->NULL</B
-></P
+>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.</P
 ><P
->See the MySQL documentation for more language constructs.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="PDB-XML"
-></A
->Chapter 18. Passdb XML plugin</H1
+>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.</P
 ><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN2635"
+NAME="AEN2725"
 ></A
->18.1. Building</H2
+>15.4.1. How does cross subnet browsing work ?</H3
 ><P
->This module requires libxml2 to be installed.</P
+>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.</P
 ><P
->To build pdb_xml, run: <B
-CLASS="COMMAND"
->make bin/pdb_xml.so</B
-> in 
-the directory <TT
-CLASS="FILENAME"
->source/</TT
->. </P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2641"
-></A
->18.2. Usage</H2
+>Consider a network set up as follows :</P
 ><P
->The usage of pdb_xml is pretty straightforward. To export data, use:
+><PRE
+CLASS="PROGRAMLISTING"
+>                                   (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)</PRE
+></P
+><P
+>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.</P
+><P
+>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.</P
+><P
+>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.</P
+><P
+>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'.</P
+><P
+>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).</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
 
-<B
-CLASS="COMMAND"
->pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B
->
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
 
-(where filename is the name of the file to put the data in)</P
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D</PRE
+></P
 ><P
->To import data, use:
-<B
-CLASS="COMMAND"
->pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B
->
-
-Where filename is the name to read the data from and current-pdb to put it in.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="SAMBA-LDAP-HOWTO"
-></A
->Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN2664"
-></A
->19.1. Purpose</H2
+>Note that at this point all the subnets are separate, no
+machine is seen across any of the subnets.</P
 ><P
->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.</P
+>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&gt;1B&lt;.  This name was registerd by the Domain master
+browser (N1_C) with the WINS server as soon as it was booted.</P
+><P
+>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 :</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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.</PRE
 ></P
-><UL
-><LI
 ><P
->OpenLDAP - <A
-HREF="http://www.openldap.org/"
-TARGET="_top"
->http://www.openldap.org/</A
+>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.</P
+><P
+>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.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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.</PRE
 ></P
-></LI
-><LI
 ><P
->iPlanet Directory Server - <A
-HREF="http://iplanet.netscape.com/directory"
-TARGET="_top"
->http://iplanet.netscape.com/directory</A
+>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.</P
+><P
+>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 :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>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.</PRE
 ></P
-></LI
-></UL
 ><P
->Note that <A
-HREF="http://www.ora.com/"
-TARGET="_top"
->O'Reilly Publishing</A
-> is working on
-a guide to LDAP for System Administrators which has a planned release date of
-early summer, 2002.</P
+>Synchronizations between the domain master browser and local
+master browsers will continue to occur, but this should be a
+steady state situation.</P
 ><P
->Two additional Samba resources which may prove to be helpful are</P
+>If either router R1 or R2 fails the following will occur:</P
 ><P
 ></P
-><UL
+><OL
+TYPE="1"
 ><LI
 ><P
->The <A
-HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-2_2-howto.html"
-TARGET="_top"
->Samba-PDC-LDAP-HOWTO</A
->
-	maintained by Ignacio Coupeau.</P
+>	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.
+	</P
 ></LI
 ><LI
 ><P
->The NT migration scripts from <A
-HREF="http://samba.idealx.org/"
-TARGET="_top"
->IDEALX</A
-> that are
-	geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
+>	Attempts to connect to these inaccessible computers will fail, but the
+	names will not be removed from the network neighbourhood lists.
 	</P
 ></LI
-></UL
+><LI
+><P
+>	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.
+	</P
+></LI
+></OL
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2684"
+NAME="AEN2760"
 ></A
->19.2. Introduction</H2
+>15.5. Setting up a WINS server</H2
 ><P
->Traditionally, when configuring <A
-HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
-TARGET="_top"
->"encrypt
-passwords = yes"</A
-> in Samba's <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file, user account
-information such as username, LM/NT password hashes, password change times, and account
-flags have been stored in the <TT
-CLASS="FILENAME"
->smbpasswd(5)</TT
-> file.  There are several
-disadvantages to this approach for sites with very large numbers of users (counted
-in the thousands).</P
+>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 </P
 ><P
+><B
+CLASS="COMMAND"
+>		wins support = yes</B
 ></P
-><UL
-><LI
 ><P
->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.</P
-></LI
-><LI
+>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.</P
 ><P
->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 <B
-CLASS="COMMAND"
->rsync(1)</B
-> and <B
+>Machines with "<B
 CLASS="COMMAND"
->ssh(1)</B
->
-and wrote custom, in-house scripts.</P
-></LI
-><LI
-><P
->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).</P
-></LI
-></UL
+>wins support = yes</B
+>" will keep a list of 
+all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P
 ><P
->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. <TT
-CLASS="PARAMETER"
-><I
->--with-ldapsam</I
-></TT
-> or
-<TT
-CLASS="PARAMETER"
-><I
->--with-tdbsam</I
-></TT
->) requires compile time support.</P
+>You should set up only ONE wins server.  Do NOT set the
+"<B
+CLASS="COMMAND"
+>wins support = yes</B
+>" option on more than one Samba 
+server.</P
 ><P
->When compiling Samba to include the <TT
-CLASS="PARAMETER"
-><I
->--with-ldapsam</I
-></TT
-> 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.</P
+>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-&#62;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.</P
 ><P
->There are a few points to stress about what the <TT
-CLASS="PARAMETER"
-><I
->--with-ldapsam</I
-></TT
->
-does not provide.  The LDAP support referred to in the this documentation does not
-include:</P
+>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-&#62;Network-&#62;Protocols-&#62;TCP-&#62;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 :</P
 ><P
+><B
+CLASS="COMMAND"
+>wins server = &gt;name or IP address&lt;</B
 ></P
-><UL
-><LI
 ><P
->A means of retrieving user account information from
-	an Windows 2000 Active Directory server.</P
-></LI
-><LI
+>where &gt;name or IP address&lt; is either the DNS name of the WINS server
+machine or its IP address.</P
 ><P
->A means of replacing /etc/passwd.</P
-></LI
-></UL
+>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
+"<B
+CLASS="COMMAND"
+>wins support = yes</B
+>" option and the 
+"<B
+CLASS="COMMAND"
+>wins server = &gt;name&lt;</B
+>" option then
+nmbd will fail to start.</P
 ><P
->The second item can be accomplished by using LDAP NSS and PAM modules.  LGPL
-versions of these libraries can be obtained from PADL Software
-(<A
-HREF="http://www.padl.com/"
-TARGET="_top"
->http://www.padl.com/</A
->).  However,
-the details of configuring these packages are beyond the scope of this document.</P
+>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.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2713"
+NAME="AEN2779"
 ></A
->19.3. Supported LDAP Servers</H2
+>15.6. Setting up Browsing in a WORKGROUP</H2
 ><P
->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
-<A
-HREF="samba-patches@samba.org"
-TARGET="_top"
->samba-patches@samba.org</A
-> and
-<A
-HREF="jerry@samba.org"
-TARGET="_top"
->jerry@samba.org</A
->.</P
+>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.</P
+><P
+>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 :</P
+><P
+><B
+CLASS="COMMAND"
+>domain master = yes</B
+></P
+><P
+>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 :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>        domain master = yes
+        local master = yes
+        preferred master = yes
+        os level = 65</PRE
+></P
+><P
+>The domain master browser may be the same machine as the WINS
+server, if you require.</P
+><P
+>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 :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>        domain master = no
+        local master = yes
+        preferred master = yes
+        os level = 65</PRE
+></P
+><P
+>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.</P
+><P
+>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.</P
+><P
+>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 :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>        domain master = no
+        local master = no
+        preferred master = no
+        os level = 0</PRE
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2718"
+NAME="AEN2797"
 ></A
->19.4. Schema and Relationship to the RFC 2307 posixAccount</H2
+>15.7. Setting up Browsing in a DOMAIN</H2
 ><P
->Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
-<TT
-CLASS="FILENAME"
->examples/LDAP/samba.schema</TT
->.  (Note that this schema
-file has been modified since the experimental support initially included
-in 2.2.2).  The sambaAccount objectclass is given here:</P
+>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&gt;1B&lt;) with WINS instead of the PDC.</P
+><P
+>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 :</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->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 ))</PRE
+>        domain master = no
+        local master = yes
+        preferred master = yes
+        os level = 65</PRE
 ></P
 ><P
->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 <A
-HREF="jerry@samba.org"
-TARGET="_top"
->jerry@samba.org</A
-></P
+>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.</P
 ><P
->Just as the smbpasswd file is mean to store information which supplements a
-user's <TT
-CLASS="FILENAME"
->/etc/passwd</TT
-> entry, so is the sambaAccount object
-meant to supplement the UNIX user account information.  A sambaAccount is a
-<TT
-CLASS="CONSTANT"
->STRUCTURAL</TT
-> 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.</P
+>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 :</P
 ><P
->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.</P
+><B
+CLASS="COMMAND"
+>        domain master = no
+        local master = no
+        preferred master = no
+        os level = 0</B
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2730"
+NAME="AEN2807"
 ></A
->19.5. Configuring Samba with LDAP</H2
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="AEN2732"
-></A
->19.5.1. OpenLDAP configuration</H3
+>15.8. Forcing samba to be the master</H2
 ><P
->To include support for the sambaAccount object in an OpenLDAP directory
-server, first copy the samba.schema file to slapd's configuration directory.</P
+>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.</P
 ><P
-><TT
-CLASS="PROMPT"
->root# </TT
-><B
-CLASS="COMMAND"
->cp samba.schema /etc/openldap/schema/</B
-></P
+>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!)</P
 ><P
->Next, include the <TT
-CLASS="FILENAME"
->samba.schema</TT
-> file in <TT
-CLASS="FILENAME"
->slapd.conf</TT
->.
-The sambaAccount object contains two attributes which depend upon other schema
-files.  The 'uid' attribute is defined in <TT
-CLASS="FILENAME"
->cosine.schema</TT
-> and
-the 'displayName' attribute is defined in the <TT
-CLASS="FILENAME"
->inetorgperson.schema</TT
->
-file.  Both of these must be included before the <TT
-CLASS="FILENAME"
->samba.schema</TT
-> file.</P
+>A "os level" of 2 would make it beat WfWg and Win95, but not NTAS.  A
+NTAS domain controller uses level 32.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->## /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
-
-....</PRE
-></P
+>The maximum os level is 255</P
 ><P
->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).</P
+>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.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
-># 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</PRE
-></P
+>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.</P
+><P
+>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.</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2749"
+NAME="AEN2816"
 ></A
->19.5.2. Configuring Samba</H3
+>15.9. Making samba the domain master</H2
 ><P
->The following parameters are available in smb.conf only with <TT
-CLASS="PARAMETER"
-><I
->--with-ldapsam</I
-></TT
->
-was included with compiling Samba.</P
+>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.</P
 ><P
-></P
-><UL
-><LI
+>Note that you should NOT set Samba to be the domain master for a
+workgroup that has the same name as an NT Domain.</P
+><P
+>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.</P
+><P
+>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.</P
+><P
+>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:</P
 ><P
-><A
-HREF="smb.conf.5.html#LDAPSSL"
-TARGET="_top"
->ldap ssl</A
 ></P
-></LI
+><OL
+TYPE="1"
 ><LI
 ><P
-><A
-HREF="smb.conf.5.html#LDAPSERVER"
-TARGET="_top"
->ldap server</A
-></P
+>	your local master browsers will be unable to find a domain master
+	browser, as it will only be looking on the local subnet.
+	</P
 ></LI
 ><LI
 ><P
-><A
-HREF="smb.conf.5.html#LDAPADMINDN"
-TARGET="_top"
->ldap admin dn</A
-></P
+>	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.
+	</P
 ></LI
-><LI
+></OL
+><P
+>If, however, both samba and your clients are using a WINS server, then:</P
 ><P
-><A
-HREF="smb.conf.5.html#LDAPSUFFIX"
-TARGET="_top"
->ldap suffix</A
 ></P
-></LI
+><OL
+TYPE="1"
 ><LI
 ><P
-><A
-HREF="smb.conf.5.html#LDAPFILTER"
-TARGET="_top"
->ldap filter</A
-></P
+>	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.
+	</P
 ></LI
 ><LI
 ><P
-><A
-HREF="smb.conf.5.html#LDAPPORT"
-TARGET="_top"
->ldap port</A
-></P
+>	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.  
+	</P
 ></LI
-></UL
-><P
->These are described in the <A
-HREF="smb.conf.5.html"
-TARGET="_top"
->smb.conf(5)</A
-> man
-page and so will not be repeated here.  However, a sample smb.conf file for
-use with an LDAP directory could appear as</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->## /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 <TT
-CLASS="REPLACEABLE"
-><I
->secretpw</I
-></TT
->' 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 = "(&amp;(uid=%u)(objectclass=sambaAccount))"</PRE
-></P
-></DIV
+></OL
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2777"
+NAME="AEN2834"
 ></A
->19.6. Accounts and Groups management</H2
+>15.10. Note about broadcast addresses</H2
 ><P
->As users accounts are managed thru the sambaAccount objectclass, you should
-modify you existing administration tools to deal with sambaAccount attributes.</P
-><P
->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).</P
-><P
->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).</P
+>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.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2782"
+NAME="AEN2837"
 ></A
->19.7. Security and sambaAccount</H2
-><P
->There are two important points to remember when discussing the security
-of sambaAccount entries in the directory.</P
+>15.11. Multiple interfaces</H2
 ><P
-></P
-><UL
-><LI
+>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.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="VFS"
+></A
+>Chapter 16. Stackable VFS modules</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN2855"
+></A
+>16.1. Introduction and configuration</H2
 ><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Never</I
-></SPAN
-> retrieve the lmPassword or
-	ntPassword attribute values over an unencrypted LDAP session.</P
-></LI
-><LI
+>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.</P
 ><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Never</I
-></SPAN
-> allow non-admin users to
-	view the lmPassword or ntPassword attribute values.</P
-></LI
-></UL
-><P
->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 <A
-HREF="ENCRYPTION.html"
-TARGET="_top"
->ENCRYPTION chapter</A
-> of the Samba-HOWTO-Collection.</P
+>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.</P
 ><P
->To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
-to require an encrypted session (<B
-CLASS="COMMAND"
->ldap ssl = on</B
->) 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
-(<B
+>To use the VFS modules, create a share similar to the one below.  The
+important parameter is the <B
 CLASS="COMMAND"
->ldap ssl = off</B
->).</P
-><P
->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.</P
-><P
->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 <TT
-CLASS="FILENAME"
->slapd.conf</TT
->:</P
-><P
-><PRE
+>vfs object</B
+> 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:
+
+<PRE
 CLASS="PROGRAMLISTING"
->## 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</PRE
+>       [audit]
+                comment = Audited /data directory
+                path = /data
+                vfs object = /path/to/audit.so /path/to/recycle.so
+                writeable = yes
+                browseable = yes</PRE
 ></P
+><P
+>The modules are used in the order they are specified.</P
+><P
+>Further documentation on writing VFS modules for Samba can be found in
+the Samba Developers Guide.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2802"
+NAME="AEN2864"
 ></A
->19.8. LDAP specials attributes for sambaAccounts</H2
-><P
->The sambaAccount objectclass is composed of the following attributes:</P
+>16.2. Included modules</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN2866"
+></A
+>16.2.1. audit</H3
 ><P
+>A simple module to audit file access to the syslog
+facility.  The following operations are logged:
+<P
 ></P
-><UL
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->lmPassword</TT
->: the LANMAN password 16-byte hash stored as a character
-	representation of a hexidecimal string.</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->ntPassword</TT
->: the NT password hash 16-byte stored as a character
-	representation of a hexidecimal string.</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->pwdLastSet</TT
->: The integer time in seconds since 1970 when the
-	<TT
-CLASS="CONSTANT"
->lmPassword</TT
-> and <TT
-CLASS="CONSTANT"
->ntPassword</TT
-> attributes were last set.
-	</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->acctFlags</TT
->: string of 11 characters surrounded by square brackets []
-	representing account flags such as U (user), W(workstation), X(no password expiration), and
-	D(disabled).</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->logonTime</TT
->: Integer value currently unused</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->logoffTime</TT
->: Integer value currently unused</P
-></LI
-><LI
-><P
-><TT
-CLASS="CONSTANT"
->kickoffTime</TT
->: Integer value currently unused</P
-></LI
-><LI
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>share</TD
+></TR
+><TR
+><TD
+>connect/disconnect</TD
+></TR
+><TR
+><TD
+>directory opens/create/remove</TD
+></TR
+><TR
+><TD
+>file open/close/rename/unlink/chmod</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><TT
-CLASS="CONSTANT"
->pwdCanChange</TT
->: Integer value currently unused</P
-></LI
-><LI
+></P
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2874"
+></A
+>16.2.2. recycle</H3
 ><P
-><TT
-CLASS="CONSTANT"
->pwdMustChange</TT
->: Integer value currently unused</P
-></LI
-><LI
+>A recycle-bin like modules. When used any unlink call
+will be intercepted and files moved to the recycle
+directory instead of beeing deleted.</P
 ><P
-><TT
-CLASS="CONSTANT"
->homeDrive</TT
->: 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.</P
-></LI
-><LI
+>Supported options:
+<P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>vfs_recycle_bin:repository</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->scriptPath</TT
->: 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.</P
-></LI
-><LI
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:keeptree</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->profilePath</TT
->: 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.</P
-></LI
-><LI
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:versions</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->smbHome</TT
->: 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.
-	</P
-></LI
-><LI
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:touch</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->userWorkstation</TT
->: character string value currently unused.
-	</P
-></LI
-><LI
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:maxsize</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->rid</TT
->: the integer representation of the user's relative identifier
-	(RID).</P
-></LI
-><LI
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:exclude</DT
+><DD
 ><P
-><TT
-CLASS="CONSTANT"
->primaryGroupID</TT
->: the relative identifier (RID) of the primary group
-	of the user.</P
-></LI
-></UL
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:exclude_dir</DT
+><DD
 ><P
->The majority of these parameters are only used when Samba is acting as a PDC of
-a domain (refer to the <A
-HREF="Samba-PDC-HOWTO.html"
-TARGET="_top"
->Samba-PDC-HOWTO</A
-> 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:</P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:noversions</DT
+><DD
 ><P
+>FIXME</P
+></DD
+></DL
+></DIV
 ></P
-><UL
-><LI
-><P
->smbHome</P
-></LI
-><LI
-><P
->scriptPath</P
-></LI
-><LI
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2911"
+></A
+>16.2.3. netatalk</H3
 ><P
->logonPath</P
-></LI
-><LI
+>A netatalk module, that will ease co-existence of samba and
+netatalk file sharing services.</P
 ><P
->homeDrive</P
-></LI
-></UL
+>Advantages compared to the old netatalk module:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>it doesn't care about creating of .AppleDouble forks, just keeps ones in sync</TD
+></TR
+><TR
+><TD
+>if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</TD
+></TR
+></TBODY
+></TABLE
 ><P
->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 <B
-CLASS="COMMAND"
->logon home = \\%L\%u</B
-> was defined in
-its <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file. When a user named "becky" logons to the domain,
-the <TT
-CLASS="PARAMETER"
-><I
->logon home</I
-></TT
-> 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 <TT
-CLASS="PARAMETER"
-><I
->logon home</I
-></TT
-> 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).</P
+></P
+></P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2872"
+NAME="AEN2918"
 ></A
->19.9. Example LDIF Entries for a sambaAccount</H2
+>16.3. VFS modules available elsewhere</H2
 ><P
->The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
+>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).</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->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</PRE
+>No statemets about the stability or functionality any module
+should be implied due to its presence here.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2922"
+></A
+>16.3.1. DatabaseFS</H3
+><P
+>URL: <A
+HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php"
+TARGET="_top"
+>http://www.css.tayloru.edu/~elorimer/databasefs/index.php</A
 ></P
 ><P
->The following is an LDIF entry for using both the sambaAccount and
-posixAccount objectclasses:</P
+>By <A
+HREF="mailto:elorimer@css.tayloru.edu"
+TARGET="_top"
+>Eric Lorimer</A
+>.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->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</PRE
-></P
+>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.</P
+><P
+>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.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN2880"
+NAME="AEN2930"
 ></A
->19.10. Comments</H2
+>16.3.2. vscan</H3
 ><P
->Please mail all comments regarding this HOWTO to <A
-HREF="mailto:jerry@samba.org"
+>URL: <A
+HREF="http://www.openantivirus.org/"
 TARGET="_top"
->jerry@samba.org</A
->.  This documents was
-last updated to reflect the Samba 2.2.3 release.&#13;</P
+>http://www.openantivirus.org/</A
+></P
+><P
+>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.</P
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -14404,15 +14586,15 @@ CLASS="CHAPTER"
 ><A
 NAME="CVS-ACCESS"
 ></A
->Chapter 20. HOWTO Access Samba source code via CVS</H1
+>Chapter 17. Access Samba source code via CVS</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2891"
+NAME="AEN2942"
 ></A
->20.1. Introduction</H2
+>17.1. Introduction</H2
 ><P
 >Samba is developed in an open environment.  Developers use CVS
 (Concurrent Versioning System) to "checkin" (also known as 
@@ -14432,9 +14614,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2896"
+NAME="AEN2947"
 ></A
->20.2. CVS Access to samba.org</H2
+>17.2. CVS Access to samba.org</H2
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2899"
+NAME="AEN2950"
 ></A
->20.2.1. Access via CVSweb</H3
+>17.2.1. Access via CVSweb</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2904"
+NAME="AEN2955"
 ></A
->20.2.2. Access via cvs</H3
+>17.2.2. Access via cvs</H3
 ><P
 >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"
 ><A
 NAME="GROUPMAPPING"
 ></A
->Chapter 21. Group mapping HOWTO</H1
+>Chapter 18. Group mapping HOWTO</H1
 ><P
 > 
 Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
@@ -14677,15 +14859,15 @@ CLASS="CHAPTER"
 ><A
 NAME="SPEED"
 ></A
->Chapter 22. Samba performance issues</H1
+>Chapter 19. Samba performance issues</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2982"
+NAME="AEN3033"
 ></A
->22.1. Comparisons</H2
+>19.1. Comparisons</H2
 ><P
 >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
@@ -14714,98 +14896,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2988"
-></A
->22.2. Oplocks</H2
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="AEN2990"
-></A
->22.2.1. Overview</H3
-><P
->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.</P
-><P
->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 :</P
-><P
-><B
-CLASS="COMMAND"
->oplocks = False</B
-></P
-><P
->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.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2998"
-></A
->22.2.2. Level2 Oplocks</H3
-><P
->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 :</P
-><P
-><B
-CLASS="COMMAND"
->level2 oplocks = true</B
-></P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3004"
-></A
->22.2.3. Old 'fake oplocks' option - deprecated</H3
-><P
->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.</P
-><P
->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.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3008"
+NAME="AEN3039"
 ></A
->22.3. Socket options</H2
+>19.2. Socket options</H2
 ><P
 >There are a number of socket options that can greatly affect the
 performance of a TCP based server like Samba.</P
@@ -14831,9 +14924,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3015"
+NAME="AEN3046"
 ></A
->22.4. Read size</H2
+>19.3. Read size</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3020"
+NAME="AEN3051"
 ></A
->22.5. Max xmit</H2
+>19.4. Max xmit</H2
 ><P
 >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,56 +14973,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3025"
-></A
->22.6. Locking</H2
-><P
->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.</P
-><P
->The performance hit will probably be greater on NFS mounted
-filesystems, but could be quite high even on local disks.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3029"
-></A
->22.7. Share modes</H2
-><P
->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".</P
-><P
->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.</P
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3034"
+NAME="AEN3056"
 ></A
->22.8. Log level</H2
+>19.5. Log level</H2
 ><P
 >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
@@ -14941,23 +14987,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3037"
-></A
->22.9. Wide lines</H2
-><P
->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.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3040"
+NAME="AEN3059"
 ></A
->22.10. Read raw</H2
+>19.6. Read raw</H2
 ><P
 >The "read raw" operation is designed to be an optimised, low-latency
 file read operation. A server may choose to not support it,
@@ -14977,9 +15009,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3045"
+NAME="AEN3064"
 ></A
->22.11. Write raw</H2
+>19.7. Write raw</H2
 ><P
 >The "write raw" operation is designed to be an optimised, low-latency
 file write operation. A server may choose to not support it,
@@ -14994,56 +15026,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3049"
-></A
->22.12. Read prediction</H2
-><P
->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.</P
-><P
->This is disabled by default. You can enable it by using "read
-prediction = yes".</P
-><P
->Note that read prediction is only used on files that were opened read
-only.</P
-><P
->Read prediction should particularly help for those silly clients (such
-as "Write" under NT) which do lots of very small reads on a file.</P
-><P
->Samba will not read ahead more data than the amount specified in the
-"read size" option. It always reads ahead on 1k block boundaries.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3056"
-></A
->22.13. Memory mapping</H2
-><P
->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.</P
-><P
->To enable you you have to recompile Samba with the -DUSE_MMAP option
-on the FLAGS line of the Makefile.</P
-><P
->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".</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3061"
+NAME="AEN3068"
 ></A
->22.14. Slow Clients</H2
+>19.8. Slow Clients</H2
 ><P
 >One person has reported that setting the protocol to COREPLUS rather
 than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
@@ -15058,9 +15043,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3065"
+NAME="AEN3072"
 ></A
->22.15. Slow Logins</H2
+>19.9. Slow Logins</H2
 ><P
 >Slow logins are almost always due to the password checking time. Using
 the lowest practical "password level" will improve things a lot. You
@@ -15071,9 +15056,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3068"
+NAME="AEN3075"
 ></A
->22.16. Client tuning</H2
+>19.10. Client tuning</H2
 ><P
 >Often a speed problem can be traced to the client. The client (for
 example Windows for Workgroups) can often be tuned for better TCP
@@ -15148,11 +15133,13 @@ turned out I was better off without any!!!!!</P
 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.</P
 ><P
->FIXME
-The figures are:          Put              Get 
+><PRE
+CLASS="PROGRAMLISTING"
+>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</P
+DX4-75 client NE2000:     370-380kB/s      330-350kB/s</PRE
+></P
 ><P
 >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 
@@ -15170,41 +15157,442 @@ 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.</P
 ></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="GROUPPROFILES"
+></A
+>Chapter 20. Creating Group Profiles</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3123"
+></A
+>20.1. Windows '9x</H2
+><P
+>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 
+<TT
+CLASS="FILENAME"
+>tools/reskit/netadmin/poledit</TT
+>.  You install this
+using the Add/Remove Programs facility and then click on the 'Have Disk'
+tab.</P
+><P
+>Use the Group Policy Editor to create a policy file that specifies the
+location of user profiles and/or the <TT
+CLASS="FILENAME"
+>My Documents</TT
+> etc.
+stuff. You then save these settings in a file called
+<TT
+CLASS="FILENAME"
+>Config.POL</TT
+> 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.</P
+><P
+>All of this is covered in the Win98 Resource Kit documentation.</P
+><P
+>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.</P
+></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3100"
+NAME="AEN3132"
+></A
+>20.2. Windows NT 4</H2
+><P
+>Unfortunately, the Resource Kit info is Win NT4/2K version specific.</P
+><P
+>Here is a quick guide:</P
+><P
+></P
+><UL
+><LI
+><P
+>On your NT4 Domain Controller, right click on 'My Computer', then
+select the tab labelled 'User Profiles'.</P
+></LI
+><LI
+><P
+>Select a user profile you want to migrate and click on it.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>I am using the term &quot;migrate&quot; 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.</P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+>Click the 'Copy To' button.</P
+></LI
+><LI
+><P
+>In the box labelled 'Copy Profile to' add your new path, eg:
+<TT
+CLASS="FILENAME"
+>c:\temp\foobar</TT
+></P
+></LI
+><LI
+><P
+>Click on the button labelled 'Change' in the "Permitted to use" box.</P
+></LI
+><LI
+><P
+>Click on the group 'Everyone' and then click OK. This closes the
+'chose user' box.</P
+></LI
+><LI
+><P
+>Now click OK.</P
+></LI
+></UL
+><P
+>Follow the above for every profile you need to migrate.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3155"
+></A
+>20.2.1. Side bar Notes</H3
+><P
+>You should obtain the SID of your NT4 domain. You can use smbpasswd to do
+this. Read the man page.</P
+><P
+>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.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3159"
+></A
+>20.2.2. Mandatory profiles</H3
+><P
+>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.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3162"
 ></A
->22.17. My Results</H2
+>20.2.3. moveuser.exe</H3
 ><P
->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.</P
+>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.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3165"
+></A
+>20.2.4. Get SID</H3
 ><P
->I get 490k/s on reading a 8Mb file with copy.
-I get 441k/s writing the same file to the samba server.</P
+>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
+Resource Kit.</P
 ><P
->Of course, there's a lot more to benchmarks than 2 raw throughput
-figures, but it gives you a ballpark figure.</P
+>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</P
 ><P
->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 ...</P
+>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.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3170"
+></A
+>20.3. Windows 2000/XP</H2
+><P
+>You must first convert the profile from a local profile to a domain
+profile on the MS Windows workstation as follows:</P
+><P
+></P
+><UL
+><LI
+><P
+>Log on as the LOCAL workstation administrator.</P
+></LI
+><LI
+><P
+>Right click on the 'My Computer' Icon, select 'Properties'</P
+></LI
+><LI
+><P
+>Click on the 'User Profiles' tab</P
+></LI
+><LI
+><P
+>Select the profile you wish to convert (click on it once)</P
+></LI
+><LI
+><P
+>Click on the button 'Copy To'</P
+></LI
+><LI
+><P
+>In the "Permitted to use" box, click on the 'Change' button.</P
+></LI
+><LI
+><P
+>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.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="90%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>You will need to log on if a logon box opens up. Eg: In the connect
+as: MIDEARTH\root, password: mypassword.</P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+>To make the profile capable of being used by anyone select 'Everyone'</P
+></LI
+><LI
+><P
+>Click OK. The Selection box will close.</P
+></LI
+><LI
+><P
+>Now click on the 'Ok' button to create the profile in the path you
+nominated.</P
+></LI
+></UL
+><P
+>Done. You now have a profile that can be editted using the samba-3.0.0
+profiles tool.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Under NT/2K the use of mandotory profiles forces the use of MS Exchange
+storage of mail data. That keeps desktop profiles usable.</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+></P
+><UL
+><LI
+><P
+>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:</P
+><P
+>"Computer Configuration\Administrative Templates\System\User
+Profiles\Do not check for user ownership of Roaming Profile Folders"</P
+><P
+>...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.</P
+><P
+>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):</P
+></LI
+><LI
+><P
+>On the XP workstation log in with an Administrator account.</P
+></LI
+><LI
+><P
+>Click: "Start", "Run"</P
+></LI
+><LI
+><P
+>Type: "mmc"</P
+></LI
+><LI
+><P
+>Click: "OK"</P
+></LI
+><LI
+><P
+>A Microsoft Management Console should appear.</P
+></LI
+><LI
+><P
+>Click: File, "Add/Remove Snap-in...", "Add"</P
+></LI
+><LI
+><P
+>Double-Click: "Group Policy"</P
+></LI
+><LI
+><P
+>Click: "Finish", "Close"</P
+></LI
+><LI
+><P
+>Click: "OK"</P
+></LI
+><LI
+><P
+>In the "Console Root" window:</P
+></LI
+><LI
+><P
+>Expand: "Local Computer Policy", "Computer Configuration",</P
+></LI
+><LI
+><P
+>"Administrative Templates", "System", "User Profiles"</P
+></LI
+><LI
+><P
+>Double-Click: "Do not check for user ownership of Roaming Profile</P
+></LI
+><LI
+><P
+>Folders"</P
+></LI
+><LI
+><P
+>Select: "Enabled"</P
+></LI
+><LI
+><P
+>Click: OK"</P
+></LI
+><LI
+><P
+>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).</P
+></LI
+><LI
+><P
+>Reboot</P
+></LI
+></UL
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ></DIV
 ></DIV
 ><DIV
 CLASS="PART"
 ><A
-NAME="AEN3106"
+NAME="APPENDIXES"
 ></A
 ><DIV
 CLASS="TITLEPAGE"
@@ -15219,243 +15607,243 @@ CLASS="TOC"
 >Table of Contents</B
 ></DT
 ><DT
->23. <A
+>21. <A
 HREF="#PORTABILITY"
 >Portability</A
 ></DT
 ><DD
 ><DL
 ><DT
->23.1. <A
-HREF="#AEN3115"
+>21.1. <A
+HREF="#AEN3251"
 >HPUX</A
 ></DT
 ><DT
->23.2. <A
-HREF="#AEN3121"
+>21.2. <A
+HREF="#AEN3257"
 >SCO Unix</A
 ></DT
 ><DT
->23.3. <A
-HREF="#AEN3125"
+>21.3. <A
+HREF="#AEN3261"
 >DNIX</A
 ></DT
 ><DT
->23.4. <A
-HREF="#AEN3154"
+>21.4. <A
+HREF="#AEN3290"
 >RedHat Linux Rembrandt-II</A
 ></DT
 ></DL
 ></DD
 ><DT
->24. <A
+>22. <A
 HREF="#OTHER-CLIENTS"
 >Samba and other CIFS clients</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.1. <A
-HREF="#AEN3175"
+>22.1. <A
+HREF="#AEN3311"
 >Macintosh clients?</A
 ></DT
 ><DT
->24.2. <A
-HREF="#AEN3184"
+>22.2. <A
+HREF="#AEN3320"
 >OS2 Client</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.2.1. <A
-HREF="#AEN3186"
+>22.2.1. <A
+HREF="#AEN3322"
 >How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?</A
 ></DT
 ><DT
->24.2.2. <A
-HREF="#AEN3201"
+>22.2.2. <A
+HREF="#AEN3337"
 >How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?</A
 ></DT
 ><DT
->24.2.3. <A
-HREF="#AEN3210"
+>22.2.3. <A
+HREF="#AEN3346"
 >Are there any other issues when OS/2 (any version) 
 		is used as a client?</A
 ></DT
 ><DT
->24.2.4. <A
-HREF="#AEN3214"
+>22.2.4. <A
+HREF="#AEN3350"
 >How do I get printer driver download working 
 		for OS/2 clients?</A
 ></DT
 ></DL
 ></DD
 ><DT
->24.3. <A
-HREF="#AEN3224"
+>22.3. <A
+HREF="#AEN3360"
 >Windows for Workgroups</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.3.1. <A
-HREF="#AEN3226"
+>22.3.1. <A
+HREF="#AEN3362"
 >Use latest TCP/IP stack from Microsoft</A
 ></DT
 ><DT
->24.3.2. <A
-HREF="#AEN3231"
+>22.3.2. <A
+HREF="#AEN3367"
 >Delete .pwl files after password change</A
 ></DT
 ><DT
->24.3.3. <A
-HREF="#AEN3236"
+>22.3.3. <A
+HREF="#AEN3372"
 >Configure WfW password handling</A
 ></DT
 ><DT
->24.3.4. <A
-HREF="#AEN3240"
+>22.3.4. <A
+HREF="#AEN3376"
 >Case handling of passwords</A
 ></DT
 ></DL
 ></DD
 ><DT
->24.4. <A
-HREF="#AEN3245"
+>22.4. <A
+HREF="#AEN3381"
 >Windows '95/'98</A
 ></DT
 ><DT
->24.5. <A
-HREF="#AEN3261"
+>22.5. <A
+HREF="#AEN3397"
 >Windows 2000 Service Pack 2</A
 ></DT
 ></DL
 ></DD
 ><DT
->25. <A
+>23. <A
 HREF="#BUGREPORT"
 >Reporting Bugs</A
 ></DT
 ><DD
 ><DL
 ><DT
->25.1. <A
-HREF="#AEN3285"
+>23.1. <A
+HREF="#AEN3421"
 >Introduction</A
 ></DT
 ><DT
->25.2. <A
-HREF="#AEN3295"
+>23.2. <A
+HREF="#AEN3431"
 >General info</A
 ></DT
 ><DT
->25.3. <A
-HREF="#AEN3301"
+>23.3. <A
+HREF="#AEN3437"
 >Debug levels</A
 ></DT
 ><DT
->25.4. <A
-HREF="#AEN3318"
+>23.4. <A
+HREF="#AEN3454"
 >Internal errors</A
 ></DT
 ><DT
->25.5. <A
-HREF="#AEN3328"
+>23.5. <A
+HREF="#AEN3464"
 >Attaching to a running process</A
 ></DT
 ><DT
->25.6. <A
-HREF="#AEN3331"
+>23.6. <A
+HREF="#AEN3467"
 >Patches</A
 ></DT
 ></DL
 ></DD
 ><DT
->26. <A
+>24. <A
 HREF="#DIAGNOSIS"
 >Diagnosing your samba server</A
 ></DT
 ><DD
 ><DL
 ><DT
->26.1. <A
-HREF="#AEN3354"
+>24.1. <A
+HREF="#AEN3490"
 >Introduction</A
 ></DT
 ><DT
->26.2. <A
-HREF="#AEN3359"
+>24.2. <A
+HREF="#AEN3495"
 >Assumptions</A
 ></DT
 ><DT
->26.3. <A
-HREF="#AEN3369"
+>24.3. <A
+HREF="#AEN3505"
 >Tests</A
 ></DT
 ><DD
 ><DL
 ><DT
->26.3.1. <A
-HREF="#AEN3371"
+>24.3.1. <A
+HREF="#AEN3507"
 >Test 1</A
 ></DT
 ><DT
->26.3.2. <A
-HREF="#AEN3377"
+>24.3.2. <A
+HREF="#AEN3513"
 >Test 2</A
 ></DT
 ><DT
->26.3.3. <A
-HREF="#AEN3383"
+>24.3.3. <A
+HREF="#AEN3519"
 >Test 3</A
 ></DT
 ><DT
->26.3.4. <A
-HREF="#AEN3398"
+>24.3.4. <A
+HREF="#AEN3534"
 >Test 4</A
 ></DT
 ><DT
->26.3.5. <A
-HREF="#AEN3403"
+>24.3.5. <A
+HREF="#AEN3539"
 >Test 5</A
 ></DT
 ><DT
->26.3.6. <A
-HREF="#AEN3409"
+>24.3.6. <A
+HREF="#AEN3545"
 >Test 6</A
 ></DT
 ><DT
->26.3.7. <A
-HREF="#AEN3417"
+>24.3.7. <A
+HREF="#AEN3553"
 >Test 7</A
 ></DT
 ><DT
->26.3.8. <A
-HREF="#AEN3443"
+>24.3.8. <A
+HREF="#AEN3579"
 >Test 8</A
 ></DT
 ><DT
->26.3.9. <A
-HREF="#AEN3460"
+>24.3.9. <A
+HREF="#AEN3596"
 >Test 9</A
 ></DT
 ><DT
->26.3.10. <A
-HREF="#AEN3468"
+>24.3.10. <A
+HREF="#AEN3604"
 >Test 10</A
 ></DT
 ><DT
->26.3.11. <A
-HREF="#AEN3474"
+>24.3.11. <A
+HREF="#AEN3610"
 >Test 11</A
 ></DT
 ></DL
 ></DD
 ><DT
->26.4. <A
-HREF="#AEN3479"
+>24.4. <A
+HREF="#AEN3615"
 >Still having troubles?</A
 ></DT
 ></DL
@@ -15469,7 +15857,7 @@ CLASS="CHAPTER"
 ><A
 NAME="PORTABILITY"
 ></A
->Chapter 23. Portability</H1
+>Chapter 21. Portability</H1
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3115"
+NAME="AEN3251"
 ></A
->23.1. HPUX</H2
+>21.1. HPUX</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3121"
+NAME="AEN3257"
 ></A
->23.2. SCO Unix</H2
+>21.2. SCO Unix</H2
 ><P
 > 
 If you run an old version of  SCO Unix then you may need to get important 
@@ -15526,9 +15914,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3125"
+NAME="AEN3261"
 ></A
->23.3. DNIX</H2
+>21.3. DNIX</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3154"
+NAME="AEN3290"
 ></A
->23.4. RedHat Linux Rembrandt-II</H2
+>21.4. RedHat Linux Rembrandt-II</H2
 ><P
 >By default RedHat Rembrandt-II during installation adds an
 entry to /etc/hosts as follows:
@@ -15659,7 +16047,7 @@ CLASS="CHAPTER"
 ><A
 NAME="OTHER-CLIENTS"
 ></A
->Chapter 24. Samba and other CIFS clients</H1
+>Chapter 22. Samba and other CIFS clients</H1
 ><P
 >This chapter contains client-specific information.</P
 ><DIV
@@ -15667,9 +16055,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3175"
+NAME="AEN3311"
 ></A
->24.1. Macintosh clients?</H2
+>22.1. Macintosh clients?</H2
 ><P
 >Yes. <A
 HREF="http://www.thursby.com/"
@@ -15713,17 +16101,17 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3184"
+NAME="AEN3320"
 ></A
->24.2. OS2 Client</H2
+>22.2. OS2 Client</H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3186"
+NAME="AEN3322"
 ></A
->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?</H3
 ><P
 >A more complete answer to this question can be 
@@ -15780,9 +16168,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3201"
+NAME="AEN3337"
 ></A
->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?</H3
 ><P
 >You can use the free Microsoft LAN Manager 2.2c Client 
@@ -15824,9 +16212,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3210"
+NAME="AEN3346"
 ></A
->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?</H3
 ><P
 >When you do a NET VIEW or use the "File and Print 
@@ -15846,9 +16234,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3214"
+NAME="AEN3350"
 ></A
->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?</H3
 ><P
 >First, create a share called [PRINTDRV] that is 
@@ -15897,17 +16285,17 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3224"
+NAME="AEN3360"
 ></A
->24.3. Windows for Workgroups</H2
+>22.3. Windows for Workgroups</H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3226"
+NAME="AEN3362"
 ></A
->24.3.1. Use latest TCP/IP stack from Microsoft</H3
+>22.3.1. Use latest TCP/IP stack from Microsoft</H3
 ><P
 >Use the latest TCP/IP stack from microsoft if you use Windows
 for workgroups.</P
@@ -15927,9 +16315,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3231"
+NAME="AEN3367"
 ></A
->24.3.2. Delete .pwl files after password change</H3
+>22.3.2. Delete .pwl files after password change</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3236"
+NAME="AEN3372"
 ></A
->24.3.3. Configure WfW password handling</H3
+>22.3.3. Configure WfW password handling</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3240"
+NAME="AEN3376"
 ></A
->24.3.4. Case handling of passwords</H3
+>22.3.4. Case handling of passwords</H3
 ><P
 >Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
 HREF="smb.conf.5.html"
@@ -15985,9 +16373,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3245"
+NAME="AEN3381"
 ></A
->24.4. Windows '95/'98</H2
+>22.4. Windows '95/'98</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3261"
+NAME="AEN3397"
 ></A
->24.5. Windows 2000 Service Pack 2</H2
+>22.5. Windows 2000 Service Pack 2</H2
 ><P
 > 
 There are several annoyances with Windows 2000 SP2. One of which
@@ -16117,15 +16505,15 @@ CLASS="CHAPTER"
 ><A
 NAME="BUGREPORT"
 ></A
->Chapter 25. Reporting Bugs</H1
+>Chapter 23. Reporting Bugs</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3285"
+NAME="AEN3421"
 ></A
->25.1. Introduction</H2
+>23.1. Introduction</H2
 ><P
 >The email address for bug reports for stable releases is <A
 HREF="samba@samba.org"
@@ -16168,9 +16556,9 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3295"
+NAME="AEN3431"
 ></A
->25.2. General info</H2
+>23.2. General info</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3301"
+NAME="AEN3437"
 ></A
->25.3. Debug levels</H2
+>23.3. Debug levels</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3318"
+NAME="AEN3454"
 ></A
->25.4. Internal errors</H2
+>23.4. Internal errors</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3328"
+NAME="AEN3464"
 ></A
->25.5. Attaching to a running process</H2
+>23.5. Attaching to a running process</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3331"
+NAME="AEN3467"
 ></A
->25.6. Patches</H2
+>23.6. Patches</H2
 ><P
 >The best sort of bug report is one that includes a fix! If you send us
 patches please use <B
@@ -16347,15 +16735,15 @@ CLASS="CHAPTER"
 ><A
 NAME="DIAGNOSIS"
 ></A
->Chapter 26. Diagnosing your samba server</H1
+>Chapter 24. Diagnosing your samba server</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3354"
+NAME="AEN3490"
 ></A
->26.1. Introduction</H2
+>24.1. Introduction</H2
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3359"
+NAME="AEN3495"
 ></A
->26.2. Assumptions</H2
+>24.2. Assumptions</H2
 ><P
 >In all of the tests it is assumed you have a Samba server called 
 BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P
@@ -16413,17 +16801,17 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3369"
+NAME="AEN3505"
 ></A
->26.3. Tests</H2
+>24.3. Tests</H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3371"
+NAME="AEN3507"
 ></A
->26.3.1. Test 1</H3
+>24.3.1. Test 1</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3377"
+NAME="AEN3513"
 ></A
->26.3.2. Test 2</H3
+>24.3.2. Test 2</H3
 ><P
 >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"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3383"
+NAME="AEN3519"
 ></A
->26.3.3. Test 3</H3
+>24.3.3. Test 3</H3
 ><P
 >Run the command "smbclient -L BIGSERVER" on the unix box. You
 should get a list of available shares back. </P
@@ -16540,9 +16928,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3398"
+NAME="AEN3534"
 ></A
->26.3.4. Test 4</H3
+>24.3.4. Test 4</H3
 ><P
 >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
 IP address of your Samba server back.</P
@@ -16561,9 +16949,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3403"
+NAME="AEN3539"
 ></A
->26.3.5. Test 5</H3
+>24.3.5. Test 5</H3
 ><P
 >run the command <B
 CLASS="COMMAND"
@@ -16582,9 +16970,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3409"
+NAME="AEN3545"
 ></A
->26.3.6. Test 6</H3
+>24.3.6. Test 6</H3
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -16616,9 +17004,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3417"
+NAME="AEN3553"
 ></A
->26.3.7. Test 7</H3
+>24.3.7. Test 7</H3
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -16705,9 +17093,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3443"
+NAME="AEN3579"
 ></A
->26.3.8. Test 8</H3
+>24.3.8. Test 8</H3
 ><P
 >On the PC type the command <B
 CLASS="COMMAND"
@@ -16765,9 +17153,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3460"
+NAME="AEN3596"
 ></A
->26.3.9. Test 9</H3
+>24.3.9. Test 9</H3
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -16799,9 +17187,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3468"
+NAME="AEN3604"
 ></A
->26.3.10. Test 10</H3
+>24.3.10. Test 10</H3
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -16825,9 +17213,9 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3474"
+NAME="AEN3610"
 ></A
->26.3.11. Test 11</H3
+>24.3.11. Test 11</H3
 ><P
 >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"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3479"
+NAME="AEN3615"
 ></A
->26.4. Still having troubles?</H2
+>24.4. Still having troubles?</H2
 ><P
 >Try the mailing list or newsgroup, or use the ethereal utility to
 sniff the problem. The official samba mailing list can be reached at
author	Jelmer Vernooij <jelmer@samba.org>	2003-02-18 22:14:04 +0000
committer	Jelmer Vernooij <jelmer@samba.org>	2003-02-18 22:14:04 +0000
commit	ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 (patch)
tree	deda0311c634bd433278a352e1a9daece40ff0f6 /docs/htmldocs/Samba-HOWTO-Collection.html
parent	4668623d62b3a7b133e26dd1397b956c4ddac335 (diff)
download	samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.gz samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.tar.bz2 samba-ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68.zip