From cdd3fa410a6b9f0ddc778149175f3ba7e8a7095d Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Thu, 17 Apr 2003 19:15:22 +0000
Subject: Regenerate docs (This used to be commit
 13a4cd540a1c193e77d973b9dac5bc2d9e7a5353)

---
 docs/htmldocs/Samba-HOWTO-Collection.html | 31094 ++++++++++++++--------------
 docs/htmldocs/ads.html                    |    78 +-
 docs/htmldocs/appendixes.html             |   442 +-
 docs/htmldocs/browsing-quick.html         |   131 +-
 docs/htmldocs/bugreport.html              |    92 +-
 docs/htmldocs/compiling.html              |   198 +-
 docs/htmldocs/diagnosis.html              |    81 +-
 docs/htmldocs/findsmb.1.html              |    24 +-
 docs/htmldocs/groupmapping.html           |     2 +-
 docs/htmldocs/improved-browsing.html      |   112 +-
 docs/htmldocs/install.html                |   151 +-
 docs/htmldocs/integrate-ms-networks.html  |   130 +-
 docs/htmldocs/introduction.html           |   282 +-
 docs/htmldocs/msdfs.html                  |    10 +-
 docs/htmldocs/net.8.html                  |  1576 +-
 docs/htmldocs/optional.html               |   949 +-
 docs/htmldocs/other-clients.html          |   136 +-
 docs/htmldocs/pam.html                    |    38 +-
 docs/htmldocs/passdb.html                 |   345 +-
 docs/htmldocs/pdbedit.8.html              |    44 +-
 docs/htmldocs/portability.html            |    63 +-
 docs/htmldocs/printing.html               |   221 +-
 docs/htmldocs/samba-bdc.html              |   100 +-
 docs/htmldocs/samba-howto-collection.html |   836 +-
 docs/htmldocs/samba-pdc.html              |   867 +-
 docs/htmldocs/samba.7.html                |   352 +-
 docs/htmldocs/securing-samba.html         |    67 +-
 docs/htmldocs/securitylevels.html         |    38 +-
 docs/htmldocs/smb.conf.5.html             |    24 +-
 docs/htmldocs/speed.html                  |   121 +-
 docs/htmldocs/type.html                   |   299 +-
 docs/htmldocs/unix-permissions.html       |    99 +-
 docs/htmldocs/vfs.html                    |   100 +-
 docs/htmldocs/winbind.html                |   258 +-
 34 files changed, 19555 insertions(+), 19805 deletions(-)

(limited to 'docs/htmldocs')

diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index 8c470203e7..5dd720ddb2 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -52,10 +52,10 @@ CLASS="EDITEDBY"
 >Edited by</H4
 ><H3
 CLASS="EDITOR"
->John H Terpstra</H3
+>Jelmer R. Vernooij</H3
 ><H3
 CLASS="EDITOR"
->Jelmer Vernooij</H3
+>John H. Terpstra</H3
 ><H3
 CLASS="EDITOR"
 >Gerald (Jerry) Carter</H3
@@ -65,7 +65,7 @@ CLASS="ABSTRACT"
 ><P
 ></P
 ><A
-NAME="AEN32"
+NAME="AEN34"
 ></A
 ><P
 >This book is a collection of HOWTOs added to Samba documentation over the years.
@@ -95,7 +95,7 @@ CLASS="LEGALNOTICE"
 ><P
 ></P
 ><A
-NAME="AEN37"
+NAME="AEN39"
 ></A
 ><P
 >This documentation is distributed under the GNU General Public License (GPL) 
@@ -125,141 +125,185 @@ HREF="#INTRODUCTION"
 ><DL
 ><DT
 >1. <A
+HREF="#INTROSMB"
+>Introduction to Samba</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="#AEN61"
+>Background</A
+></DT
+><DT
+>1.2. <A
+HREF="#AEN67"
+>Terminology</A
+></DT
+><DT
+>1.3. <A
+HREF="#AEN91"
+>Related Projects</A
+></DT
+><DT
+>1.4. <A
+HREF="#AEN100"
+>SMB Methodology</A
+></DT
+><DT
+>1.5. <A
+HREF="#AEN115"
+>Additional Resources</A
+></DT
+><DT
+>1.6. <A
+HREF="#AEN151"
+>Epilogue</A
+></DT
+><DT
+>1.7. <A
+HREF="#AEN162"
+>Miscellaneous</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
 HREF="#INSTALL"
 >How to Install and Test SAMBA</A
 ></DT
 ><DD
 ><DL
 ><DT
->1.1. <A
-HREF="#AEN65"
+>2.1. <A
+HREF="#AEN188"
 >Obtaining and installing samba</A
 ></DT
 ><DT
->1.2. <A
-HREF="#AEN71"
+>2.2. <A
+HREF="#AEN194"
 >Configuring samba</A
 ></DT
 ><DT
->1.3. <A
-HREF="#AEN107"
+>2.3. <A
+HREF="#AEN230"
 >Try listing the shares available on your 
 	server</A
 ></DT
 ><DT
->1.4. <A
-HREF="#AEN116"
+>2.4. <A
+HREF="#AEN239"
 >Try connecting with the unix client</A
 ></DT
 ><DT
->1.5. <A
-HREF="#AEN137"
+>2.5. <A
+HREF="#AEN260"
 >Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</A
 ></DT
 ><DT
->1.6. <A
-HREF="#AEN150"
+>2.6. <A
+HREF="#AEN273"
 >What If Things Don't Work?</A
 ></DT
 ></DL
 ></DD
 ><DT
->2. <A
+>3. <A
 HREF="#BROWSING-QUICK"
 >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
 ></DT
 ><DD
 ><DL
 ><DT
->2.1. <A
-HREF="#AEN183"
+>3.1. <A
+HREF="#AEN306"
 >Discussion</A
 ></DT
 ><DT
->2.2. <A
-HREF="#AEN204"
+>3.2. <A
+HREF="#AEN327"
 >How browsing functions and how to deploy stable and 
 dependable browsing using Samba</A
 ></DT
 ><DT
->2.3. <A
-HREF="#AEN218"
+>3.3. <A
+HREF="#AEN341"
 >Use of the <B
 CLASS="COMMAND"
 >Remote Announce</B
 > parameter</A
 ></DT
 ><DT
->2.4. <A
-HREF="#AEN241"
+>3.4. <A
+HREF="#AEN364"
 >Use of the <B
 CLASS="COMMAND"
 >Remote Browse Sync</B
 > parameter</A
 ></DT
 ><DT
->2.5. <A
-HREF="#AEN252"
+>3.5. <A
+HREF="#AEN375"
 >Use of WINS</A
 ></DT
 ><DT
->2.6. <A
-HREF="#AEN269"
+>3.6. <A
+HREF="#AEN401"
 >Do NOT use more than one (1) protocol on MS Windows machines</A
 ></DT
 ><DT
->2.7. <A
-HREF="#AEN277"
+>3.7. <A
+HREF="#AEN409"
 >Name Resolution Order</A
 ></DT
 ></DL
 ></DD
 ><DT
->3. <A
+>4. <A
 HREF="#PASSDB"
 >User information database</A
 ></DT
 ><DD
 ><DL
 ><DT
->3.1. <A
-HREF="#AEN335"
+>4.1. <A
+HREF="#AEN469"
 >Introduction</A
 ></DT
 ><DT
->3.2. <A
-HREF="#AEN342"
+>4.2. <A
+HREF="#AEN476"
 >Important Notes About Security</A
 ></DT
 ><DT
->3.3. <A
-HREF="#AEN380"
+>4.3. <A
+HREF="#AEN514"
 >The smbpasswd Command</A
 ></DT
 ><DT
->3.4. <A
-HREF="#AEN411"
+>4.4. <A
+HREF="#AEN545"
 >Plain text</A
 ></DT
 ><DT
->3.5. <A
-HREF="#AEN416"
+>4.5. <A
+HREF="#AEN550"
 >TDB</A
 ></DT
 ><DT
->3.6. <A
-HREF="#AEN419"
+>4.6. <A
+HREF="#AEN553"
 >LDAP</A
 ></DT
 ><DT
->3.7. <A
-HREF="#AEN637"
+>4.7. <A
+HREF="#AEN766"
 >MySQL</A
 ></DT
 ><DT
->3.8. <A
-HREF="#AEN679"
+>4.8. <A
+HREF="#AEN808"
 >XML</A
 ></DT
 ></DL
@@ -274,156 +318,151 @@ HREF="#TYPE"
 ><DD
 ><DL
 ><DT
->4. <A
+>5. <A
 HREF="#SERVERTYPE"
 >Nomenclature of Server Types</A
 ></DT
 ><DD
 ><DL
 ><DT
->4.1. <A
-HREF="#AEN717"
+>5.1. <A
+HREF="#AEN847"
 >Stand Alone Server</A
 ></DT
 ><DT
->4.2. <A
-HREF="#AEN724"
+>5.2. <A
+HREF="#AEN854"
 >Domain Member Server</A
 ></DT
 ><DT
->4.3. <A
-HREF="#AEN730"
+>5.3. <A
+HREF="#AEN860"
 >Domain Controller</A
 ></DT
 ></DL
 ></DD
 ><DT
->5. <A
+>6. <A
 HREF="#SECURITYLEVELS"
 >Samba as Stand-Alone Server</A
 ></DT
 ><DD
 ><DL
 ><DT
->5.1. <A
-HREF="#AEN766"
+>6.1. <A
+HREF="#AEN897"
 >User and Share security level</A
 ></DT
 ></DL
 ></DD
 ><DT
->6. <A
+>7. <A
 HREF="#SAMBA-PDC"
 >Samba as an NT4 or Win2k Primary Domain Controller</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.1. <A
-HREF="#AEN878"
+>7.1. <A
+HREF="#AEN1010"
 >Prerequisite Reading</A
 ></DT
 ><DT
->6.2. <A
-HREF="#AEN883"
+>7.2. <A
+HREF="#AEN1014"
 >Background</A
 ></DT
 ><DT
->6.3. <A
-HREF="#AEN923"
+>7.3. <A
+HREF="#AEN1054"
 >Configuring the Samba Domain Controller</A
 ></DT
 ><DT
->6.4. <A
-HREF="#AEN965"
+>7.4. <A
+HREF="#AEN1096"
 >Creating Machine Trust Accounts and Joining Clients to the Domain</A
 ></DT
 ><DT
->6.5. <A
-HREF="#AEN1073"
+>7.5. <A
+HREF="#AEN1212"
 >Common Problems and Errors</A
 ></DT
 ><DT
->6.6. <A
-HREF="#AEN1119"
->What other help can I get?</A
-></DT
-><DT
->6.7. <A
-HREF="#AEN1233"
+>7.6. <A
+HREF="#AEN1241"
 >Domain Control for Windows 9x/ME</A
 ></DT
 ></DL
 ></DD
 ><DT
->7. <A
+>8. <A
 HREF="#SAMBA-BDC"
 >Samba Backup Domain Controller to Samba Domain Control</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.1. <A
-HREF="#AEN1286"
+>8.1. <A
+HREF="#AEN1294"
 >Prerequisite Reading</A
 ></DT
 ><DT
->7.2. <A
-HREF="#AEN1290"
+>8.2. <A
+HREF="#AEN1298"
 >Background</A
 ></DT
 ><DT
->7.3. <A
-HREF="#AEN1298"
+>8.3. <A
+HREF="#AEN1306"
 >What qualifies a Domain Controller on the network?</A
 ></DT
 ><DT
->7.4. <A
-HREF="#AEN1307"
+>8.4. <A
+HREF="#AEN1315"
 >Can Samba be a Backup Domain Controller to an NT PDC?</A
 ></DT
 ><DT
->7.5. <A
-HREF="#AEN1312"
+>8.5. <A
+HREF="#AEN1320"
 >How do I set up a Samba BDC?</A
 ></DT
 ></DL
 ></DD
 ><DT
->8. <A
+>9. <A
 HREF="#ADS"
 >Samba as a ADS domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->8.1. <A
-HREF="#AEN1355"
+>9.1. <A
+HREF="#AEN1364"
 >Setup your <TT
 CLASS="FILENAME"
 >smb.conf</TT
 ></A
 ></DT
 ><DT
->8.2. <A
-HREF="#AEN1368"
+>9.2. <A
+HREF="#AEN1377"
 >Setup your <TT
 CLASS="FILENAME"
 >/etc/krb5.conf</TT
 ></A
 ></DT
 ><DT
->8.3. <A
+>9.3. <A
 HREF="#ADS-CREATE-MACHINE-ACCOUNT"
 >Create the computer account</A
 ></DT
 ><DT
->8.4. <A
+>9.4. <A
 HREF="#ADS-TEST-SERVER"
 >Test your server setup</A
 ></DT
 ><DT
->8.5. <A
+>9.5. <A
 HREF="#ADS-TEST-SMBCLIENT"
 >Testing with <SPAN
 CLASS="APPLICATION"
@@ -431,27 +470,27 @@ CLASS="APPLICATION"
 ></A
 ></DT
 ><DT
->8.6. <A
-HREF="#AEN1416"
+>9.6. <A
+HREF="#AEN1425"
 >Notes</A
 ></DT
 ></DL
 ></DD
 ><DT
->9. <A
-HREF="#DOMAIN-SECURITY"
+>10. <A
+HREF="#DOMAIN-MEMBER"
 >Samba as a NT4 or Win2k domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->9.1. <A
-HREF="#AEN1439"
+>10.1. <A
+HREF="#AEN1448"
 >Joining an NT Domain with Samba 3.0</A
 ></DT
 ><DT
->9.2. <A
-HREF="#AEN1493"
+>10.2. <A
+HREF="#AEN1502"
 >Why is this better than security = server?</A
 ></DT
 ></DL
@@ -466,500 +505,510 @@ HREF="#OPTIONAL"
 ><DD
 ><DL
 ><DT
->10. <A
+>11. <A
 HREF="#UNIX-PERMISSIONS"
 >UNIX Permission Bits and Windows NT Access Control Lists</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.1. <A
-HREF="#AEN1525"
+>11.1. <A
+HREF="#AEN1534"
 >Viewing and changing UNIX permissions using the NT 
 	security dialogs</A
 ></DT
 ><DT
->10.2. <A
-HREF="#AEN1531"
+>11.2. <A
+HREF="#AEN1540"
 >How to view file security on a Samba share</A
 ></DT
 ><DT
->10.3. <A
-HREF="#AEN1542"
+>11.3. <A
+HREF="#AEN1551"
 >Viewing file ownership</A
 ></DT
 ><DT
->10.4. <A
-HREF="#AEN1562"
+>11.4. <A
+HREF="#AEN1571"
 >Viewing file or directory permissions</A
 ></DT
 ><DT
->10.5. <A
-HREF="#AEN1598"
+>11.5. <A
+HREF="#AEN1607"
 >Modifying file or directory permissions</A
 ></DT
 ><DT
->10.6. <A
-HREF="#AEN1620"
+>11.6. <A
+HREF="#AEN1629"
 >Interaction with the standard Samba create mask 
 	parameters</A
 ></DT
 ><DT
->10.7. <A
-HREF="#AEN1673"
+>11.7. <A
+HREF="#AEN1682"
 >Interaction with the standard Samba file attribute 
 	mapping</A
 ></DT
 ></DL
 ></DD
 ><DT
->11. <A
+>12. <A
 HREF="#GROUPMAPPING"
 >Configuring Group Mapping</A
 ></DT
 ><DT
->12. <A
+>13. <A
 HREF="#PRINTING"
 >Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->12.1. <A
-HREF="#AEN1736"
+>13.1. <A
+HREF="#AEN1745"
 >Introduction</A
 ></DT
 ><DT
->12.2. <A
-HREF="#AEN1758"
+>13.2. <A
+HREF="#AEN1767"
 >Configuration</A
 ></DT
 ><DT
->12.3. <A
-HREF="#AEN1870"
+>13.3. <A
+HREF="#AEN1879"
 >The Imprints Toolset</A
 ></DT
 ><DT
->12.4. <A
-HREF="#AEN1913"
+>13.4. <A
+HREF="#AEN1922"
 >Diagnosis</A
 ></DT
 ></DL
 ></DD
 ><DT
->13. <A
+>14. <A
 HREF="#CUPS-PRINTING"
 >CUPS Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->13.1. <A
-HREF="#AEN2025"
+>14.1. <A
+HREF="#AEN2035"
 >Introduction</A
 ></DT
 ><DT
->13.2. <A
-HREF="#AEN2032"
+>14.2. <A
+HREF="#AEN2042"
 >Configuring <TT
 CLASS="FILENAME"
 >smb.conf</TT
 > for CUPS</A
 ></DT
 ><DT
->13.3. <A
-HREF="#AEN2052"
+>14.3. <A
+HREF="#AEN2062"
 >CUPS - RAW Print Through Mode</A
 ></DT
 ><DT
->13.4. <A
-HREF="#AEN2111"
+>14.4. <A
+HREF="#AEN2119"
 >CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients</A
 ></DT
 ><DT
->13.5. <A
-HREF="#AEN2132"
+>14.5. <A
+HREF="#AEN2140"
 >Windows Terminal Servers (WTS) as CUPS clients</A
 ></DT
 ><DT
->13.6. <A
-HREF="#AEN2136"
+>14.6. <A
+HREF="#AEN2144"
 >Setting up CUPS for driver download</A
 ></DT
 ><DT
->13.7. <A
-HREF="#AEN2149"
+>14.7. <A
+HREF="#AEN2157"
 >Sources of CUPS drivers / PPDs</A
 ></DT
 ><DT
->13.8. <A
-HREF="#AEN2205"
+>14.8. <A
+HREF="#AEN2213"
 >The CUPS Filter Chains</A
 ></DT
 ><DT
->13.9. <A
-HREF="#AEN2244"
+>14.9. <A
+HREF="#AEN2252"
 >CUPS Print Drivers and Devices</A
 ></DT
 ><DT
->13.10. <A
-HREF="#AEN2321"
+>14.10. <A
+HREF="#AEN2329"
 >Limiting the number of pages users can print</A
 ></DT
 ><DT
->13.11. <A
-HREF="#AEN2417"
+>14.11. <A
+HREF="#AEN2425"
 >Advanced Postscript Printing from MS Windows</A
 ></DT
 ><DT
->13.12. <A
-HREF="#AEN2432"
+>14.12. <A
+HREF="#AEN2440"
 >Auto-Deletion of CUPS spool files</A
 ></DT
 ></DL
 ></DD
 ><DT
->14. <A
+>15. <A
 HREF="#WINBIND"
 >Unified Logons between Windows NT and UNIX using Winbind</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.1. <A
-HREF="#AEN2506"
+>15.1. <A
+HREF="#AEN2516"
 >Abstract</A
 ></DT
 ><DT
->14.2. <A
-HREF="#AEN2510"
+>15.2. <A
+HREF="#AEN2520"
 >Introduction</A
 ></DT
 ><DT
->14.3. <A
-HREF="#AEN2523"
+>15.3. <A
+HREF="#AEN2533"
 >What Winbind Provides</A
 ></DT
 ><DT
->14.4. <A
-HREF="#AEN2534"
+>15.4. <A
+HREF="#AEN2544"
 >How Winbind Works</A
 ></DT
 ><DT
->14.5. <A
-HREF="#AEN2577"
+>15.5. <A
+HREF="#AEN2587"
 >Installation and Configuration</A
 ></DT
 ><DT
->14.6. <A
-HREF="#AEN2834"
+>15.6. <A
+HREF="#AEN2844"
 >Limitations</A
 ></DT
 ><DT
->14.7. <A
-HREF="#AEN2844"
+>15.7. <A
+HREF="#AEN2854"
 >Conclusion</A
 ></DT
 ></DL
 ></DD
 ><DT
->15. <A
+>16. <A
 HREF="#ADVANCEDNETWORKMANAGEMENT"
 >Advanced Network Manangement</A
 ></DT
 ><DD
 ><DL
 ><DT
->15.1. <A
-HREF="#AEN2859"
+>16.1. <A
+HREF="#AEN2870"
 >Configuring Samba Share Access Controls</A
 ></DT
 ><DT
->15.2. <A
-HREF="#AEN2897"
+>16.2. <A
+HREF="#AEN2908"
 >Remote Server Administration</A
 ></DT
 ><DT
->15.3. <A
-HREF="#AEN2914"
+>16.3. <A
+HREF="#AEN2925"
 >Network Logon Script Magic</A
 ></DT
 ></DL
 ></DD
 ><DT
->16. <A
+>17. <A
 HREF="#POLICYMGMT"
 >System and Account Policies</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.1. <A
-HREF="#AEN2929"
+>17.1. <A
+HREF="#AEN2959"
 >Creating and Managing System Policies</A
 ></DT
 ><DT
->16.2. <A
-HREF="#AEN3002"
+>17.2. <A
+HREF="#AEN3031"
 >Managing Account/User Policies</A
 ></DT
+><DT
+>17.3. <A
+HREF="#AEN3053"
+>System Startup and Logon Processing Overview</A
+></DT
 ></DL
 ></DD
 ><DT
->17. <A
+>18. <A
 HREF="#PROFILEMGMT"
 >Desktop Profile Management</A
 ></DT
 ><DD
 ><DL
 ><DT
->17.1. <A
-HREF="#AEN3035"
+>18.1. <A
+HREF="#AEN3096"
 >Roaming Profiles</A
 ></DT
 ><DT
->17.2. <A
-HREF="#AEN3242"
+>18.2. <A
+HREF="#AEN3303"
 >Mandatory profiles</A
 ></DT
 ><DT
->17.3. <A
-HREF="#AEN3249"
+>18.3. <A
+HREF="#AEN3310"
 >Creating/Managing Group Profiles</A
 ></DT
 ><DT
->17.4. <A
-HREF="#AEN3255"
+>18.4. <A
+HREF="#AEN3316"
 >Default Profile for Windows Users</A
 ></DT
 ></DL
 ></DD
 ><DT
->18. <A
+>19. <A
 HREF="#INTERDOMAINTRUSTS"
 >Interdomain Trust Relationships</A
 ></DT
 ><DD
 ><DL
 ><DT
->18.1. <A
-HREF="#AEN3386"
+>19.1. <A
+HREF="#AEN3447"
 >Trust Relationship Background</A
 ></DT
 ><DT
->18.2. <A
-HREF="#AEN3395"
->MS Windows NT4 Trust Configuration</A
+>19.2. <A
+HREF="#AEN3456"
+>Native MS Windows NT4 Trusts Configuration</A
 ></DT
 ><DT
->18.3. <A
-HREF="#AEN3405"
->Configuring Samba Domain Trusts</A
+>19.3. <A
+HREF="#AEN3465"
+>Configuring Samba NT-style Domain Trusts</A
 ></DT
 ></DL
 ></DD
 ><DT
->19. <A
+>20. <A
 HREF="#PAM"
 >PAM Configuration for Centrally Managed Authentication</A
 ></DT
 ><DD
 ><DL
 ><DT
->19.1. <A
-HREF="#AEN3440"
+>20.1. <A
+HREF="#AEN3508"
 >Samba and PAM</A
 ></DT
 ><DT
->19.2. <A
-HREF="#AEN3491"
+>20.2. <A
+HREF="#AEN3559"
 >Distributed Authentication</A
 ></DT
 ><DT
->19.3. <A
-HREF="#AEN3496"
+>20.3. <A
+HREF="#AEN3564"
 >PAM Configuration in smb.conf</A
 ></DT
 ></DL
 ></DD
 ><DT
->20. <A
+>21. <A
 HREF="#VFS"
 >Stackable VFS modules</A
 ></DT
 ><DD
 ><DL
 ><DT
->20.1. <A
-HREF="#AEN3531"
+>21.1. <A
+HREF="#AEN3601"
 >Introduction and configuration</A
 ></DT
 ><DT
->20.2. <A
-HREF="#AEN3540"
+>21.2. <A
+HREF="#AEN3610"
 >Included modules</A
 ></DT
 ><DT
->20.3. <A
-HREF="#AEN3598"
+>21.3. <A
+HREF="#AEN3668"
 >VFS modules available elsewhere</A
 ></DT
 ></DL
 ></DD
 ><DT
->21. <A
+>22. <A
 HREF="#MSDFS"
 >Hosting a Microsoft Distributed File System tree on Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->21.1. <A
-HREF="#AEN3626"
+>22.1. <A
+HREF="#AEN3696"
 >Instructions</A
 ></DT
 ></DL
 ></DD
 ><DT
->22. <A
+>23. <A
 HREF="#INTEGRATE-MS-NETWORKS"
 >Integrating MS Windows networks with Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->22.1. <A
-HREF="#AEN3688"
+>23.1. <A
+HREF="#AEN3759"
 >Name Resolution in a pure Unix/Linux world</A
 ></DT
 ><DT
->22.2. <A
-HREF="#AEN3751"
+>23.2. <A
+HREF="#AEN3822"
 >Name resolution as used within MS Windows networking</A
 ></DT
 ></DL
 ></DD
 ><DT
->23. <A
+>24. <A
 HREF="#IMPROVED-BROWSING"
 >Improved browsing in samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->23.1. <A
-HREF="#AEN3804"
+>24.1. <A
+HREF="#AEN3875"
 >Overview of browsing</A
 ></DT
 ><DT
->23.2. <A
-HREF="#AEN3810"
+>24.2. <A
+HREF="#AEN3881"
 >Browsing support in samba</A
 ></DT
 ><DT
->23.3. <A
-HREF="#AEN3825"
+>24.3. <A
+HREF="#AEN3896"
 >Problem resolution</A
 ></DT
 ><DT
->23.4. <A
-HREF="#AEN3837"
+>24.4. <A
+HREF="#AEN3908"
 >Browsing across subnets</A
 ></DT
 ><DT
->23.5. <A
-HREF="#AEN3878"
+>24.5. <A
+HREF="#AEN3949"
 >Setting up a WINS server</A
 ></DT
 ><DT
->23.6. <A
-HREF="#AEN3901"
+>24.6. <A
+HREF="#AEN3972"
 >Setting up Browsing in a WORKGROUP</A
 ></DT
 ><DT
->23.7. <A
-HREF="#AEN3927"
+>24.7. <A
+HREF="#AEN3998"
 >Setting up Browsing in a DOMAIN</A
 ></DT
 ><DT
->23.8. <A
+>24.8. <A
 HREF="#BROWSE-FORCE-MASTER"
 >Forcing samba to be the master</A
 ></DT
 ><DT
->23.9. <A
-HREF="#AEN3962"
+>24.9. <A
+HREF="#AEN4033"
 >Making samba the domain master</A
 ></DT
 ><DT
->23.10. <A
-HREF="#AEN3984"
+>24.10. <A
+HREF="#AEN4055"
 >Note about broadcast addresses</A
 ></DT
 ><DT
->23.11. <A
-HREF="#AEN3987"
+>24.11. <A
+HREF="#AEN4058"
 >Multiple interfaces</A
 ></DT
 ></DL
 ></DD
 ><DT
->24. <A
+>25. <A
 HREF="#SECURING-SAMBA"
 >Securing Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.1. <A
-HREF="#AEN4003"
+>25.1. <A
+HREF="#AEN4074"
 >Introduction</A
 ></DT
 ><DT
->24.2. <A
-HREF="#AEN4006"
+>25.2. <A
+HREF="#AEN4077"
 >Using host based protection</A
 ></DT
 ><DT
->24.3. <A
-HREF="#AEN4016"
+>25.3. <A
+HREF="#AEN4087"
 >Using interface protection</A
 ></DT
 ><DT
->24.4. <A
-HREF="#AEN4025"
+>25.4. <A
+HREF="#AEN4095"
 >Using a firewall</A
 ></DT
 ><DT
->24.5. <A
-HREF="#AEN4032"
+>25.5. <A
+HREF="#AEN4102"
 >Using a IPC$ share deny</A
 ></DT
 ><DT
->24.6. <A
-HREF="#AEN4041"
+>25.6. <A
+HREF="#AEN4111"
 >Upgrading Samba</A
 ></DT
 ></DL
 ></DD
 ><DT
->25. <A
+>26. <A
 HREF="#UNICODE"
 >Unicode/Charsets</A
 ></DT
 ><DD
 ><DL
 ><DT
->25.1. <A
-HREF="#AEN4056"
+>26.1. <A
+HREF="#AEN4127"
 >What are charsets and unicode?</A
 ></DT
 ><DT
->25.2. <A
-HREF="#AEN4065"
+>26.2. <A
+HREF="#AEN4136"
 >Samba and charsets</A
 ></DT
+><DT
+>26.3. <A
+HREF="#AEN4155"
+>Conversion from old names</A
+></DT
 ></DL
 ></DD
 ></DL
@@ -972,94 +1021,55 @@ HREF="#APPENDIXES"
 ><DD
 ><DL
 ><DT
->26. <A
-HREF="#SWAT"
->SWAT - The Samba Web Admininistration Tool</A
+>27. <A
+HREF="#COMPILING"
+>How to compile SAMBA</A
 ></DT
 ><DD
 ><DL
 ><DT
->26.1. <A
-HREF="#AEN4098"
->SWAT Features and Benefits</A
+>27.1. <A
+HREF="#AEN4183"
+>Access Samba source code via CVS</A
 ></DT
-></DL
-></DD
 ><DT
->27. <A
-HREF="#NT4MIGRATION"
->Migration from NT4 PDC to Samba-3 PDC</A
-></DT
-><DD
-><DL
+>27.2. <A
+HREF="#AEN4226"
+>Accessing the samba sources via rsync and ftp</A
+></DT
 ><DT
->27.1. <A
-HREF="#AEN4134"
->Planning and Getting Started</A
+>27.3. <A
+HREF="#AEN4232"
+>Verifying Samba's PGP signature</A
 ></DT
 ><DT
->27.2. <A
-HREF="#AEN4143"
->Managing Samba-3 Domain Control</A
+>27.4. <A
+HREF="#AEN4244"
+>Building the Binaries</A
+></DT
+><DT
+>27.5. <A
+HREF="#AEN4301"
+>Starting the smbd and nmbd</A
 ></DT
 ></DL
 ></DD
 ><DT
 >28. <A
-HREF="#SPEED"
->Samba performance issues</A
+HREF="#NT4MIGRATION"
+>Migration from NT4 PDC to Samba-3 PDC</A
 ></DT
 ><DD
 ><DL
 ><DT
 >28.1. <A
-HREF="#AEN4163"
->Comparisons</A
+HREF="#AEN4375"
+>Planning and Getting Started</A
 ></DT
 ><DT
 >28.2. <A
-HREF="#AEN4169"
->Socket options</A
-></DT
-><DT
->28.3. <A
-HREF="#AEN4176"
->Read size</A
-></DT
-><DT
->28.4. <A
-HREF="#AEN4181"
->Max xmit</A
-></DT
-><DT
->28.5. <A
-HREF="#AEN4186"
->Log level</A
-></DT
-><DT
->28.6. <A
-HREF="#AEN4189"
->Read raw</A
-></DT
-><DT
->28.7. <A
-HREF="#AEN4194"
->Write raw</A
-></DT
-><DT
->28.8. <A
-HREF="#AEN4198"
->Slow Clients</A
-></DT
-><DT
->28.9. <A
-HREF="#AEN4202"
->Slow Logins</A
-></DT
-><DT
->28.10. <A
-HREF="#AEN4205"
->Client tuning</A
+HREF="#AEN4408"
+>Managing Samba-3 Domain Control</A
 ></DT
 ></DL
 ></DD
@@ -1072,29 +1082,34 @@ HREF="#PORTABILITY"
 ><DL
 ><DT
 >29.1. <A
-HREF="#AEN4249"
+HREF="#AEN4423"
 >HPUX</A
 ></DT
 ><DT
 >29.2. <A
-HREF="#AEN4255"
+HREF="#AEN4429"
 >SCO Unix</A
 ></DT
 ><DT
 >29.3. <A
-HREF="#AEN4259"
+HREF="#AEN4433"
 >DNIX</A
 ></DT
 ><DT
 >29.4. <A
-HREF="#AEN4288"
+HREF="#AEN4462"
 >RedHat Linux Rembrandt-II</A
 ></DT
 ><DT
 >29.5. <A
-HREF="#AEN4294"
+HREF="#AEN4468"
 >AIX</A
 ></DT
+><DT
+>29.6. <A
+HREF="#AEN4474"
+>Solaris</A
+></DT
 ></DL
 ></DD
 ><DT
@@ -1106,101 +1121,106 @@ HREF="#OTHER-CLIENTS"
 ><DL
 ><DT
 >30.1. <A
-HREF="#AEN4319"
+HREF="#AEN4501"
 >Macintosh clients?</A
 ></DT
 ><DT
 >30.2. <A
-HREF="#AEN4328"
+HREF="#AEN4510"
 >OS2 Client</A
 ></DT
 ><DT
 >30.3. <A
-HREF="#AEN4368"
+HREF="#AEN4550"
 >Windows for Workgroups</A
 ></DT
 ><DT
 >30.4. <A
-HREF="#AEN4392"
+HREF="#AEN4574"
 >Windows '95/'98</A
 ></DT
 ><DT
 >30.5. <A
-HREF="#AEN4408"
+HREF="#AEN4590"
 >Windows 2000 Service Pack 2</A
 ></DT
 ><DT
 >30.6. <A
-HREF="#AEN4425"
+HREF="#AEN4607"
 >Windows NT 3.1</A
 ></DT
 ></DL
 ></DD
 ><DT
 >31. <A
-HREF="#COMPILING"
->How to compile SAMBA</A
+HREF="#SWAT"
+>SWAT - The Samba Web Admininistration Tool</A
 ></DT
 ><DD
 ><DL
 ><DT
 >31.1. <A
-HREF="#AEN4446"
->Access Samba source code via CVS</A
-></DT
-><DT
->31.2. <A
-HREF="#AEN4489"
->Accessing the samba sources via rsync and ftp</A
-></DT
-><DT
->31.3. <A
-HREF="#AEN4495"
->Building the Binaries</A
-></DT
-><DT
->31.4. <A
-HREF="#AEN4552"
->Starting the smbd and nmbd</A
+HREF="#AEN4624"
+>SWAT Features and Benefits</A
 ></DT
 ></DL
 ></DD
 ><DT
 >32. <A
-HREF="#BUGREPORT"
->Reporting Bugs</A
+HREF="#SPEED"
+>Samba performance issues</A
 ></DT
 ><DD
 ><DL
 ><DT
 >32.1. <A
-HREF="#AEN4627"
->Introduction</A
+HREF="#AEN4666"
+>Comparisons</A
 ></DT
 ><DT
 >32.2. <A
-HREF="#AEN4637"
->General info</A
+HREF="#AEN4672"
+>Socket options</A
 ></DT
 ><DT
 >32.3. <A
-HREF="#AEN4643"
->Debug levels</A
+HREF="#AEN4679"
+>Read size</A
 ></DT
 ><DT
 >32.4. <A
-HREF="#AEN4664"
->Internal errors</A
+HREF="#AEN4684"
+>Max xmit</A
 ></DT
 ><DT
 >32.5. <A
-HREF="#AEN4678"
->Attaching to a running process</A
+HREF="#AEN4689"
+>Log level</A
 ></DT
 ><DT
 >32.6. <A
-HREF="#AEN4686"
->Patches</A
+HREF="#AEN4692"
+>Read raw</A
+></DT
+><DT
+>32.7. <A
+HREF="#AEN4697"
+>Write raw</A
+></DT
+><DT
+>32.8. <A
+HREF="#AEN4701"
+>Slow Clients</A
+></DT
+><DT
+>32.9. <A
+HREF="#AEN4705"
+>Slow Logins</A
+></DT
+><DT
+>32.10. <A
+HREF="#AEN4708"
+>Client tuning</A
 ></DT
 ></DL
 ></DD
@@ -1213,1048 +1233,886 @@ HREF="#DIAGNOSIS"
 ><DL
 ><DT
 >33.1. <A
-HREF="#AEN4709"
+HREF="#AEN4760"
 >Introduction</A
 ></DT
 ><DT
 >33.2. <A
-HREF="#AEN4714"
+HREF="#AEN4765"
 >Assumptions</A
 ></DT
 ><DT
 >33.3. <A
-HREF="#AEN4733"
+HREF="#AEN4784"
 >The tests</A
 ></DT
 ><DT
 >33.4. <A
-HREF="#AEN4900"
+HREF="#AEN4951"
 >Still having troubles?</A
 ></DT
 ></DL
 ></DD
-></DL
-></DD
-></DL
-></DIV
-><DIV
-CLASS="PART"
-><A
-NAME="INTRODUCTION"
-></A
-><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="TITLE"
->I. General installation</H1
-><DIV
-CLASS="PARTINTRO"
-><A
-NAME="AEN42"
-></A
-><H1
->Introduction</H1
-><P
->This part contains general info on how to install samba 
-and how to configure the parts of samba you will most likely need.
-PLEASE read this.</P
-></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1. <A
-HREF="#INSTALL"
->How to Install and Test SAMBA</A
-></DT
-><DD
-><DL
-><DT
->1.1. <A
-HREF="#AEN65"
->Obtaining and installing samba</A
-></DT
 ><DT
->1.2. <A
-HREF="#AEN71"
->Configuring samba</A
+>34. <A
+HREF="#PROBLEMS"
+>Analysing and solving samba problems</A
 ></DT
 ><DD
 ><DL
 ><DT
->1.2.1. <A
-HREF="#AEN76"
->Editing the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file</A
-></DT
-><DT
->1.2.2. <A
-HREF="#AEN101"
->SWAT</A
-></DT
-></DL
-></DD
-><DT
->1.3. <A
-HREF="#AEN107"
->Try listing the shares available on your 
-	server</A
-></DT
-><DT
->1.4. <A
-HREF="#AEN116"
->Try connecting with the unix client</A
+>34.1. <A
+HREF="#AEN4983"
+>Diagnostics tools</A
 ></DT
 ><DT
->1.5. <A
-HREF="#AEN137"
->Try connecting from a DOS, WfWg, Win9x, WinNT, 
-	Win2k, OS/2, etc... client</A
+>34.2. <A
+HREF="#AEN4998"
+>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
 ></DT
 ><DT
->1.6. <A
-HREF="#AEN150"
->What If Things Don't Work?</A
+>34.3. <A
+HREF="#AEN5027"
+>Useful URL's</A
 ></DT
-><DD
-><DL
 ><DT
->1.6.1. <A
-HREF="#AEN156"
->Scope IDs</A
+>34.4. <A
+HREF="#AEN5051"
+>Getting help from the mailing lists</A
 ></DT
 ><DT
->1.6.2. <A
-HREF="#AEN159"
->Locking</A
+>34.5. <A
+HREF="#AEN5081"
+>How to get off the mailinglists</A
 ></DT
 ></DL
 ></DD
-></DL
-></DD
 ><DT
->2. <A
-HREF="#BROWSING-QUICK"
->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
+>35. <A
+HREF="#BUGREPORT"
+>Reporting Bugs</A
 ></DT
 ><DD
 ><DL
 ><DT
->2.1. <A
-HREF="#AEN183"
->Discussion</A
-></DT
-><DT
->2.2. <A
-HREF="#AEN204"
->How browsing functions and how to deploy stable and 
-dependable browsing using Samba</A
+>35.1. <A
+HREF="#AEN5104"
+>Introduction</A
 ></DT
 ><DT
->2.3. <A
-HREF="#AEN218"
->Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
+>35.2. <A
+HREF="#AEN5114"
+>General info</A
 ></DT
 ><DT
->2.4. <A
-HREF="#AEN241"
->Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
+>35.3. <A
+HREF="#AEN5120"
+>Debug levels</A
 ></DT
 ><DT
->2.5. <A
-HREF="#AEN252"
->Use of WINS</A
+>35.4. <A
+HREF="#AEN5141"
+>Internal errors</A
 ></DT
 ><DT
->2.6. <A
-HREF="#AEN269"
->Do NOT use more than one (1) protocol on MS Windows machines</A
+>35.5. <A
+HREF="#AEN5155"
+>Attaching to a running process</A
 ></DT
 ><DT
->2.7. <A
-HREF="#AEN277"
->Name Resolution Order</A
+>35.6. <A
+HREF="#AEN5163"
+>Patches</A
 ></DT
 ></DL
 ></DD
-><DT
->3. <A
-HREF="#PASSDB"
->User information database</A
-></DT
-><DD
-><DL
-><DT
->3.1. <A
-HREF="#AEN335"
->Introduction</A
-></DT
-><DT
->3.2. <A
-HREF="#AEN342"
->Important Notes About Security</A
-></DT
-><DD
-><DL
-><DT
->3.2.1. <A
-HREF="#AEN368"
->Advantages of SMB Encryption</A
-></DT
-><DT
->3.2.2. <A
-HREF="#AEN374"
->Advantages of non-encrypted passwords</A
-></DT
-></DL
-></DD
-><DT
->3.3. <A
-HREF="#AEN380"
->The smbpasswd Command</A
-></DT
-><DT
->3.4. <A
-HREF="#AEN411"
->Plain text</A
-></DT
-><DT
->3.5. <A
-HREF="#AEN416"
->TDB</A
-></DT
-><DT
->3.6. <A
-HREF="#AEN419"
->LDAP</A
-></DT
-><DD
-><DL
-><DT
->3.6.1. <A
-HREF="#AEN421"
->Introduction</A
-></DT
-><DT
->3.6.2. <A
-HREF="#AEN441"
->Introduction</A
-></DT
-><DT
->3.6.3. <A
-HREF="#AEN470"
->Supported LDAP Servers</A
-></DT
-><DT
->3.6.4. <A
-HREF="#AEN475"
->Schema and Relationship to the RFC 2307 posixAccount</A
-></DT
-><DT
->3.6.5. <A
-HREF="#AEN487"
->Configuring Samba with LDAP</A
-></DT
-><DT
->3.6.6. <A
-HREF="#AEN534"
->Accounts and Groups management</A
-></DT
-><DT
->3.6.7. <A
-HREF="#AEN539"
->Security and sambaAccount</A
-></DT
-><DT
->3.6.8. <A
-HREF="#AEN559"
->LDAP specials attributes for sambaAccounts</A
-></DT
-><DT
->3.6.9. <A
-HREF="#AEN629"
->Example LDIF Entries for a sambaAccount</A
-></DT
-></DL
-></DD
-><DT
->3.7. <A
-HREF="#AEN637"
->MySQL</A
-></DT
-><DD
-><DL
-><DT
->3.7.1. <A
-HREF="#AEN639"
->Creating the database</A
-></DT
-><DT
->3.7.2. <A
-HREF="#AEN649"
->Configuring</A
-></DT
-><DT
->3.7.3. <A
-HREF="#AEN666"
->Using plaintext passwords or encrypted password</A
-></DT
-><DT
->3.7.4. <A
-HREF="#AEN671"
->Getting non-column data from the table</A
-></DT
-></DL
-></DD
-><DT
->3.8. <A
-HREF="#AEN679"
->XML</A
-></DT
 ></DL
 ></DD
 ></DL
 ></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="INTRODUCTION"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>I. General installation</H1
+></DIV
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN44"
+></A
+><H1
+>Introduction</H1
+><P
+>This part contains general info on how to install samba 
+and how to configure the parts of samba you will most likely need.
+PLEASE read this.</P
 ></DIV
 ><DIV
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="INSTALL"
+NAME="INTROSMB"
 ></A
->Chapter 1. How to Install and Test SAMBA</H1
+>Chapter 1. Introduction to Samba</H1
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>"If you understand what you're doing, you're not learning anything." 
+-- Anonymous</I
+></SPAN
+></P
+><P
+>Samba is a file and print server for Windows-based clients using TCP/IP as the underlying
+transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
+strengths is that you can use it to blend your mix of Windows and Linux machines together
+without requiring a separate Windows NT/2000/2003 Server.  Samba is actively being developed
+by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.</P
 ><DIV
 CLASS="SECT1"
-><H2
+><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN65"
->1.1. Obtaining and installing samba</A
+NAME="AEN61"
+>1.1. Background</A
 ></H2
 ><P
->Binary packages of samba are included in almost any Linux or 
-	Unix distribution. There are also some packages available at 
-	<A
-HREF="http://samba.org/"
-TARGET="_top"
->the samba homepage</A
->.
-	</P
+>Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed
+Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was
+originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only
+ran over UDP. When there was a need to run it over TCP so that it would be compatible
+with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became
+known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to
+license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the
+concept continued in the form of SMB (Server Message Block, or the "what") using the
+NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can
+run SMB (i.e., transport) over several different protocols; many different implementations
+arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT
+(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form
+of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing
+term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445
+only. As of yet, direct-hosted TCP has yet to catch on.</P
+><P
+>Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
+Common Insecurities Fail Scrutiny:</P
 ><P
->If you need to compile samba from source, check the 
-	<A
-HREF="#COMPILING"
->appropriate appendix chapter</A
->.</P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
+stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
+been dutifully waded through during the information-gathering stages of this project, and there
+are *still* many missing pieces... While often tedious, at least the way has been generously
+littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
+thinking?</I
+></SPAN
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN71"
->1.2. Configuring samba</A
+NAME="AEN67"
+>1.2. Terminology</A
 ></H2
 ><P
->Samba's configuration is stored in the smb.conf file, 
-	that usually resides in <TT
-CLASS="FILENAME"
->/etc/samba/smb.conf</TT
-> 
-	or <TT
-CLASS="FILENAME"
->/usr/local/samba/lib/smb.conf</TT
->. You can either 
-	edit this file yourself or do it using one of the many graphical 
-	tools that are available, such as the web-based interface swat, that 
-	is included with samba.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN76"
->1.2.1. Editing the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file</A
-></H3
-><P
->There are sample configuration files in the examples 
-	subdirectory in the distribution. I suggest you read them 
-	carefully so you can see how the options go together in 
-	practice. See the man page for all the options.</P
+></P
+><UL
+><LI
 ><P
->The simplest useful configuration file would be 
-	something like this:</P
+>	SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.
+	</P
+></LI
+><LI
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
-	workgroup = MYGROUP
-
-[homes]
-	guest ok = no
-	read only = no
-	</PRE
-></P
+>	CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently
+	decided that SMB needed the word "Internet" in it, so they changed it to CIFS.  
+	</P
+></LI
+><LI
 ><P
->which would allow connections by anyone with an 
-	account on the server, using either their login name or 
-	"<B
-CLASS="COMMAND"
->homes</B
->" as the service name. (Note that I also set the 
-	workgroup that Samba is part of. See BROWSING.txt for details)</P
+>	Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp
+	only using DNS for name resolution instead of WINS.
+	</P
+></LI
+><LI
 ><P
->Make sure you put the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file in the same place 
-	you specified in the<TT
-CLASS="FILENAME"
->Makefile</TT
-> (the default is to 
-	look for it in <TT
-CLASS="FILENAME"
->/usr/local/samba/lib/</TT
->).</P
+>	IPC: Acronym for "Inter-Process Communication". A method to communicate specific
+	information between programs.
+	</P
+></LI
+><LI
 ><P
->For more information about security settings for the 
-	<B
-CLASS="COMMAND"
->[homes]</B
-> share please refer to the chapter 
-	<A
-HREF="#SECURING-SAMBA"
->Securing Samba</A
->.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN92"
->1.2.1.1. Test your config file with 
-	<B
-CLASS="COMMAND"
->testparm</B
-></A
-></H4
+>	Marshalling: - A method of serializing (i.e., sequential ordering of) variable data
+	suitable for transmission via a network connection or storing in a file. The source
+	data can be re-created using a similar process called unmarshalling.
+	</P
+></LI
+><LI
 ><P
->It's important that you test the validity of your
-	<TT
-CLASS="FILENAME"
->smb.conf</TT
-> file using the <SPAN
-CLASS="APPLICATION"
->testparm</SPAN
-> program. 
-	If testparm runs OK then it will list the loaded services. If 
-	not it will give an error message.</P
+>	NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol;
+	it is a method of communication across an existing protocol. This is a standard which
+	was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit,
+	it can help to think of this in comparison your computer's BIOS -- it controls the
+	essential functions of your input/output hardware -- whereas NetBIOS controls the
+	essential functions of your input/output traffic via the network. Again, this is a bit
+	of an exaggeration but it should help that paradigm shift. What is important to realize
+	is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
+	brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second
+	thought; this will cause no end (and no doubt) of confusion.
+	</P
+></LI
+><LI
 ><P
->Make sure it runs OK and that the services look 
-	reasonable before proceeding. </P
+>	NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI
+	is a protocol, not a standard. It is also not routable, so traffic on one side of a
+	router will be unable to communicate with the other side. Understanding NetBEUI is
+	not essential to deciphering SMB; however it helps to point out that it is not the
+	same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally
+	referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver".
+	It is not often heard from these days.
+	</P
+></LI
+><LI
 ><P
->Always run testparm again when you change 
-	<TT
-CLASS="FILENAME"
->smb.conf</TT
->!</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN101"
->1.2.2. SWAT</A
-></H3
+>	NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use
+	of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made 
+	to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports.
+	This is how file and printer sharing are accomplished in Windows 95/98/ME. They 
+	traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137, 
+	NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service 
+	(nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, 
+	and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 
+	(Detailed specifications).
+	</P
+></LI
+><LI
 ><P
->	SWAT is a web-based interface that helps you configure samba. 
-	SWAT might not be available in the samba package on your platform, 
-	but in a seperate package. Please read the swat manpage 
-	on compiling, installing and configuring swat from source.
+>	W2K: Acronym for Windows 2000 Professional or Server
 	</P
+></LI
+><LI
 ><P
->To launch SWAT just run your favorite web browser and 
-	point it at "http://localhost:901/". Replace <VAR
-CLASS="REPLACEABLE"
->localhost</VAR
-> with the name of the computer you are running samba on if you 
-	are running samba on a different computer then your browser.</P
+>	W3K: Acronym for Windows 2003 Server
+	</P
+></LI
+></UL
 ><P
->Note that you can attach to SWAT from any IP connected 
-	machine but connecting from a remote machine leaves your 
-	connection open to password sniffing as passwords will be sent 
-	in the clear over the wire. </P
-></DIV
+>If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at 
+http://www.samba.org).  Optionally, you could just search mailing.unix.samba at http://groups.google.com</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN107"
->1.3. Try listing the shares available on your 
-	server</A
+NAME="AEN91"
+>1.3. Related Projects</A
 ></H2
 ><P
-><SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->smbclient -L 
-	<VAR
-CLASS="REPLACEABLE"
->yourhostname</VAR
-></KBD
+>Currently, there are two projects that are directly related to Samba: SMBFS and CIFS network
+client file systems for Linux, both available in the Linux kernel itself.</P
+><P
 ></P
+><UL
+><LI
 ><P
->You should get back a list of shares available on 
-	your server. If you don't then something is incorrectly setup. 
-	Note that this method can also be used to see what shares 
-	are available on other LanManager clients (such as WfWg).</P
+>	SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
+	that Microsoft Windows and OS/2 Lan Manager use to share files and printers 
+	over local networks) and access them just like any other Unix directory. This is useful 
+	if you just want to mount such filesystems without being a SMBFS server.
+	</P
+></LI
+><LI
 ><P
->If you choose user level security then you may find 
-	that Samba requests a password before it will list the shares. 
-	See the <B
-CLASS="COMMAND"
->smbclient</B
-> man page for details. (you 
-	can force it to list the shares without a password by
-	adding the option -U% to the command line. This will not work 
-	with non-Samba servers)</P
+>	CIFS (Common Internet File System) is the successor to SMB, and is actively being worked
+	on in the upcoming version of the Linux kernel. The intent of this module is to 
+	provide advanced network file system functionality including support for dfs (heirarchical 
+	name space), secure per-user session establishment, safe distributed caching (oplock), 
+	optional packet signing, Unicode and other internationalization improvements, and optional 
+	Winbind (nsswitch) integration.
+	</P
+></LI
+></UL
+><P
+>Again, it's important to note that these are implementations for client filesystems, and have
+nothing to do with acting as a file and print server for SMB/CIFS clients.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN116"
->1.4. Try connecting with the unix client</A
+NAME="AEN100"
+>1.4. SMB Methodology</A
 ></H2
 ><P
-><SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->smbclient <VAR
-CLASS="REPLACEABLE"
->	//yourhostname/aservice</VAR
-></KBD
+>Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns),
+UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS
+session service, or netbios-ssn). Anyone looking at their network with a good
+packet sniffer will be amazed at the amount of traffic generated by just opening
+up a single file. In general, SMB sessions are established in the following order:</P
+><P
 ></P
+><UL
+><LI
 ><P
->Typically the <VAR
-CLASS="REPLACEABLE"
->yourhostname</VAR
-> 
-	would be the name of the host where you installed <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
->. 
-	The <VAR
-CLASS="REPLACEABLE"
->aservice</VAR
-> is 
-	any service you have defined in the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-	file. Try your user name if you just have a <B
-CLASS="COMMAND"
->[homes]</B
->
-	section
-	in <TT
-CLASS="FILENAME"
->smb.conf</TT
->.</P
+>	"TCP Connection" - establish 3-way handshake (connection) to port 139/tcp
+    or 445/tcp.
+	</P
+></LI
+><LI
 ><P
->For example if your unix host is <VAR
-CLASS="REPLACEABLE"
->bambi</VAR
->
-	and your login name is <VAR
-CLASS="REPLACEABLE"
->fred</VAR
-> you would type:</P
+>	"NetBIOS Session Request" - using the following "Calling Names": The local
+    machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS
+    name plus the 16th character 0x20
+	</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->smbclient //<VAR
-CLASS="REPLACEABLE"
->bambi</VAR
->/<VAR
-CLASS="REPLACEABLE"
->fred</VAR
->
-	</KBD
-></P
+>	"SMB Negotiate Protocol" - determine the protocol dialect to use, which will
+    be one of the following: PC Network Program 1.0 (Core) - share level security
+    mode only; Microsoft Networks 1.03 (Core Plus) - share level security
+    mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response
+    Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
+    Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
+    Authentication
+	</P
+></LI
+><LI
+><P
+>	SMB Session Startup. Passwords are encrypted (or not) according to one of
+    the following methods: Null (no encryption); Cleartext (no encryption); LM
+    and NTLM; NTLM; NTLMv2
+	</P
+></LI
+><LI
+><P
+>	SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
+    to a service type (e.g., IPC$ named pipe)
+	</P
+></LI
+></UL
+><P
+>A good way to examine this process in depth is to try out SecurityFriday's SWB program
+at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html.  It allows you to
+walk through the establishment of a SMB/CIFS session step by step.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN137"
->1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
-	Win2k, OS/2, etc... client</A
+NAME="AEN115"
+>1.5. Additional Resources</A
 ></H2
 ><P
->Try mounting disks. eg:</P
-><P
-><SAMP
-CLASS="PROMPT"
->C:\WINDOWS\&#62; </SAMP
-><KBD
-CLASS="USERINPUT"
->net use d: \\servername\service
-	</KBD
 ></P
+><UL
+><LI
 ><P
->Try printing. eg:</P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>CIFS: Common Insecurities Fail Scrutiny</I
+></SPAN
+> by "Hobbit", 
+	http://hr.uoregon.edu/davidrl/cifs.txt
+	</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->C:\WINDOWS\&#62; </SAMP
-><KBD
-CLASS="USERINPUT"
->net use lpt1:
-	\\servername\spoolservice</KBD
-></P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Doing the Samba on Windows</I
+></SPAN
+> by Financial Review,
+	http://afr.com/it/2002/10/01/FFXDF43AP6D.html
+	</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->C:\WINDOWS\&#62; </SAMP
-><KBD
-CLASS="USERINPUT"
->print filename
-	</KBD
-></P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Implementing CIFS</I
+></SPAN
+> by Christopher R. Hertel,
+	http://ubiqx.org/cifs/
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Just What Is SMB?</I
+></SPAN
+> by Richard Sharpe,
+	http://samba.anu.edu.au/cifs/docs/what-is-smb.html
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Opening Windows Everywhere</I
+></SPAN
+> by Mike Warfield,
+	http://www.linux-mag.com/1999-05/samba_01.html
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>SMB HOWTO</I
+></SPAN
+> by David Wood,
+	http://www.tldp.org/HOWTO/SMB-HOWTO.html
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>SMB/CIFS by The Root</I
+></SPAN
+> by "ledin",
+	http://www.phrack.org/phrack/60/p60-0x0b.txt
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>The Story of Samba</I
+></SPAN
+> by Christopher R. Hertel,
+	http://www.linux-mag.com/1999-09/samba_01.html
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>The Unofficial Samba HOWTO</I
+></SPAN
+> by David Lechnyr,
+	http://hr.uoregon.edu/davidrl/samba/
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Understanding the Network Neighborhood</I
+></SPAN
+> by Christopher R. Hertel,
+	http://www.linux-mag.com/2001-05/smb_01.html
+	</P
+></LI
+><LI
+><P
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Using Samba as a PDC</I
+></SPAN
+> by Andrew Bartlett,
+	http://www.linux-mag.com/2002-02/samba_01.html
+	</P
+></LI
+></UL
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN150"
->1.6. What If Things Don't Work?</A
+NAME="AEN151"
+>1.6. Epilogue</A
 ></H2
 ><P
->Then you might read the file chapter 
-	<A
-HREF="#DIAGNOSIS"
->Diagnosis</A
-> and the 
-	FAQ. If you are still stuck then try the mailing list or 
-	newsgroup (look in the README for details). Samba has been 
-	successfully installed at thousands of sites worldwide, so maybe 
-	someone else has hit your problem and has overcome it. You could 
-	also use the WWW site to scan back issues of the samba-digest.</P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>"What's fundamentally wrong is that nobody ever had any taste when they
+did it. Microsoft has been very much into making the user interface look good,
+but internally it's just a complete mess. And even people who program for Microsoft
+and who have had years of experience, just don't know how it works internally.
+Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
+mess that fixing one bug might just break a hundred programs that depend on
+that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
+in making money. They don't have anybody who takes pride in Windows 95 as an
+operating system.</I
+></SPAN
+></P
 ><P
->When you fix the problem <SPAN
+><SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->please</I
+>People inside Microsoft know it's a bad operating system and they still
+continue obviously working on it because they want to get the next version out
+because they want to have all these new features to sell more copies of the
+system.</I
 ></SPAN
-> send some 
-	updates of the documentation (or source code) to one of 
-	the documentation maintainers or the list.
-	</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN156"
->1.6.1. Scope IDs</A
-></H3
+></P
 ><P
->By default Samba uses a blank scope ID. This means 
-		all your windows boxes must also have a blank scope ID. 
-		If you really want to use a non-blank scope ID then you will 
-		need to use the 'netbios scope' smb.conf option.
-        All your PCs will need to have the same setting for 
-		this to work. I do not recommend scope IDs.</P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>The problem with that is that over time, when you have this kind of approach,
+and because nobody understands it, because nobody REALLY fixes bugs (other than
+when they're really obvious), the end result is really messy. You can't trust
+it because under certain circumstances it just spontaneously reboots or just
+halts in the middle of something that shouldn't be strange. Normally it works
+fine and then once in a blue moon for some completely unknown reason, it's dead,
+and nobody knows why. Not Microsoft, not the experienced user and certainly
+not the completely clueless user who probably sits there shivering thinking
+"What did I do wrong?" when they didn't do anything wrong at all.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>That's what's really irritating to me."</I
+></SPAN
+></P
+><P
+>-- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998
+(http://hr.uoregon.edu/davidrl/boot.txt)</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN159"
->1.6.2. Locking</A
-></H3
-><P
->One area which sometimes causes trouble is locking.</P
+NAME="AEN162"
+>1.7. Miscellaneous</A
+></H2
 ><P
->There are two types of locking which need to be 
-		performed by a SMB server. The first is "record locking" 
-		which allows a client to lock a range of bytes in a open file. 
-		The second is the "deny modes" that are specified when a file 
-		is open.</P
+>This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0,
+in case anyone asks.</P
 ><P
->Record locking semantics under Unix is very
-		different from record locking under Windows. Versions
-		of Samba before 2.2 have tried to use the native
-		fcntl() unix system call to implement proper record
-		locking between different Samba clients. This can not
-		be fully correct due to several reasons. The simplest
-		is the fact that a Windows client is allowed to lock a
-		byte range up to 2^32 or 2^64, depending on the client
-		OS. The unix locking only supports byte ranges up to
-		2^31. So it is not possible to correctly satisfy a
-		lock request above 2^31. There are many more
-		differences, too many to be listed here.</P
-><P
->Samba 2.2 and above implements record locking
-		completely independent of the underlying unix
-		system. If a byte range lock that the client requests
-		happens to fall into the range 0-2^31, Samba hands
-		this request down to the Unix system. All other locks
-		can not be seen by unix anyway.</P
-><P
->Strictly a SMB server should check for locks before 
-		every read and write call on a file. Unfortunately with the 
-		way fcntl() works this can be slow and may overstress the 
-		rpc.lockd. It is also almost always unnecessary as clients 
-		are supposed to independently make locking calls before reads 
-		and writes anyway if locking is important to them. By default 
-		Samba only makes locking calls when explicitly asked
-		to by a client, but if you set "strict locking = yes" then it will
-		make lock checking calls on every read and write. </P
-><P
->You can also disable by range locking completely 
-		using "locking = no". This is useful for those shares that 
-		don't support locking or don't need it (such as cdroms). In 
-		this case Samba fakes the return codes of locking calls to 
-		tell clients that everything is OK.</P
-><P
->The second class of locking is the "deny modes". These 
-		are set by an application when it opens a file to determine 
-		what types of access should be allowed simultaneously with 
-		its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE 
-		or DENY_ALL. There are also special compatibility modes called 
-		DENY_FCB and  DENY_DOS.</P
-></DIV
+>This chapter is Copyright © 2003 David Lechnyr (david at lechnyr dot com).
+Permission is granted to copy, distribute and/or modify this document under the terms
+of the GNU Free Documentation License, Version 1.2 or any later version published by the Free
+Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.</P
 ></DIV
 ></DIV
 ><DIV
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="BROWSING-QUICK"
+NAME="INSTALL"
 ></A
->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
-and / or across workgroups (or domains). WINS is the best tool for resolution
-of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling
-except by way of name to address mapping.</P
+>Chapter 2. How to Install and Test SAMBA</H1
 ><DIV
-CLASS="NOTE"
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN188"
+>2.1. Obtaining and installing samba</A
+></H2
 ><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"
+>Binary packages of samba are included in almost any Linux or 
+	Unix distribution. There are also some packages available at 
+	<A
+HREF="http://samba.org/"
+TARGET="_top"
+>the samba homepage</A
+>.
+	</P
 ><P
->MS Windows 2000 and later can be configured to operate with NO NetBIOS 
-over TCP/IP. Samba-3 and later also supports this mode of operation.</P
-></TD
-></TR
-></TABLE
+>If you need to compile samba from source, check the 
+	<A
+HREF="#COMPILING"
+>appropriate appendix chapter</A
+>.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN183"
->2.1. Discussion</A
+NAME="AEN194"
+>2.2. Configuring samba</A
 ></H2
 ><P
->Firstly, all MS Windows networking is based on SMB (Server Message
-Block) based messaging. SMB messaging may be implemented using NetBIOS or 
-without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
-MS Windows products can do likewise. NetBIOS based networking uses broadcast
-messaging to affect browse list management. When running NetBIOS over
-TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.</P
-><P
->Normally, only unicast UDP messaging can be forwarded by routers. The
-<B
-CLASS="COMMAND"
->remote announce</B
->
-parameter to smb.conf helps to project browse announcements
-to remote network segments via unicast UDP. Similarly, the 
-<B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter of <TT
+>Samba's configuration is stored in the smb.conf file, 
+	that usually resides in <TT
+CLASS="FILENAME"
+>/etc/samba/smb.conf</TT
+> 
+	or <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf</TT
+>. You can either 
+	edit this file yourself or do it using one of the many graphical 
+	tools that are available, such as the web-based interface swat, that 
+	is included with samba.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN199"
+>2.2.1. Editing the <TT
 CLASS="FILENAME"
 >smb.conf</TT
->
-implements browse list collation using unicast UDP.</P
+> file</A
+></H3
 ><P
->Secondly, in those networks where Samba is the only SMB server technology
-wherever possible <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> should be configured on one (1) machine as the WINS
-server. This makes it easy to manage the browsing environment. If each network
-segment is configured with it's own Samba WINS server, then the only way to
-get cross segment browsing to work is by using the 
-<B
-CLASS="COMMAND"
->remote announce</B
-> and the <B
+>There are sample configuration files in the examples 
+	subdirectory in the distribution. I suggest you read them 
+	carefully so you can see how the options go together in 
+	practice. See the man page for all the options.</P
+><P
+>The simplest useful configuration file would be 
+	something like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+	workgroup = MYGROUP
+
+[homes]
+	guest ok = no
+	read only = no
+	</PRE
+></P
+><P
+>which would allow connections by anyone with an 
+	account on the server, using either their login name or 
+	"<B
 CLASS="COMMAND"
->remote browse sync</B
->
-parameters to your <TT
+>homes</B
+>" as the service name. (Note that I also set the 
+	workgroup that Samba is part of. See BROWSING.txt for details)</P
+><P
+>Make sure you put the <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> file.</P
+> file in the same place 
+	you specified in the<TT
+CLASS="FILENAME"
+>Makefile</TT
+> (the default is to 
+	look for it in <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/</TT
+>).</P
 ><P
->If only one WINS server is used for an entire multi-segment network then
-the use of the <B
+>For more information about security settings for the 
+	<B
 CLASS="COMMAND"
->remote announce</B
-> and the 
-<B
+>[homes]</B
+> share please refer to the chapter 
+	<A
+HREF="#SECURING-SAMBA"
+>Securing Samba</A
+>.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN215"
+>2.2.1.1. Test your config file with 
+	<B
 CLASS="COMMAND"
->remote browse sync</B
-> parameters should NOT be necessary.</P
-><P
->As of Samba 3 WINS replication is being worked on. The bulk of the code has
-been committed, but it still needs maturation.</P
+>testparm</B
+></A
+></H4
 ><P
->Right now samba WINS does not support MS-WINS replication. This means that
-when setting up Samba as a WINS server there must only be one <SPAN
+>It's important that you test the validity of your
+	<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file using the <SPAN
 CLASS="APPLICATION"
->nmbd</SPAN
-> configured
-as a WINS server on the network. Some sites have used multiple Samba WINS
-servers for redundancy (one server per subnet) and then used 
-<B
-CLASS="COMMAND"
->remote browse sync</B
-> and <B
-CLASS="COMMAND"
->remote announce</B
->
-to affect browse list collation across all
-segments. Note that this means clients will only resolve local names,
-and must be configured to use DNS to resolve names on other subnets in
-order to resolve the IP addresses of the servers they can see on other
-subnets. This setup is not recommended, but is mentioned as a practical
-consideration (ie: an 'if all else fails' scenario).</P
+>testparm</SPAN
+> program. 
+	If testparm runs OK then it will list the loaded services. If 
+	not it will give an error message.</P
 ><P
->Lastly, take note that browse lists are a collection of unreliable broadcast
-messages that are repeated at intervals of not more than 15 minutes. This means
-that it will take time to establish a browse list and it can take up to 45
-minutes to stabilise, particularly across network segments.</P
+>Make sure it runs OK and that the services look 
+	reasonable before proceeding. </P
+><P
+>Always run testparm again when you change 
+	<TT
+CLASS="FILENAME"
+>smb.conf</TT
+>!</P
+></DIV
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN204"
->2.2. How browsing functions and how to deploy stable and 
-dependable browsing using Samba</A
-></H2
-><P
->As stated above, MS Windows machines register their NetBIOS names 
-(i.e.: the machine name for each service type in operation) on start 
-up. Also, as stated above, the exact method by which this name registration 
-takes place is determined by whether or not the MS Windows client/server 
-has been given a WINS server address, whether or not LMHOSTS lookup 
-is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN224"
+>2.2.2. SWAT</A
+></H3
 ><P
->In the case where there is no WINS server all name registrations as 
-well as name lookups are done by UDP broadcast. This isolates name 
-resolution to the local subnet, unless LMHOSTS is used to list all 
-names and IP addresses. In such situations Samba provides a means by 
-which the samba server name may be forcibly injected into the browse 
-list of a remote MS Windows network (using the 
-<B
-CLASS="COMMAND"
->remote announce</B
-> parameter).</P
+>	SWAT is a web-based interface that helps you configure samba. 
+	SWAT might not be available in the samba package on your platform, 
+	but in a seperate package. Please read the swat manpage 
+	on compiling, installing and configuring swat from source.
+	</P
 ><P
->Where a WINS server is used, the MS Windows client will use UDP 
-unicast to register with the WINS server. Such packets can be routed 
-and thus WINS allows name resolution to function across routed networks.</P
+>To launch SWAT just run your favorite web browser and 
+	point it at "http://localhost:901/". Replace <VAR
+CLASS="REPLACEABLE"
+>localhost</VAR
+> with the name of the computer you are running samba on if you 
+	are running samba on a different computer then your browser.</P
 ><P
->During the startup process an election will take place to create a 
-local master browser if one does not already exist. On each NetBIOS network 
-one machine will be elected to function as the domain master browser. This 
-domain browsing has nothing to do with MS security domain control. 
-Instead, the domain master browser serves the role of contacting each local 
-master browser (found by asking WINS or from LMHOSTS) and exchanging browse 
-list contents. This way every master browser will eventually obtain a complete 
-list of all machines that are on the network. Every 11-15 minutes an election 
-is held to determine which machine will be the master browser. By the nature of 
-the election criteria used, the machine with the highest uptime, or the 
-most senior protocol version, or other criteria, will win the election 
-as domain master browser.</P
+>Note that you can attach to SWAT from any IP connected 
+	machine but connecting from a remote machine leaves your 
+	connection open to password sniffing as passwords will be sent 
+	in the clear over the wire. </P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN230"
+>2.3. Try listing the shares available on your 
+	server</A
+></H2
 ><P
->Clients wishing to browse the network make use of this list, but also depend 
-on the availability of correct name resolution to the respective IP 
-address/addresses. </P
+><SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
+CLASS="USERINPUT"
+>smbclient -L 
+	<VAR
+CLASS="REPLACEABLE"
+>yourhostname</VAR
+></KBD
+></P
 ><P
->Any configuration that breaks name resolution and/or browsing intrinsics 
-will annoy users because they will have to put up with protracted 
-inability to use the network services.</P
+>You should get back a list of shares available on 
+	your server. If you don't then something is incorrectly setup. 
+	Note that this method can also be used to see what shares 
+	are available on other LanManager clients (such as WfWg).</P
 ><P
->Samba supports a feature that allows forced synchonisation 
-of browse lists across routed networks using the <B
-CLASS="COMMAND"
->remote 
-browse sync</B
-> parameter in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file. 
-This causes Samba to contact the local master browser on a remote network and 
-to request browse list synchronisation. This effectively bridges 
-two networks that are separated by routers. The two remote 
-networks may use either broadcast based name resolution or WINS 
-based name resolution, but it should be noted that the <B
+>If you choose user level security then you may find 
+	that Samba requests a password before it will list the shares. 
+	See the <B
 CLASS="COMMAND"
->remote 
-browse sync</B
-> parameter provides browse list synchronisation - and 
-that is distinct from name to address resolution, in other 
-words, for cross subnet browsing to function correctly it is 
-essential that a name to address resolution mechanism be provided. 
-This mechanism could be via DNS, <TT
-CLASS="FILENAME"
->/etc/hosts</TT
->, 
-and so on.</P
+>smbclient</B
+> man page for details. (you 
+	can force it to list the shares without a password by
+	adding the option -U% to the command line. This will not work 
+	with non-Samba servers)</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN218"
->2.3. Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
+NAME="AEN239"
+>2.4. Try connecting with the unix client</A
 ></H2
 ><P
->The <B
-CLASS="COMMAND"
->remote announce</B
-> parameter of 
-<TT
+><SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
+CLASS="USERINPUT"
+>smbclient <VAR
+CLASS="REPLACEABLE"
+>	//yourhostname/aservice</VAR
+></KBD
+></P
+><P
+>Typically the <VAR
+CLASS="REPLACEABLE"
+>yourhostname</VAR
+> 
+	would be the name of the host where you installed <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+>. 
+	The <VAR
+CLASS="REPLACEABLE"
+>aservice</VAR
+> is 
+	any service you have defined in the <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> can be used to forcibly ensure
-that all the NetBIOS names on a network get announced to a remote network.
-The syntax of the <B
+>
+	file. Try your user name if you just have a <B
 CLASS="COMMAND"
->remote announce</B
-> parameter is:
-<PRE
-CLASS="PROGRAMLISTING"
->	remote announce = <VAR
-CLASS="REPLACEABLE"
->a.b.c.d [e.f.g.h]</VAR
-> ...</PRE
+>[homes]</B
 >
-_or_
-<PRE
-CLASS="PROGRAMLISTING"
->	remote announce = <VAR
+	section
+	in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.</P
+><P
+>For example if your unix host is <VAR
 CLASS="REPLACEABLE"
->a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR
-> ...</PRE
+>bambi</VAR
 >
-
-where:
-<P
-></P
-><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
-><VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-> and 
-<VAR
+	and your login name is <VAR
 CLASS="REPLACEABLE"
->e.f.g.h</VAR
-></DT
-><DD
+>fred</VAR
+> you would type:</P
 ><P
->is either the LMB (Local Master Browser) IP address
-or the broadcst address of the remote network.
-ie: the LMB is at 192.168.1.10, or the address
-could be given as 192.168.1.255 where the netmask
-is assumed to be 24 bits (255.255.255.0).
-When the remote announcement is made to the broadcast
-address of the remote network every host will receive
-our announcements. This is noisy and therefore
-undesirable but may be necessary if we do NOT know
-the IP address of the remote LMB.</P
-></DD
-><DT
-><VAR
+><SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
+CLASS="USERINPUT"
+>smbclient //<VAR
 CLASS="REPLACEABLE"
->WORKGROUP</VAR
-></DT
-><DD
-><P
->is optional and can be either our own workgroup
-or that of the remote network. If you use the
-workgroup name of the remote network then our
-NetBIOS machine names will end up looking like
-they belong to that workgroup, this may cause
-name resolution problems and should be avoided.</P
-></DD
-></DL
-></DIV
+>bambi</VAR
+>/<VAR
+CLASS="REPLACEABLE"
+>fred</VAR
+>
+	</KBD
 ></P
 ></DIV
 ><DIV
@@ -2262,112 +2120,160 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN241"
->2.4. Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
+NAME="AEN260"
+>2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
+	Win2k, OS/2, etc... client</A
 ></H2
 ><P
->The <B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter of 
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> is used to announce to
-another LMB that it must synchronise it's NetBIOS name list with our
-Samba LMB. It works ONLY if the Samba server that has this option is
-simultaneously the LMB on it's network segment.</P
+>Try mounting disks. eg:</P
 ><P
->The syntax of the <B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter is:
-
-<PRE
-CLASS="PROGRAMLISTING"
->remote browse sync = <VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-></PRE
->
-
-where <VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P
+><SAMP
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </SAMP
+><KBD
+CLASS="USERINPUT"
+>net use d: \\servername\service
+	</KBD
+></P
+><P
+>Try printing. eg:</P
+><P
+><SAMP
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </SAMP
+><KBD
+CLASS="USERINPUT"
+>net use lpt1:
+	\\servername\spoolservice</KBD
+></P
+><P
+><SAMP
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </SAMP
+><KBD
+CLASS="USERINPUT"
+>print filename
+	</KBD
+></P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN252"
->2.5. Use of WINS</A
+NAME="AEN273"
+>2.6. What If Things Don't Work?</A
 ></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
-name_type value for each of of several types of service it has available.
-eg: It registers it's name directly as a unique (the type 0x03) name.
-It also registers it's name if it is running the lanmanager compatible
-server service (used to make shares and printers available to other users)
-by registering the server (the type 0x20) name.</P
+>Then you might read the file chapter 
+	<A
+HREF="#DIAGNOSIS"
+>Diagnosis</A
+> and the 
+	FAQ. If you are still stuck then try to follow 
+	the <A
+HREF="#PROBLEMS"
+>Analysing and Solving Problems chapter</A
+>
+	Samba has been successfully installed at thousands of sites worldwide,
+	so maybe someone else has hit your problem and has overcome it. </P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN278"
+>2.6.1. Scope IDs</A
+></H3
 ><P
->All NetBIOS names are up to 15 characters in length. The name_type variable
-is added to the end of the name - thus creating a 16 character name. Any
-name that is shorter than 15 characters is padded with spaces to the 15th
-character. ie: All NetBIOS names are 16 characters long (including the
-name_type information).</P
+>By default Samba uses a blank scope ID. This means 
+		all your windows boxes must also have a blank scope ID. 
+		If you really want to use a non-blank scope ID then you will 
+		need to use the 'netbios scope' smb.conf option.
+        All your PCs will need to have the same setting for 
+		this to work. I do not recommend scope IDs.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN281"
+>2.6.2. Locking</A
+></H3
 ><P
->WINS can store these 16 character names as they get registered. A client
-that wants to log onto the network can ask the WINS server for a list
-of all names that have registered the NetLogon service name_type. This saves
-broadcast traffic and greatly expedites logon processing. Since broadcast
-name resolution can not be used across network segments this type of
-information can only be provided via WINS _or_ via statically configured
-<TT
-CLASS="FILENAME"
->lmhosts</TT
-> files that must reside on all clients in the
-absence of WINS.</P
+>One area which sometimes causes trouble is locking.</P
 ><P
->WINS also serves the purpose of forcing browse list synchronisation by all
-LMB's. LMB's must synchronise their browse list with the DMB (domain master
-browser) and WINS helps the LMB to identify it's DMB. By definition this
-will work only within a single workgroup. Note that the domain master browser
-has NOTHING to do with what is referred to as an MS Windows NT Domain. The
-later is a reference to a security environment while the DMB refers to the
-master controller for browse list information only.</P
+>There are two types of locking which need to be 
+		performed by a SMB server. The first is "record locking" 
+		which allows a client to lock a range of bytes in a open file. 
+		The second is the "deny modes" that are specified when a file 
+		is open.</P
 ><P
->Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
-has been configured to use the WINS server/s. Any client that has not been
-configured to use the WINS server will continue to use only broadcast based
-name registration so that WINS may NEVER get to know about it. In any case,
-machines that have not registered with a WINS server will fail name to address
-lookup attempts by other clients and will therefore cause workstation access
-errors.</P
+>Record locking semantics under Unix is very
+		different from record locking under Windows. Versions
+		of Samba before 2.2 have tried to use the native
+		fcntl() unix system call to implement proper record
+		locking between different Samba clients. This can not
+		be fully correct due to several reasons. The simplest
+		is the fact that a Windows client is allowed to lock a
+		byte range up to 2^32 or 2^64, depending on the client
+		OS. The unix locking only supports byte ranges up to
+		2^31. So it is not possible to correctly satisfy a
+		lock request above 2^31. There are many more
+		differences, too many to be listed here.</P
 ><P
->To configure Samba as a WINS server just add 
-<B
-CLASS="COMMAND"
->wins support = yes</B
-> to the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-file [globals] section.</P
+>Samba 2.2 and above implements record locking
+		completely independent of the underlying unix
+		system. If a byte range lock that the client requests
+		happens to fall into the range 0-2^31, Samba hands
+		this request down to the Unix system. All other locks
+		can not be seen by unix anyway.</P
 ><P
->To configure Samba to register with a WINS server just add
-"wins server = a.b.c.d" to your smb.conf file [globals] section.</P
+>Strictly a SMB server should check for locks before 
+		every read and write call on a file. Unfortunately with the 
+		way fcntl() works this can be slow and may overstress the 
+		rpc.lockd. It is also almost always unnecessary as clients 
+		are supposed to independently make locking calls before reads 
+		and writes anyway if locking is important to them. By default 
+		Samba only makes locking calls when explicitly asked
+		to by a client, but if you set "strict locking = yes" then it will
+		make lock checking calls on every read and write. </P
+><P
+>You can also disable by range locking completely 
+		using "locking = no". This is useful for those shares that 
+		don't support locking or don't need it (such as cdroms). In 
+		this case Samba fakes the return codes of locking calls to 
+		tell clients that everything is OK.</P
+><P
+>The second class of locking is the "deny modes". These 
+		are set by an application when it opens a file to determine 
+		what types of access should be allowed simultaneously with 
+		its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE 
+		or DENY_ALL. There are also special compatibility modes called 
+		DENY_FCB and  DENY_DOS.</P
+></DIV
+></DIV
+></DIV
 ><DIV
-CLASS="IMPORTANT"
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="BROWSING-QUICK"
+></A
+>Chapter 3. 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
+and / or across workgroups (or domains). WINS is the best tool for resolution
+of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling
+except by way of name to address mapping.</P
+><DIV
+CLASS="NOTE"
 ><P
 ></P
 ><TABLE
-CLASS="IMPORTANT"
+CLASS="NOTE"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -2376,240 +2282,388 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/important.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
-ALT="Important"></TD
+ALT="Note"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->Never use both <B
-CLASS="COMMAND"
->wins support = yes</B
-> together
-with <B
-CLASS="COMMAND"
->wins server = a.b.c.d</B
->
-particularly not using it's own IP address.
-Specifying both will cause <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> to refuse to start!</P
+>MS Windows 2000 and later can be configured to operate with NO NetBIOS 
+over TCP/IP. Samba-3 and later also supports this mode of operation.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
-></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN269"
->2.6. Do NOT use more than one (1) protocol on MS Windows machines</A
+NAME="AEN306"
+>3.1. Discussion</A
 ></H2
 ><P
->A very common cause of browsing problems results from installing more than
-one protocol on an MS Windows machine.</P
+>Firstly, all MS Windows networking is based on SMB (Server Message
+Block) based messaging. SMB messaging may be implemented using NetBIOS or 
+without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
+MS Windows products can do likewise. NetBIOS based networking uses broadcast
+messaging to affect browse list management. When running NetBIOS over
+TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.</P
 ><P
->Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
-every 15 minutes. A set of election criteria is used to determine the order
-of precidence for winning this election process. A machine running Samba or
-Windows NT will be biased so that the most suitable machine will predictably
-win and thus retain it's role.</P
+>Normally, only unicast UDP messaging can be forwarded by routers. The
+<B
+CLASS="COMMAND"
+>remote announce</B
+>
+parameter to smb.conf helps to project browse announcements
+to remote network segments via unicast UDP. Similarly, the 
+<B
+CLASS="COMMAND"
+>remote browse sync</B
+> parameter of <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+implements browse list collation using unicast UDP.</P
 ><P
->The election process is "fought out" so to speak over every NetBIOS network
-interface. In the case of a Windows 9x machine that has both TCP/IP and IPX
-installed and has NetBIOS enabled over both protocols the election will be
-decided over both protocols. As often happens, if the Windows 9x machine is
-the only one with both protocols then the LMB may be won on the NetBIOS
-interface over the IPX protocol. Samba will then lose the LMB role as Windows
-9x will insist it knows who the LMB is. Samba will then cease to function
-as an LMB and thus browse list operation on all TCP/IP only machines will
-fail.</P
+>Secondly, in those networks where Samba is the only SMB server technology
+wherever possible <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> should be configured on one (1) machine as the WINS
+server. This makes it easy to manage the browsing environment. If each network
+segment is configured with it's own Samba WINS server, then the only way to
+get cross segment browsing to work is by using the 
+<B
+CLASS="COMMAND"
+>remote announce</B
+> and the <B
+CLASS="COMMAND"
+>remote browse sync</B
+>
+parameters to your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.</P
 ><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
-The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
-referred to as the WinNT family, but it should be recognised that 2000 and
-XP/2003 introduce new protocol extensions that cause them to behave 
-differently from MS Windows NT4. Generally, where a server does NOT support
-the newer or extended protocol, these will fall back to the NT4 protocols.</I
-></SPAN
-></P
+>If only one WINS server is used for an entire multi-segment network then
+the use of the <B
+CLASS="COMMAND"
+>remote announce</B
+> and the 
+<B
+CLASS="COMMAND"
+>remote browse sync</B
+> parameters should NOT be necessary.</P
 ><P
->The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!</P
+>As of Samba 3 WINS replication is being worked on. The bulk of the code has
+been committed, but it still needs maturation.</P
+><P
+>Right now samba WINS does not support MS-WINS replication. This means that
+when setting up Samba as a WINS server there must only be one <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> configured
+as a WINS server on the network. Some sites have used multiple Samba WINS
+servers for redundancy (one server per subnet) and then used 
+<B
+CLASS="COMMAND"
+>remote browse sync</B
+> and <B
+CLASS="COMMAND"
+>remote announce</B
+>
+to affect browse list collation across all
+segments. Note that this means clients will only resolve local names,
+and must be configured to use DNS to resolve names on other subnets in
+order to resolve the IP addresses of the servers they can see on other
+subnets. This setup is not recommended, but is mentioned as a practical
+consideration (ie: an 'if all else fails' scenario).</P
+><P
+>Lastly, take note that browse lists are a collection of unreliable broadcast
+messages that are repeated at intervals of not more than 15 minutes. This means
+that it will take time to establish a browse list and it can take up to 45
+minutes to stabilise, particularly across network segments.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN277"
->2.7. Name Resolution Order</A
+NAME="AEN327"
+>3.2. How browsing functions and how to deploy stable and 
+dependable browsing using Samba</A
 ></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
+>As stated above, MS Windows machines register their NetBIOS names 
+(i.e.: the machine name for each service type in operation) on start 
+up. Also, as stated above, the exact method by which this name registration 
+takes place is determined by whether or not the MS Windows client/server 
+has been given a WINS server address, whether or not LMHOSTS lookup 
+is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
 ><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->WINS: the best tool!</TD
-></TR
-><TR
-><TD
->LMHOSTS: is static and hard to maintain.</TD
-></TR
-><TR
-><TD
->Broadcast: uses UDP and can not resolve names across remote segments.</TD
-></TR
-></TBODY
-></TABLE
+>In the case where there is no WINS server all name registrations as 
+well as name lookups are done by UDP broadcast. This isolates name 
+resolution to the local subnet, unless LMHOSTS is used to list all 
+names and IP addresses. In such situations Samba provides a means by 
+which the samba server name may be forcibly injected into the browse 
+list of a remote MS Windows network (using the 
+<B
+CLASS="COMMAND"
+>remote announce</B
+> parameter).</P
 ><P
-></P
+>Where a WINS server is used, the MS Windows client will use UDP 
+unicast to register with the WINS server. Such packets can be routed 
+and thus WINS allows name resolution to function across routed networks.</P
 ><P
->Alternative means of name resolution includes:</P
+>During the startup process an election will take place to create a 
+local master browser if one does not already exist. On each NetBIOS network 
+one machine will be elected to function as the domain master browser. This 
+domain browsing has nothing to do with MS security domain control. 
+Instead, the domain master browser serves the role of contacting each local 
+master browser (found by asking WINS or from LMHOSTS) and exchanging browse 
+list contents. This way every master browser will eventually obtain a complete 
+list of all machines that are on the network. Every 11-15 minutes an election 
+is held to determine which machine will be the master browser. By the nature of 
+the election criteria used, the machine with the highest uptime, or the 
+most senior protocol version, or other criteria, will win the election 
+as domain master browser.</P
 ><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->/etc/hosts: is static, hard to maintain, and lacks name_type info</TD
-></TR
-><TR
-><TD
->DNS: is a good choice but lacks essential name_type info.</TD
-></TR
-></TBODY
-></TABLE
+>Clients wishing to browse the network make use of this list, but also depend 
+on the availability of correct name resolution to the respective IP 
+address/addresses. </P
 ><P
-></P
+>Any configuration that breaks name resolution and/or browsing intrinsics 
+will annoy users because they will have to put up with protracted 
+inability to use the network services.</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:
+>Samba supports a feature that allows forced synchonisation 
+of browse lists across routed networks using the <B
+CLASS="COMMAND"
+>remote 
+browse sync</B
+> parameter in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. 
+This causes Samba to contact the local master browser on a remote network and 
+to request browse list synchronisation. This effectively bridges 
+two networks that are separated by routers. The two remote 
+networks may use either broadcast based name resolution or WINS 
+based name resolution, but it should be noted that the <B
+CLASS="COMMAND"
+>remote 
+browse sync</B
+> parameter provides browse list synchronisation - and 
+that is distinct from name to address resolution, in other 
+words, for cross subnet browsing to function correctly it is 
+essential that a name to address resolution mechanism be provided. 
+This mechanism could be via DNS, <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+>, 
+and so on.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN341"
+>3.3. Use of the <B
+CLASS="COMMAND"
+>Remote Announce</B
+> parameter</A
+></H2
+><P
+>The <B
+CLASS="COMMAND"
+>remote announce</B
+> parameter of 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> can be used to forcibly ensure
+that all the NetBIOS names on a network get announced to a remote network.
+The syntax of the <B
+CLASS="COMMAND"
+>remote announce</B
+> parameter is:
 <PRE
 CLASS="PROGRAMLISTING"
->name resolve order = wins lmhosts bcast host</PRE
+>	remote announce = <VAR
+CLASS="REPLACEABLE"
+>a.b.c.d [e.f.g.h]</VAR
+> ...</PRE
 >
 _or_
 <PRE
 CLASS="PROGRAMLISTING"
->name resolve order = wins lmhosts  	(eliminates bcast and host)</PRE
+>	remote announce = <VAR
+CLASS="REPLACEABLE"
+>a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR
+> ...</PRE
 >
-The default is:
-<PRE
-CLASS="PROGRAMLISTING"
->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
-controlled by <TT
-CLASS="FILENAME"
->/etc/host.conf</TT
->, <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> and <TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
->.</P
+
+where:
+<P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><VAR
+CLASS="REPLACEABLE"
+>a.b.c.d</VAR
+> and 
+<VAR
+CLASS="REPLACEABLE"
+>e.f.g.h</VAR
+></DT
+><DD
+><P
+>is either the LMB (Local Master Browser) IP address
+or the broadcst address of the remote network.
+ie: the LMB is at 192.168.1.10, or the address
+could be given as 192.168.1.255 where the netmask
+is assumed to be 24 bits (255.255.255.0).
+When the remote announcement is made to the broadcast
+address of the remote network every host will receive
+our announcements. This is noisy and therefore
+undesirable but may be necessary if we do NOT know
+the IP address of the remote LMB.</P
+></DD
+><DT
+><VAR
+CLASS="REPLACEABLE"
+>WORKGROUP</VAR
+></DT
+><DD
+><P
+>is optional and can be either our own workgroup
+or that of the remote network. If you use the
+workgroup name of the remote network then our
+NetBIOS machine names will end up looking like
+they belong to that workgroup, this may cause
+name resolution problems and should be avoided.</P
+></DD
+></DL
 ></DIV
+></P
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="PASSDB"
-></A
->Chapter 3. User information database</H1
-><DIV
 CLASS="SECT1"
-><H2
+><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN335"
->3.1. Introduction</A
+NAME="AEN364"
+>3.4. Use of the <B
+CLASS="COMMAND"
+>Remote Browse Sync</B
+> parameter</A
 ></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 (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
-><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. </P
+>The <B
+CLASS="COMMAND"
+>remote browse sync</B
+> parameter of 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> is used to announce to
+another LMB that it must synchronise it's NetBIOS name list with our
+Samba LMB. It works ONLY if the Samba server that has this option is
+simultaneously the LMB on it's network segment.</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
+>The syntax of the <B
 CLASS="COMMAND"
->passdb backend = </B
-> parameter.
-	</P
+>remote browse sync</B
+> parameter is:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>remote browse sync = <VAR
+CLASS="REPLACEABLE"
+>a.b.c.d</VAR
+></PRE
+>
+
+where <VAR
+CLASS="REPLACEABLE"
+>a.b.c.d</VAR
+> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN342"
->3.2. Important Notes About Security</A
+NAME="AEN375"
+>3.5. Use of WINS</A
 ></H2
 ><P
->The unix and SMB password encryption techniques seem similar 
-	on the surface. This similarity is, however, only skin deep. The unix 
-	scheme typically sends clear text passwords over the network when 
-	logging in. This is bad. The SMB encryption scheme never sends the 
-	cleartext password over the network but it does store the 16 byte 
-	hashed values on disk. This is also bad. Why? Because the 16 byte hashed 
-	values are a "password equivalent". You cannot derive the user's 
-	password from them, but they could potentially be used in a modified 
-	client to gain access to a server. This would require considerable 
-	technical knowledge on behalf of the attacker but is perfectly possible. 
-	You should thus treat the data stored in whatever 
-	passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the 
-	cleartext passwords of all your users. Its contents must be kept 
-	secret, and the file should be protected accordingly.</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
+name_type value for each of of several types of service it has available.
+eg: It registers it's name directly as a unique (the type 0x03) name.
+It also registers it's name if it is running the lanmanager compatible
+server service (used to make shares and printers available to other users)
+by registering the server (the type 0x20) name.</P
 ><P
->Ideally we would like a password scheme which neither requires 
-	plain text passwords on the net or on disk. Unfortunately this 
-	is not available as Samba is stuck with being compatible with 
-	other SMB systems (WinNT, WfWg, Win95 etc). </P
+>All NetBIOS names are up to 15 characters in length. The name_type variable
+is added to the end of the name - thus creating a 16 character name. Any
+name that is shorter than 15 characters is padded with spaces to the 15th
+character. ie: All NetBIOS names are 16 characters long (including the
+name_type information).</P
+><P
+>WINS can store these 16 character names as they get registered. A client
+that wants to log onto the network can ask the WINS server for a list
+of all names that have registered the NetLogon service name_type. This saves
+broadcast traffic and greatly expedites logon processing. Since broadcast
+name resolution can not be used across network segments this type of
+information can only be provided via WINS _or_ via statically configured
+<TT
+CLASS="FILENAME"
+>lmhosts</TT
+> files that must reside on all clients in the
+absence of WINS.</P
+><P
+>WINS also serves the purpose of forcing browse list synchronisation by all
+LMB's. LMB's must synchronise their browse list with the DMB (domain master
+browser) and WINS helps the LMB to identify it's DMB. By definition this
+will work only within a single workgroup. Note that the domain master browser
+has NOTHING to do with what is referred to as an MS Windows NT Domain. The
+later is a reference to a security environment while the DMB refers to the
+master controller for browse list information only.</P
+><P
+>Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
+has been configured to use the WINS server/s. Any client that has not been
+configured to use the WINS server will continue to use only broadcast based
+name registration so that WINS may NEVER get to know about it. In any case,
+machines that have not registered with a WINS server will fail name to address
+lookup attempts by other clients and will therefore cause workstation access
+errors.</P
+><P
+>To configure Samba as a WINS server just add 
+<B
+CLASS="COMMAND"
+>wins support = yes</B
+> to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+file [globals] section.</P
+><P
+>To configure Samba to register with a WINS server just add
+"wins server = a.b.c.d" to your smb.conf file [globals] section.</P
 ><DIV
-CLASS="WARNING"
+CLASS="IMPORTANT"
 ><P
 ></P
 ><TABLE
-CLASS="WARNING"
+CLASS="IMPORTANT"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -2618,33 +2672,122 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/important.gif"
 HSPACE="5"
-ALT="Warning"></TD
+ALT="Important"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->Note that Windows NT 4.0 Service pack 3 changed the 
-		default for permissible authentication so that plaintext 
-		passwords are <SPAN
+>Never use both <B
+CLASS="COMMAND"
+>wins support = yes</B
+> together
+with <B
+CLASS="COMMAND"
+>wins server = a.b.c.d</B
+>
+particularly not using it's own IP address.
+Specifying both will cause <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> to refuse to start!</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN392"
+>3.5.1. WINS Replication</A
+></H3
+><P
+>Samba-3 permits WINS replication through the use of the <TT
+CLASS="FILENAME"
+>wrepld</TT
+> utility.
+This tool is not currently capable of being used as it is still in active development.
+As soon as this tool becomes moderately functional we will prepare man pages and enhance this
+section of the documentation to provide usage and technical details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN396"
+>3.5.2. Static WINS Entries</A
+></H3
+><P
+>New to Samba-3 is a tool called <TT
+CLASS="FILENAME"
+>winsedit</TT
+> that may be used to add
+static WINS entries to the WINS database. This tool can be used also to modify entries
+existing in the WINS database.</P
+><P
+>The development of the winsedit tool was made necessary due to the migration
+of the older style wins.dat file into a new tdb binary backend data store.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN401"
+>3.6. Do NOT use more than one (1) protocol on MS Windows machines</A
+></H2
+><P
+>A very common cause of browsing problems results from installing more than
+one protocol on an MS Windows machine.</P
+><P
+>Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
+every 15 minutes. A set of election criteria is used to determine the order
+of precidence for winning this election process. A machine running Samba or
+Windows NT will be biased so that the most suitable machine will predictably
+win and thus retain it's role.</P
+><P
+>The election process is "fought out" so to speak over every NetBIOS network
+interface. In the case of a Windows 9x machine that has both TCP/IP and IPX
+installed and has NetBIOS enabled over both protocols the election will be
+decided over both protocols. As often happens, if the Windows 9x machine is
+the only one with both protocols then the LMB may be won on the NetBIOS
+interface over the IPX protocol. Samba will then lose the LMB role as Windows
+9x will insist it knows who the LMB is. Samba will then cease to function
+as an LMB and thus browse list operation on all TCP/IP only machines will
+fail.</P
+><P
+><SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->never</I
+>Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
+The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
+referred to as the WinNT family, but it should be recognised that 2000 and
+XP/2003 introduce new protocol extensions that cause them to behave 
+differently from MS Windows NT4. Generally, where a server does NOT support
+the newer or extended protocol, these will fall back to the NT4 protocols.</I
 ></SPAN
-> sent over the wire. 
-		The solution to this is either to switch to encrypted passwords 
-		with Samba or edit the Windows NT registry to re-enable plaintext 
-		passwords. See the document WinNT.txt for details on how to do 
-		this.</P
+></P
 ><P
->Other Microsoft operating systems which also exhibit 
-		this behavior includes</P
+>The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN409"
+>3.7. Name Resolution Order</A
+></H2
 ><P
-> These versions of MS Windows do not support full domain
-		security protocols, although they may log onto a domain environment.
-		Of these Only MS Windows XP Home does NOT support domain logons.</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
 ><P
 ></P
 ><TABLE
@@ -2652,33 +2795,22 @@ BORDER="0"
 ><TBODY
 ><TR
 ><TD
->MS DOS Network client 3.0 with 
-			the basic network redirector installed</TD
-></TR
-><TR
-><TD
->Windows 95 with the network redirector 
-			update installed</TD
-></TR
-><TR
-><TD
->Windows 98 [se]</TD
+>WINS: the best tool!</TD
 ></TR
 ><TR
 ><TD
->Windows Me</TD
+>LMHOSTS: is static and hard to maintain.</TD
 ></TR
 ><TR
 ><TD
->Windows XP Home</TD
+>Broadcast: uses UDP and can not resolve names across remote segments.</TD
 ></TR
 ></TBODY
 ></TABLE
 ><P
 ></P
 ><P
-> The following versions of MS Windows fully support domain
-		security protocols.</P
+>Alternative means of name resolution includes:</P
 ><P
 ></P
 ><TABLE
@@ -2686,11 +2818,211 @@ BORDER="0"
 ><TBODY
 ><TR
 ><TD
->Windows NT 3.5x</TD
+>/etc/hosts: is static, hard to maintain, and lacks name_type info</TD
 ></TR
 ><TR
 ><TD
->Windows NT 4.0</TD
+>DNS: is a good choice but lacks essential name_type info.</TD
+></TR
+></TBODY
+></TABLE
+><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
+>
+_or_
+<PRE
+CLASS="PROGRAMLISTING"
+>name resolve order = wins lmhosts  	(eliminates bcast and host)</PRE
+>
+The default is:
+<PRE
+CLASS="PROGRAMLISTING"
+>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
+controlled by <TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+>, <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> and <TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+>.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PASSDB"
+></A
+>Chapter 4. User information database</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN469"
+>4.1. Introduction</A
+></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 (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
+><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. </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.
+	</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN476"
+>4.2. Important Notes About Security</A
+></H2
+><P
+>The unix and SMB password encryption techniques seem similar 
+	on the surface. This similarity is, however, only skin deep. The unix 
+	scheme typically sends clear text passwords over the network when 
+	logging in. This is bad. The SMB encryption scheme never sends the 
+	cleartext password over the network but it does store the 16 byte 
+	hashed values on disk. This is also bad. Why? Because the 16 byte hashed 
+	values are a "password equivalent". You cannot derive the user's 
+	password from them, but they could potentially be used in a modified 
+	client to gain access to a server. This would require considerable 
+	technical knowledge on behalf of the attacker but is perfectly possible. 
+	You should thus treat the data stored in whatever 
+	passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the 
+	cleartext passwords of all your users. Its contents must be kept 
+	secret, and the file should be protected accordingly.</P
+><P
+>Ideally we would like a password scheme which neither requires 
+	plain text passwords on the net or on disk. Unfortunately this 
+	is not available as Samba is stuck with being compatible with 
+	other SMB systems (WinNT, WfWg, Win95 etc). </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
+>Note that Windows NT 4.0 Service pack 3 changed the 
+		default for permissible authentication so that plaintext 
+		passwords are <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>never</I
+></SPAN
+> sent over the wire. 
+		The solution to this is either to switch to encrypted passwords 
+		with Samba or edit the Windows NT registry to re-enable plaintext 
+		passwords. See the document WinNT.txt for details on how to do 
+		this.</P
+><P
+>Other Microsoft operating systems which also exhibit 
+		this behavior includes</P
+><P
+> These versions of MS Windows do not support full domain
+		security protocols, although they may log onto a domain environment.
+		Of these Only MS Windows XP Home does NOT support domain logons.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>MS DOS Network client 3.0 with 
+			the basic network redirector installed</TD
+></TR
+><TR
+><TD
+>Windows 95 with the network redirector 
+			update installed</TD
+></TR
+><TR
+><TD
+>Windows 98 [se]</TD
+></TR
+><TR
+><TD
+>Windows Me</TD
+></TR
+><TR
+><TD
+>Windows XP Home</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+> The following versions of MS Windows fully support domain
+		security protocols.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Windows NT 3.5x</TD
+></TR
+><TR
+><TD
+>Windows NT 4.0</TD
 ></TR
 ><TR
 ><TD
@@ -2708,44 +3040,62 @@ BORDER="0"
 ></TABLE
 ><P
 ></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
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Note :</I
-></SPAN
 >All current release of 
-		Microsoft SMB/CIFS clients support authentication via the
-		SMB Challenge/Response mechanism described here.  Enabling
-		clear text authentication does not disable the ability
-		of the client to participate in encrypted authentication.</P
+	Microsoft SMB/CIFS clients support authentication via the
+	SMB Challenge/Response mechanism described here.  Enabling
+	clear text authentication does not disable the ability
+	of the client to participate in encrypted authentication.</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
 >MS Windows clients will cache the encrypted password alone.
-		Even when plain text passwords are re-enabled, through the appropriate
-		registry change, the plain text password is NEVER cached. This means that
-		in the event that a network connections should become disconnected (broken)
-		only the cached (encrypted) password will be sent to the resource server
-		to affect a auto-reconnect. If the resource server does not support encrypted
-		passwords the auto-reconnect will fail. <SPAN
+	Even when plain text passwords are re-enabled, through the appropriate
+	registry change, the plain text password is NEVER cached. This means that
+	in the event that a network connections should become disconnected (broken)
+	only the cached (encrypted) password will be sent to the resource server
+	to affect a auto-reconnect. If the resource server does not support encrypted
+	passwords the auto-reconnect will fail. <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
 >USE OF ENCRYPTED PASSWORDS
-		IS STRONGLY ADVISED.</I
+	IS STRONGLY ADVISED.</I
 ></SPAN
 ></P
-></TD
-></TR
-></TABLE
-></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN368"
->3.2.1. Advantages of SMB Encryption</A
+NAME="AEN502"
+>4.2.1. Advantages of SMB Encryption</A
 ></H3
 ><P
 ></P
@@ -2783,8 +3133,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN374"
->3.2.2. Advantages of non-encrypted passwords</A
+NAME="AEN508"
+>4.2.2. Advantages of non-encrypted passwords</A
 ></H3
 ><P
 ></P
@@ -2818,8 +3168,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN380"
->3.3. The smbpasswd Command</A
+NAME="AEN514"
+>4.3. The smbpasswd Command</A
 ></H2
 ><P
 >The smbpasswd utility is a utility similar to the 
@@ -2921,8 +3271,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN411"
->3.4. Plain text</A
+NAME="AEN545"
+>4.4. Plain text</A
 ></H2
 ><P
 >Older versions of samba retrieved user information from the unix user database 
@@ -2941,8 +3291,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN416"
->3.5. TDB</A
+NAME="AEN550"
+>4.5. TDB</A
 ></H2
 ><P
 >Samba can also store the user data in a "TDB" (Trivial Database). Using this backend 
@@ -2954,16 +3304,16 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN419"
->3.6. LDAP</A
+NAME="AEN553"
+>4.6. LDAP</A
 ></H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN421"
->3.6.1. Introduction</A
+NAME="AEN555"
+>4.6.1. Introduction</A
 ></H3
 ><P
 >This document describes how to use an LDAP directory for storing Samba user
@@ -3030,8 +3380,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN441"
->3.6.2. Introduction</A
+NAME="AEN575"
+>4.6.2. Introduction</A
 ></H3
 ><P
 >Traditionally, when configuring <A
@@ -3086,29 +3436,9 @@ Identified (RID).</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. <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
-> or
-<VAR
-CLASS="PARAMETER"
->--with-tdbsam</VAR
->) requires compile time support.</P
-><P
->When compiling Samba to include the <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
-> 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
+API, and is still so named in the CVS trees). </P
 ><P
->There are a few points to stress about what the <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
->
+>There are a few points to stress about what the ldapsam
 does not provide.  The LDAP support referred to in the this documentation does not
 include:</P
 ><P
@@ -3139,8 +3469,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN470"
->3.6.3. Supported LDAP Servers</A
+NAME="AEN599"
+>4.6.3. Supported LDAP Servers</A
 ></H3
 ><P
 >The LDAP samdb code in 2.2.3 (and later) has been developed and tested
@@ -3165,8 +3495,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN475"
->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</A
+NAME="AEN604"
+>4.6.4. Schema and Relationship to the RFC 2307 posixAccount</A
 ></H3
 ><P
 >Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
@@ -3222,16 +3552,16 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN487"
->3.6.5. Configuring Samba with LDAP</A
+NAME="AEN616"
+>4.6.5. Configuring Samba with LDAP</A
 ></H3
 ><DIV
 CLASS="SECT3"
 ><H4
 CLASS="SECT3"
 ><A
-NAME="AEN489"
->3.6.5.1. OpenLDAP configuration</A
+NAME="AEN618"
+>4.6.5.1. OpenLDAP configuration</A
 ></H4
 ><P
 >To include support for the sambaAccount object in an OpenLDAP directory
@@ -3277,9 +3607,7 @@ include	           /etc/openldap/schema/core.schema
 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
+include            /etc/openldap/schema/nis.schema
 
 ....</PRE
 ></P
@@ -3312,8 +3640,8 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN506"
->3.6.5.2. Configuring Samba</A
+NAME="AEN635"
+>4.6.5.2. Configuring Samba</A
 ></H4
 ><P
 >The following parameters are available in smb.conf only with <VAR
@@ -3428,8 +3756,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN534"
->3.6.6. Accounts and Groups management</A
+NAME="AEN663"
+>4.6.6. Accounts and Groups management</A
 ></H3
 ><P
 >As users accounts are managed thru the sambaAccount objectclass, you should
@@ -3453,8 +3781,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN539"
->3.6.7. Security and sambaAccount</A
+NAME="AEN668"
+>4.6.7. Security and sambaAccount</A
 ></H3
 ><P
 >There are two important points to remember when discussing the security
@@ -3489,9 +3817,8 @@ CLASS="EMPHASIS"
 >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
+HREF="#PASSDB"
+>User Database</A
 > of the Samba-HOWTO-Collection.</P
 ><P
 >To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
@@ -3532,8 +3859,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN559"
->3.6.8. LDAP specials attributes for sambaAccounts</A
+NAME="AEN688"
+>4.6.8. LDAP specials attributes for sambaAccounts</A
 ></H3
 ><P
 >The sambaAccount objectclass is composed of the following attributes:</P
@@ -3739,8 +4066,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN629"
->3.6.9. Example LDIF Entries for a sambaAccount</A
+NAME="AEN758"
+>4.6.9. Example LDIF Entries for a sambaAccount</A
 ></H3
 ><P
 >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
@@ -3798,16 +4125,16 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN637"
->3.7. MySQL</A
+NAME="AEN766"
+>4.7. MySQL</A
 ></H2
 ><DIV
 CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN639"
->3.7.1. Creating the database</A
+NAME="AEN768"
+>4.7.1. Creating the database</A
 ></H3
 ><P
 >You either can set up your own table and specify the field names to pdb_mysql (see below
@@ -3842,8 +4169,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN649"
->3.7.2. Configuring</A
+NAME="AEN778"
+>4.7.2. Configuring</A
 ></H3
 ><P
 >This plugin lacks some good documentation, but here is some short info:</P
@@ -3953,8 +4280,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN666"
->3.7.3. Using plaintext passwords or encrypted password</A
+NAME="AEN795"
+>4.7.3. Using plaintext passwords or encrypted password</A
 ></H3
 ><P
 >I strongly discourage the use of plaintext passwords, however, you can use them:</P
@@ -3968,8 +4295,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN671"
->3.7.4. Getting non-column data from the table</A
+NAME="AEN800"
+>4.7.4. Getting non-column data from the table</A
 ></H3
 ><P
 >It is possible to have not all data in the database and making some 'constant'.</P
@@ -3994,8 +4321,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN679"
->3.8. XML</A
+NAME="AEN808"
+>4.8. XML</A
 ></H2
 ><P
 >This module requires libxml2 to be installed.</P
@@ -4029,10 +4356,11 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >II. Type of installation</H1
+></DIV
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN688"
+NAME="AEN817"
 ></A
 ><H1
 >Introduction</H1
@@ -4041,308 +4369,12 @@ NAME="AEN688"
 for various environments.</P
 ></DIV
 ><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->4. <A
-HREF="#SERVERTYPE"
->Nomenclature of Server Types</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="#AEN717"
->Stand Alone Server</A
-></DT
-><DT
->4.2. <A
-HREF="#AEN724"
->Domain Member Server</A
-></DT
-><DT
->4.3. <A
-HREF="#AEN730"
->Domain Controller</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="#AEN733"
->Domain Controller Types</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->5. <A
-HREF="#SECURITYLEVELS"
->Samba as Stand-Alone Server</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="#AEN766"
->User and Share security level</A
-></DT
-><DD
-><DL
-><DT
->5.1.1. <A
-HREF="#AEN769"
->User Level Security</A
-></DT
-><DT
->5.1.2. <A
-HREF="#AEN779"
->Share Level Security</A
-></DT
-><DT
->5.1.3. <A
-HREF="#AEN785"
->Server Level Security</A
-></DT
-><DT
->5.1.4. <A
-HREF="#AEN825"
->Domain Level Security</A
-></DT
-><DT
->5.1.5. <A
-HREF="#AEN848"
->ADS Level Security</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->6. <A
-HREF="#SAMBA-PDC"
->Samba as an NT4 or Win2k Primary Domain Controller</A
-></DT
-><DD
-><DL
-><DT
->6.1. <A
-HREF="#AEN878"
->Prerequisite Reading</A
-></DT
-><DT
->6.2. <A
-HREF="#AEN883"
->Background</A
-></DT
-><DT
->6.3. <A
-HREF="#AEN923"
->Configuring the Samba Domain Controller</A
-></DT
-><DT
->6.4. <A
-HREF="#AEN965"
->Creating Machine Trust Accounts and Joining Clients to the Domain</A
-></DT
-><DD
-><DL
-><DT
->6.4.1. <A
-HREF="#AEN1008"
->Manual Creation of Machine Trust Accounts</A
-></DT
-><DT
->6.4.2. <A
-HREF="#AEN1049"
->"On-the-Fly" Creation of Machine Trust Accounts</A
-></DT
-><DT
->6.4.3. <A
-HREF="#AEN1058"
->Joining the Client to the Domain</A
-></DT
-></DL
-></DD
-><DT
->6.5. <A
-HREF="#AEN1073"
->Common Problems and Errors</A
-></DT
-><DT
->6.6. <A
-HREF="#AEN1119"
->What other help can I get?</A
-></DT
-><DT
->6.7. <A
-HREF="#AEN1233"
->Domain Control for Windows 9x/ME</A
-></DT
-><DD
-><DL
-><DT
->6.7.1. <A
-HREF="#AEN1256"
->Configuration Instructions:	Network Logons</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->7. <A
-HREF="#SAMBA-BDC"
->Samba Backup Domain Controller to Samba Domain Control</A
-></DT
-><DD
-><DL
-><DT
->7.1. <A
-HREF="#AEN1286"
->Prerequisite Reading</A
-></DT
-><DT
->7.2. <A
-HREF="#AEN1290"
->Background</A
-></DT
-><DT
->7.3. <A
-HREF="#AEN1298"
->What qualifies a Domain Controller on the network?</A
-></DT
-><DD
-><DL
-><DT
->7.3.1. <A
-HREF="#AEN1301"
->How does a Workstation find its domain controller?</A
-></DT
-><DT
->7.3.2. <A
-HREF="#AEN1304"
->When is the PDC needed?</A
-></DT
-></DL
-></DD
-><DT
->7.4. <A
-HREF="#AEN1307"
->Can Samba be a Backup Domain Controller to an NT PDC?</A
-></DT
-><DT
->7.5. <A
-HREF="#AEN1312"
->How do I set up a Samba BDC?</A
-></DT
-><DD
-><DL
-><DT
->7.5.1. <A
-HREF="#AEN1329"
->How do I replicate the smbpasswd file?</A
-></DT
-><DT
->7.5.2. <A
-HREF="#AEN1333"
->Can I do this all with LDAP?</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->8. <A
-HREF="#ADS"
->Samba as a ADS domain member</A
-></DT
-><DD
-><DL
-><DT
->8.1. <A
-HREF="#AEN1355"
->Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
-></DT
-><DT
->8.2. <A
-HREF="#AEN1368"
->Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
-></DT
-><DT
->8.3. <A
-HREF="#ADS-CREATE-MACHINE-ACCOUNT"
->Create the computer account</A
-></DT
-><DD
-><DL
-><DT
->8.3.1. <A
-HREF="#AEN1396"
->Possible errors</A
-></DT
-></DL
-></DD
-><DT
->8.4. <A
-HREF="#ADS-TEST-SERVER"
->Test your server setup</A
-></DT
-><DT
->8.5. <A
-HREF="#ADS-TEST-SMBCLIENT"
->Testing with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-></DT
-><DT
->8.6. <A
-HREF="#AEN1416"
->Notes</A
-></DT
-></DL
-></DD
-><DT
->9. <A
-HREF="#DOMAIN-SECURITY"
->Samba as a NT4 or Win2k domain member</A
-></DT
-><DD
-><DL
-><DT
->9.1. <A
-HREF="#AEN1439"
->Joining an NT Domain with Samba 3.0</A
-></DT
-><DT
->9.2. <A
-HREF="#AEN1493"
->Why is this better than security = server?</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
-><DIV
 CLASS="CHAPTER"
 ><HR><H1
 ><A
 NAME="SERVERTYPE"
 ></A
->Chapter 4. Nomenclature of Server Types</H1
+>Chapter 5. Nomenclature of Server Types</H1
 ><P
 >Adminstrators of Microsoft networks often refer to there being three
 different type of servers:</P
@@ -4387,8 +4419,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN717"
->4.1. Stand Alone Server</A
+NAME="AEN847"
+>5.1. Stand Alone Server</A
 ></H2
 ><P
 >The term <SPAN
@@ -4430,8 +4462,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN724"
->4.2. Domain Member Server</A
+NAME="AEN854"
+>5.2. Domain Member Server</A
 ></H2
 ><P
 >This mode of server operation involves the samba machine being made a member
@@ -4460,8 +4492,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN730"
->4.3. Domain Controller</A
+NAME="AEN860"
+>5.3. Domain Controller</A
 ></H2
 ><P
 >Over the years public perceptions of what Domain Control really is has taken on an
@@ -4472,8 +4504,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN733"
->4.3.1. Domain Controller Types</A
+NAME="AEN863"
+>5.3.1. Domain Controller Types</A
 ></H3
 ><P
 ></P
@@ -4541,7 +4573,7 @@ CLASS="emphasis"
 CLASS="EMPHASIS"
 >ADS Domain Controller</I
 ></SPAN
->.&#13;</P
+>.</P
 ></DIV
 ></DIV
 ></DIV
@@ -4551,7 +4583,7 @@ CLASS="CHAPTER"
 ><A
 NAME="SECURITYLEVELS"
 ></A
->Chapter 5. Samba as Stand-Alone Server</H1
+>Chapter 6. Samba as Stand-Alone Server</H1
 ><P
 >In this section the function and purpose of Samba's <SPAN
 CLASS="emphasis"
@@ -4566,8 +4598,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN766"
->5.1. User and Share security level</A
+NAME="AEN897"
+>6.1. User and Share security level</A
 ></H2
 ><P
 >A SMB server tells the client at startup what "security level" it is
@@ -4584,8 +4616,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN769"
->5.1.1. User Level Security</A
+NAME="AEN900"
+>6.1.1. User Level Security</A
 ></H3
 ><P
 >I'll describe user level security first, as its simpler. In user level
@@ -4625,8 +4657,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN779"
->5.1.2. Share Level Security</A
+NAME="AEN910"
+>6.1.2. Share Level Security</A
 ></H3
 ><P
 >Ok, now for share level security. In share level security the client
@@ -4662,8 +4694,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN785"
->5.1.3. Server Level Security</A
+NAME="AEN916"
+>6.1.3. Server Level Security</A
 ></H3
 ><P
 >Finally "server level" security. In server level security the samba
@@ -4698,8 +4730,8 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN790"
->5.1.3.1. Configuring Samba for Seemless Windows Network Integration</A
+NAME="AEN921"
+>6.1.3.1. Configuring Samba for Seemless Windows Network Integration</A
 ></H4
 ><P
 >MS Windows clients may use encrypted passwords as part of a challenege/response
@@ -4810,8 +4842,8 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN816"
->5.1.3.2. Use MS Windows NT as an authentication server</A
+NAME="AEN947"
+>6.1.3.2. Use MS Windows NT as an authentication server</A
 ></H4
 ><P
 >This method involves the additions of the following parameters in the <TT
@@ -4849,8 +4881,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN825"
->5.1.4. Domain Level Security</A
+NAME="AEN956"
+>6.1.4. Domain Level Security</A
 ></H3
 ><P
 >When samba is operating in <SPAN
@@ -4867,8 +4899,8 @@ CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN829"
->5.1.4.1. Samba as a member of an MS Windows NT security domain</A
+NAME="AEN960"
+>6.1.4.1. Samba as a member of an MS Windows NT security domain</A
 ></H4
 ><P
 >This method involves additon of the following paramters in the <TT
@@ -4936,8 +4968,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN848"
->5.1.5. ADS Level Security</A
+NAME="AEN979"
+>6.1.5. ADS Level Security</A
 ></H3
 ><P
 >For information about the configuration option please refer to the entire section entitled
@@ -4957,37 +4989,32 @@ CLASS="CHAPTER"
 ><A
 NAME="SAMBA-PDC"
 ></A
->Chapter 6. Samba as an NT4 or Win2k Primary Domain Controller</H1
+>Chapter 7. Samba as an NT4 or Win2k Primary Domain Controller</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN878"
->6.1. Prerequisite Reading</A
+NAME="AEN1010"
+>7.1. Prerequisite Reading</A
 ></H2
 ><P
 >Before you continue reading in this chapter, please make sure 
 that you are comfortable with configuring basic files services
 in smb.conf and how to enable and administer password 
 encryption in Samba.  Theses two topics are covered in the
-<A
-HREF="smb.conf.5.html"
-TARGET="_top"
-><TT
+<TT
 CLASS="FILENAME"
->smb.conf(5)</TT
-></A
-> 
-manpage.</P
+>smb.conf</TT
+> manpage.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN883"
->6.2. Background</A
+NAME="AEN1014"
+>7.2. Background</A
 ></H2
 ><P
 >This article outlines the steps necessary for configuring Samba as a PDC.
@@ -5133,19 +5160,17 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN923"
->6.3. Configuring the Samba Domain Controller</A
+NAME="AEN1054"
+>7.3. Configuring the Samba Domain Controller</A
 ></H2
 ><P
 >The first step in creating a working Samba PDC is to 
 understand the parameters necessary in smb.conf. Here we
 attempt to explain the parameters that are covered in
-<A
-HREF="smb.conf.5.html"
-TARGET="_top"
-> the smb.conf
-man page</A
->.</P
+the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> man page.</P
 ><P
 >Here is an example <TT
 CLASS="FILENAME"
@@ -5297,7 +5322,7 @@ TARGET="_top"
 >	Encrypted passwords must be enabled.  For more details on how 
 	to do this, refer to <A
 HREF="#PASSDB"
->ENCRYPTION.html</A
+>the User Database chapter</A
 >.
 	</P
 ></LI
@@ -5329,8 +5354,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN965"
->6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A
+NAME="AEN1096"
+>7.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A
 ></H2
 ><P
 >A machine trust account is a Samba account that is used to
@@ -5432,7 +5457,10 @@ CLASS="EMPHASIS"
 	file allows the creation of arbitrary user and machine accounts without
 	requiring that account to be added to the system (/etc/passwd) file. It
 	too requires the specification of the "non unix account range" option
-	in the [globals] section of the smb.conf file.
+	in the [globals] section of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
 	</P
 ></LI
 ><LI
@@ -5461,6 +5489,12 @@ CLASS="EMPHASIS"
 ></LI
 ></UL
 ><P
+>Read the chapter about the <A
+HREF="#PASSDB"
+>User Database</A
+> 
+for details.</P
+><P
 >A Samba PDC, however, stores each machine trust account in two parts,
 as follows:
 
@@ -5515,8 +5549,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1008"
->6.4.1. Manual Creation of Machine Trust Accounts</A
+NAME="AEN1142"
+>7.4.1. Manual Creation of Machine Trust Accounts</A
 ></H3
 ><P
 >The first step in manually creating a machine trust account is to
@@ -5621,12 +5655,12 @@ as shown here:</P
 ><SAMP
 CLASS="PROMPT"
 >root# </SAMP
-><B
-CLASS="COMMAND"
+><KBD
+CLASS="USERINPUT"
 >smbpasswd -a -m <VAR
 CLASS="REPLACEABLE"
 >machine_name</VAR
-></B
+></KBD
 ></P
 ><P
 >where <VAR
@@ -5685,8 +5719,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1049"
->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
+NAME="AEN1183"
+>7.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
 ></H3
 ><P
 >The second (and recommended) way of creating machine trust accounts is
@@ -5722,8 +5756,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1058"
->6.4.3. Joining the Client to the Domain</A
+NAME="AEN1192"
+>7.4.3. Joining the Client to the Domain</A
 ></H3
 ><P
 >The procedure for joining a client to the domain varies with the
@@ -5782,759 +5816,663 @@ CLASS="EMPHASIS"
 	(i.e., you must supply a Samba administrative account when
 	prompted).</P
 ></LI
-></UL
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1073"
->6.5. Common Problems and Errors</A
-></H2
-><P
-></P
-><P
-></P
-><UL
 ><LI
 ><P
->	<SPAN
+><SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->I cannot include a '$' in a machine name.</I
+>Samba</I
 ></SPAN
->
-	</P
+></P
+><P
+>Joining a samba client to a domain is documented in 
+	the <A
+HREF="#DOMAIN-MEMBER"
+>Domain Member</A
+> chapter.</P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1212"
+>7.5. Common Problems and Errors</A
+></H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN1214"
+>7.5.1. I cannot include a '$' in a machine name</A
+></H3
 ><P
->	A 'machine name' in (typically) <TT
+>A 'machine name' in (typically) <TT
 CLASS="FILENAME"
 >/etc/passwd</TT
 > 	
-	of the machine name with a '$' appended. FreeBSD (and other BSD 
-	systems?) won't create a user with a '$' in their name.
-	</P
+of the machine name with a '$' appended. FreeBSD (and other BSD 
+systems?) won't create a user with a '$' in their name.</P
 ><P
->	The problem is only in the program used to make the entry, once 
-	made, it works perfectly. So create a user without the '$' and 
-	use <B
+>The problem is only in the program used to make the entry, once 
+made, it works perfectly. So create a user without the '$' and 
+use <B
 CLASS="COMMAND"
 >vipw</B
 > to edit the entry, adding the '$'. Or create 
-	the whole entry with vipw if you like, make sure you use a 
-	unique User ID !
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->I get told "You already have a connection to the Domain...." 
-	or "Cannot join domain, the credentials supplied conflict with an 
-	existing set.." when creating a machine trust account.</I
-></SPAN
->
-	</P
+the whole entry with vipw if you like, make sure you use a 
+unique User ID !</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1220"
+>7.5.2. I get told "You already have a connection to the Domain...." 
+or "Cannot join domain, the credentials supplied conflict with an 
+existing set.." when creating a machine trust account.</A
+></H3
 ><P
->	This happens if you try to create a machine trust account from the 
-	machine itself and already have a connection (e.g. mapped drive) 
-	to a share (or IPC$) on the Samba PDC.  The following command
-	will remove all network drive connections:
-	</P
+>This happens if you try to create a machine trust account from the 
+machine itself and already have a connection (e.g. mapped drive) 
+to a share (or IPC$) on the Samba PDC.  The following command
+will remove all network drive connections:</P
 ><P
->	<SAMP
+><SAMP
 CLASS="PROMPT"
 >C:\WINNT\&#62;</SAMP
 > <B
 CLASS="COMMAND"
 >net use * /d</B
->
-	</P
-><P
->	Further, if the machine is a already a 'member of a workgroup' that 
-	is the same name as the domain you are joining (bad idea) you will 
-	get this message.  Change the workgroup name to something else, it 
-	does not matter what, reboot, and try again.
-	</P
-></LI
-><LI
+></P
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The system can not log you on (C000019B)....</I
-></SPAN
->
-	</P
+>Further, if the machine is a already a 'member of a workgroup' that 
+is the same name as the domain you are joining (bad idea) you will 
+get this message.  Change the workgroup name to something else, it 
+does not matter what, reboot, and try again.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1227"
+>7.5.3. The system can not log you on (C000019B)....</A
+></H3
 ><P
 >I joined the domain successfully but after upgrading 
-	to a newer version of the Samba code I get the message, "The system 
-	can not log you on (C000019B), Please try again or consult your 
-	system administrator" when attempting to logon.
-	</P
-><P
->	This occurs when the domain SID stored in the secrets.tdb database
-	is changed. The most common cause of a change in domain SID is when
-	the domain name and/or the server name (netbios name) is changed.
- 	The only way to correct the problem is to restore the original domain 
-	SID or remove the domain client from the domain and rejoin. The domain
-	SID may be reset using either the smbpasswd or rpcclient utilities.
-	</P
-></LI
-><LI
+to a newer version of the Samba code I get the message, "The system 
+can not log you on (C000019B), Please try again or consult your 
+system administrator" when attempting to logon.</P
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The machine trust account for this computer either does not 
-	exist or is not accessible.</I
-></SPAN
->
-	</P
+>This occurs when the domain SID stored in the secrets.tdb database
+is changed. The most common cause of a change in domain SID is when
+the domain name and/or the server name (netbios name) is changed.
+The only way to correct the problem is to restore the original domain 
+SID or remove the domain client from the domain and rejoin. The domain
+SID may be reset using either the smbpasswd or rpcclient utilities.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1231"
+>7.5.4. The machine trust account for this computer either does not 
+exist or is not accessible.</A
+></H3
 ><P
->	When I try to join the domain I get the message "The machine account 
-	for this computer either does not exist or is not accessible". What's 
-	wrong?
-	</P
+>When I try to join the domain I get the message "The machine account 
+for this computer either does not exist or is not accessible". What's 
+wrong?</P
 ><P
->	This problem is caused by the PDC not having a suitable machine trust account. 
-	If you are using the <VAR
+>This problem is caused by the PDC not having a suitable machine trust account. 
+If you are using the <VAR
 CLASS="PARAMETER"
 >add user script</VAR
 > method to create 
-	accounts then this would indicate that it has not worked. Ensure the domain 
-	admin user system is working.
-	</P
+accounts then this would indicate that it has not worked. Ensure the domain 
+admin user system is working.</P
 ><P
->	Alternatively if you are creating account entries manually then they 
-	have not been created correctly. Make sure that you have the entry 
-	correct for the machine trust account in smbpasswd file on the Samba PDC. 
-	If you added the account using an editor rather than using the smbpasswd 
-	utility, make sure that the account name is the machine NetBIOS name 
-	with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
-	in both /etc/passwd and the smbpasswd file. Some people have reported 
-	that inconsistent subnet masks between the Samba server and the NT 
-	client have caused this problem.   Make sure that these are consistent 
-	for both client and server.
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-	I get a message about my account being disabled.</I
-></SPAN
->
-	</P
-><P
->	This problem is caused by a PAM related bug in Samba 2.2.0.  This bug is 
-	fixed in 2.2.1.  Other symptoms could be unaccessible shares on 
-	NT/W2K member servers in the domain or the following error in your smbd.log:
-	passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user%
-	</P
+>Alternatively if you are creating account entries manually then they 
+have not been created correctly. Make sure that you have the entry 
+correct for the machine trust account in smbpasswd file on the Samba PDC. 
+If you added the account using an editor rather than using the smbpasswd 
+utility, make sure that the account name is the machine NetBIOS name 
+with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
+in both /etc/passwd and the smbpasswd file. Some people have reported 
+that inconsistent subnet masks between the Samba server and the NT 
+client have caused this problem.   Make sure that these are consistent 
+for both client and server.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1237"
+>7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+I get a message about my account being disabled.</A
+></H3
 ><P
->	At first be ensure to enable the useraccounts with <B
+>At first be ensure to enable the useraccounts with <B
 CLASS="COMMAND"
 >smbpasswd -e 
-	%user%</B
->, this is normally done, when you create an account.
-	</P
-><P
->	In order to work around this problem in 2.2.0, configure the 
-	<VAR
-CLASS="PARAMETER"
->account</VAR
-> control flag in 
-	<TT
-CLASS="FILENAME"
->/etc/pam.d/samba</TT
-> file as follows:
-	</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	account required        pam_permit.so
-	</PRE
-></P
-><P
->	If you want to remain backward compatibility to samba 2.0.x use
-	<TT
-CLASS="FILENAME"
->pam_permit.so</TT
->, it's also possible to use 
-	<TT
-CLASS="FILENAME"
->pam_pwdb.so</TT
->. There are some bugs if you try to 
-	use <TT
-CLASS="FILENAME"
->pam_unix.so</TT
->, if you need this, be ensure to use
-	the most recent version of this file.
-	</P
-></LI
-></UL
+%user%</B
+>, this is normally done, when you create an account.</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1119"
->6.6. What other help can I get?</A
+NAME="AEN1241"
+>7.6. Domain Control for Windows 9x/ME</A
 ></H2
 ><P
->There are many sources of information available in the form 
-of mailing lists, RFC's and documentation.  The docs that come 
-with the samba distribution contain very good explanations of 
-general SMB topics such as browsing.</P
+>A domain and a workgroup are exactly the same thing in terms of network
+browsing.  The difference is that a distributable authentication
+database is associated with a domain, for secure login access to a
+network.  Also, different access rights can be granted to users if they
+successfully authenticate against a domain logon server. Samba-3 does this
+now in the same way that MS Windows NT/2K.</P
 ><P
-></P
-><UL
-><LI
+>The SMB client logging on to a domain has an expectation that every other
+server in the domain should accept the same authentication information.
+Network browsing functionality of domains and workgroups is identical and
+is explained in this documentation under the browsing discussions.
+It should be noted, that browsing is totally orthogonal to logon support.</P
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->What are some diagnostics tools I can use to debug the domain logon 
-	process and where can I	find them?</I
-></SPAN
->
-	</P
+>Issues related to the single-logon network model are discussed in this
+section.  Samba supports domain logons, network logon scripts, and user
+profiles for MS Windows for workgroups and MS Windows 9X/ME clients
+which are the focus of this section.</P
 ><P
->	One of the best diagnostic tools for debugging problems is Samba itself.  
-	You can use the -d option for both smbd and nmbd to specify what 
-	'debug level' at which to run.  See the man pages on smbd, nmbd  and 
-	smb.conf for more information on debugging options.  The debug 
-	level can range from 1 (the default) to 10 (100 for debugging passwords).
-	</P
+>When an SMB client in a domain wishes to logon it broadcast requests for a
+logon server.  The first one to reply gets the job, and validates its
+password using whatever mechanism the Samba administrator has installed.
+It is possible (but very stupid) to create a domain where the user
+database is not shared between servers, i.e. they are effectively workgroup
+servers advertising themselves as participating in a domain.  This
+demonstrates how authentication is quite different from but closely
+involved with domains.</P
 ><P
->	Another helpful method of debugging is to compile samba using the 
-	<B
-CLASS="COMMAND"
->gcc -g </B
-> flag.   This will include debug 
-	information in the binaries and allow you to attach gdb to the 
-	running smbd / nmbd process.  In order to attach gdb to an smbd 
-	process for an NT workstation, first get the workstation to make the 
-	connection. Pressing ctrl-alt-delete and going down to the domain box 
-	is sufficient (at least, on the first time you join the domain) to 
-	generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
-	maintains an open connection, and therefore there will be an smbd 
-	process running (assuming that you haven't set a really short smbd 
-	idle timeout)  So, in between pressing ctrl alt delete, and actually 
-	typing in your password, you can gdb attach and continue.
-	</P
+>Using these features you can make your clients verify their logon via
+the Samba server; make clients run a batch file when they logon to
+the network and download their preferences, desktop and start menu.</P
 ><P
->	Some useful samba commands worth investigating:
-	</P
+>Before launching into the configuration instructions, it is 
+worthwhile lookingat how a Windows 9x/ME client performs a logon:</P
 ><P
 ></P
-><UL
+><OL
+TYPE="1"
 ><LI
 ><P
->testparam | more</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
+	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.
+	</P
 ></LI
 ><LI
 ><P
->smbclient -L //{netbios name of server}</P
+>	The client then connects to that server, logs on (does an SMBsessetupX) and
+	then connects to the IPC$ share (using an SMBtconX).
+	</P
 ></LI
-></UL
+><LI
 ><P
->	An SMB enabled version of tcpdump is available from 
-	<A
-HREF="http://www.tcpdump.org/"
-TARGET="_top"
->http://www.tcpdup.org/</A
->.
-	Ethereal, another good packet sniffer for Unix and Win32
-	hosts, can be downloaded from <A
-HREF="http://www.ethereal.com/"
-TARGET="_top"
->http://www.ethereal.com</A
->.
+>	The client then does a NetWkstaUserLogon request, which retrieves the name
+	of the user's logon script. 
 	</P
+></LI
+><LI
 ><P
->	For tracing things on the Microsoft Windows NT, Network Monitor 
-	(aka. netmon) is available on the Microsoft Developer Network CD's, 
-	the Windows NT Server install CD and the SMS CD's.  The version of 
-	netmon that ships with SMS allows for dumping packets between any two 
-	computers (i.e. placing the network interface in promiscuous mode).  
-	The version on the NT Server install CD will only allow monitoring 
-	of network traffic directed to the local NT box and broadcasts on the 
-	local subnet.  Be aware that Ethereal can read and write netmon 
-	formatted files.
+>	The client then connects to the NetLogon share and searches for this 	
+	and if it is found and can be read, is retrieved and executed by the client.
+	After this, the client disconnects from the NetLogon share.
 	</P
 ></LI
 ><LI
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I install 'Network Monitor' on an NT Workstation 
-	or a Windows 9x box?</I
-></SPAN
->
+>	The client then sends a NetUserGetInfo request to the server, to retrieve
+	the user's home share, which is used to search for profiles. Since the
+	response to the NetUserGetInfo request does not contain much more 	
+	the user's home share, profiles for Win9X clients MUST reside in the user
+	home directory.
 	</P
+></LI
+><LI
 ><P
->	Installing netmon on an NT workstation requires a couple 
-	of steps.  The following are for installing Netmon V4.00.349, which comes 
-	with Microsoft Windows NT Server 4.0, on Microsoft Windows NT 
-	Workstation 4.0.  The process should be similar for other version of 
-	Windows NT / Netmon.  You will need both the Microsoft Windows 
-	NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
+>	The client then connects to the user's home share and searches for the 
+	user's profile. As it turns out, you can specify the user's home share as
+	a sharename and path. For example, \\server\fred\.profile.
+	If the profiles are found, they are implemented.
 	</P
+></LI
+><LI
 ><P
->	Initially you will need to install 'Network Monitor Tools and Agent' 
-	on the NT Server.  To do this 
+>	The client then disconnects from the user's home share, and reconnects to
+	the NetLogon share and looks for CONFIG.POL, the policies file. If this is
+	found, it is read and implemented.
 	</P
+></LI
+></OL
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1264"
+>7.6.1. Configuration Instructions:	Network Logons</A
+></H3
+><P
+>The main difference between a PDC and a Windows 9x logon 
+server configuration is that</P
 ><P
 ></P
 ><UL
 ><LI
 ><P
->Goto Start - Settings - Control Panel - 
-		Network - Services - Add </P
+>Password encryption is not required for a Windows 9x logon server.</P
 ></LI
 ><LI
 ><P
->Select the 'Network Monitor Tools and Agent' and 
-		click on 'OK'.</P
-></LI
-><LI
-><P
->Click 'OK' on the Network Control Panel.
-		</P
-></LI
-><LI
-><P
->Insert the Windows NT Server 4.0 install CD 
-		when prompted.</P
+>Windows 9x/ME clients do not possess machine trust accounts.</P
 ></LI
 ></UL
 ><P
->	At this point the Netmon files should exist in 
-	<TT
-CLASS="FILENAME"
->%SYSTEMROOT%\System32\netmon\*.*</TT
->.    
-	Two subdirectories exist as well, <TT
-CLASS="FILENAME"
->parsers\</TT
-> 
-	which contains the necessary DLL's for parsing the netmon packet 
-	dump, and <TT
-CLASS="FILENAME"
->captures\</TT
->.
-	</P
-><P
->	In order to install the Netmon tools on an NT Workstation, you will 
-	first need to install the 'Network  Monitor Agent' from the Workstation 
-	install CD.
-	</P
+>Therefore, a Samba PDC will also act as a Windows 9x logon 
+server.</P
+><DIV
+CLASS="WARNING"
 ><P
 ></P
-><UL
-><LI
-><P
->Goto Start - Settings - Control Panel - 
-		Network - Services - Add</P
-></LI
-><LI
-><P
->Select the 'Network Monitor Agent' and click 
-		on 'OK'.</P
-></LI
-><LI
-><P
->Click 'OK' on the Network Control Panel.
-		</P
-></LI
-><LI
-><P
->Insert the Windows NT Workstation 4.0 install 
-		CD when prompted.</P
-></LI
-></UL
+><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
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>security mode and master browsers</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
 ><P
->	Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
-	to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
-	permissions as  you deem appropriate for your site. You will need 
-	administrative rights on the NT box to run netmon.
-	</P
+>There are a few comments to make in order to tie up some 
+loose ends.  There has been much debate over the issue of whether
+or not it is ok to configure Samba as a Domain Controller in security
+modes other than <CODE
+CLASS="CONSTANT"
+>USER</CODE
+>.  The only security mode 
+which  will not work due to technical reasons is <CODE
+CLASS="CONSTANT"
+>SHARE</CODE
+>
+mode security.  <CODE
+CLASS="CONSTANT"
+>DOMAIN</CODE
+> and <CODE
+CLASS="CONSTANT"
+>SERVER</CODE
+>
+mode security is really just a variation on SMB user level security.</P
 ><P
->	To install Netmon on a Windows 9x box install the network monitor agent 
-	from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
-	file located with the netmon driver files on the CD if you need 
-	information on how to do this.  Copy the files from a working 
-	Netmon installation.
-	</P
-></LI
-><LI
+>Actually, this issue is also closely tied to the debate on whether 
+or not Samba must be the domain master browser for its workgroup
+when operating as a DC.  While it may technically be possible
+to configure a server as such (after all, browsing and domain logons
+are two distinctly different functions), it is not a good idea to
+so.  You should remember that the DC must register the DOMAIN#1b NetBIOS 
+name.  This is the name used by Windows clients to locate the DC.
+Windows clients do not distinguish between the DC and the DMB.
+For this reason, it is very wise to configure the Samba DC as the DMB.</P
 ><P
->	The following is a list if helpful URLs and other links:
-	</P
+>Now back to the issue of configuring a Samba DC to use a mode other
+than "security = user".  If a Samba host is configured to use 
+another SMB server or DC in order to validate user connection 
+requests, then it is a fact that some other machine on the network 
+(the "password server") knows more about user than the Samba host.
+99% of the time, this other host is a domain controller.  Now 
+in order to operate in domain mode security, the "workgroup" parameter
+must be set to the name of the Windows NT domain (which already 
+has a domain controller, right?)</P
 ><P
-></P
-><UL
-><LI
+>Therefore configuring a Samba box as a DC for a domain that 
+already by definition has a PDC is asking for trouble.
+Therefore, you should always configure the Samba DC to be the DMB
+for its domain.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="SAMBA-BDC"
+></A
+>Chapter 8. Samba Backup Domain Controller to Samba Domain Control</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN1294"
+>8.1. Prerequisite Reading</A
+></H2
 ><P
->Home of Samba site <A
-HREF="http://samba.org"
+>Before you continue reading in this chapter, please make sure
+that you are comfortable with configuring a Samba PDC
+as described in the <A
+HREF="Samba-PDC-HOWTO.html"
 TARGET="_top"
->        http://samba.org</A
->. We have a mirror near you !</P
-></LI
-><LI
-><P
-> The <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Development</I
-></SPAN
-> document 
-	on the Samba mirrors might mention your problem. If so,
-	it might mean that the developers are working on it.</P
-></LI
-><LI
+>Samba-PDC-HOWTO</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1298"
+>8.2. Background</A
+></H2
 ><P
->See how Scott Merrill simulates a BDC behavior at 
-        <A
-HREF="http://www.skippy.net/linux/smb-howto.html"
-TARGET="_top"
->        http://www.skippy.net/linux/smb-howto.html</A
->. </P
-></LI
-><LI
+>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
+user logs into a Windows NT Workstation, the workstation connects to a
+Domain Controller and asks him whether the username and password the
+user typed in is correct.  The Domain Controller replies with a lot of
+information about the user, for example the place where the users
+profile is stored, the users full name of the user. All this
+information is stored in the NT user database, the so-called SAM.</P
 ><P
->Although 2.0.7 has almost had its day as a PDC, David Bannon will
-        keep the 2.0.7 PDC pages at <A
-HREF="http://bioserve.latrobe.edu.au/samba"
-TARGET="_top"
->        http://bioserve.latrobe.edu.au/samba</A
-> going for a while yet.</P
-></LI
-><LI
+>There are two kinds of Domain Controller in a NT 4 compatible Domain:
+A Primary Domain Controller (PDC) and one or more Backup Domain
+Controllers (BDC). The PDC contains the master copy of the
+SAM. Whenever the SAM has to change, for example when a user changes
+his password, this change has to be done on the PDC. A Backup Domain
+Controller is a machine that maintains a read-only copy of the
+SAM. This way it is able to reply to logon requests and authenticate
+users in case the PDC is not available. During this time no changes to
+the SAM are possible. Whenever changes to the SAM are done on the PDC,
+all BDC receive the changes from the PDC.</P
 ><P
->Misc links to CIFS information 
-        <A
-HREF="http://samba.org/cifs/"
-TARGET="_top"
->http://samba.org/cifs/</A
-></P
-></LI
-><LI
+>Since version 2.2 Samba officially supports domain logons for all
+current Windows Clients, including Windows 2000 and XP. This text
+assumes the domain to be named SAMBA. To be able to act as a PDC, some
+parameters in the [global]-section of the smb.conf have to be set:</P
 ><P
->NT Domains for Unix <A
-HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
-TARGET="_top"
->        http://mailhost.cb1.com/~lkcl/ntdom/</A
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = SAMBA
+domain master = yes
+domain logons = yes</PRE
 ></P
-></LI
-><LI
 ><P
->FTP site for older SMB specs: 
-        <A
-HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
-TARGET="_top"
->        ftp://ftp.microsoft.com/developr/drg/CIFS/</A
-></P
-></LI
-></UL
-></LI
-></UL
+>Several other things like a [homes] and a [netlogon] share also may be
+set along with settings for the profile path, the users home drive and
+others. This will not be covered in this document.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1306"
+>8.3. What qualifies a Domain Controller on the network?</A
+></H2
 ><P
-></P
-><UL
-><LI
+>Every machine that is a Domain Controller for the domain SAMBA has to
+register the NetBIOS group name SAMBA#1c with the WINS server and/or
+by broadcast on the local network. The PDC also registers the unique
+NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
+normally reserved for the domain master browser, a role that has
+nothing to do with anything related to authentication, but the
+Microsoft Domain implementation requires the domain master browser to
+be on the same machine as the PDC.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1309"
+>8.3.1. How does a Workstation find its domain controller?</A
+></H3
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get help from the mailing lists?</I
-></SPAN
->
-	</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
+this by doing a NetBIOS name query for the group name SAMBA#1c. It
+assumes that each of the machines it gets back from the queries is a
+domain controller and can answer logon requests. To not open security
+holes both the workstation and the selected (TODO: How is the DC
+chosen) domain controller authenticate each other. After that the
+workstation sends the user's credentials (his name and password) to
+the domain controller, asking for approval.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1312"
+>8.3.2. When is the PDC needed?</A
+></H3
 ><P
->	There are a number of Samba related mailing lists. Go to <A
-HREF="http://samba.org"
-TARGET="_top"
->http://samba.org</A
->, click on your nearest mirror
-	and then click on <B
-CLASS="COMMAND"
->Support</B
-> and then click on <B
-CLASS="COMMAND"
->	Samba related mailing lists</B
->.
-	</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
+for SAMBA#1b, assuming this machine maintains the master copy of the
+SAM. The workstation contacts the PDC, both mutually authenticate and
+the password change is done.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1315"
+>8.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
+></H2
 ><P
->	For questions relating to Samba TNG go to
-	<A
-HREF="http://www.samba-tng.org/"
-TARGET="_top"
->http://www.samba-tng.org/</A
-> 
-	It has been requested that you don't post questions about Samba-TNG to the
-	main stream Samba lists.</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
->	If you post a message to one of the lists please observe the following guide lines :
-	</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
+service logon requests whenever the PDC is down.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1320"
+>8.5. How do I set up a Samba BDC?</A
+></H2
+><P
+>Several things have to be done:</P
 ><P
 ></P
 ><UL
 ><LI
 ><P
-> Always remember that the developers are volunteers, they are 
-		not paid and they never guarantee to produce a particular feature at 
-		a particular time. Any time lines are 'best guess' and nothing more.
-		</P
-></LI
-><LI
-><P
-> Always mention what version of samba you are using and what 
-		operating system its running under. You should probably list the
-        relevant sections of your smb.conf file, at least the options 
-        in [global] that affect PDC support.</P
-></LI
-><LI
+>The domain SID has to be the same on the PDC and the BDC. This used to
+be stored in the file private/MACHINE.SID. This file is not created
+anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
+stored in the file private/secrets.tdb. Simply copying the secrets.tdb
+from the PDC to the BDC does not work, as the BDC would
+generate a new SID for itself and override the domain SID with this
+new BDC SID.</P
 ><P
->In addition to the version, if you obtained Samba via
-        CVS mention the date when you last checked it out.</P
+>To retrieve the domain SID from the PDC or an existing BDC and store it in the
+secrets.tdb, execute 'net rpc getsid' on the BDC.</P
 ></LI
 ><LI
 ><P
-> Try and make your question clear and brief, lots of long, 
-		convoluted questions get deleted before	they are completely read ! 
-		Don't post html encoded messages (if you can select colour or font 
-		size its html).</P
+>The Unix user database has to be synchronized from the PDC to the
+BDC. This means that both the /etc/passwd and /etc/group have to be
+replicated from the PDC to the BDC. This can be done manually
+whenever changes are made, or the PDC is set up as a NIS master
+server and the BDC as a NIS slave server. To set up the BDC as a
+mere NIS client would not be enough, as the BDC would not be able to
+access its user database in case of a PDC failure.</P
 ></LI
 ><LI
 ><P
-> If you run one of those nifty 'I'm on holidays' things when 
-		you are away, make sure its configured	to not answer mailing lists.
-		</P
+>The Samba password database in the file private/smbpasswd has to be
+replicated from the PDC to the BDC. This is a bit tricky, see the
+next section.</P
 ></LI
 ><LI
 ><P
-> Don't cross post. Work out which is the best list to post to 
-		and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
-        Many people active on the lists subscribe to more 
-		than one list and get annoyed to see the same message two or more times. 
-		Often someone will see a message and thinking it would be better dealt 
-		with on another, will forward it on for you.</P
+>Any netlogon share has to be replicated from the PDC to the
+BDC. This can be done manually whenever login scripts are changed,
+or it can be done automatically together with the smbpasswd
+synchronization.</P
 ></LI
-><LI
+></UL
 ><P
->You might include <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->partial</I
-></SPAN
->
-        log files written at a debug level set to as much as 20.  
-        Please don't send the entire log but enough to give the context of the 
-        error messages.</P
-></LI
-><LI
+>Finally, the BDC has to be found by the workstations. This can be done
+by setting</P
 ><P
->(Possibly) If you have a complete netmon trace ( from the opening of 
-        the pipe to the error ) you can send the *.CAP file as well.</P
-></LI
-><LI
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = samba
+domain master = no
+domain logons = yes</PRE
+></P
 ><P
->Please think carefully before attaching a document to an email.
-        Consider pasting the relevant parts into the body of the message. The samba
-        mailing lists go to a huge number of people, do they all need a copy of your 
-        smb.conf in their attach directory?</P
-></LI
-></UL
-></LI
-><LI
+>in the [global]-section of the smb.conf of the BDC. This makes the BDC
+only register the name SAMBA#1c with the WINS server. This is no
+problem as the name SAMBA#1c is a NetBIOS group name that is meant to
+be registered by more than one machine. The parameter 'domain master =
+no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
+name is reserved for the Primary Domain Controller.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1337"
+>8.5.1. How do I replicate the smbpasswd file?</A
+></H3
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get off the mailing lists?</I
-></SPAN
->
-	</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
+done in the smbpasswd file and has to be replicated to the BDC. So
+replicating the smbpasswd file very often is necessary.</P
 ><P
->To have your name removed from a samba mailing list, go to the
-	same place you went to to get on it. Go to <A
-HREF="http://lists.samba.org/"
-TARGET="_top"
->http://lists.samba.org</A
->, 
-	click on your nearest mirror and then click on <B
-CLASS="COMMAND"
->Support</B
-> and 
-	then click on <B
-CLASS="COMMAND"
-> Samba related mailing lists</B
->. Or perhaps see 
-	<A
-HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
-TARGET="_top"
->here</A
->
-	</P
+>As the smbpasswd file contains plain text password equivalents, it
+must not be sent unencrypted over the wire. The best way to set up
+smbpasswd replication from the PDC to the BDC is to use the utility
+rsync. rsync can use ssh as a transport. ssh itself can be set up to
+accept *only* rsync transfer without requiring the user to type a
+password.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1341"
+>8.5.2. Can I do this all with LDAP?</A
+></H3
 ><P
->	Please don't post messages to the list asking to be removed, you will just
-	be referred to the above address (unless that process failed in some way...)
-	</P
-></LI
-></UL
+>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
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="ADS"
+></A
+>Chapter 9. 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
+><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1233"
->6.7. Domain Control for Windows 9x/ME</A
+NAME="AEN1364"
+>9.1. Setup your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+></A
 ></H2
 ><P
->A domain and a workgroup are exactly the same thing in terms of network
-browsing.  The difference is that a distributable authentication
-database is associated with a domain, for secure login access to a
-network.  Also, different access rights can be granted to users if they
-successfully authenticate against a domain logon server. Samba-3 does this
-now in the same way that MS Windows NT/2K.</P
-><P
->The SMB client logging on to a domain has an expectation that every other
-server in the domain should accept the same authentication information.
-Network browsing functionality of domains and workgroups is identical and
-is explained in this documentation under the browsing discussions.
-It should be noted, that browsing is totally orthogonal to logon support.</P
-><P
->Issues related to the single-logon network model are discussed in this
-section.  Samba supports domain logons, network logon scripts, and user
-profiles for MS Windows for workgroups and MS Windows 9X/ME clients
-which are the focus of this section.</P
-><P
->When an SMB client in a domain wishes to logon it broadcast requests for a
-logon server.  The first one to reply gets the job, and validates its
-password using whatever mechanism the Samba administrator has installed.
-It is possible (but very stupid) to create a domain where the user
-database is not shared between servers, i.e. they are effectively workgroup
-servers advertising themselves as participating in a domain.  This
-demonstrates how authentication is quite different from but closely
-involved with domains.</P
-><P
->Using these features you can make your clients verify their logon via
-the Samba server; make clients run a batch file when they logon to
-the network and download their preferences, desktop and start menu.</P
-><P
->Before launching into the configuration instructions, it is 
-worthwhile lookingat how a Windows 9x/ME client performs a logon:</P
+>You must use at least the following 3 options in smb.conf:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  realm = YOUR.KERBEROS.REALM
+  security = ADS
+  encrypt passwords = yes</PRE
 ></P
-><OL
-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
-	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.
-	</P
-></LI
-><LI
-><P
->	The client then connects to that server, logs on (does an SMBsessetupX) and
-	then connects to the IPC$ share (using an SMBtconX).
-	</P
-></LI
-><LI
-><P
->	The client then does a NetWkstaUserLogon request, which retrieves the name
-	of the user's logon script. 
-	</P
-></LI
-><LI
-><P
->	The client then connects to the NetLogon share and searches for this 	
-	and if it is found and can be read, is retrieved and executed by the client.
-	After this, the client disconnects from the NetLogon share.
-	</P
-></LI
-><LI
-><P
->	The client then sends a NetUserGetInfo request to the server, to retrieve
-	the user's home share, which is used to search for profiles. Since the
-	response to the NetUserGetInfo request does not contain much more 	
-	the user's home share, profiles for Win9X clients MUST reside in the user
-	home directory.
-	</P
-></LI
-><LI
-><P
->	The client then connects to the user's home share and searches for the 
-	user's profile. As it turns out, you can specify the user's home share as
-	a sharename and path. For example, \\server\fred\.profile.
-	If the profiles are found, they are implemented.
-	</P
-></LI
-><LI
-><P
->	The client then disconnects from the user's home share, and reconnects to
-	the NetLogon share and looks for CONFIG.POL, the policies file. If this is
-	found, it is read and implemented.
-	</P
-></LI
-></OL
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1256"
->6.7.1. Configuration Instructions:	Network Logons</A
-></H3
-><P
->The main difference between a PDC and a Windows 9x logon 
-server configuration is that</P
 ><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
-><UL
-><LI
-><P
->Password encryption is not required for a Windows 9x logon server.</P
-></LI
-><LI
-><P
->Windows 9x/ME clients do not possess machine trust accounts.</P
-></LI
-></UL
-><P
->Therefore, a Samba PDC will also act as a Windows 9x logon 
-server.</P
 ><DIV
-CLASS="WARNING"
+CLASS="NOTE"
 ><P
 ></P
 ><TABLE
-CLASS="WARNING"
+CLASS="NOTE"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -6543,439 +6481,65 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
 HSPACE="5"
-ALT="Warning"></TD
-><TH
-ALIGN="LEFT"
-VALIGN="CENTER"
-><B
->security mode and master browsers</B
-></TH
-></TR
-><TR
-><TD
->&nbsp;</TD
+ALT="Note"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->There are a few comments to make in order to tie up some 
-loose ends.  There has been much debate over the issue of whether
-or not it is ok to configure Samba as a Domain Controller in security
-modes other than <CODE
-CLASS="CONSTANT"
->USER</CODE
->.  The only security mode 
-which  will not work due to technical reasons is <CODE
-CLASS="CONSTANT"
->SHARE</CODE
->
-mode security.  <CODE
-CLASS="CONSTANT"
->DOMAIN</CODE
-> and <CODE
-CLASS="CONSTANT"
->SERVER</CODE
->
-mode security is really just a variation on SMB user level security.</P
-><P
->Actually, this issue is also closely tied to the debate on whether 
-or not Samba must be the domain master browser for its workgroup
-when operating as a DC.  While it may technically be possible
-to configure a server as such (after all, browsing and domain logons
-are two distinctly different functions), it is not a good idea to
-so.  You should remember that the DC must register the DOMAIN#1b NetBIOS 
-name.  This is the name used by Windows clients to locate the DC.
-Windows clients do not distinguish between the DC and the DMB.
-For this reason, it is very wise to configure the Samba DC as the DMB.</P
-><P
->Now back to the issue of configuring a Samba DC to use a mode other
-than "security = user".  If a Samba host is configured to use 
-another SMB server or DC in order to validate user connection 
-requests, then it is a fact that some other machine on the network 
-(the "password server") knows more about user than the Samba host.
-99% of the time, this other host is a domain controller.  Now 
-in order to operate in domain mode security, the "workgroup" parameter
-must be set to the name of the Windows NT domain (which already 
-has a domain controller, right?)</P
-><P
->Therefore configuring a Samba box as a DC for a domain that 
-already by definition has a PDC is asking for trouble.
-Therefore, you should always configure the Samba DC to be the DMB
-for its domain.</P
+>You do *not* need a smbpasswd file, and older clients will
+  be authenticated as if <B
+CLASS="COMMAND"
+>security = domain</B
+>,
+  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
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="SAMBA-BDC"
-></A
->Chapter 7. Samba Backup Domain Controller to Samba Domain Control</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN1286"
->7.1. Prerequisite Reading</A
-></H2
-><P
->Before you continue reading in this chapter, please make sure
-that you are comfortable with configuring a Samba PDC
-as described in the <A
-HREF="Samba-PDC-HOWTO.html"
-TARGET="_top"
->Samba-PDC-HOWTO</A
->.</P
-></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1290"
->7.2. Background</A
+NAME="AEN1377"
+>9.2. Setup your <TT
+CLASS="FILENAME"
+>/etc/krb5.conf</TT
+></A
 ></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
-user logs into a Windows NT Workstation, the workstation connects to a
-Domain Controller and asks him whether the username and password the
-user typed in is correct.  The Domain Controller replies with a lot of
-information about the user, for example the place where the users
-profile is stored, the users full name of the user. All this
-information is stored in the NT user database, the so-called SAM.</P
-><P
->There are two kinds of Domain Controller in a NT 4 compatible Domain:
-A Primary Domain Controller (PDC) and one or more Backup Domain
-Controllers (BDC). The PDC contains the master copy of the
-SAM. Whenever the SAM has to change, for example when a user changes
-his password, this change has to be done on the PDC. A Backup Domain
-Controller is a machine that maintains a read-only copy of the
-SAM. This way it is able to reply to logon requests and authenticate
-users in case the PDC is not available. During this time no changes to
-the SAM are possible. Whenever changes to the SAM are done on the PDC,
-all BDC receive the changes from the PDC.</P
-><P
->Since version 2.2 Samba officially supports domain logons for all
-current Windows Clients, including Windows 2000 and XP. This text
-assumes the domain to be named SAMBA. To be able to act as a PDC, some
-parameters in the [global]-section of the smb.conf have to be set:</P
+>The minimal configuration for <TT
+CLASS="FILENAME"
+>krb5.conf</TT
+> is:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->workgroup = SAMBA
-domain master = yes
-domain logons = yes</PRE
+>[realms]
+    YOUR.KERBEROS.REALM = {
+	kdc = your.kerberos.server
+    }</PRE
 ></P
 ><P
->Several other things like a [homes] and a [netlogon] share also may be
-set along with settings for the profile path, the users home drive and
-others. This will not be covered in this document.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1298"
->7.3. What qualifies a Domain Controller on the network?</A
-></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
-by broadcast on the local network. The PDC also registers the unique
-NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
-normally reserved for the domain master browser, a role that has
-nothing to do with anything related to authentication, but the
-Microsoft Domain implementation requires the domain master browser to
-be on the same machine as the PDC.</P
+>Test your config by doing a <KBD
+CLASS="USERINPUT"
+>kinit <VAR
+CLASS="REPLACEABLE"
+>USERNAME</VAR
+>@<VAR
+CLASS="REPLACEABLE"
+>REALM</VAR
+></KBD
+> and making sure that
+  your password is accepted by the Win2000 KDC. </P
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1301"
->7.3.1. How does a Workstation find its domain controller?</A
-></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
-this by doing a NetBIOS name query for the group name SAMBA#1c. It
-assumes that each of the machines it gets back from the queries is a
-domain controller and can answer logon requests. To not open security
-holes both the workstation and the selected (TODO: How is the DC
-chosen) domain controller authenticate each other. After that the
-workstation sends the user's credentials (his name and password) to
-the domain controller, asking for approval.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1304"
->7.3.2. When is the PDC needed?</A
-></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
-for SAMBA#1b, assuming this machine maintains the master copy of the
-SAM. The workstation contacts the PDC, both mutually authenticate and
-the password change is done.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1307"
->7.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
-></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
-service logon requests whenever the PDC is down.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1312"
->7.5. How do I set up a Samba BDC?</A
-></H2
-><P
->Several things have to be done:</P
-><P
-></P
-><UL
-><LI
-><P
->The domain SID has to be the same on the PDC and the BDC. This used to
-be stored in the file private/MACHINE.SID. This file is not created
-anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
-stored in the file private/secrets.tdb. Simply copying the secrets.tdb
-from the PDC to the BDC does not work, as the BDC would
-generate a new SID for itself and override the domain SID with this
-new BDC SID.</P
-><P
->To retrieve the domain SID from the PDC or an existing BDC and store it in the
-secrets.tdb, execute 'net rpc getsid' on the BDC.</P
-></LI
-><LI
-><P
->The Unix user database has to be synchronized from the PDC to the
-BDC. This means that both the /etc/passwd and /etc/group have to be
-replicated from the PDC to the BDC. This can be done manually
-whenever changes are made, or the PDC is set up as a NIS master
-server and the BDC as a NIS slave server. To set up the BDC as a
-mere NIS client would not be enough, as the BDC would not be able to
-access its user database in case of a PDC failure.</P
-></LI
-><LI
-><P
->The Samba password database in the file private/smbpasswd has to be
-replicated from the PDC to the BDC. This is a bit tricky, see the
-next section.</P
-></LI
-><LI
-><P
->Any netlogon share has to be replicated from the PDC to the
-BDC. This can be done manually whenever login scripts are changed,
-or it can be done automatically together with the smbpasswd
-synchronization.</P
-></LI
-></UL
-><P
->Finally, the BDC has to be found by the workstations. This can be done
-by setting</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->workgroup = samba
-domain master = no
-domain logons = yes</PRE
-></P
-><P
->in the [global]-section of the smb.conf of the BDC. This makes the BDC
-only register the name SAMBA#1c with the WINS server. This is no
-problem as the name SAMBA#1c is a NetBIOS group name that is meant to
-be registered by more than one machine. The parameter 'domain master =
-no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
-name is reserved for the Primary Domain Controller.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1329"
->7.5.1. How do I replicate the smbpasswd file?</A
-></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
-done in the smbpasswd file and has to be replicated to the BDC. So
-replicating the smbpasswd file very often is necessary.</P
-><P
->As the smbpasswd file contains plain text password equivalents, it
-must not be sent unencrypted over the wire. The best way to set up
-smbpasswd replication from the PDC to the BDC is to use the utility
-rsync. rsync can use ssh as a transport. ssh itself can be set up to
-accept *only* rsync transfer without requiring the user to type a
-password.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1333"
->7.5.2. Can I do this all with LDAP?</A
-></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
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="ADS"
-></A
->Chapter 8. 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
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1355"
->8.1. Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
-></H2
-><P
->You must use at least the following 3 options in smb.conf:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->  realm = YOUR.KERBEROS.REALM
-  security = ADS
-  encrypt passwords = yes</PRE
-></P
-><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
-><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
->You do *not* need a smbpasswd file, and older clients will
-  be authenticated as if <B
-CLASS="COMMAND"
->security = domain</B
->,
-  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
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1368"
->8.2. Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
-></H2
-><P
->The minimal configuration for <TT
-CLASS="FILENAME"
->krb5.conf</TT
-> is:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[realms]
-    YOUR.KERBEROS.REALM = {
-	kdc = your.kerberos.server
-    }</PRE
-></P
-><P
->Test your config by doing a <KBD
-CLASS="USERINPUT"
->kinit <VAR
-CLASS="REPLACEABLE"
->USERNAME</VAR
->@<VAR
-CLASS="REPLACEABLE"
->REALM</VAR
-></KBD
-> and making sure that
-  your password is accepted by the Win2000 KDC. </P
-><DIV
-CLASS="NOTE"
+CLASS="NOTE"
 ><P
 ></P
 ><TABLE
@@ -7049,7 +6613,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-CREATE-MACHINE-ACCOUNT"
->8.3. Create the computer account</A
+>9.3. Create the computer account</A
 ></H2
 ><P
 >As a user that has write permission on the Samba private directory
@@ -7063,8 +6627,8 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN1396"
->8.3.1. Possible errors</A
+NAME="AEN1405"
+>9.3.1. Possible errors</A
 ></H3
 ><P
 ><P
@@ -7089,7 +6653,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-TEST-SERVER"
->8.4. Test your server setup</A
+>9.4. Test your server setup</A
 ></H2
 ><P
 >On a Windows 2000 client try <KBD
@@ -7109,7 +6673,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-TEST-SMBCLIENT"
->8.5. Testing with <SPAN
+>9.5. Testing with <SPAN
 CLASS="APPLICATION"
 >smbclient</SPAN
 ></A
@@ -7133,8 +6697,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1416"
->8.6. Notes</A
+NAME="AEN1425"
+>9.6. Notes</A
 ></H2
 ><P
 >You must change administrator password at least once after DC 
@@ -7148,16 +6712,16 @@ install, to create the right encoding types</P
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="DOMAIN-SECURITY"
+NAME="DOMAIN-MEMBER"
 ></A
->Chapter 9. Samba as a NT4 or Win2k domain member</H1
+>Chapter 10. Samba as a NT4 or Win2k domain member</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1439"
->9.1. Joining an NT Domain with Samba 3.0</A
+NAME="AEN1448"
+>10.1. Joining an NT Domain with Samba 3.0</A
 ></H2
 ><P
 >Assume you have a Samba 3.0 server with a NetBIOS name of 
@@ -7338,8 +6902,8 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN1493"
->9.2. Why is this better than security = server?</A
+NAME="AEN1502"
+>10.2. Why is this better than security = server?</A
 ></H2
 ><P
 >Currently, domain security in Samba doesn't free you from 
@@ -7447,10 +7011,11 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >III. Advanced Configuration</H1
+></DIV
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN1511"
+NAME="AEN1520"
 ></A
 ><H1
 >Introduction</H1
@@ -7458,5032 +7023,1098 @@ NAME="AEN1511"
 >Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.</P
 ></DIV
 ><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->10. <A
-HREF="#UNIX-PERMISSIONS"
->UNIX Permission Bits and Windows NT Access Control Lists</A
-></DT
-><DD
-><DL
-><DT
->10.1. <A
-HREF="#AEN1525"
->Viewing and changing UNIX permissions using the NT 
-	security dialogs</A
-></DT
-><DT
->10.2. <A
-HREF="#AEN1531"
->How to view file security on a Samba share</A
-></DT
-><DT
->10.3. <A
-HREF="#AEN1542"
->Viewing file ownership</A
-></DT
-><DT
->10.4. <A
-HREF="#AEN1562"
->Viewing file or directory permissions</A
-></DT
-><DD
-><DL
-><DT
->10.4.1. <A
-HREF="#AEN1577"
->File Permissions</A
-></DT
-><DT
->10.4.2. <A
-HREF="#AEN1591"
->Directory Permissions</A
-></DT
-></DL
-></DD
-><DT
->10.5. <A
-HREF="#AEN1598"
->Modifying file or directory permissions</A
-></DT
-><DT
->10.6. <A
-HREF="#AEN1620"
->Interaction with the standard Samba create mask 
-	parameters</A
-></DT
-><DT
->10.7. <A
-HREF="#AEN1673"
->Interaction with the standard Samba file attribute 
-	mapping</A
-></DT
-></DL
-></DD
-><DT
->11. <A
-HREF="#GROUPMAPPING"
->Configuring Group Mapping</A
-></DT
-><DT
->12. <A
-HREF="#PRINTING"
->Printing Support</A
-></DT
-><DD
-><DL
-><DT
->12.1. <A
-HREF="#AEN1736"
->Introduction</A
-></DT
-><DT
->12.2. <A
-HREF="#AEN1758"
->Configuration</A
-></DT
-><DD
-><DL
-><DT
->12.2.1. <A
-HREF="#AEN1766"
->Creating [print$]</A
-></DT
-><DT
->12.2.2. <A
-HREF="#AEN1801"
->Setting Drivers for Existing Printers</A
-></DT
-><DT
->12.2.3. <A
-HREF="#AEN1817"
->Support a large number of printers</A
-></DT
-><DT
->12.2.4. <A
-HREF="#AEN1832"
->Adding New Printers via the Windows NT APW</A
-></DT
-><DT
->12.2.5. <A
-HREF="#AEN1862"
->Samba and Printer Ports</A
-></DT
-></DL
-></DD
-><DT
->12.3. <A
-HREF="#AEN1870"
->The Imprints Toolset</A
-></DT
-><DD
-><DL
-><DT
->12.3.1. <A
-HREF="#AEN1874"
->What is Imprints?</A
-></DT
-><DT
->12.3.2. <A
-HREF="#AEN1884"
->Creating Printer Driver Packages</A
-></DT
-><DT
->12.3.3. <A
-HREF="#AEN1887"
->The Imprints server</A
-></DT
-><DT
->12.3.4. <A
-HREF="#AEN1891"
->The Installation Client</A
-></DT
-></DL
-></DD
-><DT
->12.4. <A
-HREF="#AEN1913"
->Diagnosis</A
-></DT
-><DD
-><DL
-><DT
->12.4.1. <A
-HREF="#AEN1915"
->Introduction</A
-></DT
-><DT
->12.4.2. <A
-HREF="#AEN1931"
->Debugging printer problems</A
-></DT
-><DT
->12.4.3. <A
-HREF="#AEN1940"
->What printers do I have?</A
-></DT
-><DT
->12.4.4. <A
-HREF="#AEN1948"
->Setting up printcap and print servers</A
-></DT
-><DT
->12.4.5. <A
-HREF="#AEN1976"
->Job sent, no output</A
-></DT
-><DT
->12.4.6. <A
-HREF="#AEN1987"
->Job sent, strange output</A
-></DT
-><DT
->12.4.7. <A
-HREF="#AEN1999"
->Raw PostScript printed</A
-></DT
-><DT
->12.4.8. <A
-HREF="#AEN2002"
->Advanced Printing</A
-></DT
-><DT
->12.4.9. <A
-HREF="#AEN2005"
->Real debugging</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->13. <A
-HREF="#CUPS-PRINTING"
->CUPS Printing Support</A
-></DT
-><DD
-><DL
-><DT
->13.1. <A
-HREF="#AEN2025"
->Introduction</A
-></DT
-><DT
->13.2. <A
-HREF="#AEN2032"
->Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></DT
-><DT
->13.3. <A
-HREF="#AEN2052"
->CUPS - RAW Print Through Mode</A
-></DT
-><DT
->13.4. <A
-HREF="#AEN2111"
->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></DT
-><DT
->13.5. <A
-HREF="#AEN2132"
->Windows Terminal Servers (WTS) as CUPS clients</A
-></DT
-><DT
->13.6. <A
-HREF="#AEN2136"
->Setting up CUPS for driver download</A
-></DT
-><DT
->13.7. <A
-HREF="#AEN2149"
->Sources of CUPS drivers / PPDs</A
-></DT
-><DD
-><DL
-><DT
->13.7.1. <A
-HREF="#AEN2176"
-><B
-CLASS="COMMAND"
->cupsaddsmb</B
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="UNIX-PERMISSIONS"
 ></A
-></DT
-></DL
-></DD
-><DT
->13.8. <A
-HREF="#AEN2205"
->The CUPS Filter Chains</A
-></DT
-><DT
->13.9. <A
-HREF="#AEN2244"
->CUPS Print Drivers and Devices</A
-></DT
-><DD
-><DL
-><DT
->13.9.1. <A
-HREF="#AEN2251"
->Further printing steps</A
-></DT
-></DL
-></DD
-><DT
->13.10. <A
-HREF="#AEN2321"
->Limiting the number of pages users can print</A
-></DT
-><DT
->13.11. <A
-HREF="#AEN2417"
->Advanced Postscript Printing from MS Windows</A
-></DT
-><DT
->13.12. <A
-HREF="#AEN2432"
->Auto-Deletion of CUPS spool files</A
-></DT
-></DL
-></DD
-><DT
->14. <A
-HREF="#WINBIND"
->Unified Logons between Windows NT and UNIX using Winbind</A
-></DT
-><DD
-><DL
-><DT
->14.1. <A
-HREF="#AEN2506"
->Abstract</A
-></DT
-><DT
->14.2. <A
-HREF="#AEN2510"
->Introduction</A
-></DT
-><DT
->14.3. <A
-HREF="#AEN2523"
->What Winbind Provides</A
-></DT
-><DD
-><DL
-><DT
->14.3.1. <A
-HREF="#AEN2530"
->Target Uses</A
-></DT
-></DL
-></DD
-><DT
->14.4. <A
-HREF="#AEN2534"
->How Winbind Works</A
-></DT
-><DD
-><DL
-><DT
->14.4.1. <A
-HREF="#AEN2539"
->Microsoft Remote Procedure Calls</A
-></DT
-><DT
->14.4.2. <A
-HREF="#AEN2543"
->Microsoft Active Directory Services</A
-></DT
-><DT
->14.4.3. <A
-HREF="#AEN2546"
->Name Service Switch</A
-></DT
-><DT
->14.4.4. <A
-HREF="#AEN2562"
->Pluggable Authentication Modules</A
-></DT
-><DT
->14.4.5. <A
-HREF="#AEN2570"
->User and Group ID Allocation</A
-></DT
-><DT
->14.4.6. <A
-HREF="#AEN2574"
->Result Caching</A
-></DT
-></DL
-></DD
-><DT
->14.5. <A
-HREF="#AEN2577"
->Installation and Configuration</A
-></DT
-><DD
-><DL
-><DT
->14.5.1. <A
-HREF="#AEN2582"
->Introduction</A
-></DT
-><DT
->14.5.2. <A
-HREF="#AEN2595"
->Requirements</A
-></DT
-><DT
->14.5.3. <A
-HREF="#AEN2609"
->Testing Things Out</A
-></DT
-></DL
-></DD
-><DT
->14.6. <A
-HREF="#AEN2834"
->Limitations</A
-></DT
-><DT
->14.7. <A
-HREF="#AEN2844"
->Conclusion</A
-></DT
-></DL
-></DD
-><DT
->15. <A
-HREF="#ADVANCEDNETWORKMANAGEMENT"
->Advanced Network Manangement</A
-></DT
-><DD
-><DL
-><DT
->15.1. <A
-HREF="#AEN2859"
->Configuring Samba Share Access Controls</A
-></DT
-><DD
-><DL
-><DT
->15.1.1. <A
-HREF="#AEN2869"
->Share Permissions Management</A
-></DT
-></DL
-></DD
-><DT
->15.2. <A
-HREF="#AEN2897"
->Remote Server Administration</A
-></DT
-><DT
->15.3. <A
-HREF="#AEN2914"
->Network Logon Script Magic</A
-></DT
-></DL
-></DD
-><DT
->16. <A
-HREF="#POLICYMGMT"
->System and Account Policies</A
-></DT
-><DD
-><DL
-><DT
->16.1. <A
-HREF="#AEN2929"
->Creating and Managing System Policies</A
-></DT
-><DD
-><DL
-><DT
->16.1.1. <A
-HREF="#AEN2943"
->Windows 9x/Me Policies</A
-></DT
-><DT
->16.1.2. <A
-HREF="#AEN2955"
->Windows NT4 Style Policy Files</A
-></DT
-><DT
->16.1.3. <A
-HREF="#AEN2973"
->MS Windows 200x / XP Professional Policies</A
-></DT
-></DL
-></DD
-><DT
->16.2. <A
-HREF="#AEN3002"
->Managing Account/User Policies</A
-></DT
-><DD
-><DL
-><DT
->16.2.1. <A
-HREF="#AEN3017"
->With Windows NT4/200x</A
-></DT
-><DT
->16.2.2. <A
-HREF="#AEN3020"
->With a Samba PDC</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->17. <A
-HREF="#PROFILEMGMT"
->Desktop Profile Management</A
-></DT
-><DD
-><DL
-><DT
->17.1. <A
-HREF="#AEN3035"
->Roaming Profiles</A
-></DT
-><DD
-><DL
-><DT
->17.1.1. <A
-HREF="#AEN3042"
->Samba Configuration for Profile Handling</A
-></DT
-><DT
->17.1.2. <A
-HREF="#AEN3077"
->Windows Client Profile Configuration Information</A
-></DT
-><DT
->17.1.3. <A
-HREF="#AEN3197"
->Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
-></DT
-><DT
->17.1.4. <A
-HREF="#AEN3204"
->Profile Migration from Windows NT4/200x Server to Samba</A
-></DT
-></DL
-></DD
-><DT
->17.2. <A
-HREF="#AEN3242"
->Mandatory profiles</A
-></DT
-><DT
->17.3. <A
-HREF="#AEN3249"
->Creating/Managing Group Profiles</A
-></DT
-><DT
->17.4. <A
-HREF="#AEN3255"
->Default Profile for Windows Users</A
-></DT
-><DD
-><DL
-><DT
->17.4.1. <A
-HREF="#AEN3259"
->MS Windows 9x/Me</A
-></DT
-><DT
->17.4.2. <A
-HREF="#AEN3271"
->MS Windows NT4 Workstation</A
-></DT
-><DT
->17.4.3. <A
-HREF="#AEN3325"
->MS Windows 200x/XP</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->18. <A
-HREF="#INTERDOMAINTRUSTS"
->Interdomain Trust Relationships</A
-></DT
-><DD
-><DL
-><DT
->18.1. <A
-HREF="#AEN3386"
->Trust Relationship Background</A
-></DT
-><DT
->18.2. <A
-HREF="#AEN3395"
->MS Windows NT4 Trust Configuration</A
-></DT
-><DD
-><DL
-><DT
->18.2.1. <A
-HREF="#AEN3398"
->NT4 as the Trusting Domain</A
-></DT
-><DT
->18.2.2. <A
-HREF="#AEN3401"
->NT4 as the Trusted Domain</A
-></DT
-></DL
-></DD
-><DT
->18.3. <A
-HREF="#AEN3405"
->Configuring Samba Domain Trusts</A
-></DT
-><DD
-><DL
-><DT
->18.3.1. <A
-HREF="#AEN3409"
->Samba3 as the Trusting Domain</A
-></DT
-><DT
->18.3.2. <A
-HREF="#AEN3416"
->Samba3 as the Trusted Domain</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->19. <A
-HREF="#PAM"
->PAM Configuration for Centrally Managed Authentication</A
-></DT
-><DD
-><DL
-><DT
->19.1. <A
-HREF="#AEN3440"
->Samba and PAM</A
-></DT
-><DT
->19.2. <A
-HREF="#AEN3491"
->Distributed Authentication</A
-></DT
-><DT
->19.3. <A
-HREF="#AEN3496"
->PAM Configuration in smb.conf</A
-></DT
-></DL
-></DD
-><DT
->20. <A
-HREF="#VFS"
->Stackable VFS modules</A
-></DT
-><DD
-><DL
-><DT
->20.1. <A
-HREF="#AEN3531"
->Introduction and configuration</A
-></DT
-><DT
->20.2. <A
-HREF="#AEN3540"
->Included modules</A
-></DT
-><DD
-><DL
-><DT
->20.2.1. <A
-HREF="#AEN3542"
->audit</A
-></DT
-><DT
->20.2.2. <A
-HREF="#AEN3550"
->extd_audit</A
-></DT
-><DT
->20.2.3. <A
-HREF="#AEN3554"
->recycle</A
-></DT
-><DT
->20.2.4. <A
-HREF="#AEN3591"
->netatalk</A
-></DT
-></DL
-></DD
-><DT
->20.3. <A
-HREF="#AEN3598"
->VFS modules available elsewhere</A
-></DT
-><DD
-><DL
-><DT
->20.3.1. <A
-HREF="#AEN3602"
->DatabaseFS</A
-></DT
-><DT
->20.3.2. <A
-HREF="#AEN3610"
->vscan</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->21. <A
-HREF="#MSDFS"
->Hosting a Microsoft Distributed File System tree on Samba</A
-></DT
-><DD
-><DL
-><DT
->21.1. <A
-HREF="#AEN3626"
->Instructions</A
-></DT
-><DD
-><DL
-><DT
->21.1.1. <A
-HREF="#AEN3661"
->Notes</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->22. <A
-HREF="#INTEGRATE-MS-NETWORKS"
->Integrating MS Windows networks with Samba</A
-></DT
-><DD
-><DL
-><DT
->22.1. <A
-HREF="#AEN3688"
->Name Resolution in a pure Unix/Linux world</A
-></DT
-><DD
-><DL
-><DT
->22.1.1. <A
-HREF="#AEN3704"
-><TT
-CLASS="FILENAME"
->/etc/hosts</TT
-></A
-></DT
-><DT
->22.1.2. <A
-HREF="#AEN3720"
-><TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
-></A
-></DT
-><DT
->22.1.3. <A
-HREF="#AEN3731"
-><TT
-CLASS="FILENAME"
->/etc/host.conf</TT
-></A
-></DT
-><DT
->22.1.4. <A
-HREF="#AEN3739"
-><TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-></A
-></DT
-></DL
-></DD
-><DT
->22.2. <A
-HREF="#AEN3751"
->Name resolution as used within MS Windows networking</A
-></DT
-><DD
-><DL
-><DT
->22.2.1. <A
-HREF="#AEN3763"
->The NetBIOS Name Cache</A
-></DT
-><DT
->22.2.2. <A
-HREF="#AEN3768"
->The LMHOSTS file</A
-></DT
-><DT
->22.2.3. <A
-HREF="#AEN3776"
->HOSTS file</A
-></DT
-><DT
->22.2.4. <A
-HREF="#AEN3781"
->DNS Lookup</A
-></DT
-><DT
->22.2.5. <A
-HREF="#AEN3784"
->WINS Lookup</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->23. <A
-HREF="#IMPROVED-BROWSING"
->Improved browsing in samba</A
-></DT
-><DD
-><DL
-><DT
->23.1. <A
-HREF="#AEN3804"
->Overview of browsing</A
-></DT
-><DT
->23.2. <A
-HREF="#AEN3810"
->Browsing support in samba</A
-></DT
-><DT
->23.3. <A
-HREF="#AEN3825"
->Problem resolution</A
-></DT
-><DT
->23.4. <A
-HREF="#AEN3837"
->Browsing across subnets</A
-></DT
-><DD
-><DL
-><DT
->23.4.1. <A
-HREF="#AEN3843"
->How does cross subnet browsing work ?</A
-></DT
-></DL
-></DD
-><DT
->23.5. <A
-HREF="#AEN3878"
->Setting up a WINS server</A
-></DT
-><DT
->23.6. <A
-HREF="#AEN3901"
->Setting up Browsing in a WORKGROUP</A
-></DT
-><DT
->23.7. <A
-HREF="#AEN3927"
->Setting up Browsing in a DOMAIN</A
-></DT
-><DT
->23.8. <A
-HREF="#BROWSE-FORCE-MASTER"
->Forcing samba to be the master</A
-></DT
-><DT
->23.9. <A
-HREF="#AEN3962"
->Making samba the domain master</A
-></DT
-><DT
->23.10. <A
-HREF="#AEN3984"
->Note about broadcast addresses</A
-></DT
-><DT
->23.11. <A
-HREF="#AEN3987"
->Multiple interfaces</A
-></DT
-></DL
-></DD
-><DT
->24. <A
-HREF="#SECURING-SAMBA"
->Securing Samba</A
-></DT
-><DD
-><DL
-><DT
->24.1. <A
-HREF="#AEN4003"
->Introduction</A
-></DT
-><DT
->24.2. <A
-HREF="#AEN4006"
->Using host based protection</A
-></DT
-><DT
->24.3. <A
-HREF="#AEN4016"
->Using interface protection</A
-></DT
-><DT
->24.4. <A
-HREF="#AEN4025"
->Using a firewall</A
-></DT
-><DT
->24.5. <A
-HREF="#AEN4032"
->Using a IPC$ share deny</A
-></DT
-><DT
->24.6. <A
-HREF="#AEN4041"
->Upgrading Samba</A
-></DT
-></DL
-></DD
-><DT
->25. <A
-HREF="#UNICODE"
->Unicode/Charsets</A
-></DT
-><DD
-><DL
-><DT
->25.1. <A
-HREF="#AEN4056"
->What are charsets and unicode?</A
-></DT
-><DT
->25.2. <A
-HREF="#AEN4065"
->Samba and charsets</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="UNIX-PERMISSIONS"
-></A
->Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN1525"
->10.1. Viewing and changing UNIX permissions using the NT 
-	security dialogs</A
-></H2
-><P
->Windows NT clients can use their native security settings 
-	dialog box to view and modify the underlying UNIX permissions.</P
-><P
->Note that this ability is careful not to compromise 
-	the security of the UNIX host Samba is running on, and 
-	still obeys all the file permission rules that a Samba 
-	administrator can set.</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
->	All access to Unix/Linux system file via Samba is controlled at
-	the operating system file access control level. When trying to
-	figure out file access problems it is vitally important to identify
-	the identity of the Windows user as it is presented by Samba at
-	the point of file access. This can best be determined from the
-	Samba log files.
-	</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1531"
->10.2. How to view file security on a Samba share</A
-></H2
-><P
->From an NT4/2000/XP client, single-click with the right 
-	mouse button on any file or directory in a Samba mounted 
-	drive letter or UNC path. When the menu pops-up, click 
-	on the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Properties</I
-></SPAN
-> entry at the bottom of 
-	the menu. This brings up the file properties dialog
-	box. Click on the tab <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Security</I
-></SPAN
-> and you 
-	will see three buttons, <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Permissions</I
-></SPAN
->, 	
-	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Auditing</I
-></SPAN
->, and <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Ownership</I
-></SPAN
->. 
-	The <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Auditing</I
-></SPAN
-> button will cause either 
-	an error message <SPAN
-CLASS="ERRORNAME"
->A requested privilege is not held 
-	by the client</SPAN
-> to appear if the user is not the 
-	NT Administrator, or a dialog which is intended to allow an 
-	Administrator to add auditing requirements to a file if the 
-	user is logged on as the NT Administrator. This dialog is 
-	non-functional with a Samba share at this time, as the only 
-	useful button, the <B
-CLASS="COMMAND"
->Add</B
-> button will not currently 
-	allow a list of users to be seen.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1542"
->10.3. Viewing file ownership</A
-></H2
-><P
->Clicking on the <B
-CLASS="COMMAND"
->"Ownership"</B
-> button 
-	brings up a dialog box telling you who owns the given file. The 
-	owner name will be of the form :</P
-><P
-><B
-CLASS="COMMAND"
->"SERVER\user (Long name)"</B
-></P
-><P
->Where <VAR
-CLASS="REPLACEABLE"
->SERVER</VAR
-> is the NetBIOS name of 
-	the Samba server, <VAR
-CLASS="REPLACEABLE"
->user</VAR
-> is the user name of 
-	the UNIX user who owns the file, and <VAR
-CLASS="REPLACEABLE"
->(Long name)</VAR
->
-	is the descriptive string identifying the user (normally found in the
-	GECOS field of the UNIX password database). Click on the <B
-CLASS="COMMAND"
->Close
-	</B
-> button to remove this dialog.</P
-><P
->If the parameter <VAR
-CLASS="PARAMETER"
->nt acl support</VAR
->
-	is set to <CODE
-CLASS="CONSTANT"
->false</CODE
-> then the file owner will 
-	be shown as the NT user <B
-CLASS="COMMAND"
->"Everyone"</B
->.</P
-><P
->The <B
-CLASS="COMMAND"
->Take Ownership</B
-> button will not allow 
-	you to change the ownership of this file to yourself (clicking on 
-	it will display a dialog box complaining that the user you are 
-	currently logged onto the NT client cannot be found). The reason 
-	for this is that changing the ownership of a file is a privileged 
-	operation in UNIX, available only to the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->root</I
-></SPAN
-> 
-	user. As clicking on this button causes NT to attempt to change 
-	the ownership of a file to the current user logged into the NT 
-	client this will not work with Samba at this time.</P
-><P
->There is an NT chown command that will work with Samba 
-	and allow a user with Administrator privilege connected 
-	to a Samba server as root to change the ownership of 
-	files on both a local NTFS filesystem or remote mounted NTFS 
-	or Samba drive. This is available as part of the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Seclib
-	</I
-></SPAN
-> NT security library written by Jeremy Allison of 
-	the Samba Team, available from the main Samba ftp site.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1562"
->10.4. Viewing file or directory permissions</A
-></H2
-><P
->The third button is the <B
-CLASS="COMMAND"
->"Permissions"</B
-> 
-	button. Clicking on this brings up a dialog box that shows both 
-	the permissions and the UNIX owner of the file or directory. 
-	The owner is displayed in the form :</P
-><P
-><B
-CLASS="COMMAND"
->"SERVER\user (Long name)"</B
-></P
-><P
->Where <VAR
-CLASS="REPLACEABLE"
->SERVER</VAR
-> is the NetBIOS name of 
-	the Samba server, <VAR
-CLASS="REPLACEABLE"
->user</VAR
-> is the user name of 
-	the UNIX user who owns the file, and <VAR
-CLASS="REPLACEABLE"
->(Long name)</VAR
->
-	is the descriptive string identifying the user (normally found in the
-	GECOS field of the UNIX password database).</P
-><P
->If the parameter <VAR
-CLASS="PARAMETER"
->nt acl support</VAR
->
-	is set to <CODE
-CLASS="CONSTANT"
->false</CODE
-> then the file owner will 
-	be shown as the NT user <B
-CLASS="COMMAND"
->"Everyone"</B
-> and the 
-	permissions will be shown as NT "Full Control".</P
-><P
->The permissions field is displayed differently for files 
-	and directories, so I'll describe the way file permissions 
-	are displayed first.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1577"
->10.4.1. File Permissions</A
-></H3
-><P
->The standard UNIX user/group/world triple and 
-		the corresponding "read", "write", "execute" permissions 
-		triples are mapped by Samba into a three element NT ACL 
-		with the 'r', 'w', and 'x' bits mapped into the corresponding 
-		NT permissions. The UNIX world permissions are mapped into 
-		the global NT group <B
-CLASS="COMMAND"
->Everyone</B
->, followed 
-		by the list of permissions allowed for UNIX world. The UNIX 
-		owner and group permissions are displayed as an NT 
-		<B
-CLASS="COMMAND"
->user</B
-> icon and an NT <B
-CLASS="COMMAND"
->local 
-		group</B
-> icon respectively followed by the list 
-	 	of permissions allowed for the UNIX user and group.</P
-><P
->As many UNIX permission sets don't map into common 
-		NT names such as <B
-CLASS="COMMAND"
->"read"</B
->, <B
-CLASS="COMMAND"
->		"change"</B
-> or <B
-CLASS="COMMAND"
->"full control"</B
-> then 
-		usually the permissions will be prefixed by the words <B
-CLASS="COMMAND"
->		"Special Access"</B
-> in the NT display list.</P
-><P
->But what happens if the file has no permissions allowed 
-		for a particular UNIX user group or world component ? In order 
-		to  allow "no permissions" to be seen and modified then Samba 
-		overloads the NT <B
-CLASS="COMMAND"
->"Take Ownership"</B
-> ACL attribute 
-		(which has no meaning in UNIX) and reports a component with 
-		no permissions as having the NT <B
-CLASS="COMMAND"
->"O"</B
-> bit set. 
-		This was chosen of course to make it look like a zero, meaning 
-		zero permissions. More details on the decision behind this will 
-		be given below.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1591"
->10.4.2. Directory Permissions</A
-></H3
-><P
->Directories on an NT NTFS file system have two 
-		different sets of permissions. The first set of permissions 
-		is the ACL set on the directory itself, this is usually displayed 
-		in the first set of parentheses in the normal <B
-CLASS="COMMAND"
->"RW"</B
-> 
-		NT style. This first set of permissions is created by Samba in 
-		exactly the same way as normal file permissions are, described 
-		above, and is displayed in the same way.</P
-><P
->The second set of directory permissions has no real meaning 
-		in the UNIX permissions world and represents the <B
-CLASS="COMMAND"
->		"inherited"</B
-> permissions that any file created within 
-		this directory would inherit.</P
-><P
->Samba synthesises these inherited permissions for NT by 
-		returning as an NT ACL the UNIX permission mode that a new file 
-		created by Samba on this share would receive.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1598"
->10.5. Modifying file or directory permissions</A
-></H2
-><P
->Modifying file and directory permissions is as simple 
-	as changing the displayed permissions in the dialog box, and 
-	clicking the <B
-CLASS="COMMAND"
->OK</B
-> button. However, there are 
-	limitations that a user needs to be aware of, and also interactions 
-	with the standard Samba permission masks and mapping of DOS 
-	attributes that need to also be taken into account.</P
-><P
->If the parameter <VAR
-CLASS="PARAMETER"
->nt acl support</VAR
->
-	is set to <CODE
-CLASS="CONSTANT"
->false</CODE
-> then any attempt to set 
-	security permissions will fail with an <B
-CLASS="COMMAND"
->"Access Denied"
-	</B
-> message.</P
-><P
->The first thing to note is that the <B
-CLASS="COMMAND"
->"Add"</B
-> 
-	button will not return a list of users in Samba (it will give 
-	an error message of <B
-CLASS="COMMAND"
->"The remote procedure call failed 
-	and did not execute"</B
->). This means that you can only 
-	manipulate the current user/group/world permissions listed in 
-	the dialog box. This actually works quite well as these are the 
-	only permissions that UNIX actually has.</P
-><P
->If a permission triple (either user, group, or world) 
-	is removed from the list of permissions in the NT dialog box, 
-	then when the <B
-CLASS="COMMAND"
->"OK"</B
-> button is pressed it will 
-	be applied as "no permissions" on the UNIX side. If you then 
-	view the permissions again the "no permissions" entry will appear 
-	as the NT <B
-CLASS="COMMAND"
->"O"</B
-> flag, as described above. This 
-	allows you to add permissions back to a file or directory once 
-	you have removed them from a triple component.</P
-><P
->As UNIX supports only the "r", "w" and "x" bits of 
-	an NT ACL then if other NT security attributes such as "Delete 
-	access" are selected then they will be ignored when applied on 
-	the Samba server.</P
-><P
->When setting permissions on a directory the second 
-	set of permissions (in the second set of parentheses) is 
-	by default applied to all files within that directory. If this 
-	is not what you want you must uncheck the <B
-CLASS="COMMAND"
->"Replace 
-	permissions on existing files"</B
-> checkbox in the NT 
-	dialog before clicking <B
-CLASS="COMMAND"
->"OK"</B
->.</P
-><P
->If you wish to remove all permissions from a 
-	user/group/world  component then you may either highlight the 
-	component and click the <B
-CLASS="COMMAND"
->"Remove"</B
-> button, 
-	or set the component to only have the special <B
-CLASS="COMMAND"
->"Take
-	Ownership"</B
-> permission (displayed as <B
-CLASS="COMMAND"
->"O"
-	</B
->) highlighted.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1620"
->10.6. Interaction with the standard Samba create mask 
-	parameters</A
-></H2
-><P
->There are four parameters 
-	to control interaction with the standard Samba create mask parameters.
-	These are :</P
-><P
-><VAR
-CLASS="PARAMETER"
->security mask</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->force security mode</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->directory security mask</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->force directory security mode</VAR
-></P
-><P
->Once a user clicks <B
-CLASS="COMMAND"
->"OK"</B
-> to apply the 
-	permissions Samba maps the given permissions into a user/group/world 
-	r/w/x triple set, and then will check the changed permissions for a 
-	file against the bits set in the <A
-HREF="smb.conf.5.html#SECURITYMASK"
-TARGET="_top"
-> 
-	<VAR
-CLASS="PARAMETER"
->security mask</VAR
-></A
-> parameter. Any bits that 
-	were changed that are not set to '1' in this parameter are left alone 
-	in the file permissions.</P
-><P
->Essentially, zero bits in the <VAR
-CLASS="PARAMETER"
->security mask</VAR
->
-	mask may be treated as a set of bits the user is <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not</I
-></SPAN
-> 
-	allowed to change, and one bits are those the user is allowed to change.
-	</P
-><P
->If not set explicitly this parameter is set to the same value as 
-	the <A
-HREF="smb.conf.5.html#CREATEMASK"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->create mask
-	</VAR
-></A
-> parameter. To allow a user to modify all the
-	user/group/world permissions on a file, set this parameter 
-	to 0777.</P
-><P
->Next Samba checks the changed permissions for a file against 
-	the bits set in the <A
-HREF="smb.conf.5.html#FORCESECURITYMODE"
-TARGET="_top"
->	<VAR
-CLASS="PARAMETER"
->force security mode</VAR
-></A
-> parameter. Any bits 
-	that were changed that correspond to bits set to '1' in this parameter 
-	are forced to be set.</P
-><P
->Essentially, bits set in the <VAR
-CLASS="PARAMETER"
->force security mode
-	</VAR
-> parameter may be treated as a set of bits that, when 
-	modifying security on a file, the user has always set to be 'on'.</P
-><P
->If not set explicitly this parameter is set to the same value 
-	as the <A
-HREF="smb.conf.5.html#FORCECREATEMODE"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->force 
-	create mode</VAR
-></A
-> parameter.
-	To allow a user to modify all the user/group/world permissions on a file
-	with no restrictions set this parameter to 000.</P
-><P
->The <VAR
-CLASS="PARAMETER"
->security mask</VAR
-> and <VAR
-CLASS="PARAMETER"
->force 
-	security mode</VAR
-> parameters are applied to the change 
-	request in that order.</P
-><P
->For a directory Samba will perform the same operations as 
-	described above for a file except using the parameter <VAR
-CLASS="PARAMETER"
->	directory security mask</VAR
-> instead of <VAR
-CLASS="PARAMETER"
->security 
-	mask</VAR
->, and <VAR
-CLASS="PARAMETER"
->force directory security mode
-	</VAR
-> parameter instead of <VAR
-CLASS="PARAMETER"
->force security mode
-	</VAR
->.</P
-><P
->The <VAR
-CLASS="PARAMETER"
->directory security mask</VAR
-> parameter 
-	by default is set to the same value as the <VAR
-CLASS="PARAMETER"
->directory mask
-	</VAR
-> parameter and the <VAR
-CLASS="PARAMETER"
->force directory security 
-	mode</VAR
-> parameter by default is set to the same value as 
- 	the <VAR
-CLASS="PARAMETER"
->force directory mode</VAR
-> parameter. </P
-><P
->In this way Samba enforces the permission restrictions that 
-	an administrator can set on a Samba share, whilst still allowing users 
-	to modify the permission bits within that restriction.</P
-><P
->If you want to set up a share that allows users full control
-	in modifying the permission bits on their files and directories and
-	doesn't force any particular bits to be set 'on', then set the following
-	parameters in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file in that share specific section :</P
-><P
-><VAR
-CLASS="PARAMETER"
->security mask = 0777</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->force security mode = 0</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->directory security mask = 0777</VAR
-></P
-><P
-><VAR
-CLASS="PARAMETER"
->force directory security mode = 0</VAR
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1673"
->10.7. Interaction with the standard Samba file attribute 
-	mapping</A
-></H2
-><P
->Samba maps some of the DOS attribute bits (such as "read 
-	only") into the UNIX permissions of a file. This means there can 
-	be a conflict between the permission bits set via the security 
-	dialog and the permission bits set by the file attribute mapping.
-	</P
-><P
->One way this can show up is if a file has no UNIX read access
-	for the owner it will show up as "read only" in the standard 
-	file attributes tabbed dialog. Unfortunately this dialog is
-	the same one that contains the security info in another tab.</P
-><P
->What this can mean is that if the owner changes the permissions
-	to allow themselves read access using the security dialog, clicks
-	<B
-CLASS="COMMAND"
->"OK"</B
-> to get back to the standard attributes tab 
-	dialog, and then clicks <B
-CLASS="COMMAND"
->"OK"</B
-> on that dialog, then 
-	NT will set the file permissions back to read-only (as that is what 
-	the attributes still say in the dialog). This means that after setting 
-	permissions and clicking <B
-CLASS="COMMAND"
->"OK"</B
-> to get back to the 
-	attributes dialog you should always hit <B
-CLASS="COMMAND"
->"Cancel"</B
-> 
-	rather than <B
-CLASS="COMMAND"
->"OK"</B
-> to ensure that your changes 
-	are not overridden.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="GROUPMAPPING"
-></A
->Chapter 11. Configuring Group Mapping</H1
-><P
-> 
-Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
-current method (likely to change) to manage the groups is a new command called
-<SPAN
-CLASS="APPLICATION"
->smbgroupedit</SPAN
->.</P
-><P
->The first immediate reason to use the group mapping on a PDC, is that
-the <B
-CLASS="COMMAND"
->domain admin group</B
-> of <TT
-CLASS="FILENAME"
->smb.conf</TT
-> is 
-now gone. This parameter was used to give the listed users local admin rights 
-on their workstations. It was some magic stuff that simply worked but didn't
-scale very well for complex setups.</P
-><P
->Let me explain how it works on NT/W2K, to have this magic fade away.
-When installing NT/W2K on a computer, the installer program creates some users
-and groups. Notably the 'Administrators' group, and gives to that group some
-privileges like the ability to change the date and time or to kill any process
-(or close too) running on the local machine. The 'Administrator' user is a
-member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
-group privileges. If a 'joe' user is created and become a member of the
-'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P
-><P
->When a NT/W2K machine is joined to a domain, during that phase, the "Domain
-Administrators' group of the PDC is added to the 'Administrators' group of the
-workstation. Every members of the 'Domain Administrators' group 'inherit' the
-rights of the 'Administrators' group when logging on the workstation.</P
-><P
->You are now wondering how to make some of your samba PDC users members of the
-'Domain Administrators' ? That's really easy.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->create a unix group (usually in <TT
-CLASS="FILENAME"
->/etc/group</TT
->), let's call it domadm</P
-></LI
-><LI
-><P
->add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT
-CLASS="FILENAME"
->/etc/group</TT
-> will look like:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->domadm:x:502:joe,john,mary</PRE
-></P
-></LI
-><LI
-><P
->Map this domadm group to the <B
-CLASS="COMMAND"
->domain admins</B
-> group by running the command:</P
-><P
-><KBD
-CLASS="USERINPUT"
->smbgroupedit -c "Domain Admins" -u domadm</KBD
-></P
-></LI
-></OL
-><P
->You're set, joe, john and mary are domain administrators !</P
-><P
->Like the Domain Admins group, you can map any arbitrary Unix group to any NT
-group. You can also make any Unix group a domain group. For example, on a domain
-member machine (an NT/W2K or a samba server running winbind), you would like to
-give access to a certain directory to some users who are member of a group on
-your samba PDC. Flag that group as a domain group by running:</P
-><P
-><KBD
-CLASS="USERINPUT"
->smbgroupedit -a unixgroup -td</KBD
-></P
-><P
->You can list the various groups in the mapping database like this</P
-><P
-><KBD
-CLASS="USERINPUT"
->smbgroupedit -v</KBD
-></P
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="PRINTING"
-></A
->Chapter 12. Printing Support</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN1736"
->12.1. Introduction</A
-></H2
-><P
->Beginning with the 2.2.0 release, Samba supports 
-the native Windows NT printing mechanisms implemented via 
-MS-RPC (i.e. the SPOOLSS named pipe).  Previous versions of 
-Samba only supported LanMan printing calls.</P
-><P
->The additional functionality provided by the new 
-SPOOLSS support includes:</P
-><P
-></P
-><UL
-><LI
-><P
->Support for downloading printer driver 
-	files to Windows 95/98/NT/2000 clients upon demand.
-	</P
-></LI
-><LI
-><P
->Uploading of printer drivers via the 
-	Windows NT Add Printer Wizard (APW) or the 
-	Imprints tool set (refer to <A
-HREF="http://imprints.sourceforge.net"
-TARGET="_top"
->http://imprints.sourceforge.net</A
->). 
-	</P
-></LI
-><LI
-><P
->Support for the native MS-RPC printing 
-	calls such as StartDocPrinter, EnumJobs(), etc...  (See 
-	the MSDN documentation at <A
-HREF="http://msdn.microsoft.com/"
-TARGET="_top"
->http://msdn.microsoft.com/</A
-> 
-	for more information on the Win32 printing API)
-	</P
-></LI
-><LI
-><P
->Support for NT Access Control Lists (ACL) 
-	on printer objects</P
-></LI
-><LI
-><P
->Improved support for printer queue manipulation 
-	through the use of an internal databases for spooled job 
-	information</P
-></LI
-></UL
-><P
->There has been some initial confusion about what all this means
-and whether or not it is a requirement for printer drivers to be 
-installed on a Samba host in order to support printing from Windows 
-clients. As a side note, Samba does not use these drivers in any way to process 
-spooled files.  They are utilized entirely by the clients.</P
-><P
->The following MS KB article, may be of some help if you are dealing with
-Windows 2000 clients:  <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How to Add Printers with No User 
-Interaction in Windows 2000</I
-></SPAN
-></P
-><P
-><A
-HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP"
-TARGET="_top"
->http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1758"
->12.2. Configuration</A
-></H2
-><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
-><TH
-ALIGN="LEFT"
-VALIGN="CENTER"
-><B
->[print$] vs. [printer$]</B
-></TH
-></TR
-><TR
-><TD
->&nbsp;</TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Previous versions of Samba recommended using a share named [printer$].  
-This name was taken from the printer$ service created by Windows 9x 
-clients when a printer was shared.  Windows 9x printer servers always have 
-a printer$ service which provides read-only access via no 
-password in order to support printer driver downloads.</P
-><P
->However, the initial implementation allowed for a 
-parameter named <VAR
-CLASS="PARAMETER"
->printer driver location</VAR
-> 
-to be used on a per share basis to specify the location of 
-the driver files associated with that printer.  Another 
-parameter named <VAR
-CLASS="PARAMETER"
->printer driver</VAR
-> provided 
-a means of defining the printer driver name to be sent to 
-the client.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1766"
->12.2.1. Creating [print$]</A
-></H3
-><P
->In order to support the uploading of printer driver 
-files, you must first configure a file share named [print$].  
-The name of this share is hard coded in Samba's internals so 
-the name is very important (print$ is the service used by 
-Windows NT print servers to provide support for printer driver 
-download).</P
-><P
->You should modify the server's smb.conf file to add the global
-parameters and to create the 
-following file share (of course, some of the parameter values,
-such as 'path' are arbitrary and should be replaced with
-appropriate values for your site):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
-    ; members of the ntadmin group should be able
-    ; to add drivers and set printer properties
-    ; root is implicitly a 'printer admin'
-    printer admin = @ntadmin
-
-[print$]
-    path = /usr/local/samba/printers
-    guest ok = yes
-    browseable = yes
-    read only = yes
-    ; since this share is configured as read only, then we need
-    ; a 'write list'.  Check the file system permissions to make
-    ; sure this account can copy files to the share.  If this
-    ; is setup to a non-root account, then it should also exist
-    ; as a 'printer admin'
-    write list = @ntadmin,root</PRE
-></P
-><P
->The <A
-HREF="smb.conf.5.html#WRITELIST"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->write list</VAR
-></A
-> is used to allow administrative 
-level user accounts to have write access in order to update files 
-on the share.  See the <A
-HREF="smb.conf.5.html"
-TARGET="_top"
->smb.conf(5) 
-man page</A
-> for more information on configuring file shares.</P
-><P
->The requirement for <A
-HREF="smb.conf.5.html#GUESTOK"
-TARGET="_top"
-><B
-CLASS="COMMAND"
->guest 
-ok = yes</B
-></A
-> depends upon how your
-site is configured.  If users will be guaranteed to have 
-an account on the Samba host, then this is a non-issue.</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
-><TH
-ALIGN="LEFT"
-VALIGN="CENTER"
-><B
->Author's Note</B
-></TH
-></TR
-><TR
-><TD
->&nbsp;</TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The non-issue is that if all your Windows NT users are guaranteed to be 
-authenticated by the Samba server (such as a domain member server and the NT 
-user has already been validated by the Domain Controller in 
-order to logon to the Windows NT console), then guest access 
-is not necessary.  Of course, in a workgroup environment where 
-you just want to be able to print without worrying about 
-silly accounts and security, then configure the share for 
-guest access.  You'll probably want to add <A
-HREF="smb.conf.5.html#MAPTOGUEST"
-TARGET="_top"
-><B
-CLASS="COMMAND"
->map to guest = Bad User</B
-></A
-> in the [global] section as well.  Make sure 
-you understand what this parameter does before using it 
-though. --jerry</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->In order for a Windows NT print server to support 
-the downloading of driver files by multiple client architectures,
-it must create subdirectories within the [print$] service
-which correspond to each of the supported client architectures.
-Samba follows this model as well.</P
-><P
->Next create the directory tree below the [print$] share 
-for each architecture you wish to support.</P
-><P
-><SAMP
-CLASS="COMPUTEROUTPUT"
->[print$]-----
-        |-W32X86           ; "Windows NT x86"
-        |-WIN40            ; "Windows 95/98"
-        |-W32ALPHA         ; "Windows NT Alpha_AXP"
-        |-W32MIPS          ; "Windows NT R4000"
-        |-W32PPC           ; "Windows NT PowerPC"</SAMP
-></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
-><TH
-ALIGN="LEFT"
-VALIGN="CENTER"
-><B
->ATTENTION!  REQUIRED PERMISSIONS</B
-></TH
-></TR
-><TR
-><TD
->&nbsp;</TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->In order to currently add a new driver to you Samba host, 
-one of two conditions must hold true:</P
-><P
-></P
-><UL
-><LI
-><P
->The account used to connect to the Samba host 
-	must have a uid of 0 (i.e. a root account)</P
-></LI
-><LI
-><P
->The account used to connect to the Samba host
-	must be a member of the <A
-HREF="smb.conf.5.html#PRINTERADMIN"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->printer 
-	admin</VAR
-></A
-> list.</P
-></LI
-></UL
-><P
->Of course, the connected account must still possess access
-to add files to the subdirectories beneath [print$]. Remember
-that all file shares are set to 'read only' by default.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Once you have created the required [print$] service and 
-associated subdirectories, simply log onto the Samba server using 
-a root (or <VAR
-CLASS="PARAMETER"
->printer admin</VAR
->) account
-from a Windows NT 4.0/2k client.  Open "Network Neighbourhood" or
-"My Network Places" and browse for the Samba host.  Once you have located
-the server, navigate to the "Printers..." folder.
-You should see an initial listing of printers
-that matches the printer shares defined on your Samba host.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1801"
->12.2.2. Setting Drivers for Existing Printers</A
-></H3
-><P
->The initial listing of printers in the Samba host's 
-Printers folder will have no real printer driver assigned 
-to them. This defaults to a NULL string to allow the use
-of the local Add Printer Wizard on NT/2000 clients.
-Attempting to view the printer properties for a printer
-which has this default driver assigned will result in 
-the error message:</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Device settings cannot be displayed.  The driver 
-for the specified printer is not installed, only spooler 
-properties will be displayed.  Do you want to install the 
-driver now?</I
-></SPAN
-></P
-><P
->Click "No" in the error dialog and you will be presented with
-the printer properties window.  The way to assign a driver to a 
-printer is to either</P
-><P
-></P
-><UL
-><LI
-><P
->Use the "New Driver..." button to install 
-	a new printer driver, or</P
-></LI
-><LI
-><P
->Select a driver from the popup list of 
-	installed drivers.  Initially this list will be empty.</P
-></LI
-></UL
-><P
->If you wish to install printer drivers for client 
-operating systems other than "Windows NT x86", you will need 
-to use the "Sharing" tab of the printer properties dialog.</P
-><P
->Assuming you have connected with a root account, you 
-will also be able modify other printer properties such as 
-ACLs and device settings using this dialog box.</P
-><P
->A few closing comments for this section, it is possible 
-on a Windows NT print server to have printers
-listed in the Printers folder which are not shared.  Samba does
-not make this distinction.  By definition, the only printers of
-which Samba is aware are those which are specified as shares in
-<TT
-CLASS="FILENAME"
->smb.conf</TT
->.</P
-><P
->Another interesting side note is that Windows NT clients do
-not use the SMB printer share, but rather can print directly 
-to any printer on another Windows NT host using MS-RPC.  This
-of course assumes that the printing client has the necessary
-privileges on the remote host serving the printer.  The default
-permissions assigned by Windows NT to a printer gives the "Print"
-permissions to the "Everyone" well-known group.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1817"
->12.2.3. Support a large number of printers</A
-></H3
-><P
->One issue that has arisen during the development
-phase of Samba 2.2 is the need to support driver downloads for
-100's of printers.  Using the Windows NT APW is somewhat 
-awkward to say the list.  If more than one printer are using the 
-same driver, the <A
-HREF="rpcclient.1.html"
-TARGET="_top"
-><B
-CLASS="COMMAND"
->rpcclient's
-setdriver command</B
-></A
-> can be used to set the driver
-associated with an installed driver.  The following is example
-of how this could be accomplished:</P
-><P
-><SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->rpcclient pogo -U root%secret -c "enumdrivers"</KBD
->
-<PRE
-CLASS="PROGRAMLISTING"
-> 
-Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
- 
-[Windows NT x86]
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4000 Series PS]
- 
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 2100 Series PS]
- 
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4Si/4SiMX PS]</PRE
->				  
-<SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->rpcclient pogo -U root%secret -c "enumprinters"</KBD
->
-<PRE
-CLASS="PROGRAMLISTING"
->Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-     flags:[0x800000]
-     name:[\\POGO\hp-print]
-     description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
-     comment:[]
-				  </PRE
->
-<SAMP
-CLASS="PROMPT"
->$ </SAMP
-><KBD
-CLASS="USERINPUT"
->rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""</KBD
->
-<PRE
-CLASS="PROGRAMLISTING"
->Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1832"
->12.2.4. Adding New Printers via the Windows NT APW</A
-></H3
-><P
->By default, Samba offers all printer shares defined in <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-in the "Printers..." folder.  Also existing in this folder is the Windows NT 
-Add Printer Wizard icon.  The APW will be show only if</P
-><P
-></P
-><UL
-><LI
-><P
->The connected user is able to successfully
-	execute an OpenPrinterEx(\\server) with administrative
-	privileges (i.e. root or <VAR
-CLASS="PARAMETER"
->printer admin</VAR
->).
-	</P
-></LI
-><LI
-><P
-><A
-HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->show 
-	add printer wizard = yes</VAR
-></A
-> (the default).
-	</P
-></LI
-></UL
-><P
->In order to be able to use the APW to successfully add a printer to a Samba 
-server, the <A
-HREF="smb.conf.5.html#ADDPRINTERCOMMAND"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->add 
-printer command</VAR
-></A
-> must have a defined value.  The program
-hook must successfully add the printer to the system (i.e. 
-<TT
-CLASS="FILENAME"
->/etc/printcap</TT
-> or appropriate files) and 
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> if necessary.</P
-><P
->When using the APW from a client, if the named printer share does 
-not exist, <B
-CLASS="COMMAND"
->smbd</B
-> will execute the <VAR
-CLASS="PARAMETER"
->add printer 
-command</VAR
-> and reparse to the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-to attempt to locate the new printer share.  If the share is still not defined,
-an error of "Access Denied" is returned to the client.  Note that the 
-<VAR
-CLASS="PARAMETER"
->add printer program</VAR
-> is executed under the context
-of the connected user, not necessarily a root account.</P
-><P
->There is a complementary <A
-HREF="smb.conf.5.html#DELETEPRINTERCOMMAND"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->delete
-printer command</VAR
-></A
-> for removing entries from the "Printers..."
-folder.</P
-><P
->The following is an example <A
-HREF="smb.conf.5.html#ADDPRINTERCOMMAN"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->add printer command</VAR
-></A
-> script. It adds the appropriate entries to <TT
-CLASS="FILENAME"
->/etc/printcap.local</TT
-> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.</P
-><PRE
-CLASS="PROGRAMLISTING"
->#!/bin/sh
-
-# Script to insert a new printer entry into printcap.local
-#
-# $1, printer name, used as the descriptive name
-# $2, share name, used as the printer name for Linux
-# $3, port name
-# $4, driver name
-# $5, location, used for the device file of the printer
-# $6, win9x location
-
-#
-# Make sure we use the location that RedHat uses for local printer defs
-PRINTCAP=/etc/printcap.local
-DATE=`date +%Y%m%d-%H%M%S`
-LP=lp
-RESTART="service lpd restart"
-
-# Keep a copy
-cp $PRINTCAP $PRINTCAP.$DATE
-# Add the printer to $PRINTCAP
-echo ""				 			&#62;&#62; $PRINTCAP
-echo "$2|$1:\\" 					&#62;&#62; $PRINTCAP
-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
-
-mkdir /var/spool/lpd/$2
-chmod 700 /var/spool/lpd/$2
-chown $LP /var/spool/lpd/$2
-#echo $1 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-#echo $2 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-#echo $3 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-#echo $4 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-#echo $5 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-#echo $6 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-$RESTART &#62;&#62; "/usr/local/samba/var/print/$5.prn"
-# Not sure if this is needed
-touch /usr/local/samba/lib/smb.conf
-#
-# You need to return a value, but I am not sure what it means.
-#
-echo "Done"
-exit 0</PRE
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1862"
->12.2.5. Samba and Printer Ports</A
-></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
-concept of ports associated with a printer.  By default, only one printer port,
-named "Samba Printer Port", exists on a system.  Samba does not really a port in
-order to print, rather it is a requirement of Windows clients.  </P
-><P
->Note that Samba does not support the concept of "Printer Pooling" internally 
-either.  This is when a logical printer is assigned to multiple ports as 
-a form of load balancing or fail over.</P
-><P
->If you require that multiple ports be defined for some reason,
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> possesses a <A
-HREF="smb.conf.5.html#ENUMPORTSCOMMAND"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->enumports 
-command</VAR
-></A
-> which can be used to define an external program 
-that generates a listing of ports on a system.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1870"
->12.3. The Imprints Toolset</A
-></H2
-><P
->The Imprints tool set provides a UNIX equivalent of the 
-	Windows NT Add Printer Wizard.  For complete information, please 
-	refer to the Imprints web site at <A
-HREF="http://imprints.sourceforge.net/"
-TARGET="_top"
->	http://imprints.sourceforge.net/</A
-> as well as the documentation 
-	included with the imprints source distribution.  This section will 
-	only provide a brief introduction to the features of Imprints.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1874"
->12.3.1. What is Imprints?</A
-></H3
-><P
->Imprints is a collection of tools for supporting the goals 
-		of</P
-><P
-></P
-><UL
-><LI
-><P
->Providing a central repository information 
-			regarding Windows NT and 95/98 printer driver packages</P
-></LI
-><LI
-><P
->Providing the tools necessary for creating 
-			the Imprints printer driver packages.</P
-></LI
-><LI
-><P
->Providing an installation client which 
-			will obtain and install printer drivers on remote Samba 
-			and Windows NT 4 print servers.</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1884"
->12.3.2. Creating Printer Driver Packages</A
-></H3
-><P
->The process of creating printer driver packages is beyond
-		the scope of this document (refer to Imprints.txt also included
-		with the Samba distribution for more information).  In short,
-		an Imprints driver package is a gzipped tarball containing the
-		driver files, related INF files, and a control file needed by the
-		installation client.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1887"
->12.3.3. The Imprints server</A
-></H3
-><P
->The Imprints server is really a database server that 
-		may be queried via standard HTTP mechanisms.  Each printer 
-		entry in the database has an associated URL for the actual
-		downloading of the package.  Each package is digitally signed
-		via GnuPG which can be used to verify that package downloaded
-		is actually the one referred in the Imprints database.  It is 
-		<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not</I
-></SPAN
-> recommended that this security check 
-		be disabled.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1891"
->12.3.4. The Installation Client</A
-></H3
-><P
->More information regarding the Imprints installation client 
-		is available in the <TT
-CLASS="FILENAME"
->Imprints-Client-HOWTO.ps</TT
-> 
-		file included with the imprints source package.</P
-><P
->The Imprints installation client comes in two forms.</P
-><P
-></P
-><UL
-><LI
-><P
->a set of command line Perl scripts</P
-></LI
-><LI
-><P
->a GTK+ based graphical interface to 
-			the command line perl scripts</P
-></LI
-></UL
-><P
->The installation client (in both forms) provides a means
-		of querying the Imprints database server for a matching
-		list of known printer model names as well as a means to 
-		download and install the drivers on remote Samba and Windows
-		NT print servers.</P
-><P
->The basic installation process is in four steps and 
-		perl code is wrapped around <B
-CLASS="COMMAND"
->smbclient</B
-> 
-		and <B
-CLASS="COMMAND"
->rpcclient</B
->.</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	
-foreach (supported architecture for a given driver)
-{
-     1.  rpcclient: Get the appropriate upload directory 
-         on the remote server
-     2.  smbclient: Upload the driver files
-     3.  rpcclient: Issues an AddPrinterDriver() MS-RPC
-}
-	
-4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
-    create the printer</PRE
-></P
-><P
->One of the problems encountered when implementing 
-		the Imprints tool set was the name space issues between 
-		various supported client architectures.  For example, Windows 
-		NT includes a driver named "Apple LaserWriter II NTX v51.8" 
-		and Windows 95 calls its version of this driver "Apple 
-		LaserWriter II NTX"</P
-><P
->The problem is how to know what client drivers have 
-		been uploaded for a printer.  As astute reader will remember 
-		that the Windows NT Printer Properties dialog only includes 
-		space for one printer driver name.  A quick look in the 
-		Windows NT 4.0 system registry at</P
-><P
-><TT
-CLASS="FILENAME"
->HKLM\System\CurrentControlSet\Control\Print\Environment
-		</TT
-></P
-><P
->will reveal that Windows NT always uses the NT driver 
-		name.  This is ok as Windows NT always requires that at least 
-		the Windows NT version of the printer driver is present.  
-		However, Samba does not have the requirement internally.  
-		Therefore, how can you use the NT driver name if is has not 
-		already been installed?</P
-><P
->The way of sidestepping this limitation is to require 
-		that all Imprints printer driver packages include both the Intel 
-		Windows NT and 95/98 printer drivers and that NT driver is 
-		installed first.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN1913"
->12.4. Diagnosis</A
-></H2
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="AEN1915"
->12.4.1. Introduction</A
-></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
-client to a Samba server, not the other way around. For the reverse
-see the examples/printing directory.</P
-><P
->Ok, so you want to print to a Samba server from your PC. The first
-thing you need to understand is that Samba does not actually do any
-printing itself, it just acts as a middleman between your PC client
-and your Unix printing subsystem. Samba receives the file from the PC
-then passes the file to a external "print command". What print command
-you use is up to you.</P
-><P
->The whole things is controlled using options in smb.conf. The most
-relevant options (which you should look up in the smb.conf man page)
-are:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->      [global]
-        print command     - send a file to a spooler
-        lpq command       - get spool queue status
-        lprm command      - remove a job
-      [printers]
-        path = /var/spool/lpd/samba</PRE
-></P
-><P
->The following are nice to know about:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        queuepause command   - stop a printer or print queue
-        queueresume command  - start a printer or print queue</PRE
-></P
-><P
->Example:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        print command = /usr/bin/lpr -r -P%p %s
-        lpq command   = /usr/bin/lpq    -P%p %s
-        lprm command  = /usr/bin/lprm   -P%p %j
-        queuepause command = /usr/sbin/lpc -P%p stop
-        queuepause command = /usr/sbin/lpc -P%p start</PRE
-></P
-><P
->Samba should set reasonable defaults for these depending on your
-system type, but it isn't clairvoyant. It is not uncommon that you
-have to tweak these for local conditions.  The commands should
-always have fully specified pathnames,  as the smdb may not have
-the correct PATH values.</P
-><P
->When you send a job to Samba to be printed,  it will make a temporary
-copy of it in the directory specified in the [printers] section.
-and it should be periodically cleaned out.  The lpr -r option
-requests that the temporary copy be removed after printing; If
-printing fails then you might find leftover files in this directory,
-and it should be periodically cleaned out.  Samba used the lpq
-command to determine the "job number" assigned to your print job
-by the spooler.</P
-><P
->The %&#62;letter&#60; are "macros" that get dynamically replaced with appropriate
-values when they are used. The %s gets replaced with the name of the spool
-file that Samba creates and the %p gets replaced with the name of the
-printer. The %j gets replaced with the "job number" which comes from
-the lpq output.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1931"
->12.4.2. Debugging printer problems</A
-></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
-of the print file. A simple example of this kind of things might
-be:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	print command = /tmp/saveprint %p %s
-
-    #!/bin/saveprint
-    # we make sure that we are the right user
-    /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
-></P
-><P
->Then you print a file and try removing it.  You may find that the
-print queue needs to be stopped in order to see the queue status
-and remove the job:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->&#13;h4: {42} % echo hi &#62;/tmp/hi
-h4: {43} % smbclient //localhost/lw4
-added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
-Password: 
-Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \&#62; print /tmp/hi
-putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \&#62; queue
-1049     3            hi-17534
-smb: \&#62; cancel 1049
-Error cancelling job 1049 : code 0
-smb: \&#62; cancel 1049
-Job 1049 cancelled
-smb: \&#62; queue
-smb: \&#62; exit</PRE
-></P
-><P
->The 'code 0' indicates that the job was removed.  The comment
-by the  smbclient is a bit misleading on this.
-You can observe the command output and then and look at the
-/tmp/tmp.print file to see what the results are.  You can quickly
-find out if the problem is with your printing system.  Often people
-have problems with their /etc/printcap file or permissions on
-various print queues.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1940"
->12.4.3. What printers do I have?</A
-></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
-use:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->    testprns printer /etc/printcap</PRE
-></P
-><P
->Samba can get its printcap information from a file or from a program.
-You can try the following to see the format of the extracted
-information:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->    testprns -a printer /etc/printcap
-
-    testprns -a printer '|/bin/cat printcap'</PRE
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1948"
->12.4.4. Setting up printcap and print servers</A
-></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
-the print spooler to set up queues and printcap information.</P
-><P
->Samba requires either a printcap or program to deliver printcap
-information.  This printcap information has the format:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->  name|alias1|alias2...:option=value:...</PRE
-></P
-><P
->For almost all printing systems, the printer 'name' must be composed
-only of alphanumeric or underscore '_' characters.  Some systems also
-allow hyphens ('-') as well.  An alias is an alternative name for the
-printer,  and an alias with a space in it is used as a 'comment'
-about the printer.  The printcap format optionally uses a \ at the end of lines
-to extend the printcap to multiple lines.</P
-><P
->Here are some examples of printcap files:</P
-><P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->pr              just printer name</P
-></LI
-><LI
-><P
->pr|alias        printer name and alias</P
-></LI
-><LI
-><P
->pr|My Printer   printer name, alias used as comment</P
-></LI
-><LI
-><P
->pr:sh:\        Same as pr:sh:cm= testing
-  :cm= \ 
-  testing</P
-></LI
-><LI
-><P
->pr:sh           Same as pr:sh:cm= testing
-  :cm= testing</P
-></LI
-></OL
-></P
-><P
->Samba reads the printcap information when first started.  If you make
-changes in the printcap information, then you must do the following:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->make sure that the print spooler is aware of these changes.
-The LPRng system uses the 'lpc reread' command to do this.</P
-></LI
-><LI
-><P
->make sure that the spool queues, etc., exist and have the
-correct permissions.  The LPRng system uses the 'checkpc -f'
-command to do this.</P
-></LI
-><LI
-><P
->You now should send a SIGHUP signal to the smbd server to have
-it reread the printcap information.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1976"
->12.4.5. Job sent, no output</A
-></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
-the command to send the file,  but there was no output from the printer.</P
-><P
->First,  check to make sure that the job REALLY is getting to the
-right print queue.  If you are using a BSD or LPRng print spooler,
-you can temporarily stop the printing of jobs.  Jobs can still be
-submitted, but they will not be printed.  Use:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->  lpc -Pprinter stop</PRE
-></P
-><P
->Now submit a print job and then use 'lpq -Pprinter' to see if the
-job is in the print queue.  If it is not in the print queue then
-you will have to find out why it is not being accepted for printing.</P
-><P
->Next, you may want to check to see what the format of the job really
-was.  With the assistance of the system administrator you can view
-the submitted jobs files.  You may be surprised to find that these
-are not in what you would expect to call a printable format.
-You can use the UNIX 'file' utitily to determine what the job
-format actually is:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->    cd /var/spool/lpd/printer   # spool directory of print jobs
-    ls                          # find job files
-    file dfA001myhost</PRE
-></P
-><P
->You should make sure that your printer supports this format OR that
-your system administrator has installed a 'print filter' that will
-convert the file to a format appropriate for your printer.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1987"
->12.4.6. Job sent, strange output</A
-></H3
-><P
->Once you have the job printing, you can then start worrying about
-making it print nicely.</P
-><P
->The most common problem is extra pages of output: banner pages
-OR blank pages at the end.</P
-><P
->If you are getting banner pages,  check and make sure that the
-printcap option or printer option is configured for no banners.
-If you have a printcap,  this is the :sh (suppress header or banner
-page) option.  You should have the following in your printer.</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->   printer: ... :sh</PRE
-></P
-><P
->If you have this option and are still getting banner pages,  there
-is a strong chance that your printer is generating them for you
-automatically.  You should make sure that banner printing is disabled
-for the printer.  This usually requires using the printer setup software
-or procedures supplied by the printer manufacturer.</P
-><P
->If you get an extra page of output,  this could be due to problems
-with your job format,  or if you are generating PostScript jobs,
-incorrect setting on your printer driver on the MicroSoft client.
-For example, under Win95 there is a option:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->  Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
-></P
-><P
->that allows you to choose if a Ctrl-D is appended to all jobs.
-This is a very bad thing to do, as most spooling systems will
-automatically add a ^D to the end of the job if it is detected as
-PostScript.  The multiple ^D may cause an additional page of output.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN1999"
->12.4.7. Raw PostScript printed</A
-></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
-the printer think the job is a text file, or your printer simply
-does not support PostScript.  You may need to enable 'Automatic
-Format Detection' on your printer.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2002"
->12.4.8. Advanced Printing</A
-></H3
-><P
->Note that you can do some pretty magic things by using your
-imagination with the "print command" option and some shell scripts.
-Doing print accounting is easy by passing the %U option to a print
-command shell script. You could even make the print command detect
-the type of output and its size and send it to an appropriate
-printer.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2005"
->12.4.9. Real debugging</A
-></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
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="CUPS-PRINTING"
-></A
->Chapter 13. CUPS Printing Support</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN2025"
->13.1. Introduction</A
-></H2
-><P
->The Common Unix Print System (CUPS) has become very popular, but to many it is
-a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
-it works. The result is seen in a large number of posting on the samba mailing lists
-expressing frustration when MS Windows printers appear not to work with a CUPS
-backr-end.
-/para&#62;&#13;</P
-><P
->This is a good time to point out how CUPS can be used and what it does. CUPS is more
-than just a print spooling system - it is a complete printer management system that
-complies with HTTP and IPP protocols. It can be managed remotely via a web browser
-and it can print using http and ipp protocols.</P
-><P
->CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
-SMART printers (ie: CUPS does file format conversion as required for the printer). In
-many ways this gives CUPS similar capabilities to the MS Windows print monitoring
-system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
-In any case, let us now move on to explore how one may configure CUPS for interfacing
-with MS Windows print clients via Samba.</P
-><P
-><A
-HREF="http://www.cups.org/"
-TARGET="_top"
->CUPS</A
-> is a newcomer in the UNIX printing scene,
-which has convinced many people upon first trial already. However, it has quite a few
-new features, which make it different from other, more traditional printing systems.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2032"
->13.2. Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></H2
-><P
->Printing with CUPS in the most basic <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-setup in Samba-3  only needs two settings: <B
-CLASS="COMMAND"
->printing = cups</B
-> and
-<B
-CLASS="COMMAND"
->printcap = cups</B
->. While CUPS itself doesn't need a printcap
-anymore, the <TT
-CLASS="FILENAME"
->cupsd.conf</TT
-> configuration file knows two directives
-(example: <B
-CLASS="COMMAND"
->Printcap /etc/printcap</B
-> and <B
-CLASS="COMMAND"
->PrintcapFormat
-BSD</B
->), which control if such a file should be created for the
-convenience of third party applications. Make sure it is set! For details see
-<B
-CLASS="COMMAND"
->man cupsd.conf</B
-> and other CUPS-related documentation.</P
-><P
->If SAMBA is compiled against libcups, then <B
-CLASS="COMMAND"
->printcap = cups</B
-> uses the
-CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
-with an additional <VAR
-CLASS="PARAMETER"
->-oraw</VAR
-> option for printing. On a Linux system,
-you can use the <B
-CLASS="COMMAND"
->ldd</B
-> command to find out details (ldd may not be
-present on other OS platforms, or its function may be embodied by a different command):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->transmeta:/home/kurt # ldd `which smbd`
-        libssl.so.0.9.6 =&#62; /usr/lib/libssl.so.0.9.6 (0x4002d000)
-        libcrypto.so.0.9.6 =&#62; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-        libcups.so.2 =&#62; /usr/lib/libcups.so.2 (0x40123000)
-        libdl.so.2 =&#62; /lib/libdl.so.2 (0x401e8000)
-        libnsl.so.1 =&#62; /lib/libnsl.so.1 (0x401ec000)
-        libpam.so.0 =&#62; /lib/libpam.so.0 (0x40202000)
-        libc.so.6 =&#62; /lib/libc.so.6 (0x4020b000)
-        /lib/ld-linux.so.2 =&#62; /lib/ld-linux.so.2 (0x40000000)</PRE
-></P
-><P
->The line "libcups.so.2 =&#62; /usr/lib/libcups.so.2
-(0x40123000)" shows there is CUPS support compiled into this version of
-Samba. If this is the case, and <B
-CLASS="COMMAND"
->printing = cups</B
-> is set, then any
-otherwise manually set print command in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> is ignored.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2052"
->13.3. CUPS - RAW Print Through Mode</A
-></H2
-><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
->When used in raw print through mode is will be necessary to use the printer
-vendor's drivers in each Windows client PC.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->When CUPS printers are configured for RAW print-through mode operation it is the
-responsibility of the Samba client to fully render the print job (file) in a format
-that is suitable for direct delivery to the printer. In this case CUPS will NOT
-do any print file format conversion work.</P
-><P
->The CUPS files that need to be correctly set for RAW mode printers to work are:
-
-<P
-></P
-><UL
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.types</TT
-></P
-><P
-></P
-></LI
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.convs</TT
-></P
-><P
-></P
-></LI
-></UL
->
-
-Both contain entries that must be uncommented to allow <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->RAW</I
-></SPAN
-> mode
-operation.</P
-><P
->Firstly, to enable CUPS based printing from Samba the following options must be
-enabled in your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file [globals] section:
-
-<P
-></P
-><UL
-><LI
-><P
->printing = CUPS</P
-></LI
-><LI
-><P
->printcap = CUPS</P
-></LI
-></UL
->
-
-When these parameters are specified the print directives in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> (as well as in
-samba itself) will be ignored because samba will directly interface with CUPS through
-it's application program interface (API) - so long as Samba has been compiled with
-CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
-printing will use the System V AT&#38;T command set with the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->-oraw</I
-></SPAN
-> 
-option automatically passing through.</P
-><P
->Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) 
-on the Samba/CUPS server does *not* add any features if a file is really
-printed "raw".  However, if you have loaded the driver for the Windows client from
-the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using
-a "Foomatic" PPD, the PJL header in question is already added on the Windows client,
-at the time when the driver initially generated the PostScript data and CUPS in true
-"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its
-printer communication backend.</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
->NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce*
-"raw" printing, it only *allows* it.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids
-the process of determining proper treatment while in the print queue system.
-
-<P
-></P
-><UL
-><LI
-><P
->	Files generated by PCL drivers and directed at PCK printers get auto-typed as
-	<TT
-CLASS="FILENAME"
->application/octet-stream</TT
->. Unknown file format types also
-	get auto-typed with this tag.
-	</P
-></LI
-><LI
-><P
->	Files generated by a Postscript driver and directed at a Postscript printer
-	are auto-typed depending on the auto-detected most suitable MIME type as:
-
-	<P
-></P
-><UL
-><LI
-><P
->* application/postscript</P
-></LI
-><LI
-><P
->* application/vnd.cups-postscript</P
-></LI
-></UL
->
-	</P
-></LI
-></UL
-></P
-><P
->"application/postscript" first goes thru the "pstops" filter (where the page counting
-and accounting takes place). The outcome will be of MIME type
-"application/vnd.cups-postscript". The pstopsfilter reads and uses information from
-the PPD and inserts user-provided options into the PostScript file. As a consequence,
-the filtered file could possibly have an unwanted PJL header.</P
-><P
->"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which
-have as their first character string one of "%!" or "&#60;04&#62;%".</P
-><P
->"application/vnd.cups-postscript" will files which contain the string
-"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the
-first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes
-("&#60;1B&#62;%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS
-or other PPD, will have to be auto-typed as "vnd.cups-postscript".  A file produced
-with a "Generic PostScript driver" will just be tagged "application/postscript".</P
-><P
->Once the file is in "application/vnd.cups-postscript" format, either "pstoraster"
-or "cupsomatic" will take over (depending on the printer configuration, as
-determined by the PPD in use).</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
->A printer queue with *no* PPD associated to it is a "raw" printer and all files
-will go directly there as received by the spooler. The exeptions are file types
-"application/octet-stream" which need "passthrough feature" enabled.
-"Raw" queues don't do any filtering at all, they hand the file directly to the
-CUPS backend. This backend is responsible for the sending of the data to the device
-(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://,
-parallel:/, serial:/, usb:/ etc.)</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
->"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
-They are a Third Party add-on, developed at Linuxprinting.org.  As such, they are
-a brilliant hack to make all models (driven by Ghostscript drivers/filters in
-traditional spoolers) also work via CUPS, with the same (good or bad!) quality
-as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript
-commandline at that stage in the CUPS filtering chain, where "normally" the native
-CUPS "pstoraster" filter would kick in.  cupsomatic by-passes pstoraster, "kidnaps"
-the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
-because the associated CUPS-O-Matic-/Foomatic-PPD specifies:</P
-><PRE
-CLASS="PROGRAMLISTING"
->   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"</PRE
-><P
->This line persuades CUPS to hand the file to cupsomatic, once it has successfully
-converted it to the MIME type "application/vnd.cups-postscript". This conversion will not
-happen for Jobs arriving from Windows which are auto-typed "application/octet-stream",
-with the according changes in "/etc/cups/mime.types" in place.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->CUPS is widely configurable and flexible, even regarding its filtering mechanism.
-Another workaround in some situations would be to have
-in "/etc/cups/mime.types" entries as follows:</P
-><PRE
-CLASS="PROGRAMLISTING"
->   application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -</PRE
-><P
->This would prevent all Postscript files from being filtered (rather, they will go
-thru the virtual "nullfilter" denoted with "-"). This could only be useful for
-PS printers. If you want to print PS code on non-PS printers an entry as follows
-could be useful:</P
-><PRE
-CLASS="PROGRAMLISTING"
->   */*           application/vnd.cups-raw  0  -</PRE
-><P
->and would effectively send *all* files to the backend without further processing.</P
-><P
->Lastly, you could have the following entry:</P
-><PRE
-CLASS="PROGRAMLISTING"
->   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter</PRE
-><P
->You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that
-parses the PostScript and removes the unwanted PJL. This would need to conform to
-CUPS filter design (mainly, receive and pass the parameters printername, job-id,
-username, jobtitle, copies, print options and possibly the filename). It would
-be installed as world executable into "/usr/lib/cups/filters/" and will be called
-by CUPS if it encounters a MIME type "application/vnd.cups-postscript".</P
-><P
->CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue
-"on hold". It will only be printed upon manual release by the printer operator.
-This is a requirement in many "central reproduction departments", where a few
-operators manage the jobs of hundreds of users on some big machine, where no
-user is allowed to have direct access. (The operators often need to load the
-proper paper type before running the 10.000 page job requested by marketing
-for the mailing, etc.).</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2111"
->13.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></H2
-><P
->CUPS is perfectly able to use PPD files (PostScript
-Printer Descriptions). PPDs can control all print device options. They
-are usually provided by the manufacturer -- if you own a PostSript printer,
-that is. PPD files are always a component of PostScript printer drivers on MS
-Windows or Apple Mac OS systems. They are ASCII files containing
-user-selectable print options, mapped to appropriate PostScript, PCL or PJL
-commands for the target printer. Printer driver GUI dialogs translate these
-options "on-the-fly" into buttons and drop-down lists for the user to
-select.</P
-><P
->CUPS can load, without any conversions, the PPD file from
-any Windows (NT is recommended) PostScript driver and handle the options.
-There is a web browser interface to the print options (select
-http://localhost:631/printers/ and click on one "Configure Printer" button
-to see it), a commandline interface (see <B
-CLASS="COMMAND"
->man lpoptions</B
-> or
-try if you have <B
-CLASS="COMMAND"
->lphelp</B
-> on your system) plus some different GUI frontends on Linux
-UNIX, which can present PPD options to the users. PPD options are normally
-meant to become evaluated by the PostScript RIP on the real PostScript
-printer.</P
-><P
->CUPS doesn't stop at "real" PostScript printers in its
-usage of PPDs. The CUPS developers have extended the PPD concept, to also
-describe available device and driver options for non-PostScript printers
-through  CUPS-PPDs.</P
-><P
->This is logical, as CUPS includes a fully featured
-PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
-process all received PostScript (and additionally many other file formats)
-from clients. All CUPS-PPDs geared to non-PostScript printers contain an
-additional line, starting with the keyword <VAR
-CLASS="PARAMETER"
->*cupsFilter</VAR
->.
-This line
-tells the CUPS print system which printer-specific filter to use for the
-interpretation of the accompanying PostScript. Thus CUPS lets all its
-printers appear as PostScript devices to its clients, because it can act as a
-PostScript RIP for those printers, processing the received PostScript code
-into a proper raster print format.</P
-><P
->CUPS-PPDs can also be used on Windows-Clients, on top of a
-PostScript driver (recommended is the Adobe one).</P
-><P
->This feature enables CUPS to do a few tricks no other
-spooler can do:</P
-><P
-></P
-><UL
-><LI
-><P
->act as a networked PostScript RIP (Raster Image Processor), handling
-    printfiles from all client platforms in a uniform way;</P
-></LI
-><LI
-><P
->act as a central accounting and billing server, as all files are passed
-    through the <B
-CLASS="COMMAND"
->pstops</B
-> Filter and are therefor logged in
-    the CUPS <TT
-CLASS="FILENAME"
->page&lowbar;log</TT
->. - <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->this
-    can not happen with "raw" print jobs, which always remain unfiltered
-    per definition;</P
-></LI
-><LI
-><P
->enable clients to consolidate on a single PostScript driver, even for
-    many different target printers.</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2132"
->13.5. Windows Terminal Servers (WTS) as CUPS clients</A
-></H2
-><P
->This setup may be of special interest to people
-experiencing major problems in WTS environments. WTS need often a multitude
-of non-PostScript drivers installed to run their clients' variety of
-different printer models. This often imposes the price of much increased
-instability. In many cases, in an attempt to overcome this problem, site
-administrators have resorted to restrict the allowed drivers installed on
-their WTS to one generic PCL- and one PostScript driver. This however
-restricts the clients in the amount of printer options available for them --
-often they can't get out more then simplex prints from one standard paper
-tray, while their devices could do much better, if driven by a different
-driver!</P
-><P
->Using an Adobe PostScript driver, enabled with a CUPS-PPD,
-seems to be a very elegant way to overcome all these shortcomings. The
-PostScript driver is not known to cause major stability problems on WTS (even
-if used with many different PPDs). The clients will be able to (again) chose
-paper trays, duplex printing and other settings. However, there is a certain
-price for this too: a  CUPS server acting as a PostScript RIP for its clients
-requires more CPU and RAM than just to act as  a "raw spooling" device. Plus,
-this setup is not yet widely tested, although the first feedbacks look very
-promising...</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2136"
->13.6. Setting up CUPS for driver download</A
-></H2
-><P
->The <B
-CLASS="COMMAND"
->cupsadsmb</B
-> utility (shipped with all current
-CUPS versions) makes the sharing of any (or all) installed CUPS printers very
-easy. Prior to using it, you need the following settings in <TT
-CLASS="FILENAME"
->smb.conf</TT
->:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
-		 load printers = yes
-		 printing = cups
-		 printcap name = cups
-
-	[printers]
-		 comment = All Printers
-		 path = /var/spool/samba
-		 browseable = no
-		 public = yes
-		 guest ok = yes
-		 writable = no
-		 printable = yes
-		 printer admin = root
-
-	[print$]
-		 comment = Printer Drivers
-		 path = /etc/samba/drivers
-		 browseable = yes
-		 guest ok = no
-		 read only = yes
-		 write list = root
-	</PRE
-></P
-><P
->For licensing reasons the necessary files of the Adobe
-Postscript driver can not be distributed with either Samba or CUPS. You need
-to download them yourself from the Adobe website. Once extracted, create a
-<TT
-CLASS="FILENAME"
->drivers</TT
-> directory in the CUPS data directory (usually
-<TT
-CLASS="FILENAME"
->/usr/share/cups/</TT
->). Copy the Adobe files using
-UPPERCASE filenames, to this directory as follows:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->		ADFONTS.MFM
-		ADOBEPS4.DRV
-		ADOBEPS4.HLP
-		ADOBEPS5.DLL
-		ADOBEPSU.DLL
-		ADOBEPSU.HLP
-		DEFPRTR2.PPD
-		ICONLIB.DLL
-	</PRE
-></P
-><P
->Users of the ESP Print Pro software are able to install
-their "Samba Drivers" package for this purpose with no problem.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2149"
->13.7. Sources of CUPS drivers / PPDs</A
-></H2
-><P
->On the internet you can find now many thousand CUPS-PPD
-files (with their companion filters), in many national languages,
-supporting more than 1.000 non-PostScript models.</P
-><P
-></P
-><UL
-><LI
-><P
-><A
-HREF="http://wwwl.easysw.com/printpro/"
-TARGET="_top"
->ESP PrintPro
-    (http://wwwl.easysw.com/printpro/)</A
->
-    (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for
-    successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris,
-    SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it
-    is written by the CUPS developers themselves and its sales help finance
-    the further development of CUPS, as they feed their creators)</P
-></LI
-><LI
-><P
->the <A
-HREF="http://gimp-print.sourceforge.net/"
-TARGET="_top"
->Gimp-Print-Project
-    (http://gimp-print.sourceforge.net/)</A
->
-    (GPL, Free Software) provides around 120 PPDs (supporting nearly 300
-    printers, many driven to photo quality output), to be used alongside the
-    Gimp-Print CUPS filters;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.turboprint.com/"
-TARGET="_top"
->TurboPrint
-    (http://www.turboprint.com/)</A
->
-    (Shareware, non-Freee) supports roughly the same amount of printers in
-    excellent quality;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/"
-TARGET="_top"
->OMNI
-    (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</A
->
-    (LPGL, Free) is a package made by IBM, now containing support for more
-    than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow
-    ported over to Linux (CUPS support is in a Beta-stage at present);</P
-></LI
-><LI
-><P
-><A
-HREF="http://hpinkjet.sourceforge.net/"
-TARGET="_top"
->HPIJS
-    (http://hpinkjet.sourceforge.net/)</A
->
-    (BSD-style licnes, Free) supports around 120 of HP's own printers and is
-    also providing excellent print quality now;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.linuxprinting.org/"
-TARGET="_top"
->Foomatic/cupsomatic (http://www.linuxprinting.org/)</A
->
-    (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every
-    Ghostscript filter known to the world, now usable with CUPS.</P
-></LI
-></UL
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->the cupsomatic trick from Linuxprinting.org is
-working different from the other drivers. While the other drivers take the
-generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
-their input, cupsomatic "kidnaps" the PostScript inside CUPS, before
-RIP-ping, deviates it to an external Ghostscript installation (which now
-becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
-finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
-PostScript RIP function again inside a system-wide Ghostscript
-installation rather than in "their own" pstoraster filter. (This
-CUPS-enabling Ghostscript version may be installed either as a
-patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
-However, this will not change the cupsomatic approach of guiding the printjob
-along a different path through the filtering system than the standard CUPS
-way...</P
-><P
->Once you installed a printer inside CUPS with one of the
-recommended methods (the lpadmin command, the web browser interface or one of
-the available GUI wizards), you can use <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> to share the
-printer via Samba. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> prepares the driver files for
-comfortable client download and installation upon their first contact with
-this printer share.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2176"
->13.7.1. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-></A
-></H3
-><P
->The <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> command copies the needed files
-for convenient Windows client installations from the previously prepared CUPS
-data directory to your [print$] share. Additionally, the PPD
-associated with this printer is copied from <TT
-CLASS="FILENAME"
->/etc/cups/ppd/</TT
-> to
-[print$].</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-> <B
-CLASS="COMMAND"
->cupsaddsmb -U root infotec_IS2027</B
->
-Password for root required to access localhost via SAMBA: <KBD
-CLASS="USERINPUT"
->[type in password 'secret']</KBD
-></PRE
-></P
-><P
->To share all printers and drivers, use the <VAR
-CLASS="PARAMETER"
->-a</VAR
->
-parameter instead of a printer name.</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->Note: The following line shave been wrapped so that information is not lost.
- 
-<SAMP
-CLASS="PROMPT"
->root# </SAMP
-> cupsaddsmb -v -U root infotec_IS2027
-    Password for root required to access localhost via SAMBA:
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
-       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
-       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
-       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
-      (average 17395.2 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
-      (average 11343.0 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
-      (average 9260.4 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
-      (average 9247.1 kb/s)
-
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
-      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
-      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
-      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
-      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
-      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
-      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
-      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
-      (average 26092.8 kb/s)
-    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
-      (average 11812.9 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
-      (average 14679.3 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
-      (average 14281.5 kb/s)
-    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
-      (average 12944.0 kb/s)
-    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
-      (average 13169.7 kb/s)
-    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
-      (average 13266.7 kb/s)
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
-       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
-    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
-       ADOBEPSU.HLP:NULL:RAW:NULL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
-       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
-       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
-       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret'
-       -c 'setdriver infotec_IS2027 infotec_IS2027'
-    cmd = setdriver infotec_IS2027 infotec_IS2027
-    Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
-    <SAMP
-CLASS="PROMPT"
->root# </SAMP
-></PRE
-></P
-><P
->If you look closely, you'll discover your root password was transfered unencrypted over
-the wire, so beware! Also, if you look further her, you'll discover error messages like
-<CODE
-CLASS="CONSTANT"
->NT_STATUS_OBJECT_NAME_COLLISION</CODE
-> in between. They occur, because
-the directories <TT
-CLASS="FILENAME"
->WIN40</TT
-> and <TT
-CLASS="FILENAME"
->W32X86</TT
-> already
-existed in the [print$] driver download share (from a previous driver
-installation). They are harmless here.</P
-><P
->Now your printer is prepared for the clients to use. From
-a client, browse to the CUPS/Samba server, open the "Printers"
-share, right-click on this printer and select "Install..." or
-"Connect..." (depending on the Windows version you use). Now their
-should be a new printer in your client's local "Printers" folder,
-named (in my case) "infotec_IS2027 on kdebitshop"</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->
-<B
-CLASS="COMMAND"
->cupsaddsmb</B
-> will only reliably work i
-with CUPS version 1.1.15 or higher
-and Samba from 2.2.4. If it doesn't work, or if the automatic printer
-driver download to the clients doesn't succeed, you can still manually
-install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients and then point the client's printer queue to the Samba printer
-share for connection, should you desire to use the CUPS networked
-PostScript RIP functions.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2205"
->13.8. The CUPS Filter Chains</A
-></H2
-><P
->The following diagrams reveal how CUPS handles print jobs.</P
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#     <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#    <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->                          V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend &#62;------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#     <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     gsrip
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#    <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->                          V
-#      |   (= "raster driver")      +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend &#62;------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#     <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript                                     |
-#                  | at work...                                      |
-#                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
-#                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
-#                  |                                                 |
-#                  +------------------v------------------------------+
-#                                     |
-#                                     |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+
-#      |
-#      |
-#      V
-#     rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-#       Ghostscript. GNU Ghostscript needs to be patched to handle the
-#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->"
-#       Note the difference to "cupsomatic", which will *not* output
-#       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
-#       devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-#      |
-#      |
-#      V
-#     <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            <VAR
+>Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN1534"
+>11.1. Viewing and changing UNIX permissions using the NT 
+	security dialogs</A
+></H2
+><P
+>Windows NT clients can use their native security settings 
+	dialog box to view and modify the underlying UNIX permissions.</P
+><P
+>Note that this ability is careful not to compromise 
+	the security of the UNIX host Samba is running on, and 
+	still obeys all the file permission rules that a Samba 
+	administrator can set.</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
+>	All access to Unix/Linux system file via Samba is controlled at
+	the operating system file access control level. When trying to
+	figure out file access problems it is vitally important to identify
+	the identity of the Windows user as it is presented by Samba at
+	the point of file access. This can best be determined from the
+	Samba log files.
+	</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1540"
+>11.2. How to view file security on a Samba share</A
+></H2
+><P
+>From an NT4/2000/XP client, single-click with the right 
+	mouse button on any file or directory in a Samba mounted 
+	drive letter or UNC path. When the menu pops-up, click 
+	on the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Properties</I
+></SPAN
+> entry at the bottom of 
+	the menu. This brings up the file properties dialog
+	box. Click on the tab <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Security</I
+></SPAN
+> and you 
+	will see three buttons, <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Permissions</I
+></SPAN
+>, 	
+	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+>, and <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Ownership</I
+></SPAN
+>. 
+	The <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+> button will cause either 
+	an error message <SPAN
+CLASS="ERRORNAME"
+>A requested privilege is not held 
+	by the client</SPAN
+> to appear if the user is not the 
+	NT Administrator, or a dialog which is intended to allow an 
+	Administrator to add auditing requirements to a file if the 
+	user is logged on as the NT Administrator. This dialog is 
+	non-functional with a Samba share at this time, as the only 
+	useful button, the <B
+CLASS="COMMAND"
+>Add</B
+> button will not currently 
+	allow a list of users to be seen.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1551"
+>11.3. Viewing file ownership</A
+></H2
+><P
+>Clicking on the <B
+CLASS="COMMAND"
+>"Ownership"</B
+> button 
+	brings up a dialog box telling you who owns the given file. The 
+	owner name will be of the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
+></P
+><P
+>Where <VAR
 CLASS="REPLACEABLE"
->s.th.</VAR
->"        |
-#                  | "-sDEVICE=cups")   .                            |
-#                  |                    .                            |
-#                  | (CUPS standard)    .      (cupsomatic)          |
-#                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
-#                  |                    .                            |
-#                  +------------------v--------------v---------------+
-#                                     |              |
-#                                     |              |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+              |
-#      |                                             |
-#      |                                             |
-#      V                                             |
-#     rasterto<VAR
+>SERVER</VAR
+> is the NetBIOS name of 
+	the Samba server, <VAR
 CLASS="REPLACEABLE"
->something</VAR
->                            |
-#      |   (= "raster driver")                       |
-#      |                                             |
-#      V                                             |
-# SOMETHING-DEVICE-SPECIFIC &#62;------------------------+
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+>user</VAR
+> is the user name of 
+	the UNIX user who owns the file, and <VAR
 CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-##########################################################################</PRE
+>(Long name)</VAR
+>
+	is the descriptive string identifying the user (normally found in the
+	GECOS field of the UNIX password database). Click on the <B
+CLASS="COMMAND"
+>Close
+	</B
+> button to remove this dialog.</P
+><P
+>If the parameter <VAR
+CLASS="PARAMETER"
+>nt acl support</VAR
+>
+	is set to <CODE
+CLASS="CONSTANT"
+>false</CODE
+> then the file owner will 
+	be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+>.</P
+><P
+>The <B
+CLASS="COMMAND"
+>Take Ownership</B
+> button will not allow 
+	you to change the ownership of this file to yourself (clicking on 
+	it will display a dialog box complaining that the user you are 
+	currently logged onto the NT client cannot be found). The reason 
+	for this is that changing the ownership of a file is a privileged 
+	operation in UNIX, available only to the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>root</I
+></SPAN
+> 
+	user. As clicking on this button causes NT to attempt to change 
+	the ownership of a file to the current user logged into the NT 
+	client this will not work with Samba at this time.</P
+><P
+>There is an NT chown command that will work with Samba 
+	and allow a user with Administrator privilege connected 
+	to a Samba server as root to change the ownership of 
+	files on both a local NTFS filesystem or remote mounted NTFS 
+	or Samba drive. This is available as part of the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Seclib
+	</I
+></SPAN
+> NT security library written by Jeremy Allison of 
+	the Samba Team, available from the main Samba ftp site.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2244"
->13.9. CUPS Print Drivers and Devices</A
+NAME="AEN1571"
+>11.4. Viewing file or directory permissions</A
 ></H2
 ><P
->CUPS ships with good support for HP LaserJet type printers. You can install
-the driver as follows:
-
-<P
+>The third button is the <B
+CLASS="COMMAND"
+>"Permissions"</B
+> 
+	button. Clicking on this brings up a dialog box that shows both 
+	the permissions and the UNIX owner of the file or directory. 
+	The owner is displayed in the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
 ></P
-><UL
-><LI
 ><P
->	lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
-	</P
-></LI
-></UL
+>Where <VAR
+CLASS="REPLACEABLE"
+>SERVER</VAR
+> is the NetBIOS name of 
+	the Samba server, <VAR
+CLASS="REPLACEABLE"
+>user</VAR
+> is the user name of 
+	the UNIX user who owns the file, and <VAR
+CLASS="REPLACEABLE"
+>(Long name)</VAR
 >
-
-(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
-for not-yet-installed-PPDs, which CUPS typically stores in 
-<TT
-CLASS="FILENAME"
->/usr/share/cups/model</TT
->. Alternatively, you may use
-"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").</P
+	is the descriptive string identifying the user (normally found in the
+	GECOS field of the UNIX password database).</P
+><P
+>If the parameter <VAR
+CLASS="PARAMETER"
+>nt acl support</VAR
+>
+	is set to <CODE
+CLASS="CONSTANT"
+>false</CODE
+> then the file owner will 
+	be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+> and the 
+	permissions will be shown as NT "Full Control".</P
+><P
+>The permissions field is displayed differently for files 
+	and directories, so I'll describe the way file permissions 
+	are displayed first.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1586"
+>11.4.1. File Permissions</A
+></H3
+><P
+>The standard UNIX user/group/world triple and 
+		the corresponding "read", "write", "execute" permissions 
+		triples are mapped by Samba into a three element NT ACL 
+		with the 'r', 'w', and 'x' bits mapped into the corresponding 
+		NT permissions. The UNIX world permissions are mapped into 
+		the global NT group <B
+CLASS="COMMAND"
+>Everyone</B
+>, followed 
+		by the list of permissions allowed for UNIX world. The UNIX 
+		owner and group permissions are displayed as an NT 
+		<B
+CLASS="COMMAND"
+>user</B
+> icon and an NT <B
+CLASS="COMMAND"
+>local 
+		group</B
+> icon respectively followed by the list 
+	 	of permissions allowed for the UNIX user and group.</P
+><P
+>As many UNIX permission sets don't map into common 
+		NT names such as <B
+CLASS="COMMAND"
+>"read"</B
+>, <B
+CLASS="COMMAND"
+>		"change"</B
+> or <B
+CLASS="COMMAND"
+>"full control"</B
+> then 
+		usually the permissions will be prefixed by the words <B
+CLASS="COMMAND"
+>		"Special Access"</B
+> in the NT display list.</P
+><P
+>But what happens if the file has no permissions allowed 
+		for a particular UNIX user group or world component ? In order 
+		to  allow "no permissions" to be seen and modified then Samba 
+		overloads the NT <B
+CLASS="COMMAND"
+>"Take Ownership"</B
+> ACL attribute 
+		(which has no meaning in UNIX) and reports a component with 
+		no permissions as having the NT <B
+CLASS="COMMAND"
+>"O"</B
+> bit set. 
+		This was chosen of course to make it look like a zero, meaning 
+		zero permissions. More details on the decision behind this will 
+		be given below.</P
+></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2251"
->13.9.1. Further printing steps</A
+NAME="AEN1600"
+>11.4.2. Directory Permissions</A
 ></H3
 ><P
->Always also consult the database on linuxprinting.org for all recommendations
-about which driver is best used for each printer:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/printer_list.cgi"
-TARGET="_top"
->http://www.linuxprinting.org/printer_list.cgi</A
-></P
-><P
->There select your model and click on "Show". You'll arrive at a page listing
-all drivers working with your model. There will always be *one* 
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->recommended</I
-></SPAN
-> one. Try this one first. In your case
-("HP LaserJet 4 Plus"), you'll arrive here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/show_printer.cgi?recnum=75104"
-TARGET="_top"
->http://www.linuxprinting.org/show_printer.cgi?recnum=75104</A
-></P
+>Directories on an NT NTFS file system have two 
+		different sets of permissions. The first set of permissions 
+		is the ACL set on the directory itself, this is usually displayed 
+		in the first set of parentheses in the normal <B
+CLASS="COMMAND"
+>"RW"</B
+> 
+		NT style. This first set of permissions is created by Samba in 
+		exactly the same way as normal file permissions are, described 
+		above, and is displayed in the same way.</P
 ><P
->The recommended driver is "ljet4". It has a link to the page for the ljet4
-driver too:</P
+>The second set of directory permissions has no real meaning 
+		in the UNIX permissions world and represents the <B
+CLASS="COMMAND"
+>		"inherited"</B
+> permissions that any file created within 
+		this directory would inherit.</P
 ><P
+>Samba synthesises these inherited permissions for NT by 
+		returning as an NT ACL the UNIX permission mode that a new file 
+		created by Samba on this share would receive.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-HREF="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4"
-TARGET="_top"
->http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</A
->&#13;</P
-><P
->On the driver's page, you'll find important and detailed info about how to use
-that driver within the various available spoolers. You can generate a PPD for
-CUPS. The PPD contains all the info about how to use your model and the driver;
-this is, once installed, working transparently for the user -- you'll only
-need to choose resolution, paper size etc. from the web-based menu or from
-the print dialog GUI or from the commandline...</P
-><P
->On the driver's page, choose to use the "PPD-O-Matic" online PPD generator
-program. Select your model and click "Generate PPD file". When you safe the
-appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt
-line endings and tabs), but use "Save as..." in your browser's menu. Save it
-at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</P
-><P
->Then install the printer:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->    "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
-          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</PRE
-></P
-><P
->Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need
-a special "CUPS filter" named "cupsomatic". Get the latest version of
-"cupsomatic" from:</P
+NAME="AEN1607"
+>11.5. Modifying file or directory permissions</A
+></H2
 ><P
-><A
-HREF="http://www.linuxprinting.org/cupsomatic"
-TARGET="_top"
->http://www.linuxprinting.org/cupsomatic</A
-></P
+>Modifying file and directory permissions is as simple 
+	as changing the displayed permissions in the dialog box, and 
+	clicking the <B
+CLASS="COMMAND"
+>OK</B
+> button. However, there are 
+	limitations that a user needs to be aware of, and also interactions 
+	with the standard Samba permission masks and mapping of DOS 
+	attributes that need to also be taken into account.</P
 ><P
->This needs to be copied to <TT
-CLASS="FILENAME"
->/usr/lib/cups/filter/cupsomatic</TT
+>If the parameter <VAR
+CLASS="PARAMETER"
+>nt acl support</VAR
 >
-and be made world executable. This filter is needed to read and act upon the
-specially encoded Foomatic comments, embedded in the printfile, which in turn
-are used to construct (transparently for you, the user) the complicated
-ghostscript command line needed for your printer/driver combo.</P
+	is set to <CODE
+CLASS="CONSTANT"
+>false</CODE
+> then any attempt to set 
+	security permissions will fail with an <B
+CLASS="COMMAND"
+>"Access Denied"
+	</B
+> message.</P
 ><P
->You can have a look at all the options for the Ghostscript commandline supported
-by your printer and the ljet4 driver by going to the section "Execution details",
-selecting your model (Laserjet 4 Plus) and clicking on "Show execution details".
-This will bring up this web page:</P
+>The first thing to note is that the <B
+CLASS="COMMAND"
+>"Add"</B
+> 
+	button will not return a list of users in Samba (it will give 
+	an error message of <B
+CLASS="COMMAND"
+>"The remote procedure call failed 
+	and did not execute"</B
+>). This means that you can only 
+	manipulate the current user/group/world permissions listed in 
+	the dialog box. This actually works quite well as these are the 
+	only permissions that UNIX actually has.</P
 ><P
-><A
-HREF="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details"
-TARGET="_top"
->http://www.linuxprinting.org/execution.cgi?driver=ljet4&#38;printer=75104&#38;.submit=Show+execution+details</A
-></P
+>If a permission triple (either user, group, or world) 
+	is removed from the list of permissions in the NT dialog box, 
+	then when the <B
+CLASS="COMMAND"
+>"OK"</B
+> button is pressed it will 
+	be applied as "no permissions" on the UNIX side. If you then 
+	view the permissions again the "no permissions" entry will appear 
+	as the NT <B
+CLASS="COMMAND"
+>"O"</B
+> flag, as described above. This 
+	allows you to add permissions back to a file or directory once 
+	you have removed them from a triple component.</P
 ><P
->The ingenious thing is that the database is kept current. If there
-is a bug fix and an improvement somewhere in the database, you will
-always get the most current and stable and feature-rich driver by following
-the steps described above.</P
-><DIV
-CLASS="NOTE"
+>As UNIX supports only the "r", "w" and "x" bits of 
+	an NT ACL then if other NT security attributes such as "Delete 
+	access" are selected then they will be ignored when applied on 
+	the Samba server.</P
 ><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"
+>When setting permissions on a directory the second 
+	set of permissions (in the second set of parentheses) is 
+	by default applied to all files within that directory. If this 
+	is not what you want you must uncheck the <B
+CLASS="COMMAND"
+>"Replace 
+	permissions on existing files"</B
+> checkbox in the NT 
+	dialog before clicking <B
+CLASS="COMMAND"
+>"OK"</B
+>.</P
 ><P
->Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
-people are aware of. (So if you use it often, please send him a note showing
-your appreciation).</P
-></TD
-></TR
-></TABLE
+>If you wish to remove all permissions from a 
+	user/group/world  component then you may either highlight the 
+	component and click the <B
+CLASS="COMMAND"
+>"Remove"</B
+> button, 
+	or set the component to only have the special <B
+CLASS="COMMAND"
+>"Take
+	Ownership"</B
+> permission (displayed as <B
+CLASS="COMMAND"
+>"O"
+	</B
+>) highlighted.</P
 ></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1629"
+>11.6. Interaction with the standard Samba create mask 
+	parameters</A
+></H2
 ><P
->The latest and greatest improvement now is support for "custom page sizes"
-for all those printers which support it.</P
-><P
->"cupsomatic" is documented here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/cups-doc.html"
-TARGET="_top"
->http://www.linuxprinting.org/cups-doc.html</A
-></P
-><P
->More printing tutorial info may be found here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/"
-TARGET="_top"
->http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</A
-></P
-><P
->Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
-approaching the "all-time high" number of 1.000 for the supported models)
-are using a special filtering chain involving Ghostscript, as described
-in this document.</P
-><P
->Summary - You need:</P
-><P
+>There are four parameters 
+	to control interaction with the standard Samba create mask parameters.
+	These are :</P
 ><P
+><VAR
+CLASS="PARAMETER"
+>security mask</VAR
 ></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->A "foomatic+<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" PPD is not enough to print with CUPS (but it is *one* important component)</TD
-></TR
-><TR
-><TD
->The "cupsomatic" filter script (Perl) in <TT
-CLASS="FILENAME"
->/usr/lib/cups/filters/</TT
-></TD
-></TR
-><TR
-><TD
->Perl to make cupsomatic run</TD
-></TR
-><TR
-><TD
->Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</TD
-></TR
-><TR
-><TD
->Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</TD
-></TR
-></TBODY
-></TABLE
 ><P
+><VAR
+CLASS="PARAMETER"
+>force security mode</VAR
 ></P
->&#13;</P
-><P
->In the case of the "hpijs" driver, you need a Ghostscript version, which
-has "ijs" amongst its supported devices in "gs -h". In the case of
-"hpijs+foomatic", a valid ghostscript commandline would be reading like this:</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->       gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
-             -sIjsServer=hpijs<VAR
-CLASS="REPLACEABLE"
->PageSize</VAR
-> -dDuplex=<VAR
-CLASS="REPLACEABLE"
->Duplex</VAR
-> <VAR
-CLASS="REPLACEABLE"
->Model</VAR
->        \
-             -r<VAR
-CLASS="REPLACEABLE"
->Resolution</VAR
->,PS:MediaPosition=<VAR
-CLASS="REPLACEABLE"
->InputSlot</VAR
-> -dIjsUseOutputFD \
-             -sOutputFile=- -</PRE
+><VAR
+CLASS="PARAMETER"
+>directory security mask</VAR
 ></P
-><DIV
-CLASS="NOTE"
 ><P
+><VAR
+CLASS="PARAMETER"
+>force directory security mode</VAR
 ></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
->Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic)
-you don't need to remember this. You can choose the available print options
-thru a GUI print command (like "glp" from ESP's commercially supported
-PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent
-"xpp") or the CUPS web interface via human-readable drop-down selection
-menus.</P
-></TD
-></TR
-></TABLE
-></DIV
 ><P
->If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software
-Products, the makers of CUPS, downloadable from
-<A
-HREF="http://www.cups.org/software.html"
+>Once a user clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> to apply the 
+	permissions Samba maps the given permissions into a user/group/world 
+	r/w/x triple set, and then will check the changed permissions for a 
+	file against the bits set in the <A
+HREF="smb.conf.5.html#SECURITYMASK"
 TARGET="_top"
->http://www.cups.org/software.html</A
->,
-co-maintained by the developers of linuxprinting.org), you are guaranteed to
-have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
-Ghostscript. It contains support for ~300 devices, whereas plain vanilla
-GNU Ghostscript 7.05 only has ~200.</P
+> 
+	<VAR
+CLASS="PARAMETER"
+>security mask</VAR
+></A
+> parameter. Any bits that 
+	were changed that are not set to '1' in this parameter are left alone 
+	in the file permissions.</P
 ><P
->If you print only one CUPS test page, from the web interface and when you try to
-print a windows test page, it acts like the job was never sent:
-
-<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Can you print "standard" jobs from the CUPS machine?</TD
-></TR
-><TR
-><TD
->Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</TD
-></TR
-><TR
-><TD
-><SPAN
+>Essentially, zero bits in the <VAR
+CLASS="PARAMETER"
+>security mask</VAR
+>
+	mask may be treated as a set of bits the user is <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->Most important:</I
+>not</I
 ></SPAN
-> What kind of printer driver are you using on the Windows clients?</TD
-></TR
-></TBODY
-></TABLE
+> 
+	allowed to change, and one bits are those the user is allowed to change.
+	</P
+><P
+>If not set explicitly this parameter is set to the same value as 
+	the <A
+HREF="smb.conf.5.html#CREATEMASK"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>create mask
+	</VAR
+></A
+> parameter. To allow a user to modify all the
+	user/group/world permissions on a file, set this parameter 
+	to 0777.</P
+><P
+>Next Samba checks the changed permissions for a file against 
+	the bits set in the <A
+HREF="smb.conf.5.html#FORCESECURITYMODE"
+TARGET="_top"
+>	<VAR
+CLASS="PARAMETER"
+>force security mode</VAR
+></A
+> parameter. Any bits 
+	that were changed that correspond to bits set to '1' in this parameter 
+	are forced to be set.</P
+><P
+>Essentially, bits set in the <VAR
+CLASS="PARAMETER"
+>force security mode
+	</VAR
+> parameter may be treated as a set of bits that, when 
+	modifying security on a file, the user has always set to be 'on'.</P
+><P
+>If not set explicitly this parameter is set to the same value 
+	as the <A
+HREF="smb.conf.5.html#FORCECREATEMODE"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>force 
+	create mode</VAR
+></A
+> parameter.
+	To allow a user to modify all the user/group/world permissions on a file
+	with no restrictions set this parameter to 000.</P
+><P
+>The <VAR
+CLASS="PARAMETER"
+>security mask</VAR
+> and <VAR
+CLASS="PARAMETER"
+>force 
+	security mode</VAR
+> parameters are applied to the change 
+	request in that order.</P
+><P
+>For a directory Samba will perform the same operations as 
+	described above for a file except using the parameter <VAR
+CLASS="PARAMETER"
+>	directory security mask</VAR
+> instead of <VAR
+CLASS="PARAMETER"
+>security 
+	mask</VAR
+>, and <VAR
+CLASS="PARAMETER"
+>force directory security mode
+	</VAR
+> parameter instead of <VAR
+CLASS="PARAMETER"
+>force security mode
+	</VAR
+>.</P
+><P
+>The <VAR
+CLASS="PARAMETER"
+>directory security mask</VAR
+> parameter 
+	by default is set to the same value as the <VAR
+CLASS="PARAMETER"
+>directory mask
+	</VAR
+> parameter and the <VAR
+CLASS="PARAMETER"
+>force directory security 
+	mode</VAR
+> parameter by default is set to the same value as 
+ 	the <VAR
+CLASS="PARAMETER"
+>force directory mode</VAR
+> parameter. </P
+><P
+>In this way Samba enforces the permission restrictions that 
+	an administrator can set on a Samba share, whilst still allowing users 
+	to modify the permission bits within that restriction.</P
 ><P
-></P
->
-
-You can try to get a more detailed debugging info by setting "LogLevel debug" in
-<TT
-CLASS="FILENAME"
->/etc/cups/cupsd.conf</TT
->, re-start cupsd and investigate <TT
+>If you want to set up a share that allows users full control
+	in modifying the permission bits on their files and directories and
+	doesn't force any particular bits to be set 'on', then set the following
+	parameters in the <TT
 CLASS="FILENAME"
->/var/log/cups/error_log</TT
->
-for the whereabouts of your Windows-originating printjobs:</P
+>smb.conf</TT
+> file in that share specific section :</P
 ><P
+><VAR
+CLASS="PARAMETER"
+>security mask = 0777</VAR
+></P
+><P
+><VAR
+CLASS="PARAMETER"
+>force security mode = 0</VAR
 ></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</TD
-></TR
-><TR
-><TD
->are there "filter" available for this MIME type?</TD
-></TR
-><TR
-><TD
->are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</TD
-></TR
-></TBODY
-></TABLE
 ><P
+><VAR
+CLASS="PARAMETER"
+>directory security mask = 0777</VAR
+></P
+><P
+><VAR
+CLASS="PARAMETER"
+>force directory security mode = 0</VAR
 ></P
-></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2321"
->13.10. Limiting the number of pages users can print</A
+NAME="AEN1682"
+>11.7. Interaction with the standard Samba file attribute 
+	mapping</A
 ></H2
 ><P
->The feature you want is dependent on the real print subsystem you're using.
-Samba's part is always to receive the job files from the clients (filtered
-*or* unfiltered) and hand it over to this printing subsystem.</P
+>Samba maps some of the DOS attribute bits (such as "read 
+	only") into the UNIX permissions of a file. This means there can 
+	be a conflict between the permission bits set via the security 
+	dialog and the permission bits set by the file attribute mapping.
+	</P
 ><P
->Of course one could "hack" things with one's own scripts.</P
+>One way this can show up is if a file has no UNIX read access
+	for the owner it will show up as "read only" in the standard 
+	file attributes tabbed dialog. Unfortunately this dialog is
+	the same one that contains the security info in another tab.</P
 ><P
->But there is CUPS (Common Unix Printing System). CUPS supports "quotas".
-Quotas can be based on sizes of jobs or on the number of pages or both,
-and are spanning any time period you want.</P
+>What this can mean is that if the owner changes the permissions
+	to allow themselves read access using the security dialog, clicks
+	<B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the standard attributes tab 
+	dialog, and then clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> on that dialog, then 
+	NT will set the file permissions back to read-only (as that is what 
+	the attributes still say in the dialog). This means that after setting 
+	permissions and clicking <B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the 
+	attributes dialog you should always hit <B
+CLASS="COMMAND"
+>"Cancel"</B
+> 
+	rather than <B
+CLASS="COMMAND"
+>"OK"</B
+> to ensure that your changes 
+	are not overridden.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="GROUPMAPPING"
+></A
+>Chapter 12. Configuring Group Mapping</H1
 ><P
->This is an example command how root would set a print quota in CUPS,
-assuming an existing printer named "quotaprinter":</P
-><PRE
-CLASS="PROGRAMLISTING"
->  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
-       -o job-page-limit=100</PRE
+> 
+Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
+current method (likely to change) to manage the groups is a new command called
+<SPAN
+CLASS="APPLICATION"
+>smbgroupedit</SPAN
+>.</P
 ><P
->This would limit every single user to print 100 pages or 1024 KB of
-data (whichever comes first) within the last 604.800 seconds ( = 1 week).</P
+>The first immediate reason to use the group mapping on a PDC, is that
+the <B
+CLASS="COMMAND"
+>domain admin group</B
+> of <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> is 
+now gone. This parameter was used to give the listed users local admin rights 
+on their workstations. It was some magic stuff that simply worked but didn't
+scale very well for complex setups.</P
 ><P
->For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter,
-otherwise it uses a "dummy" count of "1". Some printfiles don't pass it
-(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
-proprietary drivers for the target printer running on the client computers and
-CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not
-filtering them), will be counted as "1-pagers" too!</P
+>Let me explain how it works on NT/W2K, to have this magic fade away.
+When installing NT/W2K on a computer, the installer program creates some users
+and groups. Notably the 'Administrators' group, and gives to that group some
+privileges like the ability to change the date and time or to kill any process
+(or close too) running on the local machine. The 'Administrator' user is a
+member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
+group privileges. If a 'joe' user is created and become a member of the
+'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P
+><P
+>When a NT/W2K machine is joined to a domain, during that phase, the "Domain
+Administrators' group of the PDC is added to the 'Administrators' group of the
+workstation. Every members of the 'Domain Administrators' group 'inherit' the
+rights of the 'Administrators' group when logging on the workstation.</P
+><P
+>You are now wondering how to make some of your samba PDC users members of the
+'Domain Administrators' ? That's really easy.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>create a unix group (usually in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>), let's call it domadm</P
+></LI
+><LI
+><P
+>add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+> will look like:</P
 ><P
->You need to send PostScript from the clients (i.e. run a PostScript driver there)
-for having the chance to get accounting done. If the printer is a non-PostScript model,
-you need to let CUPS do the job to convert the file to a print-ready format for the
-target printer. This will be working for currently ~1.000 different printer models, see</P
 ><PRE
 CLASS="PROGRAMLISTING"
->     http://www.linuxprinting.org/printer_list.cgi</PRE
+>domadm:x:502:joe,john,mary</PRE
+></P
+></LI
+><LI
 ><P
->Before CUPS-1.1.16 your only option was to use the Adobe PostScript
-Driver on the Windows clients. The output of this driver was not always
-passed thru the "pstops" filter on the CUPS/Samba side, and therefor was
-not counted correctly (the reason is that it often --- depending on the
-"PPD" being used --- did write a "PJL"-header in front of the real
-PostScript which made CUPS to skip the pstops and go directy to
-the "pstoraster" stage).</P
+>Map this domadm group to the <B
+CLASS="COMMAND"
+>domain admins</B
+> group by running the command:</P
 ><P
->From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver
-for Windows NT/2K/XP clients" (it is tagged in the download area of
-http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package).
-It is *not* working for Win9x/ME clients. But it:</P
+><KBD
+CLASS="USERINPUT"
+>smbgroupedit -c "Domain Admins" -u domadm</KBD
+></P
+></LI
+></OL
+><P
+>You're set, joe, john and mary are domain administrators !</P
 ><P
+>Like the Domain Admins group, you can map any arbitrary Unix group to any NT
+group. You can also make any Unix group a domain group. For example, on a domain
+member machine (an NT/W2K or a samba server running winbind), you would like to
+give access to a certain directory to some users who are member of a group on
+your samba PDC. Flag that group as a domain group by running:</P
+><P
+><KBD
+CLASS="USERINPUT"
+>smbgroupedit -a unixgroup -td</KBD
 ></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->it guarantees to not write an PJL-header</TD
-></TR
-><TR
-><TD
->it guarantees to still read and support all PJL-options named in the driver PPD with its own means</TD
-></TR
-><TR
-><TD
->it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</TD
-></TR
-><TR
-><TD
->it guarantees to page-count correctly the printfile</TD
-></TR
-></TBODY
-></TABLE
+><P
+>You can list the various groups in the mapping database like this</P
+><P
+><KBD
+CLASS="USERINPUT"
+>smbgroupedit -v</KBD
+></P
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PRINTING"
+></A
+>Chapter 13. Printing Support</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN1745"
+>13.1. Introduction</A
+></H2
+><P
+>Beginning with the 2.2.0 release, Samba supports 
+the native Windows NT printing mechanisms implemented via 
+MS-RPC (i.e. the SPOOLSS named pipe).  Previous versions of 
+Samba only supported LanMan printing calls.</P
+><P
+>The additional functionality provided by the new 
+SPOOLSS support includes:</P
 ><P
 ></P
+><UL
+><LI
 ><P
->You can read more about the setup of this combination in the
-manpage for "cupsaddsmb" (only present with CUPS installed, only
-current with CUPS 1.1.16).</P
+>Support for downloading printer driver 
+	files to Windows 95/98/NT/2000 clients upon demand.
+	</P
+></LI
+><LI
 ><P
->These are the items CUPS logs in the "page_log" for every single *page* of a job:</P
+>Uploading of printer drivers via the 
+	Windows NT Add Printer Wizard (APW) or the 
+	Imprints tool set (refer to <A
+HREF="http://imprints.sourceforge.net"
+TARGET="_top"
+>http://imprints.sourceforge.net</A
+>). 
+	</P
+></LI
+><LI
 ><P
+>Support for the native MS-RPC printing 
+	calls such as StartDocPrinter, EnumJobs(), etc...  (See 
+	the MSDN documentation at <A
+HREF="http://msdn.microsoft.com/"
+TARGET="_top"
+>http://msdn.microsoft.com/</A
+> 
+	for more information on the Win32 printing API)
+	</P
+></LI
+><LI
 ><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Printer name</TD
-></TR
-><TR
-><TD
->User name</TD
-></TR
-><TR
-><TD
->Job ID</TD
-></TR
-><TR
-><TD
->Time of printing</TD
-></TR
-><TR
-><TD
->the page number</TD
-></TR
-><TR
-><TD
->the number of copies</TD
-></TR
-><TR
-><TD
->a billing info string (optional)</TD
-></TR
-></TBODY
-></TABLE
+>Support for NT Access Control Lists (ACL) 
+	on printer objects</P
+></LI
+><LI
 ><P
-></P
-></P
+>Improved support for printer queue manipulation 
+	through the use of an internal databases for spooled job 
+	information</P
+></LI
+></UL
 ><P
->Here is an extract of my CUPS server's page_log file to illustrate
-the format and included items:</P
+>There has been some initial confusion about what all this means
+and whether or not it is a requirement for printer drivers to be 
+installed on a Samba host in order to support printing from Windows 
+clients. As a side note, Samba does not use these drivers in any way to process 
+spooled files.  They are utilized entirely by the clients.</P
 ><P
-><SAMP
-CLASS="COMPUTEROUTPUT"
->	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2  #marketing
-	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2  #marketing
-	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2  #marketing
-	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2  #marketing
-	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2  #marketing
-	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2  #marketing</SAMP
+>The following MS KB article, may be of some help if you are dealing with
+Windows 2000 clients:  <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How to Add Printers with No User 
+Interaction in Windows 2000</I
+></SPAN
 ></P
 ><P
->This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job
-printed in 2 copies and billed to "#marketing"...</P
-><P
->What flaws or shortcomings are there?</P
+><A
+HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP"
+TARGET="_top"
+>http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1767"
+>13.2. Configuration</A
+></H2
+><DIV
+CLASS="WARNING"
 ><P
 ></P
 ><TABLE
+CLASS="WARNING"
+WIDTH="100%"
 BORDER="0"
-><TBODY
-><TR
-><TD
->the ones named above</TD
-></TR
 ><TR
 ><TD
->	CUPS really counts the job pages being *processsed in software*
-	(going thru the "RIP") rather than the physical sheets successfully
-	leaving the printing device -- if there is a jam while printing
-	the 5th sheet out of 1000 and the job is aborted by the printer,
-	the "page count" will still show the figure of 1000 for that job
-	</TD
-></TR
-><TR
-><TD
->	all quotas are the same for all users (no flexibility to give the
-	boss a higher quota than the clerk) no support for groups
-	</TD
-></TR
-><TR
-><TD
->	no means to read out the current balance or "used-up" number of current quota
-	</TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>[print$] vs. [printer$]</B
+></TH
 ></TR
 ><TR
 ><TD
->	a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
-	</TD
-></TR
-><TR
+>&nbsp;</TD
 ><TD
->	a user being denied a job because of a filled-up quota doesn't get a meaningful
-	error message from CUPS other than "client-error-not-possible".
-	</TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Previous versions of Samba recommended using a share named [printer$].  
+This name was taken from the printer$ service created by Windows 9x 
+clients when a printer was shared.  Windows 9x printer servers always have 
+a printer$ service which provides read-only access via no 
+password in order to support printer driver downloads.</P
+><P
+>However, the initial implementation allowed for a 
+parameter named <VAR
+CLASS="PARAMETER"
+>printer driver location</VAR
+> 
+to be used on a per share basis to specify the location of 
+the driver files associated with that printer.  Another 
+parameter named <VAR
+CLASS="PARAMETER"
+>printer driver</VAR
+> provided 
+a means of defining the printer driver name to be sent to 
+the client.</P
+></TD
 ></TR
-></TBODY
 ></TABLE
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1775"
+>13.2.1. Creating [print$]</A
+></H3
+><P
+>In order to support the uploading of printer driver 
+files, you must first configure a file share named [print$].  
+The name of this share is hard coded in Samba's internals so 
+the name is very important (print$ is the service used by 
+Windows NT print servers to provide support for printer driver 
+download).</P
+><P
+>You should modify the server's smb.conf file to add the global
+parameters and to create the 
+following file share (of course, some of the parameter values,
+such as 'path' are arbitrary and should be replaced with
+appropriate values for your site):</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+    ; members of the ntadmin group should be able
+    ; to add drivers and set printer properties
+    ; root is implicitly a 'printer admin'
+    printer admin = @ntadmin
+
+[print$]
+    path = /usr/local/samba/printers
+    guest ok = yes
+    browseable = yes
+    read only = yes
+    ; since this share is configured as read only, then we need
+    ; a 'write list'.  Check the file system permissions to make
+    ; sure this account can copy files to the share.  If this
+    ; is setup to a non-root account, then it should also exist
+    ; as a 'printer admin'
+    write list = @ntadmin,root</PRE
 ></P
 ><P
->But this is the best system out there currently. And there are
-huge improvements under development:</P
+>The <A
+HREF="smb.conf.5.html#WRITELIST"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>write list</VAR
+></A
+> is used to allow administrative 
+level user accounts to have write access in order to update files 
+on the share.  See the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5) 
+man page</A
+> for more information on configuring file shares.</P
+><P
+>The requirement for <A
+HREF="smb.conf.5.html#GUESTOK"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>guest 
+ok = yes</B
+></A
+> depends upon how your
+site is configured.  If users will be guaranteed to have 
+an account on the Samba host, then this is a non-issue.</P
+><DIV
+CLASS="NOTE"
 ><P
 ></P
 ><TABLE
+CLASS="NOTE"
+WIDTH="100%"
 BORDER="0"
-><TBODY
-><TR
-><TD
->page counting will go into the "backends" (these talk
-	directly to the printer and will increase the count in sync with the
-	 actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</TD
-></TR
 ><TR
 ><TD
->quotas will be handled more flexibly</TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>Author's Note</B
+></TH
 ></TR
 ><TR
 ><TD
->probably there will be support for users to inquire their "accounts" in advance</TD
-></TR
-><TR
+>&nbsp;</TD
 ><TD
->probably there will be support for some other tools around this topic</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->Other than the current stage of the CUPS development, I don't
-know any other ready-to-use tool which you could consider.</P
+ALIGN="LEFT"
+VALIGN="TOP"
 ><P
->You can download the driver files from
-<A
-HREF="http://www.cups.org/software.html"
+>The non-issue is that if all your Windows NT users are guaranteed to be 
+authenticated by the Samba server (such as a domain member server and the NT 
+user has already been validated by the Domain Controller in 
+order to logon to the Windows NT console), then guest access 
+is not necessary.  Of course, in a workgroup environment where 
+you just want to be able to print without worrying about 
+silly accounts and security, then configure the share for 
+guest access.  You'll probably want to add <A
+HREF="smb.conf.5.html#MAPTOGUEST"
 TARGET="_top"
->http://www.cups.org/software.html</A
->.
-It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16
-Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to
-download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
-the files:</P
+><B
+CLASS="COMMAND"
+>map to guest = Bad User</B
+></A
+> in the [global] section as well.  Make sure 
+you understand what this parameter does before using it 
+though. --jerry</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->	<SAMP
-CLASS="COMPUTEROUTPUT"
->	   cups-samba.install
-	   cups-samba.license
-	   cups-samba.readme
-	   cups-samba.remove
-	   cups-samba.ss
-	</SAMP
->
-	</P
+>In order for a Windows NT print server to support 
+the downloading of driver files by multiple client architectures,
+it must create subdirectories within the [print$] service
+which correspond to each of the supported client architectures.
+Samba follows this model as well.</P
 ><P
->These have been packaged with the ESP meta packager software "EPM". The
-*.install and *.remove files are simple shell script, which untars the
-*.ss (which is nothing else than a tar-archive) and puts its contents
-into <TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. Its contents are 3 files:</P
+>Next create the directory tree below the [print$] share 
+for each architecture you wish to support.</P
 ><P
->	<SAMP
+><SAMP
 CLASS="COMPUTEROUTPUT"
->	   cupsdrvr.dll
-	   cupsui.dll
-	   cups.hlp
-	</SAMP
->
-	</P
+>[print$]-----
+        |-W32X86           ; "Windows NT x86"
+        |-WIN40            ; "Windows 95/98"
+        |-W32ALPHA         ; "Windows NT Alpha_AXP"
+        |-W32MIPS          ; "Windows NT R4000"
+        |-W32PPC           ; "Windows NT PowerPC"</SAMP
+></P
 ><DIV
-CLASS="CAUTION"
+CLASS="WARNING"
 ><P
 ></P
 ><TABLE
-CLASS="CAUTION"
+CLASS="WARNING"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -12492,2063 +8123,2719 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/caution.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
-ALT="Caution"></TD
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>ATTENTION!  REQUIRED PERMISSIONS</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->Due to a bug one CUPS release puts the <TT
-CLASS="FILENAME"
->cups.hlp</TT
+>In order to currently add a new driver to you Samba host, 
+one of two conditions must hold true:</P
+><P
+></P
+><UL
+><LI
+><P
+>The account used to connect to the Samba host 
+	must have a uid of 0 (i.e. a root account)</P
+></LI
+><LI
+><P
+>The account used to connect to the Samba host
+	must be a member of the <A
+HREF="smb.conf.5.html#PRINTERADMIN"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>printer 
+	admin</VAR
+></A
+> list.</P
+></LI
+></UL
+><P
+>Of course, the connected account must still possess access
+to add files to the subdirectories beneath [print$]. Remember
+that all file shares are set to 'read only' by default.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Once you have created the required [print$] service and 
+associated subdirectories, simply log onto the Samba server using 
+a root (or <VAR
+CLASS="PARAMETER"
+>printer admin</VAR
+>) account
+from a Windows NT 4.0/2k client.  Open "Network Neighbourhood" or
+"My Network Places" and browse for the Samba host.  Once you have located
+the server, navigate to the "Printers..." folder.
+You should see an initial listing of printers
+that matches the printer shares defined on your Samba host.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1810"
+>13.2.2. Setting Drivers for Existing Printers</A
+></H3
+><P
+>The initial listing of printers in the Samba host's 
+Printers folder will have no real printer driver assigned 
+to them. This defaults to a NULL string to allow the use
+of the local Add Printer Wizard on NT/2000 clients.
+Attempting to view the printer properties for a printer
+which has this default driver assigned will result in 
+the error message:</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Device settings cannot be displayed.  The driver 
+for the specified printer is not installed, only spooler 
+properties will be displayed.  Do you want to install the 
+driver now?</I
+></SPAN
+></P
+><P
+>Click "No" in the error dialog and you will be presented with
+the printer properties window.  The way to assign a driver to a 
+printer is to either</P
+><P
+></P
+><UL
+><LI
+><P
+>Use the "New Driver..." button to install 
+	a new printer driver, or</P
+></LI
+><LI
+><P
+>Select a driver from the popup list of 
+	installed drivers.  Initially this list will be empty.</P
+></LI
+></UL
+><P
+>If you wish to install printer drivers for client 
+operating systems other than "Windows NT x86", you will need 
+to use the "Sharing" tab of the printer properties dialog.</P
+><P
+>Assuming you have connected with a root account, you 
+will also be able modify other printer properties such as 
+ACLs and device settings using this dialog box.</P
+><P
+>A few closing comments for this section, it is possible 
+on a Windows NT print server to have printers
+listed in the Printers folder which are not shared.  Samba does
+not make this distinction.  By definition, the only printers of
+which Samba is aware are those which are specified as shares in
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.</P
+><P
+>Another interesting side note is that Windows NT clients do
+not use the SMB printer share, but rather can print directly 
+to any printer on another Windows NT host using MS-RPC.  This
+of course assumes that the printing client has the necessary
+privileges on the remote host serving the printer.  The default
+permissions assigned by Windows NT to a printer gives the "Print"
+permissions to the "Everyone" well-known group.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1826"
+>13.2.3. Support a large number of printers</A
+></H3
+><P
+>One issue that has arisen during the development
+phase of Samba 2.2 is the need to support driver downloads for
+100's of printers.  Using the Windows NT APW is somewhat 
+awkward to say the list.  If more than one printer are using the 
+same driver, the <A
+HREF="rpcclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>rpcclient's
+setdriver command</B
+></A
+> can be used to set the driver
+associated with an installed driver.  The following is example
+of how this could be accomplished:</P
+><P
+><SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
+CLASS="USERINPUT"
+>rpcclient pogo -U root%secret -c "enumdrivers"</KBD
 >
-into <TT
-CLASS="FILENAME"
->/usr/share/drivers/</TT
-> instead of
-<TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. To work around this, copy/move
-the file after running the "./cups-samba.install" script manually to the right place:</P
-><P
->	<KBD
+<PRE
+CLASS="PROGRAMLISTING"
+> 
+Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+ 
+[Windows NT x86]
+Printer Driver Info 1:
+     Driver Name: [HP LaserJet 4000 Series PS]
+ 
+Printer Driver Info 1:
+     Driver Name: [HP LaserJet 2100 Series PS]
+ 
+Printer Driver Info 1:
+     Driver Name: [HP LaserJet 4Si/4SiMX PS]</PRE
+>				  
+<SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
 CLASS="USERINPUT"
-> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-	</KBD
+>rpcclient pogo -U root%secret -c "enumprinters"</KBD
 >
-	</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
+<PRE
+CLASS="PROGRAMLISTING"
+>Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+     flags:[0x800000]
+     name:[\\POGO\hp-print]
+     description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
+     comment:[]
+				  </PRE
+>
+<SAMP
+CLASS="PROMPT"
+>$ </SAMP
+><KBD
+CLASS="USERINPUT"
+>rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""</KBD
+>
+<PRE
+CLASS="PROGRAMLISTING"
+>Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE
 ></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
->This new CUPS PostScript driver is currently binary-only, but free
-no source code is provided (yet). The reason is this: it has
-been developed with the help of the Microsoft Driver Developer Kit (DDK)
-and compiled with Microsoft Visual Studio 6. It is not clear to the driver
-developers if they are allowed to distribute the whole of the source code
-as Free Software. However, they will likely release the "diff" in source
-code under the GPL, so anybody with a license of Visual Studio and a DDK
-will be able to compile for him/herself.</P
-><P
->Once you have run the install script (and possibly manually moved the
-"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be
-put into Samba's [print$] share (which often maps to "/etc/samba/drivers/"
-and contains a subdir tree with WIN40 and W32X86 branches), by running
-"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to
-put root into the smbpasswd file by running "smbpasswd" should you run
-this whole procedure for the first time.] Once the driver files are in the
-[print$] share, they are ready to be downloaded and installed by the
-Win NT/2k/XP clients.</P
-></TD
-></TR
-></TABLE
 ></DIV
 ><DIV
-CLASS="NOTE"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1841"
+>13.2.4. Adding New Printers via the Windows NT APW</A
+></H3
+><P
+>By default, Samba offers all printer shares defined in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+in the "Printers..." folder.  Also existing in this folder is the Windows NT 
+Add Printer Wizard icon.  The APW will be show only if</P
 ><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"
+><UL
+><LI
 ><P
->	Win 9x/ME clients won't work with this driver. For these you'd
-	still need to use the ADOBE*.* drivers as previously.
+>The connected user is able to successfully
+	execute an OpenPrinterEx(\\server) with administrative
+	privileges (i.e. root or <VAR
+CLASS="PARAMETER"
+>printer admin</VAR
+>).
 	</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"
+></LI
+><LI
 ><P
->	It is not harming if you've still the ADOBE*.* driver files from
-	previous installations in the "/usr/share/cups/drivers/" directory.
-	The new cupsaddsmb (from 1.1.16) will automatically use the
-	"newest" installed driver (which here then is the CUPS drivers).
+><A
+HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>show 
+	add printer wizard = yes</VAR
+></A
+> (the default).
 	</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
+></LI
+></UL
 ><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"
+>In order to be able to use the APW to successfully add a printer to a Samba 
+server, the <A
+HREF="smb.conf.5.html#ADDPRINTERCOMMAND"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>add 
+printer command</VAR
+></A
+> must have a defined value.  The program
+hook must successfully add the printer to the system (i.e. 
+<TT
+CLASS="FILENAME"
+>/etc/printcap</TT
+> or appropriate files) and 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> if necessary.</P
+><P
+>When using the APW from a client, if the named printer share does 
+not exist, <B
+CLASS="COMMAND"
+>smbd</B
+> will execute the <VAR
+CLASS="PARAMETER"
+>add printer 
+command</VAR
+> and reparse to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+to attempt to locate the new printer share.  If the share is still not defined,
+an error of "Access Denied" is returned to the client.  Note that the 
+<VAR
+CLASS="PARAMETER"
+>add printer program</VAR
+> is executed under the context
+of the connected user, not necessarily a root account.</P
 ><P
->	Should your Win clients have had the old ADOBE*.* files and the
-	Adobe PostScript drivers installed, the download and installation
-	of the new CUPS PostScript driver for Windows NT/2k/XP will fail
-	at first.
-	</P
+>There is a complementary <A
+HREF="smb.conf.5.html#DELETEPRINTERCOMMAND"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>delete
+printer command</VAR
+></A
+> for removing entries from the "Printers..."
+folder.</P
 ><P
->	It is not enough to "delete" the printer (as the driver files
-	will still be kept by the clients and re-used if you try to
-	re-install the printer). To really get rid of the Adobe driver
-	files on the clients, open the "Printers" folder (possibly via
-	"Start --&#62; Settings --&#62; Control Panel --&#62; Printers"), right-click
-	onto the folder background and select "Server Properties". A
-	new dialog opens; select the "Drivers" tab; on the list select
-	the driver you want to delete and click on the "Delete" button.
-	(This will only work if there is no single printer left which
-	uses that particular driver -- you need to "delete" all printers
-	using this driver in the "Printers" folder first.)
-	</P
-></TD
-></TR
-></TABLE
+>The following is an example <A
+HREF="smb.conf.5.html#ADDPRINTERCOMMAN"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>add printer command</VAR
+></A
+> script. It adds the appropriate entries to <TT
+CLASS="FILENAME"
+>/etc/printcap.local</TT
+> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>#!/bin/sh
+
+# Script to insert a new printer entry into printcap.local
+#
+# $1, printer name, used as the descriptive name
+# $2, share name, used as the printer name for Linux
+# $3, port name
+# $4, driver name
+# $5, location, used for the device file of the printer
+# $6, win9x location
+
+#
+# Make sure we use the location that RedHat uses for local printer defs
+PRINTCAP=/etc/printcap.local
+DATE=`date +%Y%m%d-%H%M%S`
+LP=lp
+RESTART="service lpd restart"
+
+# Keep a copy
+cp $PRINTCAP $PRINTCAP.$DATE
+# Add the printer to $PRINTCAP
+echo ""				 			&#62;&#62; $PRINTCAP
+echo "$2|$1:\\" 					&#62;&#62; $PRINTCAP
+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
+
+mkdir /var/spool/lpd/$2
+chmod 700 /var/spool/lpd/$2
+chown $LP /var/spool/lpd/$2
+#echo $1 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $2 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $3 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $4 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $5 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $6 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+$RESTART &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+# Not sure if this is needed
+touch /usr/local/samba/lib/smb.conf
+#
+# You need to return a value, but I am not sure what it means.
+#
+echo "Done"
+exit 0</PRE
 ></DIV
 ><DIV
-CLASS="NOTE"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1871"
+>13.2.5. Samba and Printer Ports</A
+></H3
 ><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"
+>Windows NT/2000 print servers associate a port with each printer.  These normally
+take the form of LPT1:, COM1:, FILE:, etc...  Samba must also support the
+concept of ports associated with a printer.  By default, only one printer port,
+named "Samba Printer Port", exists on a system.  Samba does not really a port in
+order to print, rather it is a requirement of Windows clients.  </P
 ><P
->	Once you have successfully downloaded the CUPS PostScript driver
-	to a client, you can easily switch all printers to this one
-	by proceeding as described elsewhere in the "Samba HOWTO
-	Collection" to change a driver for an existing printer.
-	</P
-></TD
-></TR
-></TABLE
+>Note that Samba does not support the concept of "Printer Pooling" internally 
+either.  This is when a logical printer is assigned to multiple ports as 
+a form of load balancing or fail over.</P
+><P
+>If you require that multiple ports be defined for some reason,
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> possesses a <A
+HREF="smb.conf.5.html#ENUMPORTSCOMMAND"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>enumports 
+command</VAR
+></A
+> which can be used to define an external program 
+that generates a listing of ports on a system.</P
 ></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1879"
+>13.3. The Imprints Toolset</A
+></H2
 ><P
->What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP"
-as compared to the Adobe drivers?</P
+>The Imprints tool set provides a UNIX equivalent of the 
+	Windows NT Add Printer Wizard.  For complete information, please 
+	refer to the Imprints web site at <A
+HREF="http://imprints.sourceforge.net/"
+TARGET="_top"
+>	http://imprints.sourceforge.net/</A
+> as well as the documentation 
+	included with the imprints source distribution.  This section will 
+	only provide a brief introduction to the features of Imprints.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1883"
+>13.3.1. What is Imprints?</A
+></H3
 ><P
+>Imprints is a collection of tools for supporting the goals 
+		of</P
 ><P
 ></P
 ><UL
 ><LI
 ><P
->	no hassle with the Adobe EULA
-	</P
+>Providing a central repository information 
+			regarding Windows NT and 95/98 printer driver packages</P
 ></LI
 ><LI
 ><P
->	no hassle with the question "where do I get the ADOBE*.* driver files from?"
-	</P
+>Providing the tools necessary for creating 
+			the Imprints printer driver packages.</P
 ></LI
 ><LI
 ><P
->	the Adobe drivers (depending on the printer PPD associated with them)
-	often put a PJL header in front of the core PostScript part of the print
-	file (thus the file starts with "<VAR
-CLASS="REPLACEABLE"
->1B</VAR
->%-12345X" or "<VAR
-CLASS="REPLACEABLE"
->escape</VAR
->%-12345X"
-	instead of "%!PS"). This leads to the CUPS daemon autotyping the
-	arriving file as a print-ready file, not requiring a pass thru the
-	"pstops" filter (to speak more technical, it is not regarded as the
-	generic MIME type "application/postscript", but as the more special
-	MIME type "application/cups.vnd-postscript"), which therefore also
-	leads to the page accounting in "/var/log/cups/page_log" not receiving
-	the exact mumber of pages; instead the dummy page number of "1" is
-	logged in a standard setup)
-	</P
+>Providing an installation client which 
+			will obtain and install printer drivers on remote Samba 
+			and Windows NT 4 print servers.</P
 ></LI
-><LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1893"
+>13.3.2. Creating Printer Driver Packages</A
+></H3
 ><P
->	the Adobe driver has more options to "mis-configure" the PostScript
-	generated by it (like setting it inadvertedly to "Optimize for Speed",
-	instead of "Optimize for Portability", which could lead to CUPS being
-	unable to process it)
-	</P
-></LI
-><LI
+>The process of creating printer driver packages is beyond
+		the scope of this document (refer to Imprints.txt also included
+		with the Samba distribution for more information).  In short,
+		an Imprints driver package is a gzipped tarball containing the
+		driver files, related INF files, and a control file needed by the
+		installation client.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1896"
+>13.3.3. The Imprints server</A
+></H3
+><P
+>The Imprints server is really a database server that 
+		may be queried via standard HTTP mechanisms.  Each printer 
+		entry in the database has an associated URL for the actual
+		downloading of the package.  Each package is digitally signed
+		via GnuPG which can be used to verify that package downloaded
+		is actually the one referred in the Imprints database.  It is 
+		<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not</I
+></SPAN
+> recommended that this security check 
+		be disabled.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1900"
+>13.3.4. The Installation Client</A
+></H3
+><P
+>More information regarding the Imprints installation client 
+		is available in the <TT
+CLASS="FILENAME"
+>Imprints-Client-HOWTO.ps</TT
+> 
+		file included with the imprints source package.</P
 ><P
->	the CUPS PostScript driver output sent by Windows clients to the CUPS
-	server will be guaranteed to be auto-typed as generic MIME type
-	"application/postscript", thusly passing thru the CUPS "pstops" filter
-	and logging the correct number of pages in the page_log for accounting
-	and quota purposes
-	</P
-></LI
-><LI
+>The Imprints installation client comes in two forms.</P
 ><P
->	the CUPS PostScript driver supports the sending of additional print
-	options by the Win NT/2k/XP clients, such as naming the CUPS standard
-	banner pages (or the custom ones, should they be installed at the time
-	of driver download), using the CUPS "page-label" option, setting a
-	job-priority and setting the scheduled time of printing (with the option
-	to support additional useful IPP job attributes in the future).
-	</P
-></LI
+></P
+><UL
 ><LI
 ><P
->	the CUPS PostScript driver supports the inclusion of the new
-	"*cupsJobTicket" comments at the beginnig of the PostScript file (which
-	could be used in the future for all sort of beneficial extensions on
-	the CUPS side, but which will not disturb any other application as those
-	will regard it as a comment and simply ignore it).
-	</P
+>a set of command line Perl scripts</P
 ></LI
 ><LI
 ><P
->	the CUPS PostScript driver will be the heart of the fully fledged CUPS
-	IPP client for Windows NT/2k/XP to be released soon (probably alongside
-	the first Beta release for CUPS 1.2).
-	</P
+>a GTK+ based graphical interface to 
+			the command line perl scripts</P
 ></LI
 ></UL
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2417"
->13.11. Advanced Postscript Printing from MS Windows</A
-></H2
-><P
->Let the Windows Clients use a PostScript driver to deliver poistscript to
-the samba print server (just like any Linux or Unix Client would also use
-PostScript to send to the server)</P
-><P
->Make the Unix printing subsystem to which Samba sends the job convert the
-incoming PostScript files to the native print format of the target printers
-(would be PCL if you have an HP printer)</P
 ><P
->Now if you are afraid that this would just mean using a *Generic* PostScript
-driver for the clients that has no Simplex/Duplex selection, and no paper tray
-choice, but you need them to be able to set up print jobs, with all the bells
-and whistles of your printers:-</P
+>The installation client (in both forms) provides a means
+		of querying the Imprints database server for a matching
+		list of known printer model names as well as a means to 
+		download and install the drivers on remote Samba and Windows
+		NT print servers.</P
 ><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Not possible with traditional spooling systems</TD
-></TR
-><TR
-><TD
->	But perfectly supported by CUPS (which uses "PPD" files to
-	describe how to control the print options for PostScript and
-	non-PostScript devices alike...
-	</TD
-></TR
-></TBODY
-></TABLE
+>The basic installation process is in four steps and 
+		perl code is wrapped around <B
+CLASS="COMMAND"
+>smbclient</B
+> 
+		and <B
+CLASS="COMMAND"
+>rpcclient</B
+>.</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	
+foreach (supported architecture for a given driver)
+{
+     1.  rpcclient: Get the appropriate upload directory 
+         on the remote server
+     2.  smbclient: Upload the driver files
+     3.  rpcclient: Issues an AddPrinterDriver() MS-RPC
+}
+	
+4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
+    create the printer</PRE
 ></P
 ><P
->CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
-drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
-them to setup the job to their liking and CUPS will use the received job options
-to make the (PCL-, ESC/P- or PostScript-) printer behave as required.</P
-><P
->If you want to have the additional benefit of page count logging and accounting
-then the CUPS PostScript driver is the best choice (better than the Adobe one).</P
+>One of the problems encountered when implementing 
+		the Imprints tool set was the name space issues between 
+		various supported client architectures.  For example, Windows 
+		NT includes a driver named "Apple LaserWriter II NTX v51.8" 
+		and Windows 95 calls its version of this driver "Apple 
+		LaserWriter II NTX"</P
 ><P
->If you want to make the drivers downloadable for the clients then "cupsaddsmb" is
-your friend. It will setup the [print$] share on the Samba host to be ready to serve
-the clients for a "point and print" driver installation.</P
-><DIV
-CLASS="WARNING"
+>The problem is how to know what client drivers have 
+		been uploaded for a printer.  As astute reader will remember 
+		that the Windows NT Printer Properties dialog only includes 
+		space for one printer driver name.  A quick look in the 
+		Windows NT 4.0 system registry at</P
 ><P
+><TT
+CLASS="FILENAME"
+>HKLM\System\CurrentControlSet\Control\Print\Environment
+		</TT
 ></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
->What strings are attached?</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->There are some. But, given the sheer CPU power you can buy nowadays,
-these can be overcome easily. The strings:</P
+>will reveal that Windows NT always uses the NT driver 
+		name.  This is ok as Windows NT always requires that at least 
+		the Windows NT version of the printer driver is present.  
+		However, Samba does not have the requirement internally.  
+		Therefore, how can you use the NT driver name if is has not 
+		already been installed?</P
 ><P
->Well, if the CUPS/Samba side will have to print to many printers serving many users,
-you probably will need to set up a second server (which can do automatic load balancing
-with the first one, plus a degree of fail-over mechanism). Converting the incoming
-PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work
-of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM
-than for the mere "raw spooling" task your current setup is solving. It all depends
-on the avarage and peak printing load the server should be able to handle.</P
+>The way of sidestepping this limitation is to require 
+		that all Imprints printer driver packages include both the Intel 
+		Windows NT and 95/98 printer drivers and that NT driver is 
+		installed first.</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2432"
->13.12. Auto-Deletion of CUPS spool files</A
+NAME="AEN1922"
+>13.4. Diagnosis</A
 ></H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN1924"
+>13.4.1. Introduction</A
+></H3
 ><P
->Samba print files pass thru two "spool" directories. One the incoming directory
-managed by Samba, (set eg: in the <B
-CLASS="COMMAND"
->path = /var/spool/samba</B
-> directive in the [printers]
-section of <TT
-CLASS="FILENAME"
->smb.conf</TT
->). Second is the spool directory of your UNIX print subsystem.
-For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive
-"RequestRoot /var/spool/cups".</P
-><P
->I am not sure, which one of your directories keeps the files.  From what you say,
-it is most likely the Samba part.</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
+client to a Samba server, not the other way around. For the reverse
+see the examples/printing directory.</P
 ><P
->For the CUPS part, you may want to consult:</P
+>Ok, so you want to print to a Samba server from your PC. The first
+thing you need to understand is that Samba does not actually do any
+printing itself, it just acts as a middleman between your PC client
+and your Unix printing subsystem. Samba receives the file from the PC
+then passes the file to a external "print command". What print command
+you use is up to you.</P
 ><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobFiles</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobHistory</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#MaxJobs</TD
-></TR
-></TBODY
-></TABLE
+>The whole things is controlled using options in smb.conf. The most
+relevant options (which you should look up in the smb.conf man page)
+are:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>      [global]
+        print command     - send a file to a spooler
+        lpq command       - get spool queue status
+        lprm command      - remove a job
+      [printers]
+        path = /var/spool/lpd/samba</PRE
 ></P
 ><P
->There are the settings described for your CUPS daemon, which could lead to completed
-job files not being deleted.</P
-><P
->"PreserveJobHistory Yes" -- keeps some details of jobs in
-cupsd's mind (well it keeps the "c12345", "c12346" etc. files
-in the CUPS spool directory, which do a similar job as the
-old-fashioned BSD-LPD control files). This is set to "Yes"
-as a default.</P
-><P
->"PreserveJobFiles Yes" -- keeps the job files themselves in
-cupsd's mind (well it keeps the "d12345", "d12346" etc. files
-in the CUPS spool directory...). This is set to "No" as the
-CUPS default.</P
-><P
->"MaxJobs 500" -- this directive controls the maximum number
-of jobs that are kept in memory. Once the number of jobs
-reaches the limit, the oldest completed job is automatically
-purged from the system to make room for the new one. If all
-of the known jobs are still pending or active then the new
-job will be rejected. Setting the maximum to 0 disables this
-functionality. The default setting is 0.</P
-><P
->(There are also additional settings for "MaxJobsPerUser" and
-"MaxJobsPerPrinter"...)</P
-><P
->For everything to work as announced, you need to have three things:</P
+>The following are nice to know about:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>        queuepause command   - stop a printer or print queue
+        queueresume command  - start a printer or print queue</PRE
 ></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->	a Samba-<SPAN
-CLASS="APPLICATION"
->smbd</SPAN
-> which is compiled against "libcups" (Check on Linux by running <KBD
-CLASS="USERINPUT"
->ldd `which smbd`</KBD
->)
-	</TD
-></TR
-><TR
-><TD
->	a Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printing = cups</B
->
-	</TD
-></TR
-><TR
-><TD
->	another Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printcap = cups</B
->
-	</TD
-></TR
-></TBODY
-></TABLE
 ><P
-></P
-><DIV
-CLASS="NOTE"
+>Example:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>        print command = /usr/bin/lpr -r -P%p %s
+        lpq command   = /usr/bin/lpq    -P%p %s
+        lprm command  = /usr/bin/lprm   -P%p %j
+        queuepause command = /usr/sbin/lpc -P%p stop
+        queuepause command = /usr/sbin/lpc -P%p start</PRE
 ></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
->Note, that in this case all other manually set printing-related
-commands (like "print command", "lpq command", "lprm command",
-"lppause command" or "lpresume command") are ignored and they
-should normally have no influence what-so-ever on your printing.</P
-></TD
-></TR
-></TABLE
+>Samba should set reasonable defaults for these depending on your
+system type, but it isn't clairvoyant. It is not uncommon that you
+have to tweak these for local conditions.  The commands should
+always have fully specified pathnames,  as the smdb may not have
+the correct PATH values.</P
+><P
+>When you send a job to Samba to be printed,  it will make a temporary
+copy of it in the directory specified in the [printers] section.
+and it should be periodically cleaned out.  The lpr -r option
+requests that the temporary copy be removed after printing; If
+printing fails then you might find leftover files in this directory,
+and it should be periodically cleaned out.  Samba used the lpq
+command to determine the "job number" assigned to your print job
+by the spooler.</P
+><P
+>The %&#62;letter&#60; are "macros" that get dynamically replaced with appropriate
+values when they are used. The %s gets replaced with the name of the spool
+file that Samba creates and the %p gets replaced with the name of the
+printer. The %j gets replaced with the "job number" which comes from
+the lpq output.</P
 ></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1940"
+>13.4.2. Debugging printer problems</A
+></H3
 ><P
->If you want to do things manually, replace the "printing = cups"
-by "printing = bsd". Then your manually set commands may work
-(haven't tested this), and a "print command = lp -d %P %s; rm %s"
-may do what you need.</P
+>One way to debug printing problems is to start by replacing these
+command with shell scripts that record the arguments and the contents
+of the print file. A simple example of this kind of things might
+be:</P
 ><P
->You forgot to mention the CUPS version you're using. If you did
-set things up as described in the man pages, then the Samba
-spool files should be deleted. Otherwise it may be a bug. On
-the CUPS side, you can control the behaviour as described
-above.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>	print command = /tmp/saveprint %p %s
+
+    #!/bin/saveprint
+    # we make sure that we are the right user
+    /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
+></P
 ><P
->If you have more problems, post the output of these commands:</P
+>Then you print a file and try removing it.  You may find that the
+print queue needs to be stopped in order to see the queue status
+and remove the job:</P
 ><P
-><KBD
-CLASS="USERINPUT"
->   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</KBD
+><PRE
+CLASS="PROGRAMLISTING"
+>&#13;h4: {42} % echo hi &#62;/tmp/hi
+h4: {43} % smbclient //localhost/lw4
+added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
+Password: 
+Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
+smb: \&#62; print /tmp/hi
+putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
+smb: \&#62; queue
+1049     3            hi-17534
+smb: \&#62; cancel 1049
+Error cancelling job 1049 : code 0
+smb: \&#62; cancel 1049
+Job 1049 cancelled
+smb: \&#62; queue
+smb: \&#62; exit</PRE
 ></P
 ><P
->(adapt paths as needed). These commands sanitize the files
-and cut out the empty lines and lines with comments, providing
-the "naked settings" in a compact way.</P
-></DIV
+>The 'code 0' indicates that the job was removed.  The comment
+by the  smbclient is a bit misleading on this.
+You can observe the command output and then and look at the
+/tmp/tmp.print file to see what the results are.  You can quickly
+find out if the problem is with your printing system.  Often people
+have problems with their /etc/printcap file or permissions on
+various print queues.</P
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="WINBIND"
-></A
->Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN2506"
->14.1. Abstract</A
-></H2
+NAME="AEN1949"
+>13.4.3. What printers do I have?</A
+></H3
 ><P
->Integration of UNIX and Microsoft Windows NT through 
-	a unified logon has been considered a "holy grail" in heterogeneous 
-	computing environments for a long time. We present 
-	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->winbind</I
-></SPAN
->, a component of the Samba suite 
-	of programs as a solution to the unified logon problem. Winbind 
-	uses a UNIX implementation 
-	of Microsoft RPC calls, Pluggable Authentication Modules, and the Name 
-	Service Switch to allow Windows NT domain users to appear and operate 
-	as UNIX users on a UNIX machine. This paper describes the winbind 
-	system, explaining the functionality it provides, how it is configured, 
-	and how it works internally.</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
+use:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>    testprns printer /etc/printcap</PRE
+></P
+><P
+>Samba can get its printcap information from a file or from a program.
+You can try the following to see the format of the extracted
+information:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>    testprns -a printer /etc/printcap
+
+    testprns -a printer '|/bin/cat printcap'</PRE
+></P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN2510"
->14.2. Introduction</A
-></H2
+NAME="AEN1957"
+>13.4.4. Setting up printcap and print servers</A
+></H3
 ><P
->It is well known that UNIX and Microsoft Windows NT have 
-	different models for representing user and group information and 
-	use different technologies for implementing them. This fact has 
-	made it difficult to integrate the two systems in a satisfactory 
-	manner.</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
+the print spooler to set up queues and printcap information.</P
 ><P
->One common solution in use today has been to create 
-	identically named user accounts on both the UNIX and Windows systems 
-	and use the Samba suite of programs to provide file and print services 
-	between the two. This solution is far from perfect however, as 
-	adding and deleting users on both sets of machines becomes a chore 
-	and two sets of passwords are required both of which
-	can lead to synchronization problems between the UNIX and Windows 
-	systems and confusion for users.</P
+>Samba requires either a printcap or program to deliver printcap
+information.  This printcap information has the format:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  name|alias1|alias2...:option=value:...</PRE
+></P
+><P
+>For almost all printing systems, the printer 'name' must be composed
+only of alphanumeric or underscore '_' characters.  Some systems also
+allow hyphens ('-') as well.  An alias is an alternative name for the
+printer,  and an alias with a space in it is used as a 'comment'
+about the printer.  The printcap format optionally uses a \ at the end of lines
+to extend the printcap to multiple lines.</P
+><P
+>Here are some examples of printcap files:</P
 ><P
->We divide the unified logon problem for UNIX machines into 
-	three smaller problems:</P
 ><P
 ></P
-><UL
+><OL
+TYPE="1"
 ><LI
 ><P
->Obtaining Windows NT user and group information
-		</P
+>pr              just printer name</P
 ></LI
 ><LI
 ><P
->Authenticating Windows NT users
-		</P
+>pr|alias        printer name and alias</P
 ></LI
 ><LI
 ><P
->Password changing for Windows NT users
-		</P
+>pr|My Printer   printer name, alias used as comment</P
 ></LI
-></UL
-><P
->Ideally, a prospective solution to the unified logon problem 
-	would satisfy all the above components without duplication of 
-	information on the UNIX machines and without creating additional 
-	tasks for the system administrator when maintaining users and 
-	groups on either system. The winbind system provides a simple 
-	and elegant solution to all three components of the unified logon 
-	problem.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2523"
->14.3. What Winbind Provides</A
-></H2
+><LI
 ><P
->Winbind unifies UNIX and Windows NT account management by 
-	allowing a UNIX box to become a full member of a NT domain. Once 
-	this is done the UNIX box will see NT users and groups as if 
-	they were native UNIX users and groups, allowing the NT domain 
-	to be used in much the same manner that NIS+ is used within 
-	UNIX-only environments.</P
+>pr:sh:\        Same as pr:sh:cm= testing
+  :cm= \ 
+  testing</P
+></LI
+><LI
 ><P
->The end result is that whenever any 
-	program on the UNIX machine asks the operating system to lookup 
-	a user or group name, the query will be resolved by asking the 
-	NT domain controller for the specified domain to do the lookup.
-	Because Winbind hooks into the operating system at a low level 
-	(via the NSS name resolution modules in the C library) this 
-	redirection to the NT domain controller is completely 
-	transparent.</P
+>pr:sh           Same as pr:sh:cm= testing
+  :cm= testing</P
+></LI
+></OL
+></P
 ><P
->Users on the UNIX machine can then use NT user and group 
-	names as they would use "native" UNIX names. They can chown files 
-	so that they are owned by NT domain users or even login to the 
-	UNIX machine and run a UNIX X-Window session as a domain user.</P
+>Samba reads the printcap information when first started.  If you make
+changes in the printcap information, then you must do the following:</P
 ><P
->The only obvious indication that Winbind is being used is 
-	that user and group names take the form DOMAIN\user and 
-	DOMAIN\group. This is necessary as it allows Winbind to determine 
-	that redirection to a domain controller is wanted for a particular 
-	lookup and which trusted domain is being referenced.</P
+></P
+><OL
+TYPE="1"
+><LI
 ><P
->Additionally, Winbind provides an authentication service 
-	that hooks into the Pluggable Authentication Modules (PAM) system 
-	to provide authentication via a NT domain to any PAM enabled 
-	applications. This capability solves the problem of synchronizing 
-	passwords between systems since all passwords are stored in a single 
-	location (on the domain controller).</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2530"
->14.3.1. Target Uses</A
-></H3
+>make sure that the print spooler is aware of these changes.
+The LPRng system uses the 'lpc reread' command to do this.</P
+></LI
+><LI
 ><P
->Winbind is targeted at organizations that have an 
-		existing NT based domain infrastructure into which they wish 
-		to put UNIX workstations or servers. Winbind will allow these 
-		organizations to deploy UNIX workstations without having to 
-		maintain a separate account infrastructure. This greatly 
-		simplifies the administrative overhead of deploying UNIX 
-		workstations into a NT based organization.</P
+>make sure that the spool queues, etc., exist and have the
+correct permissions.  The LPRng system uses the 'checkpc -f'
+command to do this.</P
+></LI
+><LI
 ><P
->Another interesting way in which we expect Winbind to 
-		be used is as a central part of UNIX based appliances. Appliances 
-		that provide file and print services to Microsoft based networks 
-		will be able to use Winbind to provide seamless integration of 
-		the appliance into the domain.</P
-></DIV
+>You now should send a SIGHUP signal to the smbd server to have
+it reread the printcap information.</P
+></LI
+></OL
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2534"
->14.4. How Winbind Works</A
-></H2
-><P
->The winbind system is designed around a client/server 
-	architecture. A long running <B
-CLASS="COMMAND"
->winbindd</B
-> daemon 
-	listens on a UNIX domain socket waiting for requests
-	to arrive. These requests are generated by the NSS and PAM 
-	clients and processed sequentially.</P
-><P
->The technologies used to implement winbind are described 
-	in detail below.</P
-><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2539"
->14.4.1. Microsoft Remote Procedure Calls</A
+NAME="AEN1985"
+>13.4.5. Job sent, no output</A
 ></H3
 ><P
->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 
-		Windows NT machines including remote management, user authentication
-		and print spooling. Although initially this work was done 
-		to aid the implementation of Primary Domain Controller (PDC) 
-		functionality in Samba, it has also yielded a body of code which 
-		can be used for other purposes.</P
-><P
->Winbind uses various MSRPC calls to enumerate domain users 
-		and groups and to obtain detailed information about individual 
-		users or groups. Other MSRPC calls can be used to authenticate 
-		NT domain users and to change user passwords. By directly querying 
-		a Windows PDC for user and group information, winbind maps the 
-		NT account information onto UNIX user and group names.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2543"
->14.4.2. Microsoft Active Directory Services</A
-></H3
+>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
+the command to send the file,  but there was no output from the printer.</P
 ><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="AEN2546"
->14.4.3. Name Service Switch</A
-></H3
+>First,  check to make sure that the job REALLY is getting to the
+right print queue.  If you are using a BSD or LPRng print spooler,
+you can temporarily stop the printing of jobs.  Jobs can still be
+submitted, but they will not be printed.  Use:</P
 ><P
->The Name Service Switch, or NSS, is a feature that is 
-		present in many UNIX operating systems. It allows system 
-		information such as hostnames, mail aliases and user information 
-		to be resolved from different sources. For example, a standalone 
-		UNIX workstation may resolve system information from a series of 
-		flat files stored on the local filesystem. A networked workstation 
-		may first attempt to resolve system information from local files, 
-		and then consult a NIS database for user information or a DNS server 
-		for hostname information.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>  lpc -Pprinter stop</PRE
+></P
 ><P
->The NSS application programming interface allows winbind 
-		to present itself as a source of system information when 
-		resolving UNIX usernames and groups.  Winbind uses this interface, 
-		and information obtained from a Windows NT server using MSRPC 
-		calls to provide a new source of account enumeration.  Using standard 
-		UNIX library calls, one can enumerate the users and groups on
-		a UNIX machine running winbind and see all users and groups in 
-		a NT domain plus any trusted domain as though they were local 
-		users and groups.</P
+>Now submit a print job and then use 'lpq -Pprinter' to see if the
+job is in the print queue.  If it is not in the print queue then
+you will have to find out why it is not being accepted for printing.</P
 ><P
->The primary control file for NSS is 
-		<TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
->. 
-		When a UNIX application makes a request to do a lookup 
-		the C library looks in <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> 
-		for a line which matches the service type being requested, for 
-		example the "passwd" service type is used when user or group names 
-		are looked up. This	config line species which implementations 
-		of that service should be tried and in what order. If the passwd 
-		config line is:</P
+>Next, you may want to check to see what the format of the job really
+was.  With the assistance of the system administrator you can view
+the submitted jobs files.  You may be surprised to find that these
+are not in what you would expect to call a printable format.
+You can use the UNIX 'file' utitily to determine what the job
+format actually is:</P
 ><P
-><B
-CLASS="COMMAND"
->passwd: files example</B
+><PRE
+CLASS="PROGRAMLISTING"
+>    cd /var/spool/lpd/printer   # spool directory of print jobs
+    ls                          # find job files
+    file dfA001myhost</PRE
 ></P
 ><P
->then the C library will first load a module called 
-		<TT
-CLASS="FILENAME"
->/lib/libnss_files.so</TT
-> followed by
-		the module <TT
-CLASS="FILENAME"
->/lib/libnss_example.so</TT
->. The 
-		C library will dynamically load each of these modules in turn 
-		and call resolver functions within the modules to try to resolve 
-		the request. Once the request is resolved the C library returns the
-		result to the application.</P
-><P
->This NSS interface provides a very easy way for Winbind 
-		to hook into the operating system. All that needs to be done 
-		is to put <TT
-CLASS="FILENAME"
->libnss_winbind.so</TT
-> in <TT
-CLASS="FILENAME"
->/lib/</TT
-> 
-		then add "winbind" into <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> at 
-		the appropriate place. The C library will then call Winbind to 
-		resolve user and group names.</P
+>You should make sure that your printer supports this format OR that
+your system administrator has installed a 'print filter' that will
+convert the file to a format appropriate for your printer.</P
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2562"
->14.4.4. Pluggable Authentication Modules</A
+NAME="AEN1996"
+>13.4.6. Job sent, strange output</A
 ></H3
 ><P
->Pluggable Authentication Modules, also known as PAM, 
-		is a system for abstracting authentication and authorization 
-		technologies. With a PAM module it is possible to specify different 
-		authentication methods for different system applications without 
-		having to recompile these applications. PAM is also useful
-		for implementing a particular policy for authorization. For example, 
-		a system administrator may only allow console logins from users 
-		stored in the local password file but only allow users resolved from 
-		a NIS database to log in over the network.</P
+>Once you have the job printing, you can then start worrying about
+making it print nicely.</P
 ><P
->Winbind uses the authentication management and password 
-		management PAM interface to integrate Windows NT users into a 
-		UNIX system. This allows Windows NT users to log in to a UNIX 
-		machine and be authenticated against a suitable Primary Domain 
-		Controller. These users can also change their passwords and have 
-		this change take effect directly on the Primary Domain Controller.
-		</P
+>The most common problem is extra pages of output: banner pages
+OR blank pages at the end.</P
 ><P
->PAM is configured by providing control files in the directory 
-		<TT
-CLASS="FILENAME"
->/etc/pam.d/</TT
-> for each of the services that 
-		require authentication. When an authentication request is made 
-		by an application the PAM code in the C library looks up this
-		control file to determine what modules to load to do the 
-		authentication check and in what order. This interface makes adding 
-		a new authentication service for Winbind very easy, all that needs 
-		to be done is that the <TT
-CLASS="FILENAME"
->pam_winbind.so</TT
-> module 
-		is copied to <TT
-CLASS="FILENAME"
->/lib/security/</TT
-> and the PAM 
-		control files for relevant services are updated to allow 
-		authentication via winbind. See the PAM documentation
-		for more details.</P
+>If you are getting banner pages,  check and make sure that the
+printcap option or printer option is configured for no banners.
+If you have a printcap,  this is the :sh (suppress header or banner
+page) option.  You should have the following in your printer.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>   printer: ... :sh</PRE
+></P
+><P
+>If you have this option and are still getting banner pages,  there
+is a strong chance that your printer is generating them for you
+automatically.  You should make sure that banner printing is disabled
+for the printer.  This usually requires using the printer setup software
+or procedures supplied by the printer manufacturer.</P
+><P
+>If you get an extra page of output,  this could be due to problems
+with your job format,  or if you are generating PostScript jobs,
+incorrect setting on your printer driver on the MicroSoft client.
+For example, under Win95 there is a option:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
+></P
+><P
+>that allows you to choose if a Ctrl-D is appended to all jobs.
+This is a very bad thing to do, as most spooling systems will
+automatically add a ^D to the end of the job if it is detected as
+PostScript.  The multiple ^D may cause an additional page of output.</P
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2570"
->14.4.5. User and Group ID Allocation</A
+NAME="AEN2008"
+>13.4.7. Raw PostScript printed</A
 ></H3
 ><P
->When a user or group is created under Windows NT 
-		is it allocated a numerical relative identifier (RID). This is 
-		slightly different to UNIX which has a range of numbers that are 
-		used to identify users, and the same range in which to identify 
-		groups. It is winbind's job to convert RIDs to UNIX id numbers and
-		vice versa.  When winbind is configured it is given part of the UNIX 
-		user id space and a part of the UNIX group id space in which to 
-		store Windows NT users and groups. If a Windows NT user is 
-		resolved for the first time, it is allocated the next UNIX id from 
-		the range. The same process applies for Windows NT groups. Over 
-		time, winbind will have mapped all Windows NT users and groups
-		to UNIX user ids and group ids.</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
+the printer think the job is a text file, or your printer simply
+does not support PostScript.  You may need to enable 'Automatic
+Format Detection' on your printer.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2011"
+>13.4.8. Advanced Printing</A
+></H3
 ><P
->The results of this mapping are stored persistently in 
-		an ID mapping database held in a tdb database). This ensures that 
-		RIDs are mapped to UNIX IDs in a consistent way.</P
+>Note that you can do some pretty magic things by using your
+imagination with the "print command" option and some shell scripts.
+Doing print accounting is easy by passing the %U option to a print
+command shell script. You could even make the print command detect
+the type of output and its size and send it to an appropriate
+printer.</P
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN2574"
->14.4.6. Result Caching</A
+NAME="AEN2014"
+>13.4.9. Real debugging</A
 ></H3
 ><P
->An active system can generate a lot of user and group 
-		name lookups. To reduce the network cost of these lookups winbind 
-		uses a caching scheme based on the SAM sequence number supplied 
-		by NT domain controllers.  User or group information returned 
-		by a PDC is cached by winbind along with a sequence number also 
-		returned by the PDC. This sequence number is incremented by 
-		Windows NT whenever any user or group information is modified. If 
-		a cached entry has expired, the sequence number is requested from 
-		the PDC and compared against the sequence number of the cached entry. 
-		If the sequence numbers do not match, then the cached information 
-		is discarded and up to date information is requested directly 
-		from the PDC.</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
 ></DIV
 ></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="CUPS-PRINTING"
+></A
+>Chapter 14. CUPS Printing Support</H1
 ><DIV
 CLASS="SECT1"
-><HR><H2
+><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2577"
->14.5. Installation and Configuration</A
+NAME="AEN2035"
+>14.1. Introduction</A
 ></H2
 ><P
->Many thanks to John Trostel <A
-HREF="mailto:jtrostel@snapserver.com"
+>The Common Unix Print System (CUPS) has become very popular, but to many it is
+a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
+it works. The result is seen in a large number of posting on the samba mailing lists
+expressing frustration when MS Windows printers appear not to work with a CUPS
+backr-end.</P
+><P
+>This is a good time to point out how CUPS can be used and what it does. CUPS is more
+than just a print spooling system - it is a complete printer management system that
+complies with HTTP and IPP protocols. It can be managed remotely via a web browser
+and it can print using http and ipp protocols.</P
+><P
+>CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
+SMART printers (ie: CUPS does file format conversion as required for the printer). In
+many ways this gives CUPS similar capabilities to the MS Windows print monitoring
+system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
+In any case, let us now move on to explore how one may configure CUPS for interfacing
+with MS Windows print clients via Samba.</P
+><P
+><A
+HREF="http://www.cups.org/"
 TARGET="_top"
->jtrostel@snapserver.com</A
+>CUPS</A
+> is a newcomer in the UNIX printing scene,
+which has convinced many people upon first trial already. However, it has quite a few
+new features, which make it different from other, more traditional printing systems.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2042"
+>14.2. Configuring <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> for CUPS</A
+></H2
+><P
+>Printing with CUPS in the most basic <TT
+CLASS="FILENAME"
+>smb.conf</TT
 >
-for providing the HOWTO for this section.</P
+setup in Samba-3  only needs two settings: <B
+CLASS="COMMAND"
+>printing = cups</B
+> and
+<B
+CLASS="COMMAND"
+>printcap = cups</B
+>. While CUPS itself doesn't need a printcap
+anymore, the <TT
+CLASS="FILENAME"
+>cupsd.conf</TT
+> configuration file knows two directives
+(example: <B
+CLASS="COMMAND"
+>Printcap /etc/printcap</B
+> and <B
+CLASS="COMMAND"
+>PrintcapFormat
+BSD</B
+>), which control if such a file should be created for the
+convenience of third party applications. Make sure it is set! For details see
+<B
+CLASS="COMMAND"
+>man cupsd.conf</B
+> and other CUPS-related documentation.</P
 ><P
->This HOWTO describes how to get winbind services up and running 
-to control access and authenticate users on your Linux box using 
-the winbind services which come with SAMBA 2.2.2.</P
+>If SAMBA is compiled against libcups, then <B
+CLASS="COMMAND"
+>printcap = cups</B
+> uses the
+CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
+with an additional <VAR
+CLASS="PARAMETER"
+>-oraw</VAR
+> option for printing. On a Linux system,
+you can use the <B
+CLASS="COMMAND"
+>ldd</B
+> command to find out details (ldd may not be
+present on other OS platforms, or its function may be embodied by a different command):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>transmeta:/home/kurt # ldd `which smbd`
+        libssl.so.0.9.6 =&#62; /usr/lib/libssl.so.0.9.6 (0x4002d000)
+        libcrypto.so.0.9.6 =&#62; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+        libcups.so.2 =&#62; /usr/lib/libcups.so.2 (0x40123000)
+        libdl.so.2 =&#62; /lib/libdl.so.2 (0x401e8000)
+        libnsl.so.1 =&#62; /lib/libnsl.so.1 (0x401ec000)
+        libpam.so.0 =&#62; /lib/libpam.so.0 (0x40202000)
+        libc.so.6 =&#62; /lib/libc.so.6 (0x4020b000)
+        /lib/ld-linux.so.2 =&#62; /lib/ld-linux.so.2 (0x40000000)</PRE
+></P
+><P
+>The line "libcups.so.2 =&#62; /usr/lib/libcups.so.2
+(0x40123000)" shows there is CUPS support compiled into this version of
+Samba. If this is the case, and <B
+CLASS="COMMAND"
+>printing = cups</B
+> is set, then any
+otherwise manually set print command in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> is ignored.</P
+></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2582"
->14.5.1. Introduction</A
-></H3
+NAME="AEN2062"
+>14.3. CUPS - RAW Print Through Mode</A
+></H2
+><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
->This HOWTO describes the procedures used to get winbind up and 
-running on my RedHat 7.1 system.  Winbind is capable of providing access 
-and authentication control for Windows Domain users through an NT 
-or Win2K PDC for 'regular' services, such as telnet a nd ftp, as
-well for SAMBA services.</P
+>When used in raw print through mode is will be necessary to use the printer
+vendor's drivers in each Windows client PC.</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->This HOWTO has been written from a 'RedHat-centric' perspective, so if 
-you are using another distribution, you may have to modify the instructions 
-somewhat to fit the way your distribution works.</P
+>When CUPS printers are configured for RAW print-through mode operation it is the
+responsibility of the Samba client to fully render the print job (file) in a format
+that is suitable for direct delivery to the printer. In this case CUPS will NOT
+do any print file format conversion work.</P
 ><P
+>The CUPS files that need to be correctly set for RAW mode printers to work are:
+
+<P
 ></P
 ><UL
 ><LI
 ><P
->	<SPAN
+><TT
+CLASS="FILENAME"
+>/etc/cups/mime.types</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/cups/mime.convs</TT
+></P
+></LI
+></UL
+>
+
+Both contain entries that must be uncommented to allow <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->Why should I to this?</I
+>RAW</I
 ></SPAN
->
-	</P
+> mode
+operation.</P
 ><P
->This allows the SAMBA administrator to rely on the 
-	authentication mechanisms on the NT/Win2K PDC for the authentication 
-	of domain members.  NT/Win2K users no longer need to have separate 
-	accounts on the SAMBA server.
-	</P
+>Firstly, to enable CUPS based printing from Samba the following options must be
+enabled in your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file [globals] section:
+
+<P
+></P
+><UL
+><LI
+><P
+>printing = CUPS</P
 ></LI
 ><LI
 ><P
->	<SPAN
+>printcap = CUPS</P
+></LI
+></UL
+>
+
+When these parameters are specified the print directives in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> (as well as in
+samba itself) will be ignored because samba will directly interface with CUPS through
+it's application program interface (API) - so long as Samba has been compiled with
+CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
+printing will use the System V AT&#38;T command set with the <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->Who should be reading this document?</I
+>-oraw</I
 ></SPAN
->
+> 
+option automatically passing through.</P
+><P
+>Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) 
+on the Samba/CUPS server does *not* add any features if a file is really
+printed "raw".  However, if you have loaded the driver for the Windows client from
+the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using
+a "Foomatic" PPD, the PJL header in question is already added on the Windows client,
+at the time when the driver initially generated the PostScript data and CUPS in true
+"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its
+printer communication backend.</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
+>NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce*
+"raw" printing, it only *allows* it.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids
+the process of determining proper treatment while in the print queue system.
+
+<P
+></P
+><UL
+><LI
+><P
+>	Files generated by PCL drivers and directed at PCK printers get auto-typed as
+	<TT
+CLASS="FILENAME"
+>application/octet-stream</TT
+>. Unknown file format types also
+	get auto-typed with this tag.
 	</P
+></LI
+><LI
 ><P
->	This HOWTO is designed for system administrators.  If you are 
-	implementing SAMBA on a file server and wish to (fairly easily) 
-	integrate existing NT/Win2K users from your PDC onto the
-	SAMBA server, this HOWTO is for you.  That said, I am no NT or PAM 
-	expert, so you may find a better or easier way to accomplish 
-	these tasks.
+>	Files generated by a Postscript driver and directed at a Postscript printer
+	are auto-typed depending on the auto-detected most suitable MIME type as:
+
+	<P
+></P
+><UL
+><LI
+><P
+>* application/postscript</P
+></LI
+><LI
+><P
+>* application/vnd.cups-postscript</P
+></LI
+></UL
+>
 	</P
 ></LI
 ></UL
-></DIV
+></P
+><P
+>"application/postscript" first goes thru the "pstops" filter (where the page counting
+and accounting takes place). The outcome will be of MIME type
+"application/vnd.cups-postscript". The pstopsfilter reads and uses information from
+the PPD and inserts user-provided options into the PostScript file. As a consequence,
+the filtered file could possibly have an unwanted PJL header.</P
+><P
+>"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which
+have as their first character string one of "%!" or "&#62;04&#60;%".</P
+><P
+>"application/vnd.cups-postscript" will files which contain the string
+"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the
+first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes
+("&#62;1B&#60;%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS
+or other PPD, will have to be auto-typed as "vnd.cups-postscript".  A file produced
+with a "Generic PostScript driver" will just be tagged "application/postscript".</P
+><P
+>Once the file is in "application/vnd.cups-postscript" format, either "pstoraster"
+or "cupsomatic" will take over (depending on the printer configuration, as
+determined by the PPD in use).</P
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2595"
->14.5.2. Requirements</A
-></H3
+CLASS="NOTE"
 ><P
->If you have a samba configuration file that you are currently 
-using... <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->BACK IT UP!</I
-></SPAN
->  If your system already uses PAM, 
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->back up the <TT
-CLASS="FILENAME"
->/etc/pam.d</TT
-> directory 
-contents!</I
-></SPAN
-> If you haven't already made a boot disk, 
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->MAKE ONE NOW!</I
-></SPAN
 ></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
->Messing with the pam configuration files can make it nearly impossible 
-to log in to yourmachine. That's why you want to be able to boot back 
-into your machine in single user mode and restore your 
-<TT
-CLASS="FILENAME"
->/etc/pam.d</TT
-> back to the original state they were in if 
-you get frustrated with the way things are going.  ;-)</P
+>A printer queue with *no* PPD associated to it is a "raw" printer and all files
+will go directly there as received by the spooler. The exeptions are file types
+"application/octet-stream" which need "passthrough feature" enabled.
+"Raw" queues don't do any filtering at all, they hand the file directly to the
+CUPS backend. This backend is responsible for the sending of the data to the device
+(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://,
+parallel:/, serial:/, usb:/ etc.)</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
->The latest version of SAMBA (version 3.0 as of this writing), now 
-includes a functioning winbindd daemon.  Please refer to the 
-<A
-HREF="http://samba.org/"
-TARGET="_top"
->main SAMBA web page</A
-> or, 
-better yet, your closest SAMBA mirror site for instructions on 
-downloading the source code.</P
+>"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
+They are a Third Party add-on, developed at Linuxprinting.org.  As such, they are
+a brilliant hack to make all models (driven by Ghostscript drivers/filters in
+traditional spoolers) also work via CUPS, with the same (good or bad!) quality
+as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript
+commandline at that stage in the CUPS filtering chain, where "normally" the native
+CUPS "pstoraster" filter would kick in.  cupsomatic by-passes pstoraster, "kidnaps"
+the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
+because the associated CUPS-O-Matic-/Foomatic-PPD specifies:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"</PRE
 ><P
->To allow Domain users the ability to access SAMBA shares and 
-files, as well as potentially other services provided by your 
-SAMBA machine, PAM (pluggable authentication modules) must
-be setup properly on your machine.  In order to compile the 
-winbind modules, you should have at least the pam libraries resident 
-on your system.  For recent RedHat systems (7.1, for instance), that 
-means <TT
-CLASS="FILENAME"
->pam-0.74-22</TT
->.  For best results, it is helpful to also
-install the development packages in <TT
-CLASS="FILENAME"
->pam-devel-0.74-22</TT
->.</P
+>This line persuades CUPS to hand the file to cupsomatic, once it has successfully
+converted it to the MIME type "application/vnd.cups-postscript". This conversion will not
+happen for Jobs arriving from Windows which are auto-typed "application/octet-stream",
+with the according changes in "/etc/cups/mime.types" in place.</P
+></TD
+></TR
+></TABLE
 ></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2609"
->14.5.3. Testing Things Out</A
-></H3
 ><P
->Before starting, it is probably best to kill off all the SAMBA 
-related daemons running on your server.  Kill off all <B
-CLASS="COMMAND"
->smbd</B
->, 
-<B
-CLASS="COMMAND"
->nmbd</B
->, and <B
-CLASS="COMMAND"
->winbindd</B
-> processes that may 
-be running.  To use PAM, you will want to make sure that you have the 
-standard PAM package (for RedHat) which supplies the <TT
-CLASS="FILENAME"
->/etc/pam.d</TT
-> 
-directory structure, including the pam modules are used by pam-aware 
-services, several pam libraries, and the <TT
-CLASS="FILENAME"
->/usr/doc</TT
-> 
-and <TT
-CLASS="FILENAME"
->/usr/man</TT
-> entries for pam.  Winbind built better 
-in SAMBA if the pam-devel package was also installed.  This package includes 
-the header files needed to compile pam-aware applications. For instance, 
-my RedHat system has both <TT
-CLASS="FILENAME"
->pam-0.74-22</TT
-> and
-<TT
-CLASS="FILENAME"
->pam-devel-0.74-22</TT
-> RPMs installed.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2620"
->14.5.3.1. Configure and compile SAMBA</A
-></H4
+>CUPS is widely configurable and flexible, even regarding its filtering mechanism.
+Another workaround in some situations would be to have
+in "/etc/cups/mime.types" entries as follows:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>   application/postscript           application/vnd.cups-raw  0  -
+   application/vnd.cups-postscript  application/vnd.cups-raw  0  -</PRE
 ><P
->The configuration and compilation of SAMBA is pretty straightforward.
-The first three steps may not be necessary depending upon
-whether or not you have previously built the Samba binaries.</P
+>This would prevent all Postscript files from being filtered (rather, they will go
+thru the virtual "nullfilter" denoted with "-"). This could only be useful for
+PS printers. If you want to print PS code on non-PS printers an entry as follows
+could be useful:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>   */*           application/vnd.cups-raw  0  -</PRE
+><P
+>and would effectively send *all* files to the backend without further processing.</P
 ><P
+>Lastly, you could have the following entry:</P
 ><PRE
 CLASS="PROGRAMLISTING"
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->autoconf</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->make clean</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->rm config.cache</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->./configure</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->make</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->make install</B
-></PRE
-></P
+>   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter</PRE
 ><P
->This will, by default, install SAMBA in <TT
-CLASS="FILENAME"
->/usr/local/samba</TT
->.
-See the main SAMBA documentation if you want to install SAMBA somewhere else.
-It will also build the winbindd executable and libraries. </P
+>You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that
+parses the PostScript and removes the unwanted PJL. This would need to conform to
+CUPS filter design (mainly, receive and pass the parameters printername, job-id,
+username, jobtitle, copies, print options and possibly the filename). It would
+be installed as world executable into "/usr/lib/cups/filters/" and will be called
+by CUPS if it encounters a MIME type "application/vnd.cups-postscript".</P
+><P
+>CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue
+"on hold". It will only be printed upon manual release by the printer operator.
+This is a requirement in many "central reproduction departments", where a few
+operators manage the jobs of hundreds of users on some big machine, where no
+user is allowed to have direct access. (The operators often need to load the
+proper paper type before running the 10.000 page job requested by marketing
+for the mailing, etc.).</P
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2639"
->14.5.3.2. Configure <TT
-CLASS="FILENAME"
->nsswitch.conf</TT
-> and the 
-winbind libraries</A
-></H4
+NAME="AEN2119"
+>14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
+PostScript driver with CUPS-PPDs downloaded to clients</A
+></H2
 ><P
->The libraries needed to run the <B
-CLASS="COMMAND"
->winbindd</B
-> daemon 
-through nsswitch need to be copied to their proper locations, so</P
+>CUPS is perfectly able to use PPD files (PostScript
+Printer Descriptions). PPDs can control all print device options. They
+are usually provided by the manufacturer -- if you own a PostSript printer,
+that is. PPD files are always a component of PostScript printer drivers on MS
+Windows or Apple Mac OS systems. They are ASCII files containing
+user-selectable print options, mapped to appropriate PostScript, PCL or PJL
+commands for the target printer. Printer driver GUI dialogs translate these
+options "on-the-fly" into buttons and drop-down lists for the user to
+select.</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
+>CUPS can load, without any conversions, the PPD file from
+any Windows (NT is recommended) PostScript driver and handle the options.
+There is a web browser interface to the print options (select
+http://localhost:631/printers/ and click on one "Configure Printer" button
+to see it), a commandline interface (see <B
 CLASS="COMMAND"
->cp ../samba/source/nsswitch/libnss_winbind.so /lib</B
-></P
+>man lpoptions</B
+> or
+try if you have <B
+CLASS="COMMAND"
+>lphelp</B
+> on your system) plus some different GUI frontends on Linux
+UNIX, which can present PPD options to the users. PPD options are normally
+meant to become evaluated by the PostScript RIP on the real PostScript
+printer.</P
+><P
+>CUPS doesn't stop at "real" PostScript printers in its
+usage of PPDs. The CUPS developers have extended the PPD concept, to also
+describe available device and driver options for non-PostScript printers
+through  CUPS-PPDs.</P
+><P
+>This is logical, as CUPS includes a fully featured
+PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
+process all received PostScript (and additionally many other file formats)
+from clients. All CUPS-PPDs geared to non-PostScript printers contain an
+additional line, starting with the keyword <VAR
+CLASS="PARAMETER"
+>*cupsFilter</VAR
+>.
+This line
+tells the CUPS print system which printer-specific filter to use for the
+interpretation of the accompanying PostScript. Thus CUPS lets all its
+printers appear as PostScript devices to its clients, because it can act as a
+PostScript RIP for those printers, processing the received PostScript code
+into a proper raster print format.</P
+><P
+>CUPS-PPDs can also be used on Windows-Clients, on top of a
+PostScript driver (recommended is the Adobe one).</P
 ><P
->I also found it necessary to make the following symbolic link:</P
+>This feature enables CUPS to do a few tricks no other
+spooler can do:</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B
 ></P
+><UL
+><LI
 ><P
->And, in the case of Sun solaris:</P
-><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B
->
-<SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B
-></P
+>act as a networked PostScript RIP (Raster Image Processor), handling
+    printfiles from all client platforms in a uniform way;</P
+></LI
+><LI
 ><P
->Now, as root you need to edit <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> to 
-allow user and group entries to be visible from the <B
+>act as a central accounting and billing server, as all files are passed
+    through the <B
 CLASS="COMMAND"
->winbindd</B
-> 
-daemon.  My <TT
+>pstops</B
+> Filter and are therefor logged in
+    the CUPS <TT
 CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> file look like 
-this after editing:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	passwd:     files winbind
-	shadow:     files 
-	group:      files winbind</PRE
-></P
+>page&lowbar;log</TT
+>. - <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE: </I
+></SPAN
+>this
+    can not happen with "raw" print jobs, which always remain unfiltered
+    per definition;</P
+></LI
+><LI
 ><P
->	
-The libraries needed by the winbind daemon will be automatically 
-entered into the <B
-CLASS="COMMAND"
->ldconfig</B
-> cache the next time 
-your system reboots, but it 
-is faster (and you don't need to reboot) if you do it manually:</P
+>enable clients to consolidate on a single PostScript driver, even for
+    many different target printers.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2140"
+>14.5. Windows Terminal Servers (WTS) as CUPS clients</A
+></H2
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->/sbin/ldconfig -v | grep winbind</B
-></P
+>This setup may be of special interest to people
+experiencing major problems in WTS environments. WTS need often a multitude
+of non-PostScript drivers installed to run their clients' variety of
+different printer models. This often imposes the price of much increased
+instability. In many cases, in an attempt to overcome this problem, site
+administrators have resorted to restrict the allowed drivers installed on
+their WTS to one generic PCL- and one PostScript driver. This however
+restricts the clients in the amount of printer options available for them --
+often they can't get out more then simplex prints from one standard paper
+tray, while their devices could do much better, if driven by a different
+driver!</P
 ><P
->This makes <TT
-CLASS="FILENAME"
->libnss_winbind</TT
-> available to winbindd 
-and echos back a check to you.</P
+>Using an Adobe PostScript driver, enabled with a CUPS-PPD,
+seems to be a very elegant way to overcome all these shortcomings. The
+PostScript driver is not known to cause major stability problems on WTS (even
+if used with many different PPDs). The clients will be able to (again) chose
+paper trays, duplex printing and other settings. However, there is a certain
+price for this too: a  CUPS server acting as a PostScript RIP for its clients
+requires more CPU and RAM than just to act as  a "raw spooling" device. Plus,
+this setup is not yet widely tested, although the first feedbacks look very
+promising...</P
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2672"
->14.5.3.3. Configure smb.conf</A
-></H4
+NAME="AEN2144"
+>14.6. Setting up CUPS for driver download</A
+></H2
 ><P
->Several parameters are needed in the smb.conf file to control 
-the behavior of <B
+>The <B
 CLASS="COMMAND"
->winbindd</B
->. Configure 
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> These are described in more detail in 
-the <A
-HREF="winbindd.8.html"
-TARGET="_top"
->winbindd(8)</A
-> man page.  My 
-<TT
+>cupsadsmb</B
+> utility (shipped with all current
+CUPS versions) makes the sharing of any (or all) installed CUPS printers very
+easy. Prior to using it, you need the following settings in <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> file was modified to
-include the following entries in the [global] section:</P
+>:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
 >[global]
-     &#60;...&#62;
-     # separate domain and username with '+', like DOMAIN+username
-     <A
-HREF="winbindd.8.html#WINBINDSEPARATOR"
-TARGET="_top"
->winbind separator</A
-> = +
-     # use uids from 10000 to 20000 for domain users
-     <A
-HREF="winbindd.8.html#WINBINDUID"
-TARGET="_top"
->winbind uid</A
-> = 10000-20000
-     # use gids from 10000 to 20000 for domain groups
-     <A
-HREF="winbindd.8.html#WINBINDGID"
-TARGET="_top"
->winbind gid</A
-> = 10000-20000
-     # allow enumeration of winbind users and groups
-     <A
-HREF="winbindd.8.html#WINBINDENUMUSERS"
-TARGET="_top"
->winbind enum users</A
-> = yes
-     <A
-HREF="winbindd.8.html#WINBINDENUMGROUP"
-TARGET="_top"
->winbind enum groups</A
-> = yes
-     # give winbind users a real shell (only needed if they have telnet access)
-     <A
-HREF="winbindd.8.html#TEMPLATEHOMEDIR"
-TARGET="_top"
->template homedir</A
-> = /home/winnt/%D/%U
-     <A
-HREF="winbindd.8.html#TEMPLATESHELL"
-TARGET="_top"
->template shell</A
-> = /bin/bash</PRE
+		 load printers = yes
+		 printing = cups
+		 printcap name = cups
+
+	[printers]
+		 comment = All Printers
+		 path = /var/spool/samba
+		 browseable = no
+		 public = yes
+		 guest ok = yes
+		 writable = no
+		 printable = yes
+		 printer admin = root
+
+	[print$]
+		 comment = Printer Drivers
+		 path = /etc/samba/drivers
+		 browseable = yes
+		 guest ok = no
+		 read only = yes
+		 write list = root
+	</PRE
 ></P
-></DIV
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2688"
->14.5.3.4. Join the SAMBA server to the PDC domain</A
-></H4
 ><P
->Enter the following command to make the SAMBA server join the 
-PDC domain, where <VAR
-CLASS="REPLACEABLE"
->DOMAIN</VAR
-> is the name of 
-your Windows domain and <VAR
-CLASS="REPLACEABLE"
->Administrator</VAR
-> is 
-a domain user who has administrative privileges in the domain.</P
+>For licensing reasons the necessary files of the Adobe
+Postscript driver can not be distributed with either Samba or CUPS. You need
+to download them yourself from the Adobe website. Once extracted, create a
+<TT
+CLASS="FILENAME"
+>drivers</TT
+> directory in the CUPS data directory (usually
+<TT
+CLASS="FILENAME"
+>/usr/share/cups/</TT
+>). Copy the Adobe files using
+UPPERCASE filenames, to this directory as follows:</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/net join -S PDC -U Administrator</B
+><PRE
+CLASS="PROGRAMLISTING"
+>		ADFONTS.MFM
+		ADOBEPS4.DRV
+		ADOBEPS4.HLP
+		ADOBEPS5.DLL
+		ADOBEPSU.DLL
+		ADOBEPSU.HLP
+		DEFPRTR2.PPD
+		ICONLIB.DLL
+	</PRE
 ></P
 ><P
->The proper response to the command should be: "Joined the domain 
-<VAR
-CLASS="REPLACEABLE"
->DOMAIN</VAR
->" where <VAR
-CLASS="REPLACEABLE"
->DOMAIN</VAR
-> 
-is your DOMAIN name.</P
+>Users of the ESP Print Pro software are able to install
+their "Samba Drivers" package for this purpose with no problem.</P
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2699"
->14.5.3.5. Start up the winbindd daemon and test it!</A
-></H4
+NAME="AEN2157"
+>14.7. Sources of CUPS drivers / PPDs</A
+></H2
 ><P
->Eventually, you will want to modify your smb startup script to 
-automatically invoke the winbindd daemon when the other parts of 
-SAMBA start, but it is possible to test out just the winbind
-portion first.  To start up winbind services, enter the following 
-command as root:</P
+>On the internet you can find now many thousand CUPS-PPD
+files (with their companion filters), in many national languages,
+supporting more than 1.000 non-PostScript models.</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/winbindd</B
 ></P
+><UL
+><LI
 ><P
->Winbindd can now also run in 'dual daemon mode'. This will make it 
-run as 2 processes. The first will answer all requests from the cache,
-thus making responses to clients faster. The other will
-update the cache for the query that the first has just responded.
-Advantage of this is that responses stay accurate and are faster. 
-You can enable dual daemon mode by adding '-B' to the commandline:</P
+><A
+HREF="http://wwwl.easysw.com/printpro/"
+TARGET="_top"
+>ESP PrintPro
+    (http://wwwl.easysw.com/printpro/)</A
+>
+    (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for
+    successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris,
+    SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it
+    is written by the CUPS developers themselves and its sales help finance
+    the further development of CUPS, as they feed their creators)</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/winbindd -B</B
-></P
+>the <A
+HREF="http://gimp-print.sourceforge.net/"
+TARGET="_top"
+>Gimp-Print-Project
+    (http://gimp-print.sourceforge.net/)</A
+>
+    (GPL, Free Software) provides around 120 PPDs (supporting nearly 300
+    printers, many driven to photo quality output), to be used alongside the
+    Gimp-Print CUPS filters;</P
+></LI
+><LI
 ><P
->I'm always paranoid and like to make sure the daemon 
-is really running...</P
+><A
+HREF="http://www.turboprint.com/"
+TARGET="_top"
+>TurboPrint
+    (http://www.turboprint.com/)</A
+>
+    (Shareware, non-Freee) supports roughly the same amount of printers in
+    excellent quality;</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->ps -ae | grep winbindd</B
-></P
+><A
+HREF="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/"
+TARGET="_top"
+>OMNI
+    (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</A
+>
+    (LPGL, Free) is a package made by IBM, now containing support for more
+    than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow
+    ported over to Linux (CUPS support is in a Beta-stage at present);</P
+></LI
+><LI
 ><P
->This command should produce output like this, if the daemon is running</P
+><A
+HREF="http://hpinkjet.sourceforge.net/"
+TARGET="_top"
+>HPIJS
+    (http://hpinkjet.sourceforge.net/)</A
+>
+    (BSD-style licnes, Free) supports around 120 of HP's own printers and is
+    also providing excellent print quality now;</P
+></LI
+><LI
 ><P
->3025 ?        00:00:00 winbindd</P
+><A
+HREF="http://www.linuxprinting.org/"
+TARGET="_top"
+>Foomatic/cupsomatic (http://www.linuxprinting.org/)</A
+>
+    (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every
+    Ghostscript filter known to the world, now usable with CUPS.</P
+></LI
+></UL
 ><P
->Now... for the real test, try to get some information about the 
-users on your PDC</P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE: </I
+></SPAN
+>the cupsomatic trick from Linuxprinting.org is
+working different from the other drivers. While the other drivers take the
+generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
+their input, cupsomatic "kidnaps" the PostScript inside CUPS, before
+RIP-ping, deviates it to an external Ghostscript installation (which now
+becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
+finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
+PostScript RIP function again inside a system-wide Ghostscript
+installation rather than in "their own" pstoraster filter. (This
+CUPS-enabling Ghostscript version may be installed either as a
+patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
+However, this will not change the cupsomatic approach of guiding the printjob
+along a different path through the filtering system than the standard CUPS
+way...</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
+>Once you installed a printer inside CUPS with one of the
+recommended methods (the lpadmin command, the web browser interface or one of
+the available GUI wizards), you can use <B
 CLASS="COMMAND"
->/usr/local/samba/bin/wbinfo -u</B
-></P
-><P
->	
-This should echo back a list of users on your Windows users on 
-your PDC.  For example, I get the following response:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->CEO+Administrator
-CEO+burdell
-CEO+Guest
-CEO+jt-ad
-CEO+krbtgt
-CEO+TsInternetUser</PRE
-></P
-><P
->Obviously, I have named my domain 'CEO' and my <VAR
-CLASS="PARAMETER"
->winbind
-separator</VAR
-> is '+'.</P
+>cupsaddsmb</B
+> to share the
+printer via Samba. <B
+CLASS="COMMAND"
+>cupsaddsmb</B
+> prepares the driver files for
+comfortable client download and installation upon their first contact with
+this printer share.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2184"
+>14.7.1. <B
+CLASS="COMMAND"
+>cupsaddsmb</B
+></A
+></H3
 ><P
->You can do the same sort of thing to get group information from 
-the PDC:</P
+>The <B
+CLASS="COMMAND"
+>cupsaddsmb</B
+> command copies the needed files
+for convenient Windows client installations from the previously prepared CUPS
+data directory to your [print$] share. Additionally, the PPD
+associated with this printer is copied from <TT
+CLASS="FILENAME"
+>/etc/cups/ppd/</TT
+> to
+[print$].</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
 ><SAMP
 CLASS="PROMPT"
->root#</SAMP
+>root# </SAMP
 > <B
 CLASS="COMMAND"
->/usr/local/samba/bin/wbinfo -g</B
+>cupsaddsmb -U root infotec_IS2027</B
 >
-CEO+Domain Admins
-CEO+Domain Users
-CEO+Domain Guests
-CEO+Domain Computers
-CEO+Domain Controllers
-CEO+Cert Publishers
-CEO+Schema Admins
-CEO+Enterprise Admins
-CEO+Group Policy Creator Owners</PRE
+Password for root required to access localhost via SAMBA: <KBD
+CLASS="USERINPUT"
+>[type in password 'secret']</KBD
+></PRE
 ></P
 ><P
->The function 'getent' can now be used to get unified 
-lists of both local and PDC users and groups.
-Try the following command:</P
+>To share all printers and drivers, use the <VAR
+CLASS="PARAMETER"
+>-a</VAR
+>
+parameter instead of a printer name.</P
 ><P
-><SAMP
+>Probably you want to see what's going on. Use the
+<VAR
+CLASS="PARAMETER"
+>-v</VAR
+> parameter to get a more verbose output:</P
+><P
+>Probably you want to see what's going on. Use the
+<VAR
+CLASS="PARAMETER"
+>-v</VAR
+> parameter to get a more verbose output:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>Note: The following line shave been wrapped so that information is not lost.
+ 
+<SAMP
+CLASS="PROMPT"
+>root# </SAMP
+> cupsaddsmb -v -U root infotec_IS2027
+    Password for root required to access localhost via SAMBA:
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
+       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
+       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
+       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
+      (average 17395.2 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
+      (average 11343.0 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
+      (average 9260.4 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
+      (average 9247.1 kb/s)
+
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
+      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
+      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
+      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
+      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
+      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
+      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
+      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
+      (average 26092.8 kb/s)
+    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
+      (average 11812.9 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
+      (average 14679.3 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
+      (average 14281.5 kb/s)
+    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
+      (average 12944.0 kb/s)
+    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
+      (average 13169.7 kb/s)
+    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
+      (average 13266.7 kb/s)
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
+       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
+    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
+       ADOBEPSU.HLP:NULL:RAW:NULL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
+       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
+       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
+       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret'
+       -c 'setdriver infotec_IS2027 infotec_IS2027'
+    cmd = setdriver infotec_IS2027 infotec_IS2027
+    Succesfully set infotec_IS2027 to driver infotec_IS2027.
+
+    <SAMP
 CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->getent passwd</B
+>root# </SAMP
+></PRE
 ></P
 ><P
->You should get a list that looks like your <TT
+>If you look closely, you'll discover your root password was transfered unencrypted over
+the wire, so beware! Also, if you look further her, you'll discover error messages like
+<CODE
+CLASS="CONSTANT"
+>NT_STATUS_OBJECT_NAME_COLLISION</CODE
+> in between. They occur, because
+the directories <TT
 CLASS="FILENAME"
->/etc/passwd</TT
-> 
-list followed by the domain users with their new uids, gids, home 
-directories and default shells.</P
+>WIN40</TT
+> and <TT
+CLASS="FILENAME"
+>W32X86</TT
+> already
+existed in the [print$] driver download share (from a previous driver
+installation). They are harmless here.</P
 ><P
->The same thing can be done for groups with the command</P
+>Now your printer is prepared for the clients to use. From
+a client, browse to the CUPS/Samba server, open the "Printers"
+share, right-click on this printer and select "Install..." or
+"Connect..." (depending on the Windows version you use). Now their
+should be a new printer in your client's local "Printers" folder,
+named (in my case) "infotec_IS2027 on kdebitshop"</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE: </I
+></SPAN
+>
+<B
 CLASS="COMMAND"
->getent group</B
-></P
+>cupsaddsmb</B
+> will only reliably work i
+with CUPS version 1.1.15 or higher
+and Samba from 2.2.4. If it doesn't work, or if the automatic printer
+driver download to the clients doesn't succeed, you can still manually
+install the CUPS printer PPD on top of the Adobe PostScript driver on
+clients and then point the client's printer queue to the Samba printer
+share for connection, should you desire to use the CUPS networked
+PostScript RIP functions.</P
+></DIV
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2739"
->14.5.3.6. Fix the init.d startup scripts</A
-></H4
-><DIV
-CLASS="SECT4"
-><H5
-CLASS="SECT4"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2741"
->14.5.3.6.1. Linux</A
-></H5
-><P
->The <B
-CLASS="COMMAND"
->winbindd</B
-> daemon needs to start up after the 
-<B
-CLASS="COMMAND"
->smbd</B
-> and <B
-CLASS="COMMAND"
->nmbd</B
-> daemons are running.  
-To accomplish this task, you need to modify the startup scripts of your system. They are located at <TT
-CLASS="FILENAME"
->/etc/init.d/smb</TT
-> in RedHat and 
-<TT
-CLASS="FILENAME"
->/etc/init.d/samba</TT
-> in Debian.
-script to add commands to invoke this daemon in the proper sequence.  My 
-startup script starts up <B
-CLASS="COMMAND"
->smbd</B
->, 
-<B
-CLASS="COMMAND"
->nmbd</B
->, and <B
-CLASS="COMMAND"
->winbindd</B
-> from the 
-<TT
-CLASS="FILENAME"
->/usr/local/samba/bin</TT
-> directory directly.  The 'start' 
-function in the script looks like this:</P
+NAME="AEN2213"
+>14.8. The CUPS Filter Chains</A
+></H2
 ><P
+>The following diagrams reveal how CUPS handles print jobs.</P
 ><PRE
 CLASS="PROGRAMLISTING"
->start() {
-        KIND="SMB"
-        echo -n $"Starting $KIND services: "
-        daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
-        RETVAL=$?
-        echo
-        KIND="NMB"
-        echo -n $"Starting $KIND services: "
-        daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
-        RETVAL2=$?
-        echo
-        KIND="Winbind"
-        echo -n $"Starting $KIND services: "
-        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=1
-        return $RETVAL
-}</PRE
-></P
-><P
->If you would like to run winbindd in dual daemon mode, replace 
-the line 
-<PRE
+>#########################################################################
+#
+# CUPS in and of itself has this (general) filter chain (CAPITAL
+# letters are FILE-FORMATS or MIME types, other are filters (this is
+# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
+#
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#     <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
+#      |           # installation on the system
+#      |  (= "postscipt interpreter")
+#      |
+#      V
+# APPLICATION/VND.CUPS-RASTER
+#      |
+#      |
+#      V
+#     rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# ESP PrintPro has some enhanced "rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>" filters as compared to
+# CUPS, and also a somewhat improved "pstoraster" filter.
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+#########################################################################</PRE
+><PRE
 CLASS="PROGRAMLISTING"
->        daemon /usr/local/samba/bin/winbindd</PRE
->
-
-in the example above with:
-
-<PRE
+>#########################################################################
+#
+# This is how "cupsomatic" comes into play:
+# =========================================
+#
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#    <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#    pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+#      |                                          |
+#      |                                          V
+#      V                                         cupsomatic
+#    pstoraster                                  (constructs complicated
+#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |                                         to let the file be
+#      V                                         processed by a
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=<VAR
+CLASS="REPLACEABLE"
+>s.th.</VAR
+>"
+#      |                                         call...)
+#      |                                          |
+#      V                                          |
+#    rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>                          V
+#      |    (= "raster driver")     +-------------------------+
+#      |                            | Ghostscript at work.... |
+#      V                            |                         |
+# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+#      |                                          |
+#      |                                          |
+#      V                                          |
+#    backend &#62;------------------------------------+
+#      |
+#      |
+#      V
+#    THE PRINTER
+#
+#
+# Note, that cupsomatic "kidnaps" the printfile after the
+# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
+# the CUPS-external, systemwide Ghostscript installation, bypassing the
+# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
+# "rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>", and hands the rasterized file directly to the CUPS
+# backend...
+#
+# cupsomatic is not made by the CUPS developers. It is an independent
+# contribution to printing development, made by people from
+# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+#########################################################################</PRE
+><PRE
 CLASS="PROGRAMLISTING"
->        daemon /usr/local/samba/bin/winbindd -B</PRE
->.</P
-><P
->The 'stop' function has a corresponding entry to shut down the 
-services and looks like this:</P
-><P
+>#########################################################################
+#
+# And this is how it works for ESP PrintPro from 4.3:
+# ===================================================
+#
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#     <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT
+#      |
+#      |
+#      V
+#     gsrip
+#      |  (= "postscipt interpreter")
+#      |
+#      V
+# APPLICATION/VND.CUPS-RASTER
+#      |
+#      |
+#      V
+#     rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+#########################################################################</PRE
 ><PRE
 CLASS="PROGRAMLISTING"
->stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
-        killproc smbd
-        RETVAL=$?
-        echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
-        killproc nmbd
-        RETVAL2=$?
-        echo
-        KIND="Winbind"
-        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
-        echo ""
-        return $RETVAL
-}</PRE
-></P
-></DIV
-><DIV
-CLASS="SECT4"
-><HR><H5
-CLASS="SECT4"
-><A
-NAME="AEN2761"
->14.5.3.6.2. Solaris</A
-></H5
-><P
->On solaris, you need to modify the 
-<TT
-CLASS="FILENAME"
->/etc/init.d/samba.server</TT
-> startup script. It usually 
-only starts smbd and nmbd but should now start winbindd too. If you 
-have samba installed in <TT
-CLASS="FILENAME"
->/usr/local/samba/bin</TT
->, 
-the file could contains something like this:</P
-><P
+>#########################################################################
+#
+# This is how "cupsomatic" would come into play with ESP PrintPro:
+# ================================================================
+#
+#
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#    <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#    pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+#      |                                          |
+#      |                                          V
+#      V                                         cupsomatic
+#    gsrip                                       (constructs complicated
+#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |                                         to let the file be
+#      V                                         processed by a
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=<VAR
+CLASS="REPLACEABLE"
+>s.th.</VAR
+>"
+#      |                                         call...)
+#      |                                          |
+#      V                                          |
+#    rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>                          V
+#      |   (= "raster driver")      +-------------------------+
+#      |                            | Ghostscript at work.... |
+#      V                            |                         |
+# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+#      |                                          |
+#      |                                          |
+#      V                                          |
+#    backend &#62;------------------------------------+
+#      |
+#      |
+#      V
+#    THE PRINTER
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+#########################################################################</PRE
 ><PRE
 CLASS="PROGRAMLISTING"
->##
-## samba.server
-##
-
-if [ ! -d /usr/bin ]
-then                    # /usr not mounted
-        exit
-fi
-
-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
-}
- 
-# Start/stop processes required for samba server
-
-case "$1" in
-
-'start')
+>#########################################################################
 #
-# Edit these lines to suit your installation (paths, workgroup, host)
+# And this is how it works for CUPS from 1.1.15:
+# ==============================================
 #
-echo Starting SMBD
-   /usr/local/samba/bin/smbd -D -s \
-	/usr/local/samba/smb.conf
-
-echo Starting NMBD
-   /usr/local/samba/bin/nmbd -D -l \
-	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
-
-echo Starting Winbind Daemon
-   /usr/local/samba/bin/winbindd
-   ;;
-
-'stop')
-   killproc nmbd
-   killproc smbd
-   killproc winbindd
-   ;;
-
-*)
-   echo "Usage: /etc/init.d/samba.server { start | stop }"
-   ;;
-esac</PRE
-></P
-><P
->Again, if you would like to run samba in dual daemon mode, replace 
-<PRE
-CLASS="PROGRAMLISTING"
->   /usr/local/samba/bin/winbindd</PRE
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#     <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT-----+
+#                                     |
+#                  +------------------v------------------------------+
+#                  | Ghostscript                                     |
+#                  | at work...                                      |
+#                  | (with                                           |
+#                  | "-sDEVICE=cups")                                |
+#                  |                                                 |
+#                  |         (= "postscipt interpreter")             |
+#                  |                                                 |
+#                  +------------------v------------------------------+
+#                                     |
+#                                     |
+# APPLICATION/VND.CUPS-RASTER &#62;-------+
+#      |
+#      |
+#      V
+#     rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
 >
-
-in the script above with:
-
-<PRE
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
+#       Ghostscript. GNU Ghostscript needs to be patched to handle the
+#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
+#       "gs -h" needs to show up a "cups" device. pstoraster is now a
+#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
+#       the job. It will output "application/vnd.cup-raster", which will
+#       be finally processed by a CUPS raster driver "rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>"
+#       Note the difference to "cupsomatic", which will *not* output
+#       CUPS-raster, but a final version of the printfile, ready to be
+#       sent to the printer. cupsomatic also doesn't use the "cups"
+#       devicemode in Ghostscript, but one of the classical devicemodes....
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+#########################################################################</PRE
+><PRE
 CLASS="PROGRAMLISTING"
->   /usr/local/samba/bin/winbindd -B</PRE
-></P
+>#########################################################################
+#
+# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
+# ========================================================================
+#
+# <VAR
+CLASS="REPLACEABLE"
+>SOMETHNG</VAR
+>-FILEFORMAT
+#      |
+#      |
+#      V
+#     <VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>tops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT-----+
+#                                     |
+#                  +------------------v------------------------------+
+#                  | Ghostscript        . Ghostscript at work....    |
+#                  | at work...         . (with "-sDEVICE=           |
+#                  | (with              .            <VAR
+CLASS="REPLACEABLE"
+>s.th.</VAR
+>"        |
+#                  | "-sDEVICE=cups")   .                            |
+#                  |                    .                            |
+#                  | (CUPS standard)    .      (cupsomatic)          |
+#                  |                    .                            |
+#                  |          (= "postscript interpreter")           |
+#                  |                    .                            |
+#                  +------------------v--------------v---------------+
+#                                     |              |
+#                                     |              |
+# APPLICATION/VND.CUPS-RASTER &#62;-------+              |
+#      |                                             |
+#      |                                             |
+#      V                                             |
+#     rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>                            |
+#      |   (= "raster driver")                       |
+#      |                                             |
+#      V                                             |
+# SOMETHING-DEVICE-SPECIFIC &#62;------------------------+
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rasterto<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+> is noted.
+#
+##########################################################################</PRE
 ></DIV
 ><DIV
-CLASS="SECT4"
-><HR><H5
-CLASS="SECT4"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN2771"
->14.5.3.6.3. Restarting</A
-></H5
+NAME="AEN2252"
+>14.9. CUPS Print Drivers and Devices</A
+></H2
 ><P
->If you restart the <B
-CLASS="COMMAND"
->smbd</B
->, <B
-CLASS="COMMAND"
->nmbd</B
->, 
-and <B
-CLASS="COMMAND"
->winbindd</B
-> daemons at this point, you
-should be able to connect to the samba server as a domain member just as
-if you were a local user.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2777"
->14.5.3.7. Configure Winbind and PAM</A
-></H4
+>CUPS ships with good support for HP LaserJet type printers. You can install
+the driver as follows:
+
+<P
+></P
+><UL
+><LI
 ><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 
-services, keep reading.  The pam configuration files need to be altered in
-this step.  (Did you remember to make backups of your original 
+>	lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
+	</P
+></LI
+></UL
+>
+
+(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
+for not-yet-installed-PPDs, which CUPS typically stores in 
 <TT
 CLASS="FILENAME"
->/etc/pam.d</TT
-> files? If not, do it now.)</P
+>/usr/share/cups/model</TT
+>. Alternatively, you may use
+"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2259"
+>14.9.1. Further printing steps</A
+></H3
 ><P
->You will need a pam module to use winbindd with these other services.  This 
-module will be compiled in the <TT
-CLASS="FILENAME"
->../source/nsswitch</TT
-> directory
-by invoking the command</P
+>Always also consult the database on linuxprinting.org for all recommendations
+about which driver is best used for each printer:</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->make nsswitch/pam_winbind.so</B
+><A
+HREF="http://www.linuxprinting.org/printer_list.cgi"
+TARGET="_top"
+>http://www.linuxprinting.org/printer_list.cgi</A
 ></P
 ><P
->from the <TT
-CLASS="FILENAME"
->../source</TT
-> directory.  The
-<TT
-CLASS="FILENAME"
->pam_winbind.so</TT
-> file should be copied to the location of
-your other pam security modules.  On my RedHat system, this was the
-<TT
-CLASS="FILENAME"
->/lib/security</TT
-> directory. On Solaris, the pam security 
-modules reside in <TT
-CLASS="FILENAME"
->/usr/lib/security</TT
->.</P
+>There select your model and click on "Show". You'll arrive at a page listing
+all drivers working with your model. There will always be *one* 
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>recommended</I
+></SPAN
+> one. Try this one first. In your case
+("HP LaserJet 4 Plus"), you'll arrive here:</P
 ><P
-><SAMP
-CLASS="PROMPT"
->root#</SAMP
-> <B
-CLASS="COMMAND"
->cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B
+><A
+HREF="http://www.linuxprinting.org/show_printer.cgi?recnum=75104"
+TARGET="_top"
+>http://www.linuxprinting.org/show_printer.cgi?recnum=75104</A
 ></P
-><DIV
-CLASS="SECT4"
-><HR><H5
-CLASS="SECT4"
+><P
+>The recommended driver is "ljet4". It has a link to the page for the ljet4
+driver too:</P
+><P
 ><A
-NAME="AEN2794"
->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
-></H5
+HREF="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4"
+TARGET="_top"
+>http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</A
+></P
 ><P
->The <TT
-CLASS="FILENAME"
->/etc/pam.d/samba</TT
-> file does not need to be changed. I 
-just left this fileas it was:</P
+>On the driver's page, you'll find important and detailed info about how to use
+that driver within the various available spoolers. You can generate a PPD for
+CUPS. The PPD contains all the info about how to use your model and the driver;
+this is, once installed, working transparently for the user -- you'll only
+need to choose resolution, paper size etc. from the web-based menu or from
+the print dialog GUI or from the commandline...</P
+><P
+>On the driver's page, choose to use the "PPD-O-Matic" online PPD generator
+program. Select your model and click "Generate PPD file". When you safe the
+appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt
+line endings and tabs), but use "Save as..." in your browser's menu. Save it
+at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</P
+><P
+>Then install the printer:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->auth    required        /lib/security/pam_stack.so service=system-auth
-account required        /lib/security/pam_stack.so service=system-auth</PRE
+>    "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
+          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</PRE
 ></P
 ><P
->The other services that I modified to allow the use of winbind 
-as an authentication service were the normal login on the console (or a terminal 
-session), telnet logins, and ftp service.  In order to enable these 
-services, you may first need to change the entries in 
-<TT
-CLASS="FILENAME"
->/etc/xinetd.d</TT
-> (or <TT
-CLASS="FILENAME"
->/etc/inetd.conf</TT
->).  
-RedHat 7.1 uses the new xinetd.d structure, in this case you need 
-to change the lines in <TT
-CLASS="FILENAME"
->/etc/xinetd.d/telnet</TT
-> 
-and <TT
+>Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need
+a special "CUPS filter" named "cupsomatic". Get the latest version of
+"cupsomatic" from:</P
+><P
+><A
+HREF="http://www.linuxprinting.org/cupsomatic"
+TARGET="_top"
+>http://www.linuxprinting.org/cupsomatic</A
+></P
+><P
+>This needs to be copied to <TT
 CLASS="FILENAME"
->/etc/xinetd.d/wu-ftp</TT
-> from </P
+>/usr/lib/cups/filter/cupsomatic</TT
+>
+and be made world executable. This filter is needed to read and act upon the
+specially encoded Foomatic comments, embedded in the printfile, which in turn
+are used to construct (transparently for you, the user) the complicated
+ghostscript command line needed for your printer/driver combo.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->enable = no</PRE
+>You can have a look at all the options for the Ghostscript commandline supported
+by your printer and the ljet4 driver by going to the section "Execution details",
+selecting your model (Laserjet 4 Plus) and clicking on "Show execution details".
+This will bring up this web page:</P
+><P
+><A
+HREF="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details"
+TARGET="_top"
+>http://www.linuxprinting.org/execution.cgi?driver=ljet4&#38;printer=75104&#38;.submit=Show+execution+details</A
 ></P
 ><P
->to</P
+>The ingenious thing is that the database is kept current. If there
+is a bug fix and an improvement somewhere in the database, you will
+always get the most current and stable and feature-rich driver by following
+the steps described above.</P
+><DIV
+CLASS="NOTE"
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->enable = yes</PRE
 ></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
->	
-For ftp services to work properly, you will also need to either 
-have individual directories for the domain users already present on 
-the server, or change the home directory template to a general
-directory for all domain users.  These can be easily set using 
-the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> global entry 
-<B
-CLASS="COMMAND"
->template homedir</B
->.</P
+>Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
+people are aware of. (So if you use it often, please send him a note showing
+your appreciation).</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->The <TT
-CLASS="FILENAME"
->/etc/pam.d/ftp</TT
-> file can be changed 
-to allow winbind ftp access in a manner similar to the
-samba file.  My <TT
+>The latest and greatest improvement now is support for "custom page sizes"
+for all those printers which support it.</P
+><P
+>"cupsomatic" is documented here:</P
+><P
+><A
+HREF="http://www.linuxprinting.org/cups-doc.html"
+TARGET="_top"
+>http://www.linuxprinting.org/cups-doc.html</A
+></P
+><P
+>More printing tutorial info may be found here:</P
+><P
+><A
+HREF="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/"
+TARGET="_top"
+>http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</A
+></P
+><P
+>Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
+approaching the "all-time high" number of 1.000 for the supported models)
+are using a special filtering chain involving Ghostscript, as described
+in this document.</P
+><P
+>Summary - You need:</P
+><P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>A "foomatic+<VAR
+CLASS="REPLACEABLE"
+>something</VAR
+>" PPD is not enough to print with CUPS (but it is *one* important component)</TD
+></TR
+><TR
+><TD
+>The "cupsomatic" filter script (Perl) in <TT
 CLASS="FILENAME"
->/etc/pam.d/ftp</TT
-> file was 
-changed to look like this:</P
+>/usr/lib/cups/filters/</TT
+></TD
+></TR
+><TR
+><TD
+>Perl to make cupsomatic run</TD
+></TR
+><TR
+><TD
+>Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</TD
+></TR
+><TR
+><TD
+>Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
-auth       sufficient   /lib/security/pam_winbind.so
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_shells.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth</PRE
+></P
 ></P
 ><P
->The <TT
-CLASS="FILENAME"
->/etc/pam.d/login</TT
-> file can be changed nearly the 
-same way.  It now looks like this:</P
+>In the case of the "hpijs" driver, you need a Ghostscript version, which
+has "ijs" amongst its supported devices in "gs -h". In the case of
+"hpijs+foomatic", a valid ghostscript commandline would be reading like this:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->auth       required     /lib/security/pam_securetty.so
-auth       sufficient   /lib/security/pam_winbind.so
-auth       sufficient   /lib/security/pam_unix.so use_first_pass
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_nologin.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-password   required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth
-session    optional     /lib/security/pam_console.so</PRE
+>       gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
+             -sIjsServer=hpijs<VAR
+CLASS="REPLACEABLE"
+>PageSize</VAR
+> -dDuplex=<VAR
+CLASS="REPLACEABLE"
+>Duplex</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>Model</VAR
+>        \
+             -r<VAR
+CLASS="REPLACEABLE"
+>Resolution</VAR
+>,PS:MediaPosition=<VAR
+CLASS="REPLACEABLE"
+>InputSlot</VAR
+> -dIjsUseOutputFD \
+             -sOutputFile=- -</PRE
 ></P
+><DIV
+CLASS="NOTE"
 ><P
->In this case, I added the <B
-CLASS="COMMAND"
->auth sufficient /lib/security/pam_winbind.so</B
-> 
-lines as before, but also added the <B
-CLASS="COMMAND"
->required pam_securetty.so</B
-> 
-above it, to disallow root logins over the network.  I also added a 
-<B
-CLASS="COMMAND"
->sufficient /lib/security/pam_unix.so use_first_pass</B
->
-line after the <B
-CLASS="COMMAND"
->winbind.so</B
-> line to get rid of annoying 
-double prompts for passwords.</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
+>Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic)
+you don't need to remember this. You can choose the available print options
+thru a GUI print command (like "glp" from ESP's commercially supported
+PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent
+"xpp") or the CUPS web interface via human-readable drop-down selection
+menus.</P
+></TD
+></TR
+></TABLE
 ></DIV
-><DIV
-CLASS="SECT4"
-><HR><H5
-CLASS="SECT4"
-><A
-NAME="AEN2827"
->14.5.3.7.2. Solaris-specific configuration</A
-></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
-that I made.You can customize the pam.conf file as per your requirements,but
-be sure of those changes because in the worst case it will leave your system
-nearly impossible to boot.</P
+>If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software
+Products, the makers of CUPS, downloadable from
+<A
+HREF="http://www.cups.org/software.html"
+TARGET="_top"
+>http://www.cups.org/software.html</A
+>,
+co-maintained by the developers of linuxprinting.org), you are guaranteed to
+have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
+Ghostscript. It contains support for ~300 devices, whereas plain vanilla
+GNU Ghostscript 7.05 only has ~200.</P
+><P
+>If you print only one CUPS test page, from the web interface and when you try to
+print a windows test page, it acts like the job was never sent:
+
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Can you print "standard" jobs from the CUPS machine?</TD
+></TR
+><TR
+><TD
+>Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</TD
+></TR
+><TR
+><TD
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Most important:</I
+></SPAN
+> What kind of printer driver are you using on the Windows clients?</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->#
-#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
-#
-# Copyright (c) 1996-1999, Sun Microsystems, Inc.
-# All Rights Reserved.
-#
-# PAM configuration
-#
-# Authentication management
-#
-login   auth required   /usr/lib/security/pam_winbind.so
-login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
-login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
-#
-rlogin  auth sufficient /usr/lib/security/pam_winbind.so
-rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-dtlogin auth sufficient /usr/lib/security/pam_winbind.so
-dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
-other   auth sufficient /usr/lib/security/pam_winbind.so
-other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-# Account management
-#
-login   account sufficient      /usr/lib/security/pam_winbind.so
-login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-dtlogin account sufficient      /usr/lib/security/pam_winbind.so
-dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-other   account sufficient      /usr/lib/security/pam_winbind.so
-other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Session management
-#
-other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Password management
-#
-#other   password sufficient     /usr/lib/security/pam_winbind.so
-other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
-dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
-#
-# Support for Kerberos V5 authentication (uncomment to use Kerberos)
-#
-#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass</PRE
 ></P
+>
+
+You can try to get a more detailed debugging info by setting "LogLevel debug" in
+<TT
+CLASS="FILENAME"
+>/etc/cups/cupsd.conf</TT
+>, re-start cupsd and investigate <TT
+CLASS="FILENAME"
+>/var/log/cups/error_log</TT
+>
+for the whereabouts of your Windows-originating printjobs:</P
 ><P
->I also added a try_first_pass line after the winbind.so line to get rid of
-annoying double prompts for passwords.</P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</TD
+></TR
+><TR
+><TD
+>are there "filter" available for this MIME type?</TD
+></TR
+><TR
+><TD
+>are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</TD
+></TR
+></TBODY
+></TABLE
 ><P
->Now restart your Samba and try connecting through your application that you
-configured in the pam.conf.</P
-></DIV
-></DIV
+></P
 ></DIV
 ></DIV
 ><DIV
@@ -14556,639 +10843,623 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN2834"
->14.6. Limitations</A
+NAME="AEN2329"
+>14.10. Limiting the number of pages users can print</A
 ></H2
 ><P
->Winbind has a number of limitations in its current 
-	released version that we hope to overcome in future 
-	releases:</P
-><P
-></P
-><UL
-><LI
-><P
->Winbind is currently only available for 
-		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
-		Modules systems. This is becoming more common as NSS and 
-		PAM gain	support among UNIX vendors.</P
-></LI
-><LI
+>The feature you want is dependent on the real print subsystem you're using.
+Samba's part is always to receive the job files from the clients (filtered
+*or* unfiltered) and hand it over to this printing subsystem.</P
 ><P
->The mappings of Windows NT RIDs to UNIX ids 
-		is not made algorithmically and depends on the order in which 
-		unmapped users or groups are seen by winbind. It may be difficult 
-		to recover the mappings of rid to UNIX id mapping if the file 
-		containing this information is corrupted or destroyed.</P
-></LI
-><LI
+>Of course one could "hack" things with one's own scripts.</P
 ><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, this is
-		instead up to the PDC to enforce.</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2844"
->14.7. Conclusion</A
-></H2
+>But there is CUPS (Common Unix Printing System). CUPS supports "quotas".
+Quotas can be based on sizes of jobs or on the number of pages or both,
+and are spanning any time period you want.</P
 ><P
->The winbind system, through the use of the Name Service 
-	Switch, Pluggable Authentication Modules, and appropriate 
-	Microsoft RPC calls have allowed us to provide seamless 
-	integration of Microsoft Windows NT domain users on a
-	UNIX system. The result is a great reduction in the administrative 
-	cost of running a mixed UNIX and NT network.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="ADVANCEDNETWORKMANAGEMENT"
-></A
->Chapter 15. Advanced Network Manangement</H1
+>This is an example command how root would set a print quota in CUPS,
+assuming an existing printer named "quotaprinter":</P
+><PRE
+CLASS="PROGRAMLISTING"
+>  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
+       -o job-page-limit=100</PRE
 ><P
->This section attempts to document peripheral issues that are of great importance to network
-administrators who want to improve network resource access control, to automate the user
-environment, and to make their lives a little easier.</P
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2859"
->15.1. Configuring Samba Share Access Controls</A
-></H2
+>This would limit every single user to print 100 pages or 1024 KB of
+data (whichever comes first) within the last 604.800 seconds ( = 1 week).</P
 ><P
->This section deals with how to configure Samba per share access control restrictions.
-By default samba sets no restrictions on the share itself. Restrictions on the share itself
-can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
-connect to a share. In the absence of specific restrictions the default setting is to allow
-the global user <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Everyone</I
-></SPAN
-> Full Control (ie: Full control, Change and Read).</P
+>For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter,
+otherwise it uses a "dummy" count of "1". Some printfiles don't pass it
+(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
+proprietary drivers for the target printer running on the client computers and
+CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not
+filtering them), will be counted as "1-pagers" too!</P
 ><P
->At this time Samba does NOT provide a tool for configuring access control setting on the Share
-itself. Samba does have the capacity to store and act on access control settings, but  the only
-way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
-Computer Management.</P
+>You need to send PostScript from the clients (i.e. run a PostScript driver there)
+for having the chance to get accounting done. If the printer is a non-PostScript model,
+you need to let CUPS do the job to convert the file to a print-ready format for the
+target printer. This will be working for currently ~1.000 different printer models, see</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     http://www.linuxprinting.org/printer_list.cgi</PRE
 ><P
->Samba stores the per share access control settings in a file called <TT
-CLASS="FILENAME"
->share_info.tdb</TT
->.
-The location of this file on your system will depend on how samba was compiled. The default location
-for samba's tdb files is under <TT
-CLASS="FILENAME"
->/usr/local/samba/var</TT
->. If the <TT
-CLASS="FILENAME"
->tdbdump</TT
->
-utility has been compiled and installed on your system then you can examine the contents of this file
-by: <KBD
-CLASS="USERINPUT"
->tdbdump share_info.tdb</KBD
->.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2869"
->15.1.1. Share Permissions Management</A
-></H3
+>Before CUPS-1.1.16 your only option was to use the Adobe PostScript
+Driver on the Windows clients. The output of this driver was not always
+passed thru the "pstops" filter on the CUPS/Samba side, and therefor was
+not counted correctly (the reason is that it often --- depending on the
+"PPD" being used --- did write a "PJL"-header in front of the real
+PostScript which made CUPS to skip the pstops and go directy to
+the "pstoraster" stage).</P
 ><P
->The best tool for the task is platform dependant. Choose the best tool for your environmemt.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2872"
->15.1.1.1. Windows NT4 Workstation/Server</A
-></H4
+>From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver
+for Windows NT/2K/XP clients" (it is tagged in the download area of
+http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package).
+It is *not* working for Win9x/ME clients. But it:</P
 ><P
->The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
-Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
-You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.</P
-><DIV
-CLASS="PROCEDURE"
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>it guarantees to not write an PJL-header</TD
+></TR
+><TR
+><TD
+>it guarantees to still read and support all PJL-options named in the driver PPD with its own means</TD
+></TR
+><TR
+><TD
+>it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</TD
+></TR
+><TR
+><TD
+>it guarantees to page-count correctly the printfile</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><B
->Instructions</B
 ></P
-><OL
-TYPE="1"
-><LI
 ><P
->Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
-select Computer, then click on the Shared Directories entry.</P
-></LI
-><LI
+>You can read more about the setup of this combination in the
+manpage for "cupsaddsmb" (only present with CUPS installed, only
+current with CUPS 1.1.16).</P
 ><P
->	Now click on the share that you wish to manage, then click on the Properties tab, next click on
-	the Permissions tab. Now you can Add or change access control settings as you wish.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2881"
->15.1.1.2. Windows 200x/XP</A
-></H4
+>These are the items CUPS logs in the "page_log" for every single *page* of a job:</P
 ><P
->On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
-tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
-then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Everyone</I
-></SPAN
-> Full Control on the Share.</P
 ><P
->MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
-Microsoft Management Console (MMC). This tool is located by clicking on <TT
-CLASS="FILENAME"
->Control Panel -&#62;
-Administrative Tools -&#62; Computer Management</TT
->.</P
-><DIV
-CLASS="PROCEDURE"
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Printer name</TD
+></TR
+><TR
+><TD
+>User name</TD
+></TR
+><TR
+><TD
+>Job ID</TD
+></TR
+><TR
+><TD
+>Time of printing</TD
+></TR
+><TR
+><TD
+>the page number</TD
+></TR
+><TR
+><TD
+>the number of copies</TD
+></TR
+><TR
+><TD
+>a billing info string (optional)</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><B
->Instructions</B
 ></P
-><OL
-TYPE="1"
-><LI
+></P
 ><P
->	After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
-	select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
-	to enter a domain login user identifier and a password. This will authenticate you to the domain.
-	If you where already logged in with administrative privilidge this step is not offered.</P
-></LI
-><LI
+>Here is an extract of my CUPS server's page_log file to illustrate
+the format and included items:</P
 ><P
->If the Samba server is not shown in the Select Computer box, then type in the name of the target
-Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
-next to 'Shared Folders' in the left panel.</P
-></LI
-><LI
+><SAMP
+CLASS="COMPUTEROUTPUT"
+>	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2  #marketing</SAMP
+></P
 ><P
->Now in the right panel, double-click on the share you wish to set access control permissions on.
-Then click on the tab 'Share Permissions'. It is now possible to add access control entities
-to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
-wish to assign for each entry.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="WARNING"
+>This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job
+printed in 2 copies and billed to "#marketing"...</P
+><P
+>What flaws or shortcomings are there?</P
 ><P
 ></P
 ><TABLE
-CLASS="WARNING"
-WIDTH="100%"
 BORDER="0"
+><TBODY
 ><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
+>the ones named above</TD
+></TR
+><TR
 ><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Be careful. If you take away all permissions from the Everyone user without removing this user
-then effectively no user will be able to access the share. This is a result of what is known as
-ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
-will have no access even if this user is given explicit full control access.</P
-></TD
+>	CUPS really counts the job pages being *processsed in software*
+	(going thru the "RIP") rather than the physical sheets successfully
+	leaving the printing device -- if there is a jam while printing
+	the 5th sheet out of 1000 and the job is aborted by the printer,
+	the "page count" will still show the figure of 1000 for that job
+	</TD
+></TR
+><TR
+><TD
+>	all quotas are the same for all users (no flexibility to give the
+	boss a higher quota than the clerk) no support for groups
+	</TD
+></TR
+><TR
+><TD
+>	no means to read out the current balance or "used-up" number of current quota
+	</TD
+></TR
+><TR
+><TD
+>	a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
+	</TD
+></TR
+><TR
+><TD
+>	a user being denied a job because of a filled-up quota doesn't get a meaningful
+	error message from CUPS other than "client-error-not-possible".
+	</TD
 ></TR
+></TBODY
 ></TABLE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2897"
->15.2. Remote Server Administration</A
-></H2
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get 'User Manager' and 'Server Manager'?</I
-></SPAN
-></P
-><P
->Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
-the 'Server Manager'?</P
-><P
->Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
-systems.  The tools set includes:</P
 ><P
 ></P
-><UL
-><LI
-><P
->Server Manager</P
-></LI
-><LI
-><P
->User Manager for Domains</P
-></LI
-><LI
 ><P
->Event Viewer</P
-></LI
-></UL
+>But this is the best system out there currently. And there are
+huge improvements under development:</P
 ><P
->Click here to download the archived file <A
-HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
-TARGET="_top"
->ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
 ></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>page counting will go into the "backends" (these talk
+	directly to the printer and will increase the count in sync with the
+	 actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</TD
+></TR
+><TR
+><TD
+>quotas will be handled more flexibly</TD
+></TR
+><TR
+><TD
+>probably there will be support for users to inquire their "accounts" in advance</TD
+></TR
+><TR
+><TD
+>probably there will be support for some other tools around this topic</TD
+></TR
+></TBODY
+></TABLE
 ><P
->The Windows NT 4.0 version of the 'User Manager for 
-Domains' and 'Server Manager' are available from Microsoft via ftp 
-from <A
-HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
-TARGET="_top"
->ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
 ></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN2914"
->15.3. Network Logon Script Magic</A
-></H2
-><P
->This section needs work. Volunteer contributions most welcome. Please send your patches or updates
-to <A
-HREF="mailto:jht@samba.org"
-TARGET="_top"
->John Terpstra</A
->.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="POLICYMGMT"
-></A
->Chapter 16. System and Account Policies</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN2929"
->16.1. Creating and Managing System Policies</A
-></H2
-><P
->Under MS Windows platforms, particularly those following the release of MS Windows
-NT4 and MS Windows 95) it is possible to create a type of file that would be placed
-in the NETLOGON share of a domain controller. As the client logs onto the network
-this file is read and the contents initiate changes to the registry of the client
-machine. This file allows changes to be made to those parts of the registry that
-affect users, groups of users, or machines.</P
-><P
->For MS Windows 9x/Me this file must be called <TT
-CLASS="FILENAME"
->Config.POL</TT
-> and may
-be generated using a tool called <TT
-CLASS="FILENAME"
->poledit.exe</TT
->, better known as the
-Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
-dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
-comments from MS Windows network administrators it would appear that this tool became
-a part of the MS Windows Me Resource Kit.</P
-><P
->MS Windows NT4 Server products include the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->System Policy Editor</I
-></SPAN
->
-under the <TT
-CLASS="FILENAME"
->Start -&#62; Programs -&#62; Administrative Tools</TT
-> menu item.
-For MS Windows NT4 and later clients this file must be called <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
->.</P
 ><P
->New with the introduction of MS Windows 2000 was the Microsoft Management Console
-or MMC.  This tool is the new wave in the ever changing landscape of Microsoft
-methods for management of network access and security. Every new Microsoft product
-or technology seems to obsolete the old rules and to introduce newer and more
-complex tools and methods. To Microsoft's credit though, the MMC does appear to
-be a step forward, but improved functionality comes at a great price.</P
+>Other than the current stage of the CUPS development, I don't
+know any other ready-to-use tool which you could consider.</P
 ><P
->Before embarking on the configuration of network and system policies it is highly
-advisable to read the documentation available from Microsoft's web site regarding
+>You can download the driver files from
 <A
-HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp"
+HREF="http://www.cups.org/software.html"
 TARGET="_top"
->Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</A
-> available from Microsoft.
-There are a large number of documents in addition to this old one that should also
-be read and understood. Try searching on the Microsoft web site for "Group Policies".</P
-><P
->What follows is a very discussion with some helpful notes. The information provided
-here is incomplete - you are warned.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2943"
->16.1.1. Windows 9x/Me Policies</A
-></H3
+>http://www.cups.org/software.html</A
+>.
+It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16
+Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to
+download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
+the files:</P
 ><P
->You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
-It can be found on the Original full product Win98 installation CD under
-<TT
-CLASS="FILENAME"
->tools/reskit/netadmin/poledit</TT
->.  Install this using the
-Add/Remove Programs facility and then click on the 'Have Disk' tab.</P
+>	<SAMP
+CLASS="COMPUTEROUTPUT"
+>	   cups-samba.install
+	   cups-samba.license
+	   cups-samba.readme
+	   cups-samba.remove
+	   cups-samba.ss
+	</SAMP
+>
+	</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. Then
-save these settings in a file called <TT
+>These have been packaged with the ESP meta packager software "EPM". The
+*.install and *.remove files are simple shell script, which untars the
+*.ss (which is nothing else than a tar-archive) and puts its contents
+into <TT
 CLASS="FILENAME"
->Config.POL</TT
-> that needs to
-be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto
-the Samba Domain, it will automatically read this file and update the Win9x/Me registry
-of the machine as it logs on.</P
+>/usr/share/cups/drivers/</TT
+>. Its contents are 3 files:</P
 ><P
->Further details are covered in the Win98 Resource Kit documentation.</P
+>	<SAMP
+CLASS="COMPUTEROUTPUT"
+>	   cupsdrvr.dll
+	   cupsui.dll
+	   cups.hlp
+	</SAMP
+>
+	</P
+><DIV
+CLASS="CAUTION"
 ><P
->If you do not take the right steps, then every so often Win9x/Me 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 Win9x/Me machine. Hence, you will
-occasionally notice things changing back to the original settings.</P
+></P
+><TABLE
+CLASS="CAUTION"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
 ><P
->Install the group policy handler for Win9x to pick up group policies. Look on the
-Win98 CD in <TT
+>Due to a bug one CUPS release puts the <TT
 CLASS="FILENAME"
->\tools\reskit\netadmin\poledit</TT
->.
-Install group policies on a Win9x client by double-clicking
+>cups.hlp</TT
+>
+into <TT
+CLASS="FILENAME"
+>/usr/share/drivers/</TT
+> instead of
 <TT
 CLASS="FILENAME"
->grouppol.inf</TT
->. Log off and on again a couple of times and see
-if Win98 picks up group policies.  Unfortunately this needs to be done on every
-Win9x/Me machine that uses group policies.</P
+>/usr/share/cups/drivers/</TT
+>. To work around this, copy/move
+the file after running the "./cups-samba.install" script manually to the right place:</P
+><P
+>	<KBD
+CLASS="USERINPUT"
+> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
+	</KBD
+>
+	</P
+></TD
+></TR
+></TABLE
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2955"
->16.1.2. Windows NT4 Style Policy Files</A
-></H3
+CLASS="NOTE"
 ><P
->To create or edit <TT
-CLASS="FILENAME"
->ntconfig.pol</TT
-> you must use the NT Server
-Policy Editor, <B
-CLASS="COMMAND"
->poledit.exe</B
-> which is included with NT4 Server
-but <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not NT Workstation</I
-></SPAN
->. There is a Policy Editor on a NT4
-Workstation but it is not suitable for creating <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Domain Policies</I
-></SPAN
->.
-Further, although the Windows 95 Policy Editor can be installed on an NT4
-Workstation/Server, it will not work with NT clients. However, the files from
-the NT Server will run happily enough on an NT4 Workstation.</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
->You need <TT
-CLASS="FILENAME"
->poledit.exe, common.adm</TT
-> and <TT
-CLASS="FILENAME"
->winnt.adm</TT
->.
-It is convenient to put the two *.adm files in  the <TT
-CLASS="FILENAME"
->c:\winnt\inf</TT
-> 
-directory which is where the binary will look for them unless told otherwise. Note also that that
-directory is normally 'hidden'.</P
+>This new CUPS PostScript driver is currently binary-only, but free
+no source code is provided (yet). The reason is this: it has
+been developed with the help of the Microsoft Driver Developer Kit (DDK)
+and compiled with Microsoft Visual Studio 6. It is not clear to the driver
+developers if they are allowed to distribute the whole of the source code
+as Free Software. However, they will likely release the "diff" in source
+code under the GPL, so anybody with a license of Visual Studio and a DDK
+will be able to compile for him/herself.</P
 ><P
->The Windows NT policy editor is also included with the Service Pack 3 (and
-later) for Windows NT 4.0. Extract the files using <B
-CLASS="COMMAND"
->servicepackname /x</B
->,
-i.e. that's <B
-CLASS="COMMAND"
->Nt4sp6ai.exe /x</B
-> for service pack 6a.  The policy editor,
-<B
-CLASS="COMMAND"
->poledit.exe</B
-> and the associated template files (*.adm) should
-be extracted as well.  It is also possible to downloaded the policy template
-files for Office97 and get a copy of the policy editor.  Another possible
-location is with the Zero Administration Kit available for download from Microsoft.</P
+>Once you have run the install script (and possibly manually moved the
+"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be
+put into Samba's [print$] share (which often maps to "/etc/samba/drivers/"
+and contains a subdir tree with WIN40 and W32X86 branches), by running
+"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to
+put root into the smbpasswd file by running "smbpasswd" should you run
+this whole procedure for the first time.] Once the driver files are in the
+[print$] share, they are ready to be downloaded and installed by the
+Win NT/2k/XP clients.</P
+></TD
+></TR
+></TABLE
+></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2970"
->16.1.2.1. Registry Tattoos</A
-></H4
+CLASS="NOTE"
 ><P
->	With NT4 style registry based policy changes, a large number of settings are not
-	automatically reversed as the user logs off. Since the settings that were in the
-	NTConfig.POL file were applied to the client machine registry and that apply to the
-	hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
-	as tattooing. It can have serious consequences down-stream and the administrator must
-	be extremely careful not to lock out the ability to manage the machine at a later date.
+></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
+>	Win 9x/ME clients won't work with this driver. For these you'd
+	still need to use the ADOBE*.* drivers as previously.
+	</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
+>	It is not harming if you've still the ADOBE*.* driver files from
+	previous installations in the "/usr/share/cups/drivers/" directory.
+	The new cupsaddsmb (from 1.1.16) will automatically use the
+	"newest" installed driver (which here then is the CUPS drivers).
 	</P
-></DIV
+></TD
+></TR
+></TABLE
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN2973"
->16.1.3. MS Windows 200x / XP Professional Policies</A
-></H3
+CLASS="NOTE"
 ><P
->Windows NT4 System policies allows setting of registry parameters specific to
-users, groups and computers (client workstations) that are members of the NT4
-style domain. Such policy file will work with MS Windows 2000 / XP clients also.</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
->New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
-a superset of capabilities compared with NT4 style policies. Obviously, the tool used
-to create them is different, and the mechanism for implementing them is much changed.</P
+>	Should your Win clients have had the old ADOBE*.* files and the
+	Adobe PostScript drivers installed, the download and installation
+	of the new CUPS PostScript driver for Windows NT/2k/XP will fail
+	at first.
+	</P
 ><P
->The older NT4 style registry based policies are known as <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Administrative Templates</I
-></SPAN
->
-in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
-configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
-users' desktop (including: the location of <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->My Documents</I
-></SPAN
-> files (directory), as
-well as intrinsics of where menu items will appear in the Start menu). An additional new
-feature is the ability to make available particular software Windows applications to particular
-users and/or groups.</P
+>	It is not enough to "delete" the printer (as the driver files
+	will still be kept by the clients and re-used if you try to
+	re-install the printer). To really get rid of the Adobe driver
+	files on the clients, open the "Printers" folder (possibly via
+	"Start --&#62; Settings --&#62; Control Panel --&#62; Printers"), right-click
+	onto the folder background and select "Server Properties". A
+	new dialog opens; select the "Drivers" tab; on the list select
+	the driver you want to delete and click on the "Delete" button.
+	(This will only work if there is no single printer left which
+	uses that particular driver -- you need to "delete" all printers
+	using this driver in the "Printers" folder first.)
+	</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="NOTE"
 ><P
->Remember: NT4 policy files are named <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> and are stored in the root
-of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
-and selects the domain name to which the logon will attempt to take place. During the logon
-process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
-server, modifies the local registry values according to the settings in this file.</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
->Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
-a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
-in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
-Directory domain controllers. The part that is stored in the Active Directory itself is called the
-group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
-known as the group policy template (GPT).</P
+>	Once you have successfully downloaded the CUPS PostScript driver
+	to a client, you can easily switch all printers to this one
+	by proceeding as described elsewhere in the "Samba HOWTO
+	Collection" to change a driver for an existing printer.
+	</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP"
+as compared to the Adobe drivers?</P
 ><P
->With NT4 clients the policy file is read and executed upon only aas each user log onto the network.
-MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
-startup (machine specific part) and when the user logs onto the network the user specific part
-is applied. In MS Windows 200x style policy management each machine and/or user may be subject
-to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
-the administrator to also set filters over the policy settings. No such equivalent capability
-exists with NT4 style policy files.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN2984"
->16.1.3.1. Administration of Win2K / XP Policies</A
-></H4
-><DIV
-CLASS="PROCEDURE"
 ><P
-><B
->Instructions</B
 ></P
+><UL
+><LI
 ><P
->Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the
-executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
-(MMC) snap-in as follows:</P
-><OL
-TYPE="1"
+>	no hassle with the Adobe EULA
+	</P
+></LI
 ><LI
 ><P
->Go to the Windows 200x / XP menu <TT
-CLASS="FILENAME"
->Start-&#62;Programs-&#62;Administrative Tools</TT
->
-	and select the MMC snap-in called "Active Directory Users and Computers"</P
+>	no hassle with the question "where do I get the ADOBE*.* driver files from?"
+	</P
+></LI
+><LI
 ><P
-></P
+>	the Adobe drivers (depending on the printer PPD associated with them)
+	often put a PJL header in front of the core PostScript part of the print
+	file (thus the file starts with "<VAR
+CLASS="REPLACEABLE"
+>1B</VAR
+>%-12345X" or "<VAR
+CLASS="REPLACEABLE"
+>escape</VAR
+>%-12345X"
+	instead of "%!PS"). This leads to the CUPS daemon autotyping the
+	arriving file as a print-ready file, not requiring a pass thru the
+	"pstops" filter (to speak more technical, it is not regarded as the
+	generic MIME type "application/postscript", but as the more special
+	MIME type "application/cups.vnd-postscript"), which therefore also
+	leads to the page accounting in "/var/log/cups/page_log" not receiving
+	the exact mumber of pages; instead the dummy page number of "1" is
+	logged in a standard setup)
+	</P
 ></LI
 ><LI
 ><P
->Select the domain or organizational unit (OU) that you wish to manage, then right click
-to open the context menu for that object, select the properties item.</P
+>	the Adobe driver has more options to "mis-configure" the PostScript
+	generated by it (like setting it inadvertedly to "Optimize for Speed",
+	instead of "Optimize for Portability", which could lead to CUPS being
+	unable to process it)
+	</P
+></LI
+><LI
+><P
+>	the CUPS PostScript driver output sent by Windows clients to the CUPS
+	server will be guaranteed to be auto-typed as generic MIME type
+	"application/postscript", thusly passing thru the CUPS "pstops" filter
+	and logging the correct number of pages in the page_log for accounting
+	and quota purposes
+	</P
+></LI
+><LI
+><P
+>	the CUPS PostScript driver supports the sending of additional print
+	options by the Win NT/2k/XP clients, such as naming the CUPS standard
+	banner pages (or the custom ones, should they be installed at the time
+	of driver download), using the CUPS "page-label" option, setting a
+	job-priority and setting the scheduled time of printing (with the option
+	to support additional useful IPP job attributes in the future).
+	</P
+></LI
+><LI
+><P
+>	the CUPS PostScript driver supports the inclusion of the new
+	"*cupsJobTicket" comments at the beginnig of the PostScript file (which
+	could be used in the future for all sort of beneficial extensions on
+	the CUPS side, but which will not disturb any other application as those
+	will regard it as a comment and simply ignore it).
+	</P
 ></LI
 ><LI
 ><P
->Now left click on the Group Policy tab, then left click on the New tab. Type a name
-for the new policy you will create.</P
-></LI
-><LI
+>	the CUPS PostScript driver will be the heart of the fully fledged CUPS
+	IPP client for Windows NT/2k/XP to be released soon (probably alongside
+	the first Beta release for CUPS 1.2).
+	</P
+></LI
+></UL
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2425"
+>14.11. Advanced Postscript Printing from MS Windows</A
+></H2
+><P
+>Let the Windows Clients use a PostScript driver to deliver poistscript to
+the samba print server (just like any Linux or Unix Client would also use
+PostScript to send to the server)</P
+><P
+>Make the Unix printing subsystem to which Samba sends the job convert the
+incoming PostScript files to the native print format of the target printers
+(would be PCL if you have an HP printer)</P
+><P
+>Now if you are afraid that this would just mean using a *Generic* PostScript
+driver for the clients that has no Simplex/Duplex selection, and no paper tray
+choice, but you need them to be able to set up print jobs, with all the bells
+and whistles of your printers:-</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Not possible with traditional spooling systems</TD
+></TR
+><TR
+><TD
+>	But perfectly supported by CUPS (which uses "PPD" files to
+	describe how to control the print options for PostScript and
+	non-PostScript devices alike...
+	</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
 ><P
->Now left click on the Edit tab to commence the steps needed to create the GPO.</P
-></LI
-></OL
-></DIV
+>CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
+drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
+them to setup the job to their liking and CUPS will use the received job options
+to make the (PCL-, ESC/P- or PostScript-) printer behave as required.</P
 ><P
->All policy configuration options are controlled through the use of policy administrative
-templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
-Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
-The later introduces many new features as well as extended definition capabilities. It is
-well beyond the scope of this documentation to explain how to program .adm files, for that
-the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
-version of MS Windows.</P
+>If you want to have the additional benefit of page count logging and accounting
+then the CUPS PostScript driver is the best choice (better than the Adobe one).</P
+><P
+>If you want to make the drivers downloadable for the clients then "cupsaddsmb" is
+your friend. It will setup the [print$] share on the Samba host to be ready to serve
+the clients for a "point and print" driver installation.</P
 ><DIV
-CLASS="NOTE"
+CLASS="WARNING"
 ><P
 ></P
 ><TABLE
-CLASS="NOTE"
+CLASS="WARNING"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -15197,63 +11468,55 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
-ALT="Note"></TD
+ALT="Warning"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
-to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
-use this powerful tool. Please refer to the resource kit manuals for specific usage information.</P
+>What strings are attached?</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
-></DIV
-></DIV
+><P
+>There are some. But, given the sheer CPU power you can buy nowadays,
+these can be overcome easily. The strings:</P
+><P
+>Well, if the CUPS/Samba side will have to print to many printers serving many users,
+you probably will need to set up a second server (which can do automatic load balancing
+with the first one, plus a degree of fail-over mechanism). Converting the incoming
+PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work
+of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM
+than for the mere "raw spooling" task your current setup is solving. It all depends
+on the avarage and peak printing load the server should be able to handle.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3002"
->16.2. Managing Account/User Policies</A
+NAME="AEN2440"
+>14.12. Auto-Deletion of CUPS spool files</A
 ></H2
 ><P
->Policies can define a specific user's settings or the settings for a group of users. The resulting
-policy file contains the registry settings for all users, groups, and computers that will be using
-the policy file. Separate policy files for each user, group, or computer are not not necessary.</P
-><P
->If you create a policy that will be automatically downloaded from validating domain controllers,
-you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
-policy file and, by modifying the Windows NT-based workstation, directing the computer to update
-the policy from a manual path. You can do this by either manually changing the registry or by using
-the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
-but if a change is necessary to all machines, this change must be made individually to each workstation.</P
-><P
->When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain 
-controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
-applied to the user's part of the registry.</P
-><P
->MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
-acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
-itself. The key benefit of using AS GPOs is that they impose no registry <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->tatooing</I
-></SPAN
-> effect.
-This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.</P
+>Samba print files pass thru two "spool" directories. One the incoming directory
+managed by Samba, (set eg: in the <B
+CLASS="COMMAND"
+>path = /var/spool/samba</B
+> directive in the [printers]
+section of <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>). Second is the spool directory of your UNIX print subsystem.
+For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive
+"RequestRoot /var/spool/cups".</P
 ><P
->Inaddition to user access controls that may be imposed or applied via system and/or group policies
-in a manner that works in conjunction with user profiles, the user management environment under
-MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
-Common restrictions that are frequently used includes:</P
+>I am not sure, which one of your directories keeps the files.  From what you say,
+it is most likely the Samba part.</P
 ><P
+>For the CUPS part, you may want to consult:</P
 ><P
 ></P
 ><TABLE
@@ -15261,153 +11524,89 @@ BORDER="0"
 ><TBODY
 ><TR
 ><TD
->Logon Hours</TD
-></TR
-><TR
-><TD
->Password Aging</TD
-></TR
-><TR
-><TD
->Permitted Logon from certain machines only</TD
+>http://localhost:631/sam.html#PreserveJobFiles</TD
 ></TR
 ><TR
 ><TD
->Account type (Local or Global)</TD
+>http://localhost:631/sam.html#PreserveJobHistory</TD
 ></TR
 ><TR
 ><TD
->User Rights</TD
+>http://localhost:631/sam.html#MaxJobs</TD
 ></TR
 ></TBODY
 ></TABLE
 ><P
 ></P
-></P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3017"
->16.2.1. With Windows NT4/200x</A
-></H3
 ><P
->The tools that may be used to configure these types of controls from the MS Windows environment are:
-The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
-Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
-"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3020"
->16.2.2. With a Samba PDC</A
-></H3
+>There are the settings described for your CUPS daemon, which could lead to completed
+job files not being deleted.</P
 ><P
->With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
-<TT
-CLASS="FILENAME"
->smbpasswd, pdbedit, smbgroupedit, net, rpcclient.</TT
->. The administrator should read the
-man pages for these tools and become familiar with their use.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="PROFILEMGMT"
-></A
->Chapter 17. Desktop Profile Management</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN3035"
->17.1. Roaming Profiles</A
-></H2
-><DIV
-CLASS="WARNING"
+>"PreserveJobHistory Yes" -- keeps some details of jobs in
+cupsd's mind (well it keeps the "c12345", "c12346" etc. files
+in the CUPS spool directory, which do a similar job as the
+old-fashioned BSD-LPD control files). This is set to "Yes"
+as a default.</P
+><P
+>"PreserveJobFiles Yes" -- keeps the job files themselves in
+cupsd's mind (well it keeps the "d12345", "d12346" etc. files
+in the CUPS spool directory...). This is set to "No" as the
+CUPS default.</P
+><P
+>"MaxJobs 500" -- this directive controls the maximum number
+of jobs that are kept in memory. Once the number of jobs
+reaches the limit, the oldest completed job is automatically
+purged from the system to make room for the new one. If all
+of the known jobs are still pending or active then the new
+job will be rejected. Setting the maximum to 0 disables this
+functionality. The default setting is 0.</P
+><P
+>(There are also additional settings for "MaxJobsPerUser" and
+"MaxJobsPerPrinter"...)</P
+><P
+>For everything to work as announced, you need to have three things:</P
 ><P
 ></P
 ><TABLE
-CLASS="WARNING"
-WIDTH="100%"
 BORDER="0"
+><TBODY
 ><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
->Roaming profiles support is different for Win9x / Me and Windows NT4/200x.</P
-></TD
+>	a Samba-<SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+> which is compiled against "libcups" (Check on Linux by running <KBD
+CLASS="USERINPUT"
+>ldd `which smbd`</KBD
+>)
+	</TD
 ></TR
-></TABLE
-></DIV
-><P
->Before discussing how to configure roaming profiles, it is useful to see how
-Windows 9x / Me and Windows NT4/200x clients implement these features.</P
-><P
->Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
-profiles location. However, the response does not have room for a separate
-profiles location field, only the user's home share. This means that Win9X/Me
-profiles are restricted to being stored in the user's home directory.</P
-><P
->Windows NT4/200x  clients send a NetSAMLogon RPC request, which contains many fields,
-including a separate field for the location of the user's profiles.</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3042"
->17.1.1. Samba Configuration for Profile Handling</A
-></H3
-><P
->This section documents how to configure Samba for MS Windows client profile support.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN3045"
->17.1.1.1. NT4/200x User Profiles</A
-></H4
-><P
->To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
-following (for example):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
+><TR
+><TD
+>	a Samba-<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> setting of <B
+CLASS="COMMAND"
+>printing = cups</B
 >
-
-	This is typically implemented like:
-
-<PRE
-CLASS="PROGRAMLISTING"
->		logon path = \\%L\Profiles\%u</PRE
+	</TD
+></TR
+><TR
+><TD
+>	another Samba-<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> setting of <B
+CLASS="COMMAND"
+>printcap = cups</B
 >
-where %L translates to the name of the Samba server and %u translates to the user name</P
+	</TD
+></TR
+></TBODY
+></TABLE
 ><P
->The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. 
-The \\N%\%U service is created automatically by the [homes] service.  If you are using
-a samba server for the profiles, you _must_ make the share specified in the logon path
-browseable. Please refer to the man page for smb.conf in respect of the different
-symantics of %L and %N, as well as %U and %u.</P
+></P
 ><DIV
 CLASS="NOTE"
 ><P
@@ -15429,1209 +11628,1767 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->MS Windows NT/2K clients at times do not disconnect a connection to a server
-between logons. It is recommended to NOT use the <B
-CLASS="COMMAND"
->homes</B
->
-meta-service name as part of the profile share path.</P
+>Note, that in this case all other manually set printing-related
+commands (like "print command", "lpq command", "lprm command",
+"lppause command" or "lpresume command") are ignored and they
+should normally have no influence what-so-ever on your printing.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
+><P
+>If you want to do things manually, replace the "printing = cups"
+by "printing = bsd". Then your manually set commands may work
+(haven't tested this), and a "print command = lp -d %P %s; rm %s"
+may do what you need.</P
+><P
+>You forgot to mention the CUPS version you're using. If you did
+set things up as described in the man pages, then the Samba
+spool files should be deleted. Otherwise it may be a bug. On
+the CUPS side, you can control the behaviour as described
+above.</P
+><P
+>If you have more problems, post the output of these commands:</P
+><P
+><KBD
+CLASS="USERINPUT"
+>   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
+   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</KBD
+></P
+><P
+>(adapt paths as needed). These commands sanitize the files
+and cut out the empty lines and lines with comments, providing
+the "naked settings" in a compact way.</P
+></DIV
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="CHAPTER"
+><HR><H1
 ><A
-NAME="AEN3055"
->17.1.1.2. Windows 9x / Me User Profiles</A
-></H4
+NAME="WINBIND"
+></A
+>Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN2516"
+>15.1. Abstract</A
+></H2
 ><P
->To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has
-now been fixed so that <KBD
-CLASS="USERINPUT"
->net use /home</KBD
-> now works as well, and it, too, relies
-on the <B
-CLASS="COMMAND"
->logon home</B
->&#60; parameter.</P
+>Integration of UNIX and Microsoft Windows NT through 
+	a unified logon has been considered a "holy grail" in heterogeneous 
+	computing environments for a long time. We present 
+	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>winbind</I
+></SPAN
+>, a component of the Samba suite 
+	of programs as a solution to the unified logon problem. Winbind 
+	uses a UNIX implementation 
+	of Microsoft RPC calls, Pluggable Authentication Modules, and the Name 
+	Service Switch to allow Windows NT domain users to appear and operate 
+	as UNIX users on a UNIX machine. This paper describes the winbind 
+	system, explaining the functionality it provides, how it is configured, 
+	and how it works internally.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2520"
+>15.2. Introduction</A
+></H2
 ><P
->By using the logon home parameter, you are restricted to putting Win9x / Me
-profiles in the user's home directory.   But wait! There is a trick you
-can use. If you set the following in the <B
-CLASS="COMMAND"
->[global]</B
-> section of your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file:</P
+>It is well known that UNIX and Microsoft Windows NT have 
+	different models for representing user and group information and 
+	use different technologies for implementing them. This fact has 
+	made it difficult to integrate the two systems in a satisfactory 
+	manner.</P
+><P
+>One common solution in use today has been to create 
+	identically named user accounts on both the UNIX and Windows systems 
+	and use the Samba suite of programs to provide file and print services 
+	between the two. This solution is far from perfect however, as 
+	adding and deleting users on both sets of machines becomes a chore 
+	and two sets of passwords are required both of which
+	can lead to synchronization problems between the UNIX and Windows 
+	systems and confusion for users.</P
+><P
+>We divide the unified logon problem for UNIX machines into 
+	three smaller problems:</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	logon home = \\%L\%U\.profiles</PRE
 ></P
+><UL
+><LI
 ><P
->then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
-of your home directory called <TT
-CLASS="FILENAME"
->.profiles</TT
-> (thus making them hidden).</P
+>Obtaining Windows NT user and group information
+		</P
+></LI
+><LI
 ><P
->Not only that, but <KBD
-CLASS="USERINPUT"
->net use/home</KBD
-> will also work, because of a feature in
-Windows 9x / Me. It removes any directory stuff off the end of the home directory area
-and only uses the server and share portion. That is, it looks like you
-specified \\%L\%U for <B
+>Authenticating Windows NT users
+		</P
+></LI
+><LI
+><P
+>Password changing for Windows NT users
+		</P
+></LI
+></UL
+><P
+>Ideally, a prospective solution to the unified logon problem 
+	would satisfy all the above components without duplication of 
+	information on the UNIX machines and without creating additional 
+	tasks for the system administrator when maintaining users and 
+	groups on either system. The winbind system provides a simple 
+	and elegant solution to all three components of the unified logon 
+	problem.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2533"
+>15.3. What Winbind Provides</A
+></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 
+	this is done the UNIX box will see NT users and groups as if 
+	they were native UNIX users and groups, allowing the NT domain 
+	to be used in much the same manner that NIS+ is used within 
+	UNIX-only environments.</P
+><P
+>The end result is that whenever any 
+	program on the UNIX machine asks the operating system to lookup 
+	a user or group name, the query will be resolved by asking the 
+	NT domain controller for the specified domain to do the lookup.
+	Because Winbind hooks into the operating system at a low level 
+	(via the NSS name resolution modules in the C library) this 
+	redirection to the NT domain controller is completely 
+	transparent.</P
+><P
+>Users on the UNIX machine can then use NT user and group 
+	names as they would use "native" UNIX names. They can chown files 
+	so that they are owned by NT domain users or even login to the 
+	UNIX machine and run a UNIX X-Window session as a domain user.</P
+><P
+>The only obvious indication that Winbind is being used is 
+	that user and group names take the form DOMAIN\user and 
+	DOMAIN\group. This is necessary as it allows Winbind to determine 
+	that redirection to a domain controller is wanted for a particular 
+	lookup and which trusted domain is being referenced.</P
+><P
+>Additionally, Winbind provides an authentication service 
+	that hooks into the Pluggable Authentication Modules (PAM) system 
+	to provide authentication via a NT domain to any PAM enabled 
+	applications. This capability solves the problem of synchronizing 
+	passwords between systems since all passwords are stored in a single 
+	location (on the domain controller).</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2540"
+>15.3.1. Target Uses</A
+></H3
+><P
+>Winbind is targeted at organizations that have an 
+		existing NT based domain infrastructure into which they wish 
+		to put UNIX workstations or servers. Winbind will allow these 
+		organizations to deploy UNIX workstations without having to 
+		maintain a separate account infrastructure. This greatly 
+		simplifies the administrative overhead of deploying UNIX 
+		workstations into a NT based organization.</P
+><P
+>Another interesting way in which we expect Winbind to 
+		be used is as a central part of UNIX based appliances. Appliances 
+		that provide file and print services to Microsoft based networks 
+		will be able to use Winbind to provide seamless integration of 
+		the appliance into the domain.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2544"
+>15.4. How Winbind Works</A
+></H2
+><P
+>The winbind system is designed around a client/server 
+	architecture. A long running <B
 CLASS="COMMAND"
->logon home</B
->.</P
+>winbindd</B
+> daemon 
+	listens on a UNIX domain socket waiting for requests
+	to arrive. These requests are generated by the NSS and PAM 
+	clients and processed sequentially.</P
+><P
+>The technologies used to implement winbind are described 
+	in detail below.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2549"
+>15.4.1. Microsoft Remote Procedure Calls</A
+></H3
+><P
+>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 
+		Windows NT machines including remote management, user authentication
+		and print spooling. Although initially this work was done 
+		to aid the implementation of Primary Domain Controller (PDC) 
+		functionality in Samba, it has also yielded a body of code which 
+		can be used for other purposes.</P
+><P
+>Winbind uses various MSRPC calls to enumerate domain users 
+		and groups and to obtain detailed information about individual 
+		users or groups. Other MSRPC calls can be used to authenticate 
+		NT domain users and to change user passwords. By directly querying 
+		a Windows PDC for user and group information, winbind maps the 
+		NT account information onto UNIX user and group names.</P
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN3070"
->17.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
-></H4
-><P
->You can support profiles for both Win9X and WinNT clients by setting both the
-<B
-CLASS="COMMAND"
->logon home</B
-> and <B
-CLASS="COMMAND"
->logon path</B
-> parameters. For example:</P
+NAME="AEN2553"
+>15.4.2. Microsoft Active Directory Services</A
+></H3
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u</PRE
-></P
-></DIV
+>                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="AEN3077"
->17.1.2. Windows Client Profile Configuration Information</A
+NAME="AEN2556"
+>15.4.3. Name Service Switch</A
 ></H3
-><DIV
-CLASS="SECT3"
-><H4
-CLASS="SECT3"
-><A
-NAME="AEN3079"
->17.1.2.1. Windows 9x / Me Profile Setup</A
-></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".
-These directories and their contents will be merged with the local
-versions stored in c:\windows\profiles\username on subsequent logins,
-taking the most recent from each.  You will need to use the [global]
-options "preserve case = yes", "short preserve case = yes" and
-"case sensitive = no" in order to maintain capital letters in shortcuts
-in any of the profile folders.</P
+>The Name Service Switch, or NSS, is a feature that is 
+		present in many UNIX operating systems. It allows system 
+		information such as hostnames, mail aliases and user information 
+		to be resolved from different sources. For example, a standalone 
+		UNIX workstation may resolve system information from a series of 
+		flat files stored on the local filesystem. A networked workstation 
+		may first attempt to resolve system information from local files, 
+		and then consult a NIS database for user information or a DNS server 
+		for hostname information.</P
 ><P
->The user.DAT file contains all the user's preferences.  If you wish to
-enforce a set of preferences, rename their user.DAT file to user.MAN,
-and deny them write access to this file.</P
+>The NSS application programming interface allows winbind 
+		to present itself as a source of system information when 
+		resolving UNIX usernames and groups.  Winbind uses this interface, 
+		and information obtained from a Windows NT server using MSRPC 
+		calls to provide a new source of account enumeration.  Using standard 
+		UNIX library calls, one can enumerate the users and groups on
+		a UNIX machine running winbind and see all users and groups in 
+		a NT domain plus any trusted domain as though they were local 
+		users and groups.</P
 ><P
-></P
-><OL
-TYPE="1"
-><LI
+>The primary control file for NSS is 
+		<TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>. 
+		When a UNIX application makes a request to do a lookup 
+		the C library looks in <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> 
+		for a line which matches the service type being requested, for 
+		example the "passwd" service type is used when user or group names 
+		are looked up. This	config line species which implementations 
+		of that service should be tried and in what order. If the passwd 
+		config line is:</P
 ><P
->        On the Windows 9x / Me machine, go to Control Panel -&#62; Passwords and
-        select the User Profiles tab.  Select the required level of
-        roaming preferences.  Press OK, but do _not_ allow the computer
-        to reboot.
-        </P
-></LI
-><LI
+><B
+CLASS="COMMAND"
+>passwd: files example</B
+></P
 ><P
->        On the Windows 9x / Me machine, go to Control Panel -&#62; Network -&#62;
-        Client for Microsoft Networks -&#62; Preferences.  Select 'Log on to
-        NT Domain'.  Then, ensure that the Primary Logon is 'Client for
-        Microsoft Networks'.  Press OK, and this time allow the computer
-        to reboot.
-        </P
-></LI
-></OL
+>then the C library will first load a module called 
+		<TT
+CLASS="FILENAME"
+>/lib/libnss_files.so</TT
+> followed by
+		the module <TT
+CLASS="FILENAME"
+>/lib/libnss_example.so</TT
+>. The 
+		C library will dynamically load each of these modules in turn 
+		and call resolver functions within the modules to try to resolve 
+		the request. Once the request is resolved the C library returns the
+		result to the application.</P
 ><P
->Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
-If you have the Primary Logon as 'Client for Novell Networks', then
-the profiles and logon script will be downloaded from your Novell
-Server.  If you have the Primary Logon as 'Windows Logon', then the
-profiles will be loaded from the local machine - a bit against the
-concept of roaming profiles, it would seem!</P
+>This NSS interface provides a very easy way for Winbind 
+		to hook into the operating system. All that needs to be done 
+		is to put <TT
+CLASS="FILENAME"
+>libnss_winbind.so</TT
+> in <TT
+CLASS="FILENAME"
+>/lib/</TT
+> 
+		then add "winbind" into <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> at 
+		the appropriate place. The C library will then call Winbind to 
+		resolve user and group names.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2572"
+>15.4.4. Pluggable Authentication Modules</A
+></H3
 ><P
->You will now find that the Microsoft Networks Login box contains
-[user, password, domain] instead of just [user, password].  Type in
-the samba server's domain name (or any other domain known to exist,
-but bear in mind that the user will be authenticated against this
-domain and profiles downloaded from it, if that domain logon server
-supports it), user name and user's password.</P
+>Pluggable Authentication Modules, also known as PAM, 
+		is a system for abstracting authentication and authorization 
+		technologies. With a PAM module it is possible to specify different 
+		authentication methods for different system applications without 
+		having to recompile these applications. PAM is also useful
+		for implementing a particular policy for authorization. For example, 
+		a system administrator may only allow console logins from users 
+		stored in the local password file but only allow users resolved from 
+		a NIS database to log in over the network.</P
 ><P
->Once the user has been successfully validated, the Windows 9x / Me machine
-will inform you that 'The user has not logged on before' and asks you
-if you wish to save the user's preferences?  Select 'yes'.</P
+>Winbind uses the authentication management and password 
+		management PAM interface to integrate Windows NT users into a 
+		UNIX system. This allows Windows NT users to log in to a UNIX 
+		machine and be authenticated against a suitable Primary Domain 
+		Controller. These users can also change their passwords and have 
+		this change take effect directly on the Primary Domain Controller.
+		</P
 ><P
->Once the Windows 9x / Me client comes up with the desktop, you should be able
-to examine the contents of the directory specified in the "logon path"
-on the samba server and verify that the "Desktop", "Start Menu",
-"Programs" and "Nethood" folders have been created.</P
+>PAM is configured by providing control files in the directory 
+		<TT
+CLASS="FILENAME"
+>/etc/pam.d/</TT
+> for each of the services that 
+		require authentication. When an authentication request is made 
+		by an application the PAM code in the C library looks up this
+		control file to determine what modules to load to do the 
+		authentication check and in what order. This interface makes adding 
+		a new authentication service for Winbind very easy, all that needs 
+		to be done is that the <TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+> module 
+		is copied to <TT
+CLASS="FILENAME"
+>/lib/security/</TT
+> and the PAM 
+		control files for relevant services are updated to allow 
+		authentication via winbind. See the PAM documentation
+		for more details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2580"
+>15.4.5. User and Group ID Allocation</A
+></H3
 ><P
->These folders will be cached locally on the client, and updated when
-the user logs off (if you haven't made them read-only by then).
-You will find that if the user creates further folders or short-cuts,
-that the client will merge the profile contents downloaded with the
-contents of the profile directory already on the local client, taking
-the newest folders and short-cuts from each set.</P
+>When a user or group is created under Windows NT 
+		is it allocated a numerical relative identifier (RID). This is 
+		slightly different to UNIX which has a range of numbers that are 
+		used to identify users, and the same range in which to identify 
+		groups. It is winbind's job to convert RIDs to UNIX id numbers and
+		vice versa.  When winbind is configured it is given part of the UNIX 
+		user id space and a part of the UNIX group id space in which to 
+		store Windows NT users and groups. If a Windows NT user is 
+		resolved for the first time, it is allocated the next UNIX id from 
+		the range. The same process applies for Windows NT groups. Over 
+		time, winbind will have mapped all Windows NT users and groups
+		to UNIX user ids and group ids.</P
 ><P
->If you have made the folders / files read-only on the samba server,
-then you will get errors from the Windows 9x / Me machine on logon and logout, as
-it attempts to merge the local and the remote profile.  Basically, if
-you have any errors reported by the Windows 9x / Me machine, check the Unix file
-permissions and ownership rights on the profile directory contents,
-on the samba server.</P
+>The results of this mapping are stored persistently in 
+		an ID mapping database held in a tdb database). This ensures that 
+		RIDs are mapped to UNIX IDs in a consistent way.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2584"
+>15.4.6. Result Caching</A
+></H3
 ><P
->If you have problems creating user profiles, you can reset the user's
-local desktop cache, as shown below.  When this user then next logs in,
-they will be told that they are logging in "for the first time".</P
+>An active system can generate a lot of user and group 
+		name lookups. To reduce the network cost of these lookups winbind 
+		uses a caching scheme based on the SAM sequence number supplied 
+		by NT domain controllers.  User or group information returned 
+		by a PDC is cached by winbind along with a sequence number also 
+		returned by the PDC. This sequence number is incremented by 
+		Windows NT whenever any user or group information is modified. If 
+		a cached entry has expired, the sequence number is requested from 
+		the PDC and compared against the sequence number of the cached entry. 
+		If the sequence numbers do not match, then the cached information 
+		is discarded and up to date information is requested directly 
+		from the PDC.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2587"
+>15.5. Installation and Configuration</A
+></H2
 ><P
-></P
-><OL
-TYPE="1"
-><LI
+>Many thanks to John Trostel <A
+HREF="mailto:jtrostel@snapserver.com"
+TARGET="_top"
+>jtrostel@snapserver.com</A
+>
+for providing the HOWTO for this section.</P
 ><P
->        instead of logging in under the [user, password, domain] dialog,
-        press escape.
-        </P
-></LI
-><LI
+>This HOWTO describes how to get winbind services up and running 
+to control access and authenticate users on your Linux box using 
+the winbind services which come with SAMBA 2.2.2.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2592"
+>15.5.1. Introduction</A
+></H3
 ><P
->        run the regedit.exe program, and look in:
-        </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 
+and authentication control for Windows Domain users through an NT 
+or Win2K PDC for 'regular' services, such as telnet a nd ftp, as
+well for SAMBA services.</P
 ><P
->        HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
-        </P
+>This HOWTO has been written from a 'RedHat-centric' perspective, so if 
+you are using another distribution, you may have to modify the instructions 
+somewhat to fit the way your distribution works.</P
 ><P
->        you will find an entry, for each user, of ProfilePath.  Note the
-        contents of this key (likely to be c:\windows\profiles\username),
-        then delete the key ProfilePath for the required user.
-
-        [Exit the registry editor].
-
-        </P
-></LI
+></P
+><UL
 ><LI
 ><P
->        <SPAN
+>	<SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->WARNING</I
+>Why should I to this?</I
 ></SPAN
-> - before deleting the contents of the
-        directory listed in the ProfilePath (this is likely to be
-	<TT
-CLASS="FILENAME"
->c:\windows\profiles\username)</TT
->, ask them if they
-	have any important files stored on their desktop or in their start menu. 
-	Delete the contents of the directory ProfilePath (making a backup if any
-	of the files are needed).
-        </P
+>
+	</P
 ><P
->	This will have the effect of removing the local (read-only hidden
-	system file) user.DAT in their profile directory, as well as the
-	local "desktop", "nethood", "start menu" and "programs" folders.
-        </P
+>This allows the SAMBA administrator to rely on the 
+	authentication mechanisms on the NT/Win2K PDC for the authentication 
+	of domain members.  NT/Win2K users no longer need to have separate 
+	accounts on the SAMBA server.
+	</P
 ></LI
 ><LI
 ><P
->        search for the user's .PWL password-caching file in the c:\windows
-        directory, and delete it.
-        </P
-></LI
-><LI
+>	<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Who should be reading this document?</I
+></SPAN
+>
+	</P
 ><P
->        log off the windows 9x / Me client.
-        </P
+>	This HOWTO is designed for system administrators.  If you are 
+	implementing SAMBA on a file server and wish to (fairly easily) 
+	integrate existing NT/Win2K users from your PDC onto the
+	SAMBA server, this HOWTO is for you.  That said, I am no NT or PAM 
+	expert, so you may find a better or easier way to accomplish 
+	these tasks.
+	</P
 ></LI
-><LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2605"
+>15.5.2. Requirements</A
+></H3
 ><P
->        check the contents of the profile path (see "logon path" described
-        above), and delete the user.DAT or user.MAN file for the user,
-        making a backup if required.
-        </P
-></LI
-></OL
+>If you have a samba configuration file that you are currently 
+using... <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>BACK IT UP!</I
+></SPAN
+>  If your system already uses PAM, 
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>back up the <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> directory 
+contents!</I
+></SPAN
+> If you haven't already made a boot disk, 
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>MAKE ONE NOW!</I
+></SPAN
+></P
 ><P
->If all else fails, increase samba's debug log levels to between 3 and 10,
-and / or run a packet trace program such as ethereal or netmon.exe, and
-look for error messages.</P
+>Messing with the pam configuration files can make it nearly impossible 
+to log in to yourmachine. That's why you want to be able to boot back 
+into your machine in single user mode and restore your 
+<TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> back to the original state they were in if 
+you get frustrated with the way things are going.  ;-)</P
 ><P
->If you have access to an Windows NT4/200x server, then first set up roaming profiles
-and / or netlogons on the Windows NT4/200x server.  Make a packet trace, or examine
-the example packet traces provided with Windows NT4/200x server, and see what the
-differences are with the equivalent samba trace.</P
+>The latest version of SAMBA (version 3.0 as of this writing), now 
+includes a functioning winbindd daemon.  Please refer to the 
+<A
+HREF="http://samba.org/"
+TARGET="_top"
+>main SAMBA web page</A
+> or, 
+better yet, your closest SAMBA mirror site for instructions on 
+downloading the source code.</P
+><P
+>To allow Domain users the ability to access SAMBA shares and 
+files, as well as potentially other services provided by your 
+SAMBA machine, PAM (pluggable authentication modules) must
+be setup properly on your machine.  In order to compile the 
+winbind modules, you should have at least the pam libraries resident 
+on your system.  For recent RedHat systems (7.1, for instance), that 
+means <TT
+CLASS="FILENAME"
+>pam-0.74-22</TT
+>.  For best results, it is helpful to also
+install the development packages in <TT
+CLASS="FILENAME"
+>pam-devel-0.74-22</TT
+>.</P
 ></DIV
 ><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2619"
+>15.5.3. Testing Things Out</A
+></H3
+><P
+>Before starting, it is probably best to kill off all the SAMBA 
+related daemons running on your server.  Kill off all <B
+CLASS="COMMAND"
+>smbd</B
+>, 
+<B
+CLASS="COMMAND"
+>nmbd</B
+>, and <B
+CLASS="COMMAND"
+>winbindd</B
+> processes that may 
+be running.  To use PAM, you will want to make sure that you have the 
+standard PAM package (for RedHat) which supplies the <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> 
+directory structure, including the pam modules are used by pam-aware 
+services, several pam libraries, and the <TT
+CLASS="FILENAME"
+>/usr/doc</TT
+> 
+and <TT
+CLASS="FILENAME"
+>/usr/man</TT
+> entries for pam.  Winbind built better 
+in SAMBA if the pam-devel package was also installed.  This package includes 
+the header files needed to compile pam-aware applications. For instance, 
+my RedHat system has both <TT
+CLASS="FILENAME"
+>pam-0.74-22</TT
+> and
+<TT
+CLASS="FILENAME"
+>pam-devel-0.74-22</TT
+> RPMs installed.</P
+><DIV
 CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN3115"
->17.1.2.2. Windows NT4 Workstation</A
+NAME="AEN2630"
+>15.5.3.1. Configure and compile SAMBA</A
 ></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
-through the "logon path" parameter.</P
+>The configuration and compilation of SAMBA is pretty straightforward.
+The first three steps may not be necessary depending upon
+whether or not you have previously built the Samba binaries.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>autoconf</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>make clean</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>rm config.cache</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>./configure</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>make</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>make install</B
+></PRE
+></P
 ><P
->There is a parameter that is now available for use with NT Profiles:
-"logon drive".  This should be set to <TT
+>This will, by default, install SAMBA in <TT
 CLASS="FILENAME"
->H:</TT
-> or any other drive, and
-should be used in conjunction with the new "logon home" parameter.</P
-><P
->The entry for the NT4 profile is a _directory_ not a file.  The NT
-help on profiles mentions that a directory is also created with a .PDS
-extension.  The user, while logging in, must have write permission to
-create the full profile path (and the folder with the .PDS extension
-for those situations where it might be created.)</P
-><P
->In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. 
-It creates "Application Data" and others, as well as "Desktop", "Nethood",
-"Start Menu" and "Programs".  The profile itself is stored in a file
-NTuser.DAT.  Nothing appears to be stored in the .PDS directory, and
-its purpose is currently unknown.</P
-><P
->You can use the System Control Panel to copy a local profile onto
-a samba server (see NT Help on profiles: it is also capable of firing
-up the correct location in the System Control Panel for you).  The
-NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
-turns a profile into a mandatory one.</P
-><P
->The case of the profile is significant.  The file must be called
-NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P
+>/usr/local/samba</TT
+>.
+See the main SAMBA documentation if you want to install SAMBA somewhere else.
+It will also build the winbindd executable and libraries. </P
 ></DIV
 ><DIV
 CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN3124"
->17.1.2.3. Windows 2000/XP Professional</A
+NAME="AEN2649"
+>15.5.3.2. Configure <TT
+CLASS="FILENAME"
+>nsswitch.conf</TT
+> and the 
+winbind libraries</A
 ></H4
 ><P
->You must first convert the profile from a local profile to a domain
-profile on the MS Windows workstation as follows:</P
+>The libraries needed to run the <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon 
+through nsswitch need to be copied to their proper locations, so</P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>cp ../samba/source/nsswitch/libnss_winbind.so /lib</B
 ></P
-><UL
-><LI
 ><P
->	Log on as the LOCAL workstation administrator.
-	</P
-></LI
-><LI
+>I also found it necessary to make the following symbolic link:</P
 ><P
->	Right click on the 'My Computer' Icon, select 'Properties'
-	</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B
+></P
 ><P
->	Click on the 'User Profiles' tab
-	</P
-></LI
-><LI
+>And, in the case of Sun solaris:</P
 ><P
->	Select the profile you wish to convert (click on it once)
-	</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B
+>
+<SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B
+></P
 ><P
->	Click on the button 'Copy To'
-	</P
-></LI
-><LI
+>Now, as root you need to edit <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> to 
+allow user and group entries to be visible from the <B
+CLASS="COMMAND"
+>winbindd</B
+> 
+daemon.  My <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file look like 
+this after editing:</P
 ><P
->	In the "Permitted to use" box, click on the 'Change' button.
-	</P
-></LI
-><LI
+><PRE
+CLASS="PROGRAMLISTING"
+>	passwd:     files winbind
+	shadow:     files 
+	group:      files winbind</PRE
+></P
 ><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"
+>	
+The libraries needed by the winbind daemon will be automatically 
+entered into the <B
+CLASS="COMMAND"
+>ldconfig</B
+> cache the next time 
+your system reboots, but it 
+is faster (and you don't need to reboot) if you do it manually:</P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/sbin/ldconfig -v | grep winbind</B
 ></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
+>This makes <TT
+CLASS="FILENAME"
+>libnss_winbind</TT
+> available to winbindd 
+and echos back a check to you.</P
 ></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
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2682"
+>15.5.3.3. Configure smb.conf</A
+></H4
 ><P
->Done. You now have a profile that can be editted using the samba-3.0.0
+>Several parameters are needed in the smb.conf file to control 
+the behavior of <B
+CLASS="COMMAND"
+>winbindd</B
+>. Configure 
 <TT
 CLASS="FILENAME"
->profiles</TT
-> tool.</P
-><DIV
-CLASS="NOTE"
+>smb.conf</TT
+> These are described in more detail in 
+the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> man page.  My 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file was modified to
+include the following entries in the [global] section:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+     &#60;...&#62;
+     # separate domain and username with '+', like DOMAIN+username
+     <A
+HREF="winbindd.8.html#WINBINDSEPARATOR"
+TARGET="_top"
+>winbind separator</A
+> = +
+     # use uids from 10000 to 20000 for domain users
+     <A
+HREF="winbindd.8.html#WINBINDUID"
+TARGET="_top"
+>winbind uid</A
+> = 10000-20000
+     # use gids from 10000 to 20000 for domain groups
+     <A
+HREF="winbindd.8.html#WINBINDGID"
+TARGET="_top"
+>winbind gid</A
+> = 10000-20000
+     # allow enumeration of winbind users and groups
+     <A
+HREF="winbindd.8.html#WINBINDENUMUSERS"
+TARGET="_top"
+>winbind enum users</A
+> = yes
+     <A
+HREF="winbindd.8.html#WINBINDENUMGROUP"
+TARGET="_top"
+>winbind enum groups</A
+> = yes
+     # give winbind users a real shell (only needed if they have telnet access)
+     <A
+HREF="winbindd.8.html#TEMPLATEHOMEDIR"
+TARGET="_top"
+>template homedir</A
+> = /home/winnt/%D/%U
+     <A
+HREF="winbindd.8.html#TEMPLATESHELL"
+TARGET="_top"
+>template shell</A
+> = /bin/bash</PRE
 ></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"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2698"
+>15.5.3.4. Join the SAMBA server to the PDC domain</A
+></H4
 ><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"
+>Enter the following command to make the SAMBA server join the 
+PDC domain, where <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+> is the name of 
+your Windows domain and <VAR
+CLASS="REPLACEABLE"
+>Administrator</VAR
+> is 
+a domain user who has administrative privileges in the domain.</P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/net join -S PDC -U Administrator</B
 ></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
+>The proper response to the command should be: "Joined the domain 
+<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>" where <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+> 
+is your DOMAIN name.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2709"
+>15.5.3.5. Start up the winbindd daemon and test it!</A
+></H4
 ><P
->Click: "Start", "Run"</P
-></LI
-><LI
+>Eventually, you will want to modify your smb startup script to 
+automatically invoke the winbindd daemon when the other parts of 
+SAMBA start, but it is possible to test out just the winbind
+portion first.  To start up winbind services, enter the following 
+command as root:</P
 ><P
->Type: "mmc"</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/winbindd</B
+></P
 ><P
->Click: "OK"</P
-></LI
-><LI
+>Winbindd can now also run in 'dual daemon mode'. This will make it 
+run as 2 processes. The first will answer all requests from the cache,
+thus making responses to clients faster. The other will
+update the cache for the query that the first has just responded.
+Advantage of this is that responses stay accurate and are faster. 
+You can enable dual daemon mode by adding '-B' to the commandline:</P
 ><P
->A Microsoft Management Console should appear.</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/winbindd -B</B
+></P
 ><P
->Click: File, "Add/Remove Snap-in...", "Add"</P
-></LI
-><LI
+>I'm always paranoid and like to make sure the daemon 
+is really running...</P
 ><P
->Double-Click: "Group Policy"</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>ps -ae | grep winbindd</B
+></P
 ><P
->Click: "Finish", "Close"</P
-></LI
-><LI
+>This command should produce output like this, if the daemon is running</P
 ><P
->Click: "OK"</P
-></LI
-><LI
+>3025 ?        00:00:00 winbindd</P
 ><P
->In the "Console Root" window:</P
-></LI
-><LI
+>Now... for the real test, try to get some information about the 
+users on your PDC</P
 ><P
->Expand: "Local Computer Policy", "Computer Configuration",</P
-></LI
-><LI
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/wbinfo -u</B
+></P
 ><P
->"Administrative Templates", "System", "User Profiles"</P
-></LI
-><LI
+>	
+This should echo back a list of users on your Windows users on 
+your PDC.  For example, I get the following response:</P
 ><P
->Double-Click: "Do not check for user ownership of Roaming Profile</P
-></LI
-><LI
+><PRE
+CLASS="PROGRAMLISTING"
+>CEO+Administrator
+CEO+burdell
+CEO+Guest
+CEO+jt-ad
+CEO+krbtgt
+CEO+TsInternetUser</PRE
+></P
 ><P
->Folders"</P
-></LI
-><LI
+>Obviously, I have named my domain 'CEO' and my <VAR
+CLASS="PARAMETER"
+>winbind
+separator</VAR
+> is '+'.</P
 ><P
->Select: "Enabled"</P
-></LI
-><LI
+>You can do the same sort of thing to get group information from 
+the PDC:</P
 ><P
->Click: OK"</P
-></LI
-><LI
+><PRE
+CLASS="PROGRAMLISTING"
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/wbinfo -g</B
+>
+CEO+Domain Admins
+CEO+Domain Users
+CEO+Domain Guests
+CEO+Domain Computers
+CEO+Domain Controllers
+CEO+Cert Publishers
+CEO+Schema Admins
+CEO+Enterprise Admins
+CEO+Group Policy Creator Owners</PRE
+></P
 ><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
+>The function 'getent' can now be used to get unified 
+lists of both local and PDC users and groups.
+Try the following command:</P
 ><P
->Reboot</P
-></LI
-></UL
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3197"
->17.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
-></H3
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>getent passwd</B
+></P
 ><P
->Sharing of desktop profiles between Windows versions is NOT recommended.
-Desktop profiles are an evolving phenomenon and profiles for later versions
-of MS Windows clients add features that may interfere with earlier versions
-of MS Windows clients. Probably the more salient reason to NOT mix profiles
-is that when logging off an earlier version of MS Windows the older format
-of profile contents may overwrite information that belongs to the newer
-version resulting in loss of profile information content when that user logs
-on again with the newer version of MS Windows.</P
+>You should get a list that looks like your <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> 
+list followed by the domain users with their new uids, gids, home 
+directories and default shells.</P
 ><P
->If you then want to share the same Start Menu / Desktop with W9x/Me, you will
-need to specify a common location for the profiles. The smb.conf parameters
-that need to be common are <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->logon path</I
-></SPAN
-> and
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->logon home</I
-></SPAN
->.</P
+>The same thing can be done for groups with the command</P
 ><P
->If you have this set up correctly, you will find separate user.DAT and
-NTuser.DAT files in the same profile directory.</P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>getent group</B
+></P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3204"
->17.1.4. Profile Migration from Windows NT4/200x Server to Samba</A
-></H3
-><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
-profile be stored on a samba server, or any other SMB server, as long as
-that SMB server supports encrypted passwords.</P
-><DIV
 CLASS="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN3207"
->17.1.4.1. Windows NT4 Profile Management Tools</A
+NAME="AEN2749"
+>15.5.3.6. Fix the init.d startup scripts</A
 ></H4
+><DIV
+CLASS="SECT4"
+><H5
+CLASS="SECT4"
+><A
+NAME="AEN2751"
+>15.5.3.6.1. Linux</A
+></H5
 ><P
->Unfortunately, the Resource Kit information is specific to the version of MS Windows
-NT4/200x. The correct resource kit is required for each platform.</P
-><P
->Here is a quick guide:</P
+>The <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon needs to start up after the 
+<B
+CLASS="COMMAND"
+>smbd</B
+> and <B
+CLASS="COMMAND"
+>nmbd</B
+> daemons are running.  
+To accomplish this task, you need to modify the startup scripts of your system. They are located at <TT
+CLASS="FILENAME"
+>/etc/init.d/smb</TT
+> in RedHat and 
+<TT
+CLASS="FILENAME"
+>/etc/init.d/samba</TT
+> in Debian.
+script to add commands to invoke this daemon in the proper sequence.  My 
+startup script starts up <B
+CLASS="COMMAND"
+>smbd</B
+>, 
+<B
+CLASS="COMMAND"
+>nmbd</B
+>, and <B
+CLASS="COMMAND"
+>winbindd</B
+> from the 
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/bin</TT
+> directory directly.  The 'start' 
+function in the script looks like this:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>start() {
+        KIND="SMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        echo -n $"Starting $KIND services: "
+        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=1
+        return $RETVAL
+}</PRE
 ></P
-><UL
-><LI
 ><P
->On your NT4 Domain Controller, right click on 'My Computer', then
-select the tab labelled 'User Profiles'.</P
-></LI
-><LI
+>If you would like to run winbindd in dual daemon mode, replace 
+the line 
+<PRE
+CLASS="PROGRAMLISTING"
+>        daemon /usr/local/samba/bin/winbindd</PRE
+>
+
+in the example above with:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>        daemon /usr/local/samba/bin/winbindd -B</PRE
+>.</P
 ><P
->Select a user profile you want to migrate and click on it.</P
+>The 'stop' function has a corresponding entry to shut down the 
+services and looks like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>stop() {
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc smbd
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc nmbd
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        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
+        echo ""
+        return $RETVAL
+}</PRE
+></P
+></DIV
 ><DIV
-CLASS="NOTE"
+CLASS="SECT4"
+><HR><H5
+CLASS="SECT4"
+><A
+NAME="AEN2771"
+>15.5.3.6.2. Solaris</A
+></H5
+><P
+>On solaris, you need to modify the 
+<TT
+CLASS="FILENAME"
+>/etc/init.d/samba.server</TT
+> startup script. It usually 
+only starts smbd and nmbd but should now start winbindd too. If you 
+have samba installed in <TT
+CLASS="FILENAME"
+>/usr/local/samba/bin</TT
+>, 
+the file could contains something like this:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>##
+## samba.server
+##
+
+if [ ! -d /usr/bin ]
+then                    # /usr not mounted
+        exit
+fi
+
+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
+}
+ 
+# Start/stop processes required for samba server
+
+case "$1" in
+
+'start')
+#
+# Edit these lines to suit your installation (paths, workgroup, host)
+#
+echo Starting SMBD
+   /usr/local/samba/bin/smbd -D -s \
+	/usr/local/samba/smb.conf
+
+echo Starting NMBD
+   /usr/local/samba/bin/nmbd -D -l \
+	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
+
+echo Starting Winbind Daemon
+   /usr/local/samba/bin/winbindd
+   ;;
+
+'stop')
+   killproc nmbd
+   killproc smbd
+   killproc winbindd
+   ;;
+
+*)
+   echo "Usage: /etc/init.d/samba.server { start | stop }"
+   ;;
+esac</PRE
 ></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 "migrate" lossely. You can copy a profile to
-create a group profile. You can give the user 'Everyone' rights to the
-profile you copy this to. That is what you need to do, since your samba
-domain is not a member of a trust relationship with your NT4 PDC.</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
+>Again, if you would like to run samba in dual daemon mode, replace 
+<PRE
+CLASS="PROGRAMLISTING"
+>   /usr/local/samba/bin/winbindd</PRE
+>
+
+in the script above with:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>   /usr/local/samba/bin/winbindd -B</PRE
 ></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
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT4"
+><HR><H5
+CLASS="SECT4"
 ><A
-NAME="AEN3230"
->17.1.4.2. Side bar Notes</A
-></H4
-><P
->You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.</P
+NAME="AEN2781"
+>15.5.3.6.3. Restarting</A
+></H5
 ><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
+>If you restart the <B
+CLASS="COMMAND"
+>smbd</B
+>, <B
+CLASS="COMMAND"
+>nmbd</B
+>, 
+and <B
+CLASS="COMMAND"
+>winbindd</B
+> daemons at this point, you
+should be able to connect to the samba server as a domain member just as
+if you were a local user.</P
 ></DIV
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN3234"
->17.1.4.3. moveuser.exe</A
-></H4
-><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="SECT3"
 ><HR><H4
 CLASS="SECT3"
 ><A
-NAME="AEN3237"
->17.1.4.4. Get SID</A
+NAME="AEN2787"
+>15.5.3.7. Configure Winbind and PAM</A
 ></H4
 ><P
->You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
-Resource Kit.</P
-><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
->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
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3242"
->17.2. Mandatory profiles</A
-></H2
-><P
->A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
-During the user's session it may be possible to change the desktop environment, but
-as the user logs out all changes made will be lost. If it is desired to NOT allow the
-user any ability to change the desktop environment then this must be done through
-policy settings. See previous chapter.</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 NO circumstances should the profile directory (or it's contents) be made read-only
-as this may render the profile un-usable.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->For MS Windows NT4/200x/XP 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
-><P
->For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
-affect a mandatory profile.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3249"
->17.3. Creating/Managing Group Profiles</A
-></H2
-><P
->Most organisations are arranged into departments. There is a nice benenfit in
-this fact since usually most users in a department will require the same desktop
-applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
-use of Group Profiles. A Group Profile is a profile that is created firstly using
-a template (example) user. Then using the profile migration tool (see above) the
-profile is assigned access rights for the user group that needs to be given access
-to the group profile.</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 
+services, keep reading.  The pam configuration files need to be altered in
+this step.  (Did you remember to make backups of your original 
+<TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> files? If not, do it now.)</P
 ><P
->The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
-to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
-the now modified profile.</P
-><DIV
-CLASS="NOTE"
+>You will need a pam module to use winbindd with these other services.  This 
+module will be compiled in the <TT
+CLASS="FILENAME"
+>../source/nsswitch</TT
+> directory
+by invoking the command</P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>make nsswitch/pam_winbind.so</B
 ></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
->	Be careful with group profiles, if the user who is a member of a group also
-	has a personal profile, then the result will be a fusion (merge) of the two.
-	</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3255"
->17.4. Default Profile for Windows Users</A
-></H2
 ><P
->MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
-a profile does not already exist. Armed with a knowledge of where the default profile
-is located on the Windows workstation, and knowing which registry keys affect the path
-from which the default profile is created, it is possible to modify the default profile
-to one that has been optimised for the site. This has significant administrative 
-advantages.</P
+>from the <TT
+CLASS="FILENAME"
+>../source</TT
+> directory.  The
+<TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+> file should be copied to the location of
+your other pam security modules.  On my RedHat system, this was the
+<TT
+CLASS="FILENAME"
+>/lib/security</TT
+> directory. On Solaris, the pam security 
+modules reside in <TT
+CLASS="FILENAME"
+>/usr/lib/security</TT
+>.</P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root#</SAMP
+> <B
+CLASS="COMMAND"
+>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B
 ></P
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT4"
+><HR><H5
+CLASS="SECT4"
 ><A
-NAME="AEN3259"
->17.4.1. MS Windows 9x/Me</A
-></H3
+NAME="AEN2804"
+>15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
+></H5
 ><P
->To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
-Policy Editor or change the registry directly.</P
+>The <TT
+CLASS="FILENAME"
+>/etc/pam.d/samba</TT
+> file does not need to be changed. I 
+just left this fileas it was:</P
 ><P
->To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
-select File -&#62; Open Registry, then click on the Local Computer icon, click on Windows 98 System,
-select User Profiles, click on the enable box. Do not forget to save the registry changes.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth    required        /lib/security/pam_stack.so service=system-auth
+account required        /lib/security/pam_stack.so service=system-auth</PRE
+></P
 ><P
->To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
+>The other services that I modified to allow the use of winbind 
+as an authentication service were the normal login on the console (or a terminal 
+session), telnet logins, and ftp service.  In order to enable these 
+services, you may first need to change the entries in 
 <TT
 CLASS="FILENAME"
->HKEY_LOCAL_MACHINE\Network\Logon</TT
->. Now add a DWORD type key with the name
-"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN3265"
->17.4.1.1. How User Profiles Are Handled in Windows 9x / Me?</A
-></H4
-><P
->When a user logs on to a Windows 9x / Me machine, the local profile path, 
-<TT
+>/etc/xinetd.d</TT
+> (or <TT
 CLASS="FILENAME"
->HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</TT
->, is checked
-for an existing entry for that user:</P
+>/etc/inetd.conf</TT
+>).  
+RedHat 7.1 uses the new xinetd.d structure, in this case you need 
+to change the lines in <TT
+CLASS="FILENAME"
+>/etc/xinetd.d/telnet</TT
+> 
+and <TT
+CLASS="FILENAME"
+>/etc/xinetd.d/wu-ftp</TT
+> from </P
 ><P
->If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
-version of the user profile. Windows 9x / Me also checks the user's home directory (or other
-specified directory if the location has been modified) on the server for the User Profile.
-If a profile exists in both locations, the newer of the two is used. If the User Profile exists
-on the server, but does not exist on the local machine, the profile on the server is downloaded
-and used. If the User Profile only exists on the local machine, that copy is used.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>enable = no</PRE
+></P
 ><P
->If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
-machine is used and is copied to a newly created folder for the logged on user. At log off, any
-changes that the user made are written to the user's local profile. If the user has a roaming
-profile, the changes are written to the user's profile on the server.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3271"
->17.4.2. MS Windows NT4 Workstation</A
-></H3
+>to</P
 ><P
->On MS Windows NT4 the default user profile is obtained from the location
-<TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles</TT
-> which in a default installation will translate to
-<TT
-CLASS="FILENAME"
->C:\WinNT\Profiles</TT
->. Under this directory on a clean install there will be
-three (3) directories: <TT
+><PRE
+CLASS="PROGRAMLISTING"
+>enable = yes</PRE
+></P
+><P
+>	
+For ftp services to work properly, you will also need to either 
+have individual directories for the domain users already present on 
+the server, or change the home directory template to a general
+directory for all domain users.  These can be easily set using 
+the <TT
 CLASS="FILENAME"
->Administrator, All Users, Default User</TT
+>smb.conf</TT
+> global entry 
+<B
+CLASS="COMMAND"
+>template homedir</B
 >.</P
 ><P
 >The <TT
 CLASS="FILENAME"
->All Users</TT
-> directory contains menu settings that are common across all 
-system users. The <TT
+>/etc/pam.d/ftp</TT
+> file can be changed 
+to allow winbind ftp access in a manner similar to the
+samba file.  My <TT
 CLASS="FILENAME"
->Default User</TT
-> directory contains menu entries that are
-customisable per user depending on the profile settings chosen/created.</P
+>/etc/pam.d/ftp</TT
+> file was 
+changed to look like this:</P
 ><P
->When a new user first logs onto an MS Windows NT4 machine a new profile is created from:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
+auth       sufficient   /lib/security/pam_winbind.so
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_shells.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth</PRE
+></P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/pam.d/login</TT
+> file can be changed nearly the 
+same way.  It now looks like this:</P
 ><P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth       required     /lib/security/pam_securetty.so
+auth       sufficient   /lib/security/pam_winbind.so
+auth       sufficient   /lib/security/pam_unix.so use_first_pass
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_nologin.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so</PRE
 ></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->All Users settings</TD
-></TR
-><TR
-><TD
->Default User settings (contains the default NTUser.DAT file)</TD
-></TR
-></TBODY
-></TABLE
 ><P
+>In this case, I added the <B
+CLASS="COMMAND"
+>auth sufficient /lib/security/pam_winbind.so</B
+> 
+lines as before, but also added the <B
+CLASS="COMMAND"
+>required pam_securetty.so</B
+> 
+above it, to disallow root logins over the network.  I also added a 
+<B
+CLASS="COMMAND"
+>sufficient /lib/security/pam_unix.so use_first_pass</B
+>
+line after the <B
+CLASS="COMMAND"
+>winbind.so</B
+> line to get rid of annoying 
+double prompts for passwords.</P
+></DIV
+><DIV
+CLASS="SECT4"
+><HR><H5
+CLASS="SECT4"
+><A
+NAME="AEN2837"
+>15.5.3.7.2. Solaris-specific configuration</A
+></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
+that I made.You can customize the pam.conf file as per your requirements,but
+be sure of those changes because in the worst case it will leave your system
+nearly impossible to boot.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#
+#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+#
+# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+# All Rights Reserved.
+#
+# PAM configuration
+#
+# Authentication management
+#
+login   auth required   /usr/lib/security/pam_winbind.so
+login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
+login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
+#
+rlogin  auth sufficient /usr/lib/security/pam_winbind.so
+rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
+other   auth sufficient /usr/lib/security/pam_winbind.so
+other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+# Account management
+#
+login   account sufficient      /usr/lib/security/pam_winbind.so
+login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+dtlogin account sufficient      /usr/lib/security/pam_winbind.so
+dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+other   account sufficient      /usr/lib/security/pam_winbind.so
+other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+# Session management
+#
+other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+# Password management
+#
+#other   password sufficient     /usr/lib/security/pam_winbind.so
+other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
+dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
+#
+# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+#
+#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass</PRE
 ></P
 ><P
->When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
-the following steps are followed in respect of profile handling:</P
+>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 and try connecting through your application that you
+configured in the pam.conf.</P
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2844"
+>15.6. Limitations</A
+></H2
+><P
+>Winbind has a number of limitations in its current 
+	released version that we hope to overcome in future 
+	releases:</P
 ><P
 ></P
-><OL
-TYPE="1"
+><UL
 ><LI
 ><P
->	The users' account information which is obtained during the logon process contains
-	the location of the users' desktop profile. The profile path may be local to the
-	machine or it may be located on a network share. If there exists a profile at the location
-	of the path from the user account, then this profile is copied to the location
-	<TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->. This profile then inherits the
-	settings in the <TT
-CLASS="FILENAME"
->All Users</TT
-> profile in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles</TT
->
-	location.
-	</P
+>Winbind is currently only available for 
+		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
+		Modules systems. This is becoming more common as NSS and 
+		PAM gain	support among UNIX vendors.</P
 ></LI
 ><LI
 ><P
->	If the user account has a profile path, but at it's location a profile does not exist,
-	then a new profile is created in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->
-	directory from reading the <TT
-CLASS="FILENAME"
->Default User</TT
-> profile.
-	</P
+>The mappings of Windows NT RIDs to UNIX ids 
+		is not made algorithmically and depends on the order in which 
+		unmapped users or groups are seen by winbind. It may be difficult 
+		to recover the mappings of rid to UNIX id mapping if the file 
+		containing this information is corrupted or destroyed.</P
 ></LI
 ><LI
 ><P
->	If the NETLOGON share on the authenticating server (logon server) contains a policy file
-	(<TT
-CLASS="FILENAME"
->NTConfig.POL</TT
->) then it's contents are applied to the <TT
-CLASS="FILENAME"
->NTUser.DAT</TT
->
-	which is applied to the <TT
-CLASS="FILENAME"
->HKEY_CURRENT_USER</TT
-> part of the registry. 
-	</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, this is
+		instead up to the PDC to enforce.</P
 ></LI
-><LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2854"
+>15.7. Conclusion</A
+></H2
 ><P
->	When the user logs out, if the profile is set to be a roaming profile it will be written
-	out to the location of the profile. The <TT
-CLASS="FILENAME"
->NTuser.DAT</TT
-> file is then
-	re-created from the contents of the <TT
-CLASS="FILENAME"
->HKEY_CURRENT_USER</TT
-> contents.
-	Thus, should there not exist in the NETLOGON share an <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> at the
-	next logon, the effect of the provious <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> will still be held
-	in the profile. The effect of this is known as <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->tatooing</I
-></SPAN
->.
-	</P
-></LI
-></OL
+>The winbind system, through the use of the Name Service 
+	Switch, Pluggable Authentication Modules, and appropriate 
+	Microsoft RPC calls have allowed us to provide seamless 
+	integration of Microsoft Windows NT domain users on a
+	UNIX system. The result is a great reduction in the administrative 
+	cost of running a mixed UNIX and NT network.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="ADVANCEDNETWORKMANAGEMENT"
+></A
+>Chapter 16. Advanced Network Manangement</H1
 ><P
->MS Windows NT4 profiles may be <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Local</I
-></SPAN
-> or <SPAN
+>This section attempts to document peripheral issues that are of great importance to network
+administrators who want to improve network resource access control, to automate the user
+environment, and to make their lives a little easier.</P
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2870"
+>16.1. Configuring Samba Share Access Controls</A
+></H2
+><P
+>This section deals with how to configure Samba per share access control restrictions.
+By default samba sets no restrictions on the share itself. Restrictions on the share itself
+can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
+connect to a share. In the absence of specific restrictions the default setting is to allow
+the global user <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->Roaming</I
+>Everyone</I
 ></SPAN
->. A Local profile
-will stored in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
-> location. A roaming profile will
-also remain stored in the same way, unless the following registry key is created:</P
+> Full Control (ie: Full control, Change and Read).</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001</PRE
->
-
-In which case, the local copy (in <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->) will be
-deleted on logout.</P
+>At this time Samba does NOT provide a tool for configuring access control setting on the Share
+itself. Samba does have the capacity to store and act on access control settings, but  the only
+way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
+Computer Management.</P
 ><P
->Under MS Windows NT4 default locations for common resources (like <TT
+>Samba stores the per share access control settings in a file called <TT
 CLASS="FILENAME"
->My Documents</TT
->
-may be redirected to a network share by modifying the following registry keys. These changes may be affected
-via use of the System Policy Editor (to do so may require that you create your owns template extension
-for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
-creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P
-><P
->The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows NT4 is:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->        HKEY_CURRENT_USER
-                \Software
-                        \Microsoft
-                                \Windows
-                                        \CurrentVersion
-                                                \Explorer
-                                                        \User Shell Folders\</PRE
-></P
-><P
->The above hive key contains a list of automatically managed folders. The default entries are:</P
-><P
->        <PRE
-CLASS="PROGRAMLISTING"
->        Name            Default Value
-        --------------  -----------------------------------------
-        AppData         %USERPROFILE%\Application Data
-        Desktop         %USERPROFILE%\Desktop
-        Favorites       %USERPROFILE%\Favorites
-        NetHood         %USERPROFILE%\NetHood
-        PrintHood       %USERPROFILE%\PrintHood
-        Programs        %USERPROFILE%\Start Menu\Programs
-        Recent          %USERPROFILE%\Recent
-        SendTo          %USERPROFILE%\SendTo
-        Start Menu      %USERPROFILE%\Start Menu
-        Startup         %USERPROFILE%\Start Menu\Programs\Startup
-        </PRE
->
-        </P
-><P
->The registry key that contains the location of the default profile settings is:
-
-<PRE
-CLASS="PROGRAMLISTING"
->	HKEY_LOCAL_MACHINE
-		\SOFTWARE
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders</PRE
->
-
-The default entries are:
-
-<PRE
-CLASS="PROGRAMLISTING"
->	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
-	Common Programs		%SystemRoot%\Profiles\All Users\Programs
-	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
-	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE
-></P
-></DIV
+>share_info.tdb</TT
+>.
+The location of this file on your system will depend on how samba was compiled. The default location
+for samba's tdb files is under <TT
+CLASS="FILENAME"
+>/usr/local/samba/var</TT
+>. If the <TT
+CLASS="FILENAME"
+>tdbdump</TT
+>
+utility has been compiled and installed on your system then you can examine the contents of this file
+by: <KBD
+CLASS="USERINPUT"
+>tdbdump share_info.tdb</KBD
+>.</P
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3325"
->17.4.3. MS Windows 200x/XP</A
+NAME="AEN2880"
+>16.1.1. Share Permissions Management</A
 ></H3
+><P
+>The best tool for the task is platform dependant. Choose the best tool for your environmemt.</P
 ><DIV
-CLASS="NOTE"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2883"
+>16.1.1.1. Windows NT4 Workstation/Server</A
+></H4
 ><P
+>The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
+Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
+You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.</P
+><DIV
+CLASS="PROCEDURE"
+><P
+><B
+>Instructions</B
 ></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"
+><OL
+TYPE="1"
+><LI
 ><P
->	MS Windows XP Home Edition does use default per user profiles, but can not participate
-	in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
-	only from itself. While there are benefits in doing this the beauty of those MS Windows
-	clients that CAN participate in domain logon processes allows the administrator to create
-	a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
-	</P
-></TD
-></TR
-></TABLE
+>Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
+select Computer, then click on the Shared Directories entry.</P
+></LI
+><LI
+><P
+>	Now click on the share that you wish to manage, then click on the Properties tab, next click on
+	the Permissions tab. Now you can Add or change access control settings as you wish.</P
+></LI
+></OL
+></DIV
 ></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2892"
+>16.1.1.2. Windows 200x/XP</A
+></H4
 ><P
->When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
-<TT
-CLASS="FILENAME"
->C:\Documents and Settings\Default User</TT
->. The administrator can modify (or change
-the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
-arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
-workstation. </P
+>On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
+tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
+then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Everyone</I
+></SPAN
+> Full Control on the Share.</P
 ><P
->When MS Windows 200x/XP participate in a domain security context, and if the default user
-profile is not found, then the client will search for a default profile in the NETLOGON share
-of the authenticating server. ie: In MS Windows parlance:
-<TT
-CLASS="FILENAME"
->%LOGONSERVER%\NETLOGON\Default User</TT
-> and if one exits there it will copy this
-to the workstation to the <TT
+>MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
+Microsoft Management Console (MMC). This tool is located by clicking on <TT
 CLASS="FILENAME"
->C:\Documents and Settings\</TT
-> under the Windows
-login name of the user.</P
+>Control Panel -&#62;
+Administrative Tools -&#62; Computer Management</TT
+>.</P
 ><DIV
-CLASS="NOTE"
+CLASS="PROCEDURE"
+><P
+><B
+>Instructions</B
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>	After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
+	select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
+	to enter a domain login user identifier and a password. This will authenticate you to the domain.
+	If you where already logged in with administrative privilidge this step is not offered.</P
+></LI
+><LI
+><P
+>If the Samba server is not shown in the Select Computer box, then type in the name of the target
+Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
+next to 'Shared Folders' in the left panel.</P
+></LI
+><LI
+><P
+>Now in the right panel, double-click on the share you wish to set access control permissions on.
+Then click on the tab 'Share Permissions'. It is now possible to add access control entities
+to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
+wish to assign for each entry.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="WARNING"
 ><P
 ></P
 ><TABLE
-CLASS="NOTE"
+CLASS="WARNING"
 WIDTH="100%"
 BORDER="0"
 ><TR
@@ -16640,383 +13397,551 @@ WIDTH="25"
 ALIGN="CENTER"
 VALIGN="TOP"
 ><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
 HSPACE="5"
-ALT="Note"></TD
+ALT="Warning"></TD
 ><TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->	This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
-	should be created at the root of this share and msut be called <TT
-CLASS="FILENAME"
->Default Profile</TT
->.
-	</P
+>Be careful. If you take away all permissions from the Everyone user without removing this user
+then effectively no user will be able to access the share. This is a result of what is known as
+ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
+will have no access even if this user is given explicit full control access.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2908"
+>16.2. Remote Server Administration</A
+></H2
 ><P
->If a default profile does not exist in this location then MS Windows 200x/XP will use the local
-default profile.</P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How do I get 'User Manager' and 'Server Manager'?</I
+></SPAN
+></P
 ><P
->On loging out, the users' desktop profile will be stored to the location specified in the registry
-settings that pertain to the user. If no specific policies have been created, or passed to the client
-during the login process (as Samba does automatically), then the user's profile will be written to
-the local machine only under the path <TT
-CLASS="FILENAME"
->C:\Documents and Settings\%USERNAME%</TT
->.</P
+>Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
+the 'Server Manager'?</P
 ><P
->Those wishing to modify the default behaviour can do so through up to three methods:</P
+>Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
+systems.  The tools set includes:</P
 ><P
 ></P
 ><UL
 ><LI
 ><P
->	Modify the registry keys on the local machine manually and place the new default profile in the
-	NETLOGON share root - NOT recommended as it is maintenance intensive.
-	</P
+>Server Manager</P
 ></LI
 ><LI
 ><P
->	Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
-	in the root of the NETLOGON share along with the new default profile.
-	</P
+>User Manager for Domains</P
 ></LI
 ><LI
 ><P
->	Create a GPO that enforces this through Active Directory, and place the new default profile
-	in the NETLOGON share.
-	</P
+>Event Viewer</P
 ></LI
 ></UL
 ><P
->The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows 200x/XP is:</P
+>Click here to download the archived file <A
+HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
+TARGET="_top"
+>ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
+></P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	HKEY_CURRENT_USER
-		\Software
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders\</PRE
+>The Windows NT 4.0 version of the 'User Manager for 
+Domains' and 'Server Manager' are available from Microsoft via ftp 
+from <A
+HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
+TARGET="_top"
+>ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
 ></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2925"
+>16.3. Network Logon Script Magic</A
+></H2
 ><P
->The above hive key contains a list of automatically managed folders. The default entries are:</P
+>This section needs work. Volunteer contributions most welcome. Please send your patches or updates
+to <A
+HREF="mailto:jht@samba.org"
+TARGET="_top"
+>John Terpstra</A
+>.</P
 ><P
->	<PRE
-CLASS="PROGRAMLISTING"
->	Name		Default Value
-	--------------	-----------------------------------------
-	AppData		%USERPROFILE%\Application Data
-	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
-	Cookies		%USERPROFILE%\Cookies
-	Desktop		%USERPROFILE%\Desktop
-	Favorites	%USERPROFILE%\Favorites
-	History		%USERPROFILE%\Local Settings\History
-	Local AppData	%USERPROFILE%\Local Settings\Application Data
-	Local Settings	%USERPROFILE%\Local Settings
-	My Pictures	%USERPROFILE%\My Documents\My Pictures
-	NetHood		%USERPROFILE%\NetHood
-	Personal	%USERPROFILE%\My Documents
-	PrintHood	%USERPROFILE%\PrintHood
-	Programs	%USERPROFILE%\Start Menu\Programs
-	Recent		%USERPROFILE%\Recent
-	SendTo		%USERPROFILE%\SendTo
-	Start Menu	%USERPROFILE%\Start Menu
-	Startup		%USERPROFILE%\Start Menu\Programs\Startup
-	Templates	%USERPROFILE%\Templates
-	</PRE
->
-	</P
+>There are several opportunities for creating a custom network startup configuration environment.</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>No Logon Script</TD
+></TR
+><TR
+><TD
+>Simple universal Logon Script that applies to all users</TD
+></TR
+><TR
+><TD
+>Use of a conditional Logon Script that applies per user or per group attirbutes</TD
+></TR
+><TR
+><TD
+>Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
+	a custom Logon Script and then execute it.</TD
+></TR
+><TR
+><TD
+>User of a tool such as KixStart</TD
+></TR
+></TBODY
+></TABLE
 ><P
->There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
-the others are of type REG_EXPAND_SZ.</P
+></P
 ><P
->It makes a huge difference to the speed of handling roaming user profiles if all the folders are
-stored on a dedicated location on a network server. This means that it will NOT be necessary to
-write Outlook PST file over the network for every login and logout.</P
+>The Samba source code tree includes two logon script generation/execution tools. See <TT
+CLASS="FILENAME"
+>examples</TT
+> directory <TT
+CLASS="FILENAME"
+>genlogon</TT
+> and <TT
+CLASS="FILENAME"
+>ntlogon</TT
+> subdirectories.</P
 ><P
->To set this to a network location you could use the following examples:
+>The following listings are from the genlogon directory.</P
+><P
+>This is the genlogon.pl file:
 
 <PRE
 CLASS="PROGRAMLISTING"
->	%LOGONSERVER%\%USERNAME%\Default Folders</PRE
->
+>	#!/usr/bin/perl
+	#
+	# genlogon.pl
+	#
+	# Perl script to generate user logon scripts on the fly, when users
+	# connect from a Windows client.  This script should be called from smb.conf
+	# with the %U, %G and %L parameters. I.e:
+	#
+	#       root preexec = genlogon.pl %U %G %L
+	#
+	# The script generated will perform
+	# the following:
+	#
+	# 1. Log the user connection to /var/log/samba/netlogon.log
+	# 2. Set the PC's time to the Linux server time (which is maintained
+	#    daily to the National Institute of Standard's Atomic clock on the
+	#    internet.
+	# 3. Connect the user's home drive to H: (H for Home).
+	# 4. Connect common drives that everyone uses.
+	# 5. Connect group-specific drives for certain user groups.
+	# 6. Connect user-specific drives for certain users.
+	# 7. Connect network printers.
 
-This would store the folders in the user's home directory under a directory called "Default Folders"
+	# Log client connection
+	#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	open LOG, "&#62;&#62;/var/log/samba/netlogon.log";
+	print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
+	close LOG;
 
-You could also use:
+	# Start generating logon script
+	open LOGON, "&#62;/shared/netlogon/$ARGV[0].bat";
+	print LOGON "\@ECHO OFF\r\n";
 
-<PRE
-CLASS="PROGRAMLISTING"
->	\\SambaServer\FolderShare\%USERNAME%</PRE
->
+	# Connect shares just use by Software Development group
+	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
+	{
+		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
+	}
 
-in which case the default folders will be stored in the server named <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->SambaServer</I
-></SPAN
->
-in the share called <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->FolderShare</I
-></SPAN
-> under a directory that has the name of the MS Windows
-user as seen by the Linux/Unix file system.</P
+	# Connect shares just use by Technical Support staff
+	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
+	{
+		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
+	}
+
+	# Connect shares just used by Administration staff
+	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
+	{
+		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
+		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
+	}
+
+	# Now connect Printers.  We handle just two or three users a little
+	# differently, because they are the exceptions that have desktop
+	# printers on LPT1: - all other user's go to the LaserJet on the
+	# server.
+	if ($ARGV[0] eq 'jim'
+	    || $ARGV[0] eq 'yvonne')
+	{
+		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+	else
+	{
+		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+
+	# All done! Close the output file.
+	close LOGON;</PRE
+></P
 ><P
->Please note that once you have created a default profile share, you MUST migrate a user's profile
-(default or custom) to it.</P
+>Those wishing to use more elaborate or capable logon processing system should check out the following sites:</P
 ><P
->MS Windows 200x/XP profiles may be <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Local</I
-></SPAN
-> or <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Roaming</I
-></SPAN
->.
-A roaming profile will be cached locally unless the following registry key is created:</P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>http://www.craigelachie.org/rhacer/ntlogon</TD
+></TR
+><TR
+><TD
+>http://www.kixtart.org</TD
+></TR
+></TBODY
+></TABLE
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001</PRE
->
-
-In which case, the local cache copy will be deleted on logout.</P
-></DIV
+></P
 ></DIV
 ></DIV
 ><DIV
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="INTERDOMAINTRUSTS"
+NAME="POLICYMGMT"
 ></A
->Chapter 18. Interdomain Trust Relationships</H1
-><P
->Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
-will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
-adopt Active Directory or an LDAP based authentication back end. This section explains
-some background information regarding trust relationships and how to create them. It is now
-possible for Samba3 to NT4 trust (and vica versa), as well as Samba3 to Samba3 trusts.</P
+>Chapter 17. System and Account Policies</H1
 ><DIV
 CLASS="SECT1"
-><HR><H2
+><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3386"
->18.1. Trust Relationship Background</A
+NAME="AEN2959"
+>17.1. Creating and Managing System Policies</A
 ></H2
 ><P
->MS Windows NT3.x/4.0 type security domains employ a non-hierchical security structure.
-The limitations of this architecture as it affects the scalability of MS Windows networking
-in large organisations is well known. Additionally, the flat-name space that results from
-this design significantly impacts the delegation of administrative responsibilities in
-large and diverse organisations.</P
+>Under MS Windows platforms, particularly those following the release of MS Windows
+NT4 and MS Windows 95) it is possible to create a type of file that would be placed
+in the NETLOGON share of a domain controller. As the client logs onto the network
+this file is read and the contents initiate changes to the registry of the client
+machine. This file allows changes to be made to those parts of the registry that
+affect users, groups of users, or machines.</P
 ><P
->Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
-of circumventing the limitations of the older technologies. Not every organisation is ready
-or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
-is quite adequate, there thus remains an entrenched user base for whom there is no direct
-desire to go through a disruptive change to adopt ADS.</P
+>For MS Windows 9x/Me this file must be called <TT
+CLASS="FILENAME"
+>Config.POL</TT
+> and may
+be generated using a tool called <TT
+CLASS="FILENAME"
+>poledit.exe</TT
+>, better known as the
+Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
+dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
+comments from MS Windows network administrators it would appear that this tool became
+a part of the MS Windows Me Resource Kit.</P
 ><P
->Microsoft introduced with MS Windows NT the ability to allow differing security domains
-to affect a mechanism so that users from one domain may be given access rights and privilidges
-in another domain. The language that describes this capability is couched in terms of
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Trusts</I
-></SPAN
->. Specifically, one domain will <SPAN
+>MS Windows NT4 Server products include the <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->trust</I
+>System Policy Editor</I
 ></SPAN
-> the users
-from another domain. The domain from which users are available to another security domain is
-said to be a trusted domain. The domain in which those users have assigned rights and privilidges
-is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
-thus if users in both domains are to have privilidges and rights in each others' domain, then it is
-necessary to establish two (2) relationships, one in each direction.</P
+>
+under the <TT
+CLASS="FILENAME"
+>Start -&#62; Programs -&#62; Administrative Tools</TT
+> menu item.
+For MS Windows NT4 and later clients this file must be called <TT
+CLASS="FILENAME"
+>NTConfig.POL</TT
+>.</P
 ><P
->In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
-are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
-relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
-implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
-transitive.</P
+>New with the introduction of MS Windows 2000 was the Microsoft Management Console
+or MMC.  This tool is the new wave in the ever changing landscape of Microsoft
+methods for management of network access and security. Every new Microsoft product
+or technology seems to obsolete the old rules and to introduce newer and more
+complex tools and methods. To Microsoft's credit though, the MMC does appear to
+be a step forward, but improved functionality comes at a great price.</P
 ><P
->New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
-by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
-domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
-an inherent feature of ADS domains.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3395"
->18.2. MS Windows NT4 Trust Configuration</A
-></H2
+>Before embarking on the configuration of network and system policies it is highly
+advisable to read the documentation available from Microsoft's web site regarding
+<A
+HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp"
+TARGET="_top"
+>Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</A
+> available from Microsoft.
+There are a large number of documents in addition to this old one that should also
+be read and understood. Try searching on the Microsoft web site for "Group Policies".</P
 ><P
->There are two steps to creating an inter-domain trust relationship.&#13;</P
+>What follows is a very brief discussion with some helpful notes. The information provided
+here is incomplete - you are warned.</P
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3398"
->18.2.1. NT4 as the Trusting Domain</A
+NAME="AEN2973"
+>17.1.1. Windows 9x/Me Policies</A
 ></H3
 ><P
->For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
-To affect a two way trust relationship it is necessary for each domain administrator to make
-available (for use by an external domain) it's security resources. This is done from the Domain
-User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
-next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and
-"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that
-will be able to assign user rights to your domain. In addition it is necessary to enter a password
-that is specific to this trust relationship. The password is added twice.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3401"
->18.2.2. NT4 as the Trusted Domain</A
-></H3
+>You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
+It can be found on the Original full product Win98 installation CD under
+<TT
+CLASS="FILENAME"
+>tools/reskit/netadmin/poledit</TT
+>.  Install this using the
+Add/Remove Programs facility and then click on the 'Have Disk' tab.</P
 ><P
->A trust relationship will work only when the other (trusting) domain makes the appropriate connections
-with the trusted domain. To consumate the trust relationship the administrator will launch the
-Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
-"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in
-which must be entered the name of the remote domain as well as the password assigned to that trust.</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. 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 Win98 is configured to log onto
+the Samba Domain, it will automatically read this file and update the Win9x/Me registry
+of the machine as it logs on.</P
 ><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3405"
->18.3. Configuring Samba Domain Trusts</A
-></H2
+>Further details are covered in the Win98 Resource Kit documentation.</P
 ><P
->This descitpion is meant to be a fairly short introduction about how to set up a Samba server so
-that it could participate in interdomain trust relationships. Trust relationship support in Samba
-is in its early stage, so lot of things don't work yet. Paricularly, the contents of this document
-applies to NT4-style trusts.</P
+>If you do not take the right steps, then every so often Win9x/Me 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 Win9x/Me machine. Hence, you will
+occasionally notice things changing back to the original settings.</P
 ><P
->Each of the procedures described below is treated as they were performed with Windows NT4 Server on
-one end. The other end could just as well be another Samba3 domain. It can be clearly seen, after
-reading this document, that combining Samba-specific parts of what's written below leads to trust
-between domains in purely Samba environment.</P
+>Install the group policy handler for Win9x to pick up group policies. Look on the
+Win98 CD in <TT
+CLASS="FILENAME"
+>\tools\reskit\netadmin\poledit</TT
+>.
+Install group policies on a Win9x client by double-clicking
+<TT
+CLASS="FILENAME"
+>grouppol.inf</TT
+>. Log off and on again a couple of times and see
+if Win98 picks up group policies.  Unfortunately this needs to be done on every
+Win9x/Me machine that uses group policies.</P
+></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3409"
->18.3.1. Samba3 as the Trusting Domain</A
+NAME="AEN2985"
+>17.1.2. Windows NT4 Style Policy Files</A
 ></H3
 ><P
->In order to set Samba PDC to be trusted party of the relationship first you need
-to create special account for domain that will be the trusting party. To do that,
-you can use 'smbpasswd' utility. Creating the trusted domain account is very
-similiar to creating the connection to the trusting machine's account. Suppose,
-your domain is called SAMBA, and the remote domain is called RUMBA. Your first
-step will be to issue this command from your favourite shell:</P
+>To create or edit <TT
+CLASS="FILENAME"
+>ntconfig.pol</TT
+> you must use the NT Server
+Policy Editor, <B
+CLASS="COMMAND"
+>poledit.exe</B
+> which is included with NT4 Server
+but <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not NT Workstation</I
+></SPAN
+>. There is a Policy Editor on a NT4
+Workstation but it is not suitable for creating <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Domain Policies</I
+></SPAN
+>.
+Further, although the Windows 95 Policy Editor can be installed on an NT4
+Workstation/Server, it will not work with NT clients. However, the files from
+the NT Server will run happily enough on an NT4 Workstation.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	deity# smbpasswd -a -i rumba
-	New SMB password: XXXXXXXX
-	Retype SMB password: XXXXXXXX
-	Added user rumba$
-
-	where:
-		-a means to add a new account into the passdb database
-		-i means create this account with the Inter-Domain trust flag
-
-	The account name will be 'rumba$' (the name ofthe remote domain)</PRE
-></P
+>You need <TT
+CLASS="FILENAME"
+>poledit.exe, common.adm</TT
+> and <TT
+CLASS="FILENAME"
+>winnt.adm</TT
+>.
+It is convenient to put the two *.adm files in  the <TT
+CLASS="FILENAME"
+>c:\winnt\inf</TT
+> 
+directory which is where the binary will look for them unless told otherwise. Note also that that
+directory is normally 'hidden'.</P
 ><P
->fter issuing this command you'll be asked for typing account's
-password. You can use any password you want, but be aware that Windows NT will
-not change this password until 7 days have passed since account creating.
-After command returns successfully, you can look at your new account's entry
-(in the way depending on your configuration) and see that account's name is
-really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
-the trust by establishing it from Windows NT Server.</P
+>The Windows NT policy editor is also included with the Service Pack 3 (and
+later) for Windows NT 4.0. Extract the files using <B
+CLASS="COMMAND"
+>servicepackname /x</B
+>,
+i.e. that's <B
+CLASS="COMMAND"
+>Nt4sp6ai.exe /x</B
+> for service pack 6a.  The policy editor,
+<B
+CLASS="COMMAND"
+>poledit.exe</B
+> and the associated template files (*.adm) should
+be extracted as well.  It is also possible to downloaded the policy template
+files for Office97 and get a copy of the policy editor.  Another possible
+location is with the Zero Administration Kit available for download from Microsoft.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN3000"
+>17.1.2.1. Registry Tattoos</A
+></H4
 ><P
->Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
-Right beside 'Trusted domains' list press 'Add...' button. You'll be prompted for
-trusted domain name and the relationship's password. Type in SAMBA, as this is
-your domain name and the password you've just used during account creation.
-Press OK and if everything went fine, you will see 'Trusted domain relationship
-successfully established' message. Well done.</P
+>	With NT4 style registry based policy changes, a large number of settings are not
+	automatically reversed as the user logs off. Since the settings that were in the
+	NTConfig.POL file were applied to the client machine registry and that apply to the
+	hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
+	as tattooing. It can have serious consequences down-stream and the administrator must
+	be extremely careful not to lock out the ability to manage the machine at a later date.
+	</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3416"
->18.3.2. Samba3 as the Trusted Domain</A
+NAME="AEN3003"
+>17.1.3. MS Windows 200x / XP Professional Policies</A
 ></H3
 ><P
->This time activities are somewhat reversed. Again, we'll assume that your domain
-controlled by Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.</P
+>Windows NT4 System policies allows setting of registry parameters specific to
+users, groups and computers (client workstations) that are members of the NT4
+style domain. Such policy file will work with MS Windows 2000 / XP clients also.</P
 ><P
->The very first thing is to add account for SAMBA domain on RUMBA's PDC.</P
+>New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
+a superset of capabilities compared with NT4 style policies. Obviously, the tool used
+to create them is different, and the mechanism for implementing them is much changed.</P
 ><P
->Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
-Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
-domein (SAMBA) and password securing the relationship.</P
+>The older NT4 style registry based policies are known as <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Administrative Templates</I
+></SPAN
+>
+in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
+configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
+users' desktop (including: the location of <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>My Documents</I
+></SPAN
+> files (directory), as
+well as intrinsics of where menu items will appear in the Start menu). An additional new
+feature is the ability to make available particular software Windows applications to particular
+users and/or groups.</P
 ><P
->Password can be arbitrarily chosen the more, because it's easy to change it
-from Samba server whenever you want. After confirming password your account is
-ready and waiting. Now it's Samba's turn.</P
+>Remember: NT4 policy files are named <TT
+CLASS="FILENAME"
+>NTConfig.POL</TT
+> and are stored in the root
+of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
+and selects the domain name to which the logon will attempt to take place. During the logon
+process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
+server, modifies the local registry values according to the settings in this file.</P
 ><P
->Using your favourite shell while being logged on as root, issue this command:</P
+>Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
+a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
+in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
+Directory domain controllers. The part that is stored in the Active Directory itself is called the
+group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
+known as the group policy template (GPT).</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	deity#  net rpc trustdom establish rumba</PRE
+>With NT4 clients the policy file is read and executed upon only aas each user log onto the network.
+MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
+startup (machine specific part) and when the user logs onto the network the user specific part
+is applied. In MS Windows 200x style policy management each machine and/or user may be subject
+to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
+the administrator to also set filters over the policy settings. No such equivalent capability
+exists with NT4 style policy files.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN3014"
+>17.1.3.1. Administration of Win2K / XP Policies</A
+></H4
+><DIV
+CLASS="PROCEDURE"
+><P
+><B
+>Instructions</B
 ></P
 ><P
->You'll be prompted for password you've just typed on your Windows NT4 Server box.
-Don't worry if you will see the error message with returned code of
-<TT
+>Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the
+executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
+(MMC) snap-in as follows:</P
+><OL
+TYPE="1"
+><LI
+><P
+>Go to the Windows 200x / XP menu <TT
 CLASS="FILENAME"
->NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT</TT
->. It means the
-password you gave is correct and the NT4 Server says the account is ready for trusting your domain
-and not for ordinary connection. After that, be patient it can take a while (especially
-in large networks), you should see 'Success' message. Contgratulations! Your trust
-relationship has just been established.</P
+>Start-&#62;Programs-&#62;Administrative Tools</TT
+>
+	and select the MMC snap-in called "Active Directory Users and Computers"</P
+></LI
+><LI
+><P
+>Select the domain or organizational unit (OU) that you wish to manage, then right click
+to open the context menu for that object, select the properties item.</P
+></LI
+><LI
+><P
+>Now left click on the Group Policy tab, then left click on the New tab. Type a name
+for the new policy you will create.</P
+></LI
+><LI
+><P
+>Now left click on the Edit tab to commence the steps needed to create the GPO.</P
+></LI
+></OL
+></DIV
+><P
+>All policy configuration options are controlled through the use of policy administrative
+templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
+Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
+The later introduces many new features as well as extended definition capabilities. It is
+well beyond the scope of this documentation to explain how to program .adm files, for that
+the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
+version of MS Windows.</P
 ><DIV
 CLASS="NOTE"
 ><P
@@ -17038,262 +13963,327 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->Note that you have to run this command as root, since you need write access to
-your secrets.tdb file.</P
+>The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
+to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
+use this powerful tool. Please refer to the resource kit manuals for specific usage information.</P
 ></TD
 ></TR
 ></TABLE
-></DIV
-></DIV
-></DIV
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3031"
+>17.2. Managing Account/User Policies</A
+></H2
+><P
+>Policies can define a specific user's settings or the settings for a group of users. The resulting
+policy file contains the registry settings for all users, groups, and computers that will be using
+the policy file. Separate policy files for each user, group, or computer are not not necessary.</P
+><P
+>If you create a policy that will be automatically downloaded from validating domain controllers,
+you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
+policy file and, by modifying the Windows NT-based workstation, directing the computer to update
+the policy from a manual path. You can do this by either manually changing the registry or by using
+the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
+but if a change is necessary to all machines, this change must be made individually to each workstation.</P
+><P
+>When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain 
+controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
+applied to the user's part of the registry.</P
+><P
+>MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
+acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
+itself. The key benefit of using AS GPOs is that they impose no registry <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>tatooing</I
+></SPAN
+> effect.
+This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.</P
+><P
+>Inaddition to user access controls that may be imposed or applied via system and/or group policies
+in a manner that works in conjunction with user profiles, the user management environment under
+MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
+Common restrictions that are frequently used includes:</P
+><P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Logon Hours</TD
+></TR
+><TR
+><TD
+>Password Aging</TD
+></TR
+><TR
+><TD
+>Permitted Logon from certain machines only</TD
+></TR
+><TR
+><TD
+>Account type (Local or Global)</TD
+></TR
+><TR
+><TD
+>User Rights</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3046"
+>17.2.1. With Windows NT4/200x</A
+></H3
+><P
+>The tools that may be used to configure these types of controls from the MS Windows environment are:
+The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
+Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
+"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.</P
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="PAM"
-></A
->Chapter 19. PAM Configuration for Centrally Managed Authentication</H1
+NAME="AEN3049"
+>17.2.2. With a Samba PDC</A
+></H3
+><P
+>With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
+<TT
+CLASS="FILENAME"
+>smbpasswd, pdbedit, smbgroupedit, net, rpcclient.</TT
+>. The administrator should read the
+man pages for these tools and become familiar with their use.</P
+></DIV
+></DIV
 ><DIV
 CLASS="SECT1"
-><H2
+><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3440"
->19.1. Samba and PAM</A
+NAME="AEN3053"
+>17.3. System Startup and Logon Processing Overview</A
 ></H2
 ><P
->A number of Unix systems (eg: Sun Solaris), as well as the 
-xxxxBSD family and Linux, now utilize the Pluggable Authentication 
-Modules (PAM) facility to provide all authentication, 
-authorization and resource control services. Prior to the 
-introduction of PAM, a decision to use an alternative to 
-the system password database (<TT
-CLASS="FILENAME"
->/etc/passwd</TT
->) 
-would require the provision of alternatives for all programs that provide 
-security services. Such a choice would involve provision of 
-alternatives to such programs as: <B
-CLASS="COMMAND"
->login</B
->, 
-<B
-CLASS="COMMAND"
->passwd</B
->, <B
-CLASS="COMMAND"
->chown</B
->, etc.</P
+>The following attempts to document the order of processing of system and user policies following a system
+reboot and as part of the user logon:</P
 ><P
->PAM provides a mechanism that disconnects these security programs 
-from the underlying authentication/authorization infrastructure.
-PAM is configured either through one file <TT
-CLASS="FILENAME"
->/etc/pam.conf</TT
-> (Solaris), 
-or by editing individual files that are located in <TT
-CLASS="FILENAME"
->/etc/pam.d</TT
->.</P
-><DIV
-CLASS="NOTE"
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>	Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
+	Convention Provider (MUP) start
+	</P
+></LI
+><LI
 ><P
+>	Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
+	and applied. The list may include GPOs that:
+<P
 ></P
 ><TABLE
-CLASS="NOTE"
-WIDTH="100%"
 BORDER="0"
+><TBODY
 ><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
+>Apply to the location of machines in a Directory</TD
+></TR
+><TR
 ><TD
-ALIGN="LEFT"
-VALIGN="TOP"
+>Apply only when settings have changed</TD
+></TR
+><TR
+><TD
+>Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</TD
+></TR
+></TBODY
+></TABLE
 ><P
->	If the PAM authentication module (loadable link library file) is located in the
-	default location then it is not necessary to specify the path. In the case of
-	Linux, the default location is <TT
-CLASS="FILENAME"
->/lib/security</TT
->. If the module
-	is located other than default then the path may be specified as:
-	
-	<PRE
-CLASS="PROGRAMLISTING"
->	auth       required      /other_path/pam_strange_module.so
-	</PRE
+></P
 >
+	No desktop user interface is presented until the above have been processed.
 	</P
-></TD
-></TR
-></TABLE
-></DIV
+></LI
+><LI
 ><P
->The following is an example <TT
-CLASS="FILENAME"
->/etc/pam.d/login</TT
-> configuration file. 
-This example had all options been uncommented is probably not usable 
-as it stacks many conditions before allowing successful completion 
-of the login process. Essentially all conditions can be disabled 
-by commenting them out except the calls to <TT
-CLASS="FILENAME"
->pam_pwdb.so</TT
->.</P
+>	Execution of start-up scripts (hidden and synchronous by defaut).
+	</P
+></LI
+><LI
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	#%PAM-1.0
-	# The PAM configuration file for the `login' service
-	#
-	auth 		required	pam_securetty.so
-	auth 		required	pam_nologin.so
-	# auth 		required	pam_dialup.so
-	# auth 		optional	pam_mail.so
-	auth		required	pam_pwdb.so shadow md5
-	# account    	requisite  	pam_time.so
-	account		required	pam_pwdb.so
-	session		required	pam_pwdb.so
-	# session 	optional	pam_lastlog.so
-	# password   	required   	pam_cracklib.so retry=3
-	password	required	pam_pwdb.so shadow md5</PRE
-></P
+>	A keyboard action to affect start of logon (Ctrl-Alt-Del).
+	</P
+></LI
+><LI
 ><P
->PAM allows use of replacable modules. Those available on a 
-sample system include:</P
+>	User credentials are validated, User profile is loaded (depends on policy settings).
+	</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->$</SAMP
-><KBD
-CLASS="USERINPUT"
->/bin/ls /lib/security</KBD
->
-<PRE
-CLASS="PROGRAMLISTING"
->	pam_access.so    pam_ftp.so          pam_limits.so     
-	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
-	pam_cracklib.so  pam_group.so        pam_listfile.so   
-	pam_nologin.so   pam_rootok.so       pam_tally.so      
-	pam_deny.so      pam_issue.so        pam_mail.so       
-	pam_permit.so    pam_securetty.so    pam_time.so       
-	pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so  
-	pam_pwdb.so      pam_shells.so       pam_unix.so       
-	pam_env.so       pam_ldap.so         pam_motd.so       
-	pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
-	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
-	pam_userdb.so    pam_warn.so         pam_unix_session.so</PRE
+>	An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of:
+
+<P
 ></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Is user a domain member, thus subject to particular policies</TD
+></TR
+><TR
+><TD
+>Loopback enablement, and the state of the loopback policy (Merge or Replace)</TD
+></TR
+><TR
+><TD
+>Location of the Active Directory itself</TD
+></TR
+><TR
+><TD
+>Has the list of GPOs changed. No processing is needed if not changed.</TD
+></TR
+></TBODY
+></TABLE
 ><P
->The following example for the login program replaces the use of 
-the <TT
-CLASS="FILENAME"
->pam_pwdb.so</TT
-> module which uses the system 
-password database (<TT
-CLASS="FILENAME"
->/etc/passwd</TT
->,
-<TT
-CLASS="FILENAME"
->/etc/shadow</TT
->, <TT
-CLASS="FILENAME"
->/etc/group</TT
->) with 
-the module <TT
-CLASS="FILENAME"
->pam_smbpass.so</TT
-> which uses the Samba 
-database which contains the Microsoft MD4 encrypted password 
-hashes. This database is stored in either 
-<TT
-CLASS="FILENAME"
->/usr/local/samba/private/smbpasswd</TT
->, 
-<TT
-CLASS="FILENAME"
->/etc/samba/smbpasswd</TT
->, or in 
-<TT
-CLASS="FILENAME"
->/etc/samba.d/smbpasswd</TT
->, depending on the 
-Samba implementation for your Unix/Linux system. The 
-<TT
-CLASS="FILENAME"
->pam_smbpass.so</TT
-> module is provided by 
-Samba version 2.2.1 or later. It can be compiled by specifying the 
-<B
-CLASS="COMMAND"
->--with-pam_smbpass</B
-> options when running Samba's
-<TT
-CLASS="FILENAME"
->configure</TT
-> script.  For more information
-on the <TT
-CLASS="FILENAME"
->pam_smbpass</TT
-> module, see the documentation
-in the <TT
-CLASS="FILENAME"
->source/pam_smbpass</TT
-> directory of the Samba 
-source distribution.</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	#%PAM-1.0
-	# The PAM configuration file for the `login' service
-	#
-	auth		required	pam_smbpass.so nodelay
-	account		required	pam_smbpass.so nodelay
-	session		required	pam_smbpass.so nodelay
-	password	required	pam_smbpass.so nodelay</PRE
 ></P
+>
+	</P
+></LI
+><LI
 ><P
->The following is the PAM configuration file for a particular 
-Linux system. The default condition uses <TT
-CLASS="FILENAME"
->pam_pwdb.so</TT
->.</P
+>	User Policies are applied from Active Directory. Note: There are several types.
+	</P
+></LI
+><LI
+><P
+>	Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
+	Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
+	window.
+	</P
+></LI
+><LI
+><P
+>	The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4
+	Domain) machine (system) policies are applied at start-up, User policies are applied at logon.
+	</P
+></LI
+></OL
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PROFILEMGMT"
+></A
+>Chapter 18. Desktop Profile Management</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3096"
+>18.1. Roaming Profiles</A
+></H2
+><DIV
+CLASS="WARNING"
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	#%PAM-1.0
-	# The PAM configuration file for the `samba' service
-	#
-	auth       required     pam_pwdb.so nullok nodelay shadow audit
-	account    required     pam_pwdb.so audit nodelay
-	session    required     pam_pwdb.so nodelay
-	password   required     pam_pwdb.so shadow md5</PRE
 ></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
->In the following example the decision has been made to use the 
-smbpasswd database even for basic samba authentication. Such a 
-decision could also be made for the passwd program and would 
-thus allow the smbpasswd passwords to be changed using the passwd 
-program.</P
+>Roaming profiles support is different for Win9x / Me and Windows NT4/200x.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Before discussing how to configure roaming profiles, it is useful to see how
+Windows 9x / Me and Windows NT4/200x clients implement these features.</P
+><P
+>Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
+profiles location. However, the response does not have room for a separate
+profiles location field, only the user's home share. This means that Win9X/Me
+profiles are restricted to being stored in the user's home directory.</P
+><P
+>Windows NT4/200x  clients send a NetSAMLogon RPC request, which contains many fields,
+including a separate field for the location of the user's profiles.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3103"
+>18.1.1. Samba Configuration for Profile Handling</A
+></H3
+><P
+>This section documents how to configure Samba for MS Windows client profile support.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN3106"
+>18.1.1.1. NT4/200x User Profiles</A
+></H4
+><P
+>To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
+following (for example):</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->	#%PAM-1.0
-	# The PAM configuration file for the `samba' service
-	#
-	auth       required     pam_smbpass.so nodelay
-	account    required     pam_pwdb.so audit nodelay
-	session    required     pam_pwdb.so nodelay
-	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE
-></P
+>	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
+>
+
+	This is typically implemented like:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>		logon path = \\%L\Profiles\%u</PRE
+>
+where %L translates to the name of the Samba server and %u translates to the user name</P
+><P
+>The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. 
+The \\N%\%U service is created automatically by the [homes] service.  If you are using
+a samba server for the profiles, you _must_ make the share specified in the logon path
+browseable. Please refer to the man page for smb.conf in respect of the different
+symantics of %L and %N, as well as %U and %u.</P
 ><DIV
 CLASS="NOTE"
 ><P
@@ -17315,616 +14305,637 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->PAM allows stacking of authentication mechanisms. It is 
-also possible to pass information obtained within one PAM module through 
-to the next module in the PAM stack. Please refer to the documentation for 
-your particular system implementation for details regarding the specific 
-capabilities of PAM in this environment. Some Linux implmentations also 
-provide the <TT
-CLASS="FILENAME"
->pam_stack.so</TT
-> module that allows all 
-authentication to be configured in a single central file. The 
-<TT
-CLASS="FILENAME"
->pam_stack.so</TT
-> method has some very devoted followers 
-on the basis that it allows for easier administration. As with all issues in 
-life though, every decision makes trade-offs, so you may want examine the 
-PAM documentation for further helpful information.</P
+>MS Windows NT/2K clients at times do not disconnect a connection to a server
+between logons. It is recommended to NOT use the <B
+CLASS="COMMAND"
+>homes</B
+>
+meta-service name as part of the profile share path.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3491"
->19.2. Distributed Authentication</A
-></H2
+NAME="AEN3116"
+>18.1.1.2. Windows 9x / Me User Profiles</A
+></H4
 ><P
->The astute administrator will realize from this that the 
-combination of <TT
+>To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has
+now been fixed so that <KBD
+CLASS="USERINPUT"
+>net use /home</KBD
+> now works as well, and it, too, relies
+on the <B
+CLASS="COMMAND"
+>logon home</B
+> parameter.</P
+><P
+>By using the logon home parameter, you are restricted to putting Win9x / Me
+profiles in the user's home directory.   But wait! There is a trick you
+can use. If you set the following in the <B
+CLASS="COMMAND"
+>[global]</B
+> section of your <TT
 CLASS="FILENAME"
->pam_smbpass.so</TT
->, 
-<B
+>smb.conf</TT
+> file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	logon home = \\%L\%U\.profiles</PRE
+></P
+><P
+>then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
+of your home directory called <TT
+CLASS="FILENAME"
+>.profiles</TT
+> (thus making them hidden).</P
+><P
+>Not only that, but <KBD
+CLASS="USERINPUT"
+>net use/home</KBD
+> will also work, because of a feature in
+Windows 9x / Me. It removes any directory stuff off the end of the home directory area
+and only uses the server and share portion. That is, it looks like you
+specified \\%L\%U for <B
 CLASS="COMMAND"
->winbindd</B
->, and a distributed 
-passdb backend, such as ldap, will allow the establishment of a
-centrally managed, distributed 
-user/password database that can also be used by all 
-PAM (eg: Linux) aware programs and applications. This arrangement 
-can have particularly potent advantages compared with the 
-use of Microsoft Active Directory Service (ADS) in so far as 
-reduction of wide area network authentication traffic.</P
+>logon home</B
+>.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3496"
->19.3. PAM Configuration in smb.conf</A
-></H2
-><P
->There is an option in smb.conf called <A
-HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
-TARGET="_top"
->obey pam restrictions</A
->. 
-The following is from the on-line help for this option in SWAT;</P
+NAME="AEN3131"
+>18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
+></H4
 ><P
->When Samba is configured to enable PAM support (i.e. 
-<CODE
-CLASS="CONSTANT"
->--with-pam</CODE
->), this parameter will 
-control whether or not Samba should obey PAM's account 
-and session management directives. The default behavior 
-is to use PAM for clear text authentication only and to 
-ignore any account or session management. Note that Samba always 
-ignores PAM for authentication in the case of 
-<A
-HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
-TARGET="_top"
->encrypt passwords = yes</A
->. 
-The reason is that PAM modules cannot support the challenge/response 
-authentication mechanism needed in the presence of SMB 
-password encryption. </P
+>You can support profiles for both Win9X and WinNT clients by setting both the
+<B
+CLASS="COMMAND"
+>logon home</B
+> and <B
+CLASS="COMMAND"
+>logon path</B
+> parameters. For example:</P
 ><P
->Default: <B
-CLASS="COMMAND"
->obey pam restrictions = no</B
+><PRE
+CLASS="PROGRAMLISTING"
+>	logon home = \\%L\%u\.profiles
+	logon path = \\%L\profiles\%u</PRE
 ></P
 ></DIV
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="VFS"
-></A
->Chapter 20. Stackable VFS modules</H1
+NAME="AEN3138"
+>18.1.2. Windows Client Profile Configuration Information</A
+></H3
 ><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3531"
->20.1. Introduction and configuration</A
-></H2
+NAME="AEN3140"
+>18.1.2.1. Windows 9x / Me Profile Setup</A
+></H4
 ><P
->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
+>When a user first logs in on Windows 9X, the file user.DAT is created,
+as are folders "Start Menu", "Desktop", "Programs" and "Nethood".
+These directories and their contents will be merged with the local
+versions stored in c:\windows\profiles\username on subsequent logins,
+taking the most recent from each.  You will need to use the [global]
+options "preserve case = yes", "short preserve case = yes" and
+"case sensitive = no" in order to maintain capital letters in shortcuts
+in any of the profile folders.</P
 ><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
+>The user.DAT file contains all the user's preferences.  If you wish to
+enforce a set of preferences, rename their user.DAT file to user.MAN,
+and deny them write access to this file.</P
 ><P
->To use the VFS modules, create a share similar to the one below.  The
-important parameter is the <B
-CLASS="COMMAND"
->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"
->       [audit]
-                comment = Audited /data directory
-                path = /data
-                vfs object = /path/to/audit.so /path/to/recycle.so
-                writeable = yes
-                browseable = yes</PRE
 ></P
+><OL
+TYPE="1"
+><LI
 ><P
->The modules are used in the order they are specified.</P
+>        On the Windows 9x / Me machine, go to Control Panel -&#62; Passwords and
+        select the User Profiles tab.  Select the required level of
+        roaming preferences.  Press OK, but do _not_ allow the computer
+        to reboot.
+        </P
+></LI
+><LI
 ><P
->Further documentation on writing VFS modules for Samba can be found in
-the Samba Developers Guide.</P
+>        On the Windows 9x / Me machine, go to Control Panel -&#62; Network -&#62;
+        Client for Microsoft Networks -&#62; Preferences.  Select 'Log on to
+        NT Domain'.  Then, ensure that the Primary Logon is 'Client for
+        Microsoft Networks'.  Press OK, and this time allow the computer
+        to reboot.
+        </P
+></LI
+></OL
+><P
+>Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
+If you have the Primary Logon as 'Client for Novell Networks', then
+the profiles and logon script will be downloaded from your Novell
+Server.  If you have the Primary Logon as 'Windows Logon', then the
+profiles will be loaded from the local machine - a bit against the
+concept of roaming profiles, it would seem!</P
+><P
+>You will now find that the Microsoft Networks Login box contains
+[user, password, domain] instead of just [user, password].  Type in
+the samba server's domain name (or any other domain known to exist,
+but bear in mind that the user will be authenticated against this
+domain and profiles downloaded from it, if that domain logon server
+supports it), user name and user's password.</P
+><P
+>Once the user has been successfully validated, the Windows 9x / Me machine
+will inform you that 'The user has not logged on before' and asks you
+if you wish to save the user's preferences?  Select 'yes'.</P
+><P
+>Once the Windows 9x / Me client comes up with the desktop, you should be able
+to examine the contents of the directory specified in the "logon path"
+on the samba server and verify that the "Desktop", "Start Menu",
+"Programs" and "Nethood" folders have been created.</P
+><P
+>These folders will be cached locally on the client, and updated when
+the user logs off (if you haven't made them read-only by then).
+You will find that if the user creates further folders or short-cuts,
+that the client will merge the profile contents downloaded with the
+contents of the profile directory already on the local client, taking
+the newest folders and short-cuts from each set.</P
+><P
+>If you have made the folders / files read-only on the samba server,
+then you will get errors from the Windows 9x / Me machine on logon and logout, as
+it attempts to merge the local and the remote profile.  Basically, if
+you have any errors reported by the Windows 9x / Me machine, check the Unix file
+permissions and ownership rights on the profile directory contents,
+on the samba server.</P
+><P
+>If you have problems creating user profiles, you can reset the user's
+local desktop cache, as shown below.  When this user then next logs in,
+they will be told that they are logging in "for the first time".</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>        instead of logging in under the [user, password, domain] dialog,
+        press escape.
+        </P
+></LI
+><LI
+><P
+>        run the regedit.exe program, and look in:
+        </P
+><P
+>        HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
+        </P
+><P
+>        you will find an entry, for each user, of ProfilePath.  Note the
+        contents of this key (likely to be c:\windows\profiles\username),
+        then delete the key ProfilePath for the required user.
+
+        [Exit the registry editor].
+
+        </P
+></LI
+><LI
+><P
+>        <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING</I
+></SPAN
+> - before deleting the contents of the
+        directory listed in the ProfilePath (this is likely to be
+	<TT
+CLASS="FILENAME"
+>c:\windows\profiles\username)</TT
+>, ask them if they
+	have any important files stored on their desktop or in their start menu. 
+	Delete the contents of the directory ProfilePath (making a backup if any
+	of the files are needed).
+        </P
+><P
+>	This will have the effect of removing the local (read-only hidden
+	system file) user.DAT in their profile directory, as well as the
+	local "desktop", "nethood", "start menu" and "programs" folders.
+        </P
+></LI
+><LI
+><P
+>        search for the user's .PWL password-caching file in the c:\windows
+        directory, and delete it.
+        </P
+></LI
+><LI
+><P
+>        log off the windows 9x / Me client.
+        </P
+></LI
+><LI
+><P
+>        check the contents of the profile path (see "logon path" described
+        above), and delete the user.DAT or user.MAN file for the user,
+        making a backup if required.
+        </P
+></LI
+></OL
+><P
+>If all else fails, increase samba's debug log levels to between 3 and 10,
+and / or run a packet trace program such as ethereal or netmon.exe, and
+look for error messages.</P
+><P
+>If you have access to an Windows NT4/200x server, then first set up roaming profiles
+and / or netlogons on the Windows NT4/200x server.  Make a packet trace, or examine
+the example packet traces provided with Windows NT4/200x server, and see what the
+differences are with the equivalent samba trace.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3540"
->20.2. Included modules</A
-></H2
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3542"
->20.2.1. audit</A
-></H3
+NAME="AEN3176"
+>18.1.2.2. Windows NT4 Workstation</A
+></H4
 ><P
->A simple module to audit file access to the syslog
-facility.  The following operations are logged:
-<P
-></P
-><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
+>When a user first logs in to a Windows NT Workstation, the profile
+NTuser.DAT is created.  The profile location can be now specified
+through the "logon path" parameter.</P
+><P
+>There is a parameter that is now available for use with NT Profiles:
+"logon drive".  This should be set to <TT
+CLASS="FILENAME"
+>H:</TT
+> or any other drive, and
+should be used in conjunction with the new "logon home" parameter.</P
+><P
+>The entry for the NT4 profile is a _directory_ not a file.  The NT
+help on profiles mentions that a directory is also created with a .PDS
+extension.  The user, while logging in, must have write permission to
+create the full profile path (and the folder with the .PDS extension
+for those situations where it might be created.)</P
+><P
+>In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. 
+It creates "Application Data" and others, as well as "Desktop", "Nethood",
+"Start Menu" and "Programs".  The profile itself is stored in a file
+NTuser.DAT.  Nothing appears to be stored in the .PDS directory, and
+its purpose is currently unknown.</P
 ><P
-></P
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3550"
->20.2.2. extd_audit</A
-></H3
+>You can use the System Control Panel to copy a local profile onto
+a samba server (see NT Help on profiles: it is also capable of firing
+up the correct location in the System Control Panel for you).  The
+NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
+turns a profile into a mandatory one.</P
 ><P
->This module is identical with the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->audit</I
-></SPAN
-> module above except
-that it sends audit logs to both syslog as well as the smbd log file/s. The 
-loglevel for this module is set in the smb.conf file. At loglevel = 0, only file
-and directory deletions and directory and file creations are logged. At loglevel = 1
-file opens are renames and permission changes are logged , while at loglevel = 2 file
-open and close calls are logged also.</P
+>The case of the profile is significant.  The file must be called
+NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3554"
->20.2.3. recycle</A
-></H3
+NAME="AEN3185"
+>18.1.2.3. Windows 2000/XP Professional</A
+></H4
 ><P
->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
+>You must first convert the profile from a local profile to a domain
+profile on the MS Windows workstation as follows:</P
 ><P
->Supported options:
-<P
 ></P
-><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
->vfs_recycle_bin:repository</DT
-><DD
+><UL
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:keeptree</DT
-><DD
+>	Log on as the LOCAL workstation administrator.
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:versions</DT
-><DD
+>	Right click on the 'My Computer' Icon, select 'Properties'
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:touch</DT
-><DD
+>	Click on the 'User Profiles' tab
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:maxsize</DT
-><DD
+>	Select the profile you wish to convert (click on it once)
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:exclude</DT
-><DD
+>	Click on the button 'Copy To'
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:exclude_dir</DT
-><DD
+>	In the "Permitted to use" box, click on the 'Change' button.
+	</P
+></LI
+><LI
 ><P
->FIXME</P
-></DD
-><DT
->vfs_recycle_bin:noversions</DT
-><DD
+>	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
->FIXME</P
-></DD
-></DL
-></DIV
 ></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
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3591"
->20.2.4. netatalk</A
-></H3
+></LI
+><LI
 ><P
->A netatalk module, that will ease co-existence of samba and
-netatalk file sharing services.</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
+<TT
+CLASS="FILENAME"
+>profiles</TT
+> tool.</P
+><DIV
+CLASS="NOTE"
 ><P
->Advantages compared to the old netatalk module:
-<P
 ></P
 ><TABLE
+CLASS="NOTE"
+WIDTH="100%"
 BORDER="0"
-><TBODY
 ><TR
 ><TD
->it doesn't care about creating of .AppleDouble forks, just keeps ones in sync</TD
-></TR
-><TR
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
 ><TD
->if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</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
-></TBODY
 ></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
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3598"
->20.3. VFS modules available elsewhere</A
-></H2
+><UL
+><LI
 ><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
+>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
->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="AEN3602"
->20.3.1. DatabaseFS</A
-></H3
+>"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
->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
+>On the XP workstation log in with an Administrator account.</P
+></LI
+><LI
 ><P
->By <A
-HREF="mailto:elorimer@css.tayloru.edu"
-TARGET="_top"
->Eric Lorimer</A
->.</P
+>Click: "Start", "Run"</P
+></LI
+><LI
 ><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
+>Type: "mmc"</P
+></LI
+><LI
 ><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="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3610"
->20.3.2. vscan</A
-></H3
+>Click: "OK"</P
+></LI
+><LI
 ><P
->URL: <A
-HREF="http://www.openantivirus.org/"
-TARGET="_top"
->http://www.openantivirus.org/</A
-></P
+>A Microsoft Management Console should appear.</P
+></LI
+><LI
 ><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
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="MSDFS"
-></A
->Chapter 21. Hosting a Microsoft Distributed File System tree on Samba</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN3626"
->21.1. Instructions</A
-></H2
+>Click: File, "Add/Remove Snap-in...", "Add"</P
+></LI
+><LI
 ><P
->The Distributed File System (or Dfs) provides a means of 
-	separating the logical view of files and directories that users 
-	see from the actual physical locations of these resources on the 
-	network. It allows for higher availability, smoother storage expansion, 
-	load balancing etc. For more information about Dfs, refer to  <A
-HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
-TARGET="_top"
->	Microsoft documentation</A
->. </P
+>Double-Click: "Group Policy"</P
+></LI
+><LI
 ><P
->This document explains how to host a Dfs tree on a Unix 
-	machine (for Dfs-aware clients to browse) using Samba.</P
+>Click: "Finish", "Close"</P
+></LI
+><LI
 ><P
->To enable SMB-based DFS for Samba, configure it with the 
-	<VAR
-CLASS="PARAMETER"
->--with-msdfs</VAR
-> option. Once built, a 
-	Samba server can be made a Dfs server by setting the global 
-	boolean <A
-HREF="smb.conf.5.html#HOSTMSDFS"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->	host msdfs</VAR
-></A
-> parameter in the <TT
-CLASS="FILENAME"
->smb.conf
-	</TT
-> file. You designate a share as a Dfs root using the share 
-	level boolean <A
-HREF="smb.conf.5.html#MSDFSROOT"
-TARGET="_top"
-><VAR
-CLASS="PARAMETER"
->	msdfs root</VAR
-></A
-> parameter. A Dfs root directory on 
-	Samba hosts Dfs links in the form of symbolic links that point 
-	to other servers. For example, a symbolic link
-	<TT
-CLASS="FILENAME"
->junction-&#62;msdfs:storage1\share1</TT
-> in 
-	the share directory acts as the Dfs junction. When Dfs-aware 
-	clients attempt to access the junction link, they are redirected 
-	to the storage location (in this case, \\storage1\share1).</P
+>Click: "OK"</P
+></LI
+><LI
 ><P
->Dfs trees on Samba work with all Dfs-aware clients ranging 
-	from Windows 95 to 2000.</P
+>In the "Console Root" window:</P
+></LI
+><LI
 ><P
->Here's an example of setting up a Dfs tree on a Samba 
-	server.</P
+>Expand: "Local Computer Policy", "Computer Configuration",</P
+></LI
+><LI
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
-># The smb.conf file:
-[global]
-	netbios name = SAMBA
-	host msdfs   = yes
-
-[dfs]
-	path = /export/dfsroot
-	msdfs root = yes
-	</PRE
-></P
+>"Administrative Templates", "System", "User Profiles"</P
+></LI
+><LI
 ><P
->In the /export/dfsroot directory we set up our dfs links to 
-	other servers on the network.</P
+>Double-Click: "Do not check for user ownership of Roaming Profile</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->cd /export/dfsroot</KBD
-></P
+>Folders"</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->chown root /export/dfsroot</KBD
-></P
+>Select: "Enabled"</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->chmod 755 /export/dfsroot</KBD
-></P
+>Click: OK"</P
+></LI
+><LI
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->ln -s msdfs:storageA\\shareA linka</KBD
-></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
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->ln -s msdfs:serverB\\share,serverC\\share linkb</KBD
-></P
+>Reboot</P
+></LI
+></UL
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3258"
+>18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
+></H3
 ><P
->You should set up the permissions and ownership of 
-	the directory acting as the Dfs root such that only designated 
-	users can create, delete or modify the msdfs links. Also note 
-	that symlink names should be all lowercase. This limitation exists 
-	to have Samba avoid trying all the case combinations to get at 
-	the link name. Finally set up the symbolic links to point to the 
-	network shares you want, and start Samba.</P
+>Sharing of desktop profiles between Windows versions is NOT recommended.
+Desktop profiles are an evolving phenomenon and profiles for later versions
+of MS Windows clients add features that may interfere with earlier versions
+of MS Windows clients. Probably the more salient reason to NOT mix profiles
+is that when logging off an earlier version of MS Windows the older format
+of profile contents may overwrite information that belongs to the newer
+version resulting in loss of profile information content when that user logs
+on again with the newer version of MS Windows.</P
 ><P
->Users on Dfs-aware clients can now browse the Dfs tree 
-	on the Samba server at \\samba\dfs. Accessing 
-	links linka or linkb (which appear as directories to the client) 
-	takes users directly to the appropriate shares on the network.</P
+>If you then want to share the same Start Menu / Desktop with W9x/Me, you will
+need to specify a common location for the profiles. The smb.conf parameters
+that need to be common are <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>logon path</I
+></SPAN
+> and
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>logon home</I
+></SPAN
+>.</P
+><P
+>If you have this set up correctly, you will find separate user.DAT and
+NTuser.DAT files in the same profile directory.</P
+></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3661"
->21.1.1. Notes</A
+NAME="AEN3265"
+>18.1.4. Profile Migration from Windows NT4/200x Server to Samba</A
 ></H3
 ><P
-></P
-><UL
-><LI
-><P
->Windows clients need to be rebooted 
-			if a previously mounted non-dfs share is made a dfs 
-			root or vice versa. A better way is to introduce a 
-			new share and make it the dfs root.</P
-></LI
-><LI
-><P
->Currently there's a restriction that msdfs 
-			symlink names should all be lowercase.</P
-></LI
-><LI
-><P
->For security purposes, the directory 
-			acting as the root of the Dfs tree should have ownership 
-			and permissions set so that only designated users can 
-			modify the symbolic links in the directory.</P
-></LI
-></UL
-></DIV
-></DIV
-></DIV
+>There is nothing to stop you specifying any path that you like for the
+location of users' profiles.  Therefore, you could specify that the
+profile be stored on a samba server, or any other SMB server, as long as
+that SMB server supports encrypted passwords.</P
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="INTEGRATE-MS-NETWORKS"
-></A
->Chapter 22. Integrating MS Windows networks with Samba</H1
+NAME="AEN3268"
+>18.1.4.1. Windows NT4 Profile Management Tools</A
+></H4
 ><P
->This section deals with NetBIOS over TCP/IP name to IP address resolution. If you
-your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
-section does not apply to your installation. If your installation involves use of
-NetBIOS over TCP/IP then this section may help you to resolve networking problems.</P
-><DIV
-CLASS="NOTE"
+>Unfortunately, the Resource Kit information is specific to the version of MS Windows
+NT4/200x. The correct resource kit is required for each platform.</P
+><P
+>Here is a quick guide:</P
 ><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"
+><UL
+><LI
 ><P
->	NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
-	over Logical Link Control (LLC). On modern networks it is highly advised
-	to NOT run NetBEUI at all. Note also that there is NO such thing as
-	NetBEUI over TCP/IP - the existence of such a protocol is a complete
-	and utter mis-apprehension.</P
-></TD
-></TR
-></TABLE
-></DIV
+>On your NT4 Domain Controller, right click on 'My Computer', then
+select the tab labelled 'User Profiles'.</P
+></LI
+><LI
 ><P
->Since the introduction of MS Windows 2000 it is possible to run MS Windows networking
-without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
-name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
-TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be
-used and UDP port 137 and TCP port 139 will not.</P
+>Select a user profile you want to migrate and click on it.</P
 ><DIV
 CLASS="NOTE"
 ><P
 ></P
 ><TABLE
 CLASS="NOTE"
-WIDTH="100%"
+WIDTH="90%"
 BORDER="0"
 ><TR
 ><TD
@@ -17939,650 +14950,556 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then
-the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
-Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).</P
+>I am using the term "migrate" lossely. You can copy a profile to
+create a group profile. You can give the user 'Everyone' rights to the
+profile you copy this to. That is what you need to do, since your samba
+domain is not a member of a trust relationship with your NT4 PDC.</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
+></LI
+><LI
 ><P
->When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that
-disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires
-Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
-Use of DHCP with ADS is recommended as a further means of maintaining central control
-over client workstation network configuration.</P
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3688"
->22.1. Name Resolution in a pure Unix/Linux world</A
-></H2
-><P
->The key configuration files covered in this section are:</P
-><P
-></P
-><UL
+>Click the 'Copy To' button.</P
+></LI
 ><LI
 ><P
-><TT
+>In the box labelled 'Copy Profile to' add your new path, eg:
+	<TT
 CLASS="FILENAME"
->/etc/hosts</TT
+>c:\temp\foobar</TT
 ></P
 ></LI
 ><LI
 ><P
-><TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
-></P
+>Click on the button labelled 'Change' in the "Permitted to use" box.</P
 ></LI
 ><LI
 ><P
-><TT
-CLASS="FILENAME"
->/etc/host.conf</TT
-></P
+>Click on the group 'Everyone' and then click OK. This closes the
+	'chose user' box.</P
 ></LI
 ><LI
 ><P
-><TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-></P
+>Now click OK.</P
 ></LI
 ></UL
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3704"
->22.1.1. <TT
-CLASS="FILENAME"
->/etc/hosts</TT
-></A
-></H3
-><P
->Contains a static list of IP Addresses and names.
-eg:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box</PRE
-></P
-><P
->The purpose of <TT
-CLASS="FILENAME"
->/etc/hosts</TT
-> is to provide a 
-name resolution mechanism so that uses do not need to remember 
-IP addresses.</P
-><P
->Network packets that are sent over the physical network transport 
-layer communicate not via IP addresses but rather using the Media 
-Access Control address, or MAC address. IP Addresses are currently 
-32 bits in length and are typically presented as four (4) decimal 
-numbers that are separated by a dot (or period). eg: 168.192.1.1</P
-><P
->MAC Addresses use 48 bits (or 6 bytes) and are typically represented 
-as two digit hexadecimal numbers separated by colons. eg: 
-40:8e:0a:12:34:56</P
-><P
->Every network interfrace must have an MAC address. Associated with 
-a MAC address there may be one or more IP addresses. There is NO 
-relationship between an IP address and a MAC address, all such assignments 
-are arbitary or discretionary in nature. At the most basic level all 
-network communications takes place using MAC addressing. Since MAC 
-addresses must be globally unique, and generally remains fixed for 
-any particular interface, the assignment of an IP address makes sense 
-from a network management perspective. More than one IP address can 
-be assigned per MAC address. One address must be the primary IP address, 
-this is the address that will be returned in the ARP reply.</P
-><P
->When a user or a process wants to communicate with another machine 
-the protocol implementation ensures that the "machine name" or "host 
-name" is resolved to an IP address in a manner that is controlled 
-by the TCP/IP configuration control files. The file 
-<TT
-CLASS="FILENAME"
->/etc/hosts</TT
-> is one such file.</P
-><P
->When the IP address of the destination interface has been 
-determined a protocol called ARP/RARP is used to identify 
-the MAC address of the target interface. ARP stands for Address 
-Resolution Protocol, and is a broadcast oriented method that 
-uses UDP (User Datagram Protocol) to send a request to all 
-interfaces on the local network segment using the all 1's MAC 
-address. Network interfaces are programmed to respond to two 
-MAC addresses only; their own unique address and the address 
-ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will 
-contain the MAC address and the primary IP address for each 
-interface.</P
 ><P
->The <TT
-CLASS="FILENAME"
->/etc/hosts</TT
-> file is foundational to all 
-Unix/Linux TCP/IP installations and as a minumum will contain 
-the localhost and local network interface IP addresses and the 
-primary names by which they are known within the local machine. 
-This file helps to prime the pump so that a basic level of name 
-resolution can exist before any other method of name resolution 
-becomes available.</P
+>Follow the above for every profile you need to migrate.</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3720"
->22.1.2. <TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
-></A
-></H3
-><P
->This file tells the name resolution libraries:</P
-><P
-></P
-><UL
-><LI
+NAME="AEN3291"
+>18.1.4.2. Side bar Notes</A
+></H4
 ><P
->The name of the domain to which the machine 
-	belongs
-	</P
-></LI
-><LI
+>You should obtain the SID of your NT4 domain. You can use smbpasswd to do
+this. Read the man page.</P
 ><P
->The name(s) of any domains that should be 
-	automatically searched when trying to resolve unqualified 
-	host names to their IP address
-	</P
-></LI
-><LI
+>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="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN3295"
+>18.1.4.3. moveuser.exe</A
+></H4
 ><P
->The name or IP address of available Domain 
-	Name Servers that may be asked to perform name to address 
-	translation lookups
-	</P
-></LI
-></UL
+>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"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3731"
->22.1.3. <TT
-CLASS="FILENAME"
->/etc/host.conf</TT
-></A
-></H3
+NAME="AEN3298"
+>18.1.4.4. Get SID</A
+></H4
 ><P
-><TT
-CLASS="FILENAME"
->/etc/host.conf</TT
-> is the primary means by 
-which the setting in /etc/resolv.conf may be affected. It is a 
-critical configuration file.  This file controls the order by 
-which name resolution may procede. The typical structure is:</P
+>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
+Resource Kit.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	order hosts,bind
-	multi on</PRE
-></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
->then both addresses should be returned. Please refer to the 
-man page for host.conf for further details.</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
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN3739"
->22.1.4. <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-></A
-></H3
+NAME="AEN3303"
+>18.2. Mandatory profiles</A
+></H2
 ><P
->This file controls the actual name resolution targets. The 
-file typically has resolver object specifications as follows:</P
+>A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
+During the user's session it may be possible to change the desktop environment, but
+as the user logs out all changes made will be lost. If it is desired to NOT allow the
+user any ability to change the desktop environment then this must be done through
+policy settings. See previous chapter.</P
+><DIV
+CLASS="NOTE"
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	# /etc/nsswitch.conf
-	#
-	# Name Service Switch configuration file.
-	#
-
-	passwd:		compat
-	# Alternative entries for password authentication are:
-	# passwd:	compat files nis ldap winbind
-	shadow:		compat
-	group:		compat
-
-	hosts:		files nis dns
-	# Alternative entries for host name resolution are:
-	# hosts:	files dns nis nis+ hesoid db compat ldap wins
-	networks:	nis files dns
-
-	ethers:		nis files
-	protocols:	nis files
-	rpc:		nis files
-	services:	nis files</PRE
 ></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
->Of course, each of these mechanisms requires that the appropriate 
-facilities and/or services are correctly configured.</P
+>Under NO circumstances should the profile directory (or it's contents) be made read-only
+as this may render the profile un-usable.</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
->It should be noted that unless a network request/message must be 
-sent, TCP/IP networks are silent. All TCP/IP communications assumes a 
-principal of speaking only when necessary.</P
+>For MS Windows NT4/200x/XP 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
 ><P
->Starting with version 2.2.0 samba has Linux support for extensions to 
-the name service switch infrastructure so that linux clients will 
-be able to obtain resolution of MS Windows NetBIOS names to IP 
-Addresses. To gain this functionality Samba needs to be compiled 
-with appropriate arguments to the make command (ie: <B
-CLASS="COMMAND"
->make 
-nsswitch/libnss_wins.so</B
->). The resulting library should 
-then be installed in the <TT
-CLASS="FILENAME"
->/lib</TT
-> directory and 
-the "wins" parameter needs to be added to the "hosts:" line in 
-the <TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-> file. At this point it 
-will be possible to ping any MS Windows machine by it's NetBIOS 
-machine name, so long as that machine is within the workgroup to 
-which both the samba machine and the MS Windows machine belong.</P
-></DIV
+>For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
+affect a mandatory profile.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3751"
->22.2. Name resolution as used within MS Windows networking</A
+NAME="AEN3310"
+>18.3. Creating/Managing Group Profiles</A
 ></H2
 ><P
->MS Windows networking is predicated about the name each machine 
-is given. This name is known variously (and inconsistently) as 
-the "computer name", "machine name", "networking name", "netbios name", 
-"SMB name". All terms mean the same thing with the exception of 
-"netbios name" which can apply also to the name of the workgroup or the 
-domain name. The terms "workgroup" and "domain" are really just a 
-simply name with which the machine is associated. All NetBIOS names 
-are exactly 16 characters in length. The 16th character is reserved. 
-It is used to store a one byte value that indicates service level 
-information for the NetBIOS name that is registered. A NetBIOS machine 
-name is therefore registered for each service type that is provided by 
-the client/server.</P
+>Most organisations are arranged into departments. There is a nice benenfit in
+this fact since usually most users in a department will require the same desktop
+applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
+use of Group Profiles. A Group Profile is a profile that is created firstly using
+a template (example) user. Then using the profile migration tool (see above) the
+profile is assigned access rights for the user group that needs to be given access
+to the group profile.</P
 ><P
->The following are typical NetBIOS name/service type registrations:</P
+>The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
+to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
+the now modified profile.</P
+><DIV
+CLASS="NOTE"
 ><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
-
-	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
 ></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
->It should be noted that all NetBIOS machines register their own 
-names as per the above. This is in vast contrast to TCP/IP 
-installations where traditionally the system administrator will 
-determine in the /etc/hosts or in the DNS database what names 
-are associated with each IP address.</P
-><P
->One further point of clarification should be noted, the <TT
-CLASS="FILENAME"
->/etc/hosts</TT
-> 
-file and the DNS records do not provide the NetBIOS name type information 
-that MS Windows clients depend on to locate the type of service that may 
-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 
-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
->The name "workgroup" or "domain" really can be confusing since these 
-have the added significance of indicating what is the security 
-architecture of the MS Windows network. The term "workgroup" indicates 
-that the primary nature of the network environment is that of a 
-peer-to-peer design. In a WORKGROUP all machines are responsible for 
-their own security, and generally such security is limited to use of 
-just a password (known as SHARE MODE security). In most situations 
-with peer-to-peer networking the users who control their own machines 
-will simply opt to have no security at all. It is possible to have 
-USER MODE security in a WORKGROUP environment, thus requiring use 
-of a user name and a matching password.</P
-><P
->MS Windows networking is thus predetermined to use machine names 
-for all local and remote machine message passing. The protocol used is 
-called Server Message Block (SMB) and this is implemented using 
-the NetBIOS protocol (Network Basic Input Output System). NetBIOS can 
-be encapsulated using LLC (Logical Link Control) protocol - in which case 
-the resulting protocol is called NetBEUI (Network Basic Extended User 
-Interface). NetBIOS can also be run over IPX (Internetworking Packet 
-Exchange) protocol as used by Novell NetWare, and it can be run 
-over TCP/IP protocols - in which case the resulting protocol is called 
-NBT or NetBT, the NetBIOS over TCP/IP.</P
+>	Be careful with group profiles, if the user who is a member of a group also
+	has a personal profile, then the result will be a fusion (merge) of the two.
+	</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3316"
+>18.4. Default Profile for Windows Users</A
+></H2
 ><P
->MS Windows machines use a complex array of name resolution mechanisms. 
-Since we are primarily concerned with TCP/IP this demonstration is 
-limited to this area.</P
+>MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
+a profile does not already exist. Armed with a knowledge of where the default profile
+is located on the Windows workstation, and knowing which registry keys affect the path
+from which the default profile is created, it is possible to modify the default profile
+to one that has been optimised for the site. This has significant administrative 
+advantages.</P
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3763"
->22.2.1. The NetBIOS Name Cache</A
+NAME="AEN3319"
+>18.4.1. MS Windows 9x/Me</A
 ></H3
 ><P
->All MS Windows machines employ an in memory buffer in which is 
-stored the NetBIOS names and IP addresses for all external 
-machines that that machine has communicated with over the 
-past 10-15 minutes. It is more efficient to obtain an IP address 
-for a machine from the local cache than it is to go through all the 
-configured name resolution mechanisms.</P
+>To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
+Policy Editor or change the registry directly.</P
 ><P
->If a machine whose name is in the local name cache has been shut 
-down before the name had been expired and flushed from the cache, then 
-an attempt to exchange a message with that machine will be subject 
-to time-out delays. i.e.: Its name is in the cache, so a name resolution 
-lookup will succeed, but the machine can not respond. This can be 
-frustrating for users - but it is a characteristic of the protocol.</P
+>To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
+select File -&#62; Open Registry, then click on the Local Computer icon, click on Windows 98 System,
+select User Profiles, click on the enable box. Do not forget to save the registry changes.</P
 ><P
->The MS Windows utility that allows examination of the NetBIOS 
-name cache is called "nbtstat". The Samba equivalent of this 
-is called "nmblookup".</P
-></DIV
+>To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
+<TT
+CLASS="FILENAME"
+>HKEY_LOCAL_MACHINE\Network\Logon</TT
+>. Now add a DWORD type key with the name
+"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN3768"
->22.2.2. The LMHOSTS file</A
-></H3
+NAME="AEN3325"
+>18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?</A
+></H4
 ><P
->This file is usually located in MS Windows NT 4.0 or 
-2000 in <TT
-CLASS="FILENAME"
->C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
-> and contains 
-the IP Address and the machine name in matched pairs. The 
+>When a user logs on to a Windows 9x / Me machine, the local profile path, 
 <TT
 CLASS="FILENAME"
->LMHOSTS</TT
-> file performs NetBIOS name 
-to IP address mapping oriented.</P
+>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</TT
+>, is checked
+for an existing entry for that user:</P
 ><P
->It typically looks like:</P
+>If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
+version of the user profile. Windows 9x / Me also checks the user's home directory (or other
+specified directory if the location has been modified) on the server for the User Profile.
+If a profile exists in both locations, the newer of the two is used. If the User Profile exists
+on the server, but does not exist on the local machine, the profile on the server is downloaded
+and used. If the User Profile only exists on the local machine, that copy is used.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	# Copyright (c) 1998 Microsoft Corp.
-	#
-	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-	# over TCP/IP) stack for Windows98
-	#
-	# This file contains the mappings of IP addresses to NT computernames
-	# (NetBIOS) names.  Each entry should be kept on an individual line.
-	# The IP address should be placed in the first column followed by the
-	# corresponding computername. The address and the comptername
-	# should be separated by at least one space or tab. The "#" character
-	# is generally used to denote the start of a comment (see the exceptions
-	# below).
-	#
-	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-	# files and offers the following extensions:
-	#
-	#      #PRE
-	#      #DOM:&#60;domain&#62;
-	#      #INCLUDE &#60;filename&#62;
-	#      #BEGIN_ALTERNATE
-	#      #END_ALTERNATE
-	#      \0xnn (non-printing character support)
-	#
-	# Following any entry in the file with the characters "#PRE" will cause
-	# the entry to be preloaded into the name cache. By default, entries are
-	# not preloaded, but are parsed only after dynamic name resolution fails.
-	#
-	# Following an entry with the "#DOM:&#60;domain&#62;" tag will associate the
-	# entry with the domain specified by &#60;domain&#62;. This affects how the
-	# browser and logon services behave in TCP/IP environments. To preload
-	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The &#60;domain&#62; is always preloaded although it will not
-	# be shown when the name cache is viewed.
-	#
-	# Specifying "#INCLUDE &#60;filename&#62;" will force the RFC NetBIOS (NBT)
-	# software to seek the specified &#60;filename&#62; and parse it as if it were
-	# local. &#60;filename&#62; is generally a UNC-based name, allowing a
-	# centralized lmhosts file to be maintained on a server.
-	# It is ALWAYS necessary to provide a mapping for the IP address of the
-	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addtion the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
-	# be able to read the lmhosts file successfully. This key is under
-	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
-	#
-	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-	# statements to be grouped together. Any single successful include
-	# will cause the group to succeed.
-	#
-	# Finally, non-printing characters can be embedded in mappings by
-	# first surrounding the NetBIOS name in quotations, then using the
-	# \0xnn notation to specify a hex value for a non-printing character.
-	#
-	# The following example illustrates all of these extensions:
-	#
-	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
-	# 102.54.94.123    popular            #PRE             #source server
-	# 102.54.94.117    localsrv           #PRE             #needed for the include
-	#
-	# #BEGIN_ALTERNATE
-	# #INCLUDE \\localsrv\public\lmhosts
-	# #INCLUDE \\rhino\public\lmhosts
-	# #END_ALTERNATE
-	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-	# system is unavailable.
-	#
-	# Note that the whole file is parsed including comments on each lookup,
-	# so keeping the number of comments to a minimum will improve performance.
-	# Therefore it is not advisable to simply add lmhosts file entries onto the
-	# end of this file.</PRE
-></P
+>If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
+machine is used and is copied to a newly created folder for the logged on user. At log off, any
+changes that the user made are written to the user's local profile. If the user has a roaming
+profile, the changes are written to the user's profile on the server.</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3776"
->22.2.3. HOSTS file</A
+NAME="AEN3331"
+>18.4.2. MS Windows NT4 Workstation</A
 ></H3
 ><P
->This file is usually located in MS Windows NT 4.0 or 2000 in 
+>On MS Windows NT4 the default user profile is obtained from the location
 <TT
 CLASS="FILENAME"
->C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
-> and contains 
-the IP Address and the IP hostname in matched pairs. It can be 
-used by the name resolution infrastructure in MS Windows, depending 
-on how the TCP/IP environment is configured. This file is in 
-every way the equivalent of the Unix/Linux <TT
+>%SystemRoot%\Profiles</TT
+> which in a default installation will translate to
+<TT
+CLASS="FILENAME"
+>C:\WinNT\Profiles</TT
+>. Under this directory on a clean install there will be
+three (3) directories: <TT
+CLASS="FILENAME"
+>Administrator, All Users, Default User</TT
+>.</P
+><P
+>The <TT
+CLASS="FILENAME"
+>All Users</TT
+> directory contains menu settings that are common across all 
+system users. The <TT
+CLASS="FILENAME"
+>Default User</TT
+> directory contains menu entries that are
+customisable per user depending on the profile settings chosen/created.</P
+><P
+>When a new user first logs onto an MS Windows NT4 machine a new profile is created from:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>All Users settings</TD
+></TR
+><TR
+><TD
+>Default User settings (contains the default NTUser.DAT file)</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
+the following steps are followed in respect of profile handling:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>	The users' account information which is obtained during the logon process contains
+	the location of the users' desktop profile. The profile path may be local to the
+	machine or it may be located on a network share. If there exists a profile at the location
+	of the path from the user account, then this profile is copied to the location
+	<TT
+CLASS="FILENAME"
+>%SystemRoot%\Profiles\%USERNAME%</TT
+>. This profile then inherits the
+	settings in the <TT
+CLASS="FILENAME"
+>All Users</TT
+> profile in the <TT
+CLASS="FILENAME"
+>%SystemRoot%\Profiles</TT
+>
+	location.
+	</P
+></LI
+><LI
+><P
+>	If the user account has a profile path, but at it's location a profile does not exist,
+	then a new profile is created in the <TT
+CLASS="FILENAME"
+>%SystemRoot%\Profiles\%USERNAME%</TT
+>
+	directory from reading the <TT
+CLASS="FILENAME"
+>Default User</TT
+> profile.
+	</P
+></LI
+><LI
+><P
+>	If the NETLOGON share on the authenticating server (logon server) contains a policy file
+	(<TT
+CLASS="FILENAME"
+>NTConfig.POL</TT
+>) then it's contents are applied to the <TT
+CLASS="FILENAME"
+>NTUser.DAT</TT
+>
+	which is applied to the <TT
+CLASS="FILENAME"
+>HKEY_CURRENT_USER</TT
+> part of the registry. 
+	</P
+></LI
+><LI
+><P
+>	When the user logs out, if the profile is set to be a roaming profile it will be written
+	out to the location of the profile. The <TT
+CLASS="FILENAME"
+>NTuser.DAT</TT
+> file is then
+	re-created from the contents of the <TT
+CLASS="FILENAME"
+>HKEY_CURRENT_USER</TT
+> contents.
+	Thus, should there not exist in the NETLOGON share an <TT
 CLASS="FILENAME"
->/etc/hosts</TT
-> file.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3781"
->22.2.4. DNS Lookup</A
-></H3
-><P
->This capability is configured in the TCP/IP setup area in the network 
-configuration facility. If enabled an elaborate name resolution sequence 
-is followed the precise nature of which isdependant on what the NetBIOS 
-Node Type parameter is configured to. A Node Type of 0 means use 
-NetBIOS broadcast (over UDP broadcast) is first used if the name 
-that is the subject of a name lookup is not found in the NetBIOS name 
-cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to 
-Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the 
-WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast 
-lookup is used.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN3784"
->22.2.5. WINS Lookup</A
-></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 
-the names and IP addresses that are registered by a Windows client 
-if the TCP/IP setup has been given at least one WINS Server IP Address.</P
+>NTConfig.POL</TT
+> at the
+	next logon, the effect of the provious <TT
+CLASS="FILENAME"
+>NTConfig.POL</TT
+> will still be held
+	in the profile. The effect of this is known as <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>tatooing</I
+></SPAN
+>.
+	</P
+></LI
+></OL
 ><P
->To configure Samba to be a WINS server the following parameter needs 
-to be added to the <TT
+>MS Windows NT4 profiles may be <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Local</I
+></SPAN
+> or <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Roaming</I
+></SPAN
+>. A Local profile
+will stored in the <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file:</P
+>%SystemRoot%\Profiles\%USERNAME%</TT
+> location. A roaming profile will
+also remain stored in the same way, unless the following registry key is created:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->	wins support = Yes</PRE
-></P
+>	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001</PRE
+>
+
+In which case, the local copy (in <TT
+CLASS="FILENAME"
+>%SystemRoot%\Profiles\%USERNAME%</TT
+>) will be
+deleted on logout.</P
 ><P
->To configure Samba to use a WINS server the following parameters are 
-needed in the <TT
+>Under MS Windows NT4 default locations for common resources (like <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file:</P
+>My Documents</TT
+>
+may be redirected to a network share by modifying the following registry keys. These changes may be affected
+via use of the System Policy Editor (to do so may require that you create your owns template extension
+for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
+creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P
+><P
+>The Registry Hive key that affects the behaviour of folders that are part of the default user profile
+are controlled by entries on Windows NT4 is:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->	wins support = No
-	wins server = xxx.xxx.xxx.xxx</PRE
+>        HKEY_CURRENT_USER
+                \Software
+                        \Microsoft
+                                \Windows
+                                        \CurrentVersion
+                                                \Explorer
+                                                        \User Shell Folders\</PRE
 ></P
 ><P
->where <VAR
-CLASS="REPLACEABLE"
->xxx.xxx.xxx.xxx</VAR
-> is the IP address 
-of the WINS server.</P
-></DIV
-></DIV
+>The above hive key contains a list of automatically managed folders. The default entries are:</P
+><P
+>        <PRE
+CLASS="PROGRAMLISTING"
+>        Name            Default Value
+        --------------  -----------------------------------------
+        AppData         %USERPROFILE%\Application Data
+        Desktop         %USERPROFILE%\Desktop
+        Favorites       %USERPROFILE%\Favorites
+        NetHood         %USERPROFILE%\NetHood
+        PrintHood       %USERPROFILE%\PrintHood
+        Programs        %USERPROFILE%\Start Menu\Programs
+        Recent          %USERPROFILE%\Recent
+        SendTo          %USERPROFILE%\SendTo
+        Start Menu      %USERPROFILE%\Start Menu
+        Startup         %USERPROFILE%\Start Menu\Programs\Startup
+        </PRE
+>
+        </P
+><P
+>The registry key that contains the location of the default profile settings is:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>	HKEY_LOCAL_MACHINE
+		\SOFTWARE
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders</PRE
+>
+
+The default entries are:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
+	Common Programs		%SystemRoot%\Profiles\All Users\Programs
+	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
+	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE
+></P
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="IMPROVED-BROWSING"
-></A
->Chapter 23. Improved browsing in samba</H1
+NAME="AEN3385"
+>18.4.3. MS Windows 200x/XP</A
+></H3
 ><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN3804"
->23.1. Overview of browsing</A
-></H2
-><P
->SMB networking provides a mechanism by which clients can access a list
-of machines in a network, a so-called <B
-CLASS="COMMAND"
->browse list</B
->.  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
+CLASS="NOTE"
 ><P
->MS Windows 2000 and later, as with Samba 3 and later, can be
-configured to not use NetBIOS over TCP/IP. When configured this way
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will NOT work if name resolution
-from SMB machine names to IP addresses does not function correctly.</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
->Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
-recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
-WINS allows remote segment clients to obtain NetBIOS name_type information
-that can NOT be provided by any other means of name resolution.</P
+>	MS Windows XP Home Edition does use default per user profiles, but can not participate
+	in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
+	only from itself. While there are benefits in doing this the beauty of those MS Windows
+	clients that CAN participate in domain logon processes allows the administrator to create
+	a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
+	</P
+></TD
+></TR
+></TABLE
 ></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3810"
->23.2. Browsing support in samba</A
-></H2
 ><P
->Samba facilitates browsing.  The browsing is supported by <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
->
-and is also controlled by options in the <TT
+>When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
+<TT
 CLASS="FILENAME"
->smb.conf</TT
-> file.
-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.</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
+>C:\Documents and Settings\Default User</TT
+>. The administrator can modify (or change
+the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
+arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
+workstation. </P
+><P
+>When MS Windows 200x/XP participate in a domain security context, and if the default user
+profile is not found, then the client will search for a default profile in the NETLOGON share
+of the authenticating server. ie: In MS Windows parlance:
+<TT
+CLASS="FILENAME"
+>%LOGONSERVER%\NETLOGON\Default User</TT
+> and if one exits there it will copy this
+to the workstation to the <TT
+CLASS="FILENAME"
+>C:\Documents and Settings\</TT
+> under the Windows
+login name of the user.</P
 ><DIV
 CLASS="NOTE"
 ><P
@@ -18604,1690 +15521,3581 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->Nmbd can be configured as a WINS server, but it is not
-necessary to specifically use samba as your WINS server.  MS Windows
-NT4, Server or Advanced Server 2000 or 2003 can be configured as
-your WINS server.  In a mixed NT/2000/2003 server and samba environment on
-a Wide Area Network, it is recommended that you use the Microsoft
-WINS server capabilities.  In a samba-only environment, it is
-recommended that you use one and only one Samba server as your WINS server.</P
+>	This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
+	should be created at the root of this share and msut be called <TT
+CLASS="FILENAME"
+>Default Profile</TT
+>.
+	</P
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ><P
->To get browsing to work you need to run nmbd as usual, but will need
-to use the <B
-CLASS="COMMAND"
->workgroup</B
-> option in <TT
+>If a default profile does not exist in this location then MS Windows 200x/XP will use the local
+default profile.</P
+><P
+>On loging out, the users' desktop profile will be stored to the location specified in the registry
+settings that pertain to the user. If no specific policies have been created, or passed to the client
+during the login process (as Samba does automatically), then the user's profile will be written to
+the local machine only under the path <TT
 CLASS="FILENAME"
->smb.conf</TT
+>C:\Documents and Settings\%USERNAME%</TT
+>.</P
+><P
+>Those wishing to modify the default behaviour can do so through up to three methods:</P
+><P
+></P
+><UL
+><LI
+><P
+>	Modify the registry keys on the local machine manually and place the new default profile in the
+	NETLOGON share root - NOT recommended as it is maintenance intensive.
+	</P
+></LI
+><LI
+><P
+>	Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
+	in the root of the NETLOGON share along with the new default profile.
+	</P
+></LI
+><LI
+><P
+>	Create a GPO that enforces this through Active Directory, and place the new default profile
+	in the NETLOGON share.
+	</P
+></LI
+></UL
+><P
+>The Registry Hive key that affects the behaviour of folders that are part of the default user profile
+are controlled by entries on Windows 200x/XP is:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	HKEY_CURRENT_USER
+		\Software
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders\</PRE
+></P
+><P
+>The above hive key contains a list of automatically managed folders. The default entries are:</P
+><P
+>	<PRE
+CLASS="PROGRAMLISTING"
+>	Name		Default Value
+	--------------	-----------------------------------------
+	AppData		%USERPROFILE%\Application Data
+	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
+	Cookies		%USERPROFILE%\Cookies
+	Desktop		%USERPROFILE%\Desktop
+	Favorites	%USERPROFILE%\Favorites
+	History		%USERPROFILE%\Local Settings\History
+	Local AppData	%USERPROFILE%\Local Settings\Application Data
+	Local Settings	%USERPROFILE%\Local Settings
+	My Pictures	%USERPROFILE%\My Documents\My Pictures
+	NetHood		%USERPROFILE%\NetHood
+	Personal	%USERPROFILE%\My Documents
+	PrintHood	%USERPROFILE%\PrintHood
+	Programs	%USERPROFILE%\Start Menu\Programs
+	Recent		%USERPROFILE%\Recent
+	SendTo		%USERPROFILE%\SendTo
+	Start Menu	%USERPROFILE%\Start Menu
+	Startup		%USERPROFILE%\Start Menu\Programs\Startup
+	Templates	%USERPROFILE%\Templates
+	</PRE
 >
-to control what workgroup Samba becomes a part of.</P
+	</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 <B
-CLASS="COMMAND"
->remote announce</B
-> in the 
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> man page.  </P
+>There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
+the others are of type REG_EXPAND_SZ.</P
+><P
+>It makes a huge difference to the speed of handling roaming user profiles if all the folders are
+stored on a dedicated location on a network server. This means that it will NOT be necessary to
+write Outlook PST file over the network for every login and logout.</P
+><P
+>To set this to a network location you could use the following examples:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>	%LOGONSERVER%\%USERNAME%\Default Folders</PRE
+>
+
+This would store the folders in the user's home directory under a directory called "Default Folders"
+
+You could also use:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>	\\SambaServer\FolderShare\%USERNAME%</PRE
+>
+
+in which case the default folders will be stored in the server named <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>SambaServer</I
+></SPAN
+>
+in the share called <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>FolderShare</I
+></SPAN
+> under a directory that has the name of the MS Windows
+user as seen by the Linux/Unix file system.</P
+><P
+>Please note that once you have created a default profile share, you MUST migrate a user's profile
+(default or custom) to it.</P
+><P
+>MS Windows 200x/XP profiles may be <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Local</I
+></SPAN
+> or <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Roaming</I
+></SPAN
+>.
+A roaming profile will be cached locally unless the following registry key is created:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001</PRE
+>
+
+In which case, the local cache copy will be deleted on logout.</P
+></DIV
 ></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="INTERDOMAINTRUSTS"
+></A
+>Chapter 19. Interdomain Trust Relationships</H1
+><P
+>Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
+will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
+adopt Active Directory or an LDAP based authentication back end. This section explains
+some background information regarding trust relationships and how to create them. It is now
+possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.</P
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3825"
->23.3. Problem resolution</A
+NAME="AEN3447"
+>19.1. Trust Relationship Background</A
 ></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 <TT
-CLASS="FILENAME"
->browse.dat</TT
->.</P
-><P
->Note that if it doesn't work for you, then you should still be able to
-type the server name as <TT
-CLASS="FILENAME"
->\\SERVER</TT
-> in filemanager then
-hit enter and filemanager should display the list of available shares.</P
+>MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure.
+The limitations of this architecture as it affects the scalability of MS Windows networking
+in large organisations is well known. Additionally, the flat-name space that results from
+this design significantly impacts the delegation of administrative responsibilities in
+large and diverse organisations.</P
 ><P
->Some people find browsing fails because they don't have the global
-<B
-CLASS="COMMAND"
->guest account</B
-> 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
+>Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
+of circumventing the limitations of the older technologies. Not every organisation is ready
+or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
+is quite adequate, there thus remains an entrenched user base for whom there is no direct
+desire to go through a disruptive change to adopt ADS.</P
 ><P
-><SPAN
+>Microsoft introduced with MS Windows NT the ability to allow differing security domains
+to affect a mechanism so that users from one domain may be given access rights and privileges
+in another domain. The language that describes this capability is couched in terms of
+<SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
->MS Windows 2000 and upwards (as with Samba) can be configured to disallow
-anonymous (ie: Guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged in user to query the IPC$ share. MS Windows
-9X clients are not able to do this and thus will NOT be able to browse
-server resources.</I
+>Trusts</I
 ></SPAN
-></P
+>. Specifically, one domain will <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>trust</I
+></SPAN
+> the users
+from another domain. The domain from which users are available to another security domain is
+said to be a trusted domain. The domain in which those users have assigned rights and privileges
+is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
+thus if users in both domains are to have privileges and rights in each others' domain, then it is
+necessary to establish two (2) relationships, one in each direction.</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 <TT
-CLASS="FILENAME"
->smb.conf</TT
->)</P
+>In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
+are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
+relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
+implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
+transitive.</P
+><P
+>New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
+by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
+domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
+an inherent feature of ADS domains. Samba-3 implements MS Windows NT4
+style Interdomain trusts and interoperates with MS Windows 200x ADS
+security domains in similar manner to MS Windows NT4 style domains.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3837"
->23.4. Browsing across subnets</A
+NAME="AEN3456"
+>19.2. Native MS Windows NT4 Trusts Configuration</A
 ></H2
 ><P
->Since the release of Samba 1.9.17(alpha1) 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 <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file.</P
+>There are two steps to creating an interdomain trust relationship.</P
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN3843"
->23.4.1. How does cross subnet browsing work ?</A
+NAME="AEN3459"
+>19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)</A
 ></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.
-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&#62;1B&#60;.  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
+>For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
+To affect a two way trust relationship it is necessary for each domain administrator to make
+available (for use by an external domain) it's security resources. This is done from the Domain
+User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
+next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and
+"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that
+will be able to assign user rights to your domain. In addition it is necessary to enter a password
+that is specific to this trust relationship. The password needs to be
+typed twice (for standard confirmation).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3462"
+>19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)</A
+></H3
 ><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
+>A trust relationship will work only when the other (trusting) domain makes the appropriate connections
+with the trusted domain. To consumate the trust relationship the administrator will launch the
+Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
+"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in
+which must be entered the name of the remote domain as well as the password assigned to that trust.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3465"
+>19.3. Configuring Samba NT-style Domain Trusts</A
+></H2
 ><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
+>This description is meant to be a fairly short introduction about how to set up a Samba server so
+that it could participate in interdomain trust relationships. Trust relationship support in Samba
+is in its early stage, so lot of things don't work yet.</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
+>Each of the procedures described below is treated as they were performed with Windows NT4 Server on
+one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after
+reading this document, that combining Samba-specific parts of what's written below leads to trust
+between domains in purely Samba environment.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3469"
+>19.3.1. Samba-3 as the Trusting Domain</A
+></H3
 ><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
+>In order to set Samba PDC to be trusted party of the relationship first you need
+to create special account for the domain that will be the trusting party. To do that,
+you can use the 'smbpasswd' utility. Creating the trusted domain account is very
+similiar to creating a trusted machine account. Suppose, your domain is
+called SAMBA, and the remote domain is called RUMBA. The first step
+will be to issue this command from your favourite shell:</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(*)
+CLASS="SCREEN"
+>   &nbsp;<SAMP
+CLASS="PROMPT"
+>deity#</SAMP
+> <KBD
+CLASS="USERINPUT"
+>smbpasswd -a -i rumba</KBD
+>
+   &nbsp;	New SMB password: XXXXXXXX
+   &nbsp;	Retype SMB password: XXXXXXXX
+   &nbsp;	Added user rumba$</PRE
+>
 
-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
+where <VAR
+CLASS="PARAMETER"
+>-a</VAR
+> means to add a new account into the
+passdb database and <VAR
+CLASS="PARAMETER"
+>-i</VAR
+> means: ''create this
+account with the InterDomain trust flag''</P
 ><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
+>The account name will be 'rumba$' (the name of the remote domain)</P
 ><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
+>After issuing this command you'll be asked to enter the password for
+the account. You can use any password you want, but be aware that Windows NT will
+not change this password until 7 days following account creation.
+After the command returns successfully, you can look at the entry for new account
+(in the way depending on your configuration) and see that account's name is
+really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
+the trust by establishing it from Windows NT Server.</P
+><P
+>Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
+Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for
+the trusted domain name and the relationship password. Type in SAMBA, as this is
+your domain name, and the password used at the time of account creation.
+Press OK and, if everything went without incident, you will see 'Trusted domain relationship
+successfully established' message.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN3878"
->23.5. Setting up a WINS server</A
-></H2
+NAME="AEN3481"
+>19.3.2. Samba-3 as the Trusted Domain</A
+></H3
 ><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 <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file on the selected machine :
-in the [globals] section add the line </P
+>This time activities are somewhat reversed. Again, we'll assume that your domain
+controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.</P
 ><P
-><B
-CLASS="COMMAND"
->		wins support = yes</B
-></P
+>The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.</P
 ><P
->Versions of Samba prior to 1.9.17 had this parameter default to
-yes.  If you have any older versions of Samba on your network it is
-strongly suggested you upgrade to a recent version, or at the very
-least set the parameter to 'no' on all these machines.</P
+>Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
+Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
+domain (SAMBA) and password securing the relationship.</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
+>The password can be arbitrarily chosen. It is easy to change it the password
+from Samba server whenever you want. After confirming the password your account is
+ready for use. Now it's Samba's turn.</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
+>Using your favourite shell while being logged in as root, issue this command:</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 
-<B
-CLASS="COMMAND"
->wins support = yes</B
-> parameter set.</P
+><SAMP
+CLASS="PROMPT"
+>deity# </SAMP
+><KBD
+CLASS="USERINPUT"
+>net rpc trustdom establish rumba</KBD
+></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 <TT
-CLASS="FILENAME"
->smb.conf</TT
-> files :</P
+>You will be prompted for the password you just typed on your Windows NT4 Server box.
+Don not worry if you see an error message that mentions a returned code of
+<SPAN
+CLASS="ERRORNAME"
+>NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT</SPAN
+>. It means the
+password you gave is correct and the NT4 Server says the account is
+ready for interdomain connection and not for ordinary
+connection. After that, be patient it can take a while (especially
+in large networks), you should see the 'Success' message. Congratulations! Your trust
+relationship has just been established.</P
+><DIV
+CLASS="NOTE"
 ><P
-><B
-CLASS="COMMAND"
->wins server = &#62;name or IP address&#60;</B
 ></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
->where &#62;name or IP address&#60; 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 <TT
+>Note that you have to run this command as root because you must have write access to
+the <TT
 CLASS="FILENAME"
->smb.conf</TT
-> 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 = &#60;name&#62;</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
+>secrets.tdb</TT
+> file.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
 ></DIV
 ><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PAM"
+></A
+>Chapter 20. PAM Configuration for Centrally Managed Authentication</H1
+><DIV
 CLASS="SECT1"
-><HR><H2
+><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3901"
->23.6. Setting up Browsing in a WORKGROUP</A
+NAME="AEN3508"
+>20.1. Samba and PAM</A
 ></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 <TT
+>A number of Unix systems (eg: Sun Solaris), as well as the 
+xxxxBSD family and Linux, now utilize the Pluggable Authentication 
+Modules (PAM) facility to provide all authentication, 
+authorization and resource control services. Prior to the 
+introduction of PAM, a decision to use an alternative to 
+the system password database (<TT
 CLASS="FILENAME"
->smb.conf</TT
-> file :</P
-><P
-><B
+>/etc/passwd</TT
+>) 
+would require the provision of alternatives for all programs that provide 
+security services. Such a choice would involve provision of 
+alternatives to such programs as: <B
 CLASS="COMMAND"
->domain master = yes</B
-></P
+>login</B
+>, 
+<B
+CLASS="COMMAND"
+>passwd</B
+>, <B
+CLASS="COMMAND"
+>chown</B
+>, etc.</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 <TT
+>PAM provides a mechanism that disconnects these security programs 
+from the underlying authentication/authorization infrastructure.
+PAM is configured either through one file <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+>/etc/pam.conf</TT
+> (Solaris), 
+or by editing individual files that are located in <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+>.</P
+><DIV
+CLASS="NOTE"
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->domain master = yes
-local master = yes
-preferred master = yes
-os level = 65</PRE
 ></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
->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 MS Windows NT/2K/XP/2003  machine should be
-able to do this, as will Windows 9x 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
-<TT
+>	If the PAM authentication module (loadable link library file) is located in the
+	default location then it is not necessary to specify the path. In the case of
+	Linux, the default location is <TT
+CLASS="FILENAME"
+>/lib/security</TT
+>. If the module
+	is located other than default then the path may be specified as:
+	
+	<PRE
+CLASS="PROGRAMLISTING"
+>	auth       required      /other_path/pam_strange_module.so
+	</PRE
+>
+	</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>The following is an example <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+>/etc/pam.d/login</TT
+> configuration file. 
+This example had all options been uncommented is probably not usable 
+as it stacks many conditions before allowing successful completion 
+of the login process. Essentially all conditions can be disabled 
+by commenting them out except the calls to <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+>.</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->domain master = no
-local master = yes
-preferred master = yes
-os level = 65</PRE
+>	#%PAM-1.0
+	# The PAM configuration file for the `login' service
+	#
+	auth 		required	pam_securetty.so
+	auth 		required	pam_nologin.so
+	# auth 		required	pam_dialup.so
+	# auth 		optional	pam_mail.so
+	auth		required	pam_pwdb.so shadow md5
+	# account    	requisite  	pam_time.so
+	account		required	pam_pwdb.so
+	session		required	pam_pwdb.so
+	# session 	optional	pam_lastlog.so
+	# password   	required   	pam_cracklib.so retry=3
+	password	required	pam_pwdb.so shadow md5</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
+>PAM allows use of replacable modules. Those available on a 
+sample system include:</P
 ><P
->The <B
-CLASS="COMMAND"
->local master</B
-> parameter allows Samba to act as a
-local master browser.  The <B
-CLASS="COMMAND"
->preferred master</B
-> causes nmbd
-to force a browser election on startup and the <B
-CLASS="COMMAND"
->os level</B
+><SAMP
+CLASS="PROMPT"
+>$</SAMP
+><KBD
+CLASS="USERINPUT"
+>/bin/ls /lib/security</KBD
 >
-parameter sets Samba high enough so that it should win any browser elections.</P
+<PRE
+CLASS="PROGRAMLISTING"
+>	pam_access.so    pam_ftp.so          pam_limits.so     
+	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
+	pam_cracklib.so  pam_group.so        pam_listfile.so   
+	pam_nologin.so   pam_rootok.so       pam_tally.so      
+	pam_deny.so      pam_issue.so        pam_mail.so       
+	pam_permit.so    pam_securetty.so    pam_time.so       
+	pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so  
+	pam_pwdb.so      pam_shells.so       pam_unix.so       
+	pam_env.so       pam_ldap.so         pam_motd.so       
+	pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
+	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
+	pam_userdb.so    pam_warn.so         pam_unix_session.so</PRE
+></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 <B
+>The following example for the login program replaces the use of 
+the <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+> module which uses the system 
+password database (<TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>,
+<TT
+CLASS="FILENAME"
+>/etc/shadow</TT
+>, <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>) with 
+the module <TT
+CLASS="FILENAME"
+>pam_smbpass.so</TT
+> which uses the Samba 
+database which contains the Microsoft MD4 encrypted password 
+hashes. This database is stored in either 
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/private/smbpasswd</TT
+>, 
+<TT
+CLASS="FILENAME"
+>/etc/samba/smbpasswd</TT
+>, or in 
+<TT
+CLASS="FILENAME"
+>/etc/samba.d/smbpasswd</TT
+>, depending on the 
+Samba implementation for your Unix/Linux system. The 
+<TT
+CLASS="FILENAME"
+>pam_smbpass.so</TT
+> module is provided by 
+Samba version 2.2.1 or later. It can be compiled by specifying the 
+<B
 CLASS="COMMAND"
->[global]</B
-> section of the 
+>--with-pam_smbpass</B
+> options when running Samba's
 <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+>configure</TT
+> script.  For more information
+on the <TT
+CLASS="FILENAME"
+>pam_smbpass</TT
+> module, see the documentation
+in the <TT
+CLASS="FILENAME"
+>source/pam_smbpass</TT
+> directory of the Samba 
+source distribution.</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->domain master = no
-local master = no
-preferred master = no
-os level = 0</PRE
+>	#%PAM-1.0
+	# The PAM configuration file for the `login' service
+	#
+	auth		required	pam_smbpass.so nodelay
+	account		required	pam_smbpass.so nodelay
+	session		required	pam_smbpass.so nodelay
+	password	required	pam_smbpass.so nodelay</PRE
 ></P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN3927"
->23.7. Setting up Browsing in a DOMAIN</A
-></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 (<VAR
-CLASS="REPLACEABLE"
->DOMAIN</VAR
->&#60;1B&#62;)
-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 <B
-CLASS="COMMAND"
->[global]</B
-> section 
-of the <TT
+>The following is the PAM configuration file for a particular 
+Linux system. The default condition uses <TT
 CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+>pam_pwdb.so</TT
+>.</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->domain master = no
-local master = yes
-preferred master = yes
-os level = 65</PRE
+>	#%PAM-1.0
+	# The PAM configuration file for the `samba' service
+	#
+	auth       required     pam_pwdb.so nullok nodelay shadow audit
+	account    required     pam_pwdb.so audit nodelay
+	session    required     pam_pwdb.so nodelay
+	password   required     pam_pwdb.so shadow md5</PRE
 ></P
 ><P
->If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the <B
-CLASS="COMMAND"
->os level</B
-> 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 <A
-HREF="#BROWSE-FORCE-MASTER"
->Forcing samba to be the master browser</A
->
-below.</P
+>In the following example the decision has been made to use the 
+smbpasswd database even for basic samba authentication. Such a 
+decision could also be made for the passwd program and would 
+thus allow the smbpasswd passwords to be changed using the passwd 
+program.</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 <B
-CLASS="COMMAND"
->[global]</B
-> section of the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-file :</P
+><PRE
+CLASS="PROGRAMLISTING"
+>	#%PAM-1.0
+	# The PAM configuration file for the `samba' service
+	#
+	auth       required     pam_smbpass.so nodelay
+	account    required     pam_pwdb.so audit nodelay
+	session    required     pam_pwdb.so nodelay
+	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE
+></P
+><DIV
+CLASS="NOTE"
 ><P
-><B
-CLASS="COMMAND"
->        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0</B
 ></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
+>PAM allows stacking of authentication mechanisms. It is 
+also possible to pass information obtained within one PAM module through 
+to the next module in the PAM stack. Please refer to the documentation for 
+your particular system implementation for details regarding the specific 
+capabilities of PAM in this environment. Some Linux implmentations also 
+provide the <TT
+CLASS="FILENAME"
+>pam_stack.so</TT
+> module that allows all 
+authentication to be configured in a single central file. The 
+<TT
+CLASS="FILENAME"
+>pam_stack.so</TT
+> method has some very devoted followers 
+on the basis that it allows for easier administration. As with all issues in 
+life though, every decision makes trade-offs, so you may want examine the 
+PAM documentation for further helpful information.</P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="BROWSE-FORCE-MASTER"
->23.8. Forcing samba to be the master</A
+NAME="AEN3559"
+>20.2. Distributed Authentication</A
 ></H2
 ><P
->Who becomes the <B
-CLASS="COMMAND"
->master browser</B
-> 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 <B
-CLASS="COMMAND"
->os level</B
-> global
-option in <TT
+>The astute administrator will realize from this that the 
+combination of <TT
 CLASS="FILENAME"
->smb.conf</TT
-> 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 <B
-CLASS="COMMAND"
->os level</B
-> of 2 would make it beat WfWg and Win95, but not MS Windows
-NT/2K Server.  A MS Windows NT/2K Server domain controller uses level 32.</P
-><P
->The maximum os level is 255</P
-><P
->If you want samba to force an election on startup, then set the
+>pam_smbpass.so</TT
+>, 
 <B
 CLASS="COMMAND"
->preferred master</B
-> global option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> 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 <B
-CLASS="COMMAND"
->preferred master</B
-> 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 <B
-CLASS="COMMAND"
->domain master browser</B
->, then it is
-recommended that you also set <B
-CLASS="COMMAND"
->preferred master</B
-> 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
+>winbindd</B
+>, and a distributed 
+passdb backend, such as ldap, will allow the establishment of a
+centrally managed, distributed 
+user/password database that can also be used by all 
+PAM (eg: Linux) aware programs and applications. This arrangement 
+can have particularly potent advantages compared with the 
+use of Microsoft Active Directory Service (ADS) in so far as 
+reduction of wide area network authentication traffic.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN3962"
->23.9. Making samba the domain master</A
+NAME="AEN3564"
+>20.3. PAM Configuration in smb.conf</A
 ></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 <B
-CLASS="COMMAND"
->domain master = yes</B
->
-in <TT
-CLASS="FILENAME"
->smb.conf</TT
->.  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
+>There is an option in smb.conf called <A
+HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
+TARGET="_top"
+>obey pam restrictions</A
+>. 
+The following is from the on-line help for this option in SWAT;</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
+>When Samba is configured to enable PAM support (i.e. 
+<CODE
+CLASS="CONSTANT"
+>--with-pam</CODE
+>), this parameter will 
+control whether or not Samba should obey PAM's account 
+and session management directives. The default behavior 
+is to use PAM for clear text authentication only and to 
+ignore any account or session management. Note that Samba always 
+ignores PAM for authentication in the case of 
+<A
+HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
+TARGET="_top"
+>encrypt passwords = yes</A
+>. 
+The reason is that PAM modules cannot support the challenge/response 
+authentication mechanism needed in the presence of SMB 
+password encryption. </P
 ><P
->If you want samba to be the domain master then I suggest you also set
-the <B
-CLASS="COMMAND"
->os level</B
-> high enough to make sure it wins elections, and set
-<B
+>Default: <B
 CLASS="COMMAND"
->preferred master</B
-> 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
+>obey pam restrictions = no</B
 ></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
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="VFS"
+></A
+>Chapter 21. Stackable VFS modules</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3601"
+>21.1. Introduction and configuration</A
+></H2
 ><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
+>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
->If, however, both samba and your clients are using a WINS server, then:</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 use the VFS modules, create a share similar to the one below.  The
+important parameter is the <B
+CLASS="COMMAND"
+>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"
+>       [audit]
+                comment = Audited /data directory
+                path = /data
+                vfs object = /path/to/audit.so /path/to/recycle.so
+                writeable = yes
+                browseable = yes</PRE
 ></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
+>The modules are used in the order they are specified.</P
 ><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
+>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="AEN3984"
->23.10. Note about broadcast addresses</A
+NAME="AEN3610"
+>21.2. Included modules</A
 ></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"
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
 ><A
-NAME="AEN3987"
->23.11. Multiple interfaces</A
-></H2
+NAME="AEN3612"
+>21.2.1. audit</A
+></H3
+><P
+>A simple module to audit file access to the syslog
+facility.  The following operations are logged:
+<P
+></P
+><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
->Samba now supports machines with multiple network interfaces.  If you
-have multiple interfaces then you will need to use the <B
-CLASS="COMMAND"
->interfaces</B
->
-option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to configure them. </P
-></DIV
+></P
+></P
 ></DIV
 ><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="SECURING-SAMBA"
-></A
->Chapter 24. Securing Samba</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN4003"
->24.1. Introduction</A
-></H2
+NAME="AEN3620"
+>21.2.2. extd_audit</A
+></H3
 ><P
->This note was attached to the Samba 2.2.8 release notes as it contained an
-important security fix.  The information contained here applies to Samba
-installations in general.</P
+>This module is identical with the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>audit</I
+></SPAN
+> module above except
+that it sends audit logs to both syslog as well as the smbd log file/s. The 
+loglevel for this module is set in the smb.conf file. At loglevel = 0, only file
+and directory deletions and directory and file creations are logged. At loglevel = 1
+file opens are renames and permission changes are logged , while at loglevel = 2 file
+open and close calls are logged also.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN4006"
->24.2. Using host based protection</A
-></H2
-><P
->In many installations of Samba the greatest threat comes for outside
-your immediate network. By default Samba will accept connections from
-any host, which means that if you run an insecure version of Samba on
-a host that is directly connected to the Internet you can be
-especially vulnerable.</P
+NAME="AEN3624"
+>21.2.3. recycle</A
+></H3
 ><P
->One of the simplest fixes in this case is to use the <B
-CLASS="COMMAND"
->hosts allow</B
-> and
-<B
-CLASS="COMMAND"
->hosts deny</B
-> options in the Samba <TT
-CLASS="FILENAME"
->smb.conf</TT
-> configuration file to only
-allow access to your server from a specific range of hosts. An example
-might be:</P
+>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
-><PRE
-CLASS="PROGRAMLISTING"
->  hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
-  hosts deny = 0.0.0.0/0</PRE
+>Supported options:
+<P
 ></P
-><P
->The above will only allow SMB connections from 'localhost' (your own
-computer) and from the two private networks 192.168.2 and
-192.168.3. All other connections will be refused connections as soon
-as the client sends its first packet. The refusal will be marked as a
-'not listening on called name' error.</P
-></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4016"
->24.3. Using interface protection</A
-></H2
+CLASS="VARIABLELIST"
+><DL
+><DT
+>vfs_recycle_bin:repository</DT
+><DD
 ><P
->By default Samba will accept connections on any network interface that
-it finds on your system. That means if you have a ISDN line or a PPP
-connection to the Internet then Samba will accept connections on those
-links. This may not be what you want.</P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:keeptree</DT
+><DD
 ><P
->You can change this behaviour using options like the following:</P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:versions</DT
+><DD
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->  interfaces = eth* lo
-  bind interfaces only = yes</PRE
-></P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:touch</DT
+><DD
 ><P
-></P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:maxsize</DT
+><DD
 ><P
->This tells Samba to only listen for connections on interfaces with a
-name starting with 'eth' such as eth0, eth1, plus on the loopback
-interface called 'lo'. The name you will need to use depends on what
-OS you are using, in the above I used the common name for Ethernet
-adapters on Linux.</P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:exclude</DT
+><DD
 ><P
->If you use the above and someone tries to make a SMB connection to
-your host over a PPP interface called 'ppp0' then they will get a TCP
-connection refused reply. In that case no Samba code is run at all as
-the operating system has been told not to pass connections from that
-interface to any process.</P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:exclude_dir</DT
+><DD
+><P
+>FIXME</P
+></DD
+><DT
+>vfs_recycle_bin:noversions</DT
+><DD
+><P
+>FIXME</P
+></DD
+></DL
+></DIV
+></P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN4025"
->24.4. Using a firewall</A
-></H2
-><P
->Many people use a firewall to deny access to services that they don't
-want exposed outside their network. This can be a very good idea,
-although I would recommend using it in conjunction with the above
-methods so that you are protected even if your firewall is not active
-for some reason.</P
+NAME="AEN3661"
+>21.2.4. netatalk</A
+></H3
 ><P
->If you are setting up a firewall then you need to know what TCP and
-UDP ports to allow and block. Samba uses the following:</P
+>A netatalk module, that will ease co-existence of samba and
+netatalk file sharing services.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->UDP/137    - used by nmbd
-UDP/138    - used by nmbd
-TCP/139    - used by smbd
-TCP/445    - used by smbd</PRE
+>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
->The last one is important as many older firewall setups may not be
-aware of it, given that this port was only added to the protocol in
-recent years. </P
+></P
+></P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4032"
->24.5. Using a IPC$ share deny</A
+NAME="AEN3668"
+>21.3. VFS modules available elsewhere</A
 ></H2
 ><P
->If the above methods are not suitable, then you could also place a
-more specific deny on the IPC$ share that is used in the recently
-discovered security hole. This allows you to offer access to other
-shares while denying access to IPC$ from potentially untrustworthy
-hosts.</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
->To do that you could use:</P
+>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="AEN3672"
+>21.3.1. DatabaseFS</A
+></H3
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->  [ipc$]
-     hosts allow = 192.168.115.0/24 127.0.0.1
-     hosts deny = 0.0.0.0/0</PRE
+>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
->this would tell Samba that IPC$ connections are not allowed from
-anywhere but the two listed places (localhost and a local
-subnet). Connections to other shares would still be allowed. As the
-IPC$ share is the only share that is always accessible anonymously
-this provides some level of protection against attackers that do not
-know a username/password for your host.</P
+>By <A
+HREF="mailto:elorimer@css.tayloru.edu"
+TARGET="_top"
+>Eric Lorimer</A
+>.</P
 ><P
->If you use this method then clients will be given a 'access denied'
-reply when they try to access the IPC$ share. That means that those
-clients will not be able to browse shares, and may also be unable to
-access some other resources. </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
->This is not recommended unless you cannot use one of the other
-methods listed above for some reason.</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="AEN4041"
->24.6. Upgrading Samba</A
-></H2
+NAME="AEN3680"
+>21.3.2. vscan</A
+></H3
 ><P
->Please check regularly on <A
-HREF="http://www.samba.org/"
+>URL: <A
+HREF="http://www.openantivirus.org/"
 TARGET="_top"
->http://www.samba.org/</A
-> for updates and
-important announcements.  Occasionally security releases are made and 
-it is highly recommended to upgrade Samba when a security vulnerability
-is discovered.</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
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="UNICODE"
+NAME="MSDFS"
 ></A
->Chapter 25. Unicode/Charsets</H1
+>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</H1
 ><DIV
 CLASS="SECT1"
 ><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4056"
->25.1. What are charsets and unicode?</A
+NAME="AEN3696"
+>22.1. Instructions</A
 ></H2
 ><P
->Computers communicate in numbers. In texts, each number will be 
-translated to a corresponding letter. The meaning that will be assigned 
-to a certain number depends on the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->character set(charset)</I
-></SPAN
-> that is used. 
-A charset can be seen as a table that is used to translate numbers to 
-letters. Not all computers use the same charset (there are charsets 
-with German umlauts, Japanese characters, etc). Usually a charset contains 
-256 characters, which means that storing a character with it takes 
-exactly one byte. </P
+>The Distributed File System (or Dfs) provides a means of 
+	separating the logical view of files and directories that users 
+	see from the actual physical locations of these resources on the 
+	network. It allows for higher availability, smoother storage expansion, 
+	load balancing etc. For more information about Dfs, refer to  <A
+HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
+TARGET="_top"
+>	Microsoft documentation</A
+>. </P
 ><P
->There are also charsets that support even more characters, 
-but those need twice(or even more) as much storage space. These 
-charsets can contain <B
-CLASS="COMMAND"
->256 * 256 = 65536</B
-> characters, which
-is more then all possible characters one could think of. They are called 
-multibyte charsets (because they use more then one byte to 
-store one character). </P
+>This document explains how to host a Dfs tree on a Unix 
+	machine (for Dfs-aware clients to browse) using Samba.</P
 ><P
->A standardised multibyte charset is unicode, info available at 
-<A
-HREF="http://www.unicode.org/"
+>To enable SMB-based DFS for Samba, configure it with the 
+	<VAR
+CLASS="PARAMETER"
+>--with-msdfs</VAR
+> option. Once built, a 
+	Samba server can be made a Dfs server by setting the global 
+	boolean <A
+HREF="smb.conf.5.html#HOSTMSDFS"
 TARGET="_top"
->www.unicode.org</A
->. 
-Big advantage of using a multibyte charset is that you only need one; no 
-need to make sure two computers use the same charset when they are 
-communicating.</P
+><VAR
+CLASS="PARAMETER"
+>	host msdfs</VAR
+></A
+> parameter in the <TT
+CLASS="FILENAME"
+>smb.conf
+	</TT
+> file. You designate a share as a Dfs root using the share 
+	level boolean <A
+HREF="smb.conf.5.html#MSDFSROOT"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>	msdfs root</VAR
+></A
+> parameter. A Dfs root directory on 
+	Samba hosts Dfs links in the form of symbolic links that point 
+	to other servers. For example, a symbolic link
+	<TT
+CLASS="FILENAME"
+>junction-&#62;msdfs:storage1\share1</TT
+> in 
+	the share directory acts as the Dfs junction. When Dfs-aware 
+	clients attempt to access the junction link, they are redirected 
+	to the storage location (in this case, \\storage1\share1).</P
 ><P
->Old windows clients used to use single-byte charsets, named 
-'codepages' by microsoft. However, there is no support for 
-negotiating the charset to be used in the smb protocol. Thus, you 
-have to make sure you are using the same charset when talking to an old client.
-Newer clients (Windows NT, 2K, XP) talk unicode over the wire.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4065"
->25.2. Samba and charsets</A
-></H2
+>Dfs trees on Samba work with all Dfs-aware clients ranging 
+	from Windows 95 to 2000.</P
 ><P
->As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, 
-samba knows of three kinds of character sets: </P
+>Here's an example of setting up a Dfs tree on a Samba 
+	server.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+># The smb.conf file:
+[global]
+	netbios name = SAMBA
+	host msdfs   = yes
+
+[dfs]
+	path = /export/dfsroot
+	msdfs root = yes
+	</PRE
+></P
+><P
+>In the /export/dfsroot directory we set up our dfs links to 
+	other servers on the network.</P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>cd /export/dfsroot</KBD
+></P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>chown root /export/dfsroot</KBD
+></P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>chmod 755 /export/dfsroot</KBD
+></P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>ln -s msdfs:storageA\\shareA linka</KBD
+></P
 ><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>ln -s msdfs:serverB\\share,serverC\\share linkb</KBD
 ></P
+><P
+>You should set up the permissions and ownership of 
+	the directory acting as the Dfs root such that only designated 
+	users can create, delete or modify the msdfs links. Also note 
+	that symlink names should be all lowercase. This limitation exists 
+	to have Samba avoid trying all the case combinations to get at 
+	the link name. Finally set up the symbolic links to point to the 
+	network shares you want, and start Samba.</P
+><P
+>Users on Dfs-aware clients can now browse the Dfs tree 
+	on the Samba server at \\samba\dfs. Accessing 
+	links linka or linkb (which appear as directories to the client) 
+	takes users directly to the appropriate shares on the network.</P
 ><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
->unix charset</DT
-><DD
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3731"
+>22.1.1. Notes</A
+></H3
 ><P
->		This is the charset used internally by your operating system. 
-		The default is <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->ASCII</I
-></SPAN
->, which is fine for most 
-		systems.
-		</P
-></DD
-><DT
->display charset</DT
-><DD
+></P
+><UL
+><LI
 ><P
->This is the charset samba will use to print messages
-		on your screen. It should generally be the same as the <B
-CLASS="COMMAND"
->unix charset</B
->.
-		</P
-></DD
-><DT
->dos charset</DT
-><DD
+>Windows clients need to be rebooted 
+			if a previously mounted non-dfs share is made a dfs 
+			root or vice versa. A better way is to introduce a 
+			new share and make it the dfs root.</P
+></LI
+><LI
 ><P
->This is the charset samba uses when communicating with 
-		DOS and Windows 9x clients. It will talk unicode to all newer clients.
-		The default depends on the charsets you have installed on your system.
-		Run <B
-CLASS="COMMAND"
->testparm -v | grep "dos charset"</B
-> to see 
-		what the default is on your system. 
-		</P
-></DD
-></DL
-></DIV
+>Currently there's a restriction that msdfs 
+			symlink names should all be lowercase.</P
+></LI
+><LI
+><P
+>For security purposes, the directory 
+			acting as the root of the Dfs tree should have ownership 
+			and permissions set so that only designated users can 
+			modify the symbolic links in the directory.</P
+></LI
+></UL
 ></DIV
 ></DIV
 ></DIV
 ><DIV
-CLASS="PART"
-><A
-NAME="APPENDIXES"
-></A
-><DIV
-CLASS="TITLEPAGE"
-><H1
-CLASS="TITLE"
->IV. Appendixes</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->26. <A
-HREF="#SWAT"
->SWAT - The Samba Web Admininistration Tool</A
-></DT
-><DD
-><DL
-><DT
->26.1. <A
-HREF="#AEN4098"
->SWAT Features and Benefits</A
-></DT
-><DD
-><DL
-><DT
->26.1.1. <A
-HREF="#AEN4101"
->The SWAT Home Page</A
-></DT
-><DT
->26.1.2. <A
-HREF="#AEN4104"
->Global Settings</A
-></DT
-><DT
->26.1.3. <A
-HREF="#AEN4107"
->The SWAT Wizard</A
-></DT
-><DT
->26.1.4. <A
-HREF="#AEN4110"
->Share Settings</A
-></DT
-><DT
->26.1.5. <A
-HREF="#AEN4113"
->Printing Settings</A
-></DT
-><DT
->26.1.6. <A
-HREF="#AEN4116"
->The Status Page</A
-></DT
-><DT
->26.1.7. <A
-HREF="#AEN4119"
->The Password Change Page</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->27. <A
-HREF="#NT4MIGRATION"
->Migration from NT4 PDC to Samba-3 PDC</A
-></DT
-><DD
-><DL
-><DT
->27.1. <A
-HREF="#AEN4134"
->Planning and Getting Started</A
-></DT
-><DD
-><DL
-><DT
->27.1.1. <A
-HREF="#AEN4137"
->Objectives</A
-></DT
-><DT
->27.1.2. <A
-HREF="#AEN4140"
->Steps In Migration Process</A
-></DT
-></DL
-></DD
-><DT
->27.2. <A
-HREF="#AEN4143"
->Managing Samba-3 Domain Control</A
-></DT
-></DL
-></DD
-><DT
->28. <A
-HREF="#SPEED"
->Samba performance issues</A
-></DT
-><DD
-><DL
-><DT
->28.1. <A
-HREF="#AEN4163"
->Comparisons</A
-></DT
-><DT
->28.2. <A
-HREF="#AEN4169"
->Socket options</A
-></DT
-><DT
->28.3. <A
-HREF="#AEN4176"
->Read size</A
-></DT
-><DT
->28.4. <A
-HREF="#AEN4181"
->Max xmit</A
-></DT
-><DT
->28.5. <A
-HREF="#AEN4186"
->Log level</A
-></DT
-><DT
->28.6. <A
-HREF="#AEN4189"
->Read raw</A
-></DT
-><DT
->28.7. <A
-HREF="#AEN4194"
->Write raw</A
-></DT
-><DT
->28.8. <A
-HREF="#AEN4198"
->Slow Clients</A
-></DT
-><DT
->28.9. <A
-HREF="#AEN4202"
->Slow Logins</A
-></DT
-><DT
->28.10. <A
-HREF="#AEN4205"
->Client tuning</A
-></DT
-></DL
-></DD
-><DT
->29. <A
-HREF="#PORTABILITY"
->Portability</A
-></DT
-><DD
-><DL
-><DT
->29.1. <A
-HREF="#AEN4249"
->HPUX</A
-></DT
-><DT
->29.2. <A
-HREF="#AEN4255"
->SCO Unix</A
-></DT
-><DT
->29.3. <A
-HREF="#AEN4259"
->DNIX</A
-></DT
-><DT
->29.4. <A
-HREF="#AEN4288"
->RedHat Linux Rembrandt-II</A
-></DT
-><DT
->29.5. <A
-HREF="#AEN4294"
->AIX</A
-></DT
-><DD
-><DL
-><DT
->29.5.1. <A
-HREF="#AEN4296"
->Sequential Read Ahead</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->30. <A
-HREF="#OTHER-CLIENTS"
->Samba and other CIFS clients</A
-></DT
-><DD
-><DL
-><DT
->30.1. <A
-HREF="#AEN4319"
->Macintosh clients?</A
-></DT
-><DT
->30.2. <A
-HREF="#AEN4328"
->OS2 Client</A
-></DT
-><DD
-><DL
-><DT
->30.2.1. <A
-HREF="#AEN4330"
->How can I configure OS/2 Warp Connect or 
-		OS/2 Warp 4 as a client for Samba?</A
-></DT
-><DT
->30.2.2. <A
-HREF="#AEN4345"
->How can I configure OS/2 Warp 3 (not Connect), 
-		OS/2 1.2, 1.3 or 2.x for Samba?</A
-></DT
-><DT
->30.2.3. <A
-HREF="#AEN4354"
->Are there any other issues when OS/2 (any version) 
-		is used as a client?</A
-></DT
-><DT
->30.2.4. <A
-HREF="#AEN4358"
->How do I get printer driver download working 
-		for OS/2 clients?</A
-></DT
-></DL
-></DD
-><DT
->30.3. <A
-HREF="#AEN4368"
->Windows for Workgroups</A
-></DT
-><DD
-><DL
-><DT
->30.3.1. <A
-HREF="#AEN4370"
->Use latest TCP/IP stack from Microsoft</A
-></DT
-><DT
->30.3.2. <A
-HREF="#AEN4375"
->Delete .pwl files after password change</A
-></DT
-><DT
->30.3.3. <A
-HREF="#AEN4380"
->Configure WfW password handling</A
-></DT
-><DT
->30.3.4. <A
-HREF="#AEN4384"
->Case handling of passwords</A
-></DT
-><DT
->30.3.5. <A
-HREF="#AEN4389"
->Use TCP/IP as default protocol</A
-></DT
-></DL
-></DD
-><DT
->30.4. <A
-HREF="#AEN4392"
->Windows '95/'98</A
-></DT
-><DT
->30.5. <A
-HREF="#AEN4408"
->Windows 2000 Service Pack 2</A
-></DT
-><DT
->30.6. <A
-HREF="#AEN4425"
->Windows NT 3.1</A
-></DT
-></DL
-></DD
-><DT
->31. <A
-HREF="#COMPILING"
->How to compile SAMBA</A
-></DT
-><DD
-><DL
-><DT
->31.1. <A
-HREF="#AEN4446"
->Access Samba source code via CVS</A
-></DT
-><DD
-><DL
-><DT
->31.1.1. <A
-HREF="#AEN4448"
->Introduction</A
-></DT
-><DT
->31.1.2. <A
-HREF="#AEN4453"
->CVS Access to samba.org</A
-></DT
-></DL
-></DD
-><DT
->31.2. <A
-HREF="#AEN4489"
->Accessing the samba sources via rsync and ftp</A
-></DT
-><DT
->31.3. <A
-HREF="#AEN4495"
->Building the Binaries</A
-></DT
-><DD
-><DL
-><DT
->31.3.1. <A
-HREF="#AEN4523"
->Compiling samba with Active Directory support</A
-></DT
-></DL
-></DD
-><DT
->31.4. <A
-HREF="#AEN4552"
->Starting the smbd and nmbd</A
-></DT
-><DD
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="INTEGRATE-MS-NETWORKS"
+></A
+>Chapter 23. Integrating MS Windows networks with Samba</H1
+><P
+>This section deals with NetBIOS over TCP/IP name to IP address resolution. If you
+your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
+section does not apply to your installation. If your installation involves use of
+NetBIOS over TCP/IP then this section may help you to resolve networking problems.</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
+>	NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
+	over Logical Link Control (LLC). On modern networks it is highly advised
+	to NOT run NetBEUI at all. Note also that there is NO such thing as
+	NetBEUI over TCP/IP - the existence of such a protocol is a complete
+	and utter mis-apprehension.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Since the introduction of MS Windows 2000 it is possible to run MS Windows networking
+without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
+name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
+TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be
+used and UDP port 137 and TCP port 139 will not.</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
+>When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then
+the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
+Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that
+disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires
+Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
+Use of DHCP with ADS is recommended as a further means of maintaining central control
+over client workstation network configuration.</P
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3759"
+>23.1. Name Resolution in a pure Unix/Linux world</A
+></H2
+><P
+>The key configuration files covered in this section are:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></P
+></LI
+></UL
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3775"
+>23.1.1. <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></A
+></H3
+><P
+>Contains a static list of IP Addresses and names.
+eg:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	127.0.0.1	localhost localhost.localdomain
+	192.168.1.1	bigbox.caldera.com	bigbox	alias4box</PRE
+></P
+><P
+>The purpose of <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> is to provide a 
+name resolution mechanism so that uses do not need to remember 
+IP addresses.</P
+><P
+>Network packets that are sent over the physical network transport 
+layer communicate not via IP addresses but rather using the Media 
+Access Control address, or MAC address. IP Addresses are currently 
+32 bits in length and are typically presented as four (4) decimal 
+numbers that are separated by a dot (or period). eg: 168.192.1.1</P
+><P
+>MAC Addresses use 48 bits (or 6 bytes) and are typically represented 
+as two digit hexadecimal numbers separated by colons. eg: 
+40:8e:0a:12:34:56</P
+><P
+>Every network interfrace must have an MAC address. Associated with 
+a MAC address there may be one or more IP addresses. There is NO 
+relationship between an IP address and a MAC address, all such assignments 
+are arbitary or discretionary in nature. At the most basic level all 
+network communications takes place using MAC addressing. Since MAC 
+addresses must be globally unique, and generally remains fixed for 
+any particular interface, the assignment of an IP address makes sense 
+from a network management perspective. More than one IP address can 
+be assigned per MAC address. One address must be the primary IP address, 
+this is the address that will be returned in the ARP reply.</P
+><P
+>When a user or a process wants to communicate with another machine 
+the protocol implementation ensures that the "machine name" or "host 
+name" is resolved to an IP address in a manner that is controlled 
+by the TCP/IP configuration control files. The file 
+<TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> is one such file.</P
+><P
+>When the IP address of the destination interface has been 
+determined a protocol called ARP/RARP is used to identify 
+the MAC address of the target interface. ARP stands for Address 
+Resolution Protocol, and is a broadcast oriented method that 
+uses UDP (User Datagram Protocol) to send a request to all 
+interfaces on the local network segment using the all 1's MAC 
+address. Network interfaces are programmed to respond to two 
+MAC addresses only; their own unique address and the address 
+ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will 
+contain the MAC address and the primary IP address for each 
+interface.</P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file is foundational to all 
+Unix/Linux TCP/IP installations and as a minumum will contain 
+the localhost and local network interface IP addresses and the 
+primary names by which they are known within the local machine. 
+This file helps to prime the pump so that a basic level of name 
+resolution can exist before any other method of name resolution 
+becomes available.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3791"
+>23.1.2. <TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></A
+></H3
+><P
+>This file tells the name resolution libraries:</P
+><P
+></P
+><UL
+><LI
+><P
+>The name of the domain to which the machine 
+	belongs
+	</P
+></LI
+><LI
+><P
+>The name(s) of any domains that should be 
+	automatically searched when trying to resolve unqualified 
+	host names to their IP address
+	</P
+></LI
+><LI
+><P
+>The name or IP address of available Domain 
+	Name Servers that may be asked to perform name to address 
+	translation lookups
+	</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3802"
+>23.1.3. <TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></A
+></H3
+><P
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+> is the primary means by 
+which the setting in /etc/resolv.conf may be affected. It is a 
+critical configuration file.  This file controls the order by 
+which name resolution may procede. The typical structure is:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	order hosts,bind
+	multi on</PRE
+></P
+><P
+>then both addresses should be returned. Please refer to the 
+man page for host.conf for further details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3810"
+>23.1.4. <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></A
+></H3
+><P
+>This file controls the actual name resolution targets. The 
+file typically has resolver object specifications as follows:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	# /etc/nsswitch.conf
+	#
+	# Name Service Switch configuration file.
+	#
+
+	passwd:		compat
+	# Alternative entries for password authentication are:
+	# passwd:	compat files nis ldap winbind
+	shadow:		compat
+	group:		compat
+
+	hosts:		files nis dns
+	# Alternative entries for host name resolution are:
+	# hosts:	files dns nis nis+ hesoid db compat ldap wins
+	networks:	nis files dns
+
+	ethers:		nis files
+	protocols:	nis files
+	rpc:		nis files
+	services:	nis files</PRE
+></P
+><P
+>Of course, each of these mechanisms requires that the appropriate 
+facilities and/or services are correctly configured.</P
+><P
+>It should be noted that unless a network request/message must be 
+sent, TCP/IP networks are silent. All TCP/IP communications assumes a 
+principal of speaking only when necessary.</P
+><P
+>Starting with version 2.2.0 samba has Linux support for extensions to 
+the name service switch infrastructure so that linux clients will 
+be able to obtain resolution of MS Windows NetBIOS names to IP 
+Addresses. To gain this functionality Samba needs to be compiled 
+with appropriate arguments to the make command (ie: <B
+CLASS="COMMAND"
+>make 
+nsswitch/libnss_wins.so</B
+>). The resulting library should 
+then be installed in the <TT
+CLASS="FILENAME"
+>/lib</TT
+> directory and 
+the "wins" parameter needs to be added to the "hosts:" line in 
+the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file. At this point it 
+will be possible to ping any MS Windows machine by it's NetBIOS 
+machine name, so long as that machine is within the workgroup to 
+which both the samba machine and the MS Windows machine belong.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3822"
+>23.2. Name resolution as used within MS Windows networking</A
+></H2
+><P
+>MS Windows networking is predicated about the name each machine 
+is given. This name is known variously (and inconsistently) as 
+the "computer name", "machine name", "networking name", "netbios name", 
+"SMB name". All terms mean the same thing with the exception of 
+"netbios name" which can apply also to the name of the workgroup or the 
+domain name. The terms "workgroup" and "domain" are really just a 
+simply name with which the machine is associated. All NetBIOS names 
+are exactly 16 characters in length. The 16th character is reserved. 
+It is used to store a one byte value that indicates service level 
+information for the NetBIOS name that is registered. A NetBIOS machine 
+name is therefore registered for each service type that is provided by 
+the client/server.</P
+><P
+>The following are typical NetBIOS name/service type registrations:</P
+><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
+
+	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
+></P
+><P
+>It should be noted that all NetBIOS machines register their own 
+names as per the above. This is in vast contrast to TCP/IP 
+installations where traditionally the system administrator will 
+determine in the /etc/hosts or in the DNS database what names 
+are associated with each IP address.</P
+><P
+>One further point of clarification should be noted, the <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> 
+file and the DNS records do not provide the NetBIOS name type information 
+that MS Windows clients depend on to locate the type of service that may 
+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 
+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
+>The name "workgroup" or "domain" really can be confusing since these 
+have the added significance of indicating what is the security 
+architecture of the MS Windows network. The term "workgroup" indicates 
+that the primary nature of the network environment is that of a 
+peer-to-peer design. In a WORKGROUP all machines are responsible for 
+their own security, and generally such security is limited to use of 
+just a password (known as SHARE MODE security). In most situations 
+with peer-to-peer networking the users who control their own machines 
+will simply opt to have no security at all. It is possible to have 
+USER MODE security in a WORKGROUP environment, thus requiring use 
+of a user name and a matching password.</P
+><P
+>MS Windows networking is thus predetermined to use machine names 
+for all local and remote machine message passing. The protocol used is 
+called Server Message Block (SMB) and this is implemented using 
+the NetBIOS protocol (Network Basic Input Output System). NetBIOS can 
+be encapsulated using LLC (Logical Link Control) protocol - in which case 
+the resulting protocol is called NetBEUI (Network Basic Extended User 
+Interface). NetBIOS can also be run over IPX (Internetworking Packet 
+Exchange) protocol as used by Novell NetWare, and it can be run 
+over TCP/IP protocols - in which case the resulting protocol is called 
+NBT or NetBT, the NetBIOS over TCP/IP.</P
+><P
+>MS Windows machines use a complex array of name resolution mechanisms. 
+Since we are primarily concerned with TCP/IP this demonstration is 
+limited to this area.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3834"
+>23.2.1. The NetBIOS Name Cache</A
+></H3
+><P
+>All MS Windows machines employ an in memory buffer in which is 
+stored the NetBIOS names and IP addresses for all external 
+machines that that machine has communicated with over the 
+past 10-15 minutes. It is more efficient to obtain an IP address 
+for a machine from the local cache than it is to go through all the 
+configured name resolution mechanisms.</P
+><P
+>If a machine whose name is in the local name cache has been shut 
+down before the name had been expired and flushed from the cache, then 
+an attempt to exchange a message with that machine will be subject 
+to time-out delays. i.e.: Its name is in the cache, so a name resolution 
+lookup will succeed, but the machine can not respond. This can be 
+frustrating for users - but it is a characteristic of the protocol.</P
+><P
+>The MS Windows utility that allows examination of the NetBIOS 
+name cache is called "nbtstat". The Samba equivalent of this 
+is called "nmblookup".</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3839"
+>23.2.2. The LMHOSTS file</A
+></H3
+><P
+>This file is usually located in MS Windows NT 4.0 or 
+2000 in <TT
+CLASS="FILENAME"
+>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
+> and contains 
+the IP Address and the machine name in matched pairs. The 
+<TT
+CLASS="FILENAME"
+>LMHOSTS</TT
+> file performs NetBIOS name 
+to IP address mapping oriented.</P
+><P
+>It typically looks like:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	# Copyright (c) 1998 Microsoft Corp.
+	#
+	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+	# over TCP/IP) stack for Windows98
+	#
+	# This file contains the mappings of IP addresses to NT computernames
+	# (NetBIOS) names.  Each entry should be kept on an individual line.
+	# The IP address should be placed in the first column followed by the
+	# corresponding computername. The address and the comptername
+	# should be separated by at least one space or tab. The "#" character
+	# is generally used to denote the start of a comment (see the exceptions
+	# below).
+	#
+	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+	# files and offers the following extensions:
+	#
+	#      #PRE
+	#      #DOM:&#60;domain&#62;
+	#      #INCLUDE &#60;filename&#62;
+	#      #BEGIN_ALTERNATE
+	#      #END_ALTERNATE
+	#      \0xnn (non-printing character support)
+	#
+	# Following any entry in the file with the characters "#PRE" will cause
+	# the entry to be preloaded into the name cache. By default, entries are
+	# not preloaded, but are parsed only after dynamic name resolution fails.
+	#
+	# Following an entry with the "#DOM:&#60;domain&#62;" tag will associate the
+	# entry with the domain specified by &#60;domain&#62;. This affects how the
+	# browser and logon services behave in TCP/IP environments. To preload
+	# the host name associated with #DOM entry, it is necessary to also add a
+	# #PRE to the line. The &#60;domain&#62; is always preloaded although it will not
+	# be shown when the name cache is viewed.
+	#
+	# Specifying "#INCLUDE &#60;filename&#62;" will force the RFC NetBIOS (NBT)
+	# software to seek the specified &#60;filename&#62; and parse it as if it were
+	# local. &#60;filename&#62; is generally a UNC-based name, allowing a
+	# centralized lmhosts file to be maintained on a server.
+	# It is ALWAYS necessary to provide a mapping for the IP address of the
+	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+	# In addtion the share "public" in the example below must be in the
+	# LanManServer list of "NullSessionShares" in order for client machines to
+	# be able to read the lmhosts file successfully. This key is under
+	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
+	# in the registry. Simply add "public" to the list found there.
+	#
+	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+	# statements to be grouped together. Any single successful include
+	# will cause the group to succeed.
+	#
+	# Finally, non-printing characters can be embedded in mappings by
+	# first surrounding the NetBIOS name in quotations, then using the
+	# \0xnn notation to specify a hex value for a non-printing character.
+	#
+	# The following example illustrates all of these extensions:
+	#
+	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
+	# 102.54.94.102    "appname  \0x14"                    #special app server
+	# 102.54.94.123    popular            #PRE             #source server
+	# 102.54.94.117    localsrv           #PRE             #needed for the include
+	#
+	# #BEGIN_ALTERNATE
+	# #INCLUDE \\localsrv\public\lmhosts
+	# #INCLUDE \\rhino\public\lmhosts
+	# #END_ALTERNATE
+	#
+	# In the above example, the "appname" server contains a special
+	# character in its name, the "popular" and "localsrv" server names are
+	# preloaded, and the "rhino" server name is specified so it can be used
+	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+	# system is unavailable.
+	#
+	# Note that the whole file is parsed including comments on each lookup,
+	# so keeping the number of comments to a minimum will improve performance.
+	# Therefore it is not advisable to simply add lmhosts file entries onto the
+	# end of this file.</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3847"
+>23.2.3. HOSTS file</A
+></H3
+><P
+>This file is usually located in MS Windows NT 4.0 or 2000 in 
+<TT
+CLASS="FILENAME"
+>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
+> and contains 
+the IP Address and the IP hostname in matched pairs. It can be 
+used by the name resolution infrastructure in MS Windows, depending 
+on how the TCP/IP environment is configured. This file is in 
+every way the equivalent of the Unix/Linux <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3852"
+>23.2.4. DNS Lookup</A
+></H3
+><P
+>This capability is configured in the TCP/IP setup area in the network 
+configuration facility. If enabled an elaborate name resolution sequence 
+is followed the precise nature of which isdependant on what the NetBIOS 
+Node Type parameter is configured to. A Node Type of 0 means use 
+NetBIOS broadcast (over UDP broadcast) is first used if the name 
+that is the subject of a name lookup is not found in the NetBIOS name 
+cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to 
+Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the 
+WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast 
+lookup is used.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3855"
+>23.2.5. WINS Lookup</A
+></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 
+the names and IP addresses that are registered by a Windows client 
+if the TCP/IP setup has been given at least one WINS Server IP Address.</P
+><P
+>To configure Samba to be a WINS server the following parameter needs 
+to be added to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	wins support = Yes</PRE
+></P
+><P
+>To configure Samba to use a WINS server the following parameters are 
+needed in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	wins support = No
+	wins server = xxx.xxx.xxx.xxx</PRE
+></P
+><P
+>where <VAR
+CLASS="REPLACEABLE"
+>xxx.xxx.xxx.xxx</VAR
+> is the IP address 
+of the WINS server.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="IMPROVED-BROWSING"
+></A
+>Chapter 24. Improved browsing in samba</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3875"
+>24.1. Overview of browsing</A
+></H2
+><P
+>SMB networking provides a mechanism by which clients can access a list
+of machines in a network, a so-called <B
+CLASS="COMMAND"
+>browse list</B
+>.  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
+>MS Windows 2000 and later, as with Samba 3 and later, can be
+configured to not use NetBIOS over TCP/IP. When configured this way
+it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
+configured and operative. Browsing will NOT work if name resolution
+from SMB machine names to IP addresses does not function correctly.</P
+><P
+>Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
+recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
+WINS allows remote segment clients to obtain NetBIOS name_type information
+that can NOT be provided by any other means of name resolution.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3881"
+>24.2. Browsing support in samba</A
+></H2
+><P
+>Samba facilitates browsing.  The browsing is supported by <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+>
+and is also controlled by options in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
+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.</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
+><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
+>Nmbd can be configured as a WINS server, but it is not
+necessary to specifically use samba as your WINS server.  MS Windows
+NT4, Server or Advanced Server 2000 or 2003 can be configured as
+your WINS server.  In a mixed NT/2000/2003 server and samba environment on
+a Wide Area Network, it is recommended that you use the Microsoft
+WINS server capabilities.  In a samba-only environment, it is
+recommended that you use one and only one Samba server as your WINS server.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>To get browsing to work you need to run nmbd as usual, but will need
+to use the <B
+CLASS="COMMAND"
+>workgroup</B
+> option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+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 <B
+CLASS="COMMAND"
+>remote announce</B
+> in the 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> man page.  </P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3896"
+>24.3. Problem resolution</A
+></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 <TT
+CLASS="FILENAME"
+>browse.dat</TT
+>.</P
+><P
+>Note that if it doesn't work for you, then you should still be able to
+type the server name as <TT
+CLASS="FILENAME"
+>\\SERVER</TT
+> 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
+<B
+CLASS="COMMAND"
+>guest account</B
+> 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
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>MS Windows 2000 and upwards (as with Samba) can be configured to disallow
+anonymous (ie: Guest account) access to the IPC$ share. In that case, the
+MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
+name of the currently logged in user to query the IPC$ share. MS Windows
+9X clients are not able to do this and thus will NOT be able to browse
+server resources.</I
+></SPAN
+></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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>)</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3908"
+>24.4. Browsing across subnets</A
+></H2
+><P
+>Since the release of Samba 1.9.17(alpha1) 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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3914"
+>24.4.1. How does cross subnet browsing work ?</A
+></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.
+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&#62;1B&#60;.  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="AEN3949"
+>24.5. Setting up a WINS server</A
+></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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 prior to 1.9.17 had this parameter default to
+yes.  If you have any older versions of Samba on your network it is
+strongly suggested you upgrade to a recent version, or at the very
+least set the parameter to 'no' on all these machines.</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 
+<B
+CLASS="COMMAND"
+>wins support = yes</B
+> 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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> files :</P
+><P
+><B
+CLASS="COMMAND"
+>wins server = &#62;name or IP address&#60;</B
+></P
+><P
+>where &#62;name or IP address&#60; 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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 = &#60;name&#62;</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="AEN3972"
+>24.6. Setting up Browsing in a WORKGROUP</A
+></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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 MS Windows NT/2K/XP/2003  machine should be
+able to do this, as will Windows 9x 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
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 <B
+CLASS="COMMAND"
+>local master</B
+> parameter allows Samba to act as a
+local master browser.  The <B
+CLASS="COMMAND"
+>preferred master</B
+> causes nmbd
+to force a browser election on startup and the <B
+CLASS="COMMAND"
+>os level</B
+>
+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 <B
+CLASS="COMMAND"
+>[global]</B
+> section of the 
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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="AEN3998"
+>24.7. Setting up Browsing in a DOMAIN</A
+></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 (<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>&#60;1B&#62;)
+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 <B
+CLASS="COMMAND"
+>[global]</B
+> section 
+of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 <B
+CLASS="COMMAND"
+>os level</B
+> 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 <A
+HREF="#BROWSE-FORCE-MASTER"
+>Forcing samba to be the master browser</A
+>
+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 <B
+CLASS="COMMAND"
+>[global]</B
+> section of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+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="BROWSE-FORCE-MASTER"
+>24.8. Forcing samba to be the master</A
+></H2
+><P
+>Who becomes the <B
+CLASS="COMMAND"
+>master browser</B
+> 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 <B
+CLASS="COMMAND"
+>os level</B
+> global
+option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 <B
+CLASS="COMMAND"
+>os level</B
+> of 2 would make it beat WfWg and Win95, but not MS Windows
+NT/2K Server.  A MS Windows NT/2K Server domain controller uses level 32.</P
+><P
+>The maximum os level is 255</P
+><P
+>If you want samba to force an election on startup, then set the
+<B
+CLASS="COMMAND"
+>preferred master</B
+> global option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> 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 <B
+CLASS="COMMAND"
+>preferred master</B
+> 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 <B
+CLASS="COMMAND"
+>domain master browser</B
+>, then it is
+recommended that you also set <B
+CLASS="COMMAND"
+>preferred master</B
+> 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="AEN4033"
+>24.9. Making samba the domain master</A
+></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 <B
+CLASS="COMMAND"
+>domain master = yes</B
+>
+in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.  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 <B
+CLASS="COMMAND"
+>os level</B
+> high enough to make sure it wins elections, and set
+<B
+CLASS="COMMAND"
+>preferred master</B
+> 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="AEN4055"
+>24.10. Note about broadcast addresses</A
+></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="AEN4058"
+>24.11. Multiple interfaces</A
+></H2
+><P
+>Samba now supports machines with multiple network interfaces.  If you
+have multiple interfaces then you will need to use the <B
+CLASS="COMMAND"
+>interfaces</B
+>
+option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> to configure them. </P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="SECURING-SAMBA"
+></A
+>Chapter 25. Securing Samba</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN4074"
+>25.1. Introduction</A
+></H2
+><P
+>This note was attached to the Samba 2.2.8 release notes as it contained an
+important security fix.  The information contained here applies to Samba
+installations in general.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4077"
+>25.2. Using host based protection</A
+></H2
+><P
+>In many installations of Samba the greatest threat comes for outside
+your immediate network. By default Samba will accept connections from
+any host, which means that if you run an insecure version of Samba on
+a host that is directly connected to the Internet you can be
+especially vulnerable.</P
+><P
+>One of the simplest fixes in this case is to use the <B
+CLASS="COMMAND"
+>hosts allow</B
+> and
+<B
+CLASS="COMMAND"
+>hosts deny</B
+> options in the Samba <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> configuration file to only
+allow access to your server from a specific range of hosts. An example
+might be:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
+  hosts deny = 0.0.0.0/0</PRE
+></P
+><P
+>The above will only allow SMB connections from 'localhost' (your own
+computer) and from the two private networks 192.168.2 and
+192.168.3. All other connections will be refused connections as soon
+as the client sends its first packet. The refusal will be marked as a
+'not listening on called name' error.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4087"
+>25.3. Using interface protection</A
+></H2
+><P
+>By default Samba will accept connections on any network interface that
+it finds on your system. That means if you have a ISDN line or a PPP
+connection to the Internet then Samba will accept connections on those
+links. This may not be what you want.</P
+><P
+>You can change this behaviour using options like the following:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  interfaces = eth* lo
+  bind interfaces only = yes</PRE
+></P
+><P
+>This tells Samba to only listen for connections on interfaces with a
+name starting with 'eth' such as eth0, eth1, plus on the loopback
+interface called 'lo'. The name you will need to use depends on what
+OS you are using, in the above I used the common name for Ethernet
+adapters on Linux.</P
+><P
+>If you use the above and someone tries to make a SMB connection to
+your host over a PPP interface called 'ppp0' then they will get a TCP
+connection refused reply. In that case no Samba code is run at all as
+the operating system has been told not to pass connections from that
+interface to any process.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4095"
+>25.4. Using a firewall</A
+></H2
+><P
+>Many people use a firewall to deny access to services that they don't
+want exposed outside their network. This can be a very good idea,
+although I would recommend using it in conjunction with the above
+methods so that you are protected even if your firewall is not active
+for some reason.</P
+><P
+>If you are setting up a firewall then you need to know what TCP and
+UDP ports to allow and block. Samba uses the following:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>UDP/137    - used by nmbd
+UDP/138    - used by nmbd
+TCP/139    - used by smbd
+TCP/445    - used by smbd</PRE
+></P
+><P
+>The last one is important as many older firewall setups may not be
+aware of it, given that this port was only added to the protocol in
+recent years. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4102"
+>25.5. Using a IPC$ share deny</A
+></H2
+><P
+>If the above methods are not suitable, then you could also place a
+more specific deny on the IPC$ share that is used in the recently
+discovered security hole. This allows you to offer access to other
+shares while denying access to IPC$ from potentially untrustworthy
+hosts.</P
+><P
+>To do that you could use:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>  [ipc$]
+     hosts allow = 192.168.115.0/24 127.0.0.1
+     hosts deny = 0.0.0.0/0</PRE
+></P
+><P
+>this would tell Samba that IPC$ connections are not allowed from
+anywhere but the two listed places (localhost and a local
+subnet). Connections to other shares would still be allowed. As the
+IPC$ share is the only share that is always accessible anonymously
+this provides some level of protection against attackers that do not
+know a username/password for your host.</P
+><P
+>If you use this method then clients will be given a 'access denied'
+reply when they try to access the IPC$ share. That means that those
+clients will not be able to browse shares, and may also be unable to
+access some other resources. </P
+><P
+>This is not recommended unless you cannot use one of the other
+methods listed above for some reason.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4111"
+>25.6. Upgrading Samba</A
+></H2
+><P
+>Please check regularly on <A
+HREF="http://www.samba.org/"
+TARGET="_top"
+>http://www.samba.org/</A
+> for updates and
+important announcements.  Occasionally security releases are made and 
+it is highly recommended to upgrade Samba when a security vulnerability
+is discovered.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="UNICODE"
+></A
+>Chapter 26. Unicode/Charsets</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN4127"
+>26.1. What are charsets and unicode?</A
+></H2
+><P
+>Computers communicate in numbers. In texts, each number will be 
+translated to a corresponding letter. The meaning that will be assigned 
+to a certain number depends on the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>character set(charset)</I
+></SPAN
+> that is used. 
+A charset can be seen as a table that is used to translate numbers to 
+letters. Not all computers use the same charset (there are charsets 
+with German umlauts, Japanese characters, etc). Usually a charset contains 
+256 characters, which means that storing a character with it takes 
+exactly one byte. </P
+><P
+>There are also charsets that support even more characters, 
+but those need twice(or even more) as much storage space. These 
+charsets can contain <B
+CLASS="COMMAND"
+>256 * 256 = 65536</B
+> characters, which
+is more then all possible characters one could think of. They are called 
+multibyte charsets (because they use more then one byte to 
+store one character). </P
+><P
+>A standardised multibyte charset is unicode, info available at 
+<A
+HREF="http://www.unicode.org/"
+TARGET="_top"
+>www.unicode.org</A
+>. 
+Big advantage of using a multibyte charset is that you only need one; no 
+need to make sure two computers use the same charset when they are 
+communicating.</P
+><P
+>Old windows clients used to use single-byte charsets, named 
+'codepages' by microsoft. However, there is no support for 
+negotiating the charset to be used in the smb protocol. Thus, you 
+have to make sure you are using the same charset when talking to an old client.
+Newer clients (Windows NT, 2K, XP) talk unicode over the wire.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4136"
+>26.2. Samba and charsets</A
+></H2
+><P
+>As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, 
+samba knows of three kinds of character sets: </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
 ><DL
 ><DT
->31.4.1. <A
-HREF="#AEN4562"
->Starting from inetd.conf</A
-></DT
-><DT
->31.4.2. <A
-HREF="#AEN4596"
->Alternative: starting it as a daemon</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->32. <A
-HREF="#BUGREPORT"
->Reporting Bugs</A
-></DT
+>unix charset</DT
 ><DD
-><DL
-><DT
->32.1. <A
-HREF="#AEN4627"
->Introduction</A
-></DT
-><DT
->32.2. <A
-HREF="#AEN4637"
->General info</A
-></DT
-><DT
->32.3. <A
-HREF="#AEN4643"
->Debug levels</A
-></DT
-><DT
->32.4. <A
-HREF="#AEN4664"
->Internal errors</A
-></DT
-><DT
->32.5. <A
-HREF="#AEN4678"
->Attaching to a running process</A
-></DT
-><DT
->32.6. <A
-HREF="#AEN4686"
->Patches</A
-></DT
-></DL
+><P
+>		This is the charset used internally by your operating system. 
+		The default is <CODE
+CLASS="CONSTANT"
+>ASCII</CODE
+>, which is fine for most 
+		systems.
+		</P
 ></DD
 ><DT
->33. <A
-HREF="#DIAGNOSIS"
->The samba checklist</A
-></DT
+>display charset</DT
 ><DD
-><DL
-><DT
->33.1. <A
-HREF="#AEN4709"
->Introduction</A
-></DT
-><DT
->33.2. <A
-HREF="#AEN4714"
->Assumptions</A
-></DT
-><DT
->33.3. <A
-HREF="#AEN4733"
->The tests</A
-></DT
+><P
+>This is the charset samba will use to print messages
+		on your screen. It should generally be the same as the <B
+CLASS="COMMAND"
+>unix charset</B
+>.
+		</P
+></DD
 ><DT
->33.4. <A
-HREF="#AEN4900"
->Still having troubles?</A
-></DT
-></DL
+>dos charset</DT
+><DD
+><P
+>This is the charset samba uses when communicating with 
+		DOS and Windows 9x clients. It will talk unicode to all newer clients.
+		The default depends on the charsets you have installed on your system.
+		Run <B
+CLASS="COMMAND"
+>testparm -v | grep "dos charset"</B
+> to see 
+		what the default is on your system. 
+		</P
 ></DD
 ></DL
 ></DIV
 ></DIV
 ><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4155"
+>26.3. Conversion from old names</A
+></H2
+><P
+>Because previous samba versions did not do any charset conversion, 
+characters in filenames are usually not correct in the unix charset but only 
+for the local charset used by the DOS/Windows clients.</P
+><P
+>The following script from Steve Langasek converts all 
+filenames from CP850 to the iso8859-15 charset.</P
+><P
+><SAMP
+CLASS="PROMPT"
+>#</SAMP
+><KBD
+CLASS="USERINPUT"
+>find <VAR
+CLASS="REPLACEABLE"
+>/path/to/share</VAR
+> -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \
+  -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;</KBD
+></P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="APPENDIXES"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>IV. Appendixes</H1
+></DIV
+><DIV
 CLASS="CHAPTER"
 ><HR><H1
 ><A
-NAME="SWAT"
+NAME="COMPILING"
 ></A
->Chapter 26. SWAT - The Samba Web Admininistration Tool</H1
+>Chapter 27. How to compile SAMBA</H1
+><P
+>You can obtain the samba source from the <A
+HREF="http://samba.org/"
+TARGET="_top"
+>samba website</A
+>. To obtain a development version, 
+you can download samba from CVS or using rsync.</P
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4183"
+>27.1. Access Samba source code via CVS</A
+></H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN4185"
+>27.1.1. Introduction</A
+></H3
+><P
+>Samba is developed in an open environment.  Developers use CVS
+(Concurrent Versioning System) to "checkin" (also known as 
+"commit") new source code.  Samba's various CVS branches can
+be accessed via anonymous CVS using the instructions
+detailed in this chapter.</P
+><P
+>This chapter is a modified version of the instructions found at
+<A
+HREF="http://samba.org/samba/cvs.html"
+TARGET="_top"
+>http://samba.org/samba/cvs.html</A
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4190"
+>27.1.2. CVS Access to samba.org</A
+></H3
+><P
+>The machine samba.org runs a publicly accessible CVS 
+repository for access to the source code of several packages, 
+including samba, rsync and jitterbug. There are two main ways of 
+accessing the CVS server on this host.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN4193"
+>27.1.2.1. Access via CVSweb</A
+></H4
+><P
+>You can access the source code via your 
+favourite WWW browser. This allows you to access the contents of 
+individual files in the repository and also to look at the revision 
+history and commit logs of individual files. You can also ask for a diff 
+listing between any two versions on the repository.</P
+><P
+>Use the URL : <A
+HREF="http://samba.org/cgi-bin/cvsweb"
+TARGET="_top"
+>http://samba.org/cgi-bin/cvsweb</A
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN4198"
+>27.1.2.2. Access via cvs</A
+></H4
+><P
+>You can also access the source code via a 
+normal cvs client.  This gives you much more control over you can 
+do with the repository and allows you to checkout whole source trees 
+and keep them up to date via normal cvs commands. This is the 
+preferred method of access if you are a developer and not
+just a casual browser.</P
+><P
+>To download the latest cvs source code, point your
+browser at the URL : <A
+HREF="http://www.cyclic.com/"
+TARGET="_top"
+>http://www.cyclic.com/</A
+>.
+and click on the 'How to get cvs' link. CVS is free software under 
+the GNU GPL (as is Samba).  Note that there are several graphical CVS clients
+which provide a graphical interface to the sometimes mundane CVS commands.
+Links to theses clients are also available from http://www.cyclic.com.</P
+><P
+>To gain access via anonymous cvs use the following steps. 
+For this example it is assumed that you want a copy of the 
+samba source code. For the other source code repositories 
+on this system just substitute the correct package name</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>	Install a recent copy of cvs. All you really need is a 
+	copy of the cvs client binary. 
+	</P
+></LI
+><LI
+><P
+>	Run the command 
+	</P
+><P
+>	<KBD
+CLASS="USERINPUT"
+>cvs -d :pserver:cvs@samba.org:/cvsroot login</KBD
+>
+	</P
+><P
+>	When it asks you for a password type <KBD
+CLASS="USERINPUT"
+>cvs</KBD
+>.
+	</P
+></LI
+><LI
+><P
+>	Run the command 
+	</P
+><P
+>	<KBD
+CLASS="USERINPUT"
+>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</KBD
+>
+	</P
+><P
+>	This will create a directory called samba containing the 
+	latest samba source code (i.e. the HEAD tagged cvs branch). This 
+	currently corresponds to the 3.0 development tree. 
+	</P
+><P
+>	CVS branches other HEAD can be obtained by using the <VAR
+CLASS="PARAMETER"
+>-r</VAR
+>
+	and defining a tag name.  A list of branch tag names can be found on the
+	"Development" page of the samba web site.  A common request is to obtain the
+	latest 2.2 release code.  This could be done by using the following userinput.
+	</P
+><P
+>	<KBD
+CLASS="USERINPUT"
+>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</KBD
+>
+	</P
+></LI
+><LI
+><P
+>	Whenever you want to merge in the latest code changes use 
+	the following command from within the samba directory: 
+	</P
+><P
+>	<KBD
+CLASS="USERINPUT"
+>cvs update -d -P</KBD
+>
+	</P
+></LI
+></OL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4226"
+>27.2. Accessing the samba sources via rsync and ftp</A
+></H2
+><P
+>	pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A
+HREF="ftp://pserver.samba.org/pub/unpacked"
+TARGET="_top"
+>ftp://pserver.samba.org/pub/unpacked</A
+> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp.
+	See <A
+HREF="http://rsync.samba.org/"
+TARGET="_top"
+>the rsync homepage</A
+> for more info on rsync.                       
+	</P
+><P
+>	The disadvantage of the unpacked trees
+	is that they do not support automatic
+	merging of local changes like CVS does.
+	rsync access is most convenient for an 
+	initial install.                       
+	</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4232"
+>27.3. Verifying Samba's PGP signature</A
+></H2
+><P
+>In these days of insecurity, it's strongly recommended that you verify the PGP signature for any
+source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of
+all Samba downloads have had a corresponding PGP signature download (a very low percentage, which
+should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP
+signatures should be a standard reflex.</P
+><P
+>With that said, go ahead and download the following files:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</PRE
+></P
 ><P
->This is a rough guide to SWAT.</P
+>The first file is the PGP signature for the Samba source file; the other is the Samba public
+PGP key itself. Import the public PGP key with:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ gpg --import samba-pubkey.asc</PRE
+><P
+>And verify the Samba source code integrity with:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc</PRE
+><P
+>If you receive a message like, "Good signature from Samba Distribution Verification Key..."
+then all is well. The warnings about trust relationships can be ignored. An example of what
+you would not want to see would be:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     gpg: BAD signature from "Samba Distribution Verification Key"</PRE
+></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4098"
->26.1. SWAT Features and Benefits</A
+NAME="AEN4244"
+>27.4. Building the Binaries</A
 ></H2
 ><P
->You must use at least the following ...</P
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4101"
->26.1.1. The SWAT Home Page</A
-></H3
+>To do this, first run the program <KBD
+CLASS="USERINPUT"
+>./configure
+	</KBD
+> in the source directory. This should automatically 
+	configure Samba for your operating system. If you have unusual 
+	needs then you may wish to run</P
 ><P
->Blah blah here.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4104"
->26.1.2. Global Settings</A
-></H3
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>./configure --help
+	</KBD
+></P
 ><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4107"
->26.1.3. The SWAT Wizard</A
-></H3
+>first to see what special options you can enable.
+	Then executing</P
 ><P
->Lots of blah blah here.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4110"
->26.1.4. Share Settings</A
-></H3
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>make</KBD
+></P
 ><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4113"
->26.1.5. Printing Settings</A
-></H3
+>will create the binaries. Once it's successfully 
+	compiled you can use </P
 ><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4116"
->26.1.6. The Status Page</A
-></H3
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>make install</KBD
+></P
 ><P
->Document steps right here!</P
-></DIV
+>to install the binaries and manual pages. You can 
+	separately install the binaries and/or man pages using</P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>make installbin
+	</KBD
+></P
+><P
+>and</P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>make installman
+	</KBD
+></P
+><P
+>Note that if you are upgrading for a previous version 
+	of Samba you might like to know that the old versions of 
+	the binaries will be renamed with a ".old" extension. You 
+	can go back to the previous version with</P
+><P
+><SAMP
+CLASS="PROMPT"
+>root# </SAMP
+><KBD
+CLASS="USERINPUT"
+>make revert
+	</KBD
+></P
+><P
+>if you find this version a disaster!</P
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4119"
->26.1.7. The Password Change Page</A
+NAME="AEN4272"
+>27.4.1. Compiling samba with Active Directory support</A
 ></H3
 ><P
->Document steps right here!</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="NT4MIGRATION"
-></A
->Chapter 27. Migration from NT4 PDC to Samba-3 PDC</H1
+>In order to compile samba with ADS support, you need to have installed
+	on your system: 
+	<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.</TD
+></TR
+><TR
+><TD
+>the OpenLDAP development libraries.</TD
+></TR
+></TBODY
+></TABLE
 ><P
->This is a rough guide to assist those wishing to migrate from NT4 domain control to
-Samba-3 based domain control.</P
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4134"
->27.1. Planning and Getting Started</A
-></H2
+></P
+></P
 ><P
->You must use at least the following ...</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 <TT
+CLASS="FILENAME"
+>include/config.h</TT
+> it generates contains lines like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#define HAVE_KRB5 1
+#define HAVE_LDAP 1
+		  </PRE
+></P
+><P
+>If it doesn't then configure did not find your krb5 libraries or
+	    your ldap libraries. Look in config.log to figure out why and fix
+		  it.</P
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN4137"
->27.1.1. Objectives</A
-></H3
+NAME="AEN4284"
+>27.4.1.1. Installing the required packages for Debian</A
+></H4
+><P
+>On Debian you need to install the following packages:</P
+><P
+>	<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>libkrb5-dev</TD
+></TR
+><TR
+><TD
+>krb5-user</TD
+></TR
+></TBODY
+></TABLE
 ><P
->Blah blah objectives here.</P
+></P
+>
+	</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
 ><A
-NAME="AEN4140"
->27.1.2. Steps In Migration Process</A
-></H3
+NAME="AEN4291"
+>27.4.1.2. Installing the required packages for RedHat</A
+></H4
 ><P
->Document steps right here!</P
+>On RedHat this means you should have at least: </P
+><P
+>	<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>krb5-workstation (for kinit)</TD
+></TR
+><TR
+><TD
+>krb5-libs (for linking with)</TD
+></TR
+><TR
+><TD
+>krb5-devel (because you are compiling from source)</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+	</P
+><P
+>in addition to the standard development environment.</P
+><P
+>Note that these are not standard on a RedHat install, and you may need
+	to get them off CD2.</P
+></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -20295,316 +19103,487 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4143"
->27.2. Managing Samba-3 Domain Control</A
+NAME="AEN4301"
+>27.5. Starting the smbd and nmbd</A
 ></H2
 ><P
->Lots of blah blah here.</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="SPEED"
-></A
->Chapter 28. Samba performance issues</H1
+>You must choose to start smbd and nmbd either
+	as daemons or from <SPAN
+CLASS="APPLICATION"
+>inetd</SPAN
+>Don't try
+	to do both!  Either you can put them in <TT
+CLASS="FILENAME"
+>	inetd.conf</TT
+> and have them started on demand
+	by <SPAN
+CLASS="APPLICATION"
+>inetd</SPAN
+>, or you can start them as
+	daemons either from the command line or in <TT
+CLASS="FILENAME"
+>	/etc/rc.local</TT
+>. See the man pages for details
+	on the command line options. Take particular care to read
+	the bit about what user you need to be in order to start
+	Samba.  In many cases you must be root.</P
+><P
+>The main advantage of starting <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+>
+	and <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> using the recommended daemon method
+	is that they will respond slightly more quickly to an initial connection
+	request.</P
 ><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN4163"
->28.1. Comparisons</A
-></H2
+NAME="AEN4311"
+>27.5.1. Starting from inetd.conf</A
+></H3
 ><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
-programs that use the same protocol. The most readily available
-programs for file transfer that use TCP are ftp or another TCP based
-SMB server.</P
+>NOTE; The following will be different if 
+		you use NIS, NIS+ or LDAP to distribute services maps.</P
 ><P
->If you want to test against something like a NT or WfWg server then
-you will have to disable all but TCP on either the client or
-server. Otherwise you may well be using a totally different protocol
-(such as Netbeui) and comparisons may not be valid.</P
+>Look at your <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>. 
+		What is defined at port 139/tcp. If nothing is defined 
+		then add a line like this:</P
 ><P
->Generally you should find that Samba performs similarly to ftp at raw
-transfer speed. It should perform quite a bit faster than NFS,
-although this very much depends on your system.</P
+><KBD
+CLASS="USERINPUT"
+>netbios-ssn     139/tcp</KBD
+></P
 ><P
->Several people have done comparisons between Samba and Novell, NFS or
-WinNT. In some cases Samba performed the best, in others the worst. I
-suspect the biggest factor is not Samba vs some other system but the
-hardware and drivers used on the various systems. Given similar
-hardware Samba should certainly be competitive in speed with other
-systems.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4169"
->28.2. Socket options</A
-></H2
+>similarly for 137/udp you should have an entry like:</P
 ><P
->There are a number of socket options that can greatly affect the
-performance of a TCP based server like Samba.</P
+><KBD
+CLASS="USERINPUT"
+>netbios-ns	137/udp</KBD
+></P
 ><P
->The socket options that Samba uses are settable both on the command
-line with the -O option, or in the smb.conf file.</P
+>Next edit your <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> 
+		and add two lines something like this:</P
 ><P
->The "socket options" section of the smb.conf manual page describes how
-to set these and gives recommendations.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
+		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
+		</PRE
+></P
 ><P
->Getting the socket options right can make a big difference to your
-performance, but getting them wrong can degrade it by just as
-much. The correct settings are very dependent on your local network.</P
+>The exact syntax of <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> 
+		varies between unixes. Look at the other entries in inetd.conf 
+		for a guide.</P
+><DIV
+CLASS="NOTE"
 ><P
->The socket option TCP_NODELAY is the one that seems to make the
-biggest single difference for most networks. Many people report that
-adding "socket options = TCP_NODELAY" doubles the read performance of
-a Samba drive. The best explanation I have seen for this is that the
-Microsoft TCP/IP stack is slow in sending tcp ACKs.</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
+>Some unixes already have entries like netbios_ns 
+		(note the underscore) in <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>. 
+		You must either edit <TT
+CLASS="FILENAME"
+>/etc/services</TT
+> or
+		<TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> to make them consistent.</P
+></TD
+></TR
+></TABLE
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4176"
->28.3. Read size</A
-></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
-several of the SMB commands (currently SMBwrite, SMBwriteX and
-SMBreadbraw) is larger than this value then the server begins writing
-the data before it has received the whole packet from the network, or
-in the case of SMBreadbraw, it begins writing to the network before
-all the data has been read from disk.</P
+CLASS="NOTE"
 ><P
->This overlapping works best when the speeds of disk and network access
-are similar, having very little effect when the speed of one is much
-greater than the other.</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
->The default value is 16384, but very little experimentation has been
-done yet to determine the optimal value, and it is likely that the best
-value will vary greatly between systems anyway. A value over 65536 is
-pointless and will cause you to allocate memory unnecessarily.</P
+>On many systems you may need to use the 
+		<B
+CLASS="COMMAND"
+>interfaces</B
+> option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> to specify the IP address 
+		and netmask of your interfaces. Run <SPAN
+CLASS="APPLICATION"
+>ifconfig</SPAN
+> 
+		as root if you don't know what the broadcast is for your
+		net. <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> tries to determine it at run 
+		time, but fails on some unixes. 
+		</P
+></TD
+></TR
+></TABLE
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4181"
->28.4. Max xmit</A
-></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
-maximum size that Samba will negotiate using the "max xmit = " option
-in smb.conf. Note that this is the maximum size of SMB request that 
-Samba will accept, but not the maximum size that the *client* will accept.
-The client maximum receive size is sent to Samba by the client and Samba
-honours this limit.</P
+CLASS="WARNING"
 ><P
->It defaults to 65536 bytes (the maximum), but it is possible that some
-clients may perform better with a smaller transmit unit. Trying values
-of less than 2048 is likely to cause severe problems.</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
->In most cases the default is the best option.</P
+>Many unixes only accept around 5 
+		parameters on the command line in <TT
+CLASS="FILENAME"
+>inetd.conf</TT
+>. 
+		This means you shouldn't use spaces between the options and 
+		arguments, or you should use a script, and start the script 
+		from <B
+CLASS="COMMAND"
+>inetd</B
+>.</P
+></TD
+></TR
+></TABLE
 ></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4186"
->28.5. Log level</A
-></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
-server flushes the log file after each operation, which can be very
-expensive. </P
+>Restart <B
+CLASS="COMMAND"
+>inetd</B
+>, perhaps just send 
+		it a HUP. If you have installed an earlier version of <SPAN
+CLASS="APPLICATION"
+>		nmbd</SPAN
+> then you may need to kill nmbd as well.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
 ><A
-NAME="AEN4189"
->28.6. Read raw</A
-></H2
+NAME="AEN4345"
+>27.5.2. Alternative: starting it as a daemon</A
+></H3
 ><P
->The "read raw" operation is designed to be an optimised, low-latency
-file read operation. A server may choose to not support it,
-however. and Samba makes support for "read raw" optional, with it
-being enabled by default.</P
+>To start the server as a daemon you should create 
+		a script something like this one, perhaps calling 
+		it <TT
+CLASS="FILENAME"
+>startsmb</TT
+>.</P
 ><P
->In some cases clients don't handle "read raw" very well and actually
-get lower performance using it than they get using the conventional
-read operations. </P
+><PRE
+CLASS="PROGRAMLISTING"
+>		#!/bin/sh
+		/usr/local/samba/bin/smbd -D 
+		/usr/local/samba/bin/nmbd -D 
+		</PRE
+></P
 ><P
->So you might like to try "read raw = no" and see what happens on your
-network. It might lower, raise or not affect your performance. Only
-testing can really tell.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4194"
->28.7. Write raw</A
-></H2
+>then make it executable with <B
+CLASS="COMMAND"
+>chmod 
+		+x startsmb</B
+></P
 ><P
->The "write raw" operation is designed to be an optimised, low-latency
-file write operation. A server may choose to not support it,
-however. and Samba makes support for "write raw" optional, with it
-being enabled by default.</P
+>You can then run <B
+CLASS="COMMAND"
+>startsmb</B
+> by 
+		hand or execute it from <TT
+CLASS="FILENAME"
+>/etc/rc.local</TT
+>
+		</P
 ><P
->Some machines may find "write raw" slower than normal write, in which
-case you may wish to change this option.</P
-></DIV
+>To kill it send a kill signal to the processes 
+		<B
+CLASS="COMMAND"
+>nmbd</B
+> and <B
+CLASS="COMMAND"
+>smbd</B
+>.</P
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4198"
->28.8. Slow Clients</A
-></H2
+CLASS="NOTE"
 ><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
+></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
->I suspect that his PC's (386sx16 based) were asking for more data than
-they could chew. I suspect a similar speed could be had by setting
-"read raw = no" and "max xmit = 2048", instead of changing the
-protocol. Lowering the "read size" might also help.</P
+>If you use the SVR4 style init system then 
+		you may like to look at the <TT
+CLASS="FILENAME"
+>examples/svr4-startup</TT
+>
+		script to make Samba fit into that system.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
 ></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
+CLASS="CHAPTER"
+><HR><H1
 ><A
-NAME="AEN4202"
->28.9. Slow Logins</A
-></H2
+NAME="NT4MIGRATION"
+></A
+>Chapter 28. Migration from NT4 PDC to Samba-3 PDC</H1
 ><P
->Slow logins are almost always due to the password checking time. Using
-the lowest practical "password level" will improve things a lot. You
-could also enable the "UFC crypt" option in the Makefile.</P
-></DIV
+>This is a rough guide to assist those wishing to migrate from NT4 domain control to
+Samba-3 based domain control.</P
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4205"
->28.10. Client tuning</A
+NAME="AEN4375"
+>28.1. Planning and Getting Started</A
 ></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
-performance.</P
-><P
->See your client docs for details. In particular, I have heard rumours
-that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
-large impact on performance.</P
-><P
->Also note that some people have found that setting DefaultRcvWindow in
-the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
-big improvement. I don't know why.</P
-><P
->My own experience wth DefaultRcvWindow is that I get much better
-performance with a large value (16384 or larger). Other people have
-reported that anything over 3072 slows things down enourmously. One
-person even reported a speed drop of a factor of 30 when he went from
-3072 to 8192. I don't know why.</P
-><P
->It probably depends a lot on your hardware, and the type of unix box
-you have at the other end of the link.</P
+>In the IT world there is often a saying that all problems are encountered because of
+poor planning. The corrollary to this saying is that not all problems can be anticpated
+and planned for. Then again, good planning will anticpate most show stopper type situations.</P
 ><P
->Paul Cochrane has done some testing on client side tuning and come 
-to the following conclusions:</P
+>Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
+environment would do well to develop a detailed migration plan. So here are a few pointers to
+help migration get under way.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4379"
+>28.1.1. Objectives</A
+></H3
 ><P
->Install the W2setup.exe file from www.microsoft.com. This is an 
-update for the winsock stack and utilities which improve performance.</P
+>The key objective for most organisations will be to make the migration from MS Windows NT4 
+to Samba-3 domain control as painless as possible. One of the challenges you may experience
+in your migration process may well be one of convincing management that the new environment
+should remain in place. Many who have introduced open source technologies have experienced
+pressure to return to a Microsoft based platform solution at the first sign of trouble. </P
 ><P
->Configure the win95 TCPIP registry settings to give better 
-perfomance. I use a program called MTUSPEED.exe which I got off the 
-net. There are various other utilities of this type freely available. 
-The setting which give the best performance for me are:</P
+>It is strongly advised that before attempting a migration to a Samba-3 controlled network
+that every possible effort be made to gain all-round commitment to the change. Firstly, you
+should know precisely <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>why</I
+></SPAN
+> the change is important for the organisation.
+Possible motivations to make a change include:</P
 ><P
 ></P
-><OL
-TYPE="1"
-><LI
-><P
->MaxMTU                  Remove</P
-></LI
+><UL
 ><LI
 ><P
->RWIN                    Remove</P
+>Improve network manageability</P
 ></LI
 ><LI
 ><P
->MTUAutoDiscover         Disable</P
+>Obtain better user level functionality</P
 ></LI
 ><LI
 ><P
->MTUBlackHoleDetect      Disable</P
+>Reduce network operating costs</P
 ></LI
 ><LI
 ><P
->Time To Live            Enabled</P
+>Reduce exposure caused by Microsoft withdrawal of NT4 support</P
 ></LI
 ><LI
 ><P
->Time To Live - HOPS     32</P
+>Avoid MS License 6 implications</P
 ></LI
 ><LI
 ><P
->NDI Cache Size          0</P
+>Reduce organisation's dependency on Microsoft</P
 ></LI
-></OL
+></UL
 ><P
->I tried virtually all of the items mentioned in the document and 
-the only one which made a difference to me was the socket options. It 
-turned out I was better off without any!!!!!</P
+>It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
+an alternative solution that is both different from MS Windows NT4 and that offers some
+advantages compared with it. It should also be recognised that Samba-3 lacks many of the
+features that Microsoft has promoted as core values in migration from MS Windows NT4 to 
+MS Windows 2000 and beyond (with or without Active Directory services).</P
 ><P
->In terms of overall speed of transfer, between various win95 clients 
-and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE 
-drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.</P
+>What are the features the Samba-3 can NOT provide?</P
 ><P
-><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</PRE
 ></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Active Directory Server</TD
+></TR
+><TR
+><TD
+>Group Policy Objects (in Active Direcrtory)</TD
+></TR
+><TR
+><TD
+>Machine Policy objects</TD
+></TR
+><TR
+><TD
+>Logon Scripts in Active Directorty</TD
+></TR
+><TR
+><TD
+>Software Application and Access Controls in Active Directory</TD
+></TR
+></TBODY
+></TABLE
 ><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 
-running on. It's a crap machine!!!!</P
-><P
->The updates mentioned in 1 and 2 brought up the transfer rates from 
-just over 100kB/s in some clients.</P
-><P
->A new client is a P333 connected via a 100MB/s card and hub. The 
-transfer rates from this were good: 450-500kB/s on put and 600+kB/s 
-on get.</P
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4405"
+>28.1.2. Steps In Migration Process</A
+></H3
 ><P
->Looking at standard FTP throughput, Samba is a bit slower (100kB/s 
-upwards). I suppose there is more going on in the samba protocol, but 
-if it could get up to the rate of FTP the perfomance would be quite 
-staggering.</P
+>This is not a definitive ste-by-step process yet - just a place holder so the info 
+is not lost.
+
+1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
+
+2. Samba-3 set up as a DC with netlogon share, profile share, etc.
+
+3. Process:
+	a. Create a BDC account for the samba server using NT Server Manager
+		- Samba must NOT be running
+
+	b. rpcclient NT4PDC -U Administrator%passwd
+		lsaquery
+
+		Note the SID returned by step b.
+
+	c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
+
+		Note the SID in step c.
+
+	d. net getlocalsid
+
+		Note the SID, now check that all three SIDS reported are the same!
+
+	e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
+
+	f. net rpc vampire -S NT4PDC -U administrator%passwd
+
+	g. pdbedit -l
+
+		Note - did the users migrate?
+
+	h. initGrps.sh DOMNAME
+
+	i. smbgroupedit -v
+
+		Now check that all groups are recognised
+
+	j. net rpc campire -S NT4PDC -U administrator%passwd
+
+	k. pdbedit -lv
+
+		Note - check that all group membership has been migrated.
+
+
+Now it is time to migrate all the profiles, then migrate all policy files.
+
+Moe later.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4408"
+>28.2. Managing Samba-3 Domain Control</A
+></H2
+><P
+>Lots of blah blah here.</P
 ></DIV
 ></DIV
 ><DIV
@@ -20623,7 +19602,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4249"
+NAME="AEN4423"
 >29.1. HPUX</A
 ></H2
 ><P
@@ -20653,7 +19632,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4255"
+NAME="AEN4429"
 >29.2. SCO Unix</A
 ></H2
 ><P
@@ -20670,7 +19649,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4259"
+NAME="AEN4433"
 >29.3. DNIX</A
 ></H2
 ><P
@@ -20777,7 +19756,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4288"
+NAME="AEN4462"
 >29.4. RedHat Linux Rembrandt-II</A
 ></H2
 ><P
@@ -20801,7 +19780,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4294"
+NAME="AEN4468"
 >29.5. AIX</A
 ></H2
 ><DIV
@@ -20809,7 +19788,7 @@ CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4296"
+NAME="AEN4470"
 >29.5.1. Sequential Read Ahead</A
 ></H3
 ><P
@@ -20820,6 +19799,36 @@ CLASS="USERINPUT"
 samba performance significally.</P
 ></DIV
 ></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4474"
+>29.6. Solaris</A
+></H2
+><P
+>Some people have been experiencing problems with F_SETLKW64/fcntl 
+when running samba on solaris. The built in file locking mechanism was
+not scalable. Performance would degrade to the point where processes would
+get into loops of trying to lock a file. It woul try a lock, then fail,
+then try again. The lock attempt was failing before the grant was
+occurring. So the visible manifestation of this would be a handful of
+processes stealing all of the CPU, and when they were trussed they would
+be stuck if F_SETLKW64 loops.</P
+><P
+>Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
+has not been released yet.</P
+><P
+>The patch revision for 2.6 is 105181-34
+for 8 is 108528-19
+and for 9 is 112233-04</P
+><P
+>After the install of these patches it is recommended to reconfigure
+and rebuild samba.</P
+><P
+>Thanks to Joe Meslovich for reporting</P
+></DIV
 ></DIV
 ><DIV
 CLASS="CHAPTER"
@@ -20835,7 +19844,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4319"
+NAME="AEN4501"
 >30.1. Macintosh clients?</A
 ></H2
 ><P
@@ -20881,7 +19890,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4328"
+NAME="AEN4510"
 >30.2. OS2 Client</A
 ></H2
 ><DIV
@@ -20889,7 +19898,7 @@ CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4330"
+NAME="AEN4512"
 >30.2.1. How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?</A
 ></H3
@@ -20948,7 +19957,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4345"
+NAME="AEN4527"
 >30.2.2. How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?</A
 ></H3
@@ -20992,7 +20001,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4354"
+NAME="AEN4536"
 >30.2.3. Are there any other issues when OS/2 (any version) 
 		is used as a client?</A
 ></H3
@@ -21014,7 +20023,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4358"
+NAME="AEN4540"
 >30.2.4. How do I get printer driver download working 
 		for OS/2 clients?</A
 ></H3
@@ -21061,7 +20070,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4368"
+NAME="AEN4550"
 >30.3. Windows for Workgroups</A
 ></H2
 ><DIV
@@ -21069,7 +20078,7 @@ CLASS="SECT2"
 ><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4370"
+NAME="AEN4552"
 >30.3.1. Use latest TCP/IP stack from Microsoft</A
 ></H3
 ><P
@@ -21091,7 +20100,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4375"
+NAME="AEN4557"
 >30.3.2. Delete .pwl files after password change</A
 ></H3
 ><P
@@ -21111,7 +20120,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4380"
+NAME="AEN4562"
 >30.3.3. Configure WfW password handling</A
 ></H3
 ><P
@@ -21130,7 +20139,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4384"
+NAME="AEN4566"
 >30.3.4. Case handling of passwords</A
 ></H3
 ><P
@@ -21148,7 +20157,7 @@ CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4389"
+NAME="AEN4571"
 >30.3.5. Use TCP/IP as default protocol</A
 ></H3
 ><P
@@ -21164,7 +20173,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4392"
+NAME="AEN4574"
 >30.4. Windows '95/'98</A
 ></H2
 ><P
@@ -21212,7 +20221,7 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4408"
+NAME="AEN4590"
 >30.5. Windows 2000 Service Pack 2</A
 ></H2
 ><P
@@ -21270,241 +20279,41 @@ for the "access denied" message.</P
 >By disabling the <B
 CLASS="COMMAND"
 >nt acl support</B
-> parameter, Samba will send
-the Win2k client a response to the QuerySecurityDescriptor
-trans2 call which causes the client to set a default ACL
-for the profile. This default ACL includes </P
-><P
-><B
-CLASS="COMMAND"
->DOMAIN\user 	"Full Control"</B
-></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
->This bug does not occur when using winbind to
-create accounts on the Samba host for Domain users.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4425"
->30.6. Windows NT 3.1</A
-></H2
-><P
->If you have problems communicating across routers with Windows 
-NT 3.1 workstations, read <A
-HREF="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765"
-TARGET="_top"
->this Microsoft Knowledge Base article</A
->.&#13;</P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="COMPILING"
-></A
->Chapter 31. How to compile SAMBA</H1
-><P
->You can obtain the samba source from the <A
-HREF="http://samba.org/"
-TARGET="_top"
->samba website</A
->. To obtain a development version, 
-you can download samba from CVS or using rsync. </P
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4446"
->31.1. Access Samba source code via CVS</A
-></H2
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
-NAME="AEN4448"
->31.1.1. Introduction</A
-></H3
-><P
->Samba is developed in an open environment.  Developers use CVS
-(Concurrent Versioning System) to "checkin" (also known as 
-"commit") new source code.  Samba's various CVS branches can
-be accessed via anonymous CVS using the instructions
-detailed in this chapter.</P
-><P
->This chapter is a modified version of the instructions found at
-<A
-HREF="http://samba.org/samba/cvs.html"
-TARGET="_top"
->http://samba.org/samba/cvs.html</A
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
-><A
-NAME="AEN4453"
->31.1.2. CVS Access to samba.org</A
-></H3
-><P
->The machine samba.org runs a publicly accessible CVS 
-repository for access to the source code of several packages, 
-including samba, rsync and jitterbug. There are two main ways of 
-accessing the CVS server on this host.</P
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN4456"
->31.1.2.1. Access via CVSweb</A
-></H4
-><P
->You can access the source code via your 
-favourite WWW browser. This allows you to access the contents of 
-individual files in the repository and also to look at the revision 
-history and commit logs of individual files. You can also ask for a diff 
-listing between any two versions on the repository.</P
-><P
->Use the URL : <A
-HREF="http://samba.org/cgi-bin/cvsweb"
-TARGET="_top"
->http://samba.org/cgi-bin/cvsweb</A
-></P
-></DIV
-><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
-><A
-NAME="AEN4461"
->31.1.2.2. Access via cvs</A
-></H4
-><P
->You can also access the source code via a 
-normal cvs client.  This gives you much more control over you can 
-do with the repository and allows you to checkout whole source trees 
-and keep them up to date via normal cvs commands. This is the 
-preferred method of access if you are a developer and not
-just a casual browser.</P
-><P
->To download the latest cvs source code, point your
-browser at the URL : <A
-HREF="http://www.cyclic.com/"
-TARGET="_top"
->http://www.cyclic.com/</A
->.
-and click on the 'How to get cvs' link. CVS is free software under 
-the GNU GPL (as is Samba).  Note that there are several graphical CVS clients
-which provide a graphical interface to the sometimes mundane CVS commands.
-Links to theses clients are also available from http://www.cyclic.com.</P
-><P
->To gain access via anonymous cvs use the following steps. 
-For this example it is assumed that you want a copy of the 
-samba source code. For the other source code repositories 
-on this system just substitute the correct package name</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
->	Install a recent copy of cvs. All you really need is a 
-	copy of the cvs client binary. 
-	</P
-></LI
-><LI
-><P
->	Run the command 
-	</P
-><P
->	<KBD
-CLASS="USERINPUT"
->cvs -d :pserver:cvs@samba.org:/cvsroot login</KBD
->
-	</P
-><P
->	When it asks you for a password type <KBD
-CLASS="USERINPUT"
->cvs</KBD
->.
-	</P
-></LI
-><LI
-><P
->	Run the command 
-	</P
-><P
->	<KBD
-CLASS="USERINPUT"
->cvs -d :pserver:cvs@samba.org:/cvsroot co samba</KBD
->
-	</P
-><P
->	This will create a directory called samba containing the 
-	latest samba source code (i.e. the HEAD tagged cvs branch). This 
-	currently corresponds to the 3.0 development tree. 
-	</P
-><P
->	CVS branches other HEAD can be obtained by using the <VAR
-CLASS="PARAMETER"
->-r</VAR
->
-	and defining a tag name.  A list of branch tag names can be found on the
-	"Development" page of the samba web site.  A common request is to obtain the
-	latest 2.2 release code.  This could be done by using the following userinput.
-	</P
+> parameter, Samba will send
+the Win2k client a response to the QuerySecurityDescriptor
+trans2 call which causes the client to set a default ACL
+for the profile. This default ACL includes </P
 ><P
->	<KBD
-CLASS="USERINPUT"
->cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</KBD
->
-	</P
-></LI
-><LI
+><B
+CLASS="COMMAND"
+>DOMAIN\user 	"Full Control"</B
+></P
+><DIV
+CLASS="NOTE"
 ><P
->	Whenever you want to merge in the latest code changes use 
-	the following command from within the samba directory: 
-	</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
->	<KBD
-CLASS="USERINPUT"
->cvs update -d -P</KBD
->
-	</P
-></LI
-></OL
-></DIV
+>This bug does not occur when using winbind to
+create accounts on the Samba host for Domain users.</P
+></TD
+></TR
+></TABLE
 ></DIV
 ></DIV
 ><DIV
@@ -21512,504 +20321,488 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4489"
->31.2. Accessing the samba sources via rsync and ftp</A
+NAME="AEN4607"
+>30.6. Windows NT 3.1</A
 ></H2
 ><P
->	pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A
-HREF="ftp://pserver.samba.org/pub/unpacked"
-TARGET="_top"
->ftp://pserver.samba.org/pub/unpacked</A
-> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp.
-	See <A
-HREF="http://rsync.samba.org/"
+>If you have problems communicating across routers with Windows 
+NT 3.1 workstations, read <A
+HREF="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765"
 TARGET="_top"
->the rsync homepage</A
-> for more info on rsync.                       
-	</P
-><P
->	The disadvantage of the unpacked trees
-	is that they do not support automatic
-	merging of local changes like CVS does.
-	rsync access is most convenient for an 
-	initial install.                       
-	</P
+>this Microsoft Knowledge Base article</A
+>.&#13;</P
+></DIV
 ></DIV
 ><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="SWAT"
+></A
+>Chapter 31. SWAT - The Samba Web Admininistration Tool</H1
+><P
+>This is a rough guide to SWAT.</P
+><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4495"
->31.3. Building the Binaries</A
+NAME="AEN4624"
+>31.1. SWAT Features and Benefits</A
 ></H2
 ><P
->To do this, first run the program <KBD
-CLASS="USERINPUT"
->./configure
-	</KBD
-> in the source directory. This should automatically 
-	configure Samba for your operating system. If you have unusual 
-	needs then you may wish to run</P
-><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->./configure --help
-	</KBD
-></P
-><P
->first to see what special options you can enable.
-	Then executing</P
-><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->make</KBD
-></P
-><P
->will create the binaries. Once it's successfully 
-	compiled you can use </P
-><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->make install</KBD
-></P
-><P
->to install the binaries and manual pages. You can 
-	separately install the binaries and/or man pages using</P
+>You must use at least the following ...</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4627"
+>31.1.1. The SWAT Home Page</A
+></H3
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->make installbin
-	</KBD
-></P
+>Blah blah here.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4630"
+>31.1.2. Global Settings</A
+></H3
 ><P
->and</P
+>Document steps right here!</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4633"
+>31.1.3. The SWAT Wizard</A
+></H3
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->make installman
-	</KBD
-></P
+>Lots of blah blah here.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4636"
+>31.1.4. Share Settings</A
+></H3
 ><P
->Note that if you are upgrading for a previous version 
-	of Samba you might like to know that the old versions of 
-	the binaries will be renamed with a ".old" extension. You 
-	can go back to the previous version with</P
+>Document steps right here!</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4639"
+>31.1.5. Printing Settings</A
+></H3
 ><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->make revert
-	</KBD
-></P
+>Document steps right here!</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN4642"
+>31.1.6. The Status Page</A
+></H3
 ><P
->if you find this version a disaster!</P
+>Document steps right here!</P
+></DIV
 ><DIV
 CLASS="SECT2"
 ><HR><H3
 CLASS="SECT2"
 ><A
-NAME="AEN4523"
->31.3.1. Compiling samba with Active Directory support</A
+NAME="AEN4645"
+>31.1.7. The Password Change Page</A
 ></H3
 ><P
->In order to compile samba with ADS support, you need to have installed
-	on your system: 
-	<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.</TD
-></TR
-><TR
-><TD
->the OpenLDAP development libraries.</TD
-></TR
-></TBODY
-></TABLE
+>Document steps right here!</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="SPEED"
+></A
+>Chapter 32. Samba performance issues</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN4666"
+>32.1. Comparisons</A
+></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
+programs that use the same protocol. The most readily available
+programs for file transfer that use TCP are ftp or another TCP based
+SMB server.</P
+><P
+>If you want to test against something like a NT or WfWg server then
+you will have to disable all but TCP on either the client or
+server. Otherwise you may well be using a totally different protocol
+(such as Netbeui) and comparisons may not be valid.</P
+><P
+>Generally you should find that Samba performs similarly to ftp at raw
+transfer speed. It should perform quite a bit faster than NFS,
+although this very much depends on your system.</P
+><P
+>Several people have done comparisons between Samba and Novell, NFS or
+WinNT. In some cases Samba performed the best, in others the worst. I
+suspect the biggest factor is not Samba vs some other system but the
+hardware and drivers used on the various systems. Given similar
+hardware Samba should certainly be competitive in speed with other
+systems.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4672"
+>32.2. Socket options</A
+></H2
 ><P
-></P
->
-
-	</P
+>There are a number of socket options that can greatly affect the
+performance of a TCP based server like Samba.</P
 ><P
->If your kerberos libraries are in a non-standard location then
-	  remember to add the configure option --with-krb5=DIR.</P
+>The socket options that Samba uses are settable both on the command
+line with the -O option, or in the smb.conf file.</P
 ><P
->After you run configure make sure that <TT
-CLASS="FILENAME"
->include/config.h</TT
-> it generates contains lines like this:</P
+>The "socket options" section of the smb.conf manual page describes how
+to set these and gives recommendations.</P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->#define HAVE_KRB5 1
-#define HAVE_LDAP 1
-		  </PRE
-></P
+>Getting the socket options right can make a big difference to your
+performance, but getting them wrong can degrade it by just as
+much. The correct settings are very dependent on your local network.</P
 ><P
->If it doesn't then configure did not find your krb5 libraries or
-	    your ldap libraries. Look in config.log to figure out why and fix
-		  it.</P
+>The socket option TCP_NODELAY is the one that seems to make the
+biggest single difference for most networks. Many people report that
+adding "socket options = TCP_NODELAY" doubles the read performance of
+a Samba drive. The best explanation I have seen for this is that the
+Microsoft TCP/IP stack is slow in sending tcp ACKs.</P
+></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN4535"
->31.3.1.1. Installing the required packages for Debian</A
-></H4
+NAME="AEN4679"
+>32.3. Read size</A
+></H2
 ><P
->On Debian you need to install the following packages:</P
+>The option "read size" affects the overlap of disk reads/writes with
+network reads/writes. If the amount of data being transferred in
+several of the SMB commands (currently SMBwrite, SMBwriteX and
+SMBreadbraw) is larger than this value then the server begins writing
+the data before it has received the whole packet from the network, or
+in the case of SMBreadbraw, it begins writing to the network before
+all the data has been read from disk.</P
 ><P
->	<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->libkrb5-dev</TD
-></TR
-><TR
-><TD
->krb5-user</TD
-></TR
-></TBODY
-></TABLE
+>This overlapping works best when the speeds of disk and network access
+are similar, having very little effect when the speed of one is much
+greater than the other.</P
 ><P
-></P
->
-	</P
+>The default value is 16384, but very little experimentation has been
+done yet to determine the optimal value, and it is likely that the best
+value will vary greatly between systems anyway. A value over 65536 is
+pointless and will cause you to allocate memory unnecessarily.</P
 ></DIV
 ><DIV
-CLASS="SECT3"
-><HR><H4
-CLASS="SECT3"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN4542"
->31.3.1.2. Installing the required packages for RedHat</A
-></H4
-><P
->On RedHat this means you should have at least: </P
+NAME="AEN4684"
+>32.4. Max xmit</A
+></H2
 ><P
->	<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->krb5-workstation (for kinit)</TD
-></TR
-><TR
-><TD
->krb5-libs (for linking with)</TD
-></TR
-><TR
-><TD
->krb5-devel (because you are compiling from source)</TD
-></TR
-></TBODY
-></TABLE
+>At startup the client and server negotiate a "maximum transmit" size,
+which limits the size of nearly all SMB commands. You can set the
+maximum size that Samba will negotiate using the "max xmit = " option
+in smb.conf. Note that this is the maximum size of SMB request that 
+Samba will accept, but not the maximum size that the *client* will accept.
+The client maximum receive size is sent to Samba by the client and Samba
+honours this limit.</P
 ><P
-></P
->
-	</P
+>It defaults to 65536 bytes (the maximum), but it is possible that some
+clients may perform better with a smaller transmit unit. Trying values
+of less than 2048 is likely to cause severe problems.</P
 ><P
->in addition to the standard development environment.</P
+>In most cases the default is the best option.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4689"
+>32.5. Log level</A
+></H2
 ><P
->Note that these are not standard on a RedHat install, and you may need
-	to get them off CD2.</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
+server flushes the log file after each operation, which can be very
+expensive. </P
 ></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4692"
+>32.6. Read raw</A
+></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,
+however. and Samba makes support for "read raw" optional, with it
+being enabled by default.</P
+><P
+>In some cases clients don't handle "read raw" very well and actually
+get lower performance using it than they get using the conventional
+read operations. </P
+><P
+>So you might like to try "read raw = no" and see what happens on your
+network. It might lower, raise or not affect your performance. Only
+testing can really tell.</P
 ></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4697"
+>32.7. Write raw</A
+></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,
+however. and Samba makes support for "write raw" optional, with it
+being enabled by default.</P
+><P
+>Some machines may find "write raw" slower than normal write, in which
+case you may wish to change this option.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4552"
->31.4. Starting the smbd and nmbd</A
+NAME="AEN4701"
+>32.8. Slow Clients</A
 ></H2
 ><P
->You must choose to start smbd and nmbd either
-	as daemons or from <SPAN
-CLASS="APPLICATION"
->inetd</SPAN
->Don't try
-	to do both!  Either you can put them in <TT
-CLASS="FILENAME"
->	inetd.conf</TT
-> and have them started on demand
-	by <SPAN
-CLASS="APPLICATION"
->inetd</SPAN
->, or you can start them as
-	daemons either from the command line or in <TT
-CLASS="FILENAME"
->	/etc/rc.local</TT
->. See the man pages for details
-	on the command line options. Take particular care to read
-	the bit about what user you need to be in order to start
-	Samba.  In many cases you must be root.</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
 ><P
->The main advantage of starting <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
->
-	and <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> using the recommended daemon method
-	is that they will respond slightly more quickly to an initial connection
-	request.</P
+>I suspect that his PC's (386sx16 based) were asking for more data than
+they could chew. I suspect a similar speed could be had by setting
+"read raw = no" and "max xmit = 2048", instead of changing the
+protocol. Lowering the "read size" might also help.</P
+></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN4562"
->31.4.1. Starting from inetd.conf</A
-></H3
+NAME="AEN4705"
+>32.9. Slow Logins</A
+></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
+could also enable the "UFC crypt" option in the Makefile.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4708"
+>32.10. Client tuning</A
+></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
+performance.</P
+><P
+>See your client docs for details. In particular, I have heard rumours
+that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
+large impact on performance.</P
+><P
+>Also note that some people have found that setting DefaultRcvWindow in
+the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
+big improvement. I don't know why.</P
+><P
+>My own experience wth DefaultRcvWindow is that I get much better
+performance with a large value (16384 or larger). Other people have
+reported that anything over 3072 slows things down enourmously. One
+person even reported a speed drop of a factor of 30 when he went from
+3072 to 8192. I don't know why.</P
+><P
+>It probably depends a lot on your hardware, and the type of unix box
+you have at the other end of the link.</P
+><P
+>Paul Cochrane has done some testing on client side tuning and come 
+to the following conclusions:</P
 ><P
->NOTE; The following will be different if 
-		you use NIS, NIS+ or LDAP to distribute services maps.</P
+>Install the W2setup.exe file from www.microsoft.com. This is an 
+update for the winsock stack and utilities which improve performance.</P
 ><P
->Look at your <TT
-CLASS="FILENAME"
->/etc/services</TT
->. 
-		What is defined at port 139/tcp. If nothing is defined 
-		then add a line like this:</P
+>Configure the win95 TCPIP registry settings to give better 
+perfomance. I use a program called MTUSPEED.exe which I got off the 
+net. There are various other utilities of this type freely available. 
+The setting which give the best performance for me are:</P
 ><P
-><KBD
-CLASS="USERINPUT"
->netbios-ssn     139/tcp</KBD
 ></P
+><OL
+TYPE="1"
+><LI
 ><P
->similarly for 137/udp you should have an entry like:</P
+>MaxMTU                  Remove</P
+></LI
+><LI
 ><P
-><KBD
-CLASS="USERINPUT"
->netbios-ns	137/udp</KBD
-></P
+>RWIN                    Remove</P
+></LI
+><LI
 ><P
->Next edit your <TT
-CLASS="FILENAME"
->/etc/inetd.conf</TT
-> 
-		and add two lines something like this:</P
+>MTUAutoDiscover         Disable</P
+></LI
+><LI
+><P
+>MTUBlackHoleDetect      Disable</P
+></LI
+><LI
+><P
+>Time To Live            Enabled</P
+></LI
+><LI
+><P
+>Time To Live - HOPS     32</P
+></LI
+><LI
+><P
+>NDI Cache Size          0</P
+></LI
+></OL
+><P
+>I tried virtually all of the items mentioned in the document and 
+the only one which made a difference to me was the socket options. It 
+turned out I was better off without any!!!!!</P
+><P
+>In terms of overall speed of transfer, between various win95 clients 
+and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE 
+drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
-		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
-		</PRE
+>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</PRE
 ></P
 ><P
->The exact syntax of <TT
-CLASS="FILENAME"
->/etc/inetd.conf</TT
-> 
-		varies between unixes. Look at the other entries in inetd.conf 
-		for a guide.</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"
+>I based these test on transfer two files a 4.5MB text file and a 15MB 
+textfile. The results arn't bad considering the hardware Samba is 
+running on. It's a crap machine!!!!</P
 ><P
->Some unixes already have entries like netbios_ns 
-		(note the underscore) in <TT
-CLASS="FILENAME"
->/etc/services</TT
->. 
-		You must either edit <TT
-CLASS="FILENAME"
->/etc/services</TT
-> or
-		<TT
-CLASS="FILENAME"
->/etc/inetd.conf</TT
-> to make them consistent.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
+>The updates mentioned in 1 and 2 brought up the transfer rates from 
+just over 100kB/s in some clients.</P
 ><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"
+>A new client is a P333 connected via a 100MB/s card and hub. The 
+transfer rates from this were good: 450-500kB/s on put and 600+kB/s 
+on get.</P
 ><P
->On many systems you may need to use the 
-		<B
-CLASS="COMMAND"
->interfaces</B
-> option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to specify the IP address 
-		and netmask of your interfaces. Run <SPAN
-CLASS="APPLICATION"
->ifconfig</SPAN
-> 
-		as root if you don't know what the broadcast is for your
-		net. <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> tries to determine it at run 
-		time, but fails on some unixes. 
-		</P
-></TD
-></TR
-></TABLE
+>Looking at standard FTP throughput, Samba is a bit slower (100kB/s 
+upwards). I suppose there is more going on in the samba protocol, but 
+if it could get up to the rate of FTP the perfomance would be quite 
+staggering.</P
+></DIV
 ></DIV
 ><DIV
-CLASS="WARNING"
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="DIAGNOSIS"
+></A
+>Chapter 33. The samba checklist</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN4760"
+>33.1. Introduction</A
+></H2
 ><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"
+>This file contains a list of tests you can perform to validate your
+Samba server. It also tells you what the likely cause of the problem
+is if it fails any one of these steps. If it passes all these tests
+then it is probably working fine.</P
 ><P
->Many unixes only accept around 5 
-		parameters on the command line in <TT
-CLASS="FILENAME"
->inetd.conf</TT
->. 
-		This means you shouldn't use spaces between the options and 
-		arguments, or you should use a script, and start the script 
-		from <B
-CLASS="COMMAND"
->inetd</B
->.</P
-></TD
-></TR
-></TABLE
-></DIV
+>You should do ALL the tests, in the order shown. We have tried to
+carefully choose them so later tests only use capabilities verified in
+the earlier tests.</P
 ><P
->Restart <B
-CLASS="COMMAND"
->inetd</B
->, perhaps just send 
-		it a HUP. If you have installed an earlier version of <SPAN
-CLASS="APPLICATION"
->		nmbd</SPAN
-> then you may need to kill nmbd as well.</P
+>If you send one of the samba mailing lists  an email saying "it doesn't work"
+and you have not followed this test procedure then you should not be surprised
+your email is ignored.</P
 ></DIV
 ><DIV
-CLASS="SECT2"
-><HR><H3
-CLASS="SECT2"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
 ><A
-NAME="AEN4596"
->31.4.2. Alternative: starting it as a daemon</A
-></H3
+NAME="AEN4765"
+>33.2. Assumptions</A
+></H2
 ><P
->To start the server as a daemon you should create 
-		a script something like this one, perhaps calling 
-		it <TT
+>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
+><P
+>The procedure is similar for other types of clients.</P
+><P
+>It is also assumed you know the name of an available share in your
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. I will assume this share is called <VAR
+CLASS="REPLACEABLE"
+>tmp</VAR
+>.
+You can add a <VAR
+CLASS="REPLACEABLE"
+>tmp</VAR
+> share like by adding the
+following to <TT
 CLASS="FILENAME"
->startsmb</TT
->.</P
+>smb.conf</TT
+>:</P
 ><P
 ><PRE
 CLASS="PROGRAMLISTING"
->		#!/bin/sh
-		/usr/local/samba/bin/smbd -D 
-		/usr/local/samba/bin/nmbd -D 
-		</PRE
-></P
-><P
->then make it executable with <B
-CLASS="COMMAND"
->chmod 
-		+x startsmb</B
+>&#13;[tmp]
+ comment = temporary files 
+ path = /tmp
+ read only = yes&#13;</PRE
 ></P
-><P
->You can then run <B
-CLASS="COMMAND"
->startsmb</B
-> by 
-		hand or execute it from <TT
-CLASS="FILENAME"
->/etc/rc.local</TT
->
-		</P
-><P
->To kill it send a kill signal to the processes 
-		<B
-CLASS="COMMAND"
->nmbd</B
-> and <B
-CLASS="COMMAND"
->smbd</B
->.</P
 ><DIV
 CLASS="NOTE"
 ><P
@@ -22031,69 +20824,31 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->If you use the SVR4 style init system then 
-		you may like to look at the <TT
-CLASS="FILENAME"
->examples/svr4-startup</TT
->
-		script to make Samba fit into that system.</P
+>These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. </P
 ></TD
 ></TR
 ></TABLE
 ></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="BUGREPORT"
-></A
->Chapter 32. Reporting Bugs</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN4627"
->32.1. Introduction</A
-></H2
-><P
->The email address for bug reports for stable releases is <A
-HREF="mailto:samba@samba.org"
-TARGET="_top"
->samba@samba.org</A
->. 
-Bug reports for alpha releases should go to <A
-HREF="mailto:samba-technical@samba.org"
-TARGET="_top"
->samba-technical@samba.org</A
->.</P
-><P
->Please take the time to read this file before you submit a bug
-report. Also, please see if it has changed between releases, as we
-may be changing the bug reporting mechanism at some time.</P
 ><P
->Please also do as much as you can yourself to help track down the
-bug. Samba is maintained by a dedicated group of people who volunteer
-their time, skills and efforts. We receive far more mail about it than
-we can possibly answer, so you have a much higher chance of an answer
-and a fix if you send us a "developer friendly" bug report that lets
-us fix it fast. </P
-><P
->Do not assume that if you post the bug to the comp.protocols.smb
-newsgroup or the mailing list that we will read it. If you suspect that your 
-problem is not a bug but a configuration problem then it is better to send 
-it to the Samba mailing list, as there are (at last count) 5000 other users on
-that list that may be able to help you.</P
+>Please pay attention to the error messages you receive. If any error message
+reports that your server is being unfriendly you should first check that you
+IP name resolution is correctly set up. eg: Make sure your <TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+>
+file points to name servers that really do exist.</P
 ><P
->You may also like to look though the recent mailing list archives,
-which are conveniently accessible on the Samba web pages
-at <A
-HREF="http://samba.org/samba/"
-TARGET="_top"
->http://samba.org/samba/</A
+>Also, if you do not have DNS server access for name resolution please check
+that the settings for your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file results in <B
+CLASS="COMMAND"
+>dns proxy = no</B
+>. The
+best way to check this is with <KBD
+CLASS="USERINPUT"
+>testparm smb.conf</KBD
 >.</P
 ></DIV
 ><DIV
@@ -22101,283 +20856,324 @@ CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4637"
->32.2. General info</A
+NAME="AEN4784"
+>33.3. The tests</A
 ></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
-you've misconfigured something and run testparm to test your config
-file for correct syntax.</P
-><P
->Have you run through the <A
-HREF="#DIAGNOSIS"
->diagnosis</A
->? 
-This is very important.</P
-><P
->If you include part of a log file with your bug report then be sure to
-annotate it with exactly what you were doing on the client at the
-time, and exactly what the results were.</P
-></DIV
 ><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4643"
->32.3. Debug levels</A
-></H2
+CLASS="PROCEDURE"
 ><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
-be very useful. Depending on the problem a log level of between 3 and
-10 showing the problem may be appropriate. A higher level givesmore
-detail, but may use too much disk space.</P
+><B
+>Diagnosing your samba server</B
+></P
+><OL
+TYPE="1"
+><LI
 ><P
->To set the debug level use <B
-CLASS="COMMAND"
->log level =</B
-> in your 
-<TT
+>In the directory in which you store your <TT
 CLASS="FILENAME"
 >smb.conf</TT
->. You may also find it useful to set the log 
-level higher for just one machine and keep separate logs for each machine. 
-To do this use:</P
+> file, run the command
+<KBD
+CLASS="USERINPUT"
+>testparm smb.conf</KBD
+>. If it reports any errors then your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+configuration file is faulty.</P
+><DIV
+CLASS="NOTE"
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m</PRE
 ></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
->then create a file 
-<TT
-CLASS="FILENAME"
->/usr/local/samba/lib/smb.conf.<VAR
-CLASS="REPLACEABLE"
->machine</VAR
-></TT
-> where
-<VAR
-CLASS="REPLACEABLE"
->machine</VAR
-> is the name of the client you wish to debug. In that file
-put any <TT
+>Your <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> commands you want, for example 
+> file may be located in: <TT
+CLASS="FILENAME"
+>/etc/samba</TT
+>
+Or in:   <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib</TT
+></P
+></TD
+></TR
+></TABLE
+></DIV
+></LI
+><LI
+><P
+>Run the command <KBD
+CLASS="USERINPUT"
+>ping BIGSERVER</KBD
+> from the PC and 
+<KBD
+CLASS="USERINPUT"
+>ping ACLIENT</KBD
+> from
+the unix box. If you don't get a valid response then your TCP/IP
+software is not correctly installed. </P
+><P
+>Note that you will need to start a "dos prompt" window on the PC to
+run ping.</P
+><P
+>If you get a message saying "host not found" or similar then your DNS
+software or <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file is not correctly setup.
+It is possible to
+run samba without DNS entries for the server and client, but I assume
+you do have correct entries for the remainder of these tests. </P
+><P
+>Another reason why ping might fail is if your host is running firewall 
+software. You will need to relax the rules to let in the workstation
+in question, perhaps by allowing access from another subnet (on Linux
+this is done via the <SPAN
+CLASS="APPLICATION"
+>ipfwadm</SPAN
+> program.)</P
+></LI
+><LI
+><P
+>Run the command <KBD
+CLASS="USERINPUT"
+>smbclient -L BIGSERVER</KBD
+> on the unix box. You
+should get a list of available shares back. </P
+><P
+>If you get a error message containing the string "Bad password" then
+you probably have either an incorrect <B
+CLASS="COMMAND"
+>hosts allow</B
+>, 
 <B
 CLASS="COMMAND"
->log level=</B
-> may be useful. This also allows you to 
-experiment with different security systems, protocol levels etc on just 
-one machine.</P
-><P
->The <TT
+>hosts deny</B
+> or <B
+CLASS="COMMAND"
+>valid users</B
+> line in your 
+<TT
 CLASS="FILENAME"
 >smb.conf</TT
-> entry <B
+>, or your guest account is not
+valid. Check what your guest account is using <SPAN
+CLASS="APPLICATION"
+>testparm</SPAN
+> and
+temporarily remove any <B
 CLASS="COMMAND"
->log level =</B
-> 
-is synonymous with the entry <B
+>hosts allow</B
+>, <B
 CLASS="COMMAND"
->debuglevel =</B
-> that has been 
-used in older versions of Samba and is being retained for backwards 
-compatibility of <TT
-CLASS="FILENAME"
->smb.conf</TT
-> files.</P
-><P
->As the <B
+>hosts deny</B
+>, <B
 CLASS="COMMAND"
->log level =</B
-> value is increased you will record 
-a significantly increasing level of debugging information. For most 
-debugging operations you may not need a setting higher than 3. Nearly 
-all bugs can be tracked at a setting of 10, but be prepared for a VERY 
-large volume of log data.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4664"
->32.4. Internal errors</A
-></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
-segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software).</P
-><P
->If the message came from smbd then it will probably be accompanied by
-a message which details the last SMB message received by smbd. This
-info is often very useful in tracking down the problem so please
-include it in your bug report.</P
+>valid users</B
+> or <B
+CLASS="COMMAND"
+>invalid users</B
+> lines.</P
 ><P
->You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.</P
+>If you get a "connection refused" response then the smbd server may
+not be running. If you installed it in inetd.conf then you probably edited
+that file incorrectly. If you installed it as a daemon then check that
+it is running, and check that the netbios-ssn port is in a LISTEN
+state using <KBD
+CLASS="USERINPUT"
+>netstat -a</KBD
+>.</P
 ><P
->You may also find that a core file appeared in a <TT
+>If you get a "session request failed" then the server refused the
+connection. If it says "Your server software is being unfriendly" then
+its probably because you have invalid command line parameters to <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+>,
+or a similar fatal problem with the initial startup of <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+>. Also
+check your config file (<TT
 CLASS="FILENAME"
->corefiles</TT
+>smb.conf</TT
+>) for syntax errors with <SPAN
+CLASS="APPLICATION"
+>testparm</SPAN
 >
-subdirectory of the directory where you keep your samba log
-files. This file is the most useful tool for tracking down the bug. To
-use it you do this:</P
+and that the various directories where samba keeps its log and lock
+files exist.</P
 ><P
-><B
-CLASS="COMMAND"
->gdb smbd core</B
+>There are a number of reasons for which smbd may refuse or decline
+a session request. The most common of these involve one or more of
+the following <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file entries:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy
+	bind interfaces only = Yes</PRE
 ></P
 ><P
->adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try <KBD
-CLASS="USERINPUT"
->dbx</KBD
->. Then within the debugger use the
-command <KBD
-CLASS="USERINPUT"
->where</KBD
-> to give a stack trace of where the problem
-occurred. Include this in your mail.</P
+>In the above, no allowance has been made for any session requests that
+will automatically translate to the loopback adaptor address 127.0.0.1.
+To solve this problem change these lines to:</P
 ><P
->If you known any assembly language then do a <KBD
-CLASS="USERINPUT"
->disass</KBD
-> of the routine
-where the problem occurred (if its in a library routine then
-disassemble the routine that called it) and try to work out exactly
-where the problem is by looking at the surrounding code. Even if you
-don't know assembly then incuding this info in the bug report can be
-useful. </P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4678"
->32.5. Attaching to a running process</A
-></H2
+><PRE
+CLASS="PROGRAMLISTING"
+>	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy 127.</PRE
+></P
 ><P
->Unfortunately some unixes (in particular some recent linux kernels)
-refuse to dump a core file if the task has changed uid (which smbd
-does often). To debug with this sort of system you could try to attach
-to the running process using <KBD
-CLASS="USERINPUT"
->gdb smbd <VAR
-CLASS="REPLACEABLE"
->PID</VAR
-></KBD
-> where you get <VAR
-CLASS="REPLACEABLE"
->PID</VAR
-> from
-<SPAN
+>Do NOT use the <B
+CLASS="COMMAND"
+>bind interfaces only</B
+> parameter where you 
+may wish to
+use the samba password change facility, or where <SPAN
 CLASS="APPLICATION"
->smbstatus</SPAN
->. Then use <KBD
-CLASS="USERINPUT"
->c</KBD
-> to continue and try to cause the core dump
-using the client. The debugger should catch the fault and tell you
-where it occurred.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4686"
->32.6. Patches</A
-></H2
+>smbclient</SPAN
+> may need to
+access local service for name resolution or for local resource
+connections. (Note: the <B
+CLASS="COMMAND"
+>bind interfaces only</B
+> parameter deficiency
+where it will not allow connections to the loopback address will be
+fixed soon).</P
 ><P
->The best sort of bug report is one that includes a fix! If you send us
-patches please use <KBD
-CLASS="USERINPUT"
->diff -u</KBD
-> format if your version of 
-diff supports it, otherwise use <KBD
+>Another common cause of these two errors is having something already running 
+on port 139, such as Samba (ie: smbd is running from <SPAN
+CLASS="APPLICATION"
+>inetd</SPAN
+> already) or
+something like Digital's Pathworks. Check your <TT
+CLASS="FILENAME"
+>inetd.conf</TT
+> file before trying
+to start <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+> as a daemon, it can avoid a lot of frustration!</P
+><P
+>And yet another possible cause for failure of this test is when the subnet mask
+and / or broadcast address settings are incorrect. Please check that the
+network interface IP Address / Broadcast Address / Subnet Mask settings are
+correct and that Samba has correctly noted these in the <TT
+CLASS="FILENAME"
+>log.nmb</TT
+> file.</P
+></LI
+><LI
+><P
+>Run the command <KBD
 CLASS="USERINPUT"
->diff -c4</KBD
->. Make sure 
-your do the diff against a clean version of the source and let me know 
-exactly what version you used. </P
-></DIV
-></DIV
-><DIV
-CLASS="CHAPTER"
-><HR><H1
-><A
-NAME="DIAGNOSIS"
-></A
->Chapter 33. The samba checklist</H1
-><DIV
-CLASS="SECT1"
-><H2
-CLASS="SECT1"
-><A
-NAME="AEN4709"
->33.1. Introduction</A
-></H2
+>nmblookup -B BIGSERVER __SAMBA__</KBD
+>. You should get the
+IP address of your Samba server back.</P
+><P
+>If you don't then nmbd is incorrectly installed. Check your <TT
+CLASS="FILENAME"
+>inetd.conf</TT
+>
+if you run it from there, or that the daemon is running and listening
+to udp port 137.</P
 ><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
-is if it fails any one of these steps. If it passes all these tests
-then it is probably working fine.</P
+>One common problem is that many inetd implementations can't take many
+parameters on the command line. If this is the case then create a
+one-line script that contains the right parameters and run that from
+inetd.</P
+></LI
+><LI
 ><P
->You should do ALL the tests, in the order shown. We have tried to
-carefully choose them so later tests only use capabilities verified in
-the earlier tests.</P
+>run the command <KBD
+CLASS="USERINPUT"
+>nmblookup -B ACLIENT '*'</KBD
+></P
 ><P
->If you send one of the samba mailing lists  an email saying "it doesn't work"
-and you have not followed this test procedure then you should not be surprised
-your email is ignored.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4714"
->33.2. Assumptions</A
-></H2
+>You should get the PCs IP address back. If you don't then the client
+software on the PC isn't installed correctly, or isn't started, or you
+got the name of the PC wrong. </P
 ><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
+>If ACLIENT doesn't resolve via DNS then use the IP address of the
+client in the above test.</P
+></LI
+><LI
 ><P
->The procedure is similar for other types of clients.</P
+>Run the command <KBD
+CLASS="USERINPUT"
+>nmblookup -d 2 '*'</KBD
+></P
 ><P
->It is also assumed you know the name of an available share in your
-<TT
-CLASS="FILENAME"
->smb.conf</TT
->. I will assume this share is called <VAR
-CLASS="REPLACEABLE"
->tmp</VAR
->.
-You can add a <VAR
-CLASS="REPLACEABLE"
->tmp</VAR
-> share like by adding the
-following to <TT
+>This time we are trying the same as the previous test but are trying
+it via a broadcast to the default broadcast address. A number of
+Netbios/TCPIP hosts on the network should respond, although Samba may
+not catch all of the responses in the short time it listens. You
+should see "got a positive name query response" messages from several
+hosts.</P
+><P
+>If this doesn't give a similar result to the previous test then
+nmblookup isn't correctly getting your broadcast address through its
+automatic mechanism. In this case you should experiment use the
+<B
+CLASS="COMMAND"
+>interfaces</B
+> option in <TT
 CLASS="FILENAME"
 >smb.conf</TT
->:</P
+> to manually configure your IP
+address, broadcast and netmask. </P
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->&#13;[tmp]
- comment = temporary files 
- path = /tmp
- read only = yes&#13;</PRE
+>If your PC and server aren't on the same subnet then you will need to
+use the <VAR
+CLASS="PARAMETER"
+>-B</VAR
+> option to set the broadcast address to the that of the PCs
+subnet.</P
+><P
+>This test will probably fail if your subnet mask and broadcast address are
+not correct. (Refer to TEST 3 notes above).</P
+></LI
+><LI
+><P
+>Run the command <KBD
+CLASS="USERINPUT"
+>smbclient //BIGSERVER/TMP</KBD
+>. You should 
+then be prompted for a password. You should use the password of the account
+you are logged into the unix box with. If you want to test with
+another account then add the <VAR
+CLASS="PARAMETER"
+>-U <VAR
+CLASS="REPLACEABLE"
+>accountname</VAR
+></VAR
+> option to the end of
+the command line.  eg: 
+<KBD
+CLASS="USERINPUT"
+>smbclient //bigserver/tmp -Ujohndoe</KBD
 ></P
 ><DIV
 CLASS="NOTE"
@@ -22400,673 +21196,951 @@ ALT="Note"></TD
 ALIGN="LEFT"
 VALIGN="TOP"
 ><P
->These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. </P
+>It is possible to specify the password along with the username
+as follows:
+<KBD
+CLASS="USERINPUT"
+>smbclient //bigserver/tmp -Ujohndoe%secret</KBD
+></P
 ></TD
 ></TR
 ></TABLE
 ></DIV
 ><P
->Please pay attention to the error messages you receive. If any error message
-reports that your server is being unfriendly you should first check that you
-IP name resolution is correctly set up. eg: Make sure your <TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
->
-file points to name servers that really do exist.</P
-><P
->Also, if you do not have DNS server access for name resolution please check
-that the settings for your <TT
+>Once you enter the password you should get the <SAMP
+CLASS="PROMPT"
+>smb&#62;</SAMP
+> prompt. If you
+don't then look at the error message. If it says "invalid network
+name" then the service "tmp" is not correctly setup in your <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> file results in <B
-CLASS="COMMAND"
->dns proxy = no</B
->. The
-best way to check this is with <KBD
-CLASS="USERINPUT"
->testparm smb.conf</KBD
 >.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><HR><H2
-CLASS="SECT1"
-><A
-NAME="AEN4733"
->33.3. The tests</A
-></H2
-><DIV
-CLASS="PROCEDURE"
 ><P
-><B
->Diagnosing your samba server</B
+>If it says "bad password" then the likely causes are:</P
+><P
 ></P
 ><OL
 TYPE="1"
 ><LI
 ><P
->In the directory in which you store your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file, run the command
-<KBD
-CLASS="USERINPUT"
->testparm smb.conf</KBD
->. If it reports any errors then your <TT
+>	you have shadow passords (or some other password system) but didn't
+	compile in support for them in <SPAN
+CLASS="APPLICATION"
+>smbd</SPAN
+>
+	</P
+></LI
+><LI
+><P
+>	your <B
+CLASS="COMMAND"
+>valid users</B
+> configuration is incorrect
+	</P
+></LI
+><LI
+><P
+>	you have a mixed case password and you haven't enabled the <B
+CLASS="COMMAND"
+>password
+	level</B
+> option at a high enough level
+	</P
+></LI
+><LI
+><P
+>	the <B
+CLASS="COMMAND"
+>path =</B
+> line in <TT
 CLASS="FILENAME"
 >smb.conf</TT
+> is incorrect. Check it with <SPAN
+CLASS="APPLICATION"
+>testparm</SPAN
 >
-configuration file is faulty.</P
-><DIV
-CLASS="NOTE"
+	</P
+></LI
+><LI
 ><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"
+>	you enabled password encryption but didn't create the SMB encrypted
+	password file
+	</P
+></LI
+></OL
+><P
+>Once connected you should be able to use the commands 
+<B
+CLASS="COMMAND"
+>dir</B
+> <B
+CLASS="COMMAND"
+>get</B
+> <B
+CLASS="COMMAND"
+>put</B
+> etc. 
+Type <B
+CLASS="COMMAND"
+>help <VAR
+CLASS="REPLACEABLE"
+>command</VAR
+></B
+> for instructions. You should
+especially check that the amount of free disk space shown is correct
+when you type <B
+CLASS="COMMAND"
+>dir</B
+>.</P
+></LI
+><LI
+><P
+>On the PC type the command <KBD
+CLASS="USERINPUT"
+>net view \\BIGSERVER</KBD
+>. You will 
+need to do this from within a "dos prompt" window. You should get back a 
+list of available shares on the server.</P
+><P
+>If you get a "network name not found" or similar error then netbios
+name resolution is not working. This is usually caused by a problem in
+nmbd. To overcome it you could do one of the following (you only need
+to choose one of them):</P
 ><P
->Your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file may be located in: <TT
-CLASS="FILENAME"
->/etc/samba</TT
->
-Or in:   <TT
-CLASS="FILENAME"
->/usr/local/samba/lib</TT
 ></P
-></TD
-></TR
-></TABLE
-></DIV
+><OL
+TYPE="1"
+><LI
+><P
+>	fixup the <SPAN
+CLASS="APPLICATION"
+>nmbd</SPAN
+> installation</P
 ></LI
 ><LI
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->ping BIGSERVER</KBD
-> from the PC and 
-<KBD
+>	add the IP address of BIGSERVER to the <B
+CLASS="COMMAND"
+>wins server</B
+> box in the
+	advanced tcp/ip setup on the PC.</P
+></LI
+><LI
+><P
+>	enable windows name resolution via DNS in the advanced section of
+	the tcp/ip setup</P
+></LI
+><LI
+><P
+>	add BIGSERVER to your lmhosts file on the PC.</P
+></LI
+></OL
+><P
+>If you get a "invalid network name" or "bad password error" then the
+same fixes apply as they did for the <KBD
 CLASS="USERINPUT"
->ping ACLIENT</KBD
-> from
-the unix box. If you don't get a valid response then your TCP/IP
-software is not correctly installed. </P
+>smbclient -L</KBD
+> test above. In
+particular, make sure your <B
+CLASS="COMMAND"
+>hosts allow</B
+> line is correct (see the man
+pages)</P
 ><P
->Note that you will need to start a "dos prompt" window on the PC to
-run ping.</P
+>Also, do not overlook that fact that when the workstation requests the
+connection to the samba server it will attempt to connect using the 
+name with which you logged onto your Windows machine. You need to make
+sure that an account exists on your Samba server with that exact same
+name and password.</P
 ><P
->If you get a message saying "host not found" or similar then your DNS
-software or <TT
+>If you get "specified computer is not receiving requests" or similar
+it probably means that the host is not contactable via tcp services.
+Check to see if the host is running tcp wrappers, and if so add an entry in
+the <TT
 CLASS="FILENAME"
->/etc/hosts</TT
-> file is not correctly setup.
-It is possible to
-run samba without DNS entries for the server and client, but I assume
-you do have correct entries for the remainder of these tests. </P
-><P
->Another reason why ping might fail is if your host is running firewall 
-software. You will need to relax the rules to let in the workstation
-in question, perhaps by allowing access from another subnet (on Linux
-this is done via the <SPAN
-CLASS="APPLICATION"
->ipfwadm</SPAN
-> program.)</P
+>hosts.allow</TT
+> file for your client (or subnet, etc.)</P
 ></LI
 ><LI
 ><P
 >Run the command <KBD
 CLASS="USERINPUT"
->smbclient -L BIGSERVER</KBD
-> on the unix box. You
-should get a list of available shares back. </P
-><P
->If you get a error message containing the string "Bad password" then
-you probably have either an incorrect <B
+>net use x: \\BIGSERVER\TMP</KBD
+>. You should 
+be prompted for a password then you should get a "command completed 
+successfully" message. If not then your PC software is incorrectly 
+installed or your smb.conf is incorrect. make sure your <B
 CLASS="COMMAND"
 >hosts allow</B
->, 
-<B
+>
+and other config lines in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> are correct.</P
+><P
+>It's also possible that the server can't work out what user name to
+connect you as. To see if this is the problem add the line <B
 CLASS="COMMAND"
->hosts deny</B
-> or <B
+>user =
+<VAR
+CLASS="REPLACEABLE"
+>username</VAR
+></B
+> to the <B
 CLASS="COMMAND"
->valid users</B
-> line in your 
+>[tmp]</B
+> section of 
 <TT
 CLASS="FILENAME"
 >smb.conf</TT
->, or your guest account is not
-valid. Check what your guest account is using <SPAN
-CLASS="APPLICATION"
->testparm</SPAN
-> and
-temporarily remove any <B
-CLASS="COMMAND"
->hosts allow</B
->, <B
-CLASS="COMMAND"
->hosts deny</B
->, <B
-CLASS="COMMAND"
->valid users</B
-> or <B
+> where <VAR
+CLASS="REPLACEABLE"
+>username</VAR
+> is the
+username corresponding to the password you typed. If you find this
+fixes things you may need the username mapping option. </P
+><P
+>It might also be the case that your client only sends encrypted passwords 
+and you have <B
 CLASS="COMMAND"
->invalid users</B
-> lines.</P
+>encrypt passwords = no</B
+> in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+Turn it back on to fix.</P
+></LI
+><LI
 ><P
->If you get a "connection refused" response then the smbd server may
-not be running. If you installed it in inetd.conf then you probably edited
-that file incorrectly. If you installed it as a daemon then check that
-it is running, and check that the netbios-ssn port is in a LISTEN
-state using <KBD
+>Run the command <KBD
 CLASS="USERINPUT"
->netstat -a</KBD
->.</P
+>nmblookup -M <VAR
+CLASS="REPLACEABLE"
+>testgroup</VAR
+></KBD
+> where 
+<VAR
+CLASS="REPLACEABLE"
+>testgroup</VAR
+> is the name of the workgroup that your Samba server and 
+Windows PCs belong to. You should get back the IP address of the 
+master browser for that workgroup.</P
 ><P
->If you get a "session request failed" then the server refused the
-connection. If it says "Your server software is being unfriendly" then
-its probably because you have invalid command line parameters to <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
->,
-or a similar fatal problem with the initial startup of <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
->. Also
-check your config file (<TT
+>If you don't then the election process has failed. Wait a minute to
+see if it is just being slow then try again. If it still fails after
+that then look at the browsing options you have set in <TT
 CLASS="FILENAME"
 >smb.conf</TT
->) for syntax errors with <SPAN
-CLASS="APPLICATION"
->testparm</SPAN
->
-and that the various directories where samba keeps its log and lock
-files exist.</P
+>. Make
+sure you have <B
+CLASS="COMMAND"
+>preferred master = yes</B
+> to ensure that 
+an election is held at startup.</P
+></LI
+><LI
 ><P
->There are a number of reasons for which smbd may refuse or decline
-a session request. The most common of these involve one or more of
-the following <TT
+>From file manager try to browse the server. Your samba server should
+appear in the browse list of your local workgroup (or the one you
+specified in smb.conf). You should be able to double click on the name
+of the server and get a list of shares. If you get a "invalid
+password" error when you do then you are probably running WinNT and it
+is refusing to browse a server that has no encrypted password
+capability and is in user level security mode. In this case either set
+<B
+CLASS="COMMAND"
+>security = server</B
+> AND 
+<B
+CLASS="COMMAND"
+>password server = Windows_NT_Machine</B
+> in your
+<TT
 CLASS="FILENAME"
 >smb.conf</TT
-> file entries:</P
+> file, or make sure <B
+CLASS="COMMAND"
+>encrypted passwords</B
+> is
+set to "yes".</P
+></LI
+></OL
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4951"
+>33.4. Still having troubles?</A
+></H2
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes</PRE
-></P
+>Read the chapter on 
+<A
+HREF="#PROBLEMS"
+>Analysing and Solving Problems</A
+>.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PROBLEMS"
+></A
+>Chapter 34. Analysing and solving samba problems</H1
 ><P
->In the above, no allowance has been made for any session requests that
-will automatically translate to the loopback adaptor address 127.0.0.1.
-To solve this problem change these lines to:</P
+>There are many sources of information available in the form 
+of mailing lists, RFC's and documentation.  The docs that come 
+with the samba distribution contain very good explanations of 
+general SMB topics such as browsing.</P
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4983"
+>34.1. Diagnostics tools</A
+></H2
 ><P
-><PRE
-CLASS="PROGRAMLISTING"
->	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.</PRE
-></P
+>One of the best diagnostic tools for debugging problems is Samba itself.  
+You can use the -d option for both smbd and nmbd to specify what 
+'debug level' at which to run.  See the man pages on smbd, nmbd  and 
+smb.conf for more information on debugging options.  The debug 
+level can range from 1 (the default) to 10 (100 for debugging passwords).</P
 ><P
->Do NOT use the <B
-CLASS="COMMAND"
->bind interfaces only</B
-> parameter where you 
-may wish to
-use the samba password change facility, or where <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-> may need to
-access local service for name resolution or for local resource
-connections. (Note: the <B
+>Another helpful method of debugging is to compile samba using the 
+<B
 CLASS="COMMAND"
->bind interfaces only</B
-> parameter deficiency
-where it will not allow connections to the loopback address will be
-fixed soon).</P
+>gcc -g </B
+> flag.   This will include debug 
+information in the binaries and allow you to attach gdb to the 
+running smbd / nmbd process.  In order to attach gdb to an smbd 
+process for an NT workstation, first get the workstation to make the 
+connection. Pressing ctrl-alt-delete and going down to the domain box 
+is sufficient (at least, on the first time you join the domain) to 
+generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
+maintains an open connection, and therefore there will be an smbd 
+process running (assuming that you haven't set a really short smbd 
+idle timeout)  So, in between pressing ctrl alt delete, and actually 
+typing in your password, you can gdb attach and continue.</P
 ><P
->Another common cause of these two errors is having something already running 
-on port 139, such as Samba (ie: smbd is running from <SPAN
-CLASS="APPLICATION"
->inetd</SPAN
-> already) or
-something like Digital's Pathworks. Check your <TT
-CLASS="FILENAME"
->inetd.conf</TT
-> file before trying
-to start <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
-> as a daemon, it can avoid a lot of frustration!</P
+>Some useful samba commands worth investigating:</P
 ><P
->And yet another possible cause for failure of this test is when the subnet mask
-and / or broadcast address settings are incorrect. Please check that the
-network interface IP Address / Broadcast Address / Subnet Mask settings are
-correct and that Samba has correctly noted these in the <TT
-CLASS="FILENAME"
->log.nmb</TT
-> file.</P
+></P
+><UL
+><LI
+><P
+>testparam | more</P
 ></LI
 ><LI
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->nmblookup -B BIGSERVER __SAMBA__</KBD
->. You should get the
-IP address of your Samba server back.</P
+>smbclient -L //{netbios name of server}</P
+></LI
+></UL
 ><P
->If you don't then nmbd is incorrectly installed. Check your <TT
-CLASS="FILENAME"
->inetd.conf</TT
->
-if you run it from there, or that the daemon is running and listening
-to udp port 137.</P
+>An SMB enabled version of tcpdump is available from 
+<A
+HREF="http://www.tcpdump.org/"
+TARGET="_top"
+>http://www.tcpdup.org/</A
+>.
+Ethereal, another good packet sniffer for Unix and Win32
+hosts, can be downloaded from <A
+HREF="http://www.ethereal.com/"
+TARGET="_top"
+>http://www.ethereal.com</A
+>.</P
 ><P
->One common problem is that many inetd implementations can't take many
-parameters on the command line. If this is the case then create a
-one-line script that contains the right parameters and run that from
-inetd.</P
-></LI
-><LI
+>For tracing things on the Microsoft Windows NT, Network Monitor 
+(aka. netmon) is available on the Microsoft Developer Network CD's, 
+the Windows NT Server install CD and the SMS CD's.  The version of 
+netmon that ships with SMS allows for dumping packets between any two 
+computers (i.e. placing the network interface in promiscuous mode).  
+The version on the NT Server install CD will only allow monitoring 
+of network traffic directed to the local NT box and broadcasts on the 
+local subnet.  Be aware that Ethereal can read and write netmon 
+formatted files.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN4998"
+>34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
+></H2
+><P
+>Installing netmon on an NT workstation requires a couple 
+of steps.  The following are for installing Netmon V4.00.349, which comes 
+with Microsoft Windows NT Server 4.0, on Microsoft Windows NT 
+Workstation 4.0.  The process should be similar for other version of 
+Windows NT / Netmon.  You will need both the Microsoft Windows 
+NT Server 4.0 Install CD and the Workstation 4.0 Install CD.</P
+><P
+>Initially you will need to install 'Network Monitor Tools and Agent' 
+on the NT Server.  To do this </P
 ><P
->run the command <KBD
-CLASS="USERINPUT"
->nmblookup -B ACLIENT '*'</KBD
 ></P
+><UL
+><LI
 ><P
->You should get the PCs IP address back. If you don't then the client
-software on the PC isn't installed correctly, or isn't started, or you
-got the name of the PC wrong. </P
+>Goto Start - Settings - Control Panel - 
+	Network - Services - Add </P
+></LI
+><LI
 ><P
->If ACLIENT doesn't resolve via DNS then use the IP address of the
-client in the above test.</P
+>Select the 'Network Monitor Tools and Agent' and 
+	click on 'OK'.</P
 ></LI
 ><LI
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->nmblookup -d 2 '*'</KBD
-></P
+>Click 'OK' on the Network Control Panel.
+	</P
+></LI
+><LI
 ><P
->This time we are trying the same as the previous test but are trying
-it via a broadcast to the default broadcast address. A number of
-Netbios/TCPIP hosts on the network should respond, although Samba may
-not catch all of the responses in the short time it listens. You
-should see "got a positive name query response" messages from several
-hosts.</P
+>Insert the Windows NT Server 4.0 install CD 
+	when prompted.</P
+></LI
+></UL
 ><P
->If this doesn't give a similar result to the previous test then
-nmblookup isn't correctly getting your broadcast address through its
-automatic mechanism. In this case you should experiment use the
-<B
-CLASS="COMMAND"
->interfaces</B
-> option in <TT
+>At this point the Netmon files should exist in 
+<TT
 CLASS="FILENAME"
->smb.conf</TT
-> to manually configure your IP
-address, broadcast and netmask. </P
+>%SYSTEMROOT%\System32\netmon\*.*</TT
+>.    
+Two subdirectories exist as well, <TT
+CLASS="FILENAME"
+>parsers\</TT
+> 
+which contains the necessary DLL's for parsing the netmon packet 
+dump, and <TT
+CLASS="FILENAME"
+>captures\</TT
+>.</P
 ><P
->If your PC and server aren't on the same subnet then you will need to
-use the <VAR
-CLASS="PARAMETER"
->-B</VAR
-> option to set the broadcast address to the that of the PCs
-subnet.</P
+>In order to install the Netmon tools on an NT Workstation, you will 
+first need to install the 'Network  Monitor Agent' from the Workstation 
+install CD.</P
 ><P
->This test will probably fail if your subnet mask and broadcast address are
-not correct. (Refer to TEST 3 notes above).</P
+></P
+><UL
+><LI
+><P
+>Goto Start - Settings - Control Panel - 
+	Network - Services - Add</P
 ></LI
 ><LI
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->smbclient //BIGSERVER/TMP</KBD
->. You should 
-then be prompted for a password. You should use the password of the account
-you are logged into the unix box with. If you want to test with
-another account then add the <VAR
-CLASS="PARAMETER"
->-U <VAR
-CLASS="REPLACEABLE"
->accountname</VAR
-></VAR
-> option to the end of
-the command line.  eg: 
-<KBD
-CLASS="USERINPUT"
->smbclient //bigserver/tmp -Ujohndoe</KBD
-></P
+>Select the 'Network Monitor Agent' and click 
+	on 'OK'.</P
+></LI
+><LI
+><P
+>Click 'OK' on the Network Control Panel.
+	</P
+></LI
+><LI
+><P
+>Insert the Windows NT Workstation 4.0 install 
+	CD when prompted.</P
+></LI
+></UL
+><P
+>Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
+to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
+permissions as  you deem appropriate for your site. You will need 
+administrative rights on the NT box to run netmon.</P
+><P
+>To install Netmon on a Windows 9x box install the network monitor agent 
+from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
+file located with the netmon driver files on the CD if you need 
+information on how to do this.  Copy the files from a working 
+Netmon installation.</P
+></DIV
 ><DIV
-CLASS="NOTE"
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5027"
+>34.3. Useful URL's</A
+></H2
 ><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"
+><UL
+><LI
 ><P
->It is possible to specify the password along with the username
-as follows:
-<KBD
-CLASS="USERINPUT"
->smbclient //bigserver/tmp -Ujohndoe%secret</KBD
-></P
-></TD
-></TR
-></TABLE
-></DIV
+>Home of Samba site <A
+HREF="http://samba.org"
+TARGET="_top"
+>      http://samba.org</A
+>. We have a mirror near you !</P
+></LI
+><LI
 ><P
->Once you enter the password you should get the <SAMP
-CLASS="PROMPT"
->smb&#62;</SAMP
-> prompt. If you
-don't then look at the error message. If it says "invalid network
-name" then the service "tmp" is not correctly setup in your <TT
-CLASS="FILENAME"
->smb.conf</TT
->.</P
+> The <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Development</I
+></SPAN
+> document 
+on the Samba mirrors might mention your problem. If so,
+it might mean that the developers are working on it.</P
+></LI
+><LI
+><P
+>See how Scott Merrill simulates a BDC behavior at 
+       <A
+HREF="http://www.skippy.net/linux/smb-howto.html"
+TARGET="_top"
+>       http://www.skippy.net/linux/smb-howto.html</A
+>. </P
+></LI
+><LI
 ><P
->If it says "bad password" then the likely causes are:</P
+>Although 2.0.7 has almost had its day as a PDC, David Bannon will
+       keep the 2.0.7 PDC pages at <A
+HREF="http://bioserve.latrobe.edu.au/samba"
+TARGET="_top"
+>       http://bioserve.latrobe.edu.au/samba</A
+> going for a while yet.</P
+></LI
+><LI
 ><P
+>Misc links to CIFS information 
+       <A
+HREF="http://samba.org/cifs/"
+TARGET="_top"
+>http://samba.org/cifs/</A
 ></P
-><OL
-TYPE="1"
+></LI
 ><LI
 ><P
->	you have shadow passords (or some other password system) but didn't
-	compile in support for them in <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
->
-	</P
+>NT Domains for Unix <A
+HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
+TARGET="_top"
+>       http://mailhost.cb1.com/~lkcl/ntdom/</A
+></P
 ></LI
 ><LI
 ><P
->	your <B
-CLASS="COMMAND"
->valid users</B
-> configuration is incorrect
-	</P
+>FTP site for older SMB specs: 
+       <A
+HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
+TARGET="_top"
+>       ftp://ftp.microsoft.com/developr/drg/CIFS/</A
+></P
 ></LI
-><LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5051"
+>34.4. Getting help from the mailing lists</A
+></H2
 ><P
->	you have a mixed case password and you haven't enabled the <B
+>There are a number of Samba related mailing lists. Go to <A
+HREF="http://samba.org"
+TARGET="_top"
+>http://samba.org</A
+>, click on your nearest mirror
+and then click on <B
 CLASS="COMMAND"
->password
-	level</B
-> option at a high enough level
-	</P
+>Support</B
+> and then click on <B
+CLASS="COMMAND"
+>Samba related mailing lists</B
+>.</P
+><P
+>For questions relating to Samba TNG go to
+<A
+HREF="http://www.samba-tng.org/"
+TARGET="_top"
+>http://www.samba-tng.org/</A
+> 
+It has been requested that you don't post questions about Samba-TNG to the
+main stream Samba lists.</P
+><P
+>If you post a message to one of the lists please observe the following guide lines :</P
+><P
+></P
+><UL
+><LI
+><P
+> Always remember that the developers are volunteers, they are 
+not paid and they never guarantee to produce a particular feature at 
+a particular time. Any time lines are 'best guess' and nothing more.</P
 ></LI
 ><LI
 ><P
->	the <B
-CLASS="COMMAND"
->path =</B
-> line in <TT
+> Always mention what version of samba you are using and what 
+operating system its running under. You should probably list the
+relevant sections of your <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> is incorrect. Check it with <SPAN
-CLASS="APPLICATION"
->testparm</SPAN
->
-	</P
+> file, at least the options 
+in [global] that affect PDC support.</P
 ></LI
 ><LI
 ><P
->	you enabled password encryption but didn't create the SMB encrypted
-	password file
-	</P
+>In addition to the version, if you obtained Samba via
+CVS mention the date when you last checked it out.</P
 ></LI
-></OL
+><LI
 ><P
->Once connected you should be able to use the commands 
-<B
-CLASS="COMMAND"
->dir</B
-> <B
-CLASS="COMMAND"
->get</B
-> <B
-CLASS="COMMAND"
->put</B
-> etc. 
-Type <B
-CLASS="COMMAND"
->help <VAR
-CLASS="REPLACEABLE"
->command</VAR
-></B
-> for instructions. You should
-especially check that the amount of free disk space shown is correct
-when you type <B
-CLASS="COMMAND"
->dir</B
->.</P
+> Try and make your question clear and brief, lots of long, 
+convoluted questions get deleted before	they are completely read ! 
+Don't post html encoded messages (if you can select colour or font 
+size its html).</P
 ></LI
 ><LI
 ><P
->On the PC type the command <KBD
-CLASS="USERINPUT"
->net view \\BIGSERVER</KBD
->. You will 
-need to do this from within a "dos prompt" window. You should get back a 
-list of available shares on the server.</P
-><P
->If you get a "network name not found" or similar error then netbios
-name resolution is not working. This is usually caused by a problem in
-nmbd. To overcome it you could do one of the following (you only need
-to choose one of them):</P
-><P
-></P
-><OL
-TYPE="1"
+> If you run one of those nifty 'I'm on holidays' things when 
+you are away, make sure its configured	to not answer mailing lists.</P
+></LI
 ><LI
 ><P
->	fixup the <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> installation</P
+> Don't cross post. Work out which is the best list to post to 
+and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
+Many people active on the lists subscribe to more 
+than one list and get annoyed to see the same message two or more times. 
+Often someone will see a message and thinking it would be better dealt 
+with on another, will forward it on for you.</P
 ></LI
 ><LI
 ><P
->	add the IP address of BIGSERVER to the <B
-CLASS="COMMAND"
->wins server</B
-> box in the
-	advanced tcp/ip setup on the PC.</P
+>You might include <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>partial</I
+></SPAN
+>
+log files written at a debug level set to as much as 20.  
+Please don't send the entire log but enough to give the context of the 
+error messages.</P
 ></LI
 ><LI
 ><P
->	enable windows name resolution via DNS in the advanced section of
-	the tcp/ip setup</P
+>(Possibly) If you have a complete netmon trace ( from the opening of 
+the pipe to the error ) you can send the *.CAP file as well.</P
 ></LI
 ><LI
 ><P
->	add BIGSERVER to your lmhosts file on the PC.</P
+>Please think carefully before attaching a document to an email.
+Consider pasting the relevant parts into the body of the message. The samba
+mailing lists go to a huge number of people, do they all need a copy of your 
+smb.conf in their attach directory?</P
 ></LI
-></OL
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5081"
+>34.5. How to get off the mailinglists</A
+></H2
 ><P
->If you get a "invalid network name" or "bad password error" then the
-same fixes apply as they did for the <KBD
-CLASS="USERINPUT"
->smbclient -L</KBD
-> test above. In
-particular, make sure your <B
+>To have your name removed from a samba mailing list, go to the
+same place you went to to get on it. Go to <A
+HREF="http://lists.samba.org/"
+TARGET="_top"
+>http://lists.samba.org</A
+>, 
+click on your nearest mirror and then click on <B
 CLASS="COMMAND"
->hosts allow</B
-> line is correct (see the man
-pages)</P
+>Support</B
+> and 
+then click on <B
+CLASS="COMMAND"
+> Samba related mailing lists</B
+>. Or perhaps see 
+<A
+HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
+TARGET="_top"
+>here</A
+></P
 ><P
->Also, do not overlook that fact that when the workstation requests the
-connection to the samba server it will attempt to connect using the 
-name with which you logged onto your Windows machine. You need to make
-sure that an account exists on your Samba server with that exact same
-name and password.</P
+>Please don't post messages to the list asking to be removed, you will just
+be referred to the above address (unless that process failed in some way...)</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="BUGREPORT"
+></A
+>Chapter 35. Reporting Bugs</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN5104"
+>35.1. Introduction</A
+></H2
 ><P
->If you get "specified computer is not receiving requests" or similar
-it probably means that the host is not contactable via tcp services.
-Check to see if the host is running tcp wrappers, and if so add an entry in
-the <TT
-CLASS="FILENAME"
->hosts.allow</TT
-> file for your client (or subnet, etc.)</P
-></LI
-><LI
+>The email address for bug reports for stable releases is <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>samba@samba.org</A
+>. 
+Bug reports for alpha releases should go to <A
+HREF="mailto:samba-technical@samba.org"
+TARGET="_top"
+>samba-technical@samba.org</A
+>.</P
+><P
+>Please take the time to read this file before you submit a bug
+report. Also, please see if it has changed between releases, as we
+may be changing the bug reporting mechanism at some time.</P
+><P
+>Please also do as much as you can yourself to help track down the
+bug. Samba is maintained by a dedicated group of people who volunteer
+their time, skills and efforts. We receive far more mail about it than
+we can possibly answer, so you have a much higher chance of an answer
+and a fix if you send us a "developer friendly" bug report that lets
+us fix it fast. </P
+><P
+>Do not assume that if you post the bug to the comp.protocols.smb
+newsgroup or the mailing list that we will read it. If you suspect that your 
+problem is not a bug but a configuration problem then it is better to send 
+it to the Samba mailing list, as there are (at last count) 5000 other users on
+that list that may be able to help you.</P
+><P
+>You may also like to look though the recent mailing list archives,
+which are conveniently accessible on the Samba web pages
+at <A
+HREF="http://samba.org/samba/"
+TARGET="_top"
+>http://samba.org/samba/</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5114"
+>35.2. General info</A
+></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
+you've misconfigured something and run testparm to test your config
+file for correct syntax.</P
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->net use x: \\BIGSERVER\TMP</KBD
->. You should 
-be prompted for a password then you should get a "command completed 
-successfully" message. If not then your PC software is incorrectly 
-installed or your smb.conf is incorrect. make sure your <B
-CLASS="COMMAND"
->hosts allow</B
->
-and other config lines in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> are correct.</P
+>Have you run through the <A
+HREF="#DIAGNOSIS"
+>diagnosis</A
+>? 
+This is very important.</P
 ><P
->It's also possible that the server can't work out what user name to
-connect you as. To see if this is the problem add the line <B
-CLASS="COMMAND"
->user =
-<VAR
-CLASS="REPLACEABLE"
->username</VAR
-></B
-> to the <B
+>If you include part of a log file with your bug report then be sure to
+annotate it with exactly what you were doing on the client at the
+time, and exactly what the results were.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5120"
+>35.3. Debug levels</A
+></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
+be very useful. Depending on the problem a log level of between 3 and
+10 showing the problem may be appropriate. A higher level givesmore
+detail, but may use too much disk space.</P
+><P
+>To set the debug level use <B
 CLASS="COMMAND"
->[tmp]</B
-> section of 
+>log level =</B
+> in your 
 <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> where <VAR
-CLASS="REPLACEABLE"
->username</VAR
-> is the
-username corresponding to the password you typed. If you find this
-fixes things you may need the username mapping option. </P
+>. You may also find it useful to set the log 
+level higher for just one machine and keep separate logs for each machine. 
+To do this use:</P
 ><P
->It might also be the case that your client only sends encrypted passwords 
-and you have <B
-CLASS="COMMAND"
->encrypt passwords = no</B
-> in <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-Turn it back on to fix.</P
-></LI
-><LI
+><PRE
+CLASS="PROGRAMLISTING"
+>log level = 10
+log file = /usr/local/samba/lib/log.%m
+include = /usr/local/samba/lib/smb.conf.%m</PRE
+></P
 ><P
->Run the command <KBD
-CLASS="USERINPUT"
->nmblookup -M <VAR
+>then create a file 
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf.<VAR
 CLASS="REPLACEABLE"
->testgroup</VAR
-></KBD
-> where 
+>machine</VAR
+></TT
+> where
 <VAR
 CLASS="REPLACEABLE"
->testgroup</VAR
-> is the name of the workgroup that your Samba server and 
-Windows PCs belong to. You should get back the IP address of the 
-master browser for that workgroup.</P
-><P
->If you don't then the election process has failed. Wait a minute to
-see if it is just being slow then try again. If it still fails after
-that then look at the browsing options you have set in <TT
+>machine</VAR
+> is the name of the client you wish to debug. In that file
+put any <TT
 CLASS="FILENAME"
 >smb.conf</TT
->. Make
-sure you have <B
+> commands you want, for example 
+<B
 CLASS="COMMAND"
->preferred master = yes</B
-> to ensure that 
-an election is held at startup.</P
-></LI
-><LI
+>log level=</B
+> may be useful. This also allows you to 
+experiment with different security systems, protocol levels etc on just 
+one machine.</P
 ><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
-specified in smb.conf). You should be able to double click on the name
-of the server and get a list of shares. If you get a "invalid
-password" error when you do then you are probably running WinNT and it
-is refusing to browse a server that has no encrypted password
-capability and is in user level security mode. In this case either set
-<B
+>The <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> entry <B
 CLASS="COMMAND"
->security = server</B
-> AND 
-<B
+>log level =</B
+> 
+is synonymous with the entry <B
 CLASS="COMMAND"
->password server = Windows_NT_Machine</B
-> in your
-<TT
+>debuglevel =</B
+> that has been 
+used in older versions of Samba and is being retained for backwards 
+compatibility of <TT
 CLASS="FILENAME"
 >smb.conf</TT
-> file, or make sure <B
+> files.</P
+><P
+>As the <B
 CLASS="COMMAND"
->encrypted passwords</B
-> is
-set to "yes".</P
-></LI
-></OL
-></DIV
+>log level =</B
+> value is increased you will record 
+a significantly increasing level of debugging information. For most 
+debugging operations you may not need a setting higher than 3. Nearly 
+all bugs can be tracked at a setting of 10, but be prepared for a VERY 
+large volume of log data.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><HR><H2
 CLASS="SECT1"
 ><A
-NAME="AEN4900"
->33.4. Still having troubles?</A
+NAME="AEN5141"
+>35.4. Internal errors</A
 ></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
-<A
-HREF="mailto:samba@samba.org"
-TARGET="_top"
->samba@samba.org</A
->. To find 
-out more about samba and how to subscribe to the mailing list check 
-out the samba web page at 
-<A
-HREF="http://samba.org/samba"
-TARGET="_top"
->http://samba.org/samba/</A
+>If you get a "INTERNAL ERROR" message in your log files it means that
+Samba got an unexpected signal while running. It is probably a
+segmentation fault and almost certainly means a bug in Samba (unless
+you have faulty hardware or system software).</P
+><P
+>If the message came from smbd then it will probably be accompanied by
+a message which details the last SMB message received by smbd. This
+info is often very useful in tracking down the problem so please
+include it in your bug report.</P
+><P
+>You should also detail how to reproduce the problem, if
+possible. Please make this reasonably detailed.</P
+><P
+>You may also find that a core file appeared in a <TT
+CLASS="FILENAME"
+>corefiles</TT
+>
+subdirectory of the directory where you keep your samba log
+files. This file is the most useful tool for tracking down the bug. To
+use it you do this:</P
+><P
+><B
+CLASS="COMMAND"
+>gdb smbd core</B
 ></P
+><P
+>adding appropriate paths to smbd and core so gdb can find them. If you
+don't have gdb then try <KBD
+CLASS="USERINPUT"
+>dbx</KBD
+>. Then within the debugger use the
+command <KBD
+CLASS="USERINPUT"
+>where</KBD
+> to give a stack trace of where the problem
+occurred. Include this in your mail.</P
+><P
+>If you known any assembly language then do a <KBD
+CLASS="USERINPUT"
+>disass</KBD
+> of the routine
+where the problem occurred (if its in a library routine then
+disassemble the routine that called it) and try to work out exactly
+where the problem is by looking at the surrounding code. Even if you
+don't know assembly then incuding this info in the bug report can be
+useful. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5155"
+>35.5. Attaching to a running process</A
+></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
+does often). To debug with this sort of system you could try to attach
+to the running process using <KBD
+CLASS="USERINPUT"
+>gdb smbd <VAR
+CLASS="REPLACEABLE"
+>PID</VAR
+></KBD
+> where you get <VAR
+CLASS="REPLACEABLE"
+>PID</VAR
+> from
+<SPAN
+CLASS="APPLICATION"
+>smbstatus</SPAN
+>. Then use <KBD
+CLASS="USERINPUT"
+>c</KBD
+> to continue and try to cause the core dump
+using the client. The debugger should catch the fault and tell you
+where it occurred.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN5163"
+>35.6. Patches</A
+></H2
+><P
+>The best sort of bug report is one that includes a fix! If you send us
+patches please use <KBD
+CLASS="USERINPUT"
+>diff -u</KBD
+> format if your version of 
+diff supports it, otherwise use <KBD
+CLASS="USERINPUT"
+>diff -c4</KBD
+>. Make sure 
+your do the diff against a clean version of the source and let me know 
+exactly what version you used. </P
 ></DIV
 ></DIV
 ></DIV
diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html
index 45236cda46..b31d572f90 100644
--- a/docs/htmldocs/ads.html
+++ b/docs/htmldocs/ads.html
@@ -17,7 +17,7 @@ TITLE="Samba Backup Domain Controller to Samba Domain Control"
 HREF="samba-bdc.html"><LINK
 REL="NEXT"
 TITLE="Samba as a NT4 or Win2k domain member"
-HREF="domain-security.html"></HEAD
+HREF="domain-member.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -59,7 +59,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="domain-security.html"
+HREF="domain-member.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -74,7 +74,55 @@ CLASS="CHAPTER"
 ><A
 NAME="ADS"
 ></A
->Chapter 8. Samba as a ADS domain member</H1
+>Chapter 9. Samba as a ADS domain member</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>9.1. <A
+HREF="ads.html#AEN1364"
+>Setup your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+></A
+></DT
+><DT
+>9.2. <A
+HREF="ads.html#AEN1377"
+>Setup your <TT
+CLASS="FILENAME"
+>/etc/krb5.conf</TT
+></A
+></DT
+><DT
+>9.3. <A
+HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
+>Create the computer account</A
+></DT
+><DT
+>9.4. <A
+HREF="ads.html#ADS-TEST-SERVER"
+>Test your server setup</A
+></DT
+><DT
+>9.5. <A
+HREF="ads.html#ADS-TEST-SMBCLIENT"
+>Testing with <SPAN
+CLASS="APPLICATION"
+>smbclient</SPAN
+></A
+></DT
+><DT
+>9.6. <A
+HREF="ads.html#AEN1425"
+>Notes</A
+></DT
+></DL
+></DIV
 ><P
 >This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
 Windows2000 KDC. </P
@@ -83,8 +131,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1355"
->8.1. Setup your <TT
+NAME="AEN1364"
+>9.1. Setup your <TT
 CLASS="FILENAME"
 >smb.conf</TT
 ></A
@@ -151,8 +199,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1368"
->8.2. Setup your <TT
+NAME="AEN1377"
+>9.2. Setup your <TT
 CLASS="FILENAME"
 >/etc/krb5.conf</TT
 ></A
@@ -257,7 +305,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-CREATE-MACHINE-ACCOUNT"
->8.3. Create the computer account</A
+>9.3. Create the computer account</A
 ></H1
 ><P
 >As a user that has write permission on the Samba private directory
@@ -271,8 +319,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1396"
->8.3.1. Possible errors</A
+NAME="AEN1405"
+>9.3.1. Possible errors</A
 ></H2
 ><P
 ><P
@@ -297,7 +345,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-TEST-SERVER"
->8.4. Test your server setup</A
+>9.4. Test your server setup</A
 ></H1
 ><P
 >On a Windows 2000 client try <KBD
@@ -317,7 +365,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="ADS-TEST-SMBCLIENT"
->8.5. Testing with <SPAN
+>9.5. Testing with <SPAN
 CLASS="APPLICATION"
 >smbclient</SPAN
 ></A
@@ -341,8 +389,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1416"
->8.6. Notes</A
+NAME="AEN1425"
+>9.6. Notes</A
 ></H1
 ><P
 >You must change administrator password at least once after DC 
@@ -386,7 +434,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="domain-security.html"
+HREF="domain-member.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html
index ff0588130c..8015702c51 100644
--- a/docs/htmldocs/appendixes.html
+++ b/docs/htmldocs/appendixes.html
@@ -13,8 +13,8 @@ REL="PREVIOUS"
 TITLE="Unicode/Charsets"
 HREF="unicode.html"><LINK
 REL="NEXT"
-TITLE="SWAT - The Samba Web Admininistration Tool"
-HREF="swat.html"></HEAD
+TITLE="How to compile SAMBA"
+HREF="compiling.html"></HEAD
 ><BODY
 CLASS="PART"
 BGCOLOR="#FFFFFF"
@@ -56,7 +56,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="swat.html"
+HREF="compiling.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -75,438 +75,6 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >IV. Appendixes</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->26. <A
-HREF="swat.html"
->SWAT - The Samba Web Admininistration Tool</A
-></DT
-><DD
-><DL
-><DT
->26.1. <A
-HREF="swat.html#AEN4098"
->SWAT Features and Benefits</A
-></DT
-><DD
-><DL
-><DT
->26.1.1. <A
-HREF="swat.html#AEN4101"
->The SWAT Home Page</A
-></DT
-><DT
->26.1.2. <A
-HREF="swat.html#AEN4104"
->Global Settings</A
-></DT
-><DT
->26.1.3. <A
-HREF="swat.html#AEN4107"
->The SWAT Wizard</A
-></DT
-><DT
->26.1.4. <A
-HREF="swat.html#AEN4110"
->Share Settings</A
-></DT
-><DT
->26.1.5. <A
-HREF="swat.html#AEN4113"
->Printing Settings</A
-></DT
-><DT
->26.1.6. <A
-HREF="swat.html#AEN4116"
->The Status Page</A
-></DT
-><DT
->26.1.7. <A
-HREF="swat.html#AEN4119"
->The Password Change Page</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->27. <A
-HREF="nt4migration.html"
->Migration from NT4 PDC to Samba-3 PDC</A
-></DT
-><DD
-><DL
-><DT
->27.1. <A
-HREF="nt4migration.html#AEN4134"
->Planning and Getting Started</A
-></DT
-><DD
-><DL
-><DT
->27.1.1. <A
-HREF="nt4migration.html#AEN4137"
->Objectives</A
-></DT
-><DT
->27.1.2. <A
-HREF="nt4migration.html#AEN4140"
->Steps In Migration Process</A
-></DT
-></DL
-></DD
-><DT
->27.2. <A
-HREF="nt4migration.html#AEN4143"
->Managing Samba-3 Domain Control</A
-></DT
-></DL
-></DD
-><DT
->28. <A
-HREF="speed.html"
->Samba performance issues</A
-></DT
-><DD
-><DL
-><DT
->28.1. <A
-HREF="speed.html#AEN4163"
->Comparisons</A
-></DT
-><DT
->28.2. <A
-HREF="speed.html#AEN4169"
->Socket options</A
-></DT
-><DT
->28.3. <A
-HREF="speed.html#AEN4176"
->Read size</A
-></DT
-><DT
->28.4. <A
-HREF="speed.html#AEN4181"
->Max xmit</A
-></DT
-><DT
->28.5. <A
-HREF="speed.html#AEN4186"
->Log level</A
-></DT
-><DT
->28.6. <A
-HREF="speed.html#AEN4189"
->Read raw</A
-></DT
-><DT
->28.7. <A
-HREF="speed.html#AEN4194"
->Write raw</A
-></DT
-><DT
->28.8. <A
-HREF="speed.html#AEN4198"
->Slow Clients</A
-></DT
-><DT
->28.9. <A
-HREF="speed.html#AEN4202"
->Slow Logins</A
-></DT
-><DT
->28.10. <A
-HREF="speed.html#AEN4205"
->Client tuning</A
-></DT
-></DL
-></DD
-><DT
->29. <A
-HREF="portability.html"
->Portability</A
-></DT
-><DD
-><DL
-><DT
->29.1. <A
-HREF="portability.html#AEN4249"
->HPUX</A
-></DT
-><DT
->29.2. <A
-HREF="portability.html#AEN4255"
->SCO Unix</A
-></DT
-><DT
->29.3. <A
-HREF="portability.html#AEN4259"
->DNIX</A
-></DT
-><DT
->29.4. <A
-HREF="portability.html#AEN4288"
->RedHat Linux Rembrandt-II</A
-></DT
-><DT
->29.5. <A
-HREF="portability.html#AEN4294"
->AIX</A
-></DT
-><DD
-><DL
-><DT
->29.5.1. <A
-HREF="portability.html#AEN4296"
->Sequential Read Ahead</A
-></DT
-></DL
-></DD
-><DT
->29.6. <A
-HREF="portability.html#AEN4300"
->Solaris</A
-></DT
-></DL
-></DD
-><DT
->30. <A
-HREF="other-clients.html"
->Samba and other CIFS clients</A
-></DT
-><DD
-><DL
-><DT
->30.1. <A
-HREF="other-clients.html#AEN4326"
->Macintosh clients?</A
-></DT
-><DT
->30.2. <A
-HREF="other-clients.html#AEN4335"
->OS2 Client</A
-></DT
-><DD
-><DL
-><DT
->30.2.1. <A
-HREF="other-clients.html#AEN4337"
->How can I configure OS/2 Warp Connect or 
-		OS/2 Warp 4 as a client for Samba?</A
-></DT
-><DT
->30.2.2. <A
-HREF="other-clients.html#AEN4352"
->How can I configure OS/2 Warp 3 (not Connect), 
-		OS/2 1.2, 1.3 or 2.x for Samba?</A
-></DT
-><DT
->30.2.3. <A
-HREF="other-clients.html#AEN4361"
->Are there any other issues when OS/2 (any version) 
-		is used as a client?</A
-></DT
-><DT
->30.2.4. <A
-HREF="other-clients.html#AEN4365"
->How do I get printer driver download working 
-		for OS/2 clients?</A
-></DT
-></DL
-></DD
-><DT
->30.3. <A
-HREF="other-clients.html#AEN4375"
->Windows for Workgroups</A
-></DT
-><DD
-><DL
-><DT
->30.3.1. <A
-HREF="other-clients.html#AEN4377"
->Use latest TCP/IP stack from Microsoft</A
-></DT
-><DT
->30.3.2. <A
-HREF="other-clients.html#AEN4382"
->Delete .pwl files after password change</A
-></DT
-><DT
->30.3.3. <A
-HREF="other-clients.html#AEN4387"
->Configure WfW password handling</A
-></DT
-><DT
->30.3.4. <A
-HREF="other-clients.html#AEN4391"
->Case handling of passwords</A
-></DT
-><DT
->30.3.5. <A
-HREF="other-clients.html#AEN4396"
->Use TCP/IP as default protocol</A
-></DT
-></DL
-></DD
-><DT
->30.4. <A
-HREF="other-clients.html#AEN4399"
->Windows '95/'98</A
-></DT
-><DT
->30.5. <A
-HREF="other-clients.html#AEN4415"
->Windows 2000 Service Pack 2</A
-></DT
-><DT
->30.6. <A
-HREF="other-clients.html#AEN4432"
->Windows NT 3.1</A
-></DT
-></DL
-></DD
-><DT
->31. <A
-HREF="compiling.html"
->How to compile SAMBA</A
-></DT
-><DD
-><DL
-><DT
->31.1. <A
-HREF="compiling.html#AEN4453"
->Access Samba source code via CVS</A
-></DT
-><DD
-><DL
-><DT
->31.1.1. <A
-HREF="compiling.html#AEN4455"
->Introduction</A
-></DT
-><DT
->31.1.2. <A
-HREF="compiling.html#AEN4460"
->CVS Access to samba.org</A
-></DT
-></DL
-></DD
-><DT
->31.2. <A
-HREF="compiling.html#AEN4496"
->Accessing the samba sources via rsync and ftp</A
-></DT
-><DT
->31.3. <A
-HREF="compiling.html#AEN4502"
->Building the Binaries</A
-></DT
-><DD
-><DL
-><DT
->31.3.1. <A
-HREF="compiling.html#AEN4530"
->Compiling samba with Active Directory support</A
-></DT
-></DL
-></DD
-><DT
->31.4. <A
-HREF="compiling.html#AEN4559"
->Starting the smbd and nmbd</A
-></DT
-><DD
-><DL
-><DT
->31.4.1. <A
-HREF="compiling.html#AEN4569"
->Starting from inetd.conf</A
-></DT
-><DT
->31.4.2. <A
-HREF="compiling.html#AEN4603"
->Alternative: starting it as a daemon</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->32. <A
-HREF="bugreport.html"
->Reporting Bugs</A
-></DT
-><DD
-><DL
-><DT
->32.1. <A
-HREF="bugreport.html#AEN4634"
->Introduction</A
-></DT
-><DT
->32.2. <A
-HREF="bugreport.html#AEN4644"
->General info</A
-></DT
-><DT
->32.3. <A
-HREF="bugreport.html#AEN4650"
->Debug levels</A
-></DT
-><DT
->32.4. <A
-HREF="bugreport.html#AEN4671"
->Internal errors</A
-></DT
-><DT
->32.5. <A
-HREF="bugreport.html#AEN4685"
->Attaching to a running process</A
-></DT
-><DT
->32.6. <A
-HREF="bugreport.html#AEN4693"
->Patches</A
-></DT
-></DL
-></DD
-><DT
->33. <A
-HREF="diagnosis.html"
->The samba checklist</A
-></DT
-><DD
-><DL
-><DT
->33.1. <A
-HREF="diagnosis.html#AEN4716"
->Introduction</A
-></DT
-><DT
->33.2. <A
-HREF="diagnosis.html#AEN4721"
->Assumptions</A
-></DT
-><DT
->33.3. <A
-HREF="diagnosis.html#AEN4740"
->The tests</A
-></DT
-><DT
->33.4. <A
-HREF="diagnosis.html#AEN4907"
->Still having troubles?</A
-></DT
-></DL
-></DD
-></DL
-></DIV
 ></DIV
 ></DIV
 ><DIV
@@ -543,7 +111,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="swat.html"
+HREF="compiling.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -563,7 +131,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->SWAT - The Samba Web Admininistration Tool</TD
+>How to compile SAMBA</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html
index 95a1ca3504..843fa377c2 100644
--- a/docs/htmldocs/browsing-quick.html
+++ b/docs/htmldocs/browsing-quick.html
@@ -74,7 +74,72 @@ CLASS="CHAPTER"
 ><A
 NAME="BROWSING-QUICK"
 ></A
->Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
+>Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>3.1. <A
+HREF="browsing-quick.html#AEN306"
+>Discussion</A
+></DT
+><DT
+>3.2. <A
+HREF="browsing-quick.html#AEN327"
+>How browsing functions and how to deploy stable and 
+dependable browsing using Samba</A
+></DT
+><DT
+>3.3. <A
+HREF="browsing-quick.html#AEN341"
+>Use of the <B
+CLASS="COMMAND"
+>Remote Announce</B
+> parameter</A
+></DT
+><DT
+>3.4. <A
+HREF="browsing-quick.html#AEN364"
+>Use of the <B
+CLASS="COMMAND"
+>Remote Browse Sync</B
+> parameter</A
+></DT
+><DT
+>3.5. <A
+HREF="browsing-quick.html#AEN375"
+>Use of WINS</A
+></DT
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="browsing-quick.html#AEN392"
+>WINS Replication</A
+></DT
+><DT
+>3.5.2. <A
+HREF="browsing-quick.html#AEN396"
+>Static WINS Entries</A
+></DT
+></DL
+></DD
+><DT
+>3.6. <A
+HREF="browsing-quick.html#AEN401"
+>Do NOT use more than one (1) protocol on MS Windows machines</A
+></DT
+><DT
+>3.7. <A
+HREF="browsing-quick.html#AEN409"
+>Name Resolution Order</A
+></DT
+></DL
+></DIV
 ><P
 >This document should be read in conjunction with Browsing and may
 be taken as the fast track guide to implementing browsing across subnets
@@ -113,8 +178,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN183"
->2.1. Discussion</A
+NAME="AEN306"
+>3.1. Discussion</A
 ></H1
 ><P
 >Firstly, all MS Windows networking is based on SMB (Server Message
@@ -204,8 +269,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN204"
->2.2. How browsing functions and how to deploy stable and 
+NAME="AEN327"
+>3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba</A
 ></H1
 ><P
@@ -284,8 +349,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN218"
->2.3. Use of the <B
+NAME="AEN341"
+>3.3. Use of the <B
 CLASS="COMMAND"
 >Remote Announce</B
 > parameter</A
@@ -371,8 +436,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN241"
->2.4. Use of the <B
+NAME="AEN364"
+>3.4. Use of the <B
 CLASS="COMMAND"
 >Remote Browse Sync</B
 > parameter</A
@@ -413,8 +478,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN252"
->2.5. Use of WINS</A
+NAME="AEN375"
+>3.5. Use of WINS</A
 ></H1
 ><P
 >Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
@@ -509,14 +574,50 @@ CLASS="APPLICATION"
 ></TR
 ></TABLE
 ></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN392"
+>3.5.1. WINS Replication</A
+></H2
+><P
+>Samba-3 permits WINS replication through the use of the <TT
+CLASS="FILENAME"
+>wrepld</TT
+> utility.
+This tool is not currently capable of being used as it is still in active development.
+As soon as this tool becomes moderately functional we will prepare man pages and enhance this
+section of the documentation to provide usage and technical details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN396"
+>3.5.2. Static WINS Entries</A
+></H2
+><P
+>New to Samba-3 is a tool called <TT
+CLASS="FILENAME"
+>winsedit</TT
+> that may be used to add
+static WINS entries to the WINS database. This tool can be used also to modify entries
+existing in the WINS database.</P
+><P
+>The development of the winsedit tool was made necessary due to the migration
+of the older style wins.dat file into a new tdb binary backend data store.</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN269"
->2.6. Do NOT use more than one (1) protocol on MS Windows machines</A
+NAME="AEN401"
+>3.6. Do NOT use more than one (1) protocol on MS Windows machines</A
 ></H1
 ><P
 >A very common cause of browsing problems results from installing more than
@@ -558,8 +659,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN277"
->2.7. Name Resolution Order</A
+NAME="AEN409"
+>3.7. Name Resolution Order</A
 ></H1
 ><P
 >Resolution of NetBIOS names to IP addresses can take place using a number
diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html
index 516d187e6a..9aa2fcfe2a 100644
--- a/docs/htmldocs/bugreport.html
+++ b/docs/htmldocs/bugreport.html
@@ -13,11 +13,8 @@ REL="UP"
 TITLE="Appendixes"
 HREF="appendixes.html"><LINK
 REL="PREVIOUS"
-TITLE="How to compile SAMBA"
-HREF="compiling.html"><LINK
-REL="NEXT"
-TITLE="The samba checklist"
-HREF="diagnosis.html"></HEAD
+TITLE="Analysing and solving samba problems"
+HREF="problems.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -45,7 +42,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="compiling.html"
+HREF="problems.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -58,11 +55,7 @@ VALIGN="bottom"
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
-><A
-HREF="diagnosis.html"
-ACCESSKEY="N"
->Next</A
-></TD
+>&nbsp;</TD
 ></TR
 ></TABLE
 ><HR
@@ -74,14 +67,53 @@ CLASS="CHAPTER"
 ><A
 NAME="BUGREPORT"
 ></A
->Chapter 32. Reporting Bugs</H1
+>Chapter 35. Reporting Bugs</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>35.1. <A
+HREF="bugreport.html#AEN5104"
+>Introduction</A
+></DT
+><DT
+>35.2. <A
+HREF="bugreport.html#AEN5114"
+>General info</A
+></DT
+><DT
+>35.3. <A
+HREF="bugreport.html#AEN5120"
+>Debug levels</A
+></DT
+><DT
+>35.4. <A
+HREF="bugreport.html#AEN5141"
+>Internal errors</A
+></DT
+><DT
+>35.5. <A
+HREF="bugreport.html#AEN5155"
+>Attaching to a running process</A
+></DT
+><DT
+>35.6. <A
+HREF="bugreport.html#AEN5163"
+>Patches</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4634"
->32.1. Introduction</A
+NAME="AEN5104"
+>35.1. Introduction</A
 ></H1
 ><P
 >The email address for bug reports for stable releases is <A
@@ -125,8 +157,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4644"
->32.2. General info</A
+NAME="AEN5114"
+>35.2. General info</A
 ></H1
 ><P
 >Before submitting a bug report check your config for silly
@@ -149,8 +181,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4650"
->32.3. Debug levels</A
+NAME="AEN5120"
+>35.3. Debug levels</A
 ></H1
 ><P
 >If the bug has anything to do with Samba behaving incorrectly as a
@@ -231,8 +263,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4671"
->32.4. Internal errors</A
+NAME="AEN5141"
+>35.4. Internal errors</A
 ></H1
 ><P
 >If you get a "INTERNAL ERROR" message in your log files it means that
@@ -287,8 +319,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4685"
->32.5. Attaching to a running process</A
+NAME="AEN5155"
+>35.5. Attaching to a running process</A
 ></H1
 ><P
 >Unfortunately some unixes (in particular some recent linux kernels)
@@ -319,8 +351,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4693"
->32.6. Patches</A
+NAME="AEN5163"
+>35.6. Patches</A
 ></H1
 ><P
 >The best sort of bug report is one that includes a fix! If you send us
@@ -352,7 +384,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="compiling.html"
+HREF="problems.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -369,18 +401,14 @@ ACCESSKEY="H"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
-><A
-HREF="diagnosis.html"
-ACCESSKEY="N"
->Next</A
-></TD
+>&nbsp;</TD
 ></TR
 ><TR
 ><TD
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->How to compile SAMBA</TD
+>Analysing and solving samba problems</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -394,7 +422,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->The samba checklist</TD
+>&nbsp;</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html
index c387dd72fb..77633836b9 100644
--- a/docs/htmldocs/compiling.html
+++ b/docs/htmldocs/compiling.html
@@ -13,11 +13,11 @@ REL="UP"
 TITLE="Appendixes"
 HREF="appendixes.html"><LINK
 REL="PREVIOUS"
-TITLE="Samba and other CIFS clients"
-HREF="other-clients.html"><LINK
+TITLE="Appendixes"
+HREF="appendixes.html"><LINK
 REL="NEXT"
-TITLE="Reporting Bugs"
-HREF="bugreport.html"></HEAD
+TITLE="Migration from NT4 PDC to Samba-3 PDC"
+HREF="nt4migration.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -45,7 +45,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="other-clients.html"
+HREF="appendixes.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -59,7 +59,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="bugreport.html"
+HREF="nt4migration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -74,29 +74,105 @@ CLASS="CHAPTER"
 ><A
 NAME="COMPILING"
 ></A
->Chapter 31. How to compile SAMBA</H1
+>Chapter 27. How to compile SAMBA</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>27.1. <A
+HREF="compiling.html#AEN4183"
+>Access Samba source code via CVS</A
+></DT
+><DD
+><DL
+><DT
+>27.1.1. <A
+HREF="compiling.html#AEN4185"
+>Introduction</A
+></DT
+><DT
+>27.1.2. <A
+HREF="compiling.html#AEN4190"
+>CVS Access to samba.org</A
+></DT
+><DD
+><DL
+><DT
+>27.1.2.1. <A
+HREF="compiling.html#AEN4193"
+>Access via CVSweb</A
+></DT
+><DT
+>27.1.2.2. <A
+HREF="compiling.html#AEN4198"
+>Access via cvs</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>27.2. <A
+HREF="compiling.html#AEN4226"
+>Accessing the samba sources via rsync and ftp</A
+></DT
+><DT
+>27.3. <A
+HREF="compiling.html#AEN4232"
+>Verifying Samba's PGP signature</A
+></DT
+><DT
+>27.4. <A
+HREF="compiling.html#AEN4244"
+>Building the Binaries</A
+></DT
+><DT
+>27.5. <A
+HREF="compiling.html#AEN4301"
+>Starting the smbd and nmbd</A
+></DT
+><DD
+><DL
+><DT
+>27.5.1. <A
+HREF="compiling.html#AEN4311"
+>Starting from inetd.conf</A
+></DT
+><DT
+>27.5.2. <A
+HREF="compiling.html#AEN4345"
+>Alternative: starting it as a daemon</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><P
 >You can obtain the samba source from the <A
 HREF="http://samba.org/"
 TARGET="_top"
 >samba website</A
 >. To obtain a development version, 
-you can download samba from CVS or using rsync. </P
+you can download samba from CVS or using rsync.</P
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4453"
->31.1. Access Samba source code via CVS</A
+NAME="AEN4183"
+>27.1. Access Samba source code via CVS</A
 ></H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4455"
->31.1.1. Introduction</A
+NAME="AEN4185"
+>27.1.1. Introduction</A
 ></H2
 ><P
 >Samba is developed in an open environment.  Developers use CVS
@@ -117,8 +193,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4460"
->31.1.2. CVS Access to samba.org</A
+NAME="AEN4190"
+>27.1.2. CVS Access to samba.org</A
 ></H2
 ><P
 >The machine samba.org runs a publicly accessible CVS 
@@ -130,8 +206,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN4463"
->31.1.2.1. Access via CVSweb</A
+NAME="AEN4193"
+>27.1.2.1. Access via CVSweb</A
 ></H3
 ><P
 >You can access the source code via your 
@@ -151,8 +227,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN4468"
->31.1.2.2. Access via cvs</A
+NAME="AEN4198"
+>27.1.2.2. Access via cvs</A
 ></H3
 ><P
 >You can also access the source code via a 
@@ -256,8 +332,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4496"
->31.2. Accessing the samba sources via rsync and ftp</A
+NAME="AEN4226"
+>27.2. Accessing the samba sources via rsync and ftp</A
 ></H1
 ><P
 >	pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A
@@ -284,8 +360,50 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4502"
->31.3. Building the Binaries</A
+NAME="AEN4232"
+>27.3. Verifying Samba's PGP signature</A
+></H1
+><P
+>In these days of insecurity, it's strongly recommended that you verify the PGP signature for any
+source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of
+all Samba downloads have had a corresponding PGP signature download (a very low percentage, which
+should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP
+signatures should be a standard reflex.</P
+><P
+>With that said, go ahead and download the following files:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</PRE
+></P
+><P
+>The first file is the PGP signature for the Samba source file; the other is the Samba public
+PGP key itself. Import the public PGP key with:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ gpg --import samba-pubkey.asc</PRE
+><P
+>And verify the Samba source code integrity with:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc</PRE
+><P
+>If you receive a message like, "Good signature from Samba Distribution Verification Key..."
+then all is well. The warnings about trust relationships can be ignored. An example of what
+you would not want to see would be:</P
+><PRE
+CLASS="PROGRAMLISTING"
+>     gpg: BAD signature from "Samba Distribution Verification Key"</PRE
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN4244"
+>27.4. Building the Binaries</A
 ></H1
 ><P
 >To do this, first run the program <KBD
@@ -370,8 +488,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4530"
->31.3.1. Compiling samba with Active Directory support</A
+NAME="AEN4272"
+>27.4.1. Compiling samba with Active Directory support</A
 ></H2
 ><P
 >In order to compile samba with ADS support, you need to have installed
@@ -393,9 +511,7 @@ BORDER="0"
 ></TABLE
 ><P
 ></P
->
-
-	</P
+></P
 ><P
 >If your kerberos libraries are in a non-standard location then
 	  remember to add the configure option --with-krb5=DIR.</P
@@ -420,8 +536,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN4542"
->31.3.1.1. Installing the required packages for Debian</A
+NAME="AEN4284"
+>27.4.1.1. Installing the required packages for Debian</A
 ></H3
 ><P
 >On Debian you need to install the following packages:</P
@@ -451,8 +567,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN4549"
->31.3.1.2. Installing the required packages for RedHat</A
+NAME="AEN4291"
+>27.4.1.2. Installing the required packages for RedHat</A
 ></H3
 ><P
 >On RedHat this means you should have at least: </P
@@ -493,8 +609,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4559"
->31.4. Starting the smbd and nmbd</A
+NAME="AEN4301"
+>27.5. Starting the smbd and nmbd</A
 ></H1
 ><P
 >You must choose to start smbd and nmbd either
@@ -533,8 +649,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4569"
->31.4.1. Starting from inetd.conf</A
+NAME="AEN4311"
+>27.5.1. Starting from inetd.conf</A
 ></H2
 ><P
 >NOTE; The following will be different if 
@@ -711,8 +827,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4603"
->31.4.2. Alternative: starting it as a daemon</A
+NAME="AEN4345"
+>27.5.2. Alternative: starting it as a daemon</A
 ></H2
 ><P
 >To start the server as a daemon you should create 
@@ -804,7 +920,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="other-clients.html"
+HREF="appendixes.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -822,7 +938,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="bugreport.html"
+HREF="nt4migration.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -832,7 +948,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Samba and other CIFS clients</TD
+>Appendixes</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -846,7 +962,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Reporting Bugs</TD
+>Migration from NT4 PDC to Samba-3 PDC</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html
index 43651c049d..ad7ddcf886 100644
--- a/docs/htmldocs/diagnosis.html
+++ b/docs/htmldocs/diagnosis.html
@@ -13,8 +13,11 @@ REL="UP"
 TITLE="Appendixes"
 HREF="appendixes.html"><LINK
 REL="PREVIOUS"
-TITLE="Reporting Bugs"
-HREF="bugreport.html"></HEAD
+TITLE="Samba performance issues"
+HREF="speed.html"><LINK
+REL="NEXT"
+TITLE="Analysing and solving samba problems"
+HREF="problems.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -42,7 +45,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="bugreport.html"
+HREF="speed.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -55,7 +58,11 @@ VALIGN="bottom"
 WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
->&nbsp;</TD
+><A
+HREF="problems.html"
+ACCESSKEY="N"
+>Next</A
+></TD
 ></TR
 ></TABLE
 ><HR
@@ -69,11 +76,40 @@ NAME="DIAGNOSIS"
 ></A
 >Chapter 33. The samba checklist</H1
 ><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>33.1. <A
+HREF="diagnosis.html#AEN4760"
+>Introduction</A
+></DT
+><DT
+>33.2. <A
+HREF="diagnosis.html#AEN4765"
+>Assumptions</A
+></DT
+><DT
+>33.3. <A
+HREF="diagnosis.html#AEN4784"
+>The tests</A
+></DT
+><DT
+>33.4. <A
+HREF="diagnosis.html#AEN4951"
+>Still having troubles?</A
+></DT
+></DL
+></DIV
+><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4716"
+NAME="AEN4760"
 >33.1. Introduction</A
 ></H1
 ><P
@@ -95,7 +131,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4721"
+NAME="AEN4765"
 >33.2. Assumptions</A
 ></H1
 ><P
@@ -181,7 +217,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4740"
+NAME="AEN4784"
 >33.3. The tests</A
 ></H1
 ><DIV
@@ -798,24 +834,15 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4907"
+NAME="AEN4951"
 >33.4. Still having troubles?</A
 ></H1
 ><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
+>Read the chapter on 
 <A
-HREF="mailto:samba@samba.org"
-TARGET="_top"
->samba@samba.org</A
->. To find 
-out more about samba and how to subscribe to the mailing list check 
-out the samba web page at 
-<A
-HREF="http://samba.org/samba"
-TARGET="_top"
->http://samba.org/samba/</A
-></P
+HREF="problems.html"
+>Analysing and Solving Problems</A
+>.</P
 ></DIV
 ></DIV
 ><DIV
@@ -834,7 +861,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="bugreport.html"
+HREF="speed.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -851,14 +878,18 @@ ACCESSKEY="H"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->&nbsp;</TD
+><A
+HREF="problems.html"
+ACCESSKEY="N"
+>Next</A
+></TD
 ></TR
 ><TR
 ><TD
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Reporting Bugs</TD
+>Samba performance issues</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -872,7 +903,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->&nbsp;</TD
+>Analysing and solving samba problems</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html
index bc0aec55c0..34b63f4fe1 100644
--- a/docs/htmldocs/findsmb.1.html
+++ b/docs/htmldocs/findsmb.1.html
@@ -212,18 +212,18 @@ CLASS="CONSTANT"
 	to the following</P
 ><PRE
 CLASS="SCREEN"
->IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
---------------------------------------------------------------------- 
-192.168.35.10   MINESET-TEST1  [DMVENGR]
-192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
-192.168.35.56   HERBNT2        [HERB-NT]
-192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
-192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
-192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
-192.168.35.78   HERBDHCP1     +[HERB]
-192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
-192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
-192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]</PRE
+>   &nbsp;IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
+   &nbsp;--------------------------------------------------------------------- 
+   &nbsp;192.168.35.10   MINESET-TEST1  [DMVENGR]
+   &nbsp;192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
+  5&nbsp;192.168.35.56   HERBNT2        [HERB-NT]
+   &nbsp;192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
+   &nbsp;192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
+   &nbsp;192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
+   &nbsp;192.168.35.78   HERBDHCP1     +[HERB]
+ 10&nbsp;192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
+   &nbsp;192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
+   &nbsp;192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]</PRE
 ></DIV
 ><DIV
 CLASS="REFSECT1"
diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html
index 95a1ce107f..f594ceca02 100644
--- a/docs/htmldocs/groupmapping.html
+++ b/docs/htmldocs/groupmapping.html
@@ -74,7 +74,7 @@ CLASS="CHAPTER"
 ><A
 NAME="GROUPMAPPING"
 ></A
->Chapter 11. Configuring Group Mapping</H1
+>Chapter 12. Configuring Group Mapping</H1
 ><P
 > 
 Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html
index 3817bbece8..6a7aaf6081 100644
--- a/docs/htmldocs/improved-browsing.html
+++ b/docs/htmldocs/improved-browsing.html
@@ -74,14 +74,78 @@ CLASS="CHAPTER"
 ><A
 NAME="IMPROVED-BROWSING"
 ></A
->Chapter 23. Improved browsing in samba</H1
+>Chapter 24. Improved browsing in samba</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>24.1. <A
+HREF="improved-browsing.html#AEN3875"
+>Overview of browsing</A
+></DT
+><DT
+>24.2. <A
+HREF="improved-browsing.html#AEN3881"
+>Browsing support in samba</A
+></DT
+><DT
+>24.3. <A
+HREF="improved-browsing.html#AEN3896"
+>Problem resolution</A
+></DT
+><DT
+>24.4. <A
+HREF="improved-browsing.html#AEN3908"
+>Browsing across subnets</A
+></DT
+><DT
+>24.5. <A
+HREF="improved-browsing.html#AEN3949"
+>Setting up a WINS server</A
+></DT
+><DT
+>24.6. <A
+HREF="improved-browsing.html#AEN3972"
+>Setting up Browsing in a WORKGROUP</A
+></DT
+><DT
+>24.7. <A
+HREF="improved-browsing.html#AEN3998"
+>Setting up Browsing in a DOMAIN</A
+></DT
+><DT
+>24.8. <A
+HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
+>Forcing samba to be the master</A
+></DT
+><DT
+>24.9. <A
+HREF="improved-browsing.html#AEN4033"
+>Making samba the domain master</A
+></DT
+><DT
+>24.10. <A
+HREF="improved-browsing.html#AEN4055"
+>Note about broadcast addresses</A
+></DT
+><DT
+>24.11. <A
+HREF="improved-browsing.html#AEN4058"
+>Multiple interfaces</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3804"
->23.1. Overview of browsing</A
+NAME="AEN3875"
+>24.1. Overview of browsing</A
 ></H1
 ><P
 >SMB networking provides a mechanism by which clients can access a list
@@ -112,8 +176,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3810"
->23.2. Browsing support in samba</A
+NAME="AEN3881"
+>24.2. Browsing support in samba</A
 ></H1
 ><P
 >Samba facilitates browsing.  The browsing is supported by <SPAN
@@ -198,8 +262,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3825"
->23.3. Problem resolution</A
+NAME="AEN3896"
+>24.3. Problem resolution</A
 ></H1
 ><P
 >If something doesn't work then hopefully the log.nmb file will help
@@ -250,8 +314,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3837"
->23.4. Browsing across subnets</A
+NAME="AEN3908"
+>24.4. Browsing across subnets</A
 ></H1
 ><P
 >Since the release of Samba 1.9.17(alpha1) Samba has been
@@ -284,8 +348,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3843"
->23.4.1. How does cross subnet browsing work ?</A
+NAME="AEN3914"
+>24.4.1. How does cross subnet browsing work ?</A
 ></H2
 ><P
 >Cross subnet browsing is a complicated dance, containing multiple
@@ -495,8 +559,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3878"
->23.5. Setting up a WINS server</A
+NAME="AEN3949"
+>24.5. Setting up a WINS server</A
 ></H1
 ><P
 >Either a Samba machine or a Windows NT Server machine may be set up
@@ -590,8 +654,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3901"
->23.6. Setting up Browsing in a WORKGROUP</A
+NAME="AEN3972"
+>24.6. Setting up Browsing in a WORKGROUP</A
 ></H1
 ><P
 >To set up cross subnet browsing on a network containing machines
@@ -700,8 +764,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3927"
->23.7. Setting up Browsing in a DOMAIN</A
+NAME="AEN3998"
+>24.7. Setting up Browsing in a DOMAIN</A
 ></H1
 ><P
 >If you are adding Samba servers to a Windows NT Domain then
@@ -775,7 +839,7 @@ CLASS="SECT1"
 CLASS="SECT1"
 ><A
 NAME="BROWSE-FORCE-MASTER"
->23.8. Forcing samba to be the master</A
+>24.8. Forcing samba to be the master</A
 ></H1
 ><P
 >Who becomes the <B
@@ -849,8 +913,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3962"
->23.9. Making samba the domain master</A
+NAME="AEN4033"
+>24.9. Making samba the domain master</A
 ></H1
 ><P
 >The domain master is responsible for collating the browse lists of
@@ -934,8 +998,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3984"
->23.10. Note about broadcast addresses</A
+NAME="AEN4055"
+>24.10. Note about broadcast addresses</A
 ></H1
 ><P
 >If your network uses a "0" based broadcast address (for example if it
@@ -948,8 +1012,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3987"
->23.11. Multiple interfaces</A
+NAME="AEN4058"
+>24.11. Multiple interfaces</A
 ></H1
 ><P
 >Samba now supports machines with multiple network interfaces.  If you
diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html
index cc2674ea1c..54d10859f5 100644
--- a/docs/htmldocs/install.html
+++ b/docs/htmldocs/install.html
@@ -13,8 +13,8 @@ REL="UP"
 TITLE="General installation"
 HREF="introduction.html"><LINK
 REL="PREVIOUS"
-TITLE="General installation"
-HREF="introduction.html"><LINK
+TITLE="Introduction to Samba"
+HREF="introsmb.html"><LINK
 REL="NEXT"
 TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
 HREF="browsing-quick.html"></HEAD
@@ -45,7 +45,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="introduction.html"
+HREF="introsmb.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -74,14 +74,86 @@ CLASS="CHAPTER"
 ><A
 NAME="INSTALL"
 ></A
->Chapter 1. How to Install and Test SAMBA</H1
+>Chapter 2. How to Install and Test SAMBA</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>2.1. <A
+HREF="install.html#AEN188"
+>Obtaining and installing samba</A
+></DT
+><DT
+>2.2. <A
+HREF="install.html#AEN194"
+>Configuring samba</A
+></DT
+><DD
+><DL
+><DT
+>2.2.1. <A
+HREF="install.html#AEN199"
+>Editing the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file</A
+></DT
+><DT
+>2.2.2. <A
+HREF="install.html#AEN224"
+>SWAT</A
+></DT
+></DL
+></DD
+><DT
+>2.3. <A
+HREF="install.html#AEN230"
+>Try listing the shares available on your 
+	server</A
+></DT
+><DT
+>2.4. <A
+HREF="install.html#AEN239"
+>Try connecting with the unix client</A
+></DT
+><DT
+>2.5. <A
+HREF="install.html#AEN260"
+>Try connecting from a DOS, WfWg, Win9x, WinNT, 
+	Win2k, OS/2, etc... client</A
+></DT
+><DT
+>2.6. <A
+HREF="install.html#AEN273"
+>What If Things Don't Work?</A
+></DT
+><DD
+><DL
+><DT
+>2.6.1. <A
+HREF="install.html#AEN278"
+>Scope IDs</A
+></DT
+><DT
+>2.6.2. <A
+HREF="install.html#AEN281"
+>Locking</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN65"
->1.1. Obtaining and installing samba</A
+NAME="AEN188"
+>2.1. Obtaining and installing samba</A
 ></H1
 ><P
 >Binary packages of samba are included in almost any Linux or 
@@ -104,8 +176,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN71"
->1.2. Configuring samba</A
+NAME="AEN194"
+>2.2. Configuring samba</A
 ></H1
 ><P
 >Samba's configuration is stored in the smb.conf file, 
@@ -125,8 +197,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN76"
->1.2.1. Editing the <TT
+NAME="AEN199"
+>2.2.1. Editing the <TT
 CLASS="FILENAME"
 >smb.conf</TT
 > file</A
@@ -186,8 +258,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN92"
->1.2.1.1. Test your config file with 
+NAME="AEN215"
+>2.2.1.1. Test your config file with 
 	<B
 CLASS="COMMAND"
 >testparm</B
@@ -220,8 +292,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN101"
->1.2.2. SWAT</A
+NAME="AEN224"
+>2.2.2. SWAT</A
 ></H2
 ><P
 >	SWAT is a web-based interface that helps you configure samba. 
@@ -248,8 +320,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN107"
->1.3. Try listing the shares available on your 
+NAME="AEN230"
+>2.3. Try listing the shares available on your 
 	server</A
 ></H1
 ><P
@@ -285,8 +357,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN116"
->1.4. Try connecting with the unix client</A
+NAME="AEN239"
+>2.4. Try connecting with the unix client</A
 ></H1
 ><P
 ><SAMP
@@ -355,8 +427,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN137"
->1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
+NAME="AEN260"
+>2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</A
 ></H1
 ><P
@@ -396,8 +468,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN150"
->1.6. What If Things Don't Work?</A
+NAME="AEN273"
+>2.6. What If Things Don't Work?</A
 ></H1
 ><P
 >Then you might read the file chapter 
@@ -405,29 +477,20 @@ NAME="AEN150"
 HREF="diagnosis.html"
 >Diagnosis</A
 > and the 
-	FAQ. If you are still stuck then try the mailing list or 
-	newsgroup (look in the README for details). Samba has been 
-	successfully installed at thousands of sites worldwide, so maybe 
-	someone else has hit your problem and has overcome it. You could 
-	also use the WWW site to scan back issues of the samba-digest.</P
-><P
->When you fix the problem <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->please</I
-></SPAN
-> send some 
-	updates of the documentation (or source code) to one of 
-	the documentation maintainers or the list.
-	</P
+	FAQ. If you are still stuck then try to follow 
+	the <A
+HREF="problems.html"
+>Analysing and Solving Problems chapter</A
+>
+	Samba has been successfully installed at thousands of sites worldwide,
+	so maybe someone else has hit your problem and has overcome it. </P
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN156"
->1.6.1. Scope IDs</A
+NAME="AEN278"
+>2.6.1. Scope IDs</A
 ></H2
 ><P
 >By default Samba uses a blank scope ID. This means 
@@ -442,8 +505,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN159"
->1.6.2. Locking</A
+NAME="AEN281"
+>2.6.2. Locking</A
 ></H2
 ><P
 >One area which sometimes causes trouble is locking.</P
@@ -515,7 +578,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="introduction.html"
+HREF="introsmb.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -543,7 +606,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->General installation</TD
+>Introduction to Samba</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html
index 5d9e1cdaec..56f4963fa6 100644
--- a/docs/htmldocs/integrate-ms-networks.html
+++ b/docs/htmldocs/integrate-ms-networks.html
@@ -74,7 +74,91 @@ CLASS="CHAPTER"
 ><A
 NAME="INTEGRATE-MS-NETWORKS"
 ></A
->Chapter 22. Integrating MS Windows networks with Samba</H1
+>Chapter 23. Integrating MS Windows networks with Samba</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>23.1. <A
+HREF="integrate-ms-networks.html#AEN3759"
+>Name Resolution in a pure Unix/Linux world</A
+></DT
+><DD
+><DL
+><DT
+>23.1.1. <A
+HREF="integrate-ms-networks.html#AEN3775"
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></A
+></DT
+><DT
+>23.1.2. <A
+HREF="integrate-ms-networks.html#AEN3791"
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></A
+></DT
+><DT
+>23.1.3. <A
+HREF="integrate-ms-networks.html#AEN3802"
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></A
+></DT
+><DT
+>23.1.4. <A
+HREF="integrate-ms-networks.html#AEN3810"
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></A
+></DT
+></DL
+></DD
+><DT
+>23.2. <A
+HREF="integrate-ms-networks.html#AEN3822"
+>Name resolution as used within MS Windows networking</A
+></DT
+><DD
+><DL
+><DT
+>23.2.1. <A
+HREF="integrate-ms-networks.html#AEN3834"
+>The NetBIOS Name Cache</A
+></DT
+><DT
+>23.2.2. <A
+HREF="integrate-ms-networks.html#AEN3839"
+>The LMHOSTS file</A
+></DT
+><DT
+>23.2.3. <A
+HREF="integrate-ms-networks.html#AEN3847"
+>HOSTS file</A
+></DT
+><DT
+>23.2.4. <A
+HREF="integrate-ms-networks.html#AEN3852"
+>DNS Lookup</A
+></DT
+><DT
+>23.2.5. <A
+HREF="integrate-ms-networks.html#AEN3855"
+>WINS Lookup</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><P
 >This section deals with NetBIOS over TCP/IP name to IP address resolution. If you
 your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
@@ -155,8 +239,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3688"
->22.1. Name Resolution in a pure Unix/Linux world</A
+NAME="AEN3759"
+>23.1. Name Resolution in a pure Unix/Linux world</A
 ></H1
 ><P
 >The key configuration files covered in this section are:</P
@@ -197,8 +281,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3704"
->22.1.1. <TT
+NAME="AEN3775"
+>23.1.1. <TT
 CLASS="FILENAME"
 >/etc/hosts</TT
 ></A
@@ -278,8 +362,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3720"
->22.1.2. <TT
+NAME="AEN3791"
+>23.1.2. <TT
 CLASS="FILENAME"
 >/etc/resolv.conf</TT
 ></A
@@ -316,8 +400,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3731"
->22.1.3. <TT
+NAME="AEN3802"
+>23.1.3. <TT
 CLASS="FILENAME"
 >/etc/host.conf</TT
 ></A
@@ -345,8 +429,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3739"
->22.1.4. <TT
+NAME="AEN3810"
+>23.1.4. <TT
 CLASS="FILENAME"
 >/etc/nsswitch.conf</TT
 ></A
@@ -414,8 +498,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3751"
->22.2. Name resolution as used within MS Windows networking</A
+NAME="AEN3822"
+>23.2. Name resolution as used within MS Windows networking</A
 ></H1
 ><P
 >MS Windows networking is predicated about the name each machine 
@@ -499,8 +583,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3763"
->22.2.1. The NetBIOS Name Cache</A
+NAME="AEN3834"
+>23.2.1. The NetBIOS Name Cache</A
 ></H2
 ><P
 >All MS Windows machines employ an in memory buffer in which is 
@@ -526,8 +610,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3768"
->22.2.2. The LMHOSTS file</A
+NAME="AEN3839"
+>23.2.2. The LMHOSTS file</A
 ></H2
 ><P
 >This file is usually located in MS Windows NT 4.0 or 
@@ -629,8 +713,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3776"
->22.2.3. HOSTS file</A
+NAME="AEN3847"
+>23.2.3. HOSTS file</A
 ></H2
 ><P
 >This file is usually located in MS Windows NT 4.0 or 2000 in 
@@ -651,8 +735,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3781"
->22.2.4. DNS Lookup</A
+NAME="AEN3852"
+>23.2.4. DNS Lookup</A
 ></H2
 ><P
 >This capability is configured in the TCP/IP setup area in the network 
@@ -671,8 +755,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3784"
->22.2.5. WINS Lookup</A
+NAME="AEN3855"
+>23.2.5. WINS Lookup</A
 ></H2
 ><P
 >A WINS (Windows Internet Name Server) service is the equivaent of the 
diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html
index e16808e8f3..f45e60b5c5 100644
--- a/docs/htmldocs/introduction.html
+++ b/docs/htmldocs/introduction.html
@@ -13,8 +13,8 @@ REL="PREVIOUS"
 TITLE="SAMBA Project Documentation"
 HREF="samba-howto-collection.html"><LINK
 REL="NEXT"
-TITLE="How to Install and Test SAMBA"
-HREF="install.html"></HEAD
+TITLE="Introduction to Samba"
+HREF="introsmb.html"></HEAD
 ><BODY
 CLASS="PART"
 BGCOLOR="#FFFFFF"
@@ -56,7 +56,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="install.html"
+HREF="introsmb.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -75,10 +75,11 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >I. General installation</H1
+></DIV
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN42"
+NAME="AEN44"
 ></A
 ><H1
 >Introduction</H1
@@ -87,275 +88,6 @@ NAME="AEN42"
 and how to configure the parts of samba you will most likely need.
 PLEASE read this.</P
 ></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1. <A
-HREF="install.html"
->How to Install and Test SAMBA</A
-></DT
-><DD
-><DL
-><DT
->1.1. <A
-HREF="install.html#AEN65"
->Obtaining and installing samba</A
-></DT
-><DT
->1.2. <A
-HREF="install.html#AEN71"
->Configuring samba</A
-></DT
-><DD
-><DL
-><DT
->1.2.1. <A
-HREF="install.html#AEN76"
->Editing the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file</A
-></DT
-><DT
->1.2.2. <A
-HREF="install.html#AEN101"
->SWAT</A
-></DT
-></DL
-></DD
-><DT
->1.3. <A
-HREF="install.html#AEN107"
->Try listing the shares available on your 
-	server</A
-></DT
-><DT
->1.4. <A
-HREF="install.html#AEN116"
->Try connecting with the unix client</A
-></DT
-><DT
->1.5. <A
-HREF="install.html#AEN137"
->Try connecting from a DOS, WfWg, Win9x, WinNT, 
-	Win2k, OS/2, etc... client</A
-></DT
-><DT
->1.6. <A
-HREF="install.html#AEN150"
->What If Things Don't Work?</A
-></DT
-><DD
-><DL
-><DT
->1.6.1. <A
-HREF="install.html#AEN156"
->Scope IDs</A
-></DT
-><DT
->1.6.2. <A
-HREF="install.html#AEN159"
->Locking</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->2. <A
-HREF="browsing-quick.html"
->Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
-></DT
-><DD
-><DL
-><DT
->2.1. <A
-HREF="browsing-quick.html#AEN183"
->Discussion</A
-></DT
-><DT
->2.2. <A
-HREF="browsing-quick.html#AEN204"
->How browsing functions and how to deploy stable and 
-dependable browsing using Samba</A
-></DT
-><DT
->2.3. <A
-HREF="browsing-quick.html#AEN218"
->Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
-></DT
-><DT
->2.4. <A
-HREF="browsing-quick.html#AEN241"
->Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
-></DT
-><DT
->2.5. <A
-HREF="browsing-quick.html#AEN252"
->Use of WINS</A
-></DT
-><DT
->2.6. <A
-HREF="browsing-quick.html#AEN269"
->Do NOT use more than one (1) protocol on MS Windows machines</A
-></DT
-><DT
->2.7. <A
-HREF="browsing-quick.html#AEN277"
->Name Resolution Order</A
-></DT
-></DL
-></DD
-><DT
->3. <A
-HREF="passdb.html"
->User information database</A
-></DT
-><DD
-><DL
-><DT
->3.1. <A
-HREF="passdb.html#AEN335"
->Introduction</A
-></DT
-><DT
->3.2. <A
-HREF="passdb.html#AEN342"
->Important Notes About Security</A
-></DT
-><DD
-><DL
-><DT
->3.2.1. <A
-HREF="passdb.html#AEN368"
->Advantages of SMB Encryption</A
-></DT
-><DT
->3.2.2. <A
-HREF="passdb.html#AEN374"
->Advantages of non-encrypted passwords</A
-></DT
-></DL
-></DD
-><DT
->3.3. <A
-HREF="passdb.html#AEN380"
->The smbpasswd Command</A
-></DT
-><DT
->3.4. <A
-HREF="passdb.html#AEN411"
->Plain text</A
-></DT
-><DT
->3.5. <A
-HREF="passdb.html#AEN416"
->TDB</A
-></DT
-><DT
->3.6. <A
-HREF="passdb.html#AEN419"
->LDAP</A
-></DT
-><DD
-><DL
-><DT
->3.6.1. <A
-HREF="passdb.html#AEN421"
->Introduction</A
-></DT
-><DT
->3.6.2. <A
-HREF="passdb.html#AEN441"
->Introduction</A
-></DT
-><DT
->3.6.3. <A
-HREF="passdb.html#AEN470"
->Supported LDAP Servers</A
-></DT
-><DT
->3.6.4. <A
-HREF="passdb.html#AEN475"
->Schema and Relationship to the RFC 2307 posixAccount</A
-></DT
-><DT
->3.6.5. <A
-HREF="passdb.html#AEN487"
->Configuring Samba with LDAP</A
-></DT
-><DT
->3.6.6. <A
-HREF="passdb.html#AEN534"
->Accounts and Groups management</A
-></DT
-><DT
->3.6.7. <A
-HREF="passdb.html#AEN539"
->Security and sambaAccount</A
-></DT
-><DT
->3.6.8. <A
-HREF="passdb.html#AEN559"
->LDAP specials attributes for sambaAccounts</A
-></DT
-><DT
->3.6.9. <A
-HREF="passdb.html#AEN629"
->Example LDIF Entries for a sambaAccount</A
-></DT
-></DL
-></DD
-><DT
->3.7. <A
-HREF="passdb.html#AEN637"
->MySQL</A
-></DT
-><DD
-><DL
-><DT
->3.7.1. <A
-HREF="passdb.html#AEN639"
->Creating the database</A
-></DT
-><DT
->3.7.2. <A
-HREF="passdb.html#AEN649"
->Configuring</A
-></DT
-><DT
->3.7.3. <A
-HREF="passdb.html#AEN666"
->Using plaintext passwords or encrypted password</A
-></DT
-><DT
->3.7.4. <A
-HREF="passdb.html#AEN671"
->Getting non-column data from the table</A
-></DT
-></DL
-></DD
-><DT
->3.8. <A
-HREF="passdb.html#AEN679"
->XML</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
@@ -391,7 +123,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="install.html"
+HREF="introsmb.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -411,7 +143,7 @@ VALIGN="top"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->How to Install and Test SAMBA</TD
+>Introduction to Samba</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html
index f05c8012ac..5677e34873 100644
--- a/docs/htmldocs/msdfs.html
+++ b/docs/htmldocs/msdfs.html
@@ -74,14 +74,14 @@ CLASS="CHAPTER"
 ><A
 NAME="MSDFS"
 ></A
->Chapter 21. Hosting a Microsoft Distributed File System tree on Samba</H1
+>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</H1
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3626"
->21.1. Instructions</A
+NAME="AEN3696"
+>22.1. Instructions</A
 ></H1
 ><P
 >The Distributed File System (or Dfs) provides a means of 
@@ -212,8 +212,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3661"
->21.1.1. Notes</A
+NAME="AEN3731"
+>22.1.1. Notes</A
 ></H2
 ><P
 ></P
diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html
index 63becc2071..26711d936f 100644
--- a/docs/htmldocs/net.8.html
+++ b/docs/htmldocs/net.8.html
@@ -26,7 +26,8 @@ NAME="AEN5"
 ><H2
 >Name</H2
 >net&nbsp;--&nbsp;Tool for administration of Samba and remote
-	CIFS servers.</DIV
+	CIFS servers.
+	</DIV
 ><DIV
 CLASS="REFSYNOPSISDIV"
 ><A
@@ -38,12 +39,12 @@ NAME="AEN8"
 ><B
 CLASS="COMMAND"
 >net</B
->  {&#60;ads|rap|rpc&#62;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-C comment] [-M maxusers] [-F flags] [-j jobid] [-l] [-r] [-f] [-t timeout] [-P] [-D debuglevel]</P
+>  {&#60;ads|rap|rpc&#62;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]</P
 ></DIV
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN31"
+NAME="AEN24"
 ></A
 ><H2
 >DESCRIPTION</H2
@@ -57,12 +58,18 @@ CLASS="REFENTRYTITLE"
 > suite.</P
 ><P
 >The samba net utility is meant to work just like the net utility 
-	available for windows and DOS.</P
+	available for windows and DOS. The first argument should be used 
+	to specify the protocol to use when executing a certain command. 
+	ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) 
+	clients and RPC can be used for NT4 and Windows 2000. If this 
+	argument is omitted, net will try to determine it automatically. 
+	Not all commands are available on all protocols.
+	</P
 ></DIV
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN38"
+NAME="AEN31"
 ></A
 ><H2
 >OPTIONS</H2
@@ -72,12 +79,10 @@ NAME="AEN38"
 CLASS="VARIABLELIST"
 ><DL
 ><DT
->-h</DT
+>-h|--help</DT
 ><DD
 ><P
->		Display summary of all available options.
-		
-		</P
+>Print a summary of command line options.</P
 ></DD
 ><DT
 >-w target-workgroup</DT
@@ -106,29 +111,67 @@ CLASS="VARIABLELIST"
 ><DD
 ><P
 >		IP address of target server to use. You have to
-		specify either this option or a target workgroup or a target server.
+		specify either this option or a target workgroup or
+		a target server.
 		</P
 ></DD
 ><DT
 >-p port</DT
 ><DD
 ><P
->		Port on the target server to connect to.
+>		Port on the target server to connect to (usually 139 or 445). 
+		Defaults to trying 445 first, then 139.
 		</P
 ></DD
 ><DT
->-n myname</DT
+>-n &#60;primary NetBIOS name&#62;</DT
 ><DD
 ><P
->		Sets name of the client.
-		</P
+>This option allows you to override
+the NetBIOS name that Samba uses for itself. This is identical
+to setting the <A
+HREF="smb.conf.5.html#netbiosname"
+TARGET="_top"
+><VAR
+CLASS="PARAMETER"
+>NetBIOS
+name</VAR
+></A
+> parameter in the <SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smb.conf</SPAN
+>(5)</SPAN
+> file.  However, a command
+line setting will take precedence over settings in
+<SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smb.conf</SPAN
+>(5)</SPAN
+>.</P
 ></DD
 ><DT
->-s conffile</DT
+>-s &#60;configuration file&#62;</DT
 ><DD
 ><P
->		Specify alternative configuration file that should be loaded.
-		</P
+>The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> for more information.
+The default configuration file name is determined at 
+compile time.</P
 ></DD
 ><DT
 >-S server</DT
@@ -139,80 +182,57 @@ CLASS="VARIABLELIST"
 		</P
 ></DD
 ><DT
->-C comment</DT
-><DD
-><P
->		FIXME
-		</P
-></DD
-><DT
->-M maxusers</DT
-><DD
-><P
->		FIXME
-		</P
-></DD
-><DT
->-F flags</DT
-><DD
-><P
->		FIXME
-		</P
-></DD
-><DT
->-j jobid</DT
-><DD
-><P
->		FIXME
-		</P
-></DD
-><DT
 >-l</DT
 ><DD
 ><P
->		FIXME
+>		When listing data, give more information on each item.
 		</P
 ></DD
 ><DT
->-r</DT
+>-P</DT
 ><DD
 ><P
->		FIXME
+>		Make queries to the external server using the machine account of the local server.
 		</P
 ></DD
 ><DT
->-f</DT
+>-d|--debug=debuglevel</DT
 ><DD
 ><P
->		FIXME
-		</P
-></DD
-><DT
->-t timeout</DT
-><DD
+><VAR
+CLASS="REPLACEABLE"
+>debuglevel</VAR
+> is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.</P
 ><P
->		FIXME
-		</P
-></DD
-><DT
->-P</DT
-><DD
+>The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.</P
 ><P
->		Make queries to the external server using the machine account of the local server.
-		</P
-></DD
-><DT
->-D debuglevel</DT
-><DD
+>Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.</P
 ><P
->set the debuglevel. Debug level 0 is the lowest
-		and 100 being the highest. This should be set to 100 if you are
-		planning on submitting a bug report to the Samba team (see
-		<TT
+>Note that specifying this parameter here will 
+override the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log
+level</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
 CLASS="FILENAME"
->BUGS.txt</TT
->).
-		</P
+>smb.conf(5)</TT
+></A
+> file.</P
 ></DD
 ></DL
 ></DIV
@@ -220,183 +240,1337 @@ CLASS="FILENAME"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN118"
+NAME="AEN99"
 ></A
 ><H2
->TIME</H2
+>COMMANDS</H2
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN101"
+></A
+><H3
+>TIME</H3
 ><P
 >The <B
 CLASS="COMMAND"
 >NET TIME</B
 > command allows you to view the time on a remote server
 	or synchronise the time on the local server with the time on the remote server.</P
-><P
-></P
 ><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
-></DT
-><DD
+CLASS="REFSECT3"
+><A
+NAME="AEN105"
+></A
+><H4
+>TIME</H4
 ><P
->		Without any options, the <B
+>Without any options, the <B
 CLASS="COMMAND"
 >NET TIME</B
 > command 
-		displays the time on the remote server.
-		</P
-></DD
-><DT
->SYSTEM</DT
-><DD
+displays the time on the remote server.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN109"
+></A
+><H4
+>TIME SYSTEM</H4
 ><P
->		Displays the time on the remote server in a format ready for <B
+> Displays the time on the remote server in a format ready for <B
 CLASS="COMMAND"
 >/bin/date</B
->
-		</P
-></DD
-><DT
->SET</DT
-><DD
+></P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN113"
+></A
+><H4
+>TIME SET</H4
 ><P
->		Tries to set the date and time of the local server to that on 
-		the remote server using <B
+>Tries to set the date and time of the local server to that on 
+the remote server using <B
 CLASS="COMMAND"
 >/bin/date</B
->.
-		</P
-></DD
-><DT
->ZONE</DT
-><DD
+>. </P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN117"
+></A
+><H4
+>TIME ZONE</H4
 ><P
->		Displays the timezone in hours from GMT on the remote computer.
-		</P
-></DD
-></DL
+>Displays the timezone in hours from GMT on the remote computer.</P
 ></DIV
 ></DIV
 ><DIV
-CLASS="REFSECT1"
+CLASS="REFSECT2"
 ><A
-NAME="AEN142"
+NAME="AEN120"
 ></A
-><H2
->RPC</H2
+><H3
+>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]</H3
 ><P
->The <B
-CLASS="COMMAND"
->NET RPC</B
-> command allows you to do various 
-	NT4 operations.</P
+>Join a domain.  If the account already exists on the server, and 
+[TYPE] is MEMBER, the machine will attempt to join automatically. 
+(Assuming that the machine has been created in server manager)
+Otherwise, a password will be prompted for, and a new account may
+be created.</P
 ><P
-></P
+>[TYPE] may be PDC, BDC or MEMBER to specify the type of server
+joining the domain.</P
+></DIV
 ><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
->JOIN -U username[%password] [options]</DT
-><DD
+CLASS="REFSECT2"
+><A
+NAME="AEN124"
+></A
+><H3
+>[RPC] OLDJOIN [options]</H3
 ><P
->		Join a domain with specified username and password. Password 
-		will be prompted if none is specified.</P
-></DD
-><DT
->JOIN [options except -U]</DT
-><DD
+>Join a domain. Use the OLDJOIN option to join the domain 
+using the old style of domain joining - you need to create a trust 
+account in server manager first.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN127"
+></A
+><H3
+>[RPC|ADS] USER</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN129"
+></A
+><H4
+>[RPC|ADS] USER DELETE <VAR
+CLASS="REPLACEABLE"
+>target</VAR
+></H4
 ><P
->		to join a domain created in server manager
-		</P
-></DD
-><DT
->USER [misc. options] [targets]</DT
-><DD
+>Delete specified user</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN133"
+></A
+><H4
+>[RPC|ADS] USER LIST</H4
 ><P
->		List users
-		</P
-></DD
-><DT
->USER DELETE &#60;name&#62; [misc options]</DT
-><DD
+>List all users</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN136"
+></A
+><H4
+>[RPC|ADS] USER INFO <VAR
+CLASS="REPLACEABLE"
+>target</VAR
+></H4
 ><P
->		delete specified user
-		</P
-></DD
-><DT
->USER INFO &#60;name&#62; [misc options]</DT
-><DD
+>List the domain groups of a the specified user.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN140"
+></A
+><H4
+>[RPC|ADS] USER ADD <VAR
+CLASS="REPLACEABLE"
+>name</VAR
+> [password] [-F user flags] [-C comment]</H4
 ><P
->		list the domain groups of the specified user
-		</P
-></DD
-><DT
->USER ADD &#60;name&#62; [password] [-F user flags] [misc. options]</DT
-><DD
+>Add specified user.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN144"
+></A
+><H3
+>[RPC|ADS] GROUP</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN146"
+></A
+><H4
+>[RPC|ADS] GROUP [misc options] [targets]</H4
 ><P
->		Add specified user
-		</P
-></DD
-><DT
->GROUP [misc options] [targets]</DT
-><DD
+>List user groups.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN149"
+></A
+><H4
+>[RPC|ADS] GROUP DELETE <VAR
+CLASS="REPLACEABLE"
+>name</VAR
+> [misc. options]</H4
 ><P
->		List user groups
-		</P
-></DD
-><DT
->GROUP DELETE &#60;name&#62; [misc. options] [targets]</DT
-><DD
+>Delete specified group.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN153"
+></A
+><H4
+>[RPC|ADS] GROUP ADD <VAR
+CLASS="REPLACEABLE"
+>name</VAR
+> [-C comment]</H4
 ><P
->		Delete specified group
-		</P
-></DD
-><DT
->GROUP ADD &#60;name&#62; [-C comment]</DT
-><DD
+>Create specified group.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN157"
+></A
+><H3
+>[RAP|RPC] SHARE</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN159"
+></A
+><H4
+>[RAP|RPC] SHARE [misc. options] [targets]</H4
 ><P
->		Create specified group
-		</P
-></DD
-><DT
->SHARE [misc. options] [targets]</DT
-><DD
+>Enumerates all exported resources (network shares) on target server.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN162"
+></A
+><H4
+>[RAP|RPC] SHARE ADD <VAR
+CLASS="REPLACEABLE"
+>name=serverpath</VAR
+> [-C comment] [-M maxusers] [targets]</H4
 ><P
->		enumerates all exported resources (network shares) on target server
-		</P
-></DD
-><DT
->SHARE ADD &#60;name=serverpath&#62; [misc. options] [targets]</DT
-><DD
+>Adds a share from a server (makes the export active). Maxusers 
+specifies the number of users that can be connected to the 
+share simultaneously.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN166"
+></A
+><H4
+>SHARE DELETE <VAR
+CLASS="REPLACEABLE"
+>sharenam</VAR
+></H4
 ><P
->		Adds a share from a server (makes the export active)
-		</P
-></DD
-><DT
->SHARE DELETE &#60;sharenam</DT
-><DD
+>Delete specified share.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN170"
+></A
+><H3
+>[RPC|RAP] FILE</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN172"
+></A
+><H4
+>[RPC|RAP] FILE</H4
+><P
+>List all open files on remote server.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN175"
+></A
+><H4
+>[RPC|RAP] FILE CLOSE <VAR
+CLASS="REPLACEABLE"
+>fileid</VAR
+></H4
+><P
+>Close file with specified <VAR
+CLASS="REPLACEABLE"
+>fileid</VAR
+> on 
+remote server.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN180"
+></A
+><H4
+>[RPC|RAP] FILE INFO <VAR
+CLASS="REPLACEABLE"
+>fileid</VAR
+></H4
+><P
+>Print information on specified <VAR
+CLASS="REPLACEABLE"
+>fileid</VAR
+>. 
+Currently listed are: file-id, username, locks, path, permissions.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN185"
+></A
+><H4
+>[RAP|RPC] FILE USER</H4
+><DIV
+CLASS="NOTE"
 ><P
 ></P
-></DD
-></DL
+><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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
 ></DIV
 ></DIV
 ><DIV
-CLASS="REFSECT1"
+CLASS="REFSECT2"
 ><A
-NAME="AEN195"
+NAME="AEN189"
 ></A
-><H2
->VERSION</H2
+><H3
+>SESSION</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN191"
+></A
+><H4
+>RAP SESSION</H4
 ><P
->This man page is incomplete for version 3.0 of the Samba 
-	suite.</P
+>Without any other options, SESSION enumerates all active SMB/CIFS 
+sessions on the target server.</P
 ></DIV
 ><DIV
-CLASS="REFSECT1"
+CLASS="REFSECT3"
+><A
+NAME="AEN194"
+></A
+><H4
+>RAP SESSION DELETE|CLOSE <VAR
+CLASS="REPLACEABLE"
+>CLIENT_NAME</VAR
+></H4
+><P
+>Close the specified sessions.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
 ><A
 NAME="AEN198"
 ></A
+><H4
+>RAP SESSION INFO <VAR
+CLASS="REPLACEABLE"
+>CLIENT_NAME</VAR
+></H4
+><P
+>Give a list with all the open files in specified session.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN202"
+></A
+><H3
+>RAP SERVER <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H3
+><P
+>List all servers in specified domain or workgroup. Defaults
+to local domain.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN206"
+></A
+><H3
+>RAP DOMAIN</H3
+><P
+>Lists all domains and workgroups visible on the 
+current network.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN209"
+></A
+><H3
+>RAP PRINTQ</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN211"
+></A
+><H4
+>RAP PRINTQ LIST <VAR
+CLASS="REPLACEABLE"
+>QUEUE_NAME</VAR
+></H4
+><P
+>Lists the specified print queue and print jobs on the server.
+If the <VAR
+CLASS="REPLACEABLE"
+>QUEUE_NAME</VAR
+> is omitted, all 
+queues are listed.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN216"
+></A
+><H4
+>RAP PRINTQ DELETE <VAR
+CLASS="REPLACEABLE"
+>JOBID</VAR
+></H4
+><P
+>Delete job with specified id.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN220"
+></A
+><H3
+>RAP VALIDATE <VAR
+CLASS="REPLACEABLE"
+>user</VAR
+> [<VAR
+CLASS="REPLACEABLE"
+>password</VAR
+>]</H3
+><P
+>Validate whether the specified user can log in to the 
+remote server. If the password is not specified on the commandline, it 
+will be prompted. </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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN227"
+></A
+><H3
+>RAP GROUPMEMBER</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN229"
+></A
+><H4
+>RAP GROUPMEMBER LIST <VAR
+CLASS="REPLACEABLE"
+>GROUP</VAR
+></H4
+><P
+>List all members of the specified group.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN233"
+></A
+><H4
+>RAP GROUPMEMBER DELETE <VAR
+CLASS="REPLACEABLE"
+>GROUP</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>USER</VAR
+></H4
+><P
+>Delete member from group.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN238"
+></A
+><H4
+>RAP GROUPMEMBER ADD <VAR
+CLASS="REPLACEABLE"
+>GROUP</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>USER</VAR
+></H4
+><P
+>Add member to group.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN243"
+></A
+><H3
+>RAP ADMIN <VAR
+CLASS="REPLACEABLE"
+>command</VAR
+></H3
+><P
+>Execute the specified <VAR
+CLASS="REPLACEABLE"
+>command</VAR
+> on 
+the remote server. Only works with OS/2 servers.</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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN250"
+></A
+><H3
+>RAP SERVICE</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN252"
+></A
+><H4
+>RAP SERVICE START <VAR
+CLASS="REPLACEABLE"
+>NAME</VAR
+> [arguments...]</H4
+><P
+>Start the specified service on the remote server. Not implemented yet.</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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN258"
+></A
+><H4
+>RAP SERVICE STOP</H4
+><P
+>Stop the specified service on the remote server.</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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN263"
+></A
+><H3
+>RAP PASSWORD <VAR
+CLASS="REPLACEABLE"
+>USER</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>OLDPASS</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>NEWPASS</VAR
+></H3
+><P
+>Change password of <VAR
+CLASS="REPLACEABLE"
+>USER</VAR
+> from <VAR
+CLASS="REPLACEABLE"
+>OLDPASS</VAR
+> to <VAR
+CLASS="REPLACEABLE"
+>NEWPASS</VAR
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN272"
+></A
+><H3
+>LOOKUP</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN274"
+></A
+><H4
+>LOOKUP HOST <VAR
+CLASS="REPLACEABLE"
+>HOSTNAME</VAR
+> [<VAR
+CLASS="REPLACEABLE"
+>TYPE</VAR
+>]</H4
+><P
+>Lookup the IP address of the given host with the specified type (netbios suffix). 
+The type defaults to 0x20 (workstation).</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN279"
+></A
+><H4
+>LOOKUP LDAP [<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H4
+><P
+>Give IP address of LDAP server of specified <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>. Defaults to local domain.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN284"
+></A
+><H4
+>LOOKUP KDC [<VAR
+CLASS="REPLACEABLE"
+>REALM</VAR
+>]</H4
+><P
+>Give IP address of KDC for the specified <VAR
+CLASS="REPLACEABLE"
+>REALM</VAR
+>.
+Defaults to local realm.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN289"
+></A
+><H4
+>LOOKUP DC [<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>]</H4
+><P
+>Give IP's of Domain Controllers for specified <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>. Defaults to local domain.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN294"
+></A
+><H4
+>LOOKUP MASTER <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H4
+><P
+>Give IP of master browser for specified <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+>
+or workgroup. Defaults to local domain.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN299"
+></A
+><H3
+>CACHE</H3
+><P
+>Samba uses a general caching interface called 'gencache'. It 
+can be controlled using 'NET CACHE'.</P
+><P
+>All the timeout parameters support the suffixes:
+
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>s - Seconds</TD
+></TR
+><TR
+><TD
+>m - Minutes</TD
+></TR
+><TR
+><TD
+>h - Hours</TD
+></TR
+><TR
+><TD
+>d - Days</TD
+></TR
+><TR
+><TD
+>w - Weeks</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>&#13;</P
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN309"
+></A
+><H4
+>CACHE ADD <VAR
+CLASS="REPLACEABLE"
+>key</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>data</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>time-out</VAR
+></H4
+><P
+>Add specified key+data to the cache with the given timeout.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN315"
+></A
+><H4
+>CACHE DEL <VAR
+CLASS="REPLACEABLE"
+>key</VAR
+></H4
+><P
+>Delete key from the cache.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN319"
+></A
+><H4
+>CACHE SET <VAR
+CLASS="REPLACEABLE"
+>key</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>data</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>time-out</VAR
+></H4
+><P
+>Update data of existing cache entry.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN325"
+></A
+><H4
+>CACHE SEARCH <VAR
+CLASS="REPLACEABLE"
+>PATTERN</VAR
+></H4
+><P
+>Search for the specified pattern in the cache data.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN329"
+></A
+><H4
+>CACHE LIST</H4
+><P
+>List all current items in the cache.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN332"
+></A
+><H4
+>CACHE FLUSH</H4
+><P
+>Remove all the current items from the cache.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN335"
+></A
+><H3
+>GETLOCALSID [DOMAIN]</H3
+><P
+>Print the SID of the specified domain, or if the parameter is 
+omitted, the SID of the domain the local server is in.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN338"
+></A
+><H3
+>SETLOCALSID S-1-5-21-x-y-z</H3
+><P
+>Sets domain sid for the local server to the specified SID.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN341"
+></A
+><H3
+>MAXRID</H3
+><P
+>Prints out the highest RID currently in use on the local 
+server (by the active 'passdb backend').</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN344"
+></A
+><H3
+>RPC INFO</H3
+><P
+>Print information about the domain of the remote server, 
+such as domain name, domain sid and number of users and groups.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN347"
+></A
+><H3
+>[RPC|ADS] TESTJOIN</H3
+><P
+>Check whether participation in a domain is still valid.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN350"
+></A
+><H3
+>[RPC|ADS] CHANGETRUSTPW</H3
+><P
+>Force change of domain trust password.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN353"
+></A
+><H3
+>RPC TRUSTDOM</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN355"
+></A
+><H4
+>RPC TRUSTDOM ADD <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H4
+><P
+>Add a interdomain trust account for 
+<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+> to the remote server. </P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN360"
+></A
+><H4
+>RPC TRUSTDOM DEL <VAR
+CLASS="REPLACEABLE"
+>DOMAIM</VAR
+></H4
+><P
+>Remove interdomain trust account for 
+<VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+> from the remote server. </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
+>Currently NOT implemented.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN367"
+></A
+><H4
+>RPC TRUSTDOM ESTABLISH <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H4
+><P
+>Establish a trust relationship to a trusting domain. 
+Interdomain account must already be created on the remote PDC.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN371"
+></A
+><H4
+>RPC TRUSTDOM REVOKE <VAR
+CLASS="REPLACEABLE"
+>DOMAIN</VAR
+></H4
+><P
+>Abandon relationship to trusted domain</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN375"
+></A
+><H4
+>RPC TRUSTDOM LIST</H4
+><P
+>List all current interdomain trust relationships.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN378"
+></A
+><H3
+>RPC ABORTSHUTDOWN</H3
+><P
+>Abort the shutdown of a remote server.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN381"
+></A
+><H3
+>SHUTDOWN [-t timeout] [-r] [-f] [-C message]</H3
+><P
+>Shut down the remote server.</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-r</DT
+><DD
+><P
+>Reboot after shutdown.</P
+></DD
+><DT
+>-f</DT
+><DD
+><P
+>Force shutting down all applications.</P
+></DD
+><DT
+>-t timeout</DT
+><DD
+><P
+>Timeout before system will be shut down. An interactive 
+user of the system can use this time to cancel the shutdown.</P
+></DD
+><DT
+>-C message</DT
+><DD
+><P
+>Display the specified message on the screen to 
+announce the shutdown.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN401"
+></A
+><H3
+>SAMDUMP</H3
+><P
+>Print out sam database of remote server. You need
+to run this on either a BDC. </P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN404"
+></A
+><H3
+>VAMPIRE</H3
+><P
+>Export users, aliases and groups from remote server to 
+local server. Can only be run an a BDC.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN407"
+></A
+><H3
+>GETSID</H3
+><P
+>Fetch domain SID and store it in the local <TT
+CLASS="FILENAME"
+>secrets.tdb</TT
+>. </P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN411"
+></A
+><H3
+>ADS LEAVE</H3
+><P
+>Make the remote host leave the domain it is part of. </P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN414"
+></A
+><H3
+>ADS STATUS</H3
+><P
+>Print out status of machine account of the local machine in ADS.
+Prints out quite some debug info. Aimed at developers, regular 
+users should use <B
+CLASS="COMMAND"
+>NET ADS TESTJOIN</B
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN418"
+></A
+><H3
+>ADS PRINTER</H3
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN420"
+></A
+><H4
+>ADS PRINTER INFO [<VAR
+CLASS="REPLACEABLE"
+>PRINTER</VAR
+>] [<VAR
+CLASS="REPLACEABLE"
+>SERVER</VAR
+>]</H4
+><P
+>Lookup info for <VAR
+CLASS="REPLACEABLE"
+>PRINTER</VAR
+> on <VAR
+CLASS="REPLACEABLE"
+>SERVER</VAR
+>. The printer name defaults to "*", the 
+server name defaults to the local host.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN427"
+></A
+><H4
+>ADS PRINTER PUBLISH <VAR
+CLASS="REPLACEABLE"
+>PRINTER</VAR
+></H4
+><P
+>Publish specified printer using ADS.</P
+></DIV
+><DIV
+CLASS="REFSECT3"
+><A
+NAME="AEN431"
+></A
+><H4
+>ADS PRINTER REMOVE <VAR
+CLASS="REPLACEABLE"
+>PRINTER</VAR
+></H4
+><P
+>Remove specified printer from ADS directory.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN435"
+></A
+><H3
+>ADS SEARCH <VAR
+CLASS="REPLACEABLE"
+>EXPRESSION</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>ATTRIBUTES...</VAR
+></H3
+><P
+>Perform a raw LDAP search on a ADS server and dump the results. The 
+expression is a standard LDAP search expression, and the 
+attributes are a list of LDAP fields to show in the results.</P
+><P
+>Example: <KBD
+CLASS="USERINPUT"
+>net ads search '(objectCategory=group)' sAMAccountName</KBD
+></P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN442"
+></A
+><H3
+>ADS DN <VAR
+CLASS="REPLACEABLE"
+>DN</VAR
+> <VAR
+CLASS="REPLACEABLE"
+>(attributes)</VAR
+></H3
+><P
+>Perform a raw LDAP search on a ADS server and dump the results. The 
+DN standard LDAP DN, and the attributes are a list of LDAP fields 
+to show in the result. </P
+><P
+>Example: <KBD
+CLASS="USERINPUT"
+>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</KBD
+></P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN449"
+></A
+><H3
+>WORKGROUP</H3
+><P
+>Print out workgroup name for specified kerberos realm.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN452"
+></A
+><H3
+>HELP [COMMAND]</H3
+><P
+>Gives usage information for the specified command.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN455"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is incomplete for version 3.0 of the Samba 
+	suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN458"
+></A
 ><H2
 >AUTHOR</H2
 ><P
@@ -405,9 +1579,7 @@ NAME="AEN198"
 	by the Samba Team as an Open Source project similar 
 	to the way the Linux kernel is developed.</P
 ><P
->The original Samba man pages were written by Karl Auer.
-	The current set of manpages and documentation is maintained
-	by the Samba Team in the same fashion as the Samba source code.</P
+>The net manpage was written by Jelmer Vernooij.</P
 ></DIV
 ></BODY
 ></HTML
diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html
index 20bf1e4e21..3e5177578c 100644
--- a/docs/htmldocs/optional.html
+++ b/docs/htmldocs/optional.html
@@ -11,7 +11,7 @@ TITLE="SAMBA Project Documentation"
 HREF="samba-howto-collection.html"><LINK
 REL="PREVIOUS"
 TITLE="Samba as a NT4 or Win2k domain member"
-HREF="domain-security.html"><LINK
+HREF="domain-member.html"><LINK
 REL="NEXT"
 TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
 HREF="unix-permissions.html"></HEAD
@@ -42,7 +42,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="domain-security.html"
+HREF="domain-member.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -75,956 +75,17 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >III. Advanced Configuration</H1
+></DIV
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN1511"
+NAME="AEN1520"
 ></A
 ><H1
 >Introduction</H1
 ><P
 >Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.</P
 ></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->10. <A
-HREF="unix-permissions.html"
->UNIX Permission Bits and Windows NT Access Control Lists</A
-></DT
-><DD
-><DL
-><DT
->10.1. <A
-HREF="unix-permissions.html#AEN1525"
->Viewing and changing UNIX permissions using the NT 
-	security dialogs</A
-></DT
-><DT
->10.2. <A
-HREF="unix-permissions.html#AEN1531"
->How to view file security on a Samba share</A
-></DT
-><DT
->10.3. <A
-HREF="unix-permissions.html#AEN1542"
->Viewing file ownership</A
-></DT
-><DT
->10.4. <A
-HREF="unix-permissions.html#AEN1562"
->Viewing file or directory permissions</A
-></DT
-><DD
-><DL
-><DT
->10.4.1. <A
-HREF="unix-permissions.html#AEN1577"
->File Permissions</A
-></DT
-><DT
->10.4.2. <A
-HREF="unix-permissions.html#AEN1591"
->Directory Permissions</A
-></DT
-></DL
-></DD
-><DT
->10.5. <A
-HREF="unix-permissions.html#AEN1598"
->Modifying file or directory permissions</A
-></DT
-><DT
->10.6. <A
-HREF="unix-permissions.html#AEN1620"
->Interaction with the standard Samba create mask 
-	parameters</A
-></DT
-><DT
->10.7. <A
-HREF="unix-permissions.html#AEN1673"
->Interaction with the standard Samba file attribute 
-	mapping</A
-></DT
-></DL
-></DD
-><DT
->11. <A
-HREF="groupmapping.html"
->Configuring Group Mapping</A
-></DT
-><DT
->12. <A
-HREF="printing.html"
->Printing Support</A
-></DT
-><DD
-><DL
-><DT
->12.1. <A
-HREF="printing.html#AEN1736"
->Introduction</A
-></DT
-><DT
->12.2. <A
-HREF="printing.html#AEN1758"
->Configuration</A
-></DT
-><DD
-><DL
-><DT
->12.2.1. <A
-HREF="printing.html#AEN1766"
->Creating [print$]</A
-></DT
-><DT
->12.2.2. <A
-HREF="printing.html#AEN1801"
->Setting Drivers for Existing Printers</A
-></DT
-><DT
->12.2.3. <A
-HREF="printing.html#AEN1817"
->Support a large number of printers</A
-></DT
-><DT
->12.2.4. <A
-HREF="printing.html#AEN1832"
->Adding New Printers via the Windows NT APW</A
-></DT
-><DT
->12.2.5. <A
-HREF="printing.html#AEN1862"
->Samba and Printer Ports</A
-></DT
-></DL
-></DD
-><DT
->12.3. <A
-HREF="printing.html#AEN1870"
->The Imprints Toolset</A
-></DT
-><DD
-><DL
-><DT
->12.3.1. <A
-HREF="printing.html#AEN1874"
->What is Imprints?</A
-></DT
-><DT
->12.3.2. <A
-HREF="printing.html#AEN1884"
->Creating Printer Driver Packages</A
-></DT
-><DT
->12.3.3. <A
-HREF="printing.html#AEN1887"
->The Imprints server</A
-></DT
-><DT
->12.3.4. <A
-HREF="printing.html#AEN1891"
->The Installation Client</A
-></DT
-></DL
-></DD
-><DT
->12.4. <A
-HREF="printing.html#AEN1913"
->Diagnosis</A
-></DT
-><DD
-><DL
-><DT
->12.4.1. <A
-HREF="printing.html#AEN1915"
->Introduction</A
-></DT
-><DT
->12.4.2. <A
-HREF="printing.html#AEN1931"
->Debugging printer problems</A
-></DT
-><DT
->12.4.3. <A
-HREF="printing.html#AEN1940"
->What printers do I have?</A
-></DT
-><DT
->12.4.4. <A
-HREF="printing.html#AEN1948"
->Setting up printcap and print servers</A
-></DT
-><DT
->12.4.5. <A
-HREF="printing.html#AEN1976"
->Job sent, no output</A
-></DT
-><DT
->12.4.6. <A
-HREF="printing.html#AEN1987"
->Job sent, strange output</A
-></DT
-><DT
->12.4.7. <A
-HREF="printing.html#AEN1999"
->Raw PostScript printed</A
-></DT
-><DT
->12.4.8. <A
-HREF="printing.html#AEN2002"
->Advanced Printing</A
-></DT
-><DT
->12.4.9. <A
-HREF="printing.html#AEN2005"
->Real debugging</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->13. <A
-HREF="cups-printing.html"
->CUPS Printing Support</A
-></DT
-><DD
-><DL
-><DT
->13.1. <A
-HREF="cups-printing.html#AEN2025"
->Introduction</A
-></DT
-><DT
->13.2. <A
-HREF="cups-printing.html#AEN2032"
->Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></DT
-><DT
->13.3. <A
-HREF="cups-printing.html#AEN2052"
->CUPS - RAW Print Through Mode</A
-></DT
-><DT
->13.4. <A
-HREF="cups-printing.html#AEN2111"
->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></DT
-><DT
->13.5. <A
-HREF="cups-printing.html#AEN2132"
->Windows Terminal Servers (WTS) as CUPS clients</A
-></DT
-><DT
->13.6. <A
-HREF="cups-printing.html#AEN2136"
->Setting up CUPS for driver download</A
-></DT
-><DT
->13.7. <A
-HREF="cups-printing.html#AEN2149"
->Sources of CUPS drivers / PPDs</A
-></DT
-><DD
-><DL
-><DT
->13.7.1. <A
-HREF="cups-printing.html#AEN2176"
-><B
-CLASS="COMMAND"
->cupsaddsmb</B
-></A
-></DT
-></DL
-></DD
-><DT
->13.8. <A
-HREF="cups-printing.html#AEN2205"
->The CUPS Filter Chains</A
-></DT
-><DT
->13.9. <A
-HREF="cups-printing.html#AEN2244"
->CUPS Print Drivers and Devices</A
-></DT
-><DD
-><DL
-><DT
->13.9.1. <A
-HREF="cups-printing.html#AEN2251"
->Further printing steps</A
-></DT
-></DL
-></DD
-><DT
->13.10. <A
-HREF="cups-printing.html#AEN2321"
->Limiting the number of pages users can print</A
-></DT
-><DT
->13.11. <A
-HREF="cups-printing.html#AEN2417"
->Advanced Postscript Printing from MS Windows</A
-></DT
-><DT
->13.12. <A
-HREF="cups-printing.html#AEN2432"
->Auto-Deletion of CUPS spool files</A
-></DT
-></DL
-></DD
-><DT
->14. <A
-HREF="winbind.html"
->Unified Logons between Windows NT and UNIX using Winbind</A
-></DT
-><DD
-><DL
-><DT
->14.1. <A
-HREF="winbind.html#AEN2506"
->Abstract</A
-></DT
-><DT
->14.2. <A
-HREF="winbind.html#AEN2510"
->Introduction</A
-></DT
-><DT
->14.3. <A
-HREF="winbind.html#AEN2523"
->What Winbind Provides</A
-></DT
-><DD
-><DL
-><DT
->14.3.1. <A
-HREF="winbind.html#AEN2530"
->Target Uses</A
-></DT
-></DL
-></DD
-><DT
->14.4. <A
-HREF="winbind.html#AEN2534"
->How Winbind Works</A
-></DT
-><DD
-><DL
-><DT
->14.4.1. <A
-HREF="winbind.html#AEN2539"
->Microsoft Remote Procedure Calls</A
-></DT
-><DT
->14.4.2. <A
-HREF="winbind.html#AEN2543"
->Microsoft Active Directory Services</A
-></DT
-><DT
->14.4.3. <A
-HREF="winbind.html#AEN2546"
->Name Service Switch</A
-></DT
-><DT
->14.4.4. <A
-HREF="winbind.html#AEN2562"
->Pluggable Authentication Modules</A
-></DT
-><DT
->14.4.5. <A
-HREF="winbind.html#AEN2570"
->User and Group ID Allocation</A
-></DT
-><DT
->14.4.6. <A
-HREF="winbind.html#AEN2574"
->Result Caching</A
-></DT
-></DL
-></DD
-><DT
->14.5. <A
-HREF="winbind.html#AEN2577"
->Installation and Configuration</A
-></DT
-><DD
-><DL
-><DT
->14.5.1. <A
-HREF="winbind.html#AEN2582"
->Introduction</A
-></DT
-><DT
->14.5.2. <A
-HREF="winbind.html#AEN2595"
->Requirements</A
-></DT
-><DT
->14.5.3. <A
-HREF="winbind.html#AEN2609"
->Testing Things Out</A
-></DT
-></DL
-></DD
-><DT
->14.6. <A
-HREF="winbind.html#AEN2834"
->Limitations</A
-></DT
-><DT
->14.7. <A
-HREF="winbind.html#AEN2844"
->Conclusion</A
-></DT
-></DL
-></DD
-><DT
->15. <A
-HREF="advancednetworkmanagement.html"
->Advanced Network Manangement</A
-></DT
-><DD
-><DL
-><DT
->15.1. <A
-HREF="advancednetworkmanagement.html#AEN2859"
->Configuring Samba Share Access Controls</A
-></DT
-><DD
-><DL
-><DT
->15.1.1. <A
-HREF="advancednetworkmanagement.html#AEN2869"
->Share Permissions Management</A
-></DT
-></DL
-></DD
-><DT
->15.2. <A
-HREF="advancednetworkmanagement.html#AEN2897"
->Remote Server Administration</A
-></DT
-><DT
->15.3. <A
-HREF="advancednetworkmanagement.html#AEN2914"
->Network Logon Script Magic</A
-></DT
-></DL
-></DD
-><DT
->16. <A
-HREF="policymgmt.html"
->System and Account Policies</A
-></DT
-><DD
-><DL
-><DT
->16.1. <A
-HREF="policymgmt.html#AEN2929"
->Creating and Managing System Policies</A
-></DT
-><DD
-><DL
-><DT
->16.1.1. <A
-HREF="policymgmt.html#AEN2943"
->Windows 9x/Me Policies</A
-></DT
-><DT
->16.1.2. <A
-HREF="policymgmt.html#AEN2955"
->Windows NT4 Style Policy Files</A
-></DT
-><DT
->16.1.3. <A
-HREF="policymgmt.html#AEN2973"
->MS Windows 200x / XP Professional Policies</A
-></DT
-></DL
-></DD
-><DT
->16.2. <A
-HREF="policymgmt.html#AEN3002"
->Managing Account/User Policies</A
-></DT
-><DD
-><DL
-><DT
->16.2.1. <A
-HREF="policymgmt.html#AEN3017"
->With Windows NT4/200x</A
-></DT
-><DT
->16.2.2. <A
-HREF="policymgmt.html#AEN3020"
->With a Samba PDC</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->17. <A
-HREF="profilemgmt.html"
->Desktop Profile Management</A
-></DT
-><DD
-><DL
-><DT
->17.1. <A
-HREF="profilemgmt.html#AEN3035"
->Roaming Profiles</A
-></DT
-><DD
-><DL
-><DT
->17.1.1. <A
-HREF="profilemgmt.html#AEN3042"
->Samba Configuration for Profile Handling</A
-></DT
-><DT
->17.1.2. <A
-HREF="profilemgmt.html#AEN3077"
->Windows Client Profile Configuration Information</A
-></DT
-><DT
->17.1.3. <A
-HREF="profilemgmt.html#AEN3197"
->Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
-></DT
-><DT
->17.1.4. <A
-HREF="profilemgmt.html#AEN3204"
->Profile Migration from Windows NT4/200x Server to Samba</A
-></DT
-></DL
-></DD
-><DT
->17.2. <A
-HREF="profilemgmt.html#AEN3242"
->Mandatory profiles</A
-></DT
-><DT
->17.3. <A
-HREF="profilemgmt.html#AEN3249"
->Creating/Managing Group Profiles</A
-></DT
-><DT
->17.4. <A
-HREF="profilemgmt.html#AEN3255"
->Default Profile for Windows Users</A
-></DT
-><DD
-><DL
-><DT
->17.4.1. <A
-HREF="profilemgmt.html#AEN3259"
->MS Windows 9x/Me</A
-></DT
-><DT
->17.4.2. <A
-HREF="profilemgmt.html#AEN3271"
->MS Windows NT4 Workstation</A
-></DT
-><DT
->17.4.3. <A
-HREF="profilemgmt.html#AEN3325"
->MS Windows 200x/XP</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->18. <A
-HREF="interdomaintrusts.html"
->Interdomain Trust Relationships</A
-></DT
-><DD
-><DL
-><DT
->18.1. <A
-HREF="interdomaintrusts.html#AEN3386"
->Trust Relationship Background</A
-></DT
-><DT
->18.2. <A
-HREF="interdomaintrusts.html#AEN3395"
->MS Windows NT4 Trust Configuration</A
-></DT
-><DD
-><DL
-><DT
->18.2.1. <A
-HREF="interdomaintrusts.html#AEN3398"
->NT4 as the Trusting Domain</A
-></DT
-><DT
->18.2.2. <A
-HREF="interdomaintrusts.html#AEN3401"
->NT4 as the Trusted Domain</A
-></DT
-></DL
-></DD
-><DT
->18.3. <A
-HREF="interdomaintrusts.html#AEN3405"
->Configuring Samba Domain Trusts</A
-></DT
-><DD
-><DL
-><DT
->18.3.1. <A
-HREF="interdomaintrusts.html#AEN3409"
->Samba3 as the Trusting Domain</A
-></DT
-><DT
->18.3.2. <A
-HREF="interdomaintrusts.html#AEN3416"
->Samba3 as the Trusted Domain</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->19. <A
-HREF="pam.html"
->PAM Configuration for Centrally Managed Authentication</A
-></DT
-><DD
-><DL
-><DT
->19.1. <A
-HREF="pam.html#AEN3440"
->Samba and PAM</A
-></DT
-><DT
->19.2. <A
-HREF="pam.html#AEN3491"
->Distributed Authentication</A
-></DT
-><DT
->19.3. <A
-HREF="pam.html#AEN3496"
->PAM Configuration in smb.conf</A
-></DT
-></DL
-></DD
-><DT
->20. <A
-HREF="vfs.html"
->Stackable VFS modules</A
-></DT
-><DD
-><DL
-><DT
->20.1. <A
-HREF="vfs.html#AEN3531"
->Introduction and configuration</A
-></DT
-><DT
->20.2. <A
-HREF="vfs.html#AEN3540"
->Included modules</A
-></DT
-><DD
-><DL
-><DT
->20.2.1. <A
-HREF="vfs.html#AEN3542"
->audit</A
-></DT
-><DT
->20.2.2. <A
-HREF="vfs.html#AEN3550"
->extd_audit</A
-></DT
-><DT
->20.2.3. <A
-HREF="vfs.html#AEN3554"
->recycle</A
-></DT
-><DT
->20.2.4. <A
-HREF="vfs.html#AEN3591"
->netatalk</A
-></DT
-></DL
-></DD
-><DT
->20.3. <A
-HREF="vfs.html#AEN3598"
->VFS modules available elsewhere</A
-></DT
-><DD
-><DL
-><DT
->20.3.1. <A
-HREF="vfs.html#AEN3602"
->DatabaseFS</A
-></DT
-><DT
->20.3.2. <A
-HREF="vfs.html#AEN3610"
->vscan</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->21. <A
-HREF="msdfs.html"
->Hosting a Microsoft Distributed File System tree on Samba</A
-></DT
-><DD
-><DL
-><DT
->21.1. <A
-HREF="msdfs.html#AEN3626"
->Instructions</A
-></DT
-><DD
-><DL
-><DT
->21.1.1. <A
-HREF="msdfs.html#AEN3661"
->Notes</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->22. <A
-HREF="integrate-ms-networks.html"
->Integrating MS Windows networks with Samba</A
-></DT
-><DD
-><DL
-><DT
->22.1. <A
-HREF="integrate-ms-networks.html#AEN3688"
->Name Resolution in a pure Unix/Linux world</A
-></DT
-><DD
-><DL
-><DT
->22.1.1. <A
-HREF="integrate-ms-networks.html#AEN3704"
-><TT
-CLASS="FILENAME"
->/etc/hosts</TT
-></A
-></DT
-><DT
->22.1.2. <A
-HREF="integrate-ms-networks.html#AEN3720"
-><TT
-CLASS="FILENAME"
->/etc/resolv.conf</TT
-></A
-></DT
-><DT
->22.1.3. <A
-HREF="integrate-ms-networks.html#AEN3731"
-><TT
-CLASS="FILENAME"
->/etc/host.conf</TT
-></A
-></DT
-><DT
->22.1.4. <A
-HREF="integrate-ms-networks.html#AEN3739"
-><TT
-CLASS="FILENAME"
->/etc/nsswitch.conf</TT
-></A
-></DT
-></DL
-></DD
-><DT
->22.2. <A
-HREF="integrate-ms-networks.html#AEN3751"
->Name resolution as used within MS Windows networking</A
-></DT
-><DD
-><DL
-><DT
->22.2.1. <A
-HREF="integrate-ms-networks.html#AEN3763"
->The NetBIOS Name Cache</A
-></DT
-><DT
->22.2.2. <A
-HREF="integrate-ms-networks.html#AEN3768"
->The LMHOSTS file</A
-></DT
-><DT
->22.2.3. <A
-HREF="integrate-ms-networks.html#AEN3776"
->HOSTS file</A
-></DT
-><DT
->22.2.4. <A
-HREF="integrate-ms-networks.html#AEN3781"
->DNS Lookup</A
-></DT
-><DT
->22.2.5. <A
-HREF="integrate-ms-networks.html#AEN3784"
->WINS Lookup</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->23. <A
-HREF="improved-browsing.html"
->Improved browsing in samba</A
-></DT
-><DD
-><DL
-><DT
->23.1. <A
-HREF="improved-browsing.html#AEN3804"
->Overview of browsing</A
-></DT
-><DT
->23.2. <A
-HREF="improved-browsing.html#AEN3810"
->Browsing support in samba</A
-></DT
-><DT
->23.3. <A
-HREF="improved-browsing.html#AEN3825"
->Problem resolution</A
-></DT
-><DT
->23.4. <A
-HREF="improved-browsing.html#AEN3837"
->Browsing across subnets</A
-></DT
-><DD
-><DL
-><DT
->23.4.1. <A
-HREF="improved-browsing.html#AEN3843"
->How does cross subnet browsing work ?</A
-></DT
-></DL
-></DD
-><DT
->23.5. <A
-HREF="improved-browsing.html#AEN3878"
->Setting up a WINS server</A
-></DT
-><DT
->23.6. <A
-HREF="improved-browsing.html#AEN3901"
->Setting up Browsing in a WORKGROUP</A
-></DT
-><DT
->23.7. <A
-HREF="improved-browsing.html#AEN3927"
->Setting up Browsing in a DOMAIN</A
-></DT
-><DT
->23.8. <A
-HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
->Forcing samba to be the master</A
-></DT
-><DT
->23.9. <A
-HREF="improved-browsing.html#AEN3962"
->Making samba the domain master</A
-></DT
-><DT
->23.10. <A
-HREF="improved-browsing.html#AEN3984"
->Note about broadcast addresses</A
-></DT
-><DT
->23.11. <A
-HREF="improved-browsing.html#AEN3987"
->Multiple interfaces</A
-></DT
-></DL
-></DD
-><DT
->24. <A
-HREF="securing-samba.html"
->Securing Samba</A
-></DT
-><DD
-><DL
-><DT
->24.1. <A
-HREF="securing-samba.html#AEN4003"
->Introduction</A
-></DT
-><DT
->24.2. <A
-HREF="securing-samba.html#AEN4006"
->Using host based protection</A
-></DT
-><DT
->24.3. <A
-HREF="securing-samba.html#AEN4016"
->Using interface protection</A
-></DT
-><DT
->24.4. <A
-HREF="securing-samba.html#AEN4025"
->Using a firewall</A
-></DT
-><DT
->24.5. <A
-HREF="securing-samba.html#AEN4032"
->Using a IPC$ share deny</A
-></DT
-><DT
->24.6. <A
-HREF="securing-samba.html#AEN4041"
->Upgrading Samba</A
-></DT
-></DL
-></DD
-><DT
->25. <A
-HREF="unicode.html"
->Unicode/Charsets</A
-></DT
-><DD
-><DL
-><DT
->25.1. <A
-HREF="unicode.html#AEN4056"
->What are charsets and unicode?</A
-></DT
-><DT
->25.2. <A
-HREF="unicode.html#AEN4065"
->Samba and charsets</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
@@ -1042,7 +103,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="domain-security.html"
+HREF="domain-member.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html
index ac0cef9f14..be7773cd2a 100644
--- a/docs/htmldocs/other-clients.html
+++ b/docs/htmldocs/other-clients.html
@@ -16,8 +16,8 @@ REL="PREVIOUS"
 TITLE="Portability"
 HREF="portability.html"><LINK
 REL="NEXT"
-TITLE="How to compile SAMBA"
-HREF="compiling.html"></HEAD
+TITLE="SWAT - The Samba Web Admininistration Tool"
+HREF="swat.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -59,7 +59,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="compiling.html"
+HREF="swat.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -75,6 +75,102 @@ CLASS="CHAPTER"
 NAME="OTHER-CLIENTS"
 ></A
 >Chapter 30. Samba and other CIFS clients</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>30.1. <A
+HREF="other-clients.html#AEN4501"
+>Macintosh clients?</A
+></DT
+><DT
+>30.2. <A
+HREF="other-clients.html#AEN4510"
+>OS2 Client</A
+></DT
+><DD
+><DL
+><DT
+>30.2.1. <A
+HREF="other-clients.html#AEN4512"
+>How can I configure OS/2 Warp Connect or 
+		OS/2 Warp 4 as a client for Samba?</A
+></DT
+><DT
+>30.2.2. <A
+HREF="other-clients.html#AEN4527"
+>How can I configure OS/2 Warp 3 (not Connect), 
+		OS/2 1.2, 1.3 or 2.x for Samba?</A
+></DT
+><DT
+>30.2.3. <A
+HREF="other-clients.html#AEN4536"
+>Are there any other issues when OS/2 (any version) 
+		is used as a client?</A
+></DT
+><DT
+>30.2.4. <A
+HREF="other-clients.html#AEN4540"
+>How do I get printer driver download working 
+		for OS/2 clients?</A
+></DT
+></DL
+></DD
+><DT
+>30.3. <A
+HREF="other-clients.html#AEN4550"
+>Windows for Workgroups</A
+></DT
+><DD
+><DL
+><DT
+>30.3.1. <A
+HREF="other-clients.html#AEN4552"
+>Use latest TCP/IP stack from Microsoft</A
+></DT
+><DT
+>30.3.2. <A
+HREF="other-clients.html#AEN4557"
+>Delete .pwl files after password change</A
+></DT
+><DT
+>30.3.3. <A
+HREF="other-clients.html#AEN4562"
+>Configure WfW password handling</A
+></DT
+><DT
+>30.3.4. <A
+HREF="other-clients.html#AEN4566"
+>Case handling of passwords</A
+></DT
+><DT
+>30.3.5. <A
+HREF="other-clients.html#AEN4571"
+>Use TCP/IP as default protocol</A
+></DT
+></DL
+></DD
+><DT
+>30.4. <A
+HREF="other-clients.html#AEN4574"
+>Windows '95/'98</A
+></DT
+><DT
+>30.5. <A
+HREF="other-clients.html#AEN4590"
+>Windows 2000 Service Pack 2</A
+></DT
+><DT
+>30.6. <A
+HREF="other-clients.html#AEN4607"
+>Windows NT 3.1</A
+></DT
+></DL
+></DIV
 ><P
 >This chapter contains client-specific information.</P
 ><DIV
@@ -82,7 +178,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4326"
+NAME="AEN4501"
 >30.1. Macintosh clients?</A
 ></H1
 ><P
@@ -128,7 +224,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4335"
+NAME="AEN4510"
 >30.2. OS2 Client</A
 ></H1
 ><DIV
@@ -136,7 +232,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4337"
+NAME="AEN4512"
 >30.2.1. How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?</A
 ></H2
@@ -195,7 +291,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4352"
+NAME="AEN4527"
 >30.2.2. How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?</A
 ></H2
@@ -239,7 +335,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4361"
+NAME="AEN4536"
 >30.2.3. Are there any other issues when OS/2 (any version) 
 		is used as a client?</A
 ></H2
@@ -261,7 +357,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4365"
+NAME="AEN4540"
 >30.2.4. How do I get printer driver download working 
 		for OS/2 clients?</A
 ></H2
@@ -308,7 +404,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4375"
+NAME="AEN4550"
 >30.3. Windows for Workgroups</A
 ></H1
 ><DIV
@@ -316,7 +412,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4377"
+NAME="AEN4552"
 >30.3.1. Use latest TCP/IP stack from Microsoft</A
 ></H2
 ><P
@@ -338,7 +434,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4382"
+NAME="AEN4557"
 >30.3.2. Delete .pwl files after password change</A
 ></H2
 ><P
@@ -358,7 +454,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4387"
+NAME="AEN4562"
 >30.3.3. Configure WfW password handling</A
 ></H2
 ><P
@@ -377,7 +473,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4391"
+NAME="AEN4566"
 >30.3.4. Case handling of passwords</A
 ></H2
 ><P
@@ -395,7 +491,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4396"
+NAME="AEN4571"
 >30.3.5. Use TCP/IP as default protocol</A
 ></H2
 ><P
@@ -411,7 +507,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4399"
+NAME="AEN4574"
 >30.4. Windows '95/'98</A
 ></H1
 ><P
@@ -459,7 +555,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4415"
+NAME="AEN4590"
 >30.5. Windows 2000 Service Pack 2</A
 ></H1
 ><P
@@ -559,7 +655,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4432"
+NAME="AEN4607"
 >30.6. Windows NT 3.1</A
 ></H1
 ><P
@@ -605,7 +701,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="compiling.html"
+HREF="swat.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -629,7 +725,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->How to compile SAMBA</TD
+>SWAT - The Samba Web Admininistration Tool</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html
index a4530aa0a1..8c01914110 100644
--- a/docs/htmldocs/pam.html
+++ b/docs/htmldocs/pam.html
@@ -74,14 +74,38 @@ CLASS="CHAPTER"
 ><A
 NAME="PAM"
 ></A
->Chapter 19. PAM Configuration for Centrally Managed Authentication</H1
+>Chapter 20. PAM Configuration for Centrally Managed Authentication</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>20.1. <A
+HREF="pam.html#AEN3508"
+>Samba and PAM</A
+></DT
+><DT
+>20.2. <A
+HREF="pam.html#AEN3559"
+>Distributed Authentication</A
+></DT
+><DT
+>20.3. <A
+HREF="pam.html#AEN3564"
+>PAM Configuration in smb.conf</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3440"
->19.1. Samba and PAM</A
+NAME="AEN3508"
+>20.1. Samba and PAM</A
 ></H1
 ><P
 >A number of Unix systems (eg: Sun Solaris), as well as the 
@@ -363,8 +387,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3491"
->19.2. Distributed Authentication</A
+NAME="AEN3559"
+>20.2. Distributed Authentication</A
 ></H1
 ><P
 >The astute administrator will realize from this that the 
@@ -389,8 +413,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3496"
->19.3. PAM Configuration in smb.conf</A
+NAME="AEN3564"
+>20.3. PAM Configuration in smb.conf</A
 ></H1
 ><P
 >There is an option in smb.conf called <A
diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html
index 35a941b63a..0b3fb11a2a 100644
--- a/docs/htmldocs/passdb.html
+++ b/docs/htmldocs/passdb.html
@@ -74,14 +74,164 @@ CLASS="CHAPTER"
 ><A
 NAME="PASSDB"
 ></A
->Chapter 3. User information database</H1
+>Chapter 4. User information database</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>4.1. <A
+HREF="passdb.html#AEN469"
+>Introduction</A
+></DT
+><DT
+>4.2. <A
+HREF="passdb.html#AEN476"
+>Important Notes About Security</A
+></DT
+><DD
+><DL
+><DT
+>4.2.1. <A
+HREF="passdb.html#AEN502"
+>Advantages of SMB Encryption</A
+></DT
+><DT
+>4.2.2. <A
+HREF="passdb.html#AEN508"
+>Advantages of non-encrypted passwords</A
+></DT
+></DL
+></DD
+><DT
+>4.3. <A
+HREF="passdb.html#AEN514"
+>The smbpasswd Command</A
+></DT
+><DT
+>4.4. <A
+HREF="passdb.html#AEN545"
+>Plain text</A
+></DT
+><DT
+>4.5. <A
+HREF="passdb.html#AEN550"
+>TDB</A
+></DT
+><DT
+>4.6. <A
+HREF="passdb.html#AEN553"
+>LDAP</A
+></DT
+><DD
+><DL
+><DT
+>4.6.1. <A
+HREF="passdb.html#AEN555"
+>Introduction</A
+></DT
+><DT
+>4.6.2. <A
+HREF="passdb.html#AEN575"
+>Introduction</A
+></DT
+><DT
+>4.6.3. <A
+HREF="passdb.html#AEN599"
+>Supported LDAP Servers</A
+></DT
+><DT
+>4.6.4. <A
+HREF="passdb.html#AEN604"
+>Schema and Relationship to the RFC 2307 posixAccount</A
+></DT
+><DT
+>4.6.5. <A
+HREF="passdb.html#AEN616"
+>Configuring Samba with LDAP</A
+></DT
+><DD
+><DL
+><DT
+>4.6.5.1. <A
+HREF="passdb.html#AEN618"
+>OpenLDAP configuration</A
+></DT
+><DT
+>4.6.5.2. <A
+HREF="passdb.html#AEN635"
+>Configuring Samba</A
+></DT
+></DL
+></DD
+><DT
+>4.6.6. <A
+HREF="passdb.html#AEN663"
+>Accounts and Groups management</A
+></DT
+><DT
+>4.6.7. <A
+HREF="passdb.html#AEN668"
+>Security and sambaAccount</A
+></DT
+><DT
+>4.6.8. <A
+HREF="passdb.html#AEN688"
+>LDAP specials attributes for sambaAccounts</A
+></DT
+><DT
+>4.6.9. <A
+HREF="passdb.html#AEN758"
+>Example LDIF Entries for a sambaAccount</A
+></DT
+></DL
+></DD
+><DT
+>4.7. <A
+HREF="passdb.html#AEN766"
+>MySQL</A
+></DT
+><DD
+><DL
+><DT
+>4.7.1. <A
+HREF="passdb.html#AEN768"
+>Creating the database</A
+></DT
+><DT
+>4.7.2. <A
+HREF="passdb.html#AEN778"
+>Configuring</A
+></DT
+><DT
+>4.7.3. <A
+HREF="passdb.html#AEN795"
+>Using plaintext passwords or encrypted password</A
+></DT
+><DT
+>4.7.4. <A
+HREF="passdb.html#AEN800"
+>Getting non-column data from the table</A
+></DT
+></DL
+></DD
+><DT
+>4.8. <A
+HREF="passdb.html#AEN808"
+>XML</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN335"
->3.1. Introduction</A
+NAME="AEN469"
+>4.1. Introduction</A
 ></H1
 ><P
 >Old windows clients send plain text passwords over the wire. 
@@ -121,8 +271,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN342"
->3.2. Important Notes About Security</A
+NAME="AEN476"
+>4.2. Important Notes About Security</A
 ></H1
 ><P
 >The unix and SMB password encryption techniques seem similar 
@@ -248,44 +398,62 @@ BORDER="0"
 ></TABLE
 ><P
 ></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
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Note :</I
-></SPAN
 >All current release of 
-		Microsoft SMB/CIFS clients support authentication via the
-		SMB Challenge/Response mechanism described here.  Enabling
-		clear text authentication does not disable the ability
-		of the client to participate in encrypted authentication.</P
+	Microsoft SMB/CIFS clients support authentication via the
+	SMB Challenge/Response mechanism described here.  Enabling
+	clear text authentication does not disable the ability
+	of the client to participate in encrypted authentication.</P
+></TD
+></TR
+></TABLE
+></DIV
 ><P
 >MS Windows clients will cache the encrypted password alone.
-		Even when plain text passwords are re-enabled, through the appropriate
-		registry change, the plain text password is NEVER cached. This means that
-		in the event that a network connections should become disconnected (broken)
-		only the cached (encrypted) password will be sent to the resource server
-		to affect a auto-reconnect. If the resource server does not support encrypted
-		passwords the auto-reconnect will fail. <SPAN
+	Even when plain text passwords are re-enabled, through the appropriate
+	registry change, the plain text password is NEVER cached. This means that
+	in the event that a network connections should become disconnected (broken)
+	only the cached (encrypted) password will be sent to the resource server
+	to affect a auto-reconnect. If the resource server does not support encrypted
+	passwords the auto-reconnect will fail. <SPAN
 CLASS="emphasis"
 ><I
 CLASS="EMPHASIS"
 >USE OF ENCRYPTED PASSWORDS
-		IS STRONGLY ADVISED.</I
+	IS STRONGLY ADVISED.</I
 ></SPAN
 ></P
-></TD
-></TR
-></TABLE
-></DIV
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN368"
->3.2.1. Advantages of SMB Encryption</A
+NAME="AEN502"
+>4.2.1. Advantages of SMB Encryption</A
 ></H2
 ><P
 ></P
@@ -323,8 +491,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN374"
->3.2.2. Advantages of non-encrypted passwords</A
+NAME="AEN508"
+>4.2.2. Advantages of non-encrypted passwords</A
 ></H2
 ><P
 ></P
@@ -358,8 +526,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN380"
->3.3. The smbpasswd Command</A
+NAME="AEN514"
+>4.3. The smbpasswd Command</A
 ></H1
 ><P
 >The smbpasswd utility is a utility similar to the 
@@ -461,8 +629,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN411"
->3.4. Plain text</A
+NAME="AEN545"
+>4.4. Plain text</A
 ></H1
 ><P
 >Older versions of samba retrieved user information from the unix user database 
@@ -481,8 +649,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN416"
->3.5. TDB</A
+NAME="AEN550"
+>4.5. TDB</A
 ></H1
 ><P
 >Samba can also store the user data in a "TDB" (Trivial Database). Using this backend 
@@ -494,16 +662,16 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN419"
->3.6. LDAP</A
+NAME="AEN553"
+>4.6. LDAP</A
 ></H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN421"
->3.6.1. Introduction</A
+NAME="AEN555"
+>4.6.1. Introduction</A
 ></H2
 ><P
 >This document describes how to use an LDAP directory for storing Samba user
@@ -570,8 +738,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN441"
->3.6.2. Introduction</A
+NAME="AEN575"
+>4.6.2. Introduction</A
 ></H2
 ><P
 >Traditionally, when configuring <A
@@ -626,29 +794,9 @@ Identified (RID).</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. <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
-> or
-<VAR
-CLASS="PARAMETER"
->--with-tdbsam</VAR
->) requires compile time support.</P
-><P
->When compiling Samba to include the <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
-> 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
+API, and is still so named in the CVS trees). </P
 ><P
->There are a few points to stress about what the <VAR
-CLASS="PARAMETER"
->--with-ldapsam</VAR
->
+>There are a few points to stress about what the ldapsam
 does not provide.  The LDAP support referred to in the this documentation does not
 include:</P
 ><P
@@ -679,8 +827,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN470"
->3.6.3. Supported LDAP Servers</A
+NAME="AEN599"
+>4.6.3. Supported LDAP Servers</A
 ></H2
 ><P
 >The LDAP samdb code in 2.2.3 (and later) has been developed and tested
@@ -705,8 +853,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN475"
->3.6.4. Schema and Relationship to the RFC 2307 posixAccount</A
+NAME="AEN604"
+>4.6.4. Schema and Relationship to the RFC 2307 posixAccount</A
 ></H2
 ><P
 >Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
@@ -762,16 +910,16 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN487"
->3.6.5. Configuring Samba with LDAP</A
+NAME="AEN616"
+>4.6.5. Configuring Samba with LDAP</A
 ></H2
 ><DIV
 CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN489"
->3.6.5.1. OpenLDAP configuration</A
+NAME="AEN618"
+>4.6.5.1. OpenLDAP configuration</A
 ></H3
 ><P
 >To include support for the sambaAccount object in an OpenLDAP directory
@@ -817,9 +965,7 @@ include	           /etc/openldap/schema/core.schema
 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
+include            /etc/openldap/schema/nis.schema
 
 ....</PRE
 ></P
@@ -852,8 +998,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN506"
->3.6.5.2. Configuring Samba</A
+NAME="AEN635"
+>4.6.5.2. Configuring Samba</A
 ></H3
 ><P
 >The following parameters are available in smb.conf only with <VAR
@@ -968,8 +1114,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN534"
->3.6.6. Accounts and Groups management</A
+NAME="AEN663"
+>4.6.6. Accounts and Groups management</A
 ></H2
 ><P
 >As users accounts are managed thru the sambaAccount objectclass, you should
@@ -993,8 +1139,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN539"
->3.6.7. Security and sambaAccount</A
+NAME="AEN668"
+>4.6.7. Security and sambaAccount</A
 ></H2
 ><P
 >There are two important points to remember when discussing the security
@@ -1029,9 +1175,8 @@ CLASS="EMPHASIS"
 >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
+HREF="passdb.html"
+>User Database</A
 > of the Samba-HOWTO-Collection.</P
 ><P
 >To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
@@ -1072,8 +1217,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN559"
->3.6.8. LDAP specials attributes for sambaAccounts</A
+NAME="AEN688"
+>4.6.8. LDAP specials attributes for sambaAccounts</A
 ></H2
 ><P
 >The sambaAccount objectclass is composed of the following attributes:</P
@@ -1279,8 +1424,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN629"
->3.6.9. Example LDIF Entries for a sambaAccount</A
+NAME="AEN758"
+>4.6.9. Example LDIF Entries for a sambaAccount</A
 ></H2
 ><P
 >The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
@@ -1338,16 +1483,16 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN637"
->3.7. MySQL</A
+NAME="AEN766"
+>4.7. MySQL</A
 ></H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN639"
->3.7.1. Creating the database</A
+NAME="AEN768"
+>4.7.1. Creating the database</A
 ></H2
 ><P
 >You either can set up your own table and specify the field names to pdb_mysql (see below
@@ -1382,8 +1527,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN649"
->3.7.2. Configuring</A
+NAME="AEN778"
+>4.7.2. Configuring</A
 ></H2
 ><P
 >This plugin lacks some good documentation, but here is some short info:</P
@@ -1493,8 +1638,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN666"
->3.7.3. Using plaintext passwords or encrypted password</A
+NAME="AEN795"
+>4.7.3. Using plaintext passwords or encrypted password</A
 ></H2
 ><P
 >I strongly discourage the use of plaintext passwords, however, you can use them:</P
@@ -1508,8 +1653,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN671"
->3.7.4. Getting non-column data from the table</A
+NAME="AEN800"
+>4.7.4. Getting non-column data from the table</A
 ></H2
 ><P
 >It is possible to have not all data in the database and making some 'constant'.</P
@@ -1534,8 +1679,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN679"
->3.8. XML</A
+NAME="AEN808"
+>4.8. XML</A
 ></H1
 ><P
 >This module requires libxml2 to be installed.</P
diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html
index 5fb41fba4b..2fa0f15d38 100644
--- a/docs/htmldocs/pdbedit.8.html
+++ b/docs/htmldocs/pdbedit.8.html
@@ -95,8 +95,8 @@ CLASS="COMMAND"
 ><P
 ><PRE
 CLASS="SCREEN"
->sorce:500:Simo Sorce
-samba:45:Test User</PRE
+>   &nbsp;sorce:500:Simo Sorce
+   &nbsp;samba:45:Test User</PRE
 ></P
 ></DD
 ><DT
@@ -114,24 +114,24 @@ CLASS="COMMAND"
 ><P
 ><PRE
 CLASS="SCREEN"
->---------------
-username:       sorce
-user ID/Group:  500/500
-user RID/GRID:  2000/2001
-Full Name:      Simo Sorce
-Home Directory: \\BERSERKER\sorce
-HomeDir Drive:  H:
-Logon Script:   \\BERSERKER\netlogon\sorce.bat
-Profile Path:   \\BERSERKER\profile
----------------
-username:       samba
-user ID/Group:  45/45
-user RID/GRID:  1090/1091
-Full Name:      Test User
-Home Directory: \\BERSERKER\samba
-HomeDir Drive:  
-Logon Script:   
-Profile Path:   \\BERSERKER\profile</PRE
+>   &nbsp;---------------
+   &nbsp;username:       sorce
+   &nbsp;user ID/Group:  500/500
+   &nbsp;user RID/GRID:  2000/2001
+  5&nbsp;Full Name:      Simo Sorce
+   &nbsp;Home Directory: \\BERSERKER\sorce
+   &nbsp;HomeDir Drive:  H:
+   &nbsp;Logon Script:   \\BERSERKER\netlogon\sorce.bat
+   &nbsp;Profile Path:   \\BERSERKER\profile
+ 10&nbsp;---------------
+   &nbsp;username:       samba
+   &nbsp;user ID/Group:  45/45
+   &nbsp;user RID/GRID:  1090/1091
+   &nbsp;Full Name:      Test User
+ 15&nbsp;Home Directory: \\BERSERKER\samba
+   &nbsp;HomeDir Drive:  
+   &nbsp;Logon Script:   
+   &nbsp;Profile Path:   \\BERSERKER\profile</PRE
 ></P
 ></DD
 ><DT
@@ -159,8 +159,8 @@ CLASS="COMMAND"
 ></P
 ><PRE
 CLASS="SCREEN"
->sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
-samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:</PRE
+>   &nbsp;sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
+   &nbsp;samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:</PRE
 ></DD
 ><DT
 >-u username</DT
diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html
index 52788e2f0a..9daa44e78e 100644
--- a/docs/htmldocs/portability.html
+++ b/docs/htmldocs/portability.html
@@ -13,8 +13,8 @@ REL="UP"
 TITLE="Appendixes"
 HREF="appendixes.html"><LINK
 REL="PREVIOUS"
-TITLE="Samba performance issues"
-HREF="speed.html"><LINK
+TITLE="Migration from NT4 PDC to Samba-3 PDC"
+HREF="nt4migration.html"><LINK
 REL="NEXT"
 TITLE="Samba and other CIFS clients"
 HREF="other-clients.html"></HEAD
@@ -45,7 +45,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="speed.html"
+HREF="nt4migration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -75,6 +75,45 @@ CLASS="CHAPTER"
 NAME="PORTABILITY"
 ></A
 >Chapter 29. Portability</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>29.1. <A
+HREF="portability.html#AEN4423"
+>HPUX</A
+></DT
+><DT
+>29.2. <A
+HREF="portability.html#AEN4429"
+>SCO Unix</A
+></DT
+><DT
+>29.3. <A
+HREF="portability.html#AEN4433"
+>DNIX</A
+></DT
+><DT
+>29.4. <A
+HREF="portability.html#AEN4462"
+>RedHat Linux Rembrandt-II</A
+></DT
+><DT
+>29.5. <A
+HREF="portability.html#AEN4468"
+>AIX</A
+></DT
+><DT
+>29.6. <A
+HREF="portability.html#AEN4474"
+>Solaris</A
+></DT
+></DL
+></DIV
 ><P
 >Samba works on a wide range of platforms but the interface all the 
 platforms provide is not always compatible. This chapter contains 
@@ -84,7 +123,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4249"
+NAME="AEN4423"
 >29.1. HPUX</A
 ></H1
 ><P
@@ -114,7 +153,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4255"
+NAME="AEN4429"
 >29.2. SCO Unix</A
 ></H1
 ><P
@@ -131,7 +170,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4259"
+NAME="AEN4433"
 >29.3. DNIX</A
 ></H1
 ><P
@@ -238,7 +277,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4288"
+NAME="AEN4462"
 >29.4. RedHat Linux Rembrandt-II</A
 ></H1
 ><P
@@ -262,7 +301,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4294"
+NAME="AEN4468"
 >29.5. AIX</A
 ></H1
 ><DIV
@@ -270,7 +309,7 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN4296"
+NAME="AEN4470"
 >29.5.1. Sequential Read Ahead</A
 ></H2
 ><P
@@ -286,7 +325,7 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4300"
+NAME="AEN4474"
 >29.6. Solaris</A
 ></H1
 ><P
@@ -328,7 +367,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="speed.html"
+HREF="nt4migration.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -356,7 +395,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Samba performance issues</TD
+>Migration from NT4 PDC to Samba-3 PDC</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html
index a123992b36..0cc1b0a8f8 100644
--- a/docs/htmldocs/printing.html
+++ b/docs/htmldocs/printing.html
@@ -74,14 +74,145 @@ CLASS="CHAPTER"
 ><A
 NAME="PRINTING"
 ></A
->Chapter 12. Printing Support</H1
+>Chapter 13. Printing Support</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>13.1. <A
+HREF="printing.html#AEN1745"
+>Introduction</A
+></DT
+><DT
+>13.2. <A
+HREF="printing.html#AEN1767"
+>Configuration</A
+></DT
+><DD
+><DL
+><DT
+>13.2.1. <A
+HREF="printing.html#AEN1775"
+>Creating [print$]</A
+></DT
+><DT
+>13.2.2. <A
+HREF="printing.html#AEN1810"
+>Setting Drivers for Existing Printers</A
+></DT
+><DT
+>13.2.3. <A
+HREF="printing.html#AEN1826"
+>Support a large number of printers</A
+></DT
+><DT
+>13.2.4. <A
+HREF="printing.html#AEN1841"
+>Adding New Printers via the Windows NT APW</A
+></DT
+><DT
+>13.2.5. <A
+HREF="printing.html#AEN1871"
+>Samba and Printer Ports</A
+></DT
+></DL
+></DD
+><DT
+>13.3. <A
+HREF="printing.html#AEN1879"
+>The Imprints Toolset</A
+></DT
+><DD
+><DL
+><DT
+>13.3.1. <A
+HREF="printing.html#AEN1883"
+>What is Imprints?</A
+></DT
+><DT
+>13.3.2. <A
+HREF="printing.html#AEN1893"
+>Creating Printer Driver Packages</A
+></DT
+><DT
+>13.3.3. <A
+HREF="printing.html#AEN1896"
+>The Imprints server</A
+></DT
+><DT
+>13.3.4. <A
+HREF="printing.html#AEN1900"
+>The Installation Client</A
+></DT
+></DL
+></DD
+><DT
+>13.4. <A
+HREF="printing.html#AEN1922"
+>Diagnosis</A
+></DT
+><DD
+><DL
+><DT
+>13.4.1. <A
+HREF="printing.html#AEN1924"
+>Introduction</A
+></DT
+><DT
+>13.4.2. <A
+HREF="printing.html#AEN1940"
+>Debugging printer problems</A
+></DT
+><DT
+>13.4.3. <A
+HREF="printing.html#AEN1949"
+>What printers do I have?</A
+></DT
+><DT
+>13.4.4. <A
+HREF="printing.html#AEN1957"
+>Setting up printcap and print servers</A
+></DT
+><DT
+>13.4.5. <A
+HREF="printing.html#AEN1985"
+>Job sent, no output</A
+></DT
+><DT
+>13.4.6. <A
+HREF="printing.html#AEN1996"
+>Job sent, strange output</A
+></DT
+><DT
+>13.4.7. <A
+HREF="printing.html#AEN2008"
+>Raw PostScript printed</A
+></DT
+><DT
+>13.4.8. <A
+HREF="printing.html#AEN2011"
+>Advanced Printing</A
+></DT
+><DT
+>13.4.9. <A
+HREF="printing.html#AEN2014"
+>Real debugging</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1736"
->12.1. Introduction</A
+NAME="AEN1745"
+>13.1. Introduction</A
 ></H1
 ><P
 >Beginning with the 2.2.0 release, Samba supports 
@@ -163,8 +294,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1758"
->12.2. Configuration</A
+NAME="AEN1767"
+>13.2. Configuration</A
 ></H1
 ><DIV
 CLASS="WARNING"
@@ -225,8 +356,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1766"
->12.2.1. Creating [print$]</A
+NAME="AEN1775"
+>13.2.1. Creating [print$]</A
 ></H2
 ><P
 >In order to support the uploading of printer driver 
@@ -442,8 +573,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1801"
->12.2.2. Setting Drivers for Existing Printers</A
+NAME="AEN1810"
+>13.2.2. Setting Drivers for Existing Printers</A
 ></H2
 ><P
 >The initial listing of printers in the Samba host's 
@@ -514,8 +645,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1817"
->12.2.3. Support a large number of printers</A
+NAME="AEN1826"
+>13.2.3. Support a large number of printers</A
 ></H2
 ><P
 >One issue that has arisen during the development
@@ -590,8 +721,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1832"
->12.2.4. Adding New Printers via the Windows NT APW</A
+NAME="AEN1841"
+>13.2.4. Adding New Printers via the Windows NT APW</A
 ></H2
 ><P
 >By default, Samba offers all printer shares defined in <TT
@@ -745,8 +876,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1862"
->12.2.5. Samba and Printer Ports</A
+NAME="AEN1871"
+>13.2.5. Samba and Printer Ports</A
 ></H2
 ><P
 >Windows NT/2000 print servers associate a port with each printer.  These normally
@@ -780,8 +911,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1870"
->12.3. The Imprints Toolset</A
+NAME="AEN1879"
+>13.3. The Imprints Toolset</A
 ></H1
 ><P
 >The Imprints tool set provides a UNIX equivalent of the 
@@ -798,8 +929,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1874"
->12.3.1. What is Imprints?</A
+NAME="AEN1883"
+>13.3.1. What is Imprints?</A
 ></H2
 ><P
 >Imprints is a collection of tools for supporting the goals 
@@ -830,8 +961,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1884"
->12.3.2. Creating Printer Driver Packages</A
+NAME="AEN1893"
+>13.3.2. Creating Printer Driver Packages</A
 ></H2
 ><P
 >The process of creating printer driver packages is beyond
@@ -846,8 +977,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1887"
->12.3.3. The Imprints server</A
+NAME="AEN1896"
+>13.3.3. The Imprints server</A
 ></H2
 ><P
 >The Imprints server is really a database server that 
@@ -870,8 +1001,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1891"
->12.3.4. The Installation Client</A
+NAME="AEN1900"
+>13.3.4. The Installation Client</A
 ></H2
 ><P
 >More information regarding the Imprints installation client 
@@ -964,16 +1095,16 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1913"
->12.4. Diagnosis</A
+NAME="AEN1922"
+>13.4. Diagnosis</A
 ></H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1915"
->12.4.1. Introduction</A
+NAME="AEN1924"
+>13.4.1. Introduction</A
 ></H2
 ><P
 >This is a short description of how to debug printing problems with
@@ -1047,8 +1178,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1931"
->12.4.2. Debugging printer problems</A
+NAME="AEN1940"
+>13.4.2. Debugging printer problems</A
 ></H2
 ><P
 >One way to debug printing problems is to start by replacing these
@@ -1104,8 +1235,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1940"
->12.4.3. What printers do I have?</A
+NAME="AEN1949"
+>13.4.3. What printers do I have?</A
 ></H2
 ><P
 >You can use the 'testprns' program to check to see if the printer
@@ -1133,8 +1264,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1948"
->12.4.4. Setting up printcap and print servers</A
+NAME="AEN1957"
+>13.4.4. Setting up printcap and print servers</A
 ></H2
 ><P
 >You may need to set up some printcaps for your Samba system to use.
@@ -1217,8 +1348,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1976"
->12.4.5. Job sent, no output</A
+NAME="AEN1985"
+>13.4.5. Job sent, no output</A
 ></H2
 ><P
 >This is the most frustrating part of printing.  You may have sent the
@@ -1262,8 +1393,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1987"
->12.4.6. Job sent, strange output</A
+NAME="AEN1996"
+>13.4.6. Job sent, strange output</A
 ></H2
 ><P
 >Once you have the job printing, you can then start worrying about
@@ -1308,8 +1439,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1999"
->12.4.7. Raw PostScript printed</A
+NAME="AEN2008"
+>13.4.7. Raw PostScript printed</A
 ></H2
 ><P
 >This is a problem that is usually caused by either the print spooling
@@ -1323,8 +1454,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2002"
->12.4.8. Advanced Printing</A
+NAME="AEN2011"
+>13.4.8. Advanced Printing</A
 ></H2
 ><P
 >Note that you can do some pretty magic things by using your
@@ -1339,8 +1470,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2005"
->12.4.9. Real debugging</A
+NAME="AEN2014"
+>13.4.9. Real debugging</A
 ></H2
 ><P
 >If the above debug tips don't help, then maybe you need to bring in
diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html
index 69787dbeaf..618889cab2 100644
--- a/docs/htmldocs/samba-bdc.html
+++ b/docs/htmldocs/samba-bdc.html
@@ -74,14 +74,76 @@ CLASS="CHAPTER"
 ><A
 NAME="SAMBA-BDC"
 ></A
->Chapter 7. Samba Backup Domain Controller to Samba Domain Control</H1
+>Chapter 8. Samba Backup Domain Controller to Samba Domain Control</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>8.1. <A
+HREF="samba-bdc.html#AEN1294"
+>Prerequisite Reading</A
+></DT
+><DT
+>8.2. <A
+HREF="samba-bdc.html#AEN1298"
+>Background</A
+></DT
+><DT
+>8.3. <A
+HREF="samba-bdc.html#AEN1306"
+>What qualifies a Domain Controller on the network?</A
+></DT
+><DD
+><DL
+><DT
+>8.3.1. <A
+HREF="samba-bdc.html#AEN1309"
+>How does a Workstation find its domain controller?</A
+></DT
+><DT
+>8.3.2. <A
+HREF="samba-bdc.html#AEN1312"
+>When is the PDC needed?</A
+></DT
+></DL
+></DD
+><DT
+>8.4. <A
+HREF="samba-bdc.html#AEN1315"
+>Can Samba be a Backup Domain Controller to an NT PDC?</A
+></DT
+><DT
+>8.5. <A
+HREF="samba-bdc.html#AEN1320"
+>How do I set up a Samba BDC?</A
+></DT
+><DD
+><DL
+><DT
+>8.5.1. <A
+HREF="samba-bdc.html#AEN1337"
+>How do I replicate the smbpasswd file?</A
+></DT
+><DT
+>8.5.2. <A
+HREF="samba-bdc.html#AEN1341"
+>Can I do this all with LDAP?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1286"
->7.1. Prerequisite Reading</A
+NAME="AEN1294"
+>8.1. Prerequisite Reading</A
 ></H1
 ><P
 >Before you continue reading in this chapter, please make sure
@@ -97,8 +159,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1290"
->7.2. Background</A
+NAME="AEN1298"
+>8.2. Background</A
 ></H1
 ><P
 >What is a Domain Controller? It is a machine that is able to answer
@@ -142,8 +204,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1298"
->7.3. What qualifies a Domain Controller on the network?</A
+NAME="AEN1306"
+>8.3. What qualifies a Domain Controller on the network?</A
 ></H1
 ><P
 >Every machine that is a Domain Controller for the domain SAMBA has to
@@ -159,8 +221,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1301"
->7.3.1. How does a Workstation find its domain controller?</A
+NAME="AEN1309"
+>8.3.1. How does a Workstation find its domain controller?</A
 ></H2
 ><P
 >A NT workstation in the domain SAMBA that wants a local user to be
@@ -178,8 +240,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1304"
->7.3.2. When is the PDC needed?</A
+NAME="AEN1312"
+>8.3.2. When is the PDC needed?</A
 ></H2
 ><P
 >Whenever a user wants to change his password, this has to be done on
@@ -194,8 +256,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1307"
->7.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
+NAME="AEN1315"
+>8.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
 ></H1
 ><P
 >With version 2.2, no. The native NT SAM replication protocols have
@@ -217,8 +279,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1312"
->7.5. How do I set up a Samba BDC?</A
+NAME="AEN1320"
+>8.5. How do I set up a Samba BDC?</A
 ></H1
 ><P
 >Several things have to be done:</P
@@ -284,8 +346,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1329"
->7.5.1. How do I replicate the smbpasswd file?</A
+NAME="AEN1337"
+>8.5.1. How do I replicate the smbpasswd file?</A
 ></H2
 ><P
 >Replication of the smbpasswd file is sensitive. It has to be done
@@ -305,8 +367,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1333"
->7.5.2. Can I do this all with LDAP?</A
+NAME="AEN1341"
+>8.5.2. Can I do this all with LDAP?</A
 ></H2
 ><P
 >The simple answer is YES.  Samba's pdb_ldap code supports
diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html
index fae541f90f..1111d86de1 100644
--- a/docs/htmldocs/samba-howto-collection.html
+++ b/docs/htmldocs/samba-howto-collection.html
@@ -55,10 +55,10 @@ CLASS="EDITEDBY"
 >Edited by</H4
 ><H3
 CLASS="EDITOR"
->John H Terpstra</H3
+>Jelmer R. Vernooij</H3
 ><H3
 CLASS="EDITOR"
->Jelmer Vernooij</H3
+>John H. Terpstra</H3
 ><H3
 CLASS="EDITOR"
 >Gerald (Jerry) Carter</H3
@@ -68,7 +68,7 @@ CLASS="ABSTRACT"
 ><P
 ></P
 ><A
-NAME="AEN32"
+NAME="AEN34"
 ></A
 ><P
 >This book is a collection of HOWTOs added to Samba documentation over the years.
@@ -98,7 +98,7 @@ CLASS="LEGALNOTICE"
 ><P
 ></P
 ><A
-NAME="AEN37"
+NAME="AEN39"
 ></A
 ><P
 >This documentation is distributed under the GNU General Public License (GPL) 
@@ -128,141 +128,185 @@ HREF="introduction.html"
 ><DL
 ><DT
 >1. <A
+HREF="introsmb.html"
+>Introduction to Samba</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="introsmb.html#AEN61"
+>Background</A
+></DT
+><DT
+>1.2. <A
+HREF="introsmb.html#AEN67"
+>Terminology</A
+></DT
+><DT
+>1.3. <A
+HREF="introsmb.html#AEN91"
+>Related Projects</A
+></DT
+><DT
+>1.4. <A
+HREF="introsmb.html#AEN100"
+>SMB Methodology</A
+></DT
+><DT
+>1.5. <A
+HREF="introsmb.html#AEN115"
+>Additional Resources</A
+></DT
+><DT
+>1.6. <A
+HREF="introsmb.html#AEN151"
+>Epilogue</A
+></DT
+><DT
+>1.7. <A
+HREF="introsmb.html#AEN162"
+>Miscellaneous</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
 HREF="install.html"
 >How to Install and Test SAMBA</A
 ></DT
 ><DD
 ><DL
 ><DT
->1.1. <A
-HREF="install.html#AEN65"
+>2.1. <A
+HREF="install.html#AEN188"
 >Obtaining and installing samba</A
 ></DT
 ><DT
->1.2. <A
-HREF="install.html#AEN71"
+>2.2. <A
+HREF="install.html#AEN194"
 >Configuring samba</A
 ></DT
 ><DT
->1.3. <A
-HREF="install.html#AEN107"
+>2.3. <A
+HREF="install.html#AEN230"
 >Try listing the shares available on your 
 	server</A
 ></DT
 ><DT
->1.4. <A
-HREF="install.html#AEN116"
+>2.4. <A
+HREF="install.html#AEN239"
 >Try connecting with the unix client</A
 ></DT
 ><DT
->1.5. <A
-HREF="install.html#AEN137"
+>2.5. <A
+HREF="install.html#AEN260"
 >Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client</A
 ></DT
 ><DT
->1.6. <A
-HREF="install.html#AEN150"
+>2.6. <A
+HREF="install.html#AEN273"
 >What If Things Don't Work?</A
 ></DT
 ></DL
 ></DD
 ><DT
->2. <A
+>3. <A
 HREF="browsing-quick.html"
 >Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
 ></DT
 ><DD
 ><DL
 ><DT
->2.1. <A
-HREF="browsing-quick.html#AEN183"
+>3.1. <A
+HREF="browsing-quick.html#AEN306"
 >Discussion</A
 ></DT
 ><DT
->2.2. <A
-HREF="browsing-quick.html#AEN204"
+>3.2. <A
+HREF="browsing-quick.html#AEN327"
 >How browsing functions and how to deploy stable and 
 dependable browsing using Samba</A
 ></DT
 ><DT
->2.3. <A
-HREF="browsing-quick.html#AEN218"
+>3.3. <A
+HREF="browsing-quick.html#AEN341"
 >Use of the <B
 CLASS="COMMAND"
 >Remote Announce</B
 > parameter</A
 ></DT
 ><DT
->2.4. <A
-HREF="browsing-quick.html#AEN241"
+>3.4. <A
+HREF="browsing-quick.html#AEN364"
 >Use of the <B
 CLASS="COMMAND"
 >Remote Browse Sync</B
 > parameter</A
 ></DT
 ><DT
->2.5. <A
-HREF="browsing-quick.html#AEN252"
+>3.5. <A
+HREF="browsing-quick.html#AEN375"
 >Use of WINS</A
 ></DT
 ><DT
->2.6. <A
-HREF="browsing-quick.html#AEN269"
+>3.6. <A
+HREF="browsing-quick.html#AEN401"
 >Do NOT use more than one (1) protocol on MS Windows machines</A
 ></DT
 ><DT
->2.7. <A
-HREF="browsing-quick.html#AEN277"
+>3.7. <A
+HREF="browsing-quick.html#AEN409"
 >Name Resolution Order</A
 ></DT
 ></DL
 ></DD
 ><DT
->3. <A
+>4. <A
 HREF="passdb.html"
 >User information database</A
 ></DT
 ><DD
 ><DL
 ><DT
->3.1. <A
-HREF="passdb.html#AEN335"
+>4.1. <A
+HREF="passdb.html#AEN469"
 >Introduction</A
 ></DT
 ><DT
->3.2. <A
-HREF="passdb.html#AEN342"
+>4.2. <A
+HREF="passdb.html#AEN476"
 >Important Notes About Security</A
 ></DT
 ><DT
->3.3. <A
-HREF="passdb.html#AEN380"
+>4.3. <A
+HREF="passdb.html#AEN514"
 >The smbpasswd Command</A
 ></DT
 ><DT
->3.4. <A
-HREF="passdb.html#AEN411"
+>4.4. <A
+HREF="passdb.html#AEN545"
 >Plain text</A
 ></DT
 ><DT
->3.5. <A
-HREF="passdb.html#AEN416"
+>4.5. <A
+HREF="passdb.html#AEN550"
 >TDB</A
 ></DT
 ><DT
->3.6. <A
-HREF="passdb.html#AEN419"
+>4.6. <A
+HREF="passdb.html#AEN553"
 >LDAP</A
 ></DT
 ><DT
->3.7. <A
-HREF="passdb.html#AEN637"
+>4.7. <A
+HREF="passdb.html#AEN766"
 >MySQL</A
 ></DT
 ><DT
->3.8. <A
-HREF="passdb.html#AEN679"
+>4.8. <A
+HREF="passdb.html#AEN808"
 >XML</A
 ></DT
 ></DL
@@ -277,156 +321,151 @@ HREF="type.html"
 ><DD
 ><DL
 ><DT
->4. <A
+>5. <A
 HREF="servertype.html"
 >Nomenclature of Server Types</A
 ></DT
 ><DD
 ><DL
 ><DT
->4.1. <A
-HREF="servertype.html#AEN717"
+>5.1. <A
+HREF="servertype.html#AEN847"
 >Stand Alone Server</A
 ></DT
 ><DT
->4.2. <A
-HREF="servertype.html#AEN724"
+>5.2. <A
+HREF="servertype.html#AEN854"
 >Domain Member Server</A
 ></DT
 ><DT
->4.3. <A
-HREF="servertype.html#AEN730"
+>5.3. <A
+HREF="servertype.html#AEN860"
 >Domain Controller</A
 ></DT
 ></DL
 ></DD
 ><DT
->5. <A
+>6. <A
 HREF="securitylevels.html"
 >Samba as Stand-Alone Server</A
 ></DT
 ><DD
 ><DL
 ><DT
->5.1. <A
-HREF="securitylevels.html#AEN766"
+>6.1. <A
+HREF="securitylevels.html#AEN897"
 >User and Share security level</A
 ></DT
 ></DL
 ></DD
 ><DT
->6. <A
+>7. <A
 HREF="samba-pdc.html"
 >Samba as an NT4 or Win2k Primary Domain Controller</A
 ></DT
 ><DD
 ><DL
 ><DT
->6.1. <A
-HREF="samba-pdc.html#AEN878"
+>7.1. <A
+HREF="samba-pdc.html#AEN1010"
 >Prerequisite Reading</A
 ></DT
 ><DT
->6.2. <A
-HREF="samba-pdc.html#AEN883"
+>7.2. <A
+HREF="samba-pdc.html#AEN1014"
 >Background</A
 ></DT
 ><DT
->6.3. <A
-HREF="samba-pdc.html#AEN923"
+>7.3. <A
+HREF="samba-pdc.html#AEN1054"
 >Configuring the Samba Domain Controller</A
 ></DT
 ><DT
->6.4. <A
-HREF="samba-pdc.html#AEN965"
+>7.4. <A
+HREF="samba-pdc.html#AEN1096"
 >Creating Machine Trust Accounts and Joining Clients to the Domain</A
 ></DT
 ><DT
->6.5. <A
-HREF="samba-pdc.html#AEN1073"
+>7.5. <A
+HREF="samba-pdc.html#AEN1212"
 >Common Problems and Errors</A
 ></DT
 ><DT
->6.6. <A
-HREF="samba-pdc.html#AEN1119"
->What other help can I get?</A
-></DT
-><DT
->6.7. <A
-HREF="samba-pdc.html#AEN1233"
+>7.6. <A
+HREF="samba-pdc.html#AEN1241"
 >Domain Control for Windows 9x/ME</A
 ></DT
 ></DL
 ></DD
 ><DT
->7. <A
+>8. <A
 HREF="samba-bdc.html"
 >Samba Backup Domain Controller to Samba Domain Control</A
 ></DT
 ><DD
 ><DL
 ><DT
->7.1. <A
-HREF="samba-bdc.html#AEN1286"
+>8.1. <A
+HREF="samba-bdc.html#AEN1294"
 >Prerequisite Reading</A
 ></DT
 ><DT
->7.2. <A
-HREF="samba-bdc.html#AEN1290"
+>8.2. <A
+HREF="samba-bdc.html#AEN1298"
 >Background</A
 ></DT
 ><DT
->7.3. <A
-HREF="samba-bdc.html#AEN1298"
+>8.3. <A
+HREF="samba-bdc.html#AEN1306"
 >What qualifies a Domain Controller on the network?</A
 ></DT
 ><DT
->7.4. <A
-HREF="samba-bdc.html#AEN1307"
+>8.4. <A
+HREF="samba-bdc.html#AEN1315"
 >Can Samba be a Backup Domain Controller to an NT PDC?</A
 ></DT
 ><DT
->7.5. <A
-HREF="samba-bdc.html#AEN1312"
+>8.5. <A
+HREF="samba-bdc.html#AEN1320"
 >How do I set up a Samba BDC?</A
 ></DT
 ></DL
 ></DD
 ><DT
->8. <A
+>9. <A
 HREF="ads.html"
 >Samba as a ADS domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->8.1. <A
-HREF="ads.html#AEN1355"
+>9.1. <A
+HREF="ads.html#AEN1364"
 >Setup your <TT
 CLASS="FILENAME"
 >smb.conf</TT
 ></A
 ></DT
 ><DT
->8.2. <A
-HREF="ads.html#AEN1368"
+>9.2. <A
+HREF="ads.html#AEN1377"
 >Setup your <TT
 CLASS="FILENAME"
 >/etc/krb5.conf</TT
 ></A
 ></DT
 ><DT
->8.3. <A
+>9.3. <A
 HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
 >Create the computer account</A
 ></DT
 ><DT
->8.4. <A
+>9.4. <A
 HREF="ads.html#ADS-TEST-SERVER"
 >Test your server setup</A
 ></DT
 ><DT
->8.5. <A
+>9.5. <A
 HREF="ads.html#ADS-TEST-SMBCLIENT"
 >Testing with <SPAN
 CLASS="APPLICATION"
@@ -434,27 +473,27 @@ CLASS="APPLICATION"
 ></A
 ></DT
 ><DT
->8.6. <A
-HREF="ads.html#AEN1416"
+>9.6. <A
+HREF="ads.html#AEN1425"
 >Notes</A
 ></DT
 ></DL
 ></DD
 ><DT
->9. <A
-HREF="domain-security.html"
+>10. <A
+HREF="domain-member.html"
 >Samba as a NT4 or Win2k domain member</A
 ></DT
 ><DD
 ><DL
 ><DT
->9.1. <A
-HREF="domain-security.html#AEN1439"
+>10.1. <A
+HREF="domain-member.html#AEN1448"
 >Joining an NT Domain with Samba 3.0</A
 ></DT
 ><DT
->9.2. <A
-HREF="domain-security.html#AEN1493"
+>10.2. <A
+HREF="domain-member.html#AEN1502"
 >Why is this better than security = server?</A
 ></DT
 ></DL
@@ -469,500 +508,510 @@ HREF="optional.html"
 ><DD
 ><DL
 ><DT
->10. <A
+>11. <A
 HREF="unix-permissions.html"
 >UNIX Permission Bits and Windows NT Access Control Lists</A
 ></DT
 ><DD
 ><DL
 ><DT
->10.1. <A
-HREF="unix-permissions.html#AEN1525"
+>11.1. <A
+HREF="unix-permissions.html#AEN1534"
 >Viewing and changing UNIX permissions using the NT 
 	security dialogs</A
 ></DT
 ><DT
->10.2. <A
-HREF="unix-permissions.html#AEN1531"
+>11.2. <A
+HREF="unix-permissions.html#AEN1540"
 >How to view file security on a Samba share</A
 ></DT
 ><DT
->10.3. <A
-HREF="unix-permissions.html#AEN1542"
+>11.3. <A
+HREF="unix-permissions.html#AEN1551"
 >Viewing file ownership</A
 ></DT
 ><DT
->10.4. <A
-HREF="unix-permissions.html#AEN1562"
+>11.4. <A
+HREF="unix-permissions.html#AEN1571"
 >Viewing file or directory permissions</A
 ></DT
 ><DT
->10.5. <A
-HREF="unix-permissions.html#AEN1598"
+>11.5. <A
+HREF="unix-permissions.html#AEN1607"
 >Modifying file or directory permissions</A
 ></DT
 ><DT
->10.6. <A
-HREF="unix-permissions.html#AEN1620"
+>11.6. <A
+HREF="unix-permissions.html#AEN1629"
 >Interaction with the standard Samba create mask 
 	parameters</A
 ></DT
 ><DT
->10.7. <A
-HREF="unix-permissions.html#AEN1673"
+>11.7. <A
+HREF="unix-permissions.html#AEN1682"
 >Interaction with the standard Samba file attribute 
 	mapping</A
 ></DT
 ></DL
 ></DD
 ><DT
->11. <A
+>12. <A
 HREF="groupmapping.html"
 >Configuring Group Mapping</A
 ></DT
 ><DT
->12. <A
+>13. <A
 HREF="printing.html"
 >Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->12.1. <A
-HREF="printing.html#AEN1736"
+>13.1. <A
+HREF="printing.html#AEN1745"
 >Introduction</A
 ></DT
 ><DT
->12.2. <A
-HREF="printing.html#AEN1758"
+>13.2. <A
+HREF="printing.html#AEN1767"
 >Configuration</A
 ></DT
 ><DT
->12.3. <A
-HREF="printing.html#AEN1870"
+>13.3. <A
+HREF="printing.html#AEN1879"
 >The Imprints Toolset</A
 ></DT
 ><DT
->12.4. <A
-HREF="printing.html#AEN1913"
+>13.4. <A
+HREF="printing.html#AEN1922"
 >Diagnosis</A
 ></DT
 ></DL
 ></DD
 ><DT
->13. <A
+>14. <A
 HREF="cups-printing.html"
 >CUPS Printing Support</A
 ></DT
 ><DD
 ><DL
 ><DT
->13.1. <A
-HREF="cups-printing.html#AEN2025"
+>14.1. <A
+HREF="cups-printing.html#AEN2035"
 >Introduction</A
 ></DT
 ><DT
->13.2. <A
-HREF="cups-printing.html#AEN2032"
+>14.2. <A
+HREF="cups-printing.html#AEN2042"
 >Configuring <TT
 CLASS="FILENAME"
 >smb.conf</TT
 > for CUPS</A
 ></DT
 ><DT
->13.3. <A
-HREF="cups-printing.html#AEN2052"
+>14.3. <A
+HREF="cups-printing.html#AEN2062"
 >CUPS - RAW Print Through Mode</A
 ></DT
 ><DT
->13.4. <A
-HREF="cups-printing.html#AEN2111"
+>14.4. <A
+HREF="cups-printing.html#AEN2119"
 >CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients</A
 ></DT
 ><DT
->13.5. <A
-HREF="cups-printing.html#AEN2132"
+>14.5. <A
+HREF="cups-printing.html#AEN2140"
 >Windows Terminal Servers (WTS) as CUPS clients</A
 ></DT
 ><DT
->13.6. <A
-HREF="cups-printing.html#AEN2136"
+>14.6. <A
+HREF="cups-printing.html#AEN2144"
 >Setting up CUPS for driver download</A
 ></DT
 ><DT
->13.7. <A
-HREF="cups-printing.html#AEN2149"
+>14.7. <A
+HREF="cups-printing.html#AEN2157"
 >Sources of CUPS drivers / PPDs</A
 ></DT
 ><DT
->13.8. <A
-HREF="cups-printing.html#AEN2205"
+>14.8. <A
+HREF="cups-printing.html#AEN2213"
 >The CUPS Filter Chains</A
 ></DT
 ><DT
->13.9. <A
-HREF="cups-printing.html#AEN2244"
+>14.9. <A
+HREF="cups-printing.html#AEN2252"
 >CUPS Print Drivers and Devices</A
 ></DT
 ><DT
->13.10. <A
-HREF="cups-printing.html#AEN2321"
+>14.10. <A
+HREF="cups-printing.html#AEN2329"
 >Limiting the number of pages users can print</A
 ></DT
 ><DT
->13.11. <A
-HREF="cups-printing.html#AEN2417"
+>14.11. <A
+HREF="cups-printing.html#AEN2425"
 >Advanced Postscript Printing from MS Windows</A
 ></DT
 ><DT
->13.12. <A
-HREF="cups-printing.html#AEN2432"
+>14.12. <A
+HREF="cups-printing.html#AEN2440"
 >Auto-Deletion of CUPS spool files</A
 ></DT
 ></DL
 ></DD
 ><DT
->14. <A
+>15. <A
 HREF="winbind.html"
 >Unified Logons between Windows NT and UNIX using Winbind</A
 ></DT
 ><DD
 ><DL
 ><DT
->14.1. <A
-HREF="winbind.html#AEN2506"
+>15.1. <A
+HREF="winbind.html#AEN2516"
 >Abstract</A
 ></DT
 ><DT
->14.2. <A
-HREF="winbind.html#AEN2510"
+>15.2. <A
+HREF="winbind.html#AEN2520"
 >Introduction</A
 ></DT
 ><DT
->14.3. <A
-HREF="winbind.html#AEN2523"
+>15.3. <A
+HREF="winbind.html#AEN2533"
 >What Winbind Provides</A
 ></DT
 ><DT
->14.4. <A
-HREF="winbind.html#AEN2534"
+>15.4. <A
+HREF="winbind.html#AEN2544"
 >How Winbind Works</A
 ></DT
 ><DT
->14.5. <A
-HREF="winbind.html#AEN2577"
+>15.5. <A
+HREF="winbind.html#AEN2587"
 >Installation and Configuration</A
 ></DT
 ><DT
->14.6. <A
-HREF="winbind.html#AEN2834"
+>15.6. <A
+HREF="winbind.html#AEN2844"
 >Limitations</A
 ></DT
 ><DT
->14.7. <A
-HREF="winbind.html#AEN2844"
+>15.7. <A
+HREF="winbind.html#AEN2854"
 >Conclusion</A
 ></DT
 ></DL
 ></DD
 ><DT
->15. <A
+>16. <A
 HREF="advancednetworkmanagement.html"
 >Advanced Network Manangement</A
 ></DT
 ><DD
 ><DL
 ><DT
->15.1. <A
-HREF="advancednetworkmanagement.html#AEN2859"
+>16.1. <A
+HREF="advancednetworkmanagement.html#AEN2870"
 >Configuring Samba Share Access Controls</A
 ></DT
 ><DT
->15.2. <A
-HREF="advancednetworkmanagement.html#AEN2897"
+>16.2. <A
+HREF="advancednetworkmanagement.html#AEN2908"
 >Remote Server Administration</A
 ></DT
 ><DT
->15.3. <A
-HREF="advancednetworkmanagement.html#AEN2914"
+>16.3. <A
+HREF="advancednetworkmanagement.html#AEN2925"
 >Network Logon Script Magic</A
 ></DT
 ></DL
 ></DD
 ><DT
->16. <A
+>17. <A
 HREF="policymgmt.html"
 >System and Account Policies</A
 ></DT
 ><DD
 ><DL
 ><DT
->16.1. <A
-HREF="policymgmt.html#AEN2929"
+>17.1. <A
+HREF="policymgmt.html#AEN2959"
 >Creating and Managing System Policies</A
 ></DT
 ><DT
->16.2. <A
-HREF="policymgmt.html#AEN3002"
+>17.2. <A
+HREF="policymgmt.html#AEN3031"
 >Managing Account/User Policies</A
 ></DT
+><DT
+>17.3. <A
+HREF="policymgmt.html#AEN3053"
+>System Startup and Logon Processing Overview</A
+></DT
 ></DL
 ></DD
 ><DT
->17. <A
+>18. <A
 HREF="profilemgmt.html"
 >Desktop Profile Management</A
 ></DT
 ><DD
 ><DL
 ><DT
->17.1. <A
-HREF="profilemgmt.html#AEN3035"
+>18.1. <A
+HREF="profilemgmt.html#AEN3096"
 >Roaming Profiles</A
 ></DT
 ><DT
->17.2. <A
-HREF="profilemgmt.html#AEN3242"
+>18.2. <A
+HREF="profilemgmt.html#AEN3303"
 >Mandatory profiles</A
 ></DT
 ><DT
->17.3. <A
-HREF="profilemgmt.html#AEN3249"
+>18.3. <A
+HREF="profilemgmt.html#AEN3310"
 >Creating/Managing Group Profiles</A
 ></DT
 ><DT
->17.4. <A
-HREF="profilemgmt.html#AEN3255"
+>18.4. <A
+HREF="profilemgmt.html#AEN3316"
 >Default Profile for Windows Users</A
 ></DT
 ></DL
 ></DD
 ><DT
->18. <A
+>19. <A
 HREF="interdomaintrusts.html"
 >Interdomain Trust Relationships</A
 ></DT
 ><DD
 ><DL
 ><DT
->18.1. <A
-HREF="interdomaintrusts.html#AEN3386"
+>19.1. <A
+HREF="interdomaintrusts.html#AEN3447"
 >Trust Relationship Background</A
 ></DT
 ><DT
->18.2. <A
-HREF="interdomaintrusts.html#AEN3395"
->MS Windows NT4 Trust Configuration</A
+>19.2. <A
+HREF="interdomaintrusts.html#AEN3456"
+>Native MS Windows NT4 Trusts Configuration</A
 ></DT
 ><DT
->18.3. <A
-HREF="interdomaintrusts.html#AEN3405"
->Configuring Samba Domain Trusts</A
+>19.3. <A
+HREF="interdomaintrusts.html#AEN3465"
+>Configuring Samba NT-style Domain Trusts</A
 ></DT
 ></DL
 ></DD
 ><DT
->19. <A
+>20. <A
 HREF="pam.html"
 >PAM Configuration for Centrally Managed Authentication</A
 ></DT
 ><DD
 ><DL
 ><DT
->19.1. <A
-HREF="pam.html#AEN3440"
+>20.1. <A
+HREF="pam.html#AEN3508"
 >Samba and PAM</A
 ></DT
 ><DT
->19.2. <A
-HREF="pam.html#AEN3491"
+>20.2. <A
+HREF="pam.html#AEN3559"
 >Distributed Authentication</A
 ></DT
 ><DT
->19.3. <A
-HREF="pam.html#AEN3496"
+>20.3. <A
+HREF="pam.html#AEN3564"
 >PAM Configuration in smb.conf</A
 ></DT
 ></DL
 ></DD
 ><DT
->20. <A
+>21. <A
 HREF="vfs.html"
 >Stackable VFS modules</A
 ></DT
 ><DD
 ><DL
 ><DT
->20.1. <A
-HREF="vfs.html#AEN3531"
+>21.1. <A
+HREF="vfs.html#AEN3601"
 >Introduction and configuration</A
 ></DT
 ><DT
->20.2. <A
-HREF="vfs.html#AEN3540"
+>21.2. <A
+HREF="vfs.html#AEN3610"
 >Included modules</A
 ></DT
 ><DT
->20.3. <A
-HREF="vfs.html#AEN3598"
+>21.3. <A
+HREF="vfs.html#AEN3668"
 >VFS modules available elsewhere</A
 ></DT
 ></DL
 ></DD
 ><DT
->21. <A
+>22. <A
 HREF="msdfs.html"
 >Hosting a Microsoft Distributed File System tree on Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->21.1. <A
-HREF="msdfs.html#AEN3626"
+>22.1. <A
+HREF="msdfs.html#AEN3696"
 >Instructions</A
 ></DT
 ></DL
 ></DD
 ><DT
->22. <A
+>23. <A
 HREF="integrate-ms-networks.html"
 >Integrating MS Windows networks with Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->22.1. <A
-HREF="integrate-ms-networks.html#AEN3688"
+>23.1. <A
+HREF="integrate-ms-networks.html#AEN3759"
 >Name Resolution in a pure Unix/Linux world</A
 ></DT
 ><DT
->22.2. <A
-HREF="integrate-ms-networks.html#AEN3751"
+>23.2. <A
+HREF="integrate-ms-networks.html#AEN3822"
 >Name resolution as used within MS Windows networking</A
 ></DT
 ></DL
 ></DD
 ><DT
->23. <A
+>24. <A
 HREF="improved-browsing.html"
 >Improved browsing in samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->23.1. <A
-HREF="improved-browsing.html#AEN3804"
+>24.1. <A
+HREF="improved-browsing.html#AEN3875"
 >Overview of browsing</A
 ></DT
 ><DT
->23.2. <A
-HREF="improved-browsing.html#AEN3810"
+>24.2. <A
+HREF="improved-browsing.html#AEN3881"
 >Browsing support in samba</A
 ></DT
 ><DT
->23.3. <A
-HREF="improved-browsing.html#AEN3825"
+>24.3. <A
+HREF="improved-browsing.html#AEN3896"
 >Problem resolution</A
 ></DT
 ><DT
->23.4. <A
-HREF="improved-browsing.html#AEN3837"
+>24.4. <A
+HREF="improved-browsing.html#AEN3908"
 >Browsing across subnets</A
 ></DT
 ><DT
->23.5. <A
-HREF="improved-browsing.html#AEN3878"
+>24.5. <A
+HREF="improved-browsing.html#AEN3949"
 >Setting up a WINS server</A
 ></DT
 ><DT
->23.6. <A
-HREF="improved-browsing.html#AEN3901"
+>24.6. <A
+HREF="improved-browsing.html#AEN3972"
 >Setting up Browsing in a WORKGROUP</A
 ></DT
 ><DT
->23.7. <A
-HREF="improved-browsing.html#AEN3927"
+>24.7. <A
+HREF="improved-browsing.html#AEN3998"
 >Setting up Browsing in a DOMAIN</A
 ></DT
 ><DT
->23.8. <A
+>24.8. <A
 HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
 >Forcing samba to be the master</A
 ></DT
 ><DT
->23.9. <A
-HREF="improved-browsing.html#AEN3962"
+>24.9. <A
+HREF="improved-browsing.html#AEN4033"
 >Making samba the domain master</A
 ></DT
 ><DT
->23.10. <A
-HREF="improved-browsing.html#AEN3984"
+>24.10. <A
+HREF="improved-browsing.html#AEN4055"
 >Note about broadcast addresses</A
 ></DT
 ><DT
->23.11. <A
-HREF="improved-browsing.html#AEN3987"
+>24.11. <A
+HREF="improved-browsing.html#AEN4058"
 >Multiple interfaces</A
 ></DT
 ></DL
 ></DD
 ><DT
->24. <A
+>25. <A
 HREF="securing-samba.html"
 >Securing Samba</A
 ></DT
 ><DD
 ><DL
 ><DT
->24.1. <A
-HREF="securing-samba.html#AEN4003"
+>25.1. <A
+HREF="securing-samba.html#AEN4074"
 >Introduction</A
 ></DT
 ><DT
->24.2. <A
-HREF="securing-samba.html#AEN4006"
+>25.2. <A
+HREF="securing-samba.html#AEN4077"
 >Using host based protection</A
 ></DT
 ><DT
->24.3. <A
-HREF="securing-samba.html#AEN4016"
+>25.3. <A
+HREF="securing-samba.html#AEN4087"
 >Using interface protection</A
 ></DT
 ><DT
->24.4. <A
-HREF="securing-samba.html#AEN4025"
+>25.4. <A
+HREF="securing-samba.html#AEN4095"
 >Using a firewall</A
 ></DT
 ><DT
->24.5. <A
-HREF="securing-samba.html#AEN4032"
+>25.5. <A
+HREF="securing-samba.html#AEN4102"
 >Using a IPC$ share deny</A
 ></DT
 ><DT
->24.6. <A
-HREF="securing-samba.html#AEN4041"
+>25.6. <A
+HREF="securing-samba.html#AEN4111"
 >Upgrading Samba</A
 ></DT
 ></DL
 ></DD
 ><DT
->25. <A
+>26. <A
 HREF="unicode.html"
 >Unicode/Charsets</A
 ></DT
 ><DD
 ><DL
 ><DT
->25.1. <A
-HREF="unicode.html#AEN4056"
+>26.1. <A
+HREF="unicode.html#AEN4127"
 >What are charsets and unicode?</A
 ></DT
 ><DT
->25.2. <A
-HREF="unicode.html#AEN4065"
+>26.2. <A
+HREF="unicode.html#AEN4136"
 >Samba and charsets</A
 ></DT
+><DT
+>26.3. <A
+HREF="unicode.html#AEN4155"
+>Conversion from old names</A
+></DT
 ></DL
 ></DD
 ></DL
@@ -975,94 +1024,55 @@ HREF="appendixes.html"
 ><DD
 ><DL
 ><DT
->26. <A
-HREF="swat.html"
->SWAT - The Samba Web Admininistration Tool</A
+>27. <A
+HREF="compiling.html"
+>How to compile SAMBA</A
 ></DT
 ><DD
 ><DL
 ><DT
->26.1. <A
-HREF="swat.html#AEN4098"
->SWAT Features and Benefits</A
+>27.1. <A
+HREF="compiling.html#AEN4183"
+>Access Samba source code via CVS</A
 ></DT
-></DL
-></DD
 ><DT
->27. <A
-HREF="nt4migration.html"
->Migration from NT4 PDC to Samba-3 PDC</A
+>27.2. <A
+HREF="compiling.html#AEN4226"
+>Accessing the samba sources via rsync and ftp</A
 ></DT
-><DD
-><DL
 ><DT
->27.1. <A
-HREF="nt4migration.html#AEN4134"
->Planning and Getting Started</A
+>27.3. <A
+HREF="compiling.html#AEN4232"
+>Verifying Samba's PGP signature</A
 ></DT
 ><DT
->27.2. <A
-HREF="nt4migration.html#AEN4143"
->Managing Samba-3 Domain Control</A
+>27.4. <A
+HREF="compiling.html#AEN4244"
+>Building the Binaries</A
+></DT
+><DT
+>27.5. <A
+HREF="compiling.html#AEN4301"
+>Starting the smbd and nmbd</A
 ></DT
 ></DL
 ></DD
 ><DT
 >28. <A
-HREF="speed.html"
->Samba performance issues</A
+HREF="nt4migration.html"
+>Migration from NT4 PDC to Samba-3 PDC</A
 ></DT
 ><DD
 ><DL
 ><DT
 >28.1. <A
-HREF="speed.html#AEN4163"
->Comparisons</A
+HREF="nt4migration.html#AEN4375"
+>Planning and Getting Started</A
 ></DT
 ><DT
 >28.2. <A
-HREF="speed.html#AEN4169"
->Socket options</A
-></DT
-><DT
->28.3. <A
-HREF="speed.html#AEN4176"
->Read size</A
-></DT
-><DT
->28.4. <A
-HREF="speed.html#AEN4181"
->Max xmit</A
-></DT
-><DT
->28.5. <A
-HREF="speed.html#AEN4186"
->Log level</A
-></DT
-><DT
->28.6. <A
-HREF="speed.html#AEN4189"
->Read raw</A
-></DT
-><DT
->28.7. <A
-HREF="speed.html#AEN4194"
->Write raw</A
-></DT
-><DT
->28.8. <A
-HREF="speed.html#AEN4198"
->Slow Clients</A
-></DT
-><DT
->28.9. <A
-HREF="speed.html#AEN4202"
->Slow Logins</A
-></DT
-><DT
->28.10. <A
-HREF="speed.html#AEN4205"
->Client tuning</A
+HREF="nt4migration.html#AEN4408"
+>Managing Samba-3 Domain Control</A
 ></DT
 ></DL
 ></DD
@@ -1075,32 +1085,32 @@ HREF="portability.html"
 ><DL
 ><DT
 >29.1. <A
-HREF="portability.html#AEN4249"
+HREF="portability.html#AEN4423"
 >HPUX</A
 ></DT
 ><DT
 >29.2. <A
-HREF="portability.html#AEN4255"
+HREF="portability.html#AEN4429"
 >SCO Unix</A
 ></DT
 ><DT
 >29.3. <A
-HREF="portability.html#AEN4259"
+HREF="portability.html#AEN4433"
 >DNIX</A
 ></DT
 ><DT
 >29.4. <A
-HREF="portability.html#AEN4288"
+HREF="portability.html#AEN4462"
 >RedHat Linux Rembrandt-II</A
 ></DT
 ><DT
 >29.5. <A
-HREF="portability.html#AEN4294"
+HREF="portability.html#AEN4468"
 >AIX</A
 ></DT
 ><DT
 >29.6. <A
-HREF="portability.html#AEN4300"
+HREF="portability.html#AEN4474"
 >Solaris</A
 ></DT
 ></DL
@@ -1114,101 +1124,106 @@ HREF="other-clients.html"
 ><DL
 ><DT
 >30.1. <A
-HREF="other-clients.html#AEN4326"
+HREF="other-clients.html#AEN4501"
 >Macintosh clients?</A
 ></DT
 ><DT
 >30.2. <A
-HREF="other-clients.html#AEN4335"
+HREF="other-clients.html#AEN4510"
 >OS2 Client</A
 ></DT
 ><DT
 >30.3. <A
-HREF="other-clients.html#AEN4375"
+HREF="other-clients.html#AEN4550"
 >Windows for Workgroups</A
 ></DT
 ><DT
 >30.4. <A
-HREF="other-clients.html#AEN4399"
+HREF="other-clients.html#AEN4574"
 >Windows '95/'98</A
 ></DT
 ><DT
 >30.5. <A
-HREF="other-clients.html#AEN4415"
+HREF="other-clients.html#AEN4590"
 >Windows 2000 Service Pack 2</A
 ></DT
 ><DT
 >30.6. <A
-HREF="other-clients.html#AEN4432"
+HREF="other-clients.html#AEN4607"
 >Windows NT 3.1</A
 ></DT
 ></DL
 ></DD
 ><DT
 >31. <A
-HREF="compiling.html"
->How to compile SAMBA</A
+HREF="swat.html"
+>SWAT - The Samba Web Admininistration Tool</A
 ></DT
 ><DD
 ><DL
 ><DT
 >31.1. <A
-HREF="compiling.html#AEN4453"
->Access Samba source code via CVS</A
-></DT
-><DT
->31.2. <A
-HREF="compiling.html#AEN4496"
->Accessing the samba sources via rsync and ftp</A
-></DT
-><DT
->31.3. <A
-HREF="compiling.html#AEN4502"
->Building the Binaries</A
-></DT
-><DT
->31.4. <A
-HREF="compiling.html#AEN4559"
->Starting the smbd and nmbd</A
+HREF="swat.html#AEN4624"
+>SWAT Features and Benefits</A
 ></DT
 ></DL
 ></DD
 ><DT
 >32. <A
-HREF="bugreport.html"
->Reporting Bugs</A
+HREF="speed.html"
+>Samba performance issues</A
 ></DT
 ><DD
 ><DL
 ><DT
 >32.1. <A
-HREF="bugreport.html#AEN4634"
->Introduction</A
+HREF="speed.html#AEN4666"
+>Comparisons</A
 ></DT
 ><DT
 >32.2. <A
-HREF="bugreport.html#AEN4644"
->General info</A
+HREF="speed.html#AEN4672"
+>Socket options</A
 ></DT
 ><DT
 >32.3. <A
-HREF="bugreport.html#AEN4650"
->Debug levels</A
+HREF="speed.html#AEN4679"
+>Read size</A
 ></DT
 ><DT
 >32.4. <A
-HREF="bugreport.html#AEN4671"
->Internal errors</A
+HREF="speed.html#AEN4684"
+>Max xmit</A
 ></DT
 ><DT
 >32.5. <A
-HREF="bugreport.html#AEN4685"
->Attaching to a running process</A
+HREF="speed.html#AEN4689"
+>Log level</A
 ></DT
 ><DT
 >32.6. <A
-HREF="bugreport.html#AEN4693"
->Patches</A
+HREF="speed.html#AEN4692"
+>Read raw</A
+></DT
+><DT
+>32.7. <A
+HREF="speed.html#AEN4697"
+>Write raw</A
+></DT
+><DT
+>32.8. <A
+HREF="speed.html#AEN4701"
+>Slow Clients</A
+></DT
+><DT
+>32.9. <A
+HREF="speed.html#AEN4705"
+>Slow Logins</A
+></DT
+><DT
+>32.10. <A
+HREF="speed.html#AEN4708"
+>Client tuning</A
 ></DT
 ></DL
 ></DD
@@ -1221,26 +1236,99 @@ HREF="diagnosis.html"
 ><DL
 ><DT
 >33.1. <A
-HREF="diagnosis.html#AEN4716"
+HREF="diagnosis.html#AEN4760"
 >Introduction</A
 ></DT
 ><DT
 >33.2. <A
-HREF="diagnosis.html#AEN4721"
+HREF="diagnosis.html#AEN4765"
 >Assumptions</A
 ></DT
 ><DT
 >33.3. <A
-HREF="diagnosis.html#AEN4740"
+HREF="diagnosis.html#AEN4784"
 >The tests</A
 ></DT
 ><DT
 >33.4. <A
-HREF="diagnosis.html#AEN4907"
+HREF="diagnosis.html#AEN4951"
 >Still having troubles?</A
 ></DT
 ></DL
 ></DD
+><DT
+>34. <A
+HREF="problems.html"
+>Analysing and solving samba problems</A
+></DT
+><DD
+><DL
+><DT
+>34.1. <A
+HREF="problems.html#AEN4983"
+>Diagnostics tools</A
+></DT
+><DT
+>34.2. <A
+HREF="problems.html#AEN4998"
+>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
+></DT
+><DT
+>34.3. <A
+HREF="problems.html#AEN5027"
+>Useful URL's</A
+></DT
+><DT
+>34.4. <A
+HREF="problems.html#AEN5051"
+>Getting help from the mailing lists</A
+></DT
+><DT
+>34.5. <A
+HREF="problems.html#AEN5081"
+>How to get off the mailinglists</A
+></DT
+></DL
+></DD
+><DT
+>35. <A
+HREF="bugreport.html"
+>Reporting Bugs</A
+></DT
+><DD
+><DL
+><DT
+>35.1. <A
+HREF="bugreport.html#AEN5104"
+>Introduction</A
+></DT
+><DT
+>35.2. <A
+HREF="bugreport.html#AEN5114"
+>General info</A
+></DT
+><DT
+>35.3. <A
+HREF="bugreport.html#AEN5120"
+>Debug levels</A
+></DT
+><DT
+>35.4. <A
+HREF="bugreport.html#AEN5141"
+>Internal errors</A
+></DT
+><DT
+>35.5. <A
+HREF="bugreport.html#AEN5155"
+>Attaching to a running process</A
+></DT
+><DT
+>35.6. <A
+HREF="bugreport.html#AEN5163"
+>Patches</A
+></DT
+></DL
+></DD
 ></DL
 ></DD
 ></DL
diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html
index 0c1e085159..31e5468681 100644
--- a/docs/htmldocs/samba-pdc.html
+++ b/docs/htmldocs/samba-pdc.html
@@ -74,37 +74,123 @@ CLASS="CHAPTER"
 ><A
 NAME="SAMBA-PDC"
 ></A
->Chapter 6. Samba as an NT4 or Win2k Primary Domain Controller</H1
+>Chapter 7. Samba as an NT4 or Win2k Primary Domain Controller</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>7.1. <A
+HREF="samba-pdc.html#AEN1010"
+>Prerequisite Reading</A
+></DT
+><DT
+>7.2. <A
+HREF="samba-pdc.html#AEN1014"
+>Background</A
+></DT
+><DT
+>7.3. <A
+HREF="samba-pdc.html#AEN1054"
+>Configuring the Samba Domain Controller</A
+></DT
+><DT
+>7.4. <A
+HREF="samba-pdc.html#AEN1096"
+>Creating Machine Trust Accounts and Joining Clients to the Domain</A
+></DT
+><DD
+><DL
+><DT
+>7.4.1. <A
+HREF="samba-pdc.html#AEN1142"
+>Manual Creation of Machine Trust Accounts</A
+></DT
+><DT
+>7.4.2. <A
+HREF="samba-pdc.html#AEN1183"
+>"On-the-Fly" Creation of Machine Trust Accounts</A
+></DT
+><DT
+>7.4.3. <A
+HREF="samba-pdc.html#AEN1192"
+>Joining the Client to the Domain</A
+></DT
+></DL
+></DD
+><DT
+>7.5. <A
+HREF="samba-pdc.html#AEN1212"
+>Common Problems and Errors</A
+></DT
+><DD
+><DL
+><DT
+>7.5.1. <A
+HREF="samba-pdc.html#AEN1214"
+>I cannot include a '$' in a machine name</A
+></DT
+><DT
+>7.5.2. <A
+HREF="samba-pdc.html#AEN1220"
+>I get told "You already have a connection to the Domain...." 
+or "Cannot join domain, the credentials supplied conflict with an 
+existing set.." when creating a machine trust account.</A
+></DT
+><DT
+>7.5.3. <A
+HREF="samba-pdc.html#AEN1227"
+>The system can not log you on (C000019B)....</A
+></DT
+><DT
+>7.5.4. <A
+HREF="samba-pdc.html#AEN1231"
+>The machine trust account for this computer either does not 
+exist or is not accessible.</A
+></DT
+><DT
+>7.5.5. <A
+HREF="samba-pdc.html#AEN1237"
+>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+I get a message about my account being disabled.</A
+></DT
+></DL
+></DD
+><DT
+>7.6. <A
+HREF="samba-pdc.html#AEN1241"
+>Domain Control for Windows 9x/ME</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN878"
->6.1. Prerequisite Reading</A
+NAME="AEN1010"
+>7.1. Prerequisite Reading</A
 ></H1
 ><P
 >Before you continue reading in this chapter, please make sure 
 that you are comfortable with configuring basic files services
 in smb.conf and how to enable and administer password 
 encryption in Samba.  Theses two topics are covered in the
-<A
-HREF="smb.conf.5.html"
-TARGET="_top"
-><TT
+<TT
 CLASS="FILENAME"
->smb.conf(5)</TT
-></A
-> 
-manpage.</P
+>smb.conf</TT
+> manpage.</P
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN883"
->6.2. Background</A
+NAME="AEN1014"
+>7.2. Background</A
 ></H1
 ><P
 >This article outlines the steps necessary for configuring Samba as a PDC.
@@ -250,19 +336,17 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN923"
->6.3. Configuring the Samba Domain Controller</A
+NAME="AEN1054"
+>7.3. Configuring the Samba Domain Controller</A
 ></H1
 ><P
 >The first step in creating a working Samba PDC is to 
 understand the parameters necessary in smb.conf. Here we
 attempt to explain the parameters that are covered in
-<A
-HREF="smb.conf.5.html"
-TARGET="_top"
-> the smb.conf
-man page</A
->.</P
+the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> man page.</P
 ><P
 >Here is an example <TT
 CLASS="FILENAME"
@@ -414,7 +498,7 @@ TARGET="_top"
 >	Encrypted passwords must be enabled.  For more details on how 
 	to do this, refer to <A
 HREF="passdb.html"
->ENCRYPTION.html</A
+>the User Database chapter</A
 >.
 	</P
 ></LI
@@ -446,8 +530,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN965"
->6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A
+NAME="AEN1096"
+>7.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A
 ></H1
 ><P
 >A machine trust account is a Samba account that is used to
@@ -549,7 +633,10 @@ CLASS="EMPHASIS"
 	file allows the creation of arbitrary user and machine accounts without
 	requiring that account to be added to the system (/etc/passwd) file. It
 	too requires the specification of the "non unix account range" option
-	in the [globals] section of the smb.conf file.
+	in the [globals] section of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
 	</P
 ></LI
 ><LI
@@ -578,6 +665,12 @@ CLASS="EMPHASIS"
 ></LI
 ></UL
 ><P
+>Read the chapter about the <A
+HREF="passdb.html"
+>User Database</A
+> 
+for details.</P
+><P
 >A Samba PDC, however, stores each machine trust account in two parts,
 as follows:
 
@@ -632,8 +725,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1008"
->6.4.1. Manual Creation of Machine Trust Accounts</A
+NAME="AEN1142"
+>7.4.1. Manual Creation of Machine Trust Accounts</A
 ></H2
 ><P
 >The first step in manually creating a machine trust account is to
@@ -738,12 +831,12 @@ as shown here:</P
 ><SAMP
 CLASS="PROMPT"
 >root# </SAMP
-><B
-CLASS="COMMAND"
+><KBD
+CLASS="USERINPUT"
 >smbpasswd -a -m <VAR
 CLASS="REPLACEABLE"
 >machine_name</VAR
-></B
+></KBD
 ></P
 ><P
 >where <VAR
@@ -802,8 +895,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1049"
->6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
+NAME="AEN1183"
+>7.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
 ></H2
 ><P
 >The second (and recommended) way of creating machine trust accounts is
@@ -839,8 +932,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1058"
->6.4.3. Joining the Client to the Domain</A
+NAME="AEN1192"
+>7.4.3. Joining the Client to the Domain</A
 ></H2
 ><P
 >The procedure for joining a client to the domain varies with the
@@ -899,6 +992,22 @@ CLASS="EMPHASIS"
 	(i.e., you must supply a Samba administrative account when
 	prompted).</P
 ></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Samba</I
+></SPAN
+></P
+><P
+>Joining a samba client to a domain is documented in 
+	the <A
+HREF="domain-member.html"
+>Domain Member</A
+> chapter.</P
+></LI
 ></UL
 ></DIV
 ></DIV
@@ -907,627 +1016,141 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1073"
->6.5. Common Problems and Errors</A
+NAME="AEN1212"
+>7.5. Common Problems and Errors</A
 ></H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1214"
+>7.5.1. I cannot include a '$' in a machine name</A
+></H2
 ><P
-></P
-><P
-></P
-><UL
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->I cannot include a '$' in a machine name.</I
-></SPAN
->
-	</P
-><P
->	A 'machine name' in (typically) <TT
+>A 'machine name' in (typically) <TT
 CLASS="FILENAME"
 >/etc/passwd</TT
 > 	
-	of the machine name with a '$' appended. FreeBSD (and other BSD 
-	systems?) won't create a user with a '$' in their name.
-	</P
+of the machine name with a '$' appended. FreeBSD (and other BSD 
+systems?) won't create a user with a '$' in their name.</P
 ><P
->	The problem is only in the program used to make the entry, once 
-	made, it works perfectly. So create a user without the '$' and 
-	use <B
+>The problem is only in the program used to make the entry, once 
+made, it works perfectly. So create a user without the '$' and 
+use <B
 CLASS="COMMAND"
 >vipw</B
 > to edit the entry, adding the '$'. Or create 
-	the whole entry with vipw if you like, make sure you use a 
-	unique User ID !
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->I get told "You already have a connection to the Domain...." 
-	or "Cannot join domain, the credentials supplied conflict with an 
-	existing set.." when creating a machine trust account.</I
-></SPAN
->
-	</P
+the whole entry with vipw if you like, make sure you use a 
+unique User ID !</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1220"
+>7.5.2. I get told "You already have a connection to the Domain...." 
+or "Cannot join domain, the credentials supplied conflict with an 
+existing set.." when creating a machine trust account.</A
+></H2
 ><P
->	This happens if you try to create a machine trust account from the 
-	machine itself and already have a connection (e.g. mapped drive) 
-	to a share (or IPC$) on the Samba PDC.  The following command
-	will remove all network drive connections:
-	</P
+>This happens if you try to create a machine trust account from the 
+machine itself and already have a connection (e.g. mapped drive) 
+to a share (or IPC$) on the Samba PDC.  The following command
+will remove all network drive connections:</P
 ><P
->	<SAMP
+><SAMP
 CLASS="PROMPT"
 >C:\WINNT\&#62;</SAMP
 > <B
 CLASS="COMMAND"
 >net use * /d</B
->
-	</P
-><P
->	Further, if the machine is a already a 'member of a workgroup' that 
-	is the same name as the domain you are joining (bad idea) you will 
-	get this message.  Change the workgroup name to something else, it 
-	does not matter what, reboot, and try again.
-	</P
-></LI
-><LI
+></P
 ><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The system can not log you on (C000019B)....</I
-></SPAN
->
-	</P
+>Further, if the machine is a already a 'member of a workgroup' that 
+is the same name as the domain you are joining (bad idea) you will 
+get this message.  Change the workgroup name to something else, it 
+does not matter what, reboot, and try again.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1227"
+>7.5.3. The system can not log you on (C000019B)....</A
+></H2
 ><P
 >I joined the domain successfully but after upgrading 
-	to a newer version of the Samba code I get the message, "The system 
-	can not log you on (C000019B), Please try again or consult your 
-	system administrator" when attempting to logon.
-	</P
-><P
->	This occurs when the domain SID stored in the secrets.tdb database
-	is changed. The most common cause of a change in domain SID is when
-	the domain name and/or the server name (netbios name) is changed.
- 	The only way to correct the problem is to restore the original domain 
-	SID or remove the domain client from the domain and rejoin. The domain
-	SID may be reset using either the smbpasswd or rpcclient utilities.
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The machine trust account for this computer either does not 
-	exist or is not accessible.</I
-></SPAN
->
-	</P
+to a newer version of the Samba code I get the message, "The system 
+can not log you on (C000019B), Please try again or consult your 
+system administrator" when attempting to logon.</P
+><P
+>This occurs when the domain SID stored in the secrets.tdb database
+is changed. The most common cause of a change in domain SID is when
+the domain name and/or the server name (netbios name) is changed.
+The only way to correct the problem is to restore the original domain 
+SID or remove the domain client from the domain and rejoin. The domain
+SID may be reset using either the smbpasswd or rpcclient utilities.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1231"
+>7.5.4. The machine trust account for this computer either does not 
+exist or is not accessible.</A
+></H2
 ><P
->	When I try to join the domain I get the message "The machine account 
-	for this computer either does not exist or is not accessible". What's 
-	wrong?
-	</P
+>When I try to join the domain I get the message "The machine account 
+for this computer either does not exist or is not accessible". What's 
+wrong?</P
 ><P
->	This problem is caused by the PDC not having a suitable machine trust account. 
-	If you are using the <VAR
+>This problem is caused by the PDC not having a suitable machine trust account. 
+If you are using the <VAR
 CLASS="PARAMETER"
 >add user script</VAR
 > method to create 
-	accounts then this would indicate that it has not worked. Ensure the domain 
-	admin user system is working.
-	</P
-><P
->	Alternatively if you are creating account entries manually then they 
-	have not been created correctly. Make sure that you have the entry 
-	correct for the machine trust account in smbpasswd file on the Samba PDC. 
-	If you added the account using an editor rather than using the smbpasswd 
-	utility, make sure that the account name is the machine NetBIOS name 
-	with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
-	in both /etc/passwd and the smbpasswd file. Some people have reported 
-	that inconsistent subnet masks between the Samba server and the NT 
-	client have caused this problem.   Make sure that these are consistent 
-	for both client and server.
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-	I get a message about my account being disabled.</I
-></SPAN
->
-	</P
-><P
->	This problem is caused by a PAM related bug in Samba 2.2.0.  This bug is 
-	fixed in 2.2.1.  Other symptoms could be unaccessible shares on 
-	NT/W2K member servers in the domain or the following error in your smbd.log:
-	passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user%
-	</P
-><P
->	At first be ensure to enable the useraccounts with <B
-CLASS="COMMAND"
->smbpasswd -e 
-	%user%</B
->, this is normally done, when you create an account.
-	</P
-><P
->	In order to work around this problem in 2.2.0, configure the 
-	<VAR
-CLASS="PARAMETER"
->account</VAR
-> control flag in 
-	<TT
-CLASS="FILENAME"
->/etc/pam.d/samba</TT
-> file as follows:
-	</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->	account required        pam_permit.so
-	</PRE
-></P
-><P
->	If you want to remain backward compatibility to samba 2.0.x use
-	<TT
-CLASS="FILENAME"
->pam_permit.so</TT
->, it's also possible to use 
-	<TT
-CLASS="FILENAME"
->pam_pwdb.so</TT
->. There are some bugs if you try to 
-	use <TT
-CLASS="FILENAME"
->pam_unix.so</TT
->, if you need this, be ensure to use
-	the most recent version of this file.
-	</P
-></LI
-></UL
+accounts then this would indicate that it has not worked. Ensure the domain 
+admin user system is working.</P
+><P
+>Alternatively if you are creating account entries manually then they 
+have not been created correctly. Make sure that you have the entry 
+correct for the machine trust account in smbpasswd file on the Samba PDC. 
+If you added the account using an editor rather than using the smbpasswd 
+utility, make sure that the account name is the machine NetBIOS name 
+with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
+in both /etc/passwd and the smbpasswd file. Some people have reported 
+that inconsistent subnet masks between the Samba server and the NT 
+client have caused this problem.   Make sure that these are consistent 
+for both client and server.</P
 ></DIV
 ><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
 ><A
-NAME="AEN1119"
->6.6. What other help can I get?</A
-></H1
-><P
->There are many sources of information available in the form 
-of mailing lists, RFC's and documentation.  The docs that come 
-with the samba distribution contain very good explanations of 
-general SMB topics such as browsing.</P
-><P
-></P
-><UL
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->What are some diagnostics tools I can use to debug the domain logon 
-	process and where can I	find them?</I
-></SPAN
->
-	</P
-><P
->	One of the best diagnostic tools for debugging problems is Samba itself.  
-	You can use the -d option for both smbd and nmbd to specify what 
-	'debug level' at which to run.  See the man pages on smbd, nmbd  and 
-	smb.conf for more information on debugging options.  The debug 
-	level can range from 1 (the default) to 10 (100 for debugging passwords).
-	</P
-><P
->	Another helpful method of debugging is to compile samba using the 
-	<B
-CLASS="COMMAND"
->gcc -g </B
-> flag.   This will include debug 
-	information in the binaries and allow you to attach gdb to the 
-	running smbd / nmbd process.  In order to attach gdb to an smbd 
-	process for an NT workstation, first get the workstation to make the 
-	connection. Pressing ctrl-alt-delete and going down to the domain box 
-	is sufficient (at least, on the first time you join the domain) to 
-	generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
-	maintains an open connection, and therefore there will be an smbd 
-	process running (assuming that you haven't set a really short smbd 
-	idle timeout)  So, in between pressing ctrl alt delete, and actually 
-	typing in your password, you can gdb attach and continue.
-	</P
-><P
->	Some useful samba commands worth investigating:
-	</P
-><P
-></P
-><UL
-><LI
-><P
->testparam | more</P
-></LI
-><LI
-><P
->smbclient -L //{netbios name of server}</P
-></LI
-></UL
-><P
->	An SMB enabled version of tcpdump is available from 
-	<A
-HREF="http://www.tcpdump.org/"
-TARGET="_top"
->http://www.tcpdup.org/</A
->.
-	Ethereal, another good packet sniffer for Unix and Win32
-	hosts, can be downloaded from <A
-HREF="http://www.ethereal.com/"
-TARGET="_top"
->http://www.ethereal.com</A
->.
-	</P
-><P
->	For tracing things on the Microsoft Windows NT, Network Monitor 
-	(aka. netmon) is available on the Microsoft Developer Network CD's, 
-	the Windows NT Server install CD and the SMS CD's.  The version of 
-	netmon that ships with SMS allows for dumping packets between any two 
-	computers (i.e. placing the network interface in promiscuous mode).  
-	The version on the NT Server install CD will only allow monitoring 
-	of network traffic directed to the local NT box and broadcasts on the 
-	local subnet.  Be aware that Ethereal can read and write netmon 
-	formatted files.
-	</P
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I install 'Network Monitor' on an NT Workstation 
-	or a Windows 9x box?</I
-></SPAN
->
-	</P
-><P
->	Installing netmon on an NT workstation requires a couple 
-	of steps.  The following are for installing Netmon V4.00.349, which comes 
-	with Microsoft Windows NT Server 4.0, on Microsoft Windows NT 
-	Workstation 4.0.  The process should be similar for other version of 
-	Windows NT / Netmon.  You will need both the Microsoft Windows 
-	NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
-	</P
-><P
->	Initially you will need to install 'Network Monitor Tools and Agent' 
-	on the NT Server.  To do this 
-	</P
-><P
-></P
-><UL
-><LI
-><P
->Goto Start - Settings - Control Panel - 
-		Network - Services - Add </P
-></LI
-><LI
-><P
->Select the 'Network Monitor Tools and Agent' and 
-		click on 'OK'.</P
-></LI
-><LI
-><P
->Click 'OK' on the Network Control Panel.
-		</P
-></LI
-><LI
-><P
->Insert the Windows NT Server 4.0 install CD 
-		when prompted.</P
-></LI
-></UL
-><P
->	At this point the Netmon files should exist in 
-	<TT
-CLASS="FILENAME"
->%SYSTEMROOT%\System32\netmon\*.*</TT
->.    
-	Two subdirectories exist as well, <TT
-CLASS="FILENAME"
->parsers\</TT
-> 
-	which contains the necessary DLL's for parsing the netmon packet 
-	dump, and <TT
-CLASS="FILENAME"
->captures\</TT
->.
-	</P
-><P
->	In order to install the Netmon tools on an NT Workstation, you will 
-	first need to install the 'Network  Monitor Agent' from the Workstation 
-	install CD.
-	</P
-><P
-></P
-><UL
-><LI
-><P
->Goto Start - Settings - Control Panel - 
-		Network - Services - Add</P
-></LI
-><LI
-><P
->Select the 'Network Monitor Agent' and click 
-		on 'OK'.</P
-></LI
-><LI
-><P
->Click 'OK' on the Network Control Panel.
-		</P
-></LI
-><LI
-><P
->Insert the Windows NT Workstation 4.0 install 
-		CD when prompted.</P
-></LI
-></UL
-><P
->	Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
-	to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
-	permissions as  you deem appropriate for your site. You will need 
-	administrative rights on the NT box to run netmon.
-	</P
-><P
->	To install Netmon on a Windows 9x box install the network monitor agent 
-	from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
-	file located with the netmon driver files on the CD if you need 
-	information on how to do this.  Copy the files from a working 
-	Netmon installation.
-	</P
-></LI
-><LI
-><P
->	The following is a list if helpful URLs and other links:
-	</P
-><P
-></P
-><UL
-><LI
-><P
->Home of Samba site <A
-HREF="http://samba.org"
-TARGET="_top"
->        http://samba.org</A
->. We have a mirror near you !</P
-></LI
-><LI
-><P
-> The <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Development</I
-></SPAN
-> document 
-	on the Samba mirrors might mention your problem. If so,
-	it might mean that the developers are working on it.</P
-></LI
-><LI
-><P
->See how Scott Merrill simulates a BDC behavior at 
-        <A
-HREF="http://www.skippy.net/linux/smb-howto.html"
-TARGET="_top"
->        http://www.skippy.net/linux/smb-howto.html</A
->. </P
-></LI
-><LI
-><P
->Although 2.0.7 has almost had its day as a PDC, David Bannon will
-        keep the 2.0.7 PDC pages at <A
-HREF="http://bioserve.latrobe.edu.au/samba"
-TARGET="_top"
->        http://bioserve.latrobe.edu.au/samba</A
-> going for a while yet.</P
-></LI
-><LI
-><P
->Misc links to CIFS information 
-        <A
-HREF="http://samba.org/cifs/"
-TARGET="_top"
->http://samba.org/cifs/</A
-></P
-></LI
-><LI
-><P
->NT Domains for Unix <A
-HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
-TARGET="_top"
->        http://mailhost.cb1.com/~lkcl/ntdom/</A
-></P
-></LI
-><LI
-><P
->FTP site for older SMB specs: 
-        <A
-HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
-TARGET="_top"
->        ftp://ftp.microsoft.com/developr/drg/CIFS/</A
-></P
-></LI
-></UL
-></LI
-></UL
-><P
-></P
-><UL
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get help from the mailing lists?</I
-></SPAN
->
-	</P
-><P
->	There are a number of Samba related mailing lists. Go to <A
-HREF="http://samba.org"
-TARGET="_top"
->http://samba.org</A
->, click on your nearest mirror
-	and then click on <B
-CLASS="COMMAND"
->Support</B
-> and then click on <B
-CLASS="COMMAND"
->	Samba related mailing lists</B
->.
-	</P
-><P
->	For questions relating to Samba TNG go to
-	<A
-HREF="http://www.samba-tng.org/"
-TARGET="_top"
->http://www.samba-tng.org/</A
-> 
-	It has been requested that you don't post questions about Samba-TNG to the
-	main stream Samba lists.</P
-><P
->	If you post a message to one of the lists please observe the following guide lines :
-	</P
-><P
-></P
-><UL
-><LI
-><P
-> Always remember that the developers are volunteers, they are 
-		not paid and they never guarantee to produce a particular feature at 
-		a particular time. Any time lines are 'best guess' and nothing more.
-		</P
-></LI
-><LI
-><P
-> Always mention what version of samba you are using and what 
-		operating system its running under. You should probably list the
-        relevant sections of your smb.conf file, at least the options 
-        in [global] that affect PDC support.</P
-></LI
-><LI
-><P
->In addition to the version, if you obtained Samba via
-        CVS mention the date when you last checked it out.</P
-></LI
-><LI
-><P
-> Try and make your question clear and brief, lots of long, 
-		convoluted questions get deleted before	they are completely read ! 
-		Don't post html encoded messages (if you can select colour or font 
-		size its html).</P
-></LI
-><LI
-><P
-> If you run one of those nifty 'I'm on holidays' things when 
-		you are away, make sure its configured	to not answer mailing lists.
-		</P
-></LI
-><LI
-><P
-> Don't cross post. Work out which is the best list to post to 
-		and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
-        Many people active on the lists subscribe to more 
-		than one list and get annoyed to see the same message two or more times. 
-		Often someone will see a message and thinking it would be better dealt 
-		with on another, will forward it on for you.</P
-></LI
-><LI
-><P
->You might include <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->partial</I
-></SPAN
->
-        log files written at a debug level set to as much as 20.  
-        Please don't send the entire log but enough to give the context of the 
-        error messages.</P
-></LI
-><LI
-><P
->(Possibly) If you have a complete netmon trace ( from the opening of 
-        the pipe to the error ) you can send the *.CAP file as well.</P
-></LI
-><LI
-><P
->Please think carefully before attaching a document to an email.
-        Consider pasting the relevant parts into the body of the message. The samba
-        mailing lists go to a huge number of people, do they all need a copy of your 
-        smb.conf in their attach directory?</P
-></LI
-></UL
-></LI
-><LI
-><P
->	<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get off the mailing lists?</I
-></SPAN
->
-	</P
+NAME="AEN1237"
+>7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+I get a message about my account being disabled.</A
+></H2
 ><P
->To have your name removed from a samba mailing list, go to the
-	same place you went to to get on it. Go to <A
-HREF="http://lists.samba.org/"
-TARGET="_top"
->http://lists.samba.org</A
->, 
-	click on your nearest mirror and then click on <B
-CLASS="COMMAND"
->Support</B
-> and 
-	then click on <B
+>At first be ensure to enable the useraccounts with <B
 CLASS="COMMAND"
-> Samba related mailing lists</B
->. Or perhaps see 
-	<A
-HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
-TARGET="_top"
->here</A
->
-	</P
-><P
->	Please don't post messages to the list asking to be removed, you will just
-	be referred to the above address (unless that process failed in some way...)
-	</P
-></LI
-></UL
+>smbpasswd -e 
+%user%</B
+>, this is normally done, when you create an account.</P
+></DIV
 ></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1233"
->6.7. Domain Control for Windows 9x/ME</A
+NAME="AEN1241"
+>7.6. Domain Control for Windows 9x/ME</A
 ></H1
 ><P
 >A domain and a workgroup are exactly the same thing in terms of network
@@ -1625,8 +1248,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1256"
->6.7.1. Configuration Instructions:	Network Logons</A
+NAME="AEN1264"
+>7.6.1. Configuration Instructions:	Network Logons</A
 ></H2
 ><P
 >The main difference between a PDC and a Windows 9x logon 
diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html
index 689fba7cee..728f42f6f9 100644
--- a/docs/htmldocs/samba.7.html
+++ b/docs/htmldocs/samba.7.html
@@ -246,13 +246,353 @@ CLASS="COMMAND"
 		command is a tool for changing LanMan and Windows NT 
 		password hashes on Samba and Windows NT servers.</P
 ></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbcacls</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbcacls</B
+> command is 
+		a tool to set ACL's on remote CIFS servers. </P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbsh</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbsh</B
+> command is 
+		a program that allows you to run a unix shell with 
+		with an overloaded VFS.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbtree</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbtree</B
+> command 
+		is a text-based network neighborhood tool.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbtar</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbtar</B
+> can make 
+		backups of data on CIFS/SMB servers.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbspool</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>smbspool</B
+> is a 
+		helper utility for printing on printers connected 
+		to CIFS servers. </P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbcontrol</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>smbcontrol</B
+> is a utility
+		that can change the behaviour of running samba daemons.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>rpcclient</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>rpcclient</B
+> is a utility
+		that can be used to execute RPC commands on remote 
+		CIFS servers.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>pdbedit</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>pdbedit</B
+> command 
+		can be used to maintain the local user database on 
+		a samba server.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>findsmb</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>findsmb</B
+> command 
+		can be used to find SMB servers on the local network.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>net</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>net</B
+> command 
+		is supposed to work similar to the DOS/Windows
+		NET.EXE command.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>swat</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>swat</B
+> is a web-based
+		interface to configuring <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>winbindd</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>winbindd</B
+> is a daemon 
+		that is used for integrating authentication and 
+		the user database into unix.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>wbinfo</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>wbinfo</B
+> is a utility 
+		that retrieves and stores information related to winbind.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>editreg</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>editreg</B
+> is a command-line
+		utility that can edit windows registry files.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>profiles</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>profiles</B
+> is a command-line
+		utility that can be used to replace all occurences of 
+		a certain SID with another SID.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>vfstest</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>vfstest</B
+> is a utility
+		that can be used to test vfs modules.</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>ntlm_auth</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>ntlm_auth</B
+> is a helper-utility
+		for external programs wanting to do NTLM-authentication.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbmount</SPAN
+>(8)</SPAN
+>, <SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbumount</SPAN
+>(8)</SPAN
+>, <SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbmount</SPAN
+>(8)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>smbmount</B
+>,<B
+CLASS="COMMAND"
+>smbmnt</B
+> and <B
+CLASS="COMMAND"
+>smbmnt</B
+> are commands that can be used to 
+		mount CIFS/SMB shares on Linux.
+		</P
+></DD
+><DT
+><SPAN
+CLASS="CITEREFENTRY"
+><SPAN
+CLASS="REFENTRYTITLE"
+>smbcquotas</SPAN
+>(1)</SPAN
+></DT
+><DD
+><P
+><B
+CLASS="COMMAND"
+>smbcquotas</B
+> is a tool that 
+		can set remote QUOTA's on server with NTFS 5. </P
+></DD
 ></DL
 ></DIV
 ></DIV
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN99"
+NAME="AEN260"
 ></A
 ><H2
 >COMPONENTS</H2
@@ -281,7 +621,7 @@ TARGET="_top"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN105"
+NAME="AEN266"
 ></A
 ><H2
 >AVAILABILITY</H2
@@ -318,7 +658,7 @@ TARGET="_top"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN113"
+NAME="AEN274"
 ></A
 ><H2
 >VERSION</H2
@@ -329,7 +669,7 @@ NAME="AEN113"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN116"
+NAME="AEN277"
 ></A
 ><H2
 >CONTRIBUTIONS</H2
@@ -358,7 +698,7 @@ CLASS="COMMAND"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN123"
+NAME="AEN284"
 ></A
 ><H2
 >CONTRIBUTORS</H2
@@ -390,7 +730,7 @@ TARGET="_top"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN130"
+NAME="AEN291"
 ></A
 ><H2
 >AUTHOR</H2
diff --git a/docs/htmldocs/securing-samba.html b/docs/htmldocs/securing-samba.html
index 3cee4ac6b4..e5da8dd6d4 100644
--- a/docs/htmldocs/securing-samba.html
+++ b/docs/htmldocs/securing-samba.html
@@ -74,14 +74,53 @@ CLASS="CHAPTER"
 ><A
 NAME="SECURING-SAMBA"
 ></A
->Chapter 24. Securing Samba</H1
+>Chapter 25. Securing Samba</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>25.1. <A
+HREF="securing-samba.html#AEN4074"
+>Introduction</A
+></DT
+><DT
+>25.2. <A
+HREF="securing-samba.html#AEN4077"
+>Using host based protection</A
+></DT
+><DT
+>25.3. <A
+HREF="securing-samba.html#AEN4087"
+>Using interface protection</A
+></DT
+><DT
+>25.4. <A
+HREF="securing-samba.html#AEN4095"
+>Using a firewall</A
+></DT
+><DT
+>25.5. <A
+HREF="securing-samba.html#AEN4102"
+>Using a IPC$ share deny</A
+></DT
+><DT
+>25.6. <A
+HREF="securing-samba.html#AEN4111"
+>Upgrading Samba</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4003"
->24.1. Introduction</A
+NAME="AEN4074"
+>25.1. Introduction</A
 ></H1
 ><P
 >This note was attached to the Samba 2.2.8 release notes as it contained an
@@ -93,8 +132,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4006"
->24.2. Using host based protection</A
+NAME="AEN4077"
+>25.2. Using host based protection</A
 ></H1
 ><P
 >In many installations of Samba the greatest threat comes for outside
@@ -134,8 +173,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4016"
->24.3. Using interface protection</A
+NAME="AEN4087"
+>25.3. Using interface protection</A
 ></H1
 ><P
 >By default Samba will accept connections on any network interface that
@@ -151,8 +190,6 @@ CLASS="PROGRAMLISTING"
   bind interfaces only = yes</PRE
 ></P
 ><P
-></P
-><P
 >This tells Samba to only listen for connections on interfaces with a
 name starting with 'eth' such as eth0, eth1, plus on the loopback
 interface called 'lo'. The name you will need to use depends on what
@@ -170,8 +207,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4025"
->24.4. Using a firewall</A
+NAME="AEN4095"
+>25.4. Using a firewall</A
 ></H1
 ><P
 >Many people use a firewall to deny access to services that they don't
@@ -200,8 +237,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4032"
->24.5. Using a IPC$ share deny</A
+NAME="AEN4102"
+>25.5. Using a IPC$ share deny</A
 ></H1
 ><P
 >If the above methods are not suitable, then you could also place a
@@ -239,8 +276,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4041"
->24.6. Upgrading Samba</A
+NAME="AEN4111"
+>25.6. Upgrading Samba</A
 ></H1
 ><P
 >Please check regularly on <A
diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html
index 256df33ce4..8dc7b796ed 100644
--- a/docs/htmldocs/securitylevels.html
+++ b/docs/htmldocs/securitylevels.html
@@ -74,7 +74,7 @@ CLASS="CHAPTER"
 ><A
 NAME="SECURITYLEVELS"
 ></A
->Chapter 5. Samba as Stand-Alone Server</H1
+>Chapter 6. Samba as Stand-Alone Server</H1
 ><P
 >In this section the function and purpose of Samba's <SPAN
 CLASS="emphasis"
@@ -89,8 +89,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN766"
->5.1. User and Share security level</A
+NAME="AEN897"
+>6.1. User and Share security level</A
 ></H1
 ><P
 >A SMB server tells the client at startup what "security level" it is
@@ -107,8 +107,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN769"
->5.1.1. User Level Security</A
+NAME="AEN900"
+>6.1.1. User Level Security</A
 ></H2
 ><P
 >I'll describe user level security first, as its simpler. In user level
@@ -148,8 +148,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN779"
->5.1.2. Share Level Security</A
+NAME="AEN910"
+>6.1.2. Share Level Security</A
 ></H2
 ><P
 >Ok, now for share level security. In share level security the client
@@ -185,8 +185,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN785"
->5.1.3. Server Level Security</A
+NAME="AEN916"
+>6.1.3. Server Level Security</A
 ></H2
 ><P
 >Finally "server level" security. In server level security the samba
@@ -221,8 +221,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN790"
->5.1.3.1. Configuring Samba for Seemless Windows Network Integration</A
+NAME="AEN921"
+>6.1.3.1. Configuring Samba for Seemless Windows Network Integration</A
 ></H3
 ><P
 >MS Windows clients may use encrypted passwords as part of a challenege/response
@@ -333,8 +333,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN816"
->5.1.3.2. Use MS Windows NT as an authentication server</A
+NAME="AEN947"
+>6.1.3.2. Use MS Windows NT as an authentication server</A
 ></H3
 ><P
 >This method involves the additions of the following parameters in the <TT
@@ -372,8 +372,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN825"
->5.1.4. Domain Level Security</A
+NAME="AEN956"
+>6.1.4. Domain Level Security</A
 ></H2
 ><P
 >When samba is operating in <SPAN
@@ -390,8 +390,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN829"
->5.1.4.1. Samba as a member of an MS Windows NT security domain</A
+NAME="AEN960"
+>6.1.4.1. Samba as a member of an MS Windows NT security domain</A
 ></H3
 ><P
 >This method involves additon of the following paramters in the <TT
@@ -459,8 +459,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN848"
->5.1.5. ADS Level Security</A
+NAME="AEN979"
+>6.1.5. ADS Level Security</A
 ></H2
 ><P
 >For information about the configuration option please refer to the entire section entitled
diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html
index 6ebe2fc002..dc4b0c3541 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -174,7 +174,7 @@ CLASS="FILENAME"
 	The share is accessed via the share name "foo":</P
 ><PRE
 CLASS="SCREEN"
-><SAMP
+>   &nbsp;<SAMP
 CLASS="COMPUTEROUTPUT"
 >[foo]
 	path = /home/bar
@@ -195,7 +195,7 @@ CLASS="EMPHASIS"
 	elsewhere):</P
 ><PRE
 CLASS="SCREEN"
-><SAMP
+>   &nbsp;<SAMP
 CLASS="COMPUTEROUTPUT"
 >[aprinter]
 	path = /usr/spool/public
@@ -294,7 +294,7 @@ CLASS="USERINPUT"
 		section:</P
 ><PRE
 CLASS="SCREEN"
-><SAMP
+>   &nbsp;<SAMP
 CLASS="COMPUTEROUTPUT"
 >[homes]
 	read only = no</SAMP
@@ -395,7 +395,7 @@ NAME="AEN80"
 		this:</P
 ><PRE
 CLASS="SCREEN"
-><SAMP
+>   &nbsp;<SAMP
 CLASS="COMPUTEROUTPUT"
 >[printers]
 	path = /usr/spool/public
@@ -410,7 +410,7 @@ CLASS="COMPUTEROUTPUT"
 		more lines like this:</P
 ><PRE
 CLASS="SCREEN"
-><SAMP
+>   &nbsp;<SAMP
 CLASS="COMPUTEROUTPUT"
 >alias|alias|alias|alias...    </SAMP
 ></PRE
@@ -7091,11 +7091,7 @@ NAME="ENCRYPTPASSWORDS"
 		will be negotiated with the client. Note that Windows NT 4.0 SP3 and 
 		above and also Windows 98 will by default expect encrypted passwords 
 		unless a registry entry is changed. To use encrypted passwords in 
-		Samba see the file ENCRYPTION.txt in the Samba documentation 
-		directory <TT
-CLASS="FILENAME"
->docs/</TT
-> shipped with the source code.</P
+		Samba see the chapter User Database in the Samba HOWTO Collection.</P
 ><P
 >In order for encrypted passwords to work correctly
 		<SPAN
@@ -18461,7 +18457,7 @@ CLASS="PARAMETER"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN6291"
+NAME="AEN6290"
 ></A
 ><H2
 >WARNINGS</H2
@@ -18492,7 +18488,7 @@ CLASS="REFENTRYTITLE"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN6299"
+NAME="AEN6298"
 ></A
 ><H2
 >VERSION</H2
@@ -18502,7 +18498,7 @@ NAME="AEN6299"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN6302"
+NAME="AEN6301"
 ></A
 ><H2
 >SEE ALSO</H2
@@ -18566,7 +18562,7 @@ CLASS="REFENTRYTITLE"
 ><DIV
 CLASS="REFSECT1"
 ><A
-NAME="AEN6332"
+NAME="AEN6331"
 ></A
 ><H2
 >AUTHOR</H2
diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html
index 26cba96a28..33a326c9c6 100644
--- a/docs/htmldocs/speed.html
+++ b/docs/htmldocs/speed.html
@@ -13,11 +13,11 @@ REL="UP"
 TITLE="Appendixes"
 HREF="appendixes.html"><LINK
 REL="PREVIOUS"
-TITLE="Migration from NT4 PDC to Samba-3 PDC"
-HREF="nt4migration.html"><LINK
+TITLE="SWAT - The Samba Web Admininistration Tool"
+HREF="swat.html"><LINK
 REL="NEXT"
-TITLE="Portability"
-HREF="portability.html"></HEAD
+TITLE="The samba checklist"
+HREF="diagnosis.html"></HEAD
 ><BODY
 CLASS="CHAPTER"
 BGCOLOR="#FFFFFF"
@@ -45,7 +45,7 @@ WIDTH="10%"
 ALIGN="left"
 VALIGN="bottom"
 ><A
-HREF="nt4migration.html"
+HREF="swat.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -59,7 +59,7 @@ WIDTH="10%"
 ALIGN="right"
 VALIGN="bottom"
 ><A
-HREF="portability.html"
+HREF="diagnosis.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -74,14 +74,73 @@ CLASS="CHAPTER"
 ><A
 NAME="SPEED"
 ></A
->Chapter 28. Samba performance issues</H1
+>Chapter 32. Samba performance issues</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>32.1. <A
+HREF="speed.html#AEN4666"
+>Comparisons</A
+></DT
+><DT
+>32.2. <A
+HREF="speed.html#AEN4672"
+>Socket options</A
+></DT
+><DT
+>32.3. <A
+HREF="speed.html#AEN4679"
+>Read size</A
+></DT
+><DT
+>32.4. <A
+HREF="speed.html#AEN4684"
+>Max xmit</A
+></DT
+><DT
+>32.5. <A
+HREF="speed.html#AEN4689"
+>Log level</A
+></DT
+><DT
+>32.6. <A
+HREF="speed.html#AEN4692"
+>Read raw</A
+></DT
+><DT
+>32.7. <A
+HREF="speed.html#AEN4697"
+>Write raw</A
+></DT
+><DT
+>32.8. <A
+HREF="speed.html#AEN4701"
+>Slow Clients</A
+></DT
+><DT
+>32.9. <A
+HREF="speed.html#AEN4705"
+>Slow Logins</A
+></DT
+><DT
+>32.10. <A
+HREF="speed.html#AEN4708"
+>Client tuning</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4163"
->28.1. Comparisons</A
+NAME="AEN4666"
+>32.1. Comparisons</A
 ></H1
 ><P
 >The Samba server uses TCP to talk to the client. Thus if you are
@@ -111,8 +170,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4169"
->28.2. Socket options</A
+NAME="AEN4672"
+>32.2. Socket options</A
 ></H1
 ><P
 >There are a number of socket options that can greatly affect the
@@ -139,8 +198,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4176"
->28.3. Read size</A
+NAME="AEN4679"
+>32.3. Read size</A
 ></H1
 ><P
 >The option "read size" affects the overlap of disk reads/writes with
@@ -165,8 +224,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4181"
->28.4. Max xmit</A
+NAME="AEN4684"
+>32.4. Max xmit</A
 ></H1
 ><P
 >At startup the client and server negotiate a "maximum transmit" size,
@@ -188,8 +247,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4186"
->28.5. Log level</A
+NAME="AEN4689"
+>32.5. Log level</A
 ></H1
 ><P
 >If you set the log level (also known as "debug level") higher than 2
@@ -202,8 +261,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4189"
->28.6. Read raw</A
+NAME="AEN4692"
+>32.6. Read raw</A
 ></H1
 ><P
 >The "read raw" operation is designed to be an optimised, low-latency
@@ -224,8 +283,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4194"
->28.7. Write raw</A
+NAME="AEN4697"
+>32.7. Write raw</A
 ></H1
 ><P
 >The "write raw" operation is designed to be an optimised, low-latency
@@ -241,8 +300,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4198"
->28.8. Slow Clients</A
+NAME="AEN4701"
+>32.8. Slow Clients</A
 ></H1
 ><P
 >One person has reported that setting the protocol to COREPLUS rather
@@ -258,8 +317,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4202"
->28.9. Slow Logins</A
+NAME="AEN4705"
+>32.9. Slow Logins</A
 ></H1
 ><P
 >Slow logins are almost always due to the password checking time. Using
@@ -271,8 +330,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN4205"
->28.10. Client tuning</A
+NAME="AEN4708"
+>32.10. Client tuning</A
 ></H1
 ><P
 >Often a speed problem can be traced to the client. The client (for
@@ -389,7 +448,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 ><A
-HREF="nt4migration.html"
+HREF="swat.html"
 ACCESSKEY="P"
 >Prev</A
 ></TD
@@ -407,7 +466,7 @@ WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
 ><A
-HREF="portability.html"
+HREF="diagnosis.html"
 ACCESSKEY="N"
 >Next</A
 ></TD
@@ -417,7 +476,7 @@ ACCESSKEY="N"
 WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
->Migration from NT4 PDC to Samba-3 PDC</TD
+>SWAT - The Samba Web Admininistration Tool</TD
 ><TD
 WIDTH="34%"
 ALIGN="center"
@@ -431,7 +490,7 @@ ACCESSKEY="U"
 WIDTH="33%"
 ALIGN="right"
 VALIGN="top"
->Portability</TD
+>The samba checklist</TD
 ></TR
 ></TABLE
 ></DIV
diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html
index 4f0735b5ab..d03b459736 100644
--- a/docs/htmldocs/type.html
+++ b/docs/htmldocs/type.html
@@ -75,10 +75,11 @@ CLASS="TITLEPAGE"
 ><H1
 CLASS="TITLE"
 >II. Type of installation</H1
+></DIV
 ><DIV
 CLASS="PARTINTRO"
 ><A
-NAME="AEN688"
+NAME="AEN817"
 ></A
 ><H1
 >Introduction</H1
@@ -86,302 +87,6 @@ NAME="AEN688"
 >Samba can operate in various SMB networks. This part contains information on configuring samba 
 for various environments.</P
 ></DIV
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->4. <A
-HREF="servertype.html"
->Nomenclature of Server Types</A
-></DT
-><DD
-><DL
-><DT
->4.1. <A
-HREF="servertype.html#AEN717"
->Stand Alone Server</A
-></DT
-><DT
->4.2. <A
-HREF="servertype.html#AEN724"
->Domain Member Server</A
-></DT
-><DT
->4.3. <A
-HREF="servertype.html#AEN730"
->Domain Controller</A
-></DT
-><DD
-><DL
-><DT
->4.3.1. <A
-HREF="servertype.html#AEN733"
->Domain Controller Types</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->5. <A
-HREF="securitylevels.html"
->Samba as Stand-Alone Server</A
-></DT
-><DD
-><DL
-><DT
->5.1. <A
-HREF="securitylevels.html#AEN766"
->User and Share security level</A
-></DT
-><DD
-><DL
-><DT
->5.1.1. <A
-HREF="securitylevels.html#AEN769"
->User Level Security</A
-></DT
-><DT
->5.1.2. <A
-HREF="securitylevels.html#AEN779"
->Share Level Security</A
-></DT
-><DT
->5.1.3. <A
-HREF="securitylevels.html#AEN785"
->Server Level Security</A
-></DT
-><DT
->5.1.4. <A
-HREF="securitylevels.html#AEN825"
->Domain Level Security</A
-></DT
-><DT
->5.1.5. <A
-HREF="securitylevels.html#AEN848"
->ADS Level Security</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->6. <A
-HREF="samba-pdc.html"
->Samba as an NT4 or Win2k Primary Domain Controller</A
-></DT
-><DD
-><DL
-><DT
->6.1. <A
-HREF="samba-pdc.html#AEN878"
->Prerequisite Reading</A
-></DT
-><DT
->6.2. <A
-HREF="samba-pdc.html#AEN883"
->Background</A
-></DT
-><DT
->6.3. <A
-HREF="samba-pdc.html#AEN923"
->Configuring the Samba Domain Controller</A
-></DT
-><DT
->6.4. <A
-HREF="samba-pdc.html#AEN965"
->Creating Machine Trust Accounts and Joining Clients to the Domain</A
-></DT
-><DD
-><DL
-><DT
->6.4.1. <A
-HREF="samba-pdc.html#AEN1008"
->Manual Creation of Machine Trust Accounts</A
-></DT
-><DT
->6.4.2. <A
-HREF="samba-pdc.html#AEN1049"
->"On-the-Fly" Creation of Machine Trust Accounts</A
-></DT
-><DT
->6.4.3. <A
-HREF="samba-pdc.html#AEN1058"
->Joining the Client to the Domain</A
-></DT
-></DL
-></DD
-><DT
->6.5. <A
-HREF="samba-pdc.html#AEN1073"
->Common Problems and Errors</A
-></DT
-><DT
->6.6. <A
-HREF="samba-pdc.html#AEN1119"
->What other help can I get?</A
-></DT
-><DT
->6.7. <A
-HREF="samba-pdc.html#AEN1233"
->Domain Control for Windows 9x/ME</A
-></DT
-><DD
-><DL
-><DT
->6.7.1. <A
-HREF="samba-pdc.html#AEN1256"
->Configuration Instructions:	Network Logons</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->7. <A
-HREF="samba-bdc.html"
->Samba Backup Domain Controller to Samba Domain Control</A
-></DT
-><DD
-><DL
-><DT
->7.1. <A
-HREF="samba-bdc.html#AEN1286"
->Prerequisite Reading</A
-></DT
-><DT
->7.2. <A
-HREF="samba-bdc.html#AEN1290"
->Background</A
-></DT
-><DT
->7.3. <A
-HREF="samba-bdc.html#AEN1298"
->What qualifies a Domain Controller on the network?</A
-></DT
-><DD
-><DL
-><DT
->7.3.1. <A
-HREF="samba-bdc.html#AEN1301"
->How does a Workstation find its domain controller?</A
-></DT
-><DT
->7.3.2. <A
-HREF="samba-bdc.html#AEN1304"
->When is the PDC needed?</A
-></DT
-></DL
-></DD
-><DT
->7.4. <A
-HREF="samba-bdc.html#AEN1307"
->Can Samba be a Backup Domain Controller to an NT PDC?</A
-></DT
-><DT
->7.5. <A
-HREF="samba-bdc.html#AEN1312"
->How do I set up a Samba BDC?</A
-></DT
-><DD
-><DL
-><DT
->7.5.1. <A
-HREF="samba-bdc.html#AEN1329"
->How do I replicate the smbpasswd file?</A
-></DT
-><DT
->7.5.2. <A
-HREF="samba-bdc.html#AEN1333"
->Can I do this all with LDAP?</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->8. <A
-HREF="ads.html"
->Samba as a ADS domain member</A
-></DT
-><DD
-><DL
-><DT
->8.1. <A
-HREF="ads.html#AEN1355"
->Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
-></DT
-><DT
->8.2. <A
-HREF="ads.html#AEN1368"
->Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
-></DT
-><DT
->8.3. <A
-HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
->Create the computer account</A
-></DT
-><DD
-><DL
-><DT
->8.3.1. <A
-HREF="ads.html#AEN1396"
->Possible errors</A
-></DT
-></DL
-></DD
-><DT
->8.4. <A
-HREF="ads.html#ADS-TEST-SERVER"
->Test your server setup</A
-></DT
-><DT
->8.5. <A
-HREF="ads.html#ADS-TEST-SMBCLIENT"
->Testing with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-></DT
-><DT
->8.6. <A
-HREF="ads.html#AEN1416"
->Notes</A
-></DT
-></DL
-></DD
-><DT
->9. <A
-HREF="domain-security.html"
->Samba as a NT4 or Win2k domain member</A
-></DT
-><DD
-><DL
-><DT
->9.1. <A
-HREF="domain-security.html#AEN1439"
->Joining an NT Domain with Samba 3.0</A
-></DT
-><DT
->9.2. <A
-HREF="domain-security.html#AEN1493"
->Why is this better than security = server?</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-></DIV
 ></DIV
 ><DIV
 CLASS="NAVFOOTER"
diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html
index 65c3f5352e..fbb4998479 100644
--- a/docs/htmldocs/unix-permissions.html
+++ b/docs/htmldocs/unix-permissions.html
@@ -74,14 +74,75 @@ CLASS="CHAPTER"
 ><A
 NAME="UNIX-PERMISSIONS"
 ></A
->Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists</H1
+>Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>11.1. <A
+HREF="unix-permissions.html#AEN1534"
+>Viewing and changing UNIX permissions using the NT 
+	security dialogs</A
+></DT
+><DT
+>11.2. <A
+HREF="unix-permissions.html#AEN1540"
+>How to view file security on a Samba share</A
+></DT
+><DT
+>11.3. <A
+HREF="unix-permissions.html#AEN1551"
+>Viewing file ownership</A
+></DT
+><DT
+>11.4. <A
+HREF="unix-permissions.html#AEN1571"
+>Viewing file or directory permissions</A
+></DT
+><DD
+><DL
+><DT
+>11.4.1. <A
+HREF="unix-permissions.html#AEN1586"
+>File Permissions</A
+></DT
+><DT
+>11.4.2. <A
+HREF="unix-permissions.html#AEN1600"
+>Directory Permissions</A
+></DT
+></DL
+></DD
+><DT
+>11.5. <A
+HREF="unix-permissions.html#AEN1607"
+>Modifying file or directory permissions</A
+></DT
+><DT
+>11.6. <A
+HREF="unix-permissions.html#AEN1629"
+>Interaction with the standard Samba create mask 
+	parameters</A
+></DT
+><DT
+>11.7. <A
+HREF="unix-permissions.html#AEN1682"
+>Interaction with the standard Samba file attribute 
+	mapping</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1525"
->10.1. Viewing and changing UNIX permissions using the NT 
+NAME="AEN1534"
+>11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs</A
 ></H1
 ><P
@@ -130,8 +191,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1531"
->10.2. How to view file security on a Samba share</A
+NAME="AEN1540"
+>11.2. How to view file security on a Samba share</A
 ></H1
 ><P
 >From an NT4/2000/XP client, single-click with the right 
@@ -199,8 +260,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1542"
->10.3. Viewing file ownership</A
+NAME="AEN1551"
+>11.3. Viewing file ownership</A
 ></H1
 ><P
 >Clicking on the <B
@@ -285,8 +346,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1562"
->10.4. Viewing file or directory permissions</A
+NAME="AEN1571"
+>11.4. Viewing file or directory permissions</A
 ></H1
 ><P
 >The third button is the <B
@@ -339,8 +400,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1577"
->10.4.1. File Permissions</A
+NAME="AEN1586"
+>11.4.1. File Permissions</A
 ></H2
 ><P
 >The standard UNIX user/group/world triple and 
@@ -401,8 +462,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN1591"
->10.4.2. Directory Permissions</A
+NAME="AEN1600"
+>11.4.2. Directory Permissions</A
 ></H2
 ><P
 >Directories on an NT NTFS file system have two 
@@ -433,8 +494,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1598"
->10.5. Modifying file or directory permissions</A
+NAME="AEN1607"
+>11.5. Modifying file or directory permissions</A
 ></H1
 ><P
 >Modifying file and directory permissions is as simple 
@@ -529,8 +590,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1620"
->10.6. Interaction with the standard Samba create mask 
+NAME="AEN1629"
+>11.6. Interaction with the standard Samba create mask 
 	parameters</A
 ></H1
 ><P
@@ -718,8 +779,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN1673"
->10.7. Interaction with the standard Samba file attribute 
+NAME="AEN1682"
+>11.7. Interaction with the standard Samba file attribute 
 	mapping</A
 ></H1
 ><P
diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html
index 6f5e852b1a..06f80c4180 100644
--- a/docs/htmldocs/vfs.html
+++ b/docs/htmldocs/vfs.html
@@ -74,14 +74,76 @@ CLASS="CHAPTER"
 ><A
 NAME="VFS"
 ></A
->Chapter 20. Stackable VFS modules</H1
+>Chapter 21. Stackable VFS modules</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>21.1. <A
+HREF="vfs.html#AEN3601"
+>Introduction and configuration</A
+></DT
+><DT
+>21.2. <A
+HREF="vfs.html#AEN3610"
+>Included modules</A
+></DT
+><DD
+><DL
+><DT
+>21.2.1. <A
+HREF="vfs.html#AEN3612"
+>audit</A
+></DT
+><DT
+>21.2.2. <A
+HREF="vfs.html#AEN3620"
+>extd_audit</A
+></DT
+><DT
+>21.2.3. <A
+HREF="vfs.html#AEN3624"
+>recycle</A
+></DT
+><DT
+>21.2.4. <A
+HREF="vfs.html#AEN3661"
+>netatalk</A
+></DT
+></DL
+></DD
+><DT
+>21.3. <A
+HREF="vfs.html#AEN3668"
+>VFS modules available elsewhere</A
+></DT
+><DD
+><DL
+><DT
+>21.3.1. <A
+HREF="vfs.html#AEN3672"
+>DatabaseFS</A
+></DT
+><DT
+>21.3.2. <A
+HREF="vfs.html#AEN3680"
+>vscan</A
+></DT
+></DL
+></DD
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3531"
->20.1. Introduction and configuration</A
+NAME="AEN3601"
+>21.1. Introduction and configuration</A
 ></H1
 ><P
 >Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.  
@@ -121,16 +183,16 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3540"
->20.2. Included modules</A
+NAME="AEN3610"
+>21.2. Included modules</A
 ></H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3542"
->20.2.1. audit</A
+NAME="AEN3612"
+>21.2.1. audit</A
 ></H2
 ><P
 >A simple module to audit file access to the syslog
@@ -167,8 +229,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3550"
->20.2.2. extd_audit</A
+NAME="AEN3620"
+>21.2.2. extd_audit</A
 ></H2
 ><P
 >This module is identical with the <SPAN
@@ -189,8 +251,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3554"
->20.2.3. recycle</A
+NAME="AEN3624"
+>21.2.3. recycle</A
 ></H2
 ><P
 >A recycle-bin like modules. When used any unlink call
@@ -260,8 +322,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3591"
->20.2.4. netatalk</A
+NAME="AEN3661"
+>21.2.4. netatalk</A
 ></H2
 ><P
 >A netatalk module, that will ease co-existence of samba and
@@ -293,8 +355,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN3598"
->20.3. VFS modules available elsewhere</A
+NAME="AEN3668"
+>21.3. VFS modules available elsewhere</A
 ></H1
 ><P
 >This section contains a listing of various other VFS modules that 
@@ -309,8 +371,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3602"
->20.3.1. DatabaseFS</A
+NAME="AEN3672"
+>21.3.1. DatabaseFS</A
 ></H2
 ><P
 >URL: <A
@@ -343,8 +405,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN3610"
->20.3.2. vscan</A
+NAME="AEN3680"
+>21.3.2. vscan</A
 ></H2
 ><P
 >URL: <A
diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html
index e08d617c63..bd3e6923d4 100644
--- a/docs/htmldocs/winbind.html
+++ b/docs/htmldocs/winbind.html
@@ -74,14 +74,154 @@ CLASS="CHAPTER"
 ><A
 NAME="WINBIND"
 ></A
->Chapter 14. Unified Logons between Windows NT and UNIX using Winbind</H1
+>Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>15.1. <A
+HREF="winbind.html#AEN2516"
+>Abstract</A
+></DT
+><DT
+>15.2. <A
+HREF="winbind.html#AEN2520"
+>Introduction</A
+></DT
+><DT
+>15.3. <A
+HREF="winbind.html#AEN2533"
+>What Winbind Provides</A
+></DT
+><DT
+>15.4. <A
+HREF="winbind.html#AEN2544"
+>How Winbind Works</A
+></DT
+><DD
+><DL
+><DT
+>15.4.1. <A
+HREF="winbind.html#AEN2549"
+>Microsoft Remote Procedure Calls</A
+></DT
+><DT
+>15.4.2. <A
+HREF="winbind.html#AEN2553"
+>Microsoft Active Directory Services</A
+></DT
+><DT
+>15.4.3. <A
+HREF="winbind.html#AEN2556"
+>Name Service Switch</A
+></DT
+><DT
+>15.4.4. <A
+HREF="winbind.html#AEN2572"
+>Pluggable Authentication Modules</A
+></DT
+><DT
+>15.4.5. <A
+HREF="winbind.html#AEN2580"
+>User and Group ID Allocation</A
+></DT
+><DT
+>15.4.6. <A
+HREF="winbind.html#AEN2584"
+>Result Caching</A
+></DT
+></DL
+></DD
+><DT
+>15.5. <A
+HREF="winbind.html#AEN2587"
+>Installation and Configuration</A
+></DT
+><DD
+><DL
+><DT
+>15.5.1. <A
+HREF="winbind.html#AEN2592"
+>Introduction</A
+></DT
+><DT
+>15.5.2. <A
+HREF="winbind.html#AEN2605"
+>Requirements</A
+></DT
+><DT
+>15.5.3. <A
+HREF="winbind.html#AEN2619"
+>Testing Things Out</A
+></DT
+><DD
+><DL
+><DT
+>15.5.3.1. <A
+HREF="winbind.html#AEN2630"
+>Configure and compile SAMBA</A
+></DT
+><DT
+>15.5.3.2. <A
+HREF="winbind.html#AEN2649"
+>Configure <TT
+CLASS="FILENAME"
+>nsswitch.conf</TT
+> and the 
+winbind libraries</A
+></DT
+><DT
+>15.5.3.3. <A
+HREF="winbind.html#AEN2682"
+>Configure smb.conf</A
+></DT
+><DT
+>15.5.3.4. <A
+HREF="winbind.html#AEN2698"
+>Join the SAMBA server to the PDC domain</A
+></DT
+><DT
+>15.5.3.5. <A
+HREF="winbind.html#AEN2709"
+>Start up the winbindd daemon and test it!</A
+></DT
+><DT
+>15.5.3.6. <A
+HREF="winbind.html#AEN2749"
+>Fix the init.d startup scripts</A
+></DT
+><DT
+>15.5.3.7. <A
+HREF="winbind.html#AEN2787"
+>Configure Winbind and PAM</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>15.6. <A
+HREF="winbind.html#AEN2844"
+>Limitations</A
+></DT
+><DT
+>15.7. <A
+HREF="winbind.html#AEN2854"
+>Conclusion</A
+></DT
+></DL
+></DIV
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2506"
->14.1. Abstract</A
+NAME="AEN2516"
+>15.1. Abstract</A
 ></H1
 ><P
 >Integration of UNIX and Microsoft Windows NT through 
@@ -107,8 +247,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2510"
->14.2. Introduction</A
+NAME="AEN2520"
+>15.2. Introduction</A
 ></H1
 ><P
 >It is well known that UNIX and Microsoft Windows NT have 
@@ -161,8 +301,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2523"
->14.3. What Winbind Provides</A
+NAME="AEN2533"
+>15.3. What Winbind Provides</A
 ></H1
 ><P
 >Winbind unifies UNIX and Windows NT account management by 
@@ -203,8 +343,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2530"
->14.3.1. Target Uses</A
+NAME="AEN2540"
+>15.3.1. Target Uses</A
 ></H2
 ><P
 >Winbind is targeted at organizations that have an 
@@ -227,8 +367,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2534"
->14.4. How Winbind Works</A
+NAME="AEN2544"
+>15.4. How Winbind Works</A
 ></H1
 ><P
 >The winbind system is designed around a client/server 
@@ -247,8 +387,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2539"
->14.4.1. Microsoft Remote Procedure Calls</A
+NAME="AEN2549"
+>15.4.1. Microsoft Remote Procedure Calls</A
 ></H2
 ><P
 >Over the last few years, efforts have been underway 
@@ -273,8 +413,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2543"
->14.4.2. Microsoft Active Directory Services</A
+NAME="AEN2553"
+>15.4.2. Microsoft Active Directory Services</A
 ></H2
 ><P
 >                Since late 2001, Samba has gained the ability to
@@ -292,8 +432,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2546"
->14.4.3. Name Service Switch</A
+NAME="AEN2556"
+>15.4.3. Name Service Switch</A
 ></H2
 ><P
 >The Name Service Switch, or NSS, is a feature that is 
@@ -372,8 +512,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2562"
->14.4.4. Pluggable Authentication Modules</A
+NAME="AEN2572"
+>15.4.4. Pluggable Authentication Modules</A
 ></H2
 ><P
 >Pluggable Authentication Modules, also known as PAM, 
@@ -421,8 +561,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2570"
->14.4.5. User and Group ID Allocation</A
+NAME="AEN2580"
+>15.4.5. User and Group ID Allocation</A
 ></H2
 ><P
 >When a user or group is created under Windows NT 
@@ -447,8 +587,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2574"
->14.4.6. Result Caching</A
+NAME="AEN2584"
+>15.4.6. Result Caching</A
 ></H2
 ><P
 >An active system can generate a lot of user and group 
@@ -470,8 +610,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2577"
->14.5. Installation and Configuration</A
+NAME="AEN2587"
+>15.5. Installation and Configuration</A
 ></H1
 ><P
 >Many thanks to John Trostel <A
@@ -489,8 +629,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2582"
->14.5.1. Introduction</A
+NAME="AEN2592"
+>15.5.1. Introduction</A
 ></H2
 ><P
 >This HOWTO describes the procedures used to get winbind up and 
@@ -548,8 +688,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2595"
->14.5.2. Requirements</A
+NAME="AEN2605"
+>15.5.2. Requirements</A
 ></H2
 ><P
 >If you have a samba configuration file that you are currently 
@@ -618,8 +758,8 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN2609"
->14.5.3. Testing Things Out</A
+NAME="AEN2619"
+>15.5.3. Testing Things Out</A
 ></H2
 ><P
 >Before starting, it is probably best to kill off all the SAMBA 
@@ -663,8 +803,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2620"
->14.5.3.1. Configure and compile SAMBA</A
+NAME="AEN2630"
+>15.5.3.1. Configure and compile SAMBA</A
 ></H3
 ><P
 >The configuration and compilation of SAMBA is pretty straightforward.
@@ -729,8 +869,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2639"
->14.5.3.2. Configure <TT
+NAME="AEN2649"
+>15.5.3.2. Configure <TT
 CLASS="FILENAME"
 >nsswitch.conf</TT
 > and the 
@@ -834,8 +974,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2672"
->14.5.3.3. Configure smb.conf</A
+NAME="AEN2682"
+>15.5.3.3. Configure smb.conf</A
 ></H3
 ><P
 >Several parameters are needed in the smb.conf file to control 
@@ -909,8 +1049,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2688"
->14.5.3.4. Join the SAMBA server to the PDC domain</A
+NAME="AEN2698"
+>15.5.3.4. Join the SAMBA server to the PDC domain</A
 ></H3
 ><P
 >Enter the following command to make the SAMBA server join the 
@@ -947,8 +1087,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2699"
->14.5.3.5. Start up the winbindd daemon and test it!</A
+NAME="AEN2709"
+>15.5.3.5. Start up the winbindd daemon and test it!</A
 ></H3
 ><P
 >Eventually, you will want to modify your smb startup script to 
@@ -1083,16 +1223,16 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2739"
->14.5.3.6. Fix the init.d startup scripts</A
+NAME="AEN2749"
+>15.5.3.6. Fix the init.d startup scripts</A
 ></H3
 ><DIV
 CLASS="SECT4"
 ><H4
 CLASS="SECT4"
 ><A
-NAME="AEN2741"
->14.5.3.6.1. Linux</A
+NAME="AEN2751"
+>15.5.3.6.1. Linux</A
 ></H4
 ><P
 >The <B
@@ -1201,8 +1341,8 @@ CLASS="SECT4"
 ><H4
 CLASS="SECT4"
 ><A
-NAME="AEN2761"
->14.5.3.6.2. Solaris</A
+NAME="AEN2771"
+>15.5.3.6.2. Solaris</A
 ></H4
 ><P
 >On solaris, you need to modify the 
@@ -1285,8 +1425,8 @@ CLASS="SECT4"
 ><H4
 CLASS="SECT4"
 ><A
-NAME="AEN2771"
->14.5.3.6.3. Restarting</A
+NAME="AEN2781"
+>15.5.3.6.3. Restarting</A
 ></H4
 ><P
 >If you restart the <B
@@ -1309,8 +1449,8 @@ CLASS="SECT3"
 ><H3
 CLASS="SECT3"
 ><A
-NAME="AEN2777"
->14.5.3.7. Configure Winbind and PAM</A
+NAME="AEN2787"
+>15.5.3.7. Configure Winbind and PAM</A
 ></H3
 ><P
 >If you have made it this far, you know that winbindd and samba are working
@@ -1367,8 +1507,8 @@ CLASS="SECT4"
 ><H4
 CLASS="SECT4"
 ><A
-NAME="AEN2794"
->14.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
+NAME="AEN2804"
+>15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
 ></H4
 ><P
 >The <TT
@@ -1496,8 +1636,8 @@ CLASS="SECT4"
 ><H4
 CLASS="SECT4"
 ><A
-NAME="AEN2827"
->14.5.3.7.2. Solaris-specific configuration</A
+NAME="AEN2837"
+>15.5.3.7.2. Solaris-specific configuration</A
 ></H4
 ><P
 >The /etc/pam.conf needs to be changed. I changed this file so that my Domain
@@ -1583,8 +1723,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2834"
->14.6. Limitations</A
+NAME="AEN2844"
+>15.6. Limitations</A
 ></H1
 ><P
 >Winbind has a number of limitations in its current 
@@ -1625,8 +1765,8 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN2844"
->14.7. Conclusion</A
+NAME="AEN2854"
+>15.7. Conclusion</A
 ></H1
 ><P
 >The winbind system, through the use of the Name Service 
-- 
cgit