Update pre-release of RC2. Note: Due to config errors not all manpages

were rebuilt. (This used to be commit 01fde1a40b11e73cc98f09ab2ebbd14ed0bed4cf)
author: John Terpstra <jht@samba.org> 2003-08-29 01:15:53 +0000
committer: John Terpstra <jht@samba.org> 2003-08-29 01:15:53 +0000
commit: 04cfbc7854bb793481e9050264a1f0cac1c6198a (patch)
tree: 22d0e5d6d77baa1742fe0c9cb7b92ff6ef9f3efc /docs
parent: cc87f00bddb8e13111fcc4ebea4776df7022ae2d (diff)
download: samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.tar.gz
samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.tar.bz2
samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.zip
28 files changed, 2343 insertions, 2206 deletions
diff --git a/docs/faq/FAQ-ClientApp.html b/docs/faq/FAQ-ClientApp.html
index 3193311d1f..6ba4b1d36c 100644
--- a/docs/faq/FAQ-ClientApp.html
+++ b/docs/faq/FAQ-ClientApp.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter�2.�Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter�4.�Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter�3.�Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2868727">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2815168">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2874026">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868727"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�3.�Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter�2.�Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-errors.html" title="Chapter�4.�Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�3.�Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter�3.�Specific client application problems</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2818225">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2818256">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2816621">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818225"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><div></div></div><p>
 When installing MS Office on a Samba drive for which you have admin
 user permissions, ie. admin users = username, you will find the
 setup program unable to complete the installation.
@@ -10,7 +10,7 @@ rdonly by trying to open it for writing.
 Admin users can always open a file for writing, as they run as root.
 You just have to install as a non-admin user and then use "chown -R"
 to fix the owner.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815168"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818256"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><div></div></div><p>
 Microsoft Office products can be installed as an administrative installation
 from which the application can either be run off the administratively installed
 product that resides on a shared resource, or from which that product can be
@@ -45,7 +45,7 @@ set the following parameters on the share containing it:
 	public = yes
 </pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows
 workstation as follows: <b class="command">\\"Server_Name"\MSOP95\msoffice\setup</b>
-</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874026"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p>
+</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816621"></a>Microsoft Access database opening errors</h2></div></div><div></div></div><p>
 Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><p>
 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�2.�Compiling and installing Samba on a Unix host�</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�4.�Common errors</td></tr></table></div></body></html>
diff --git a/docs/faq/FAQ-Install.html b/docs/faq/FAQ-Install.html
index fc5b1e9812..c331922fdb 100644
--- a/docs/faq/FAQ-Install.html
+++ b/docs/faq/FAQ-Install.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter�1.�General Information"><link rel="next" href="FAQ-ClientApp.html" title="Chapter�3.�Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-Install"></a>Chapter�2.�Compiling and installing Samba on a Unix host</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2868750">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818341">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868750"></a>My client reports "cannot locate specified share name" or similar</h2></div></div><div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�2.�Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter�1.�General Information"><link rel="next" href="FAQ-ClientApp.html" title="Chapter�3.�Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�2.�Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-Install"></a>Chapter�2.�Compiling and installing Samba on a Unix host</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2818381">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818303">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818381"></a>My client reports "cannot locate specified share name" or similar</h2></div></div><div></div></div><p>
 This message indicates that your client CAN locate the specified
 server, which is a good start, but that it cannot find a service of
 the name you gave.
@@ -7,7 +7,7 @@ The first step is to check the exact name of the service you are
 trying to connect to (consult your system administrator). Assuming it
 exists and you specified it correctly (read your client's docs on how
 to specify a service name correctly), read on:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Many clients cannot accept or use service names longer than eight characters.</td></tr><tr><td>Many clients cannot accept or use service names containing spaces.</td></tr><tr><td>Some servers (not Samba though) are case sensitive with service names.</td></tr><tr><td>Some clients force service names into upper case.</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818341"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><div></div></div><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Many clients cannot accept or use service names longer than eight characters.</td></tr><tr><td>Many clients cannot accept or use service names containing spaces.</td></tr><tr><td>Some servers (not Samba though) are case sensitive with service names.</td></tr><tr><td>Some clients force service names into upper case.</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2818303"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><div></div></div><p>
 This is from Paul Eggert eggert@twinsun.com.
 </p><p>
 Most likely it's a problem with your time zone settings.
diff --git a/docs/faq/FAQ-errors.html b/docs/faq/FAQ-errors.html
index ed896b9805..45314a811c 100644
--- a/docs/faq/FAQ-errors.html
+++ b/docs/faq/FAQ-errors.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�Common errors</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-ClientApp.html" title="Chapter�3.�Specific client application problems"><link rel="next" href="FAQ-features.html" title="Chapter�5.�Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�Common errors</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-features.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-errors"></a>Chapter�4.�Common errors</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-errors.html#id2815122">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2874876">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2874916">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2874971">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2815122"></a>Not listening for calling name</h2></div></div><div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�4.�Common errors</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-ClientApp.html" title="Chapter�3.�Specific client application problems"><link rel="next" href="FAQ-features.html" title="Chapter�5.�Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�4.�Common errors</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-features.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-errors"></a>Chapter�4.�Common errors</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-errors.html#id2817184">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2817226">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2816174">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2816225">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817184"></a>Not listening for calling name</h2></div></div><div></div></div><p>
 </p><pre class="programlisting">
 Session request failed (131,129) with myname=HOBBES destname=CALVIN
 Not listening for calling name
@@ -14,7 +14,7 @@ global section of smb.conf.
 It can also be a problem with reverse DNS lookups not functioning 
 correctly, leading to the remote host identity not being able to
 be confirmed, but that is less likely.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874876"></a>System Error 1240</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817226"></a>System Error 1240</h2></div></div><div></div></div><p>
 System error 1240 means that the client is refusing to talk
 to a non-encrypting server. Microsoft changed WinNT in service
 pack 3 to refuse to connect to servers that do not support
@@ -24,7 +24,7 @@ SMB password encryption.
 the samba HOWTO Collection</td></tr><tr><td>disable this behaviour in NT. See the section about 
 Windows NT in the chapter "Portability" of the samba HOWTO collection
 </td></tr></table><p>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874916"></a>smbclient ignores -N !</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816174"></a>smbclient ignores -N !</h2></div></div><div></div></div><p>
 &#8220;<span class="quote">When getting the list of shares available on a host using the command
 <b class="command">smbclient -N -L</b>
 the program always prompts for the password if the server is a Samba server.
@@ -42,7 +42,7 @@ This will set both the username and password to null, which is
 an anonymous login for SMB. Using -N would only set the password
 to null, and this is not accepted as an anonymous login for most
 SMB servers.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874971"></a>The data on the CD-Drive I've shared seems to be corrupted!</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816225"></a>The data on the CD-Drive I've shared seems to be corrupted!</h2></div></div><div></div></div><p>
 Some OSes (notably Linux) default to auto detection of file type on
 cdroms and do cr/lf translation. This is a very bad idea when use with
 Samba. It causes all sorts of stuff ups.
diff --git a/docs/faq/FAQ-features.html b/docs/faq/FAQ-features.html
index 8eb7d94bab..5d20ba6fa0 100644
--- a/docs/faq/FAQ-features.html
+++ b/docs/faq/FAQ-features.html
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter�4.�Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-features"></a>Chapter�5.�Features</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2875179">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874300">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874353">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874445">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874838">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2814744">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2814866">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883464">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883493">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875179"></a>How can I use samba as a fax server?</h2></div></div><div></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements:
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�5.�Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter�4.�Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�5.�Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�</td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-features"></a>Chapter�5.�Features</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2816095">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2816474">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2816526">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2882877">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2882962">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2882986">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2883112">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883160">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883189">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2816095"></a>How can I use samba as a fax server?</h2></div></div><div></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>UNIX box (Linux preferred) with SAMBA and a faxmodem</td></tr><tr><td>ghostscript package</td></tr><tr><td>mgetty+sendfax package</td></tr><tr><td>pbm package (portable bitmap tools)</td></tr></table><p>
 </p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax 
-manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874300"></a>Tools for printing faxes</h3></div></div><div></div></div><p>Your incomed faxes are in:
+manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2816474"></a>Tools for printing faxes</h3></div></div><div></div></div><p>Your incomed faxes are in:
 <tt class="filename">/var/spool/fax/incoming</tt>. Print it with:</p><pre class="programlisting">
 for i in *
 do
@@ -15,7 +15,7 @@ for printing to HP lasers.
 If you want to produce files for displaying and printing with Windows, use
 some tools from the pbm-package like the following command: <b class="command">g3cat $i | g3topbm - |  ppmtopcx - &gt;$i.pcx</b>
 and view it with your favourite Windows tool (maybe paintbrush)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874353"></a>Making the fax-server</h3></div></div><div></div></div><p>fetch the file <tt class="filename">mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt class="filename">/usr/local/etc/mgetty+sendfax/</tt>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</p><p>prepare your faxspool file as mentioned in this file
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2816526"></a>Making the fax-server</h3></div></div><div></div></div><p>fetch the file <tt class="filename">mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt class="filename">/usr/local/etc/mgetty+sendfax/</tt>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</p><p>prepare your faxspool file as mentioned in this file
 edit fax/faxspool.in and reinstall or change the final
 /usr/local/bin/faxspool too.
 </p><pre class="programlisting">
@@ -33,7 +33,7 @@ lp3|fax:\
         :sd=/usr/spool/lp3:\
         :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
         :lf=/usr/spool/lp3/fax-log:
-</pre><p>Now, edit your <tt class="filename">smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874445"></a>Installing the client drivers</h3></div></div><div></div></div><p>
+</pre><p>Now, edit your <tt class="filename">smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882877"></a>Installing the client drivers</h3></div></div><div></div></div><p>
 Now you have a printer called "fax" which can be used via
 TCP/IP-printing (lpd-system) or via SAMBA (windows printing).
 </p><p>
@@ -72,7 +72,7 @@ uses the found number as the fax-destination-number.
 Now print your fax through the fax-printer and it will be
 queued for later transmission. Use faxrunq for sending the
 queue out.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874838"></a>Example smb.conf</h3></div></div><div></div></div><pre class="programlisting">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882962"></a>Example smb.conf</h3></div></div><div></div></div><pre class="programlisting">
 [global]
  printcap name = /etc/printcap
  print command = /usr/bin/lpr -r -P %p %s
@@ -88,7 +88,7 @@ queue out.
     create mode = 0700
     browseable = yes
     guest ok = no
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814744"></a>Samba doesn't work well together with DHCP!</h2></div></div><div></div></div><p>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882986"></a>Samba doesn't work well together with DHCP!</h2></div></div><div></div></div><p>
 We wish to help those folks who wish to use the ISC DHCP Server and provide
 sample configuration settings. Most operating systems today come ship with
 the ISC DHCP Server. ISC DHCP is available from:
@@ -148,7 +148,7 @@ Server provides only a sub-set of rfc1533 functionality this is hardly an issue
 in those sites that already have a large investment and commitment to Unix
 systems and technologies. The current state of the art of the DHCP Server
 specification in covered in rfc2132.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814866"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883112"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><div></div></div><p>
 SMB network clients need to be configured so that all standard TCP/IP name to
 address resolution works correctly. Once this has been achieved the SMB
 environment provides additional tools and services that act as helper agents in
@@ -163,13 +163,13 @@ This can be done, but needs a few NT registry hacks and you need to be able to
 speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
 Instructions on how to do this (including a small util for less capable
 Wizzards) can be found at
-</p><p><a href="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html" target="_top">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</a></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883464"></a>How do I convert between unix and dos text formats?</h2></div></div><div></div></div><p>
+</p><p><a href="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html" target="_top">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</a></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883160"></a>How do I convert between unix and dos text formats?</h2></div></div><div></div></div><p>
 Jim barry has written an <a href="ftp://samba.org/pub/samba/contributed/fixcrlf.zip" target="_top">
 excellent drag-and-drop cr/lf converter for
 windows</a>. Just drag your file onto the icon and it converts the file.
 </p><p>
 The utilities unix2dos and dos2unix(in the mtools package) should do 
 the job under unix.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883493"></a>Does samba have wins replication support?</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883189"></a>Does samba have wins replication support?</h2></div></div><div></div></div><p>
 At the time of writing there is currently being worked on a wins replication implementation(wrepld).
 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right">�</td></tr><tr><td width="40%" align="left" valign="top">Chapter�4.�Common errors�</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top">�</td></tr></table></div></body></html>
diff --git a/docs/faq/FAQ-general.html b/docs/faq/FAQ-general.html
index 311368c2a9..98b94c3011 100644
--- a/docs/faq/FAQ-general.html
+++ b/docs/faq/FAQ-general.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�General Information</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-Install.html" title="Chapter�2.�Compiling and installing Samba on a Unix host"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�General Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-Install.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-general"></a>Chapter�1.�General Information</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-general.html#id2882842">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2883252">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2868767">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882842"></a>What do the version numbers mean?</h2></div></div><div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�1.�General Information</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-Install.html" title="Chapter�2.�Compiling and installing Samba on a Unix host"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�1.�General Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-Install.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FAQ-general"></a>Chapter�1.�General Information</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-general.html#id2814586">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2814212">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2817416">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814586"></a>What do the version numbers mean?</h2></div></div><div></div></div><p>
 It is not recommended that you run a version of Samba with the word
 "alpha" in its name unless you know what you are doing and are willing
 to do some debugging. Many, many people just get the latest
@@ -37,11 +37,11 @@ The above system means that whenever someone looks at the samba ftp
 site they will be able to grab the highest numbered release without an
 alpha in the name and be sure of getting the current recommended
 version.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883252"></a>What platforms are supported?</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2814212"></a>What platforms are supported?</h2></div></div><div></div></div><p>
 Many different platforms have run Samba successfully. The platforms
 most widely used and thus best tested are Linux and SunOS.</p><p>
 At time of writing, there is support (or has been support for in earlier 
 versions):
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A/UX 3.0</td></tr><tr><td>AIX</td></tr><tr><td>Altos Series 386/1000</td></tr><tr><td>Amiga</td></tr><tr><td>Apollo Domain/OS sr10.3</td></tr><tr><td>BSDI </td></tr><tr><td>B.O.S. (Bull Operating System)</td></tr><tr><td>Cray, Unicos 8.0</td></tr><tr><td>Convex</td></tr><tr><td>DGUX. </td></tr><tr><td>DNIX.</td></tr><tr><td>FreeBSD</td></tr><tr><td>HP-UX</td></tr><tr><td>Intergraph. </td></tr><tr><td>Linux with/without shadow passwords and quota</td></tr><tr><td>LYNX 2.3.0</td></tr><tr><td>MachTen (a unix like system for Macintoshes)</td></tr><tr><td>Motorola 88xxx/9xx range of machines</td></tr><tr><td>NetBSD</td></tr><tr><td>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</td></tr><tr><td>OS/2 using EMX 0.9b</td></tr><tr><td>OSF1</td></tr><tr><td>QNX 4.22</td></tr><tr><td>RiscIX. </td></tr><tr><td>RISCOs 5.0B</td></tr><tr><td>SEQUENT. </td></tr><tr><td>SCO (including: 3.2v2, European dist., OpenServer 5)</td></tr><tr><td>SGI.</td></tr><tr><td>SMP_DC.OSx v1.1-94c079 on Pyramid S series</td></tr><tr><td>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</td></tr><tr><td>SUNOS 4</td></tr><tr><td>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</td></tr><tr><td>Sunsoft ISC SVR3V4</td></tr><tr><td>SVR4</td></tr><tr><td>System V with some berkely extensions (Motorola 88k R32V3.2).</td></tr><tr><td>ULTRIX.</td></tr><tr><td>UNIXWARE</td></tr><tr><td>UXP/DS</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868767"></a>How do I subscribe to the Samba Mailing Lists?</h2></div></div><div></div></div><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A/UX 3.0</td></tr><tr><td>AIX</td></tr><tr><td>Altos Series 386/1000</td></tr><tr><td>Amiga</td></tr><tr><td>Apollo Domain/OS sr10.3</td></tr><tr><td>BSDI </td></tr><tr><td>B.O.S. (Bull Operating System)</td></tr><tr><td>Cray, Unicos 8.0</td></tr><tr><td>Convex</td></tr><tr><td>DGUX. </td></tr><tr><td>DNIX.</td></tr><tr><td>FreeBSD</td></tr><tr><td>HP-UX</td></tr><tr><td>Intergraph. </td></tr><tr><td>Linux with/without shadow passwords and quota</td></tr><tr><td>LYNX 2.3.0</td></tr><tr><td>MachTen (a unix like system for Macintoshes)</td></tr><tr><td>Motorola 88xxx/9xx range of machines</td></tr><tr><td>NetBSD</td></tr><tr><td>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</td></tr><tr><td>OS/2 using EMX 0.9b</td></tr><tr><td>OSF1</td></tr><tr><td>QNX 4.22</td></tr><tr><td>RiscIX. </td></tr><tr><td>RISCOs 5.0B</td></tr><tr><td>SEQUENT. </td></tr><tr><td>SCO (including: 3.2v2, European dist., OpenServer 5)</td></tr><tr><td>SGI.</td></tr><tr><td>SMP_DC.OSx v1.1-94c079 on Pyramid S series</td></tr><tr><td>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</td></tr><tr><td>SUNOS 4</td></tr><tr><td>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</td></tr><tr><td>Sunsoft ISC SVR3V4</td></tr><tr><td>SVR4</td></tr><tr><td>System V with some berkely extensions (Motorola 88k R32V3.2).</td></tr><tr><td>ULTRIX.</td></tr><tr><td>UNIXWARE</td></tr><tr><td>UXP/DS</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2817416"></a>How do I subscribe to the Samba Mailing Lists?</h2></div></div><div></div></div><p>
 Look at <a href="http://samba.org/samba/archives.html" target="_top">the samba mailing list page</a>
 </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="FAQ-Install.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Samba FAQ�</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�2.�Compiling and installing Samba on a Unix host</td></tr></table></div></body></html>
diff --git a/docs/faq/samba-faq.html b/docs/faq/samba-faq.html
index c33143e747..832577fb64 100644
--- a/docs/faq/samba-faq.html
+++ b/docs/faq/samba-faq.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba FAQ</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-general.html" title="Chapter�1.�General Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba FAQ</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-general.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-FAQ"></a>Samba FAQ</h1></div><div><div class="author"><h3 class="author"><span class="surname">Samba Team</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2882190"></a>Dedication</h2></div></div><div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba FAQ</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-general.html" title="Chapter�1.�General Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba FAQ</th></tr><tr><td width="20%" align="left">�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a accesskey="n" href="FAQ-general.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-FAQ"></a>Samba FAQ</h1></div><div><div class="author"><h3 class="author"><span class="surname">Samba Team</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2881422"></a>Dedication</h2></div></div><div></div></div><p>
 This is the Frequently Asked Questions (FAQ) document for
 Samba, the free and very popular SMB server product. An SMB server
 allows file and printer connections from clients such as Windows,
@@ -7,4 +7,4 @@ corrections to the samba documentation mailinglist at
 <a href="mailto:samba-doc@samba.org" target="_top">samba-doc@samba.org</a>. 
 This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman, 
 and the old samba text documents which were mostly written by John Terpstra.
-</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="FAQ-general.html">General Information</a></dt><dd><dl><dt><a href="FAQ-general.html#id2882842">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2883252">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2868767">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></dd><dt>2. <a href="FAQ-Install.html">Compiling and installing Samba on a Unix host</a></dt><dd><dl><dt><a href="FAQ-Install.html#id2868750">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818341">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></dd><dt>3. <a href="FAQ-ClientApp.html">Specific client application problems</a></dt><dd><dl><dt><a href="FAQ-ClientApp.html#id2868727">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2815168">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2874026">Microsoft Access database opening errors</a></dt></dl></dd><dt>4. <a href="FAQ-errors.html">Common errors</a></dt><dd><dl><dt><a href="FAQ-errors.html#id2815122">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2874876">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2874916">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2874971">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></dd><dt>5. <a href="FAQ-features.html">Features</a></dt><dd><dl><dt><a href="FAQ-features.html#id2875179">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874300">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874353">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874445">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874838">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2814744">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2814866">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883464">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883493">Does samba have wins replication support?</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="FAQ-general.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�Chapter�1.�General Information</td></tr></table></div></body></html>
+</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="FAQ-general.html">General Information</a></dt><dd><dl><dt><a href="FAQ-general.html#id2814586">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2814212">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2817416">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></dd><dt>2. <a href="FAQ-Install.html">Compiling and installing Samba on a Unix host</a></dt><dd><dl><dt><a href="FAQ-Install.html#id2818381">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2818303">Why are my file's timestamps off by an hour, or by a few hours?</a></dt></dl></dd><dt>3. <a href="FAQ-ClientApp.html">Specific client application problems</a></dt><dd><dl><dt><a href="FAQ-ClientApp.html#id2818225">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2818256">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2816621">Microsoft Access database opening errors</a></dt></dl></dd><dt>4. <a href="FAQ-errors.html">Common errors</a></dt><dd><dl><dt><a href="FAQ-errors.html#id2817184">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2817226">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2816174">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2816225">The data on the CD-Drive I've shared seems to be corrupted!</a></dt></dl></dd><dt>5. <a href="FAQ-features.html">Features</a></dt><dd><dl><dt><a href="FAQ-features.html#id2816095">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2816474">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2816526">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2882877">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2882962">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2882986">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2883112">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2883160">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2883189">Does samba have wins replication support?</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left">�</td><td width="20%" align="center">�</td><td width="40%" align="right">�<a accesskey="n" href="FAQ-general.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">�</td><td width="20%" align="center">�</td><td width="40%" align="right" valign="top">�Chapter�1.�General Information</td></tr></table></div></body></html>
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html
index c16b48441b..97e48f3e27 100644
--- a/docs/htmldocs/Samba-Developers-Guide.html
+++ b/docs/htmldocs/Samba-Developers-Guide.html
@@ -26,15 +26,15 @@ Please send updates to <a href="mailto:jelmer@samba.org" target="_top">Jelmer Ve
 This documentation is distributed under the GNU General Public License (GPL) 
 version 2.  A copy of the license is included with the Samba source
 distribution.  A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a>
-</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2865348">Attributions</a></dt><dt>1. <a href="#netbios">Definition of NetBIOS Protocol and Name Resolution Modes</a></dt><dd><dl><dt><a href="#id2797071">NETBIOS</a></dt><dt><a href="#id2797155">BROADCAST NetBIOS</a></dt><dt><a href="#id2797186">NBNS NetBIOS</a></dt></dl></dd><dt>2. <a href="#architecture">Samba Architecture</a></dt><dd><dl><dt><a href="#id2797301">Introduction</a></dt><dt><a href="#id2797354">Multithreading and Samba</a></dt><dt><a href="#id2797393">Threading smbd</a></dt><dt><a href="#id2797467">Threading nmbd</a></dt><dt><a href="#id2797529">nbmd Design</a></dt></dl></dd><dt>3. <a href="#debug">The samba DEBUG system</a></dt><dd><dl><dt><a href="#id2797614">New Output Syntax</a></dt><dt><a href="#id2797749">The DEBUG() Macro</a></dt><dt><a href="#id2799885">The DEBUGADD() Macro</a></dt><dt><a href="#id2799932">The DEBUGLVL() Macro</a></dt><dt><a href="#id2800044">New Functions</a></dt><dd><dl><dt><a href="#id2800051">dbgtext()</a></dt><dt><a href="#id2800071">dbghdr()</a></dt><dt><a href="#id2800094">format_debug_text()</a></dt></dl></dd></dl></dd><dt>4. <a href="#CodingSuggestions">Coding Suggestions</a></dt><dt>5. <a href="#internals">Samba Internals</a></dt><dd><dl><dt><a href="#id2800556">Character Handling</a></dt><dt><a href="#id2800582">The new functions</a></dt><dt><a href="#id2800742">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2800755">CVAL(buf,pos)</a></dt><dt><a href="#id2800769">PVAL(buf,pos)</a></dt><dt><a href="#id2800783">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2800795">SVAL(buf,pos)</a></dt><dt><a href="#id2800815">IVAL(buf,pos)</a></dt><dt><a href="#id2800829">SVALS(buf,pos)</a></dt><dt><a href="#id2800844">IVALS(buf,pos)</a></dt><dt><a href="#id2800858">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2800872">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2800887">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2800901">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2800916">RSVAL(buf,pos)</a></dt><dt><a href="#id2800930">RIVAL(buf,pos)</a></dt><dt><a href="#id2800944">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2866314">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2866329">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2866366">Parameters</a></dt><dt><a href="#id2866517">Return value</a></dt></dl></dd><dt><a href="#id2866617">Code character table</a></dt></dl></dd><dt>6. <a href="#parsing">The smb.conf file</a></dt><dd><dl><dt><a href="#id2866736">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2866826">Handling of Whitespace</a></dt><dt><a href="#id2866883">Handling of Line Continuation</a></dt><dt><a href="#id2866948">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2867044">Syntax</a></dt><dd><dl><dt><a href="#id2867117">About params.c</a></dt></dl></dd></dl></dd><dt>7. <a href="#unix-smb">NetBIOS in a Unix World</a></dt><dd><dl><dt><a href="#id2867166">Introduction</a></dt><dt><a href="#id2867191">Usernames</a></dt><dt><a href="#id2867277">File Ownership</a></dt><dt><a href="#id2867326">Passwords</a></dt><dt><a href="#id2867388">Locking</a></dt><dt><a href="#id2867458">Deny Modes</a></dt><dt><a href="#id2867499">Trapdoor UIDs</a></dt><dt><a href="#id2867526">Port numbers</a></dt><dt><a href="#id2867572">Protocol Complexity</a></dt></dl></dd><dt>8. <a href="#tracing">Tracing samba system calls</a></dt><dt>9. <a href="#windows-debug">Finding useful information on windows</a></dt><dd><dl><dt><a href="#id2867998">Netlogon debugging output</a></dt></dl></dd><dt>10. <a href="#ntdomain">NT Domain RPC's</a></dt><dd><dl><dt><a href="#id2868139">Introduction</a></dt><dd><dl><dt><a href="#id2868342">Sources</a></dt><dt><a href="#id2868377">Credits</a></dt></dl></dd><dt><a href="#id2868416">Notes and Structures</a></dt><dd><dl><dt><a href="#id2868423">Notes</a></dt><dt><a href="#id2868506">Enumerations</a></dt><dt><a href="#id2868718">Structures</a></dt></dl></dd><dt><a href="#id2871669">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2871682">MSRPC Pipes</a></dt><dt><a href="#id2871787">Header</a></dt><dt><a href="#id2872660">Tail</a></dt><dt><a href="#id2872706">RPC Bind / Bind Ack</a></dt><dt><a href="#id2872896">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2873062">LSA Open Policy</a></dt><dt><a href="#id2873187">LSA Query Info Policy</a></dt><dt><a href="#id2873296">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2873387">LSA Open Secret</a></dt><dt><a href="#id2873498">LSA Close</a></dt><dt><a href="#id2873564">LSA Lookup SIDS</a></dt><dt><a href="#id2873773">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2873999">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2874162">LSA Request Challenge</a></dt><dt><a href="#id2874296">LSA Authenticate 2</a></dt><dt><a href="#id2874444">LSA Server Password Set</a></dt><dt><a href="#id2874559">LSA SAM Logon</a></dt><dt><a href="#id2874662">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2874755">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2874774">Query for PDC</a></dt><dt><a href="#id2875034">SAM Logon</a></dt></dl></dd><dt><a href="#id2875360">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2875405">Net Share Enum</a></dt><dt><a href="#id2875625">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2875741">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2875749">Definitions</a></dt><dt><a href="#id2875911">Protocol</a></dt><dt><a href="#id2876010">Comments</a></dt></dl></dd><dt><a href="#id2876057">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2876097">Well-known SIDs</a></dt><dt><a href="#id2876412">Well-known RIDS</a></dt></dl></dd></dl></dd><dt>11. <a href="#printing">Samba Printing Internals</a></dt><dd><dl><dt><a href="#id2876697">Abstract</a></dt><dt><a href="#id2876713">
+</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2796811">Attributions</a></dt><dt>1. <a href="#netbios">Definition of NetBIOS Protocol and Name Resolution Modes</a></dt><dd><dl><dt><a href="#id2800281">NETBIOS</a></dt><dt><a href="#id2800366">BROADCAST NetBIOS</a></dt><dt><a href="#id2800396">NBNS NetBIOS</a></dt></dl></dd><dt>2. <a href="#architecture">Samba Architecture</a></dt><dd><dl><dt><a href="#id2800511">Introduction</a></dt><dt><a href="#id2800565">Multithreading and Samba</a></dt><dt><a href="#id2800603">Threading smbd</a></dt><dt><a href="#id2800677">Threading nmbd</a></dt><dt><a href="#id2800740">nbmd Design</a></dt></dl></dd><dt>3. <a href="#debug">The samba DEBUG system</a></dt><dd><dl><dt><a href="#id2800810">New Output Syntax</a></dt><dt><a href="#id2800946">The DEBUG() Macro</a></dt><dt><a href="#id2801076">The DEBUGADD() Macro</a></dt><dt><a href="#id2801121">The DEBUGLVL() Macro</a></dt><dt><a href="#id2801232">New Functions</a></dt><dd><dl><dt><a href="#id2801239">dbgtext()</a></dt><dt><a href="#id2801258">dbghdr()</a></dt><dt><a href="#id2801281">format_debug_text()</a></dt></dl></dd></dl></dd><dt>4. <a href="#CodingSuggestions">Coding Suggestions</a></dt><dt>5. <a href="#internals">Samba Internals</a></dt><dd><dl><dt><a href="#id2801753">Character Handling</a></dt><dt><a href="#id2801778">The new functions</a></dt><dt><a href="#id2801936">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2801949">CVAL(buf,pos)</a></dt><dt><a href="#id2801963">PVAL(buf,pos)</a></dt><dt><a href="#id2801977">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2801990">SVAL(buf,pos)</a></dt><dt><a href="#id2802006">IVAL(buf,pos)</a></dt><dt><a href="#id2802020">SVALS(buf,pos)</a></dt><dt><a href="#id2802035">IVALS(buf,pos)</a></dt><dt><a href="#id2802049">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2802063">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2802078">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2802092">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2802106">RSVAL(buf,pos)</a></dt><dt><a href="#id2802121">RIVAL(buf,pos)</a></dt><dt><a href="#id2802135">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2802150">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2802166">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2802202">Parameters</a></dt><dt><a href="#id2866095">Return value</a></dt></dl></dd><dt><a href="#id2866180">Code character table</a></dt></dl></dd><dt>6. <a href="#parsing">The smb.conf file</a></dt><dd><dl><dt><a href="#id2866300">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2866391">Handling of Whitespace</a></dt><dt><a href="#id2866447">Handling of Line Continuation</a></dt><dt><a href="#id2866511">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2866608">Syntax</a></dt><dd><dl><dt><a href="#id2866679">About params.c</a></dt></dl></dd></dl></dd><dt>7. <a href="#unix-smb">NetBIOS in a Unix World</a></dt><dd><dl><dt><a href="#id2866728">Introduction</a></dt><dt><a href="#id2866753">Usernames</a></dt><dt><a href="#id2866834">File Ownership</a></dt><dt><a href="#id2866872">Passwords</a></dt><dt><a href="#id2866916">Locking</a></dt><dt><a href="#id2866978">Deny Modes</a></dt><dt><a href="#id2867009">Trapdoor UIDs</a></dt><dt><a href="#id2867034">Port numbers</a></dt><dt><a href="#id2867088">Protocol Complexity</a></dt></dl></dd><dt>8. <a href="#tracing">Tracing samba system calls</a></dt><dt>9. <a href="#windows-debug">Finding useful information on windows</a></dt><dd><dl><dt><a href="#id2867492">Netlogon debugging output</a></dt></dl></dd><dt>10. <a href="#ntdomain">NT Domain RPC's</a></dt><dd><dl><dt><a href="#id2867633">Introduction</a></dt><dd><dl><dt><a href="#id2867832">Sources</a></dt><dt><a href="#id2867868">Credits</a></dt></dl></dd><dt><a href="#id2867906">Notes and Structures</a></dt><dd><dl><dt><a href="#id2867913">Notes</a></dt><dt><a href="#id2867989">Enumerations</a></dt><dt><a href="#id2868203">Structures</a></dt></dl></dd><dt><a href="#id2871153">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2871166">MSRPC Pipes</a></dt><dt><a href="#id2871268">Header</a></dt><dt><a href="#id2872139">Tail</a></dt><dt><a href="#id2872184">RPC Bind / Bind Ack</a></dt><dt><a href="#id2872365">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2872530">LSA Open Policy</a></dt><dt><a href="#id2872655">LSA Query Info Policy</a></dt><dt><a href="#id2872763">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2872853">LSA Open Secret</a></dt><dt><a href="#id2872963">LSA Close</a></dt><dt><a href="#id2873028">LSA Lookup SIDS</a></dt><dt><a href="#id2873238">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2873464">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2873625">LSA Request Challenge</a></dt><dt><a href="#id2873759">LSA Authenticate 2</a></dt><dt><a href="#id2873906">LSA Server Password Set</a></dt><dt><a href="#id2874022">LSA SAM Logon</a></dt><dt><a href="#id2874125">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2874216">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2874229">Query for PDC</a></dt><dt><a href="#id2874497">SAM Logon</a></dt></dl></dd><dt><a href="#id2874822">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2874867">Net Share Enum</a></dt><dt><a href="#id2875087">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2875203">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2875211">Definitions</a></dt><dt><a href="#id2875373">Protocol</a></dt><dt><a href="#id2875471">Comments</a></dt></dl></dd><dt><a href="#id2875519">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2875558">Well-known SIDs</a></dt><dt><a href="#id2875874">Well-known RIDS</a></dt></dl></dd></dl></dd><dt>11. <a href="#printing">Samba Printing Internals</a></dt><dd><dl><dt><a href="#id2876159">Abstract</a></dt><dt><a href="#id2876175">
 Printing Interface to Various Back ends
-</a></dt><dt><a href="#id2876809">
+</a></dt><dt><a href="#id2876271">
 Print Queue TDB's
-</a></dt><dt><a href="#id2877031">
+</a></dt><dt><a href="#id2876487">
 ChangeID and Client Caching of Printer Information
-</a></dt><dt><a href="#id2877045">
+</a></dt><dt><a href="#id2876500">
 Windows NT/2K Printer Change Notify
-</a></dt></dl></dd><dt>12. <a href="#wins">Samba WINS Internals</a></dt><dd><dl><dt><a href="#id2877426">WINS Failover</a></dt></dl></dd><dt>13. <a href="#sam">The Upcoming SAM System</a></dt><dd><dl><dt><a href="#id2877582">Security in the 'new SAM'</a></dt><dt><a href="#id2877712">Standalone from UNIX</a></dt><dt><a href="#id2877739">Handles and Races in the new SAM</a></dt><dt><a href="#id2877808">Layers</a></dt><dd><dl><dt><a href="#id2877815">Application</a></dt><dt><a href="#id2877831">SAM Interface</a></dt><dt><a href="#id2877859">SAM Modules</a></dt></dl></dd><dt><a href="#id2877880">SAM Modules</a></dt><dd><dl><dt><a href="#id2877888">Special Module: sam_passdb</a></dt><dt><a href="#id2877906">sam_ads</a></dt></dl></dd><dt><a href="#id2877935">Memory Management</a></dt><dt><a href="#id2878035">Testing</a></dt></dl></dd><dt>14. <a href="#pwencrypt">LanMan and NT Password Encryption</a></dt><dd><dl><dt><a href="#id2878174">Introduction</a></dt><dt><a href="#id2878193">How does it work?</a></dt><dt><a href="#id2878320">The smbpasswd file</a></dt></dl></dd><dt>15. <a href="#modules">Modules</a></dt><dd><dl><dt><a href="#id2878688">Advantages</a></dt><dt><a href="#id2878737">Loading modules</a></dt><dd><dl><dt><a href="#id2878771">Static modules</a></dt><dt><a href="#id2878811">Shared modules</a></dt></dl></dd><dt><a href="#id2878839">Writing modules</a></dt><dd><dl><dt><a href="#id2878904">Static/Shared selection in configure.in</a></dt></dl></dd></dl></dd><dt>16. <a href="#rpc-plugin">RPC Pluggable Modules</a></dt><dd><dl><dt><a href="#id2879098">About</a></dt><dt><a href="#id2879116">General Overview</a></dt></dl></dd><dt>17. <a href="#vfs">VFS Modules</a></dt><dd><dl><dt><a href="#id2879326">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2879332">The general interface</a></dt><dt><a href="#id2879448">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2879520">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2879528">Initialization and registration</a></dt><dt><a href="#id2879720">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879963">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879970">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2880501">Some Notes</a></dt><dd><dl><dt><a href="#id2880508">Implement TRANSPARENT functions</a></dt><dt><a href="#id2880533">Implement OPAQUE functions</a></dt></dl></dd></dl></dd><dt>18. <a href="#Packaging">Notes to packagers</a></dt><dd><dl><dt><a href="#id2880600">Versioning</a></dt><dt><a href="#id2880635">Modules</a></dt></dl></dd><dt>19. <a href="#contributing">Contributing code</a></dt></dl></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2865348"></a>Attributions</h2></div></div><div></div></div><p><a href="#netbios" title="Chapter�1.�Definition of NetBIOS Protocol and Name Resolution Modes">Definition of NetBIOS Protocol and Name Resolution Modes</a></p><div class="itemizedlist"><ul type="disc"><li><p>Luke Leighton</p></li></ul></div><p><a href="#architecture" title="Chapter�2.�Samba Architecture">Samba Architecture</a></p><div class="itemizedlist"><ul type="disc"><li><p>Dan Shearer</p></li></ul></div><p><a href="#debug" title="Chapter�3.�The samba DEBUG system">The samba DEBUG system</a></p><div class="itemizedlist"><ul type="disc"><li><p>Chris Hertel</p></li></ul></div><p><a href="#CodingSuggestions" title="Chapter�4.�Coding Suggestions">Coding Suggestions</a></p><div class="itemizedlist"><ul type="disc"><li><p>Steve French</p></li><li><p>Simo Sorce</p></li><li><p>Andrew Bartlett</p></li><li><p>Tim Potter</p></li><li><p>Martin Pool</p></li></ul></div><p><a href="#internals" title="Chapter�5.�Samba Internals">Samba Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>David Chappell &lt;<a href="mailto:David.Chappell@mail.trincoll.edu" target="_top">David.Chappell@mail.trincoll.edu</a>&gt;</p></li></ul></div><p><a href="#parsing" title="Chapter�6.�The smb.conf file">The smb.conf file</a></p><div class="itemizedlist"><ul type="disc"><li><p>Chris Hertel</p></li></ul></div><p><a href="#unix-smb" title="Chapter�7.�NetBIOS in a Unix World">NetBIOS in a Unix World</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell</p></li></ul></div><p><a href="#tracing" title="Chapter�8.�Tracing samba system calls">Tracing samba system calls</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell</p></li></ul></div><p><a href="#windows-debug" title="Chapter�9.�Finding useful information on windows">Finding useful information on windows</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#ntdomain" title="Chapter�10.�NT Domain RPC's">NT Domain RPC's</a></p><div class="itemizedlist"><ul type="disc"><li><p>Luke Leighton &lt;<a href="mailto:lkcl@switchboard.net" target="_top">lkcl@switchboard.net</a>&gt;</p></li><li><p>Paul Ashton &lt;<a href="mailto:paul@argo.demon.co.uk" target="_top">paul@argo.demon.co.uk</a>&gt;</p></li><li><p>Duncan Stansfield &lt;<a href="mailto:duncans@sco.com" target="_top">duncans@sco.com</a>&gt;</p></li></ul></div><p><a href="#printing" title="Chapter�11.�Samba Printing Internals">Samba Printing Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter</p></li></ul></div><p><a href="#wins" title="Chapter�12.�Samba WINS Internals">Samba WINS Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter</p></li></ul></div><p><a href="#sam" title="Chapter�13.�The Upcoming SAM System">The Upcoming SAM System</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Bartlett</p></li></ul></div><p><a href="#pwencrypt" title="Chapter�14.�LanMan and NT Password Encryption">LanMan and NT Password Encryption</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison &lt;<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>&gt;</p></li></ul></div><p><a href="#modules" title="Chapter�15.�Modules">Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#rpc-plugin" title="Chapter�16.�RPC Pluggable Modules">RPC Pluggable Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Anthony Liguori &lt;<a href="mailto:aliguor@us.ibm.com" target="_top">aliguor@us.ibm.com</a>&gt;</p></li><li><p>Jelmer Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#vfs" title="Chapter�17.�VFS Modules">VFS Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Alexander Bokovoy &lt;<a href="mailto:ab@samba.org" target="_top">ab@samba.org</a>&gt;</p></li><li><p>Stefan Metzmacher &lt;<a href="mailto:metze@metzemix.de" target="_top">metze@metzemix.de</a>&gt;</p></li></ul></div><p><a href="#Packaging" title="Chapter�18.�Notes to packagers">Notes to packagers</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij</p></li></ul></div><p><a href="#contributing" title="Chapter�19.�Contributing code">Contributing code</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="netbios"></a>Chapter�1.�Definition of NetBIOS Protocol and Name Resolution Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3></div></div><div><p class="pubdate">12 June 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2797071">NETBIOS</a></dt><dt><a href="#id2797155">BROADCAST NetBIOS</a></dt><dt><a href="#id2797186">NBNS NetBIOS</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797071"></a>NETBIOS</h2></div></div><div></div></div><p>
+</a></dt></dl></dd><dt>12. <a href="#wins">Samba WINS Internals</a></dt><dd><dl><dt><a href="#id2876880">WINS Failover</a></dt></dl></dd><dt>13. <a href="#sam">The Upcoming SAM System</a></dt><dd><dl><dt><a href="#id2877009">Security in the 'new SAM'</a></dt><dt><a href="#id2877139">Standalone from UNIX</a></dt><dt><a href="#id2877166">Handles and Races in the new SAM</a></dt><dt><a href="#id2877235">Layers</a></dt><dd><dl><dt><a href="#id2877242">Application</a></dt><dt><a href="#id2877258">SAM Interface</a></dt><dt><a href="#id2877286">SAM Modules</a></dt></dl></dd><dt><a href="#id2877308">SAM Modules</a></dt><dd><dl><dt><a href="#id2877315">Special Module: sam_passdb</a></dt><dt><a href="#id2877333">sam_ads</a></dt></dl></dd><dt><a href="#id2877362">Memory Management</a></dt><dt><a href="#id2877454">Testing</a></dt></dl></dd><dt>14. <a href="#pwencrypt">LanMan and NT Password Encryption</a></dt><dd><dl><dt><a href="#id2877592">Introduction</a></dt><dt><a href="#id2877615">How does it work?</a></dt><dt><a href="#id2877715">The smbpasswd file</a></dt></dl></dd><dt>15. <a href="#modules">Modules</a></dt><dd><dl><dt><a href="#id2878082">Advantages</a></dt><dt><a href="#id2878130">Loading modules</a></dt><dd><dl><dt><a href="#id2878163">Static modules</a></dt><dt><a href="#id2878204">Shared modules</a></dt></dl></dd><dt><a href="#id2878231">Writing modules</a></dt><dd><dl><dt><a href="#id2878293">Static/Shared selection in configure.in</a></dt></dl></dd></dl></dd><dt>16. <a href="#rpc-plugin">RPC Pluggable Modules</a></dt><dd><dl><dt><a href="#id2878489">About</a></dt><dt><a href="#id2878508">General Overview</a></dt></dl></dd><dt>17. <a href="#vfs">VFS Modules</a></dt><dd><dl><dt><a href="#id2878716">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2878723">The general interface</a></dt><dt><a href="#id2878839">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2878926">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2878934">Initialization and registration</a></dt><dt><a href="#id2879115">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879360">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879367">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2879871">Some Notes</a></dt><dd><dl><dt><a href="#id2879878">Implement TRANSPARENT functions</a></dt><dt><a href="#id2879903">Implement OPAQUE functions</a></dt></dl></dd></dl></dd><dt>18. <a href="#Packaging">Notes to packagers</a></dt><dd><dl><dt><a href="#id2879969">Versioning</a></dt><dt><a href="#id2880004">Modules</a></dt></dl></dd><dt>19. <a href="#contributing">Contributing code</a></dt></dl></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2796811"></a>Attributions</h2></div></div><div></div></div><p><a href="#netbios" title="Chapter�1.�Definition of NetBIOS Protocol and Name Resolution Modes">Definition of NetBIOS Protocol and Name Resolution Modes</a></p><div class="itemizedlist"><ul type="disc"><li><p>Luke Leighton</p></li></ul></div><p><a href="#architecture" title="Chapter�2.�Samba Architecture">Samba Architecture</a></p><div class="itemizedlist"><ul type="disc"><li><p>Dan Shearer</p></li></ul></div><p><a href="#debug" title="Chapter�3.�The samba DEBUG system">The samba DEBUG system</a></p><div class="itemizedlist"><ul type="disc"><li><p>Chris Hertel</p></li></ul></div><p><a href="#CodingSuggestions" title="Chapter�4.�Coding Suggestions">Coding Suggestions</a></p><div class="itemizedlist"><ul type="disc"><li><p>Steve French</p></li><li><p>Simo Sorce</p></li><li><p>Andrew Bartlett</p></li><li><p>Tim Potter</p></li><li><p>Martin Pool</p></li></ul></div><p><a href="#internals" title="Chapter�5.�Samba Internals">Samba Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>David Chappell &lt;<a href="mailto:David.Chappell@mail.trincoll.edu" target="_top">David.Chappell@mail.trincoll.edu</a>&gt;</p></li></ul></div><p><a href="#parsing" title="Chapter�6.�The smb.conf file">The smb.conf file</a></p><div class="itemizedlist"><ul type="disc"><li><p>Chris Hertel</p></li></ul></div><p><a href="#unix-smb" title="Chapter�7.�NetBIOS in a Unix World">NetBIOS in a Unix World</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell</p></li></ul></div><p><a href="#tracing" title="Chapter�8.�Tracing samba system calls">Tracing samba system calls</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell</p></li></ul></div><p><a href="#windows-debug" title="Chapter�9.�Finding useful information on windows">Finding useful information on windows</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#ntdomain" title="Chapter�10.�NT Domain RPC's">NT Domain RPC's</a></p><div class="itemizedlist"><ul type="disc"><li><p>Luke Leighton &lt;<a href="mailto:lkcl@switchboard.net" target="_top">lkcl@switchboard.net</a>&gt;</p></li><li><p>Paul Ashton &lt;<a href="mailto:paul@argo.demon.co.uk" target="_top">paul@argo.demon.co.uk</a>&gt;</p></li><li><p>Duncan Stansfield &lt;<a href="mailto:duncans@sco.com" target="_top">duncans@sco.com</a>&gt;</p></li></ul></div><p><a href="#printing" title="Chapter�11.�Samba Printing Internals">Samba Printing Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter</p></li></ul></div><p><a href="#wins" title="Chapter�12.�Samba WINS Internals">Samba WINS Internals</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter</p></li></ul></div><p><a href="#sam" title="Chapter�13.�The Upcoming SAM System">The Upcoming SAM System</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Bartlett</p></li></ul></div><p><a href="#pwencrypt" title="Chapter�14.�LanMan and NT Password Encryption">LanMan and NT Password Encryption</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison &lt;<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>&gt;</p></li></ul></div><p><a href="#modules" title="Chapter�15.�Modules">Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#rpc-plugin" title="Chapter�16.�RPC Pluggable Modules">RPC Pluggable Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Anthony Liguori &lt;<a href="mailto:aliguor@us.ibm.com" target="_top">aliguor@us.ibm.com</a>&gt;</p></li><li><p>Jelmer Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#vfs" title="Chapter�17.�VFS Modules">VFS Modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Alexander Bokovoy &lt;<a href="mailto:ab@samba.org" target="_top">ab@samba.org</a>&gt;</p></li><li><p>Stefan Metzmacher &lt;<a href="mailto:metze@metzemix.de" target="_top">metze@metzemix.de</a>&gt;</p></li></ul></div><p><a href="#Packaging" title="Chapter�18.�Notes to packagers">Notes to packagers</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij</p></li></ul></div><p><a href="#contributing" title="Chapter�19.�Contributing code">Contributing code</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="netbios"></a>Chapter�1.�Definition of NetBIOS Protocol and Name Resolution Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3></div></div><div><p class="pubdate">12 June 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2800281">NETBIOS</a></dt><dt><a href="#id2800366">BROADCAST NetBIOS</a></dt><dt><a href="#id2800396">NBNS NetBIOS</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800281"></a>NETBIOS</h2></div></div><div></div></div><p>
 NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX.
 Samba only uses NetBIOS over TCP/IP.  For details on the TCP/IP NetBIOS 
 Session Service NetBIOS Datagram Service, and NetBIOS Names, see
@@ -75,7 +75,7 @@ NetBIOS names are either UNIQUE or GROUP.  Only one application can claim a
 UNIQUE NetBIOS name on a network.
 </p><p>
 There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797155"></a>BROADCAST NetBIOS</h2></div></div><div></div></div><p> 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800366"></a>BROADCAST NetBIOS</h2></div></div><div></div></div><p> 
 Clients can claim names, and therefore offer services on successfully claimed
 names, on their broadcast-isolated subnet.  One way to get NetBIOS services
 (such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and
@@ -87,7 +87,7 @@ find that some of your hosts spend 95 percent of their time dealing with
 broadcast traffic.  [If you have IPX/SPX on your LAN or WAN, you will find
 that this is already happening: a packet analyzer will show, roughly
 every twelve minutes, great swathes of broadcast traffic!].
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797186"></a>NBNS NetBIOS</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800396"></a>NBNS NetBIOS</h2></div></div><div></div></div><p>
 rfc1001.txt describes, amongst other things, the implementation and use
 of, a 'NetBIOS Name Service'.  NT/AS offers 'Windows Internet Name Service'
 which is fully rfc1001/2 compliant, but has had to take specific action
@@ -128,7 +128,7 @@ WINS Clients therefore claim names from the WINS server.  If the WINS
 server allows them to register a name, the client's NetBIOS session service
 can then offer services on this name.  Other WINS clients will then
 contact the WINS server to resolve a NetBIOS name.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="architecture"></a>Chapter�2.�Samba Architecture</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3></div></div><div><p class="pubdate"> November 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2797301">Introduction</a></dt><dt><a href="#id2797354">Multithreading and Samba</a></dt><dt><a href="#id2797393">Threading smbd</a></dt><dt><a href="#id2797467">Threading nmbd</a></dt><dt><a href="#id2797529">nbmd Design</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797301"></a>Introduction</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="architecture"></a>Chapter�2.�Samba Architecture</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Dan</span> <span class="surname">Shearer</span></h3></div></div><div><p class="pubdate"> November 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2800511">Introduction</a></dt><dt><a href="#id2800565">Multithreading and Samba</a></dt><dt><a href="#id2800603">Threading smbd</a></dt><dt><a href="#id2800677">Threading nmbd</a></dt><dt><a href="#id2800740">nbmd Design</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800511"></a>Introduction</h2></div></div><div></div></div><p>
 This document gives a general overview of how Samba works
 internally. The Samba Team has tried to come up with a model which is
 the best possible compromise between elegance, portability, security
@@ -139,7 +139,7 @@ It also tries to answer some of the frequently asked questions such as:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	Is Samba secure when running on Unix? The xyz platform?
 	What about the root priveliges issue?
-</p></li><li><p>Pros and cons of multithreading in various parts of Samba</p></li><li><p>Why not have a separate process for name resolution, WINS, and browsing?</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797354"></a>Multithreading and Samba</h2></div></div><div></div></div><p>
+</p></li><li><p>Pros and cons of multithreading in various parts of Samba</p></li><li><p>Why not have a separate process for name resolution, WINS, and browsing?</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800565"></a>Multithreading and Samba</h2></div></div><div></div></div><p>
 People sometimes tout threads as a uniformly good thing. They are very
 nice in their place but are quite inappropriate for smbd. nmbd is
 another matter, and multi-threading it would be very nice. 
@@ -156,7 +156,7 @@ smbd multi-threaded.  Multi-threading would actually make Samba much
 slower, less scalable, less portable and much less robust. The fact
 that we use a separate process for each connection is one of Samba's
 biggest advantages.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797393"></a>Threading smbd</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800603"></a>Threading smbd</h2></div></div><div></div></div><p>
 A few problems that would arise from a threaded smbd are:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	It's not only to create threads instead of processes, but you
@@ -181,7 +181,7 @@ A few problems that would arise from a threaded smbd are:
 </p></li><li><p>
 	we couldn't use the system locking calls as the locking context of
 	fcntl() is a process, not a thread.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797467"></a>Threading nmbd</h2></div></div><div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800677"></a>Threading nmbd</h2></div></div><div></div></div><p>
 This would be ideal, but gets sunk by portability requirements.
 </p><p>
 Andrew tried to write a test threads library for nmbd that used only
@@ -208,7 +208,7 @@ packet that arrives. Having a pool of processes is possible but is
 nasty to program cleanly due to the enormous amount of shared data (in
 complex structures) between the processes. We can't rely on each
 platform having a shared memory system.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797529"></a>nbmd Design</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800740"></a>nbmd Design</h2></div></div><div></div></div><p>
 Originally Andrew used recursion to simulate a multi-threaded
 environment, which use the stack enormously and made for really
 confusing debugging sessions. Luke Leighton rewrote it to use a
@@ -225,11 +225,11 @@ a single process.
 </p><p>
 Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the
 wire. It's a nice format that is very amenable to processing but still
-keeps the idea of a distinct packet. See &quot;struct packet_struct&quot; in
+keeps the idea of a distinct packet. See "struct packet_struct" in
 nameserv.h.  It has all the detail but none of the on-the-wire
 mess. This makes it ideal for using in disk or memory-based databases
 for browsing and WINS support. 
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="debug"></a>Chapter�3.�The samba DEBUG system</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">July 1998</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2797614">New Output Syntax</a></dt><dt><a href="#id2797749">The DEBUG() Macro</a></dt><dt><a href="#id2799885">The DEBUGADD() Macro</a></dt><dt><a href="#id2799932">The DEBUGLVL() Macro</a></dt><dt><a href="#id2800044">New Functions</a></dt><dd><dl><dt><a href="#id2800051">dbgtext()</a></dt><dt><a href="#id2800071">dbghdr()</a></dt><dt><a href="#id2800094">format_debug_text()</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797614"></a>New Output Syntax</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="debug"></a>Chapter�3.�The samba DEBUG system</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">July 1998</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2800810">New Output Syntax</a></dt><dt><a href="#id2800946">The DEBUG() Macro</a></dt><dt><a href="#id2801076">The DEBUGADD() Macro</a></dt><dt><a href="#id2801121">The DEBUGLVL() Macro</a></dt><dt><a href="#id2801232">New Functions</a></dt><dd><dl><dt><a href="#id2801239">dbgtext()</a></dt><dt><a href="#id2801258">dbghdr()</a></dt><dt><a href="#id2801281">format_debug_text()</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800810"></a>New Output Syntax</h2></div></div><div></div></div><p>
    The syntax of a debugging log file is represented as:
 </p><pre class="programlisting">
   &gt;debugfile&lt; :== { &gt;debugmsg&lt; }
@@ -282,16 +282,16 @@ by a newline.
 Note that in the above example the function names are not listed on
 the header line. That's because the example above was generated on an
 SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2797749"></a>The DEBUG() Macro</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800946"></a>The DEBUG() Macro</h2></div></div><div></div></div><p>
 Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters.
 The first is the message level, the second is the body of a function
 call to the Debug1() function.
 </p><p>That's confusing.</p><p>Here's an example which may help a bit. If you would write</p><pre class="programlisting">
-printf( &quot;This is a %s message.\n&quot;, &quot;debug&quot; );
+printf( "This is a %s message.\n", "debug" );
 </pre><p>
 to send the output to stdout, then you would write
 </p><pre class="programlisting">
-DEBUG( 0, ( &quot;This is a %s message.\n&quot;, &quot;debug&quot; ) );
+DEBUG( 0, ( "This is a %s message.\n", "debug" ) );
 </pre><p>
 to send the output to the debug file.  All of the normal printf()
 formatting escapes work.
@@ -316,12 +316,12 @@ DEBUG() is called, the new input is simply appended.
 DEBUG() has been used to write partial lines. Here's a simple (dumb)
 example of the kind of thing I'm talking about:
 </p><pre class="programlisting">
-    DEBUG( 0, (&quot;The test returned &quot; ) );
+    DEBUG( 0, ("The test returned " ) );
     if( test() )
-      DEBUG(0, (&quot;True&quot;) );
+      DEBUG(0, ("True") );
     else
-      DEBUG(0, (&quot;False&quot;) );
-    DEBUG(0, (&quot;.\n&quot;) );
+      DEBUG(0, ("False") );
+    DEBUG(0, (".\n") );
 </pre><p>
 Without the format buffer, the output (assuming test() returned true)
 would look like this:
@@ -333,35 +333,35 @@ would look like this:
     [1998/07/30 16:00:51, 0] file.c:function(261)
       .
 </pre><p>Which isn't much use. The format buffer kludge fixes this problem.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2799885"></a>The DEBUGADD() Macro</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801076"></a>The DEBUGADD() Macro</h2></div></div><div></div></div><p>
 In addition to the kludgey solution to the broken line problem
 described above, there is a clean solution. The DEBUGADD() macro never
 generates a header. It will append new text to the current debug
 message even if the format buffer is empty. The syntax of the
 DEBUGADD() macro is the same as that of the DEBUG() macro.
 </p><pre class="programlisting">
-    DEBUG( 0, (&quot;This is the first line.\n&quot; ) );
-    DEBUGADD( 0, (&quot;This is the second line.\nThis is the third line.\n&quot; ) );
+    DEBUG( 0, ("This is the first line.\n" ) );
+    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );
 </pre><p>Produces</p><pre class="programlisting">
     [1998/07/30 16:00:51, 0] file.c:function(512)
       This is the first line.
       This is the second line.
       This is the third line.
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2799932"></a>The DEBUGLVL() Macro</h2></div></div><div></div></div><p>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801121"></a>The DEBUGLVL() Macro</h2></div></div><div></div></div><p>
 One of the problems with the DEBUG() macro was that DEBUG() lines
 tended to get a bit long. Consider this example from
 nmbd_sendannounce.c:
 </p><pre class="programlisting">
-  DEBUG(3,(&quot;send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n&quot;,
+  DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
             type, global_myname, subrec-&gt;subnet_name, work-&gt;work_group));
 </pre><p>
 One solution to this is to break it down using DEBUG() and DEBUGADD(),
 as follows:
 </p><pre class="programlisting">
-  DEBUG( 3, ( &quot;send_local_master_announcement: &quot; ) );
-  DEBUGADD( 3, ( &quot;type %x for name %s &quot;, type, global_myname ) );
-  DEBUGADD( 3, ( &quot;on subnet %s &quot;, subrec-&gt;subnet_name ) );
-  DEBUGADD( 3, ( &quot;for workgroup %s\n&quot;, work-&gt;work_group ) );
+  DEBUG( 3, ( "send_local_master_announcement: " ) );
+  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
+  DEBUGADD( 3, ( "on subnet %s ", subrec-&gt;subnet_name ) );
+  DEBUGADD( 3, ( "for workgroup %s\n", work-&gt;work_group ) );
 </pre><p>
 A similar, but arguably nicer approach is to use the DEBUGLVL() macro.
 This macro returns True if the message level is less than or equal to
@@ -369,10 +369,10 @@ the global DEBUGLEVEL value, so:
 </p><pre class="programlisting">
   if( DEBUGLVL( 3 ) )
     {
-    dbgtext( &quot;send_local_master_announcement: &quot; );
-    dbgtext( &quot;type %x for name %s &quot;, type, global_myname );
-    dbgtext( &quot;on subnet %s &quot;, subrec-&gt;subnet_name );
-    dbgtext( &quot;for workgroup %s\n&quot;, work-&gt;work_group );
+    dbgtext( "send_local_master_announcement: " );
+    dbgtext( "type %x for name %s ", type, global_myname );
+    dbgtext( "on subnet %s ", subrec-&gt;subnet_name );
+    dbgtext( "for workgroup %s\n", work-&gt;work_group );
     }
 </pre><p>(The dbgtext() function is explained below.)</p><p>There are a few advantages to this scheme:</p><div class="orderedlist"><ol type="1"><li><p>
 The test is performed only once.
@@ -382,7 +382,7 @@ within the DEBUGLVL() block.
 </p></li><li><p>
 Processing that is only relevant to debug output can be contained
 within the DEBUGLVL() block.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800044"></a>New Functions</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800051"></a>dbgtext()</h3></div></div><div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801232"></a>New Functions</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801239"></a>dbgtext()</h3></div></div><div></div></div><p>
 This function prints debug message text to the debug file (and
 possibly to syslog) via the format buffer. The function uses a
 variable argument list just like printf() or Debug1(). The
@@ -391,7 +391,7 @@ and then passed to format_debug_text().
 
 If you use DEBUGLVL() you will probably print the body of the
 message using dbgtext(). 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800071"></a>dbghdr()</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801258"></a>dbghdr()</h3></div></div><div></div></div><p>
 This is the function that writes a debug message header.
 Headers are not processed via the format buffer. Also note that
 if the format buffer is not empty, a call to dbghdr() will not
@@ -399,7 +399,7 @@ produce any output. See the comments in dbghdr() for more info.
 </p><p>
 It is not likely that this function will be called directly. It
 is used by DEBUG() and DEBUGADD().
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800094"></a>format_debug_text()</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801281"></a>format_debug_text()</h3></div></div><div></div></div><p>
 This is a static function in debug.c. It stores the output text
 for the body of the message in a buffer until it encounters a
 newline. When the newline character is found, the buffer is
@@ -481,7 +481,7 @@ Here are some other suggestions:
 	reason: consistency
 </p></li><li><p>
 	don't explicitly extern functions (they are autogenerated by 
-	&quot;make proto&quot; into proto.h)
+	"make proto" into proto.h)
 	reason: consistency
 </p></li><li><p>
 	use endian safe macros when unpacking SMBs (see byteorder.h and
@@ -550,7 +550,7 @@ The suggestions above are simply that, suggestions, but the information may
 help in reducing the routine rework done on new code.  The preceeding list
 is expected to change routinely as new support routines and macros are
 added.
-</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter�5.�Samba Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Chappell</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:David.Chappell@mail.trincoll.edu">David.Chappell@mail.trincoll.edu</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 May 1996</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2800556">Character Handling</a></dt><dt><a href="#id2800582">The new functions</a></dt><dt><a href="#id2800742">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2800755">CVAL(buf,pos)</a></dt><dt><a href="#id2800769">PVAL(buf,pos)</a></dt><dt><a href="#id2800783">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2800795">SVAL(buf,pos)</a></dt><dt><a href="#id2800815">IVAL(buf,pos)</a></dt><dt><a href="#id2800829">SVALS(buf,pos)</a></dt><dt><a href="#id2800844">IVALS(buf,pos)</a></dt><dt><a href="#id2800858">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2800872">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2800887">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2800901">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2800916">RSVAL(buf,pos)</a></dt><dt><a href="#id2800930">RIVAL(buf,pos)</a></dt><dt><a href="#id2800944">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2866314">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2866329">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2866366">Parameters</a></dt><dt><a href="#id2866517">Return value</a></dt></dl></dd><dt><a href="#id2866617">Code character table</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800556"></a>Character Handling</h2></div></div><div></div></div><p>
+</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="internals"></a>Chapter�5.�Samba Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Chappell</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:David.Chappell@mail.trincoll.edu">David.Chappell@mail.trincoll.edu</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 May 1996</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2801753">Character Handling</a></dt><dt><a href="#id2801778">The new functions</a></dt><dt><a href="#id2801936">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2801949">CVAL(buf,pos)</a></dt><dt><a href="#id2801963">PVAL(buf,pos)</a></dt><dt><a href="#id2801977">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2801990">SVAL(buf,pos)</a></dt><dt><a href="#id2802006">IVAL(buf,pos)</a></dt><dt><a href="#id2802020">SVALS(buf,pos)</a></dt><dt><a href="#id2802035">IVALS(buf,pos)</a></dt><dt><a href="#id2802049">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2802063">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2802078">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2802092">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2802106">RSVAL(buf,pos)</a></dt><dt><a href="#id2802121">RIVAL(buf,pos)</a></dt><dt><a href="#id2802135">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2802150">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2802166">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2802202">Parameters</a></dt><dt><a href="#id2866095">Return value</a></dt></dl></dd><dt><a href="#id2866180">Code character table</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801753"></a>Character Handling</h2></div></div><div></div></div><p>
 This section describes character set handling in Samba, as implemented in
 Samba 3.0 and above
 </p><p>
@@ -560,12 +560,12 @@ strings to/from DOS codepages. The problem is that there was no way of
 telling if a particular char* is in dos codepage or unix
 codepage. This led to a nightmare of code that tried to cope with
 particular cases without handlingt the general case.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800582"></a>The new functions</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801778"></a>The new functions</h2></div></div><div></div></div><p>
 The new system works like this:
 </p><div class="orderedlist"><ol type="1"><li><p>
-	all char* strings inside Samba are &quot;unix&quot; strings. These are
-	multi-byte strings that are in the charset defined by the &quot;unix
-	charset&quot; option in smb.conf. 
+	all char* strings inside Samba are "unix" strings. These are
+	multi-byte strings that are in the charset defined by the "unix
+	charset" option in smb.conf. 
 </p></li><li><p>
 	there is no single fixed character set for unix strings, but any
 	character set that is used does need the following properties:
@@ -618,32 +618,32 @@ The new system works like this:
 	like strchr_m(). I know this is very slow, and we will eventually
 	speed it up but right now we want this stuff correct not fast.
 </p></li><li><p>
-	all lp_ functions now return unix strings. The magic &quot;DOS&quot; flag on
+	all lp_ functions now return unix strings. The magic "DOS" flag on
 	parameters is gone.
 </p></li><li><p>
 	all vfs functions take unix strings. Don't convert when passing to them
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800742"></a>Macros in byteorder.h</h2></div></div><div></div></div><p>
+</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801936"></a>Macros in byteorder.h</h2></div></div><div></div></div><p>
 This section describes the macros defined in byteorder.h.  These macros 
 are used extensively in the Samba code.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800755"></a>CVAL(buf,pos)</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801949"></a>CVAL(buf,pos)</h3></div></div><div></div></div><p>
 returns the byte at offset pos within buffer buf as an unsigned character.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800769"></a>PVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of CVAL(buf,pos) cast to type unsigned integer.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800783"></a>SCVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the byte at offset pos within buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800795"></a>SVAL(buf,pos)</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801963"></a>PVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of CVAL(buf,pos) cast to type unsigned integer.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801977"></a>SCVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the byte at offset pos within buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2801990"></a>SVAL(buf,pos)</h3></div></div><div></div></div><p>
 	returns the value of the unsigned short (16 bit) little-endian integer at 
 	offset pos within buffer buf.  An integer of this type is sometimes
-	refered to as &quot;USHORT&quot;.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800815"></a>IVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned 32 bit little-endian integer at offset 
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800829"></a>SVALS(buf,pos)</h3></div></div><div></div></div><p>returns the value of the signed short (16 bit) little-endian integer at 
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800844"></a>IVALS(buf,pos)</h3></div></div><div></div></div><p>returns the value of the signed 32 bit little-endian integer at offset pos
-within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800858"></a>SSVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the unsigned short (16 bit) little-endian integer at offset pos within 
-buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800872"></a>SIVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the unsigned 32 bit little-endian integer at offset pos within buffer 
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800887"></a>SSVALS(buf,pos,val)</h3></div></div><div></div></div><p>sets the short (16 bit) signed little-endian integer at offset pos within 
-buffer buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800901"></a>SIVALS(buf,pos,val)</h3></div></div><div></div></div><p>sets the signed 32 bit little-endian integer at offset pos withing buffer
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800916"></a>RSVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned short (16 bit) big-endian integer at 
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800930"></a>RIVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned 32 bit big-endian integer at offset 
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2800944"></a>RSSVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the value of the unsigned short (16 bit) big-endian integer at 
+	refered to as "USHORT".
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802006"></a>IVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned 32 bit little-endian integer at offset 
+pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802020"></a>SVALS(buf,pos)</h3></div></div><div></div></div><p>returns the value of the signed short (16 bit) little-endian integer at 
+offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802035"></a>IVALS(buf,pos)</h3></div></div><div></div></div><p>returns the value of the signed 32 bit little-endian integer at offset pos
+within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802049"></a>SSVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the unsigned short (16 bit) little-endian integer at offset pos within 
+buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802063"></a>SIVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the unsigned 32 bit little-endian integer at offset pos within buffer 
+buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802078"></a>SSVALS(buf,pos,val)</h3></div></div><div></div></div><p>sets the short (16 bit) signed little-endian integer at offset pos within 
+buffer buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802092"></a>SIVALS(buf,pos,val)</h3></div></div><div></div></div><p>sets the signed 32 bit little-endian integer at offset pos withing buffer
+buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802106"></a>RSVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned short (16 bit) big-endian integer at 
+offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802121"></a>RIVAL(buf,pos)</h3></div></div><div></div></div><p>returns the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802135"></a>RSSVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the value of the unsigned short (16 bit) big-endian integer at 
 offset pos within buffer buf to value val.
-refered to as &quot;USHORT&quot;.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866314"></a>RSIVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the value of the unsigned 32 bit big-endian integer at offset 
-pos within buffer buf to value val.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866329"></a>LAN Manager Samba API</h2></div></div><div></div></div><p>
+refered to as "USHORT".</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802150"></a>RSIVAL(buf,pos,val)</h3></div></div><div></div></div><p>sets the value of the unsigned 32 bit big-endian integer at offset 
+pos within buffer buf to value val.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2802166"></a>LAN Manager Samba API</h2></div></div><div></div></div><p>
 This section describes the functions need to make a LAN Manager RPC call.
 This information had been obtained by examining the Samba code and the LAN
 Manager 2.0 API documentation.  It should not be considered entirely
@@ -656,7 +656,7 @@ call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,
 </p><p>
 This function is defined in client.c.  It uses an SMB transaction to call a
 remote api.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866366"></a>Parameters</h3></div></div><div></div></div><p>The parameters are as follows:</p><div class="orderedlist"><ol type="1"><li><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802202"></a>Parameters</h3></div></div><div></div></div><p>The parameters are as follows:</p><div class="orderedlist"><ol type="1"><li><p>
 	prcnt: the number of bytes of parameters begin sent.
 </p></li><li><p>
 	drcnt:   the number of bytes of data begin sent.
@@ -689,8 +689,8 @@ in the manual, not the data which is actually passed.
 An ASCIIZ string describing the data structure which ought to be returned.
 </p></li><li><p>
 Any parameters which appear in the function call, as defined in the LAN
-Manager API documentation, after the &quot;Server&quot; and up to and including the
-&quot;uLevel&quot; parameters.
+Manager API documentation, after the "Server" and up to and including the
+"uLevel" parameters.
 </p></li><li><p>
 An unsigned 16 bit integer which gives the size in bytes of the buffer we
 will use to receive the returned array of data structures.  Presumably this
@@ -701,7 +701,7 @@ substructures apply, this string is of zero length.
 </p></li></ol></div><p>
 The code in client.c always calls call_api() with no data.  It is unclear
 when a non-zero length data buffer would be sent.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866517"></a>Return value</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866095"></a>Return value</h3></div></div><div></div></div><p>
 The returned parameters (pointed to by rparam), in their order of appearance
 are:</p><div class="orderedlist"><ol type="1"><li><p>
 An unsigned 16 bit integer which contains the API function's return code. 
@@ -718,9 +718,9 @@ It is also possible that this may sometimes be the number of bytes returned.
 </p></li></ol></div><p>
 When call_api() returns, rparam points to the returned parameters.  The
 first if these is the result code.  It will be zero if the API call
-suceeded.  This value by be read with &quot;SVAL(rparam,0)&quot;.
+suceeded.  This value by be read with "SVAL(rparam,0)".
 </p><p>
-The second parameter may be read as &quot;SVAL(rparam,2)&quot;.  It is a 16 bit offset
+The second parameter may be read as "SVAL(rparam,2)".  It is a 16 bit offset
 which indicates what the base address of the returned data buffer was when
 it was built on the server.  It should be used to correct pointer before
 use.
@@ -729,10 +729,10 @@ The returned data buffer contains the array of returned data structures.
 Note that all pointers must be adjusted before use.  The function
 fix_char_ptr() in client.c can be used for this purpose.
 </p><p>
-The third parameter (which may be read as &quot;SVAL(rparam,4)&quot;) has something to
+The third parameter (which may be read as "SVAL(rparam,4)") has something to
 do with indicating the amount of data returned or possibly the amount of
 data which can be returned if enough buffer space is allowed.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866617"></a>Code character table</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866180"></a>Code character table</h2></div></div><div></div></div><p>
 Certain data structures are described by means of ASCIIz strings containing
 code characters.  These are the code characters:
 </p><div class="orderedlist"><ol type="1"><li><p>
@@ -755,7 +755,7 @@ r	pointer to returned data buffer???
 L	length in bytes of returned data buffer???
 </p></li><li><p>
 h	number of bytes of information available???
-</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="parsing"></a>Chapter�6.�The smb.conf file</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">November 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866736">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2866826">Handling of Whitespace</a></dt><dt><a href="#id2866883">Handling of Line Continuation</a></dt><dt><a href="#id2866948">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2867044">Syntax</a></dt><dd><dl><dt><a href="#id2867117">About params.c</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866736"></a>Lexical Analysis</h2></div></div><div></div></div><p>
+</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="parsing"></a>Chapter�6.�The smb.conf file</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Chris</span> <span class="surname">Hertel</span></h3></div></div><div><p class="pubdate">November 1997</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866300">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2866391">Handling of Whitespace</a></dt><dt><a href="#id2866447">Handling of Line Continuation</a></dt><dt><a href="#id2866511">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2866608">Syntax</a></dt><dd><dl><dt><a href="#id2866679">About params.c</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866300"></a>Lexical Analysis</h2></div></div><div></div></div><p>
 Basically, the file is processed on a line by line basis.  There are
 four types of lines that are recognized by the lexical analyzer
 (params.c):
@@ -782,7 +782,7 @@ ignores them.  The latter two line types are scanned for
 These are the only tokens passed to the parameter loader
 (loadparm.c).  Parameter names and values are divided from one
 another by an equal sign: '='.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866826"></a>Handling of Whitespace</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866391"></a>Handling of Whitespace</h3></div></div><div></div></div><p>
 Whitespace is defined as all characters recognized by the isspace()
 function (see ctype(3C)) except for the newline character ('\n')
 The newline is excluded because it identifies the end of the line.
@@ -797,7 +797,7 @@ the exception of carriage return characters ('\r'), all of which
 are removed.
 </p></li><li><p>
 Leading and trailing whitespace is removed from names and values.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866883"></a>Handling of Line Continuation</h3></div></div><div></div></div><p>
+</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866447"></a>Handling of Line Continuation</h3></div></div><div></div></div><p>
 Long section header and parameter lines may be extended across
 multiple lines by use of the backslash character ('\\').  Line
 continuation is ignored for blank and comment lines.
@@ -820,7 +820,7 @@ line, plus the four preceeding the word 'with' in the second line.
 Line continuation characters are ignored on blank lines and at the end
 of comments.  They are *only* recognized within section and parameter
 lines.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866948"></a>Line Continuation Quirks</h3></div></div><div></div></div><p>Note the following example:</p><pre class="programlisting">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866511"></a>Line Continuation Quirks</h3></div></div><div></div></div><p>Note the following example:</p><pre class="programlisting">
 	param name = parameter value string \
     \
     with line continuation.
@@ -844,7 +844,7 @@ terminating character, and the rest of the line is ignored.  The lines
 </pre><p>are read as</p><pre class="programlisting">
 	[section name]
     param name = value
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867044"></a>Syntax</h2></div></div><div></div></div><p>The syntax of the smb.conf file is as follows:</p><pre class="programlisting">
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866608"></a>Syntax</h2></div></div><div></div></div><p>The syntax of the smb.conf file is as follows:</p><pre class="programlisting">
   &lt;file&gt;            :==  { &lt;section&gt; } EOF
   &lt;section&gt;         :==  &lt;section header&gt; { &lt;parameter line&gt; }
   &lt;section header&gt;  :==  '[' NAME ']'
@@ -863,12 +863,12 @@ terminating character, and the rest of the line is ignored.  The lines
 	A parameter line is divided into a NAME and a VALUE.  The *first*
 	equal sign on the line separates the NAME from the VALUE.  The
 	VALUE is terminated by a newline character (NL = '\n').
-</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867117"></a>About params.c</h3></div></div><div></div></div><p>
+</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866679"></a>About params.c</h3></div></div><div></div></div><p>
 The parsing of the config file is a bit unusual if you are used to
 lex, yacc, bison, etc.  Both lexical analysis (scanning) and parsing
 are performed by params.c.  Values are loaded via callbacks to
 loadparm.c.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unix-smb"></a>Chapter�7.�NetBIOS in a Unix World</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3></div></div><div><p class="pubdate">April 1995</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867166">Introduction</a></dt><dt><a href="#id2867191">Usernames</a></dt><dt><a href="#id2867277">File Ownership</a></dt><dt><a href="#id2867326">Passwords</a></dt><dt><a href="#id2867388">Locking</a></dt><dt><a href="#id2867458">Deny Modes</a></dt><dt><a href="#id2867499">Trapdoor UIDs</a></dt><dt><a href="#id2867526">Port numbers</a></dt><dt><a href="#id2867572">Protocol Complexity</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867166"></a>Introduction</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unix-smb"></a>Chapter�7.�NetBIOS in a Unix World</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3></div></div><div><p class="pubdate">April 1995</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866728">Introduction</a></dt><dt><a href="#id2866753">Usernames</a></dt><dt><a href="#id2866834">File Ownership</a></dt><dt><a href="#id2866872">Passwords</a></dt><dt><a href="#id2866916">Locking</a></dt><dt><a href="#id2866978">Deny Modes</a></dt><dt><a href="#id2867009">Trapdoor UIDs</a></dt><dt><a href="#id2867034">Port numbers</a></dt><dt><a href="#id2867088">Protocol Complexity</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866728"></a>Introduction</h2></div></div><div></div></div><p>
 This is a short document that describes some of the issues that
 confront a SMB implementation on unix, and how Samba copes with
 them. They may help people who are looking at unix&lt;-&gt;PC
@@ -876,7 +876,7 @@ interoperability.
 </p><p>
 It was written to help out a person who was writing a paper on unix to
 PC connectivity.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867191"></a>Usernames</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866753"></a>Usernames</h2></div></div><div></div></div><p>
 The SMB protocol has only a loose username concept. Early SMB
 protocols (such as CORE and COREPLUS) have no username concept at
 all. Even in later protocols clients often attempt operations
@@ -887,20 +887,20 @@ Unix security is based around username/password pairs. A unix box
 should not allow clients to do any substantive operation without some
 sort of validation. 
 </p><p>
-The problem mostly manifests itself when the unix server is in &quot;share
-level&quot; security mode. This is the default mode as the alternative
-&quot;user level&quot; security mode usually forces a client to connect to the
+The problem mostly manifests itself when the unix server is in "share
+level" security mode. This is the default mode as the alternative
+"user level" security mode usually forces a client to connect to the
 server as the same user for each connected share, which is
 inconvenient in many sites.
 </p><p>
-In &quot;share level&quot; security the client normally gives a username in the
-&quot;session setup&quot; protocol, but does not supply an accompanying
-password. The client then connects to resources using the &quot;tree
-connect&quot; protocol, and supplies a password. The problem is that the
+In "share level" security the client normally gives a username in the
+"session setup" protocol, but does not supply an accompanying
+password. The client then connects to resources using the "tree
+connect" protocol, and supplies a password. The problem is that the
 user on the PC types the username and the password in different
 contexts, unaware that they need to go together to give access to the
 server. The username is normally the one the user typed in when they
-&quot;logged onto&quot; the PC (this assumes Windows for Workgroups). The
+"logged onto" the PC (this assumes Windows for Workgroups). The
 password is the one they chose when connecting to the disk or printer.
 </p><p>
 The user often chooses a totally different username for their login as
@@ -913,9 +913,9 @@ in the vast majority of cases. The methods include username maps, the
 service%user syntax, the saving of session setup usernames for later
 validation and the derivation of the username from the service name
 (either directly or via the user= option).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867277"></a>File Ownership</h2></div></div><div></div></div><p>
-The commonly used SMB protocols have no way of saying &quot;you can't do
-that because you don't own the file&quot;. They have, in fact, no concept
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866834"></a>File Ownership</h2></div></div><div></div></div><p>
+The commonly used SMB protocols have no way of saying "you can't do
+that because you don't own the file". They have, in fact, no concept
 of file ownership at all.
 </p><p>
 This brings up all sorts of interesting problems. For example, when
@@ -925,13 +925,13 @@ receive the wrong date. This is because the utime() call under unix
 only succeeds for the owner of the file, or root, even if the file is
 world writeable. For security reasons Samba does all file operations
 as the validated user, not root, so the utime() fails. This can stuff
-up shared development diectories as programs like &quot;make&quot; will not get
+up shared development diectories as programs like "make" will not get
 file time comparisons right.
 </p><p>
 There are several possible solutions to this problem, including
 username mapping, and forcing a specific username for particular
 shares.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867326"></a>Passwords</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866872"></a>Passwords</h2></div></div><div></div></div><p>
 Many SMB clients uppercase passwords before sending them. I have no
 idea why they do this. Interestingly WfWg uppercases the password only
 if the server is running a protocol greater than COREPLUS, so
@@ -940,20 +940,20 @@ obviously it isn't just the data entry routines that are to blame.
 Unix passwords are case sensitive. So if users use mixed case
 passwords they are in trouble.
 </p><p>
-Samba can try to cope with this by either using the &quot;password level&quot;
+Samba can try to cope with this by either using the "password level"
 option which causes Samba to try the offered password with up to the
-specified number of case changes, or by using the &quot;password server&quot;
+specified number of case changes, or by using the "password server"
 option which allows Samba to do its validation via another machine
 (typically a WinNT server).
 </p><p>
 Samba supports the password encryption method used by SMB
 clients. Note that the use of password encryption in Microsoft
-networking leads to password hashes that are &quot;plain text equivalent&quot;.
+networking leads to password hashes that are "plain text equivalent".
 This means that it is *VERY* important to ensure that the Samba
 smbpasswd file containing these password hashes is only readable
 by the root user. See the documentation ENCRYPTION.txt for more
 details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867388"></a>Locking</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866916"></a>Locking</h2></div></div><div></div></div><p>
 Since samba 2.2, samba supports other types of locking as well. This 
 section is outdated.
 </p><p>
@@ -978,14 +978,14 @@ a unix environment because few unix programs use byte range
 locking. The stress of huge numbers of lock requests from dos/windows
 clients can kill the daemon on some systems.
 </p><p>
-The second major problem is the &quot;opportunistic locking&quot; requested by
+The second major problem is the "opportunistic locking" requested by
 some clients. If a client requests opportunistic locking then it is
 asking the server to notify it if anyone else tries to do something on
 the same file, at which time the client will say if it is willing to
 give up its lock. Unix has no simple way of implementing
 opportunistic locking, and currently Samba has no support for it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867458"></a>Deny Modes</h2></div></div><div></div></div><p>
-When a SMB client opens a file it asks for a particular &quot;deny mode&quot; to
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866978"></a>Deny Modes</h2></div></div><div></div></div><p>
+When a SMB client opens a file it asks for a particular "deny mode" to
 be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE,
 DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be
 allowed by anyone else who tries to use the file at the same time. If
@@ -998,7 +998,7 @@ directory or a shared memory implementation. The lock file method
 is clumsy and consumes processing and file resources,
 the shared memory implementation is vastly prefered and is turned on
 by default for those systems that support it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867499"></a>Trapdoor UIDs</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867009"></a>Trapdoor UIDs</h2></div></div><div></div></div><p>
 A SMB session can run with several uids on the one socket. This
 happens when a user connects to two shares with different
 usernames. To cope with this the unix server needs to switch uids
@@ -1006,11 +1006,11 @@ within the one process. On some unixes (such as SCO) this is not
 possible. This means that on those unixes the client is restricted to
 a single uid.
 </p><p>
-Note that you can also get the &quot;trapdoor uid&quot; message for other
+Note that you can also get the "trapdoor uid" message for other
 reasons. Please see the FAQ for details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867526"></a>Port numbers</h2></div></div><div></div></div><p>
-There is a convention that clients on sockets use high &quot;unprivilaged&quot;
-port numbers (&gt;1000) and connect to servers on low &quot;privilaged&quot; port
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867034"></a>Port numbers</h2></div></div><div></div></div><p>
+There is a convention that clients on sockets use high "unprivilaged"
+port numbers (&gt;1000) and connect to servers on low "privilaged" port
 numbers. This is enforced in Unix as non-root users can't open a
 socket for listening on port numbers less than 1000.
 </p><p>
@@ -1031,13 +1031,13 @@ to any of these OSes unless they are running as root. The answer comes
 back, but it goes to port 137 which the unix user can't listen
 on. Interestingly WinNT3.1 got this right - it sends node status
 responses back to the source port in the request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867572"></a>Protocol Complexity</h2></div></div><div></div></div><p>
-There are many &quot;protocol levels&quot; in the SMB protocol. It seems that
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867088"></a>Protocol Complexity</h2></div></div><div></div></div><p>
+There are many "protocol levels" in the SMB protocol. It seems that
 each time new functionality was added to a Microsoft operating system,
 they added the equivalent functions in a new protocol level of the SMB
-protocol to &quot;externalise&quot; the new capabilities.
+protocol to "externalise" the new capabilities.
 </p><p>
-This means the protocol is very &quot;rich&quot;, offering many ways of doing
+This means the protocol is very "rich", offering many ways of doing
 each file operation. This means SMB servers need to be complex and
 large. It also means it is very difficult to make them bug free. It is
 not just Samba that suffers from this problem, other servers such as
@@ -1045,19 +1045,19 @@ WinNT don't support every variation of every call and it has almost
 certainly been a headache for MS developers to support the myriad of
 SMB calls that are available.
 </p><p>
-There are about 65 &quot;top level&quot; operations in the SMB protocol (things
+There are about 65 "top level" operations in the SMB protocol (things
 like SMBread and SMBwrite). Some of these include hundreds of
 sub-functions (SMBtrans has at least 120 sub-functions, like
 DosPrintQAdd and NetSessionEnum). All of them take several options
 that can change the way they work. Many take dozens of possible
-&quot;information levels&quot; that change the structures that need to be
-returned. Samba supports all but 2 of the &quot;top level&quot; functions. It
+"information levels" that change the structures that need to be
+returned. Samba supports all but 2 of the "top level" functions. It
 supports only 8 (so far) of the SMBtrans sub-functions. Even NT
 doesn't support them all.
 </p><p>
-Samba currently supports up to the &quot;NT LM 0.12&quot; protocol, which is the
+Samba currently supports up to the "NT LM 0.12" protocol, which is the
 one preferred by Win95 and WinNT3.5. Luckily this protocol level has a
-&quot;capabilities&quot; field which specifies which super-duper new-fangled
+"capabilities" field which specifies which super-duper new-fangled
 options the server suports. This helps to make the implementation of
 this protocol level much easier.
 </p><p>
@@ -1102,13 +1102,13 @@ You'll notice that it produces a LOT of output. It is showing you the
 arguments to every system call that the program makes and the
 result. Very little happens in a program without a system call so you
 get lots of output. You'll also find that it produces a lot of
-&quot;preamble&quot; stuff showing the loading of shared libraries etc. Ignore
+"preamble" stuff showing the loading of shared libraries etc. Ignore
 this (unless its going wrong!)
 </p><p>
 For example, the only line that really matters in the <b class="command">strace echo
 hello</b> output is:
 </p><pre class="programlisting">
-write(1, &quot;hello\n&quot;, 6)                  = 6
+write(1, "hello\n", 6)                  = 6
 </pre><p>all the rest is just setting up to run the program.</p><p>
 Ok, now you're familiar with strace. To use it on Samba you need to
 strace the running smbd daemon. The way I tend ot use it is to first
@@ -1118,10 +1118,10 @@ find which process ID that client is attached to, then as root I do
 stderr output from this command to a file for later perusal. For
 example, if I'm using a csh style shell:
 </p><p><b class="command">strace -f -p 3872 &gt;&amp; strace.out</b></p><p>or with a sh style shell:</p><p><b class="command">strace -f -p 3872 &gt; strace.out 2&gt;&amp;1</b></p><p>
-Note the &quot;-f&quot; option. This is only available on some systems, and
+Note the "-f" option. This is only available on some systems, and
 allows you to trace not just the current process, but any children it
 forks. This is great for finding printing problems caused by the
-&quot;print command&quot; being wrong.
+"print command" being wrong.
 </p><p>
 Once you are attached you then can do whatever it is on the client
 that is causing problems and you will capture all the system calls
@@ -1132,20 +1132,20 @@ output for strings that I know will appear when the problem
 happens. For example, if I am having touble with permissions on a file
 I would search for that files name in the strace output and look at
 the surrounding lines. Another trick is to match up file descriptor
-numbers and &quot;follow&quot; what happens to an open file until it is closed.
+numbers and "follow" what happens to an open file until it is closed.
 </p><p>
 Beyond this you will have to use your initiative. To give you an idea
 of what you are looking for here is a piece of strace output that
 shows that <tt class="filename">/dev/null</tt> is not world writeable, which
 causes printing to fail with Samba:
 </p><pre class="programlisting">
-[pid 28268] open(&quot;/dev/null&quot;, O_RDWR)   = -1 EACCES (Permission denied)
-[pid 28268] open(&quot;/dev/null&quot;, O_WRONLY) = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)
 </pre><p>
 The process is trying to first open <tt class="filename">/dev/null</tt> read-write 
 then read-only. Both fail. This means <tt class="filename">/dev/null</tt> has 
 incorrect permissions.
-</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="windows-debug"></a>Chapter�9.�Finding useful information on windows</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867998">Netlogon debugging output</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867998"></a>Netlogon debugging output</h2></div></div><div></div></div><div class="procedure"><ol type="1"><li><p>stop netlogon service on PDC</p></li><li><p>rename original netlogon.dll to netlogon.dll.original</p></li><li><p>copy checked version of netlogon.dll to system32 directory</p></li><li><p>set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag to 0x20000004</p></li><li><p>start netlogon service on PDC</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntdomain"></a>Chapter�10.�NT Domain RPC's</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:lkcl@switchboard.net">lkcl@switchboard.net</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Ashton</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:paul@argo.demon.co.uk">paul@argo.demon.co.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Duncan</span> <span class="surname">Stansfield</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:duncans@sco.com">duncans@sco.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">01 November 97(version 0.0.24)</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2868139">Introduction</a></dt><dd><dl><dt><a href="#id2868342">Sources</a></dt><dt><a href="#id2868377">Credits</a></dt></dl></dd><dt><a href="#id2868416">Notes and Structures</a></dt><dd><dl><dt><a href="#id2868423">Notes</a></dt><dt><a href="#id2868506">Enumerations</a></dt><dt><a href="#id2868718">Structures</a></dt></dl></dd><dt><a href="#id2871669">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2871682">MSRPC Pipes</a></dt><dt><a href="#id2871787">Header</a></dt><dt><a href="#id2872660">Tail</a></dt><dt><a href="#id2872706">RPC Bind / Bind Ack</a></dt><dt><a href="#id2872896">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2873062">LSA Open Policy</a></dt><dt><a href="#id2873187">LSA Query Info Policy</a></dt><dt><a href="#id2873296">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2873387">LSA Open Secret</a></dt><dt><a href="#id2873498">LSA Close</a></dt><dt><a href="#id2873564">LSA Lookup SIDS</a></dt><dt><a href="#id2873773">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2873999">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2874162">LSA Request Challenge</a></dt><dt><a href="#id2874296">LSA Authenticate 2</a></dt><dt><a href="#id2874444">LSA Server Password Set</a></dt><dt><a href="#id2874559">LSA SAM Logon</a></dt><dt><a href="#id2874662">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2874755">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2874774">Query for PDC</a></dt><dt><a href="#id2875034">SAM Logon</a></dt></dl></dd><dt><a href="#id2875360">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2875405">Net Share Enum</a></dt><dt><a href="#id2875625">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2875741">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2875749">Definitions</a></dt><dt><a href="#id2875911">Protocol</a></dt><dt><a href="#id2876010">Comments</a></dt></dl></dd><dt><a href="#id2876057">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2876097">Well-known SIDs</a></dt><dt><a href="#id2876412">Well-known RIDS</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868139"></a>Introduction</h2></div></div><div></div></div><p>
+</p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="windows-debug"></a>Chapter�9.�Finding useful information on windows</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867492">Netlogon debugging output</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867492"></a>Netlogon debugging output</h2></div></div><div></div></div><div class="procedure"><ol type="1"><li><p>stop netlogon service on PDC</p></li><li><p>rename original netlogon.dll to netlogon.dll.original</p></li><li><p>copy checked version of netlogon.dll to system32 directory</p></li><li><p>set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag to 0x20000004</p></li><li><p>start netlogon service on PDC</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ntdomain"></a>Chapter�10.�NT Domain RPC's</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Luke</span> <span class="surname">Leighton</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:lkcl@switchboard.net">lkcl@switchboard.net</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Ashton</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:paul@argo.demon.co.uk">paul@argo.demon.co.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Duncan</span> <span class="surname">Stansfield</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:duncans@sco.com">duncans@sco.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">01 November 97(version 0.0.24)</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867633">Introduction</a></dt><dd><dl><dt><a href="#id2867832">Sources</a></dt><dt><a href="#id2867868">Credits</a></dt></dl></dd><dt><a href="#id2867906">Notes and Structures</a></dt><dd><dl><dt><a href="#id2867913">Notes</a></dt><dt><a href="#id2867989">Enumerations</a></dt><dt><a href="#id2868203">Structures</a></dt></dl></dd><dt><a href="#id2871153">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2871166">MSRPC Pipes</a></dt><dt><a href="#id2871268">Header</a></dt><dt><a href="#id2872139">Tail</a></dt><dt><a href="#id2872184">RPC Bind / Bind Ack</a></dt><dt><a href="#id2872365">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2872530">LSA Open Policy</a></dt><dt><a href="#id2872655">LSA Query Info Policy</a></dt><dt><a href="#id2872763">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2872853">LSA Open Secret</a></dt><dt><a href="#id2872963">LSA Close</a></dt><dt><a href="#id2873028">LSA Lookup SIDS</a></dt><dt><a href="#id2873238">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2873464">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2873625">LSA Request Challenge</a></dt><dt><a href="#id2873759">LSA Authenticate 2</a></dt><dt><a href="#id2873906">LSA Server Password Set</a></dt><dt><a href="#id2874022">LSA SAM Logon</a></dt><dt><a href="#id2874125">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2874216">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2874229">Query for PDC</a></dt><dt><a href="#id2874497">SAM Logon</a></dt></dl></dd><dt><a href="#id2874822">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2874867">Net Share Enum</a></dt><dt><a href="#id2875087">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2875203">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2875211">Definitions</a></dt><dt><a href="#id2875373">Protocol</a></dt><dt><a href="#id2875471">Comments</a></dt></dl></dd><dt><a href="#id2875519">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2875558">Well-known SIDs</a></dt><dt><a href="#id2875874">Well-known RIDS</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867633"></a>Introduction</h2></div></div><div></div></div><p>
 This document contains information to provide an NT workstation with login
 services, without the need for an NT server. It is the sgml version of <a href="http://mailhost.cb1.com/~lkcl/cifsntdomain.txt" target="_top">http://mailhost.cb1.com/~lkcl/cifsntdomain.txt</a>, controlled by Luke.
 </p><p>
@@ -1178,7 +1178,7 @@ NT workstation, and enabling full debugging in NETLOGON.  This is
 achieved by setting the following REG_SZ registry key to 0x1ffffff:
 </p><p><tt class="filename">HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters</tt></p><p><span class="emphasis"><em>Incorrect direct editing of the registry can cause your
 machine to fail. Then again, so can incorrect implementation of this 
-protocol. See &quot;Liability:&quot; above.</em></span></p><p>
+protocol. See "Liability:" above.</em></span></p><p>
 Bear in mind that each packet over-the-wire will have its origin in an
 API call.  Therefore, there are likely to be structures, enumerations
 and defines that are usefully documented elsewhere.
@@ -1191,12 +1191,12 @@ Failure to return this error code will make the workstation report
 that it is already a member of the domain.</p></li><li><p>the cryptographic side of the NetrServerPasswordSet command, 
 which would allow the workstation to change its password.  This password is
 used to generate the long-term session key.  [It is possible to reject this
-command, and keep the default workstation password].</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868342"></a>Sources</h3></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>cket Traces from Netmonitor (Service Pack 1 and above)</td></tr><tr><td>ul Ashton and Luke Leighton's other &quot;NT Domain&quot; doc.</td></tr><tr><td>FS documentation - cifs6.txt</td></tr><tr><td>FS documentation - cifsrap2.txt</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868377"></a>Credits</h3></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</td></tr><tr><td>Duncan Stansfield: low-level analysis of MSRPC Pipes.</td></tr><tr><td>Linus Nordberg: producing c-code from Paul's crypto spec.</td></tr><tr><td>Windows Sourcer development team</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868416"></a>Notes and Structures</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868423"></a>Notes</h3></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p>
-In the SMB Transact pipes, some &quot;Structures&quot;, described here, appear to be
+command, and keep the default workstation password].</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867832"></a>Sources</h3></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>cket Traces from Netmonitor (Service Pack 1 and above)</td></tr><tr><td>ul Ashton and Luke Leighton's other "NT Domain" doc.</td></tr><tr><td>FS documentation - cifs6.txt</td></tr><tr><td>FS documentation - cifsrap2.txt</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867868"></a>Credits</h3></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</td></tr><tr><td>Duncan Stansfield: low-level analysis of MSRPC Pipes.</td></tr><tr><td>Linus Nordberg: producing c-code from Paul's crypto spec.</td></tr><tr><td>Windows Sourcer development team</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867906"></a>Notes and Structures</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867913"></a>Notes</h3></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p>
+In the SMB Transact pipes, some "Structures", described here, appear to be
 4-byte aligned with the SMB header, at their start.  Exactly which
-&quot;Structures&quot; need aligning is not precisely known or documented.
+"Structures" need aligning is not precisely known or documented.
 </p></li><li><p>
-In the UDP NTLOGON Mailslots, some &quot;Structures&quot;, described here, appear to be
+In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be
 2-byte aligned with the start of the mailslot, at their start.
 </p></li><li><p>
 Domain SID is of the format S-revision-version-auth1-auth2...authN.
@@ -1219,15 +1219,15 @@ into or taken out of the SMB data stream.  if the count is non-zero, then
 the pointer is also non-zero.  immediately following the pointer is the
 count again, followed by an array of container sub-structures.  the count
 appears a third time after the last sub-structure.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868506"></a>Enumerations</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868513"></a>MSRPC Header type</h4></div></div><div></div></div><p>command number in the msrpc packet header</p><div class="variablelist"><dl><dt><span class="term">MSRPC_Request:</span></dt><dd><p>0x00</p></dd><dt><span class="term">MSRPC_Response:</span></dt><dd><p>0x02</p></dd><dt><span class="term">MSRPC_Bind:</span></dt><dd><p>0x0B</p></dd><dt><span class="term">MSRPC_BindAck:</span></dt><dd><p>0x0C</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868587"></a>MSRPC Packet info</h4></div></div><div></div></div><p>The meaning of these flags is undocumented</p><div class="variablelist"><dl><dt><span class="term">FirstFrag:</span></dt><dd><p>0x01 </p></dd><dt><span class="term">LastFrag:</span></dt><dd><p>0x02 </p></dd><dt><span class="term">NotaFrag:</span></dt><dd><p>0x04  </p></dd><dt><span class="term">RecRespond:</span></dt><dd><p>0x08  </p></dd><dt><span class="term">NoMultiplex:</span></dt><dd><p>0x10  </p></dd><dt><span class="term">NotForIdemp:</span></dt><dd><p>0x20  </p></dd><dt><span class="term">NotforBcast:</span></dt><dd><p>0x40  </p></dd><dt><span class="term">NoUuid:</span></dt><dd><p>0x80 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868718"></a>Structures</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868725"></a>VOID *</h4></div></div><div></div></div><p>sizeof VOID* is 32 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868737"></a>char</h4></div></div><div></div></div><p>sizeof char is 8 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868748"></a>UTIME</h4></div></div><div></div></div><p>UTIME is 32 bits, indicating time in seconds since 01jan1970.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868761"></a>NTTIME</h4></div></div><div></div></div><p>NTTIME is 64 bits.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868774"></a>DOM_SID (domain SID structure)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8</span></dt><dd><p>SID revision number</p></dd><dt><span class="term">UINT8</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8[6]</span></dt><dd><p>6 bytes for domain SID - Identifier Authority.</p></dd><dt><span class="term">UINT16[n_subauths]</span></dt><dd><p>domain SID sub-authorities</p></dd></dl></div><p><span class="emphasis"><em>Note: the domain SID is documented elsewhere.</em></span>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868867"></a>STR (string)</h4></div></div><div></div></div><p>STR (string) is a char[] : a null-terminated string of ascii characters.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868880"></a>UNIHDR (unicode string header) </h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868937"></a>UNIHDR2 (unicode string header plus buffer pointer)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNIHDR</span></dt><dd><p>unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868979"></a>UNISTR (unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869007"></a>NAME (length-indicated unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869049"></a>UNISTR2 (aligned unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>string of uncode characters</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869135"></a>OBJ_ATTR (object attributes)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0x18 - length (in bytes) including the length field.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - root directory (pointer)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - object name (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - attributes (undocumented)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - security descriptior (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - security quality of service</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869228"></a>POL_HND (LSA policy handle)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[20]</span></dt><dd><p>policy handle</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869255"></a>DOM_SID2 (domain SID structure, SIDS stored in unicode)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - SID type</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain SID unicode string header</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain SID unicode string</p></dd></dl></div><p><span class="emphasis"><em>Note:	there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length.  this will need to be resolved.</em></span></p><p><span class="emphasis"><em>Note:	the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869341"></a>DOM_RID (domain RID structure)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - well-known SID.  1 - user SID (see ShowACLs)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain RID </p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - domain index out of above reference domains</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869411"></a>LOG_INFO (server, account, client structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>account name unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>sec_chan - security channel type</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869511"></a>CLNT_SRV (server, client names structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869588"></a>CREDS (credentials + time stamp)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>credentials</p></dd><dt><span class="term">UTIME</span></dt><dd><p>time stamp</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869629"></a>CLNT_INFO2 (server, client structure, client credentials)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks.  the presumed intention is to
-	maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_SRV</span></dt><dd><p>client and server names</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding, for 4-byte alignment with SMB header.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to client credentials.</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869711"></a>CLNT_INFO (server, account, client structure, client credentials)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks.  the presumed intention is to maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>logon account info</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869764"></a>ID_INFO_1 (id info structure, auth level 1)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>ptr_id_info_1</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>domain name unicode header</p></dd><dt><span class="term">UINT32</span></dt><dd><p>param control</p></dd><dt><span class="term">UINT64</span></dt><dd><p>logon ID</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user name unicode header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>workgroup name unicode header</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 LM OWF Password</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 NT OWF Password</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>workstation name unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869934"></a>SAM_INFO (sam logon/logoff id info structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_INFO2</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to return credentials.</p></dd><dt><span class="term">CRED</span></dt><dd><p>return credentials - ignored.</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon level</p></dd><dt><span class="term">UINT16</span></dt><dd><p>switch value</p></dd></dl></div><pre class="programlisting">
+</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867989"></a>Enumerations</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867997"></a>MSRPC Header type</h4></div></div><div></div></div><p>command number in the msrpc packet header</p><div class="variablelist"><dl><dt><span class="term">MSRPC_Request:</span></dt><dd><p>0x00</p></dd><dt><span class="term">MSRPC_Response:</span></dt><dd><p>0x02</p></dd><dt><span class="term">MSRPC_Bind:</span></dt><dd><p>0x0B</p></dd><dt><span class="term">MSRPC_BindAck:</span></dt><dd><p>0x0C</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868072"></a>MSRPC Packet info</h4></div></div><div></div></div><p>The meaning of these flags is undocumented</p><div class="variablelist"><dl><dt><span class="term">FirstFrag:</span></dt><dd><p>0x01 </p></dd><dt><span class="term">LastFrag:</span></dt><dd><p>0x02 </p></dd><dt><span class="term">NotaFrag:</span></dt><dd><p>0x04  </p></dd><dt><span class="term">RecRespond:</span></dt><dd><p>0x08  </p></dd><dt><span class="term">NoMultiplex:</span></dt><dd><p>0x10  </p></dd><dt><span class="term">NotForIdemp:</span></dt><dd><p>0x20  </p></dd><dt><span class="term">NotforBcast:</span></dt><dd><p>0x40  </p></dd><dt><span class="term">NoUuid:</span></dt><dd><p>0x80 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868203"></a>Structures</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868210"></a>VOID *</h4></div></div><div></div></div><p>sizeof VOID* is 32 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868221"></a>char</h4></div></div><div></div></div><p>sizeof char is 8 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868232"></a>UTIME</h4></div></div><div></div></div><p>UTIME is 32 bits, indicating time in seconds since 01jan1970.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868246"></a>NTTIME</h4></div></div><div></div></div><p>NTTIME is 64 bits.  documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868258"></a>DOM_SID (domain SID structure)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8</span></dt><dd><p>SID revision number</p></dd><dt><span class="term">UINT8</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8[6]</span></dt><dd><p>6 bytes for domain SID - Identifier Authority.</p></dd><dt><span class="term">UINT16[n_subauths]</span></dt><dd><p>domain SID sub-authorities</p></dd></dl></div><p><span class="emphasis"><em>Note: the domain SID is documented elsewhere.</em></span>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868352"></a>STR (string)</h4></div></div><div></div></div><p>STR (string) is a char[] : a null-terminated string of ascii characters.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868365"></a>UNIHDR (unicode string header) </h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868422"></a>UNIHDR2 (unicode string header plus buffer pointer)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNIHDR</span></dt><dd><p>unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868463"></a>UNISTR (unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868491"></a>NAME (length-indicated unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868534"></a>UNISTR2 (aligned unicode string)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>string of uncode characters</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868619"></a>OBJ_ATTR (object attributes)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0x18 - length (in bytes) including the length field.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - root directory (pointer)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - object name (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - attributes (undocumented)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - security descriptior (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - security quality of service</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868713"></a>POL_HND (LSA policy handle)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[20]</span></dt><dd><p>policy handle</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868740"></a>DOM_SID2 (domain SID structure, SIDS stored in unicode)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - SID type</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain SID unicode string header</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain SID unicode string</p></dd></dl></div><p><span class="emphasis"><em>Note:	there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length.  this will need to be resolved.</em></span></p><p><span class="emphasis"><em>Note:	the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868826"></a>DOM_RID (domain RID structure)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - well-known SID.  1 - user SID (see ShowACLs)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain RID </p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - domain index out of above reference domains</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868896"></a>LOG_INFO (server, account, client structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>account name unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>sec_chan - security channel type</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868996"></a>CLNT_SRV (server, client names structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869073"></a>CREDS (credentials + time stamp)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>credentials</p></dd><dt><span class="term">UTIME</span></dt><dd><p>time stamp</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869114"></a>CLNT_INFO2 (server, client structure, client credentials)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks.  the presumed intention is to
+	maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_SRV</span></dt><dd><p>client and server names</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding, for 4-byte alignment with SMB header.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to client credentials.</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869196"></a>CLNT_INFO (server, account, client structure, client credentials)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks.  the presumed intention is to maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>logon account info</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869248"></a>ID_INFO_1 (id info structure, auth level 1)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>ptr_id_info_1</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>domain name unicode header</p></dd><dt><span class="term">UINT32</span></dt><dd><p>param control</p></dd><dt><span class="term">UINT64</span></dt><dd><p>logon ID</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user name unicode header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>workgroup name unicode header</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 LM OWF Password</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 NT OWF Password</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>workstation name unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869420"></a>SAM_INFO (sam logon/logoff id info structure)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_INFO2</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to return credentials.</p></dd><dt><span class="term">CRED</span></dt><dd><p>return credentials - ignored.</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon level</p></dd><dt><span class="term">UINT16</span></dt><dd><p>switch value</p></dd></dl></div><pre class="programlisting">
         switch (switch_value)
         case 1:
         {
             ID_INFO_1     id_info_1;
         }
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870038"></a>GID (group id info)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>group id</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user attributes (only used by NT 3.1 and 3.51)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870077"></a>DOM_REF (domain reference info)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num referenced domains?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>32 - max number of entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - num referenced domains?</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain name unicode string header</p></dd><dt><span class="term">UNIHDR2[num_ref_doms-1]</span></dt><dd><p>referenced domain unicode string headers</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">DOM_SID[num_ref_doms]</span></dt><dd><p>referenced domain SIDs</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870220"></a>DOM_INFO (domain info, levels 3 and 5 are the same))</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>??? padding to get 4-byte alignment with start of SMB header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name string buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID string buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name (unicode string)</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870333"></a>USER_INFO (user logon info)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: it would be nice to know what the 16 byte user session key is for.</em></span></p><div class="variablelist"><dl><dt><span class="term">NTTIME</span></dt><dd><p>logon time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>logoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>kickoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password last set time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password can change time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password must change time</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>username unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user's full name unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon script unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>profile path unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory drive unicode string header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon count</p></dd><dt><span class="term">UINT16</span></dt><dd><p>bad password count</p></dd><dt><span class="term">UINT32</span></dt><dd><p>User ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>Group ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer to groups.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user flags</p></dd><dt><span class="term">char[16]</span></dt><dd><p>user session key</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon server unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon domain unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented logon domain id pointer</p></dd><dt><span class="term">char[40]</span></dt><dd><p>40 undocumented padding bytes.  future expansion?</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - num_other_sids?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>NULL - undocumented pointer to other domain SIDs.</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>username unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user's full name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon script unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>profile path unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory drive unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">GID[num_groups]</span></dt><dd><p>group info</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon domain unicode string</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd><dt><span class="term">DOM_SID[num_sids]</span></dt><dd><p>other domain SIDs?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870896"></a>SH_INFO_1_PTR (pointers to level 1 share info strings)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	see cifsrap2.txt section5, page 10.</em></span></p><table class="simplelist" border="0" summary="Simple list"><tr><td>0 for shi1_type indicates a  Disk.</td></tr><tr><td>1 for shi1_type indicates a  Print Queue.</td></tr><tr><td>2 for shi1_type indicates a  Device.</td></tr><tr><td>3 for shi1_type indicates an IPC pipe.</td></tr><tr><td>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</td></tr></table><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>shi1_netname - pointer to net name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>shi1_type    - type of share.  0 - undocumented.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>shi1_remark  - pointer to comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870991"></a>SH_INFO_1_STR (level 1 share info strings)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_netname - unicode string of net name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_remark  - unicode string of comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871033"></a>SHARE_INFO_1_CTR</h4></div></div><div></div></div><p>share container with 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - Buffer</p></dd></dl></div><p>share container with &gt; 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>non-zero - Buffer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">SH_INFO_1_PTR[EntriesRead]</span></dt><dd><p>share entry pointers</p></dd><dt><span class="term">SH_INFO_1_STR[EntriesRead]</span></dt><dd><p>share entry strings</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - padding</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871203"></a>SERVER_INFO_101</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	see cifs6.txt section 6.4 - the fields described therein will be of assistance here.  for example, the type listed below is the 	same as fServerType, which is described in 6.4.1. </em></span></p><div class="variablelist"><dl><dt><span class="term">SV_TYPE_WORKSTATION</span></dt><dd><p>0x00000001  All workstations</p></dd><dt><span class="term">SV_TYPE_SERVER</span></dt><dd><p>0x00000002  All servers</p></dd><dt><span class="term">SV_TYPE_SQLSERVER</span></dt><dd><p>0x00000004  Any server running with SQL server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_CTRL</span></dt><dd><p>0x00000008  Primary domain controller</p></dd><dt><span class="term">SV_TYPE_DOMAIN_BAKCTRL</span></dt><dd><p>0x00000010  Backup domain controller</p></dd><dt><span class="term">SV_TYPE_TIME_SOURCE</span></dt><dd><p>0x00000020  Server running the timesource service</p></dd><dt><span class="term">SV_TYPE_AFP</span></dt><dd><p>0x00000040  Apple File Protocol servers</p></dd><dt><span class="term">SV_TYPE_NOVELL</span></dt><dd><p>0x00000080  Novell servers</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MEMBER</span></dt><dd><p>0x00000100  Domain Member</p></dd><dt><span class="term">SV_TYPE_PRINTQ_SERVER</span></dt><dd><p>0x00000200  Server sharing print queue</p></dd><dt><span class="term">SV_TYPE_DIALIN_SERVER</span></dt><dd><p>0x00000400  Server running dialin service.</p></dd><dt><span class="term">SV_TYPE_XENIX_SERVER</span></dt><dd><p>0x00000800  Xenix server</p></dd><dt><span class="term">SV_TYPE_NT</span></dt><dd><p>0x00001000  NT server</p></dd><dt><span class="term">SV_TYPE_WFW</span></dt><dd><p>0x00002000  Server running Windows for </p></dd><dt><span class="term">SV_TYPE_SERVER_NT</span></dt><dd><p>0x00008000  Windows NT non DC server</p></dd><dt><span class="term">SV_TYPE_POTENTIAL_BROWSER</span></dt><dd><p>0x00010000  Server that can run the browser service</p></dd><dt><span class="term">SV_TYPE_BACKUP_BROWSER</span></dt><dd><p>0x00020000  Backup browser server</p></dd><dt><span class="term">SV_TYPE_MASTER_BROWSER</span></dt><dd><p>0x00040000  Master browser server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MASTER</span></dt><dd><p>0x00080000  Domain Master Browser server</p></dd><dt><span class="term">SV_TYPE_LOCAL_LIST_ONLY</span></dt><dd><p>0x40000000  Enumerate only entries marked &quot;local&quot;</p></dd><dt><span class="term">SV_TYPE_DOMAIN_ENUM</span></dt><dd><p>0x80000000  Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</p></dd></dl></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>500 - platform_id</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - major version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - minor version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>type (SV_TYPE_... bit field)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to comment</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv101_name - unicode string of server name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv_101_comment  - unicode string of server comment.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871669"></a>MSRPC over Transact Named Pipe</h2></div></div><div></div></div><p>For details on the SMB Transact Named Pipe, see cifs6.txt</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871682"></a>MSRPC Pipes</h3></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869524"></a>GID (group id info)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>group id</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user attributes (only used by NT 3.1 and 3.51)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869562"></a>DOM_REF (domain reference info)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num referenced domains?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>32 - max number of entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - num referenced domains?</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain name unicode string header</p></dd><dt><span class="term">UNIHDR2[num_ref_doms-1]</span></dt><dd><p>referenced domain unicode string headers</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">DOM_SID[num_ref_doms]</span></dt><dd><p>referenced domain SIDs</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869705"></a>DOM_INFO (domain info, levels 3 and 5 are the same))</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>??? padding to get 4-byte alignment with start of SMB header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name string buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID string buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name (unicode string)</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869818"></a>USER_INFO (user logon info)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note: it would be nice to know what the 16 byte user session key is for.</em></span></p><div class="variablelist"><dl><dt><span class="term">NTTIME</span></dt><dd><p>logon time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>logoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>kickoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password last set time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password can change time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password must change time</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>username unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user's full name unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon script unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>profile path unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory drive unicode string header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon count</p></dd><dt><span class="term">UINT16</span></dt><dd><p>bad password count</p></dd><dt><span class="term">UINT32</span></dt><dd><p>User ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>Group ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer to groups.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user flags</p></dd><dt><span class="term">char[16]</span></dt><dd><p>user session key</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon server unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon domain unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented logon domain id pointer</p></dd><dt><span class="term">char[40]</span></dt><dd><p>40 undocumented padding bytes.  future expansion?</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - num_other_sids?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>NULL - undocumented pointer to other domain SIDs.</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>username unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user's full name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon script unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>profile path unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory drive unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">GID[num_groups]</span></dt><dd><p>group info</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon domain unicode string</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd><dt><span class="term">DOM_SID[num_sids]</span></dt><dd><p>other domain SIDs?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870381"></a>SH_INFO_1_PTR (pointers to level 1 share info strings)</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	see cifsrap2.txt section5, page 10.</em></span></p><table class="simplelist" border="0" summary="Simple list"><tr><td>0 for shi1_type indicates a  Disk.</td></tr><tr><td>1 for shi1_type indicates a  Print Queue.</td></tr><tr><td>2 for shi1_type indicates a  Device.</td></tr><tr><td>3 for shi1_type indicates an IPC pipe.</td></tr><tr><td>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</td></tr></table><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>shi1_netname - pointer to net name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>shi1_type    - type of share.  0 - undocumented.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>shi1_remark  - pointer to comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870475"></a>SH_INFO_1_STR (level 1 share info strings)</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_netname - unicode string of net name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_remark  - unicode string of comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870518"></a>SHARE_INFO_1_CTR</h4></div></div><div></div></div><p>share container with 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - Buffer</p></dd></dl></div><p>share container with &gt; 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>non-zero - Buffer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">SH_INFO_1_PTR[EntriesRead]</span></dt><dd><p>share entry pointers</p></dd><dt><span class="term">SH_INFO_1_STR[EntriesRead]</span></dt><dd><p>share entry strings</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - padding</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870687"></a>SERVER_INFO_101</h4></div></div><div></div></div><p><span class="emphasis"><em>Note:	see cifs6.txt section 6.4 - the fields described therein will be of assistance here.  for example, the type listed below is the 	same as fServerType, which is described in 6.4.1. </em></span></p><div class="variablelist"><dl><dt><span class="term">SV_TYPE_WORKSTATION</span></dt><dd><p>0x00000001  All workstations</p></dd><dt><span class="term">SV_TYPE_SERVER</span></dt><dd><p>0x00000002  All servers</p></dd><dt><span class="term">SV_TYPE_SQLSERVER</span></dt><dd><p>0x00000004  Any server running with SQL server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_CTRL</span></dt><dd><p>0x00000008  Primary domain controller</p></dd><dt><span class="term">SV_TYPE_DOMAIN_BAKCTRL</span></dt><dd><p>0x00000010  Backup domain controller</p></dd><dt><span class="term">SV_TYPE_TIME_SOURCE</span></dt><dd><p>0x00000020  Server running the timesource service</p></dd><dt><span class="term">SV_TYPE_AFP</span></dt><dd><p>0x00000040  Apple File Protocol servers</p></dd><dt><span class="term">SV_TYPE_NOVELL</span></dt><dd><p>0x00000080  Novell servers</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MEMBER</span></dt><dd><p>0x00000100  Domain Member</p></dd><dt><span class="term">SV_TYPE_PRINTQ_SERVER</span></dt><dd><p>0x00000200  Server sharing print queue</p></dd><dt><span class="term">SV_TYPE_DIALIN_SERVER</span></dt><dd><p>0x00000400  Server running dialin service.</p></dd><dt><span class="term">SV_TYPE_XENIX_SERVER</span></dt><dd><p>0x00000800  Xenix server</p></dd><dt><span class="term">SV_TYPE_NT</span></dt><dd><p>0x00001000  NT server</p></dd><dt><span class="term">SV_TYPE_WFW</span></dt><dd><p>0x00002000  Server running Windows for </p></dd><dt><span class="term">SV_TYPE_SERVER_NT</span></dt><dd><p>0x00008000  Windows NT non DC server</p></dd><dt><span class="term">SV_TYPE_POTENTIAL_BROWSER</span></dt><dd><p>0x00010000  Server that can run the browser service</p></dd><dt><span class="term">SV_TYPE_BACKUP_BROWSER</span></dt><dd><p>0x00020000  Backup browser server</p></dd><dt><span class="term">SV_TYPE_MASTER_BROWSER</span></dt><dd><p>0x00040000  Master browser server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MASTER</span></dt><dd><p>0x00080000  Domain Master Browser server</p></dd><dt><span class="term">SV_TYPE_LOCAL_LIST_ONLY</span></dt><dd><p>0x40000000  Enumerate only entries marked "local"</p></dd><dt><span class="term">SV_TYPE_DOMAIN_ENUM</span></dt><dd><p>0x80000000  Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</p></dd></dl></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>500 - platform_id</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - major version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - minor version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>type (SV_TYPE_... bit field)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to comment</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv101_name - unicode string of server name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv_101_comment  - unicode string of server comment.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871153"></a>MSRPC over Transact Named Pipe</h2></div></div><div></div></div><p>For details on the SMB Transact Named Pipe, see cifs6.txt</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871166"></a>MSRPC Pipes</h3></div></div><div></div></div><p>
 The MSRPC is conducted over an SMB Transact Pipe with a name of 
 <tt class="filename">\PIPE\</tt>.  You must first obtain a 16 bit file handle, by
 sending a SMBopenX with the pipe name <tt class="filename">\PIPE\srvsvc</tt> for
@@ -1266,21 +1266,21 @@ To be resolved:
 lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe.  Values seen so far are
 listed below:</p><pre class="programlisting">
         initial SMBopenX request:         RPC API command 0x26 params:
-        &quot;\\PIPE\\lsarpc&quot;                  0x65 0x63; 0x72 0x70; 0x44 0x65;
-        &quot;\\PIPE\\srvsvc&quot;                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871787"></a>Header</h3></div></div><div></div></div><p>[section to be rewritten, following receipt of work by Duncan Stansfield]</p><p>Interesting note: if you set packed data representation to 0x0100 0000
-then all 4-byte and 2-byte word ordering is turned around!</p><p>The start of each of the NTLSA and NETLOGON named pipes begins with:</p><div class="segmentedlist"><p><b>offset: </b>00</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>5 - RPC major version</p><p><b>offset: </b>01</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - RPC minor version</p><p><b>offset: </b>02</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>2 - RPC response packet</p><p><b>offset: </b>03</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>3 - (FirstFrag bit-wise or with LastFrag)</p><p><b>offset: </b>04</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>0x1000 0000 - packed data representation</p><p><b>offset: </b>08</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>fragment length - data size (bytes) inc header and tail.</p><p><b>offset: </b>0A</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - authentication length </p><p><b>offset: </b>0C</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>call identifier. matches 12th UINT32 of incoming RPC data.</p><p><b>offset: </b>10</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>allocation hint - data size (bytes) minus header and tail.</p><p><b>offset: </b>14</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - presentation context identifier</p><p><b>offset: </b>16</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - cancel count</p><p><b>offset: </b>17</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>in replies: 0 - reserved; in requests: opnum - see #defines.</p><p><b>offset: </b>18</p><p><b>Variable type: </b>......</p><p><b>Variable data: </b>start of data (goes on for allocation_hint bytes)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871976"></a>RPC_Packet for request, response, bind and bind acknowledgement</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 versionmaj</span></dt><dd><p>reply same as request (0x05)</p></dd><dt><span class="term">UINT8 versionmin</span></dt><dd><p>reply same as request (0x00)</p></dd><dt><span class="term">UINT8 type</span></dt><dd><p>one of the MSRPC_Type enums</p></dd><dt><span class="term">UINT8 flags</span></dt><dd><p>reply same as request (0x00 for Bind, 0x03 for Request)</p></dd><dt><span class="term">UINT32 representation</span></dt><dd><p>reply same as request (0x00000010)</p></dd><dt><span class="term">UINT16 fraglength</span></dt><dd><p>the length of the data section of the SMB trans packet</p></dd><dt><span class="term">UINT16 authlength</span></dt><dd><p></p></dd><dt><span class="term">UINT32 callid</span></dt><dd><p>call identifier. (e.g. 0x00149594)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>the remainder of the packet depending on the &quot;type&quot;</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872110"></a>Interface identification</h4></div></div><div></div></div><p>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</p><pre class="programlisting">
+        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
+        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871268"></a>Header</h3></div></div><div></div></div><p>[section to be rewritten, following receipt of work by Duncan Stansfield]</p><p>Interesting note: if you set packed data representation to 0x0100 0000
+then all 4-byte and 2-byte word ordering is turned around!</p><p>The start of each of the NTLSA and NETLOGON named pipes begins with:</p><div class="segmentedlist"><p><b>offset: </b>00</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>5 - RPC major version</p><p><b>offset: </b>01</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - RPC minor version</p><p><b>offset: </b>02</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>2 - RPC response packet</p><p><b>offset: </b>03</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>3 - (FirstFrag bit-wise or with LastFrag)</p><p><b>offset: </b>04</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>0x1000 0000 - packed data representation</p><p><b>offset: </b>08</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>fragment length - data size (bytes) inc header and tail.</p><p><b>offset: </b>0A</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - authentication length </p><p><b>offset: </b>0C</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>call identifier. matches 12th UINT32 of incoming RPC data.</p><p><b>offset: </b>10</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>allocation hint - data size (bytes) minus header and tail.</p><p><b>offset: </b>14</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - presentation context identifier</p><p><b>offset: </b>16</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - cancel count</p><p><b>offset: </b>17</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>in replies: 0 - reserved; in requests: opnum - see #defines.</p><p><b>offset: </b>18</p><p><b>Variable type: </b>......</p><p><b>Variable data: </b>start of data (goes on for allocation_hint bytes)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871457"></a>RPC_Packet for request, response, bind and bind acknowledgement</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 versionmaj</span></dt><dd><p>reply same as request (0x05)</p></dd><dt><span class="term">UINT8 versionmin</span></dt><dd><p>reply same as request (0x00)</p></dd><dt><span class="term">UINT8 type</span></dt><dd><p>one of the MSRPC_Type enums</p></dd><dt><span class="term">UINT8 flags</span></dt><dd><p>reply same as request (0x00 for Bind, 0x03 for Request)</p></dd><dt><span class="term">UINT32 representation</span></dt><dd><p>reply same as request (0x00000010)</p></dd><dt><span class="term">UINT16 fraglength</span></dt><dd><p>the length of the data section of the SMB trans packet</p></dd><dt><span class="term">UINT16 authlength</span></dt><dd><p></p></dd><dt><span class="term">UINT32 callid</span></dt><dd><p>call identifier. (e.g. 0x00149594)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>the remainder of the packet depending on the "type"</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871591"></a>Interface identification</h4></div></div><div></div></div><p>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</p><pre class="programlisting">
 abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
 transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872138"></a>RPC_Iface RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 byte[16]</span></dt><dd><p>16 bytes of number</p></dd><dt><span class="term">UINT32 version</span></dt><dd><p>the interface number</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872175"></a>RPC_ReqBind RW</h4></div></div><div></div></div><p>the remainder of the packet after the header if &quot;type&quot; was Bind in the response header, &quot;type&quot; should be BindAck</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>maximum transmission fragment size (0x1630)</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>max receive fragment size (0x1630)</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>associated group id (0x0)</p></dd><dt><span class="term">UINT32 numelements</span></dt><dd><p>the number of elements (0x1)</p></dd><dt><span class="term">UINT16 contextid</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT8 numsyntaxes</span></dt><dd><p>the number of syntaxes (has always been 1?)(0x1)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">* abstractint USE RPC_Iface</span></dt><dd><p>num and vers. of interface client is using</p></dd><dt><span class="term">* transferint USE RPC_Iface</span></dt><dd><p>num and vers. of interface to use for replies</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872318"></a>RPC_Address RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16 length</span></dt><dd><p>length of the string including null terminator</p></dd><dt><span class="term">* port USE string</span></dt><dd><p>the string above in single byte, null terminated form</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872358"></a>RPC_ResBind RW</h4></div></div><div></div></div><p>the response to place after the header in the reply packet</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>zero</p></dd><dt><span class="term">* secondaddr USE RPC_Address</span></dt><dd><p>the address string, as described earlier</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT8 numresults</span></dt><dd><p>the number of results (0x01)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT16 result</span></dt><dd><p>result (0x00 = accept)</p></dd><dt><span class="term">UINT16 reason</span></dt><dd><p>reason (0x00 = no reason specified)</p></dd><dt><span class="term">* transfersyntax USE RPC_Iface</span></dt><dd><p>the transfer syntax from the request</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872508"></a>RPC_ReqNorm RW</h4></div></div><div></div></div><p>the remainder of the packet after the header for every other other request</p><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p>the size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT16 opnum</span></dt><dd><p>operation number (0x15)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>a packet dependent on the pipe name (probably the interface) and the op number)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872580"></a>RPC_ResNorm RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p># size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p># presentation context identifier (same as request)</p></dd><dt><span class="term">UINT8 cancelcount</span></dt><dd><p># cancel count? (0x0)</p></dd><dt><span class="term">UINT8 reserved</span></dt><dd><p># 0 - one byte padding</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p># the remainder of the reply</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872660"></a>Tail</h3></div></div><div></div></div><p>The end of each of the NTLSA and NETLOGON named pipes ends with:</p><div class="variablelist"><dl><dt><span class="term">......</span></dt><dd><p>end of data</p></dd><dt><span class="term">UINT32</span></dt><dd><p>return code</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872706"></a>RPC Bind / Bind Ack</h3></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871618"></a>RPC_Iface RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 byte[16]</span></dt><dd><p>16 bytes of number</p></dd><dt><span class="term">UINT32 version</span></dt><dd><p>the interface number</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871657"></a>RPC_ReqBind RW</h4></div></div><div></div></div><p>the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>maximum transmission fragment size (0x1630)</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>max receive fragment size (0x1630)</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>associated group id (0x0)</p></dd><dt><span class="term">UINT32 numelements</span></dt><dd><p>the number of elements (0x1)</p></dd><dt><span class="term">UINT16 contextid</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT8 numsyntaxes</span></dt><dd><p>the number of syntaxes (has always been 1?)(0x1)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">* abstractint USE RPC_Iface</span></dt><dd><p>num and vers. of interface client is using</p></dd><dt><span class="term">* transferint USE RPC_Iface</span></dt><dd><p>num and vers. of interface to use for replies</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871796"></a>RPC_Address RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16 length</span></dt><dd><p>length of the string including null terminator</p></dd><dt><span class="term">* port USE string</span></dt><dd><p>the string above in single byte, null terminated form</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871836"></a>RPC_ResBind RW</h4></div></div><div></div></div><p>the response to place after the header in the reply packet</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>zero</p></dd><dt><span class="term">* secondaddr USE RPC_Address</span></dt><dd><p>the address string, as described earlier</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT8 numresults</span></dt><dd><p>the number of results (0x01)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT16 result</span></dt><dd><p>result (0x00 = accept)</p></dd><dt><span class="term">UINT16 reason</span></dt><dd><p>reason (0x00 = no reason specified)</p></dd><dt><span class="term">* transfersyntax USE RPC_Iface</span></dt><dd><p>the transfer syntax from the request</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871987"></a>RPC_ReqNorm RW</h4></div></div><div></div></div><p>the remainder of the packet after the header for every other other request</p><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p>the size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT16 opnum</span></dt><dd><p>operation number (0x15)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>a packet dependent on the pipe name (probably the interface) and the op number)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872059"></a>RPC_ResNorm RW</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p># size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p># presentation context identifier (same as request)</p></dd><dt><span class="term">UINT8 cancelcount</span></dt><dd><p># cancel count? (0x0)</p></dd><dt><span class="term">UINT8 reserved</span></dt><dd><p># 0 - one byte padding</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p># the remainder of the reply</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872139"></a>Tail</h3></div></div><div></div></div><p>The end of each of the NTLSA and NETLOGON named pipes ends with:</p><div class="variablelist"><dl><dt><span class="term">......</span></dt><dd><p>end of data</p></dd><dt><span class="term">UINT32</span></dt><dd><p>return code</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872184"></a>RPC Bind / Bind Ack</h3></div></div><div></div></div><p>
 RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc)
-with a &quot;transfer syntax&quot; (see RPC_Iface structure).  The purpose for doing
+with a "transfer syntax" (see RPC_Iface structure).  The purpose for doing
 this is unknown.
 </p><p><span class="emphasis"><em>Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters.  The first is 0x0026; the second is the file handle
 	returned by the SMBopenX Transact response.</em></span></p><p><span class="emphasis"><em>Note:	The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind.  The
 	RPC_ResBind member transfersyntax is the same in the response as
 	the</em></span></p><p><span class="emphasis"><em>Note:	The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe.  The
-	mapping identified so far is:</em></span></p><div class="variablelist"><dl><dt><span class="term">initial SMBopenX request:</span></dt><dd><p>RPC_ResBind response:</p></dd><dt><span class="term">&quot;\\PIPE\\srvsvc&quot;</span></dt><dd><p>&quot;\\PIPE\\ntsvcs&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\samr&quot;</span></dt><dd><p>&quot;\\PIPE\\lsass&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\lsarpc&quot;</span></dt><dd><p>&quot;\\PIPE\\lsass&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\wkssvc&quot;</span></dt><dd><p>&quot;\\PIPE\\wksvcs&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\NETLOGON&quot;</span></dt><dd><p>&quot;\\PIPE\\NETLOGON&quot;</p></dd></dl></div><p><span class="emphasis"><em>Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</em></span></p><p>Request:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ReqBind</td></tr></table><p>Response:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ResBind</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872896"></a>NTLSA Transact Named Pipe</h3></div></div><div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Establish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>Open an RPC Pipe with the name &quot;\\PIPE\\lsarpc&quot;.  Store the file handle.</td></tr><tr><td>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>Send an LSA Open Policy request.  Store the Policy Handle.</td></tr><tr><td>Using the Policy Handle, send LSA Query Info Policy requests, etc.</td></tr><tr><td>Using the Policy Handle, send an LSA Close.</td></tr><tr><td>Close the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">LSA Open Policy:</span></dt><dd><p>0x2c</p></dd><dt><span class="term">LSA Query Info Policy:</span></dt><dd><p>0x07</p></dd><dt><span class="term">LSA Enumerate Trusted Domains:</span></dt><dd><p>0x0d</p></dd><dt><span class="term">LSA Open Secret:</span></dt><dd><p>0xff</p></dd><dt><span class="term">LSA Lookup SIDs:</span></dt><dd><p>0xfe</p></dd><dt><span class="term">LSA Lookup Names:</span></dt><dd><p>0xfd</p></dd><dt><span class="term">LSA Close:</span></dt><dd><p>0x00</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873062"></a>LSA Open Policy</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	The policy handle can be anything you like.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873076"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name - unicode string starting with two '\'s</p></dd><dt><span class="term">OBJ_ATTR</span></dt><dd><p>object attributes</p></dd><dt><span class="term">UINT32</span></dt><dd><p>1 - desired access</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873146"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">return</span></dt><dd><p>0 - indicates success</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873187"></a>LSA Query Info Policy</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	The info class in response must be the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873202"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (also a policy handle?)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873241"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (same as info class in request).</p></dd></dl></div><pre class="programlisting">
+	mapping identified so far is:</em></span></p><div class="variablelist"><dl><dt><span class="term">initial SMBopenX request:</span></dt><dd><p>RPC_ResBind response:</p></dd><dt><span class="term">"\\PIPE\\srvsvc"</span></dt><dd><p>"\\PIPE\\ntsvcs"</p></dd><dt><span class="term">"\\PIPE\\samr"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\lsarpc"</span></dt><dd><p>"\\PIPE\\lsass"</p></dd><dt><span class="term">"\\PIPE\\wkssvc"</span></dt><dd><p>"\\PIPE\\wksvcs"</p></dd><dt><span class="term">"\\PIPE\\NETLOGON"</span></dt><dd><p>"\\PIPE\\NETLOGON"</p></dd></dl></div><p><span class="emphasis"><em>Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</em></span></p><p>Request:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ReqBind</td></tr></table><p>Response:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ResBind</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872365"></a>NTLSA Transact Named Pipe</h3></div></div><div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Establish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>Open an RPC Pipe with the name "\\PIPE\\lsarpc".  Store the file handle.</td></tr><tr><td>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>Send an LSA Open Policy request.  Store the Policy Handle.</td></tr><tr><td>Using the Policy Handle, send LSA Query Info Policy requests, etc.</td></tr><tr><td>Using the Policy Handle, send an LSA Close.</td></tr><tr><td>Close the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">LSA Open Policy:</span></dt><dd><p>0x2c</p></dd><dt><span class="term">LSA Query Info Policy:</span></dt><dd><p>0x07</p></dd><dt><span class="term">LSA Enumerate Trusted Domains:</span></dt><dd><p>0x0d</p></dd><dt><span class="term">LSA Open Secret:</span></dt><dd><p>0xff</p></dd><dt><span class="term">LSA Lookup SIDs:</span></dt><dd><p>0xfe</p></dd><dt><span class="term">LSA Lookup Names:</span></dt><dd><p>0xfd</p></dd><dt><span class="term">LSA Close:</span></dt><dd><p>0x00</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872530"></a>LSA Open Policy</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	The policy handle can be anything you like.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872543"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name - unicode string starting with two '\'s</p></dd><dt><span class="term">OBJ_ATTR</span></dt><dd><p>object attributes</p></dd><dt><span class="term">UINT32</span></dt><dd><p>1 - desired access</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872613"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">return</span></dt><dd><p>0 - indicates success</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872655"></a>LSA Query Info Policy</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	The info class in response must be the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872670"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (also a policy handle?)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872708"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (same as info class in request).</p></dd></dl></div><pre class="programlisting">
 switch (info class)
 case 3:
 case 5:
@@ -1289,11 +1289,11 @@ DOM_INFO domain info, levels 3 and 5 (are the same).
 }
 
 return    0 - indicates success
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873296"></a>LSA Enumerate Trusted Domains</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873304"></a>Request</h4></div></div><div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873316"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - enumeration context</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - entries read</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - trust information</p></dd><dt><span class="term">return</span></dt><dd><p>0x8000 001a - &quot;no trusted domains&quot; success code</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873387"></a>LSA Open Secret</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873394"></a>Request</h4></div></div><div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873406"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd></dl></div><p>return    0x0C00 0034 - &quot;no such secret&quot; success code</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873498"></a>LSA Close</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873505"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>policy handle to be closed</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873532"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>0s - closed policy handle (all zeros)</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873564"></a>LSA Lookup SIDS</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873577"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">VOID*[num_entries] undocumented domain SID pointers to be looked up.
-</span></dt><dd><p>DOM_SID[num_entries] domain SIDs to be looked up.</p></dd><dt><span class="term">char[16]</span></dt><dd><p>completely undocumented 16 bytes.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873677"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_SID2[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873773"></a>LSA Lookup Names</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873787"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">NAME[num_entries]</span></dt><dd><p>names to be looked up.</p></dd><dt><span class="term">char[]</span></dt><dd><p>undocumented bytes - falsely translated SID structure?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873901"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_RID[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873999"></a>NETLOGON rpc Transact Named Pipe</h2></div></div><div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>tablish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>en an RPC Pipe with the name &quot;\\PIPE\\NETLOGON&quot;.  Store the file handle.</td></tr><tr><td>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>eate Client Challenge. Send LSA Request Challenge.  Store Server Challenge.</td></tr><tr><td>lculate Session Key.  Send an LSA Auth 2 Challenge.  Store Auth2 Challenge.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA Srv PW Set.  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logon .  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logoff.  Calc/Verify Server Creds.</td></tr><tr><td>ose the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are</p><div class="variablelist"><dl><dt><span class="term">LSA Request Challenge:</span></dt><dd><p>0x04</p></dd><dt><span class="term">LSA Server Password Set:</span></dt><dd><p>0x06</p></dd><dt><span class="term">LSA SAM Logon:</span></dt><dd><p>0x02</p></dd><dt><span class="term">LSA SAM Logoff:</span></dt><dd><p>0x03</p></dd><dt><span class="term">LSA Auth 2:</span></dt><dd><p>0x0f</p></dd><dt><span class="term">LSA Logon Control:</span></dt><dd><p>0x0e</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874162"></a>LSA Request Challenge</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	logon client is the machine, not the user.</em></span></p><p><span class="emphasis"><em>Note:	the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case).  there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874194"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client unicode string</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client challenge</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874264"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server challenge</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874296"></a>LSA Authenticate 2</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note:	neg_flags in the response is the same as that in the request.</em></span></p><p><span class="emphasis"><em>Note:	you must take a copy of the client-calculated credentials received 	here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874327"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>client identification info</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client-calculated credentials</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 4-byte align with start of SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - negotiated flags (usual value is 0x0000 01ff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874396"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server credentials.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - same as neg_flags in request.</p></dd></dl></div><p>return    0 - indicates success.  failure value unknown.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874444"></a>LSA Server Password Set</h3></div></div><div></div></div><p><span class="emphasis"><em>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</em></span></p><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874483"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">CLNT_INFO</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">char[]</span></dt><dd><p>new password - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874525"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return    0 - indicates success; 0xC000 006a indicates failure</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874559"></a>LSA SAM Logon</h3></div></div><div></div></div><p><span class="emphasis"><em>
+</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872763"></a>LSA Enumerate Trusted Domains</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872771"></a>Request</h4></div></div><div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872783"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - enumeration context</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - entries read</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - trust information</p></dd><dt><span class="term">return</span></dt><dd><p>0x8000 001a - "no trusted domains" success code</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872853"></a>LSA Open Secret</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872860"></a>Request</h4></div></div><div></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872872"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd></dl></div><p>return    0x0C00 0034 - "no such secret" success code</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872963"></a>LSA Close</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872970"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>policy handle to be closed</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872997"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>0s - closed policy handle (all zeros)</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873028"></a>LSA Lookup SIDS</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873042"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">VOID*[num_entries] undocumented domain SID pointers to be looked up.
+</span></dt><dd><p>DOM_SID[num_entries] domain SIDs to be looked up.</p></dd><dt><span class="term">char[16]</span></dt><dd><p>completely undocumented 16 bytes.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873142"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_SID2[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873238"></a>LSA Lookup Names</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873252"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">NAME[num_entries]</span></dt><dd><p>names to be looked up.</p></dd><dt><span class="term">char[]</span></dt><dd><p>undocumented bytes - falsely translated SID structure?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873366"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_RID[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return                0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873464"></a>NETLOGON rpc Transact Named Pipe</h2></div></div><div></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>tablish a connection to the IPC$ share (SMBtconX).  use encrypted passwords.</td></tr><tr><td>en an RPC Pipe with the name "\\PIPE\\NETLOGON".  Store the file handle.</td></tr><tr><td>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>eate Client Challenge. Send LSA Request Challenge.  Store Server Challenge.</td></tr><tr><td>lculate Session Key.  Send an LSA Auth 2 Challenge.  Store Auth2 Challenge.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA Srv PW Set.  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logon .  Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds.  Send LSA SAM Logoff.  Calc/Verify Server Creds.</td></tr><tr><td>ose the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are</p><div class="variablelist"><dl><dt><span class="term">LSA Request Challenge:</span></dt><dd><p>0x04</p></dd><dt><span class="term">LSA Server Password Set:</span></dt><dd><p>0x06</p></dd><dt><span class="term">LSA SAM Logon:</span></dt><dd><p>0x02</p></dd><dt><span class="term">LSA SAM Logoff:</span></dt><dd><p>0x03</p></dd><dt><span class="term">LSA Auth 2:</span></dt><dd><p>0x0f</p></dd><dt><span class="term">LSA Logon Control:</span></dt><dd><p>0x0e</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873625"></a>LSA Request Challenge</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note:	logon client is the machine, not the user.</em></span></p><p><span class="emphasis"><em>Note:	the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case).  there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873657"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client unicode string</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client challenge</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873727"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server challenge</p></dd></dl></div><p>return    0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873759"></a>LSA Authenticate 2</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note:	neg_flags in the response is the same as that in the request.</em></span></p><p><span class="emphasis"><em>Note:	you must take a copy of the client-calculated credentials received 	here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873790"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>client identification info</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client-calculated credentials</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 4-byte align with start of SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - negotiated flags (usual value is 0x0000 01ff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873859"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server credentials.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - same as neg_flags in request.</p></dd></dl></div><p>return    0 - indicates success.  failure value unknown.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873906"></a>LSA Server Password Set</h3></div></div><div></div></div><p><span class="emphasis"><em>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</em></span></p><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873946"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">CLNT_INFO</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">char[]</span></dt><dd><p>new password - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873988"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return    0 - indicates success; 0xC000 006a indicates failure</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874022"></a>LSA SAM Logon</h3></div></div><div></div></div><p><span class="emphasis"><em>
 Note:	valid_user is True iff the username and password hash are valid for
 	the requested domain.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874574"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874601"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><pre class="programlisting">
+</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874036"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874063"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><pre class="programlisting">
 if (valid_user)
 {
 	UINT16      3 - switch value indicating USER_INFO structure.
@@ -1313,16 +1313,16 @@ else
 
     return    0xC000 0064 - NT_STATUS_NO_SUCH_USER.
 }
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874662"></a>LSA SAM Logoff</h3></div></div><div></div></div><p><span class="emphasis"><em>
+</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874125"></a>LSA SAM Logoff</h3></div></div><div></div></div><p><span class="emphasis"><em>
 Note:	presumably, the SAM_INFO structure is validated, and a (currently
 	undocumented) error code returned if the Logoff is invalid.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874677"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874705"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return      0 - indicates success.  undocumented failure indication.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874755"></a>\\MAILSLOT\NET\NTLOGON</h2></div></div><div></div></div><p><span class="emphasis"><em>
+</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874140"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874167"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials.  server time stamp appears to be ignored.</p></dd></dl></div><p>return      0 - indicates success.  undocumented failure indication.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874216"></a>\\MAILSLOT\NET\NTLOGON</h2></div></div><div></div></div><p><span class="emphasis"><em>
 Note:	mailslots will contain a response mailslot, to which the response
 	should be sent.  the target NetBIOS name is REQUEST_NAME&lt;20&gt;, where
 	REQUEST_NAME is the name of the machine that sent the request.
-</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874774"></a>Query for PDC</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those 	given in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874787"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0007 - Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874913"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x000A - Respose to Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name (in uppercase)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token (same as received in request)</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875034"></a>SAM Logon</h3></div></div><div></div></div><p><span class="emphasis"><em>Note: machine name in response is preceded by two '\' characters.</em></span></p><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><p><span class="emphasis"><em>Note:	user name in the response is presumably the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875062"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0012 - SAM Logon</p></dd><dt><span class="term">UINT16</span></dt><dd><p>request count</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT32</span></dt><dd><p>alloweable account</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain SID size</p></dd><dt><span class="term">char[sid_size]</span></dt><dd><p>domain SID, of sid_size bytes.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding to 4? 2? -byte align with start of mailslot.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875246"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0013 - Response to SAM Logon</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name - workstation trust account</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name </p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875360"></a>SRVSVC Transact Named Pipe</h2></div></div><div></div></div><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">Net Share Enum</span></dt><dd><p>0x0f</p></dd><dt><span class="term">Net Server Get Info</span></dt><dd><p>0x15</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875405"></a>Net Share Enum</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	share level and switch value in the response are presumably the same as those in the request.</em></span></p><p><span class="emphasis"><em>Note:	cifsrap2.txt (section 5) may be of limited assistance here.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875426"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>pointer (to server name?)</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info with 0 entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>preferred maximum length (0xffff ffff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875550"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info (only added if share info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875625"></a>Net Server Get Info</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	level is the same value as in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875638"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875679"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SERVER_INFO_101</p></dd><dt><span class="term">SERVER_INFO_101</span></dt><dd><p>server info (only added if server info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875741"></a>Cryptographic side of NT Domain Authentication</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875749"></a>Definitions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Add(A1,A2)</span></dt><dd><p>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</p></dd><dt><span class="term">E(K,D)</span></dt><dd><p>DES ECB encryption of 8 byte data D using 7 byte key K</p></dd><dt><span class="term">lmowf()</span></dt><dd><p>Lan man hash</p></dd><dt><span class="term">ntowf()</span></dt><dd><p>NT hash</p></dd><dt><span class="term">PW</span></dt><dd><p>md4(machine_password) == md4(lsadump $machine.acc) ==
+</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874229"></a>Query for PDC</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those 	given in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874249"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0007 - Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874376"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x000A - Respose to Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name (in uppercase)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token (same as received in request)</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874497"></a>SAM Logon</h3></div></div><div></div></div><p><span class="emphasis"><em>Note: machine name in response is preceded by two '\' characters.</em></span></p><p><span class="emphasis"><em>Note:	NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><p><span class="emphasis"><em>Note:	user name in the response is presumably the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874525"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0012 - SAM Logon</p></dd><dt><span class="term">UINT16</span></dt><dd><p>request count</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT32</span></dt><dd><p>alloweable account</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain SID size</p></dd><dt><span class="term">char[sid_size]</span></dt><dd><p>domain SID, of sid_size bytes.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding to 4? 2? -byte align with start of mailslot.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874708"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0013 - Response to SAM Logon</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name - workstation trust account</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name </p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874822"></a>SRVSVC Transact Named Pipe</h2></div></div><div></div></div><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">Net Share Enum</span></dt><dd><p>0x0f</p></dd><dt><span class="term">Net Server Get Info</span></dt><dd><p>0x15</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874867"></a>Net Share Enum</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	share level and switch value in the response are presumably the same as those in the request.</em></span></p><p><span class="emphasis"><em>Note:	cifsrap2.txt (section 5) may be of limited assistance here.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874888"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>pointer (to server name?)</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info with 0 entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>preferred maximum length (0xffff ffff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875013"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info (only added if share info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875087"></a>Net Server Get Info</h3></div></div><div></div></div><p><span class="emphasis"><em>Note:	level is the same value as in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875100"></a>Request</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875141"></a>Response</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SERVER_INFO_101</p></dd><dt><span class="term">SERVER_INFO_101</span></dt><dd><p>server info (only added if server info ptr is non-zero)</p></dd></dl></div><p>return            0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875203"></a>Cryptographic side of NT Domain Authentication</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875211"></a>Definitions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Add(A1,A2)</span></dt><dd><p>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</p></dd><dt><span class="term">E(K,D)</span></dt><dd><p>DES ECB encryption of 8 byte data D using 7 byte key K</p></dd><dt><span class="term">lmowf()</span></dt><dd><p>Lan man hash</p></dd><dt><span class="term">ntowf()</span></dt><dd><p>NT hash</p></dd><dt><span class="term">PW</span></dt><dd><p>md4(machine_password) == md4(lsadump $machine.acc) ==
 pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))
-</p></dd><dt><span class="term">ARC4(K,Lk,D,Ld)</span></dt><dd><p>ARC4 encryption of data D of length Ld with key K of length Lk</p></dd><dt><span class="term">v[m..n(,l)]</span></dt><dd><p>subset of v from bytes m to n, optionally padded with zeroes to length l</p></dd><dt><span class="term">Cred(K,D)</span></dt><dd><p>E(K[7..7,7],E(K[0..6],D)) computes a credential</p></dd><dt><span class="term">Time()</span></dt><dd><p>4 byte current time</p></dd><dt><span class="term">Cc,Cs</span></dt><dd><p>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875911"></a>Protocol</h3></div></div><div></div></div><pre class="programlisting">
+</p></dd><dt><span class="term">ARC4(K,Lk,D,Ld)</span></dt><dd><p>ARC4 encryption of data D of length Ld with key K of length Lk</p></dd><dt><span class="term">v[m..n(,l)]</span></dt><dd><p>subset of v from bytes m to n, optionally padded with zeroes to length l</p></dd><dt><span class="term">Cred(K,D)</span></dt><dd><p>E(K[7..7,7],E(K[0..6],D)) computes a credential</p></dd><dt><span class="term">Time()</span></dt><dd><p>4 byte current time</p></dd><dt><span class="term">Cc,Cs</span></dt><dd><p>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875373"></a>Protocol</h3></div></div><div></div></div><pre class="programlisting">
 C-&gt;S ReqChal,Cc
 S-&gt;C Cs
 </pre><pre class="programlisting">
@@ -1358,7 +1358,7 @@ S: Ts = Time()
 S-&gt;C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
 C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
 C: Rc = Cred(Ks,Rc+Tc+1)
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876010"></a>Comments</h3></div></div><div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875471"></a>Comments</h3></div></div><div></div></div><p>
 On first joining the domain the session key could be computed by
 anyone listening in on the network as the machine password has a well
 known value. Until the machine is rebooted it will use this session
@@ -1379,30 +1379,30 @@ returned by the server.
 The password OWFs should NOT be sent over the network reversibly
 encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server
 computing the same function using the owf values in the SAM.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876057"></a>SIDs and RIDs</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875519"></a>SIDs and RIDs</h2></div></div><div></div></div><p>
 SIDs and RIDs are well documented elsewhere.
 </p><p>
 A SID is an NT Security ID (see DOM_SID structure).  They are of the form:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>revision-NN-SubAuth1-SubAuth2-SubAuth3... </td></tr><tr><td>revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...</td></tr></table><p>
 currently, the SID revision is 1.
 The Sub-Authorities are known as Relative IDs (RIDs).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876097"></a>Well-known SIDs</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876104"></a>Universal well-known SIDs</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Null SID</span></dt><dd><p>S-1-0-0</p></dd><dt><span class="term">World</span></dt><dd><p>S-1-1-0</p></dd><dt><span class="term">Local</span></dt><dd><p>S-1-2-0</p></dd><dt><span class="term">Creator Owner ID</span></dt><dd><p>S-1-3-0</p></dd><dt><span class="term">Creator Group ID</span></dt><dd><p>S-1-3-1</p></dd><dt><span class="term">Creator Owner Server ID</span></dt><dd><p>S-1-3-2</p></dd><dt><span class="term">Creator Group Server ID</span></dt><dd><p>S-1-3-3</p></dd><dt><span class="term">(Non-unique IDs)</span></dt><dd><p>S-1-4</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876231"></a>NT well-known SIDs</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">NT Authority</span></dt><dd><p>S-1-5</p></dd><dt><span class="term">Dialup</span></dt><dd><p>S-1-5-1</p></dd><dt><span class="term">Network</span></dt><dd><p>S-1-5-2</p></dd><dt><span class="term">Batch</span></dt><dd><p>S-1-5-3</p></dd><dt><span class="term">Interactive</span></dt><dd><p>S-1-5-4</p></dd><dt><span class="term">Service</span></dt><dd><p>S-1-5-6</p></dd><dt><span class="term">AnonymousLogon(aka null logon session)</span></dt><dd><p>S-1-5-7</p></dd><dt><span class="term">Proxy</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">ServerLogon(aka domain controller account)</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">(Logon IDs)</span></dt><dd><p>S-1-5-5-X-Y</p></dd><dt><span class="term">(NT non-unique IDs)</span></dt><dd><p>S-1-5-0x15-...</p></dd><dt><span class="term">(Built-in domain)</span></dt><dd><p>s-1-5-0x20</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876412"></a>Well-known RIDS</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875558"></a>Well-known SIDs</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875566"></a>Universal well-known SIDs</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Null SID</span></dt><dd><p>S-1-0-0</p></dd><dt><span class="term">World</span></dt><dd><p>S-1-1-0</p></dd><dt><span class="term">Local</span></dt><dd><p>S-1-2-0</p></dd><dt><span class="term">Creator Owner ID</span></dt><dd><p>S-1-3-0</p></dd><dt><span class="term">Creator Group ID</span></dt><dd><p>S-1-3-1</p></dd><dt><span class="term">Creator Owner Server ID</span></dt><dd><p>S-1-3-2</p></dd><dt><span class="term">Creator Group Server ID</span></dt><dd><p>S-1-3-3</p></dd><dt><span class="term">(Non-unique IDs)</span></dt><dd><p>S-1-4</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875693"></a>NT well-known SIDs</h4></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">NT Authority</span></dt><dd><p>S-1-5</p></dd><dt><span class="term">Dialup</span></dt><dd><p>S-1-5-1</p></dd><dt><span class="term">Network</span></dt><dd><p>S-1-5-2</p></dd><dt><span class="term">Batch</span></dt><dd><p>S-1-5-3</p></dd><dt><span class="term">Interactive</span></dt><dd><p>S-1-5-4</p></dd><dt><span class="term">Service</span></dt><dd><p>S-1-5-6</p></dd><dt><span class="term">AnonymousLogon(aka null logon session)</span></dt><dd><p>S-1-5-7</p></dd><dt><span class="term">Proxy</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">ServerLogon(aka domain controller account)</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">(Logon IDs)</span></dt><dd><p>S-1-5-5-X-Y</p></dd><dt><span class="term">(NT non-unique IDs)</span></dt><dd><p>S-1-5-0x15-...</p></dd><dt><span class="term">(Built-in domain)</span></dt><dd><p>s-1-5-0x20</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875874"></a>Well-known RIDS</h3></div></div><div></div></div><p>
 A RID is a sub-authority value, as part of either a SID, or in the case
 of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1
 structure, in the LSA SAM Logon response.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876426"></a>Well-known RID users</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>DOMAIN_USER_RID_ADMIN</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F4</p><p><b>Groupname: </b>DOMAIN_USER_RID_GUEST</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F5</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876474"></a>Well-known RID groups</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>	DOMAIN_GROUP_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0200</p><p><b>Groupname: </b>	DOMAIN_GROUP_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0201</p><p><b>Groupname: </b>	DOMAIN_GROUP_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0202</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876534"></a>Well-known RID aliases</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0220</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0221</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0222</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_POWER_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0223</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_ACCOUNT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0224</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_SYSTEM_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0225</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_PRINT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0226</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_BACKUP_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0227</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_REPLICATOR</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0228</p></div></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter�11.�Samba Printing Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2876697">Abstract</a></dt><dt><a href="#id2876713">
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875888"></a>Well-known RID users</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>DOMAIN_USER_RID_ADMIN</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F4</p><p><b>Groupname: </b>DOMAIN_USER_RID_GUEST</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F5</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875936"></a>Well-known RID groups</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>	DOMAIN_GROUP_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0200</p><p><b>Groupname: </b>	DOMAIN_GROUP_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0201</p><p><b>Groupname: </b>	DOMAIN_GROUP_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0202</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875996"></a>Well-known RID aliases</h4></div></div><div></div></div><div class="segmentedlist"><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0220</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0221</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0222</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_POWER_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0223</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_ACCOUNT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0224</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_SYSTEM_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0225</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_PRINT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0226</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_BACKUP_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0227</p><p><b>Groupname: </b>	DOMAIN_ALIAS_RID_REPLICATOR</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0228</p></div></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter�11.�Samba Printing Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2876159">Abstract</a></dt><dt><a href="#id2876175">
 Printing Interface to Various Back ends
-</a></dt><dt><a href="#id2876809">
+</a></dt><dt><a href="#id2876271">
 Print Queue TDB's
-</a></dt><dt><a href="#id2877031">
+</a></dt><dt><a href="#id2876487">
 ChangeID and Client Caching of Printer Information
-</a></dt><dt><a href="#id2877045">
+</a></dt><dt><a href="#id2876500">
 Windows NT/2K Printer Change Notify
-</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876697"></a>Abstract</h2></div></div><div></div></div><p>
+</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876159"></a>Abstract</h2></div></div><div></div></div><p>
 The purpose of this document is to provide some insight into
 Samba's printing functionality and also to describe the semantics
 of certain features of Windows client printing.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876713"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876175"></a>
 Printing Interface to Various Back ends
 </h2></div></div><div></div></div><p>
 Samba uses a table of function pointers to seven functions.  The
@@ -1413,10 +1413,10 @@ Currently there are only two printing back end implementations
 defined.
 </p><div class="itemizedlist"><ul type="disc"><li><p>a generic set of functions for working with standard UNIX
 	printing subsystems</p></li><li><p>a set of CUPS specific functions (this is only enabled if
-	the CUPS libraries were located at compile time).</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876809"></a>
+	the CUPS libraries were located at compile time).</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876271"></a>
 Print Queue TDB's
 </h2></div></div><div></div></div><p>
-Samba provides periodic caching of the output from the &quot;lpq command&quot;
+Samba provides periodic caching of the output from the "lpq command"
 for performance reasons.  This cache time is configurable in seconds.
 Obviously the longer the cache time the less often smbd will be
 required to exec a copy of lpq.  However, the accuracy of the print
@@ -1436,7 +1436,7 @@ There are two ways in which a a print job can be entered into
 a print queue's TDB.  The first is to submit the job from a Windows
 client which will insert the job information directly into the TDB.
 The second method is to have the print job picked up by executing the
-&quot;lpq command&quot;.
+"lpq command".
 </p><pre class="programlisting">
 /* included from printing.h */
 struct printjob {
@@ -1457,9 +1457,9 @@ struct printjob {
 };
 </pre><p>
 The current manifestation of the printjob structure contains a field
-for the UNIX job id returned from the &quot;lpq command&quot; and a Windows job
+for the UNIX job id returned from the "lpq command" and a Windows job
 ID (32-bit bounded by PRINT_MAX_JOBID).  When a print job is returned
-by the &quot;lpq command&quot; that does not match an existing job in the queue's
+by the "lpq command" that does not match an existing job in the queue's
 TDB, a 32-bit job ID above the &lt;*vance doesn't know what word is missing here*&gt; is generating by adding UNIX_JOB_START to
 the id reported by lpq.
 </p><p>
@@ -1474,7 +1474,7 @@ steps ( refer to <tt class="filename">print.c:print_queue_update()</tt> ):
 	stored in <tt class="constant">LOCK/<i class="replaceable"><tt>printer_name</tt></i></tt>.  
 	If so, then do not update the TDB.</p></li><li><p>Lock the mutex entry in the TDB and store our own pid.
 	Check that this succeeded, else fail.</p></li><li><p>Store the updated time stamp for the new cache
-	listing</p></li><li><p>Retrieve the queue listing via &quot;lpq command&quot;</p></li><li><pre class="programlisting">
+	listing</p></li><li><p>Retrieve the queue listing via "lpq command"</p></li><li><pre class="programlisting">
 	foreach job in the queue
      	{
 		if the job is a UNIX job, create a new entry;
@@ -1489,7 +1489,7 @@ steps ( refer to <tt class="filename">print.c:print_queue_update()</tt> ):
 	}</pre></li><li><p>Delete any jobs in the TDB that are not
 	in the in the lpq listing</p></li><li><p>Store the print queue status in the TDB</p></li><li><p>update the cache time stamp again</p></li></ol></div><p>
 Note that it is the contents of this TDB that is returned to Windows
-clients and not the actual listing from the &quot;lpq command&quot;.
+clients and not the actual listing from the "lpq command".
 </p><p>
 The NT_DEVICEMODE stored as part of the printjob structure is used to
 store a pointer to a non-default DeviceMode associated with the print
@@ -1502,11 +1502,11 @@ and the job has the printer's device mode associated with it by default.
 Only non-default Device Mode are stored with print jobs in the print
 queue TDB.  Otherwise, the Device Mode is obtained from the printer
 object when the client issues a GetJob(level == 2) request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877031"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876487"></a>
 ChangeID and Client Caching of Printer Information
 </h2></div></div><div></div></div><p>
 [To be filled in later]
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877045"></a>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876500"></a>
 Windows NT/2K Printer Change Notify
 </h2></div></div><div></div></div><p>
 When working with Windows NT+ clients, it is possible for a
@@ -1604,13 +1604,13 @@ handle for notification.  Samba currently uses the snum of
 the printer for this which can break if the list of services
 has been modified since the notification handle was registered.</p></li><li><p>The size is either (a) the string length in UNICODE for strings,
 (b) the size in bytes of the security descriptor, or (c) 0 for
-data values.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wins"></a>Chapter�12.�Samba WINS Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877426">WINS Failover</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877426"></a>WINS Failover</h2></div></div><div></div></div><p>
+data values.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wins"></a>Chapter�12.�Samba WINS Internals</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="surname">Carter</span></h3></div></div><div><p class="pubdate">October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2876880">WINS Failover</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876880"></a>WINS Failover</h2></div></div><div></div></div><p>
 The current Samba codebase possesses the capability to use groups of WINS
 servers that share a common namespace for NetBIOS name registration and 
 resolution.  The formal parameter syntax is
 </p><pre class="programlisting">
 	WINS_SERVER_PARAM 	= SERVER [ SEPARATOR SERVER_LIST ]
-	WINS_SERVER_PARAM 	= &quot;wins server&quot;
+	WINS_SERVER_PARAM 	= "wins server"
 	SERVER 			= ADDR[:TAG]
 	ADDR 			= ip_addr | fqdn
 	TAG 			= string
@@ -1623,7 +1623,7 @@ A simple example of a valid wins server setting is
 	wins server = 192.168.1.2 192.168.1.3
 </pre><p>
 In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default
-TAG of &quot;*&quot;.  A TAG is used to group servers of a shared NetBIOS namespace together.  Upon
+TAG of "*".  A TAG is used to group servers of a shared NetBIOS namespace together.  Upon
 startup, nmbd will attempt to register the netbios name value with one server in each
 tagged group.
 </p><p>
@@ -1634,7 +1634,7 @@ interface names in the tags is only by convention and is not a technical require
 	wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1
 </pre><p>
 Using this configuration, nmbd would attempt to register the server's NetBIOS name 
-with one WINS server in each group.  Because the &quot;eth0&quot; group has two servers, the 
+with one WINS server in each group.  Because the "eth0" group has two servers, the 
 second server would only be used when a registration (or resolution) request to 
 the first server in that group timed out.
 </p><p>
@@ -1646,7 +1646,7 @@ If a timeout occurs when querying a specific WINS server, that server is marked
 prevent further timeouts and the next server in the WINS group is contacted.  Once marked as 
 dead, Samba will not attempt to contact that server for name registration/resolution queries 
 for a period of 10 minutes.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="sam"></a>Chapter�13.�The Upcoming SAM System</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Bartlett</span></h3></div></div><div><p class="pubdate">1 October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877582">Security in the 'new SAM'</a></dt><dt><a href="#id2877712">Standalone from UNIX</a></dt><dt><a href="#id2877739">Handles and Races in the new SAM</a></dt><dt><a href="#id2877808">Layers</a></dt><dd><dl><dt><a href="#id2877815">Application</a></dt><dt><a href="#id2877831">SAM Interface</a></dt><dt><a href="#id2877859">SAM Modules</a></dt></dl></dd><dt><a href="#id2877880">SAM Modules</a></dt><dd><dl><dt><a href="#id2877888">Special Module: sam_passdb</a></dt><dt><a href="#id2877906">sam_ads</a></dt></dl></dd><dt><a href="#id2877935">Memory Management</a></dt><dt><a href="#id2878035">Testing</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877582"></a>Security in the 'new SAM'</h2></div></div><div></div></div><p>One of the biggest problems with passdb is it's implementation of
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="sam"></a>Chapter�13.�The Upcoming SAM System</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Bartlett</span></h3></div></div><div><p class="pubdate">1 October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877009">Security in the 'new SAM'</a></dt><dt><a href="#id2877139">Standalone from UNIX</a></dt><dt><a href="#id2877166">Handles and Races in the new SAM</a></dt><dt><a href="#id2877235">Layers</a></dt><dd><dl><dt><a href="#id2877242">Application</a></dt><dt><a href="#id2877258">SAM Interface</a></dt><dt><a href="#id2877286">SAM Modules</a></dt></dl></dd><dt><a href="#id2877308">SAM Modules</a></dt><dd><dl><dt><a href="#id2877315">Special Module: sam_passdb</a></dt><dt><a href="#id2877333">sam_ads</a></dt></dl></dd><dt><a href="#id2877362">Memory Management</a></dt><dt><a href="#id2877454">Testing</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877009"></a>Security in the 'new SAM'</h2></div></div><div></div></div><p>One of the biggest problems with passdb is it's implementation of
 'security'.  Access control is on a 'are you root at the moment' basis,
 and it has no concept of NT ACLs.  Things like ldapsam had to add
 'magic' 'are you root' checks.</p><p>We took this very seriously when we started work, and the new structure
@@ -1706,7 +1706,7 @@ actual data store (like the LDAP server).
 </p><p>
 Finally, we have generic get_sec_desc() and set_sec_desc() routines to
 allow external ACL manipulation.  These do lookups based on SID.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877712"></a>Standalone from UNIX</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877139"></a>Standalone from UNIX</h2></div></div><div></div></div><p>
 One of the primary tenants of the 'new SAM' is that it would not attempt
 to deal with 'what unix id for that'.  This would be left to the 'SMS'
 (Sid Mapping System') or SID farm, and probably administered via
@@ -1716,7 +1716,7 @@ Accounts not preexisting in unix would be served up via winbind.
 </p><p>
 This is an *optional* part, and my preferred end-game.  We have a fare
 way to go before things like winbind up to it however.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877739"></a>Handles and Races in the new SAM</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877166"></a>Handles and Races in the new SAM</h2></div></div><div></div></div><p>
 One of the things that the 'new SAM' work has tried to face is both
 compatibility with existing code, and a closer alignment to the SAMR
 interface.  I consider SAMR to be a 'primary customer' to the this work,
@@ -1741,11 +1741,11 @@ have *really* changed.
 'conflicting' updates:  Currently we don't deal with this (in passdb
 or the new sam stuff), but the design is sufficiently flexible to 'deny'
 a second update.  I don't foresee locking records however.
-</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877808"></a>Layers</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877815"></a>Application</h3></div></div><div></div></div><p>
+</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877235"></a>Layers</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877242"></a>Application</h3></div></div><div></div></div><p>
 This is where smbd, samtest and whatever end-user replacement we have
 for pdbedit sits.  They use only the SAM interface, and do not get
 'special knowledge' of what is below them.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877831"></a>SAM Interface</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877258"></a>SAM Interface</h3></div></div><div></div></div><p>
 This level 'owns' the various handle structures, the get/set routines on
 those structures and provides the public interface.  The application
 layer may initialize a 'context' to be passed to all interface routines,
@@ -1756,7 +1756,7 @@ abstraction to the modules below, and arrange for their initial loading.
 </p><p>
 We could possibly add ACL checking at this layer, to avoid discrepancies
 in implementation modules.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877859"></a>SAM Modules</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877286"></a>SAM Modules</h3></div></div><div></div></div><p>
 These do not communicate with the application directly, only by setting
 values in the handles, and receiving requests from the interface.  These
 modules are responsible for translating values from the handle's
@@ -1764,13 +1764,13 @@ modules are responsible for translating values from the handle's
 to 'know' things like it's own domain SID, domain name, and any other
 state attached to the SAM.  Simpler modules may call back to some helper
 routine.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877880"></a>SAM Modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877888"></a>Special Module: sam_passdb</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877308"></a>SAM Modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877315"></a>Special Module: sam_passdb</h3></div></div><div></div></div><p>
 In order for there to be a smooth transition, kai is writing a module
 that reads existing passdb backends, and translates them into SAM
 replies.  (Also pulling data from the account policy DB etc).  We also
 intend to write a module that does the reverse - gives the SAM a passdb
 interface.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877906"></a>sam_ads</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877333"></a>sam_ads</h3></div></div><div></div></div><p>
 This is the first of the SAM modules to be committed to the tree -
 mainly because I needed to coordinate work with metze (who authored most
 of it).  This module aims to use Samba's libads code to provide an
@@ -1782,7 +1782,7 @@ the construction of an Samba AD DC.
 </p><p>
 We also intend to construct a Samba 2.2/3.0 compatible ldap module,
 again using libads code.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877935"></a>Memory Management</h2></div></div><div></div></div><p> 
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877362"></a>Memory Management</h2></div></div><div></div></div><p> 
 The 'new SAM' development effort also concerned itself with getting a
 sane implementation of memory management.  It was decided that we would
 be (as much as possible) talloc based, using an 'internal talloc
@@ -1811,7 +1811,7 @@ NT_USER_TOKEN *access_token, uint32 access_desired, const DOM_SID
 NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const
 NT_USER_TOKEN *access_token, const DOM_SID *domainsid, uint16 acct_ctrl,
 int32 *account_count, SAM_ACCOUNT_ENUM **accounts)
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878035"></a>Testing</h2></div></div><div></div></div><p>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877454"></a>Testing</h2></div></div><div></div></div><p>
 Testing is vital in any piece of software, and Samba is certainly no
 exception. In designing this new subsystem, we have taken care to ensure
 it is easily tested, independent of outside protocols.
@@ -1840,13 +1840,13 @@ Because the 'new SAM' is NT ACL based, there will be a command to
 specify an arbitrary NT ACL, but for now it uses 'system' by default.
 </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pwencrypt"></a>Chapter�14.�LanMan and NT Password Encryption</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><br>
 				<tt class="email">&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt><br>
-			</p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878174">Introduction</a></dt><dt><a href="#id2878193">How does it work?</a></dt><dt><a href="#id2878320">The smbpasswd file</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878174"></a>Introduction</h2></div></div><div></div></div><p>With the development of LanManager and Windows NT 
+			</p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877592">Introduction</a></dt><dt><a href="#id2877615">How does it work?</a></dt><dt><a href="#id2877715">The smbpasswd file</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877592"></a>Introduction</h2></div></div><div></div></div><p>With the development of LanManager and Windows NT 
 	compatible password encryption for Samba, it is now able 
 	to validate user connections in exactly the same way as 
 	a LanManager or Windows NT server.</p><p>This document describes how the SMB password encryption 
 	algorithm works and what issues there are in choosing whether 
 	you want to use it. You should read it carefully, especially 
-	the part about security and the &quot;PROS and CONS&quot; section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878193"></a>How does it work?</h2></div></div><div></div></div><p>LanManager encryption is somewhat similar to UNIX 
+	the part about security and the "PROS and CONS" section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877615"></a>How does it work?</h2></div></div><div></div></div><p>LanManager encryption is somewhat similar to UNIX 
 	password encryption. The server uses a file containing a 
 	hashed value of a user's password.  This is created by taking 
 	the user's plaintext password, capitalising it, and either 
@@ -1854,7 +1854,7 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default.
 	This 14 byte value is used as two 56 bit DES keys to encrypt 
 	a 'magic' eight byte value, forming a 16 byte value which is 
 	stored by the server and client. Let this value be known as 
-	the &quot;hashed password&quot;.</p><p>Windows NT encryption is a higher quality mechanism, 
+	the "hashed password".</p><p>Windows NT encryption is a higher quality mechanism, 
 	consisting of doing an MD4 hash on a Unicode version of the user's 
 	password. This also produces a 16 byte hash value that is 
 	non-reversible.</p><p>When a client (LanManager, Windows for WorkGroups, Windows 
@@ -1863,11 +1863,11 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default.
 	protocol that the client and server will use. In the reply to this 
 	request the Samba server generates and appends an 8 byte, random 
 	value - this is stored in the Samba server after the reply is sent 
-	and is known as the &quot;challenge&quot;.  The challenge is different for 
+	and is known as the "challenge".  The challenge is different for 
 	every client connection.</p><p>The client then uses the hashed password (16 byte values 
 	described above), appended with 5 null bytes, as three 56 bit 
 	DES keys, each of which is used to encrypt the challenge 8 byte 
-	value, forming a 24 byte value known as the &quot;response&quot;.</p><p>In the SMB call SMBsessionsetupX (when user level security 
+	value, forming a 24 byte value known as the "response".</p><p>In the SMB call SMBsessionsetupX (when user level security 
 	is selected) or the call SMBtconX (when share level security is 
 	selected), the 24 byte response is returned by the client to the 
 	Samba server.  For Windows NT protocol levels the above calculation 
@@ -1883,7 +1883,7 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default.
 	know the correct password and is denied access.</p><p>Note that the Samba server never knows or stores the cleartext 
 	of the user's password - just the 16 byte hashed values derived from 
 	it. Also note that the cleartext password or 16 byte hashed values 
-	are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878320"></a>The smbpasswd file</h2></div></div><div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol 
+	are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877715"></a>The smbpasswd file</h2></div></div><div></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol 
 	it must be able to look up the 16 byte hashed values given a user name.
 	Unfortunately, as the UNIX password value is also a one way hash
 	function (ie. it is impossible to retrieve the cleartext of the user's
@@ -1924,7 +1924,7 @@ username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
 	representation of the 16 byte hashed value of a user's password.</p><p>To set a user to have no password (not recommended), edit the file
 	using vi, and replace the first 11 characters with the ascii text
-	<tt class="constant">&quot;NO PASSWORD&quot;</tt> (minus the quotes).</p><p>For example, to clear the password for user bob, his smbpasswd file 
+	<tt class="constant">"NO PASSWORD"</tt> (minus the quotes).</p><p>For example, to clear the password for user bob, his smbpasswd file 
 	entry would look like :</p><pre class="programlisting">
 bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
@@ -1940,10 +1940,10 @@ bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	to enable this on your server.</p><p><span class="emphasis"><em>Note : </em></span>This file should be protected very 
 	carefully. Anyone with access to this file can (with enough knowledge of 
 	the protocols) gain access to your SMB server. The file is thus more 
-	sensitive than a normal unix <tt class="filename">/etc/passwd</tt> file.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="modules"></a>Chapter�15.�Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 19 March 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878688">Advantages</a></dt><dt><a href="#id2878737">Loading modules</a></dt><dd><dl><dt><a href="#id2878771">Static modules</a></dt><dt><a href="#id2878811">Shared modules</a></dt></dl></dd><dt><a href="#id2878839">Writing modules</a></dt><dd><dl><dt><a href="#id2878904">Static/Shared selection in configure.in</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878688"></a>Advantages</h2></div></div><div></div></div><p>
+	sensitive than a normal unix <tt class="filename">/etc/passwd</tt> file.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="modules"></a>Chapter�15.�Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 19 March 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878082">Advantages</a></dt><dt><a href="#id2878130">Loading modules</a></dt><dd><dl><dt><a href="#id2878163">Static modules</a></dt><dt><a href="#id2878204">Shared modules</a></dt></dl></dd><dt><a href="#id2878231">Writing modules</a></dt><dd><dl><dt><a href="#id2878293">Static/Shared selection in configure.in</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878082"></a>Advantages</h2></div></div><div></div></div><p>
 The new modules system has the following advantages:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>Transparent loading of static and shared modules (no need 
-for a subsystem to know about modules)</td></tr><tr><td>Simple selection between shared and static modules at configure time</td></tr><tr><td>&quot;preload modules&quot; option for increasing performance for stable modules</td></tr><tr><td>No nasty #define stuff anymore</td></tr><tr><td>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878737"></a>Loading modules</h2></div></div><div></div></div><p>
+for a subsystem to know about modules)</td></tr><tr><td>Simple selection between shared and static modules at configure time</td></tr><tr><td>"preload modules" option for increasing performance for stable modules</td></tr><tr><td>No nasty #define stuff anymore</td></tr><tr><td>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878130"></a>Loading modules</h2></div></div><div></div></div><p>
 Some subsystems in samba use different backends. These backends can be 
 either statically linked in to samba or available as a plugin. A subsystem 
 should have a function that allows a module to register itself. For example, 
@@ -1953,7 +1953,7 @@ NTSTATUS smb_register_passdb(int version, const char *name, pdb_init_function in
 </pre><p>
 This function will be called by the initialisation function of the module to 
 register itself. 
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878771"></a>Static modules</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878163"></a>Static modules</h3></div></div><div></div></div><p>
 The modules system compiles a list of initialisation functions for the 
 static modules of each subsystem. This is a define. For example, 
 it is here currently (from <tt class="filename">include/config.h</tt>): 
@@ -1963,7 +1963,7 @@ it is here currently (from <tt class="filename">include/config.h</tt>):
 </pre><p>
 These functions should be called before the subsystem is used. That 
 should be done when the subsystem is initialised or first used. 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878811"></a>Shared modules</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878204"></a>Shared modules</h3></div></div><div></div></div><p>
 If a subsystem needs a certain backend, it should check if it has 
 already been registered. If the backend hasn't been registered already, 
 the subsystem should call smb_probe_module(char *subsystem, char *backend).
@@ -1973,7 +1973,7 @@ is a slash, smb_probe_module() tries to load the module from the
 absolute path specified in 'backend'.
 </p><p>After smb_probe_module() has been executed, the subsystem 
 should check again if the module has been registered. 
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878839"></a>Writing modules</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878231"></a>Writing modules</h2></div></div><div></div></div><p>
 Each module has an initialisation function. For modules that are 
 included with samba this name is '<i class="replaceable"><tt>subsystem</tt></i>_<i class="replaceable"><tt>backend</tt></i>_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()).
 The prototype for these functions is:
@@ -1984,11 +1984,11 @@ registration functions. The function should return NT_STATUS_OK on success and
 NT_STATUS_UNSUCCESSFUL or a more useful nt error code on failure.</p><p>For example, pdb_ldap_init() contains: </p><pre class="programlisting">
 NTSTATUS pdb_ldap_init(void)
 {
-smb_register_passdb(PASSDB_INTERFACE_VERSION, &quot;ldapsam&quot;, pdb_init_ldapsam);
-smb_register_passdb(PASSDB_INTERFACE_VERSION, &quot;ldapsam_nua&quot;, pdb_init_ldapsam_nua);
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam);
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua);
 	return NT_STATUS_OK;
 }
-</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878904"></a>Static/Shared selection in configure.in</h3></div></div><div></div></div><p>
+</pre><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878293"></a>Static/Shared selection in configure.in</h3></div></div><div></div></div><p>
 Some macros in configure.in generate the various defines and substs that 
 are necessary for the system to work correct. All modules that should 
 be built by default have to be added to the variable 'default_modules'. 
@@ -2009,13 +2009,13 @@ Practically, this means all c files that contain <b class="command">static_init_
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 There currently also is a configure.in command called SMB_MODULE_PROVIVES().
 This is used for modules that register multiple things. It should not 
-be used as probing will most likely disappear in the future.</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rpc-plugin"></a>Chapter�16.�RPC Pluggable Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Liguori</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">January 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2879098">About</a></dt><dt><a href="#id2879116">General Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879098"></a>About</h2></div></div><div></div></div><p>
+be used as probing will most likely disappear in the future.</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="rpc-plugin"></a>Chapter�16.�RPC Pluggable Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Liguori</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">January 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878489">About</a></dt><dt><a href="#id2878508">General Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878489"></a>About</h2></div></div><div></div></div><p>
 This document describes how to make use the new RPC Pluggable Modules features
 of Samba 3.0.  This architecture was added to increase the maintainability of
 Samba allowing RPC Pipes to be worked on separately from the main CVS branch.
 The RPM architecture will also allow third-party vendors to add functionality
 to Samba through plug-ins.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879116"></a>General Overview</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878508"></a>General Overview</h2></div></div><div></div></div><p>
 When an RPC call is sent to smbd, smbd tries to load a shared library by the
 name <tt class="filename">librpc_&lt;pipename&gt;.so</tt> to handle the call if
 it doesn't know how to handle the call internally.  For instance, LSA calls
@@ -2032,7 +2032,7 @@ NTSTATUS rpc_pipe_register_commands(int version, const char *clnt, const char *s
 argument.</p></dd><dt><span class="term">clnt</span></dt><dd><p>the Client name of the named pipe</p></dd><dt><span class="term">srv</span></dt><dd><p>the Server name of the named pipe</p></dd><dt><span class="term">cmds</span></dt><dd><p>a list of api_structs that map RPC ordinal numbers to function calls</p></dd><dt><span class="term">size</span></dt><dd><p>the number of api_structs contained in cmds</p></dd></dl></div><p>
 See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of
 how to use this library.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="vfs"></a>Chapter�17.�VFS Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:ab@samba.org">ab@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:metze@metzemix.de">metze@metzemix.de</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 27 May 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2879326">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2879332">The general interface</a></dt><dt><a href="#id2879448">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2879520">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2879528">Initialization and registration</a></dt><dt><a href="#id2879720">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879963">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879970">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2880501">Some Notes</a></dt><dd><dl><dt><a href="#id2880508">Implement TRANSPARENT functions</a></dt><dt><a href="#id2880533">Implement OPAQUE functions</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879326"></a>The Samba (Posix) VFS layer</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879332"></a>The general interface</h3></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="vfs"></a>Chapter�17.�VFS Modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:ab@samba.org">ab@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:metze@metzemix.de">metze@metzemix.de</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 27 May 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878716">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2878723">The general interface</a></dt><dt><a href="#id2878839">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2878926">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2878934">Initialization and registration</a></dt><dt><a href="#id2879115">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879360">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879367">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2879871">Some Notes</a></dt><dd><dl><dt><a href="#id2879878">Implement TRANSPARENT functions</a></dt><dt><a href="#id2879903">Implement OPAQUE functions</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878716"></a>The Samba (Posix) VFS layer</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878723"></a>The general interface</h3></div></div><div></div></div><p>
 Each VFS operation has a vfs_op_type, a function pointer and a handle pointer in the
 struct vfs_ops and tree macros to make it easier to call the operations.
 (Take a look at <tt class="filename">include/vfs.h</tt> and <tt class="filename">include/vfs_macros.h</tt>.)
@@ -2128,7 +2128,7 @@ DO NOT ACCESS conn-&gt;vfs.ops.* directly !!!
 	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
 
 ...
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879448"></a>Possible VFS operation layers</h3></div></div><div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878839"></a>Possible VFS operation layers</h3></div></div><div></div></div><p>
 These values are used by the VFS subsystem when building the conn-&gt;vfs 
 and conn-&gt;vfs_opaque structs for a connection with multiple VFS modules. 
 Internally, Samba differentiates only opaque and transparent layers at this process.
@@ -2157,7 +2157,7 @@ typedef enum _vfs_op_layer {
 	SMB_VFS_LAYER_SCANNER		/* - Checks data and possibly initiates additional */
 					/*   file activity like logging to files _inside_ samba VFS */
 } vfs_op_layer;
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879520"></a>The Interaction between the Samba VFS subsystem and the modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879528"></a>Initialization and registration</h3></div></div><div></div></div><p>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878926"></a>The Interaction between the Samba VFS subsystem and the modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878934"></a>Initialization and registration</h3></div></div><div></div></div><p>
 As each Samba module a VFS module should have a 
 </p><pre class="programlisting">NTSTATUS vfs_example_init(void);</pre><p> function if it's staticly linked to samba or
 </p><pre class="programlisting">NTSTATUS init_module(void);</pre><p> function if it's a shared module.
@@ -2195,9 +2195,9 @@ static vfs_op_tuple example_op_tuples[] = {
 
 NTSTATUS init_module(void)
 {
-	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, &quot;example&quot;, example_op_tuples);
+	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, "example", example_op_tuples);
 }
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879720"></a>How the Modules handle per connection data</h3></div></div><div></div></div><p>Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879115"></a>How the Modules handle per connection data</h3></div></div><div></div></div><p>Each VFS function has as first parameter a pointer to the modules vfs_handle_struct.
 </p><pre class="programlisting">
 typedef struct vfs_handle_struct {
 	struct vfs_handle_struct  *next, *prev;
@@ -2207,7 +2207,7 @@ typedef struct vfs_handle_struct {
 	void *data;
 	void (*free_data)(void **data);
 } vfs_handle_struct;
-</pre><div class="variablelist"><dl><dt><span class="term">param</span></dt><dd><p>this is the module parameter specified in the <b class="command">vfs objects</b> parameter.</p><p>e.g. for 'vfs objects = example:test' param would be &quot;test&quot;.</p></dd><dt><span class="term">vfs_next</span></dt><dd><p>This vfs_ops struct contains the information for calling the next module operations.
+</pre><div class="variablelist"><dl><dt><span class="term">param</span></dt><dd><p>this is the module parameter specified in the <b class="command">vfs objects</b> parameter.</p><p>e.g. for 'vfs objects = example:test' param would be "test".</p></dd><dt><span class="term">vfs_next</span></dt><dd><p>This vfs_ops struct contains the information for calling the next module operations.
 Use the SMB_VFS_NEXT_* macros to call a next module operations and
 don't access handle-&gt;vfs_next.ops.* directly!</p></dd><dt><span class="term">conn</span></dt><dd><p>This is a pointer back to the connection_struct to witch the handle belongs.</p></dd><dt><span class="term">data</span></dt><dd><p>This is a pointer for holding module private data.
 You can alloc data with connection life time on the handle-&gt;conn-&gt;mem_ctx TALLOC_CTX.
@@ -2217,14 +2217,14 @@ you can set this function pointer to NULL.</p></dd></dl></div><p>Some useful MAC
 </p><pre class="programlisting">
 #define SMB_VFS_HANDLE_GET_DATA(handle, datap, type, ret) { \
 	if (!(handle)||((datap=(type *)(handle)-&gt;data)==NULL)) { \
-		DEBUG(0,(&quot;%s() failed to get vfs_handle-&gt;data!\n&quot;,FUNCTION_MACRO)); \
+		DEBUG(0,("%s() failed to get vfs_handle-&gt;data!\n",FUNCTION_MACRO)); \
 		ret; \
 	} \
 }
 
 #define SMB_VFS_HANDLE_SET_DATA(handle, datap, free_fn, type, ret) { \
 	if (!(handle)) { \
-		DEBUG(0,(&quot;%s() failed to set handle-&gt;data!\n&quot;,FUNCTION_MACRO)); \
+		DEBUG(0,("%s() failed to set handle-&gt;data!\n",FUNCTION_MACRO)); \
 		ret; \
 	} else { \
 		if ((handle)-&gt;free_data) { \
@@ -2298,20 +2298,20 @@ you can set this function pointer to NULL.</p></dd></dl></div><p>Some useful MAC
 	(handle)-&gt;vfs_next.handles.sendfile,\
 	 (tofd), (fsp), (fromfd), (header), (offset), (count)))
 ...
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879963"></a>Upgrading to the New VFS Interface</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879970"></a>Upgrading from 2.2.* and 3.0aplha modules</h3></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p>
-Add &quot;vfs_handle_struct *handle, &quot; as first parameter to all vfs operation functions.
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879360"></a>Upgrading to the New VFS Interface</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879367"></a>Upgrading from 2.2.* and 3.0aplha modules</h3></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p>
+Add "vfs_handle_struct *handle, " as first parameter to all vfs operation functions.
 e.g. example_connect(connection_struct *conn, const char *service, const char *user);
 -&gt;   example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user);
 </p></li><li><p>
-Replace &quot;default_vfs_ops.&quot; with &quot;smb_vfs_next_&quot;.
+Replace "default_vfs_ops." with "smb_vfs_next_".
 e.g. default_vfs_ops.connect(conn, service, user);
 -&gt;   smb_vfs_next_connect(conn, service, user);
 </p></li><li><p>
-Uppercase all &quot;smb_vfs_next_*&quot; functions.
+Uppercase all "smb_vfs_next_*" functions.
 e.g. smb_vfs_next_connect(conn, service, user);
 -&gt;   SMB_VFS_NEXT_CONNECT(conn, service, user);
 </p></li><li><p>
-Add &quot;handle, &quot; as first parameter to all SMB_VFS_NEXT_*() calls.
+Add "handle, " as first parameter to all SMB_VFS_NEXT_*() calls.
 e.g. SMB_VFS_NEXT_CONNECT(conn, service, user);
 -&gt;   SMB_VFS_NEXT_CONNECT(handle, conn, service, user);
 </p></li><li><p>
@@ -2411,7 +2411,7 @@ e.g.
 </p><pre class="programlisting">
 NTSTATUS init_module(void)
 {
-	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION,&quot;example&quot;,example_op_tuples);
+	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION,"example",example_op_tuples);
 }
 </pre><p>
 </p></li><li><p>
@@ -2447,14 +2447,14 @@ static int example_connect(vfs_handle_struct *handle,
 	/* alloc our private data */
 	data = (struct example_privates *)talloc_zero(conn-&gt;mem_ctx, sizeof(struct example_privates));
 	if (!data) {
-		DEBUG(0,(&quot;talloc_zero() failed\n&quot;));
+		DEBUG(0,("talloc_zero() failed\n"));
 		return -1;
 	}
 
 	/* init out private data */
-	data-&gt;some_string = talloc_strdup(conn-&gt;mem_ctx,&quot;test&quot;);
+	data-&gt;some_string = talloc_strdup(conn-&gt;mem_ctx,"test");
 	if (!data-&gt;some_string) {
-		DEBUG(0,(&quot;talloc_strdup() failed\n&quot;));
+		DEBUG(0,("talloc_strdup() failed\n"));
 		return -1;
 	}
 
@@ -2480,7 +2480,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
 	SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1);
 	
 	/* do something here...*/
-	DEBUG(0,(&quot;some_string: %s\n&quot;,data-&gt;some_string));
+	DEBUG(0,("some_string: %s\n",data-&gt;some_string));
 	
 	return SMB_VFS_NEXT_CLOSE(handle, fsp, fd);
 }
@@ -2508,14 +2508,14 @@ static int example_connect(vfs_handle_struct *handle,
 	/* alloc our private data */
 	data = (struct example_privates *)malloc(sizeof(struct example_privates));
 	if (!data) {
-		DEBUG(0,(&quot;malloc() failed\n&quot;));
+		DEBUG(0,("malloc() failed\n"));
 		return -1;
 	}
 
 	/* init out private data */
-	data-&gt;some_string = strdup(&quot;test&quot;);
+	data-&gt;some_string = strdup("test");
 	if (!data-&gt;some_string) {
-		DEBUG(0,(&quot;strdup() failed\n&quot;));
+		DEBUG(0,("strdup() failed\n"));
 		return -1;
 	}
 
@@ -2540,7 +2540,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
 	SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1);
 	
 	/* do something here...*/
-	DEBUG(0,(&quot;some_string: %s\n&quot;,data-&gt;some_string));
+	DEBUG(0,("some_string: %s\n",data-&gt;some_string));
 	
 	return SMB_VFS_NEXT_CLOSE(handle, fsp, fd);
 }
@@ -2561,7 +2561,7 @@ for your module.
 </p></li><li><p>
 Compiling &amp; Testing...
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><b class="userinput"><tt>./configure <tt class="option">--enable-developer</tt></tt></b> ...</td></tr><tr><td><b class="userinput"><tt>make</tt></b></td></tr><tr><td>Try to fix all compiler warnings</td></tr><tr><td><b class="userinput"><tt>make</tt></b></td></tr><tr><td>Testing, Testing, Testing ...</td></tr></table><p>
-</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880501"></a>Some Notes</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880508"></a>Implement TRANSPARENT functions</h3></div></div><div></div></div><p>
+</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879871"></a>Some Notes</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879878"></a>Implement TRANSPARENT functions</h3></div></div><div></div></div><p>
 Avoid writing functions like this:
 
 </p><pre class="programlisting">
@@ -2572,7 +2572,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)
 </pre><p>
 
 Overload only the functions you really need to!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880533"></a>Implement OPAQUE functions</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879903"></a>Implement OPAQUE functions</h3></div></div><div></div></div><p>
 If you want to just implement a better version of a 
 default samba opaque function
 (e.g. like a disk_free() function for a special filesystem) 
@@ -2588,16 +2588,16 @@ e.g. for a readonly filesystem.
 static int example_rename(vfs_handle_struct *handle, connection_struct *conn,
 			char *oldname, char *newname)
 {
-	DEBUG(10,(&quot;function rename() not allowed on vfs 'example'\n&quot;));
+	DEBUG(10,("function rename() not allowed on vfs 'example'\n"));
 	errno = ENOSYS;
 	return -1;
 }
-</pre></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Packaging"></a>Chapter�18.�Notes to packagers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2880600">Versioning</a></dt><dt><a href="#id2880635">Modules</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880600"></a>Versioning</h2></div></div><div></div></div><p>Please, please update the version number in 
+</pre></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Packaging"></a>Chapter�18.�Notes to packagers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="surname">Vernooij</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2879969">Versioning</a></dt><dt><a href="#id2880004">Modules</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879969"></a>Versioning</h2></div></div><div></div></div><p>Please, please update the version number in 
 <tt class="filename">source/include/version.h</tt> to include the versioning of your package. This makes it easier to distinguish standard samba builds
 from custom-build samba builds (distributions often patch packages). For 
 example, a good version would be: </p><pre class="programlisting">
 Version 2.999+3.0.alpha21-5 for Debian
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880635"></a>Modules</h2></div></div><div></div></div><p>Samba now has support for building parts of samba as plugins. This 
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880004"></a>Modules</h2></div></div><div></div></div><p>Samba now has support for building parts of samba as plugins. This 
 makes it possible to, for example, put ldap or mysql support in a seperate 
 package, thus making it possible to have a normal samba package not 
 depending on ldap or mysql. To build as much parts of samba 
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index bd68f32566..566f0b4068 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -34,49 +34,49 @@ insignificant number of ideas for inclusion (if not content itself) has been obt
 from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered.
 Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and
 application knowledge that is most to be desired by many Samba users and administrators.
-</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2799919">Legal Notice</a></dt><dt><a href="#id2799941">Attributions</a></dt><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2799013">Background</a></dt><dt><a href="#id2799095">Terminology</a></dt><dt><a href="#id2858014">Related Projects</a></dt><dt><a href="#id2858083">SMB Methodology</a></dt><dt><a href="#id2858171">Epilogue</a></dt><dt><a href="#id2858244">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2858386">Obtaining and installing samba</a></dt><dt><a href="#id2858430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2858468">Example Configuration</a></dt><dt><a href="#id2858657">SWAT</a></dt></dl></dd><dt><a href="#id2858703">Try listing the shares available on your 
-	server</a></dt><dt><a href="#id2858761">Try connecting with the unix client</a></dt><dt><a href="#id2858878">Try connecting from another SMB client</a></dt><dt><a href="#id2858961">What If Things Don't Work?</a></dt><dt><a href="#id2858993">Common Errors</a></dt><dd><dl><dt><a href="#id2859006">Large number of smbd processes</a></dt><dt><a href="#id2859105">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2859124">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2867442">Note</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2867622">Features and Benefits</a></dt><dt><a href="#id2867717">Server Types</a></dt><dt><a href="#id2867803">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867922">User Level Security</a></dt><dt><a href="#id2868060">Share Level Security</a></dt><dt><a href="#id2852162">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2852420">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2852521">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2869450">Password checking</a></dt><dt><a href="#id2869643">Common Errors</a></dt><dd><dl><dt><a href="#id2869671">What makes Samba a SERVER?</a></dt><dt><a href="#id2869710">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2869747">What makes Samba a Domain Member?</a></dt><dt><a href="#id2869786">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2870118">Features and Benefits</a></dt><dt><a href="#id2870332">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2870347">Domain Controller Types</a></dt><dt><a href="#id2870592">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2868460">Domain Control - Example Configuration</a></dt><dt><a href="#id2868947">Samba ADS Domain Control</a></dt><dt><a href="#id2868985">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2869000">Domain Network Logon Service</a></dt><dt><a href="#id2873169">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2873315">Common Errors</a></dt><dd><dl><dt><a href="#id2873322">'$' cannot be included in machine name</a></dt><dt><a href="#id2873381">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2873436">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2873520">The machine trust account not accessible</a></dt><dt><a href="#id2873592">Account disabled</a></dt><dt><a href="#id2873625">Domain Controller Unavailable</a></dt><dt><a href="#id2873647">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2873807">Features And Benefits</a></dt><dt><a href="#id2873997">Essential Background Information</a></dt><dd><dl><dt><a href="#id2874026">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2874268">Active Directory Domain Control</a></dt><dt><a href="#id2874289">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2874316">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2874329">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2874464">Example Configuration</a></dt></dl></dd><dt><a href="#id2874620">Common Errors</a></dt><dd><dl><dt><a href="#id2874633">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2874664">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2874691">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2874735">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2874943">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875556">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2875771">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875842">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2876053">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2876489">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2876674">Setup your smb.conf</a></dt><dt><a href="#id2876803">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2877177">Notes</a></dt></dl></dd><dt><a href="#id2877199">Common Errors</a></dt><dd><dl><dt><a href="#id2877226">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2877258">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2877459">Features and Benefits</a></dt><dt><a href="#id2877498">Background</a></dt><dt><a href="#id2877581">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2878101">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2878165">Note</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2878319">Features and Benefits</a></dt><dt><a href="#id2878408">What is Browsing?</a></dt><dt><a href="#id2878720">Discussion</a></dt><dd><dl><dt><a href="#id2878736">NetBIOS over TCP/IP</a></dt><dt><a href="#id2878972">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2879137">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2879284">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2879819">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2880217">Making Samba the domain master</a></dt><dt><a href="#id2880395">Note about broadcast addresses</a></dt><dt><a href="#id2880412">Multiple interfaces</a></dt><dt><a href="#id2880448">Use of the Remote Announce parameter</a></dt><dt><a href="#id2880607">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2880684">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2880872">Setting up a WINS server</a></dt><dt><a href="#id2881128">WINS Replication</a></dt><dt><a href="#id2881154">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2881238">Helpful Hints</a></dt><dd><dl><dt><a href="#id2881252">Windows Networking Protocols</a></dt><dt><a href="#id2881317">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2881481">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2881541">Browsing support in Samba</a></dt><dt><a href="#id2881662">Problem resolution</a></dt><dt><a href="#id2881749">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2882439">Common Errors</a></dt><dd><dl><dt><a href="#id2882454">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2882497">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2882539">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2882820">Features and Benefits</a></dt><dd><dl><dt><a href="#id2882834">Backwards Compatibility Backends</a></dt><dt><a href="#id2882936">New Backends</a></dt></dl></dd><dt><a href="#id2883109">Technical Information</a></dt><dd><dl><dt><a href="#id2883235">Important Notes About Security</a></dt><dt><a href="#id2883502">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2883688">The smbpasswd Command</a></dt><dt><a href="#id2883959">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2884197">Password Backends</a></dt><dd><dl><dt><a href="#id2884238">Plain Text</a></dt><dt><a href="#id2884279">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2884392">tdbsam</a></dt><dt><a href="#id2884420">ldapsam</a></dt><dt><a href="#id2886247">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2887095">Common Errors</a></dt><dd><dl><dt><a href="#id2887102">Users can not logon</a></dt><dt><a href="#id2887147">Users being added to wrong backend database</a></dt><dt><a href="#id2887258">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2887487">Features and Benefits</a></dt><dt><a href="#id2887722">Discussion</a></dt><dd><dl><dt><a href="#id2887948">Example Configuration</a></dt></dl></dd><dt><a href="#id2888015">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2888029">Sample smb.conf add group script</a></dt><dt><a href="#id2888108">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2888184">Common Errors</a></dt><dd><dl><dt><a href="#id2888199">Adding Groups Fails</a></dt><dt><a href="#id2888268">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2888294">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2888551">Features and Benefits</a></dt><dt><a href="#id2888688">File System Access Controls</a></dt><dd><dl><dt><a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2889023">Managing Directories</a></dt><dt><a href="#id2889117">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2889345">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2889373">User and Group Based Controls</a></dt><dt><a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2890173">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2890553">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2890626">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2890925">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2890933">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2890978">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2891057">Viewing file ownership</a></dt><dt><a href="#id2891188">Viewing File or Directory Permissions</a></dt><dt><a href="#id2891423">Modifying file or directory permissions</a></dt><dt><a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt><a href="#id2891979">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2892060">Common Errors</a></dt><dd><dl><dt><a href="#id2892074">Users can not write to a public share</a></dt><dt><a href="#id2892503">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2892555">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2892803">Features and Benefits</a></dt><dt><a href="#id2892860">Discussion</a></dt><dd><dl><dt><a href="#id2893002">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2893677">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2893787">Example Configuration</a></dt></dl></dd><dt><a href="#id2894184">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2894410">Workstation Service Entries</a></dt><dt><a href="#id2894437">Server Service Entries</a></dt></dl></dd><dt><a href="#id2894516">Persistent Data Corruption</a></dt><dt><a href="#id2894546">Common Errors</a></dt><dd><dl><dt><a href="#id2894619">locking.tdb error messages</a></dt><dt><a href="#id2894658">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2894680">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2894712">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2894878">Introduction</a></dt><dt><a href="#id2894910">Features and Benefits</a></dt><dt><a href="#id2894983">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2895003">Using host based protection</a></dt><dt><a href="#id2895102">User based protection</a></dt><dt><a href="#id2895162">Using interface protection</a></dt><dt><a href="#id2895230">Using a firewall</a></dt><dt><a href="#id2895287">Using a IPC$ share deny</a></dt><dt><a href="#id2895375">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2895433">Upgrading Samba</a></dt><dt><a href="#id2895457">Common Errors</a></dt><dd><dl><dt><a href="#id2895476">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2895500">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2895790">Features and Benefits</a></dt><dt><a href="#id2895819">Trust Relationship Background</a></dt><dt><a href="#id2895908">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2895935">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2896007">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2896054">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2896233">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2896417">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2896555">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2896661">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2896731">Features and Benefits</a></dt><dt><a href="#id2897006">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2897126">Features and Benefits</a></dt><dt><a href="#id2897192">Technical Introduction</a></dt><dd><dl><dt><a href="#id2897230">What happens if you send a Job from a Client</a></dt><dt><a href="#id2897302">Printing Related Configuration Parameters</a></dt><dt><a href="#id2897387">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2897853">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2898017">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2898105">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2898438">Extended Sample Configuration to Print</a></dt><dt><a href="#id2898769">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2898782">The [global] Section</a></dt><dt><a href="#id2899274">The [printers] Section</a></dt><dt><a href="#id2899717">Any [my_printer_name] Section</a></dt><dt><a href="#id2900032">Print Commands</a></dt><dt><a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2900758">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2901088">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2901237">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2901389">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2901502">Creating the [print$] Share</a></dt><dt><a href="#id2901686">Parameters in the [print$] Section</a></dt><dt><a href="#id2901973">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2902140">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2902234">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2902432">Setting Drivers for existing Printers with
-rpcclient</a></dt></dl></dd><dt><a href="#id2904055">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2904073">The first Client Driver Installation</a></dt><dt><a href="#id2904269">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2904576">Further Client Driver Install Procedures</a></dt><dt><a href="#id2904670">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2904838">Other Gotchas</a></dt><dd><dl><dt><a href="#id2904870">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2905319">Supporting large Numbers of Printers</a></dt><dt><a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2905915">Weird Error Message Cannot connect under a
-different Name</a></dt><dt><a href="#id2906013">Be careful when assembling Driver Files</a></dt><dt><a href="#id2906300">Samba and Printer Ports</a></dt><dt><a href="#id2906377">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2906398">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2906443">What is Imprints?</a></dt><dt><a href="#id2906484">Creating Printer Driver Packages</a></dt><dt><a href="#id2906504">The Imprints Server</a></dt><dt><a href="#id2906528">The Installation Client</a></dt></dl></dd><dt><a href="#id2906681">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2907000">The addprinter command</a></dt><dt><a href="#id2907046">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2907213">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2907227">Common Errors</a></dt><dd><dl><dt><a href="#id2907234">I give my root password but I don't get access</a></dt><dt><a href="#id2907268">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2907403">Introduction</a></dt><dd><dl><dt><a href="#id2907410">Features and Benefits</a></dt><dt><a href="#id2907453">Overview</a></dt></dl></dd><dt><a href="#id2907507">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2907600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2907841">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2908016">More complex smb.conf Settings for
-CUPS</a></dt></dl></dd><dt><a href="#id2908362">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2908382">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2908431">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2908485">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2908552">Explicitly enable "raw" printing for
-application/octet-stream!</a></dt><dt><a href="#id2908739">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2908865">Using CUPS/Samba in an advanced Way -- intelligent printing
-with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2909034">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2909441">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2909567">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2909654">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2909760">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2909782">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2909959">MIME types and CUPS Filters</a></dt><dt><a href="#id2910165">MIME type Conversion Rules</a></dt><dt><a href="#id2910315">Filter Requirements</a></dt><dt><a href="#id2910493">Prefilters</a></dt><dt><a href="#id2910595">pstops</a></dt><dt><a href="#id2910704">pstoraster</a></dt><dt><a href="#id2910875">imagetops and imagetoraster</a></dt><dt><a href="#id2910938">rasterto [printers specific]</a></dt><dt><a href="#id2911090">CUPS Backends</a></dt><dt><a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2911562">The Complete Picture</a></dt><dt><a href="#id2911576">mime.convs</a></dt><dt><a href="#id2911630">"Raw" printing</a></dt><dt><a href="#id2911697">"application/octet-stream" printing</a></dt><dt><a href="#id2911929">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a></dt><dt><a href="#id2912410">Examples for filtering Chains</a></dt><dt><a href="#id2912731">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2912872">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2912949">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2912965">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2913020">Driver Execution on the Client</a></dt><dt><a href="#id2913090">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2913201">Network Printing (Windows clients -- UNIX/Samba Print
-Servers)</a></dt><dd><dl><dt><a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2913432">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2913594">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2913643">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2913717">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2913734">Printer Drivers running in "Kernel Mode" cause many
-Problems</a></dt><dt><a href="#id2913768">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2913789">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2913833">PostScript Drivers with no major problems -- even in Kernel
-Mode</a></dt></dl></dd><dt><a href="#id2913895">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2913913">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2914014">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2914516">Recognize the different Driver Files</a></dt><dt><a href="#id2914656">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2914689">ESP Print Pro Package of "PostScript Driver for
-WinNT/2k/XP"</a></dt><dt><a href="#id2914749">Caveats to be considered</a></dt><dt><a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2915344">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2915567">Understanding cupsaddsmb</a></dt><dt><a href="#id2915714">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2915798">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2915877">cupsaddsmb Flowchart</a></dt><dt><a href="#id2915946">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2916097">Avoiding critical PostScript Driver Settings on the
-Client</a></dt></dl></dd><dt><a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a></dt><dd><dl><dt><a href="#id2916423">A Check of the rpcclient man Page</a></dt><dt><a href="#id2916536">Understanding the rpcclient man page</a></dt><dt><a href="#id2916644">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2916790">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2918021">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2918418">Trivial DataBase Files</a></dt><dt><a href="#id2918497">Binary Format</a></dt><dt><a href="#id2918559">Losing *.tdb Files</a></dt><dt><a href="#id2918617">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2918890">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2919583">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2920055">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2920098">Setting up Quotas</a></dt><dt><a href="#id2920162">Correct and incorrect Accounting</a></dt><dt><a href="#id2920202">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2920282">The page_log File Syntax</a></dt><dt><a href="#id2920392">Possible Shortcomings</a></dt><dt><a href="#id2920463">Future Developments</a></dt><dt><a href="#id2920510">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2920525">Additional Material</a></dt><dt><a href="#id2920734">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2920792">CUPS Configuration Settings explained</a></dt><dt><a href="#id2920874">Pre-conditions</a></dt><dt><a href="#id2921030">Manual Configuration</a></dt></dl></dd><dt><a href="#id2921088">In Case of Trouble.....</a></dt><dt><a href="#id2921154">Printing from CUPS to Windows attached
-Printers</a></dt><dt><a href="#id2921434">More CUPS filtering Chains</a></dt><dt><a href="#id2921535">Common Errors</a></dt><dd><dl><dt><a href="#id2921542">Win9x client can't install driver</a></dt><dt><a href="#id2921558">"cupsaddsmb" keeps asking for root password in
-			neverending loop</a></dt><dt><a href="#id2921604">"cupsaddsmb" gives "No PPD file for printer..."
-			message while PPD file is present</a></dt><dt><a href="#id2921660">Client can't connect to Samba printer</a></dt><dt><a href="#id2921688">Can't reconnect to Samba under new account
-			from Win2K/XP</a></dt><dt><a href="#id2921914">Avoid being connected to the Samba server as the
-		"wrong" user</a></dt><dt><a href="#id2921967">Upgrading to CUPS drivers from Adobe drivers on
-		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2921981">Can't use "cupsaddsmb" on Samba server which is
-		a PDC</a></dt><dt><a href="#id2922010">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2922027">Win2K/XP "Local Security
-		Policies"</a></dt><dt><a href="#id2922043">WinXP clients: "Administrator can not install
-		printers for all local users"</a></dt><dt><a href="#id2922065">"Print Change Notify" functions on
-		NT-clients</a></dt><dt><a href="#id2922084">WinXP-SP1</a></dt><dt><a href="#id2922126">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2922400">Most common blunders in driver
-		settings on Windows clients</a></dt><dt><a href="#id2922445">cupsaddsmb does not work
-		with newly installed printer</a></dt><dt><a href="#id2922506">Permissions on
+</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2796910">Legal Notice</a></dt><dt><a href="#id2799782">Attributions</a></dt><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2801584">Background</a></dt><dt><a href="#id2801642">Terminology</a></dt><dt><a href="#id2801779">Related Projects</a></dt><dt><a href="#id2801848">SMB Methodology</a></dt><dt><a href="#id2801936">Epilogue</a></dt><dt><a href="#id2802009">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2802151">Obtaining and installing samba</a></dt><dt><a href="#id2802195">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2802232">Example Configuration</a></dt><dt><a href="#id2866164">SWAT</a></dt></dl></dd><dt><a href="#id2866210">Try listing the shares available on your 
+	server</a></dt><dt><a href="#id2866267">Try connecting with the unix client</a></dt><dt><a href="#id2866384">Try connecting from another SMB client</a></dt><dt><a href="#id2866468">What If Things Don't Work?</a></dt><dt><a href="#id2866500">Common Errors</a></dt><dd><dl><dt><a href="#id2866513">Large number of smbd processes</a></dt><dt><a href="#id2866612">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2866630">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2866757">Note</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2866937">Features and Benefits</a></dt><dt><a href="#id2867038">Server Types</a></dt><dt><a href="#id2867124">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867244">User Level Security</a></dt><dt><a href="#id2867382">Share Level Security</a></dt><dt><a href="#id2867518">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2867776">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2867877">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868158">Password checking</a></dt><dt><a href="#id2868359">Common Errors</a></dt><dd><dl><dt><a href="#id2868387">What makes Samba a SERVER?</a></dt><dt><a href="#id2868427">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868463">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868503">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2868835">Features and Benefits</a></dt><dt><a href="#id2869049">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869064">Domain Controller Types</a></dt><dt><a href="#id2869309">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2869698">Domain Control - Example Configuration</a></dt><dt><a href="#id2870186">Samba ADS Domain Control</a></dt><dt><a href="#id2870238">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870253">Domain Network Logon Service</a></dt><dt><a href="#id2870678">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2870825">Common Errors</a></dt><dd><dl><dt><a href="#id2870831">'$' cannot be included in machine name</a></dt><dt><a href="#id2870890">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2870945">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871029">The machine trust account not accessible</a></dt><dt><a href="#id2871102">Account disabled</a></dt><dt><a href="#id2871135">Domain Controller Unavailable</a></dt><dt><a href="#id2871156">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2871317">Features And Benefits</a></dt><dt><a href="#id2871494">Essential Background Information</a></dt><dd><dl><dt><a href="#id2871522">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2871772">Active Directory Domain Control</a></dt><dt><a href="#id2871793">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2871819">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2871833">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2871968">Example Configuration</a></dt></dl></dd><dt><a href="#id2872125">Common Errors</a></dt><dd><dl><dt><a href="#id2872138">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872169">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872196">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872240">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2872448">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873061">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873276">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873347">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2873558">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2873995">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874178">Setup your smb.conf</a></dt><dt><a href="#id2874307">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2874683">Notes</a></dt></dl></dd><dt><a href="#id2874706">Common Errors</a></dt><dd><dl><dt><a href="#id2874732">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2874764">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2874966">Features and Benefits</a></dt><dt><a href="#id2875004">Background</a></dt><dt><a href="#id2875078">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2875598">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2875663">Note</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2875816">Features and Benefits</a></dt><dt><a href="#id2875904">What is Browsing?</a></dt><dt><a href="#id2876217">Discussion</a></dt><dd><dl><dt><a href="#id2876233">NetBIOS over TCP/IP</a></dt><dt><a href="#id2876469">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2876635">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2876781">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877309">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2877716">Making Samba the domain master</a></dt><dt><a href="#id2877893">Note about broadcast addresses</a></dt><dt><a href="#id2877911">Multiple interfaces</a></dt><dt><a href="#id2877946">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878104">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878182">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878371">Setting up a WINS server</a></dt><dt><a href="#id2878627">WINS Replication</a></dt><dt><a href="#id2878652">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2878737">Helpful Hints</a></dt><dd><dl><dt><a href="#id2878750">Windows Networking Protocols</a></dt><dt><a href="#id2878822">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2878986">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879046">Browsing support in Samba</a></dt><dt><a href="#id2879168">Problem resolution</a></dt><dt><a href="#id2879254">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2879936">Common Errors</a></dt><dd><dl><dt><a href="#id2879950">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2879979">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880021">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2880302">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880315">Backwards Compatibility Backends</a></dt><dt><a href="#id2880417">New Backends</a></dt></dl></dd><dt><a href="#id2880590">Technical Information</a></dt><dd><dl><dt><a href="#id2880717">Important Notes About Security</a></dt><dt><a href="#id2880966">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881151">The smbpasswd Command</a></dt><dt><a href="#id2881423">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2881676">Password Backends</a></dt><dd><dl><dt><a href="#id2881717">Plain Text</a></dt><dt><a href="#id2881758">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2881871">tdbsam</a></dt><dt><a href="#id2881898">ldapsam</a></dt><dt><a href="#id2883727">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2884575">Common Errors</a></dt><dd><dl><dt><a href="#id2884582">Users can not logon</a></dt><dt><a href="#id2884627">Users being added to wrong backend database</a></dt><dt><a href="#id2884738">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2884967">Features and Benefits</a></dt><dt><a href="#id2885202">Discussion</a></dt><dd><dl><dt><a href="#id2885422">Example Configuration</a></dt></dl></dd><dt><a href="#id2885489">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2885503">Sample smb.conf add group script</a></dt><dt><a href="#id2885582">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2885658">Common Errors</a></dt><dd><dl><dt><a href="#id2885674">Adding Groups Fails</a></dt><dt><a href="#id2885742">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2885768">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2886024">Features and Benefits</a></dt><dt><a href="#id2886154">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2886489">Managing Directories</a></dt><dt><a href="#id2886582">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2886810">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2886837">User and Group Based Controls</a></dt><dt><a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2887639">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888020">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888092">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2888391">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2888399">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2888444">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2888523">Viewing file ownership</a></dt><dt><a href="#id2888655">Viewing File or Directory Permissions</a></dt><dt><a href="#id2888889">Modifying file or directory permissions</a></dt><dt><a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt><a href="#id2889446">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2889526">Common Errors</a></dt><dd><dl><dt><a href="#id2889540">Users can not write to a public share</a></dt><dt><a href="#id2889969">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890022">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2890270">Features and Benefits</a></dt><dt><a href="#id2890336">Discussion</a></dt><dd><dl><dt><a href="#id2890479">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891158">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2891268">Example Configuration</a></dt></dl></dd><dt><a href="#id2891665">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2891896">Workstation Service Entries</a></dt><dt><a href="#id2891924">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892003">Persistent Data Corruption</a></dt><dt><a href="#id2892032">Common Errors</a></dt><dd><dl><dt><a href="#id2892106">locking.tdb error messages</a></dt><dt><a href="#id2892144">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892167">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892198">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2892365">Introduction</a></dt><dt><a href="#id2892398">Features and Benefits</a></dt><dt><a href="#id2892471">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2892490">Using host based protection</a></dt><dt><a href="#id2892590">User based protection</a></dt><dt><a href="#id2892650">Using interface protection</a></dt><dt><a href="#id2892717">Using a firewall</a></dt><dt><a href="#id2892774">Using a IPC$ share deny</a></dt><dt><a href="#id2892867">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2892926">Upgrading Samba</a></dt><dt><a href="#id2892950">Common Errors</a></dt><dd><dl><dt><a href="#id2892968">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2892992">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2893283">Features and Benefits</a></dt><dt><a href="#id2893311">Trust Relationship Background</a></dt><dt><a href="#id2893400">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2893428">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2893500">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2893547">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2893725">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2893918">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894055">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894162">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2894231">Features and Benefits</a></dt><dt><a href="#id2894506">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2894626">Features and Benefits</a></dt><dt><a href="#id2894693">Technical Introduction</a></dt><dd><dl><dt><a href="#id2894730">What happens if you send a Job from a Client</a></dt><dt><a href="#id2894801">Printing Related Configuration Parameters</a></dt><dt><a href="#id2894888">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2895354">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2895518">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2895606">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2895939">Extended Sample Configuration to Print</a></dt><dt><a href="#id2896270">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2896282">The [global] Section</a></dt><dt><a href="#id2896767">The [printers] Section</a></dt><dt><a href="#id2897210">Any [my_printer_name] Section</a></dt><dt><a href="#id2897534">Print Commands</a></dt><dt><a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2898261">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2898591">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2898740">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2898892">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2899004">Creating the [print$] Share</a></dt><dt><a href="#id2899189">Parameters in the [print$] Section</a></dt><dt><a href="#id2899475">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2899643">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2899736">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2899935">Setting Drivers for existing Printers with
+rpcclient</a></dt></dl></dd><dt><a href="#id2901625">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2901643">The first Client Driver Installation</a></dt><dt><a href="#id2901839">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2902136">Further Client Driver Install Procedures</a></dt><dt><a href="#id2902231">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2902399">Other Gotchas</a></dt><dd><dl><dt><a href="#id2902431">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2902874">Supporting large Numbers of Printers</a></dt><dt><a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2903470">Weird Error Message Cannot connect under a
+different Name</a></dt><dt><a href="#id2903569">Be careful when assembling Driver Files</a></dt><dt><a href="#id2903854">Samba and Printer Ports</a></dt><dt><a href="#id2903932">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2903954">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2903998">What is Imprints?</a></dt><dt><a href="#id2904040">Creating Printer Driver Packages</a></dt><dt><a href="#id2904059">The Imprints Server</a></dt><dt><a href="#id2904083">The Installation Client</a></dt></dl></dd><dt><a href="#id2904236">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2904556">The addprinter command</a></dt><dt><a href="#id2904602">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2904779">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2904793">Common Errors</a></dt><dd><dl><dt><a href="#id2904800">I give my root password but I don't get access</a></dt><dt><a href="#id2904834">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2904970">Introduction</a></dt><dd><dl><dt><a href="#id2904977">Features and Benefits</a></dt><dt><a href="#id2905020">Overview</a></dt></dl></dd><dt><a href="#id2905074">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2905167">Linking of smbd with libcups.so</a></dt><dt><a href="#id2905408">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2905584">More complex smb.conf Settings for
+CUPS</a></dt></dl></dd><dt><a href="#id2905929">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2905949">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2905999">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2906051">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2906119">Explicitly enable "raw" printing for
+application/octet-stream!</a></dt><dt><a href="#id2906306">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2906432">Using CUPS/Samba in an advanced Way -- intelligent printing
+with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2906600">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2907029">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2907154">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2907241">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2907348">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2907370">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2907545">MIME types and CUPS Filters</a></dt><dt><a href="#id2907752">MIME type Conversion Rules</a></dt><dt><a href="#id2907903">Filter Requirements</a></dt><dt><a href="#id2908080">Prefilters</a></dt><dt><a href="#id2908183">pstops</a></dt><dt><a href="#id2908292">pstoraster</a></dt><dt><a href="#id2908476">imagetops and imagetoraster</a></dt><dt><a href="#id2908539">rasterto [printers specific]</a></dt><dt><a href="#id2908691">CUPS Backends</a></dt><dt><a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2909176">The Complete Picture</a></dt><dt><a href="#id2909191">mime.convs</a></dt><dt><a href="#id2909245">"Raw" printing</a></dt><dt><a href="#id2909312">"application/octet-stream" printing</a></dt><dt><a href="#id2909544">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a></dt><dt><a href="#id2910018">Examples for filtering Chains</a></dt><dt><a href="#id2910331">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2910470">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2910560">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2910577">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2910632">Driver Execution on the Client</a></dt><dt><a href="#id2910701">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2910813">Network Printing (Windows clients -- UNIX/Samba Print
+Servers)</a></dt><dd><dl><dt><a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2911043">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2911206">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2911255">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2911328">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2911345">Printer Drivers running in "Kernel Mode" cause many
+Problems</a></dt><dt><a href="#id2911379">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2911400">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2911445">PostScript Drivers with no major problems -- even in Kernel
+Mode</a></dt></dl></dd><dt><a href="#id2911506">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2911524">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2911625">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2912128">Recognize the different Driver Files</a></dt><dt><a href="#id2912268">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2912301">ESP Print Pro Package of "PostScript Driver for
+WinNT/2k/XP"</a></dt><dt><a href="#id2912362">Caveats to be considered</a></dt><dt><a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2912958">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2913117">Understanding cupsaddsmb</a></dt><dt><a href="#id2913264">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2913349">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2913427">cupsaddsmb Flowchart</a></dt><dt><a href="#id2913497">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2913646">Avoiding critical PostScript Driver Settings on the
+Client</a></dt></dl></dd><dt><a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a></dt><dd><dl><dt><a href="#id2913973">A Check of the rpcclient man Page</a></dt><dt><a href="#id2914086">Understanding the rpcclient man page</a></dt><dt><a href="#id2914186">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2914333">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2915566">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2915962">Trivial DataBase Files</a></dt><dt><a href="#id2916041">Binary Format</a></dt><dt><a href="#id2916103">Losing *.tdb Files</a></dt><dt><a href="#id2916162">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2916436">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2917129">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2917602">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2917645">Setting up Quotas</a></dt><dt><a href="#id2917708">Correct and incorrect Accounting</a></dt><dt><a href="#id2917748">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2917829">The page_log File Syntax</a></dt><dt><a href="#id2917938">Possible Shortcomings</a></dt><dt><a href="#id2918010">Future Developments</a></dt><dt><a href="#id2918058">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2918072">Additional Material</a></dt><dt><a href="#id2918267">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2918326">CUPS Configuration Settings explained</a></dt><dt><a href="#id2918407">Pre-conditions</a></dt><dt><a href="#id2918564">Manual Configuration</a></dt></dl></dd><dt><a href="#id2918622">In Case of Trouble.....</a></dt><dt><a href="#id2918682">Printing from CUPS to Windows attached
+Printers</a></dt><dt><a href="#id2918955">More CUPS filtering Chains</a></dt><dt><a href="#id2796634">Common Errors</a></dt><dd><dl><dt><a href="#id2796642">Win9x client can't install driver</a></dt><dt><a href="#id2919061">"cupsaddsmb" keeps asking for root password in
+			neverending loop</a></dt><dt><a href="#id2919107">"cupsaddsmb" gives "No PPD file for printer..."
+			message while PPD file is present</a></dt><dt><a href="#id2919163">Client can't connect to Samba printer</a></dt><dt><a href="#id2919497">Can't reconnect to Samba under new account
+			from Win2K/XP</a></dt><dt><a href="#id2919582">Avoid being connected to the Samba server as the
+		"wrong" user</a></dt><dt><a href="#id2919635">Upgrading to CUPS drivers from Adobe drivers on
+		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2919649">Can't use "cupsaddsmb" on Samba server which is
+		a PDC</a></dt><dt><a href="#id2919678">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2919695">Win2K/XP "Local Security
+		Policies"</a></dt><dt><a href="#id2919711">WinXP clients: "Administrator can not install
+		printers for all local users"</a></dt><dt><a href="#id2919733">"Print Change Notify" functions on
+		NT-clients</a></dt><dt><a href="#id2919752">WinXP-SP1</a></dt><dt><a href="#id2919794">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2920067">Most common blunders in driver
+		settings on Windows clients</a></dt><dt><a href="#id2920114">cupsaddsmb does not work
+		with newly installed printer</a></dt><dt><a href="#id2920175">Permissions on
 /var/spool/samba/ get reset after each
-reboot</a></dt><dt><a href="#id2922615">Printer named "lp"
+reboot</a></dt><dt><a href="#id2920284">Printer named "lp"
 intermittently swallows jobs and spits out completely different
-ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2922701">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2922871">Features and Benefits</a></dt><dt><a href="#id2922889">Discussion</a></dt><dt><a href="#id2923117">Included modules</a></dt><dd><dl><dt><a href="#id2923124">audit</a></dt><dt><a href="#id2923166">extd_audit</a></dt><dt><a href="#id2923296">fake_perms</a></dt><dt><a href="#id2923316">recycle</a></dt><dt><a href="#id2923485">netatalk</a></dt></dl></dd><dt><a href="#id2923530">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2923552">DatabaseFS</a></dt><dt><a href="#id2923606">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2923836">Features and Benefits</a></dt><dt><a href="#id2923931">Introduction</a></dt><dt><a href="#id2924016">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2924076">Target Uses</a></dt></dl></dd><dt><a href="#id2924107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2924136">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2924169">Microsoft Active Directory Services</a></dt><dt><a href="#id2924192">Name Service Switch</a></dt><dt><a href="#id2924320">Pluggable Authentication Modules</a></dt><dt><a href="#id2924402">User and Group ID Allocation</a></dt><dt><a href="#id2924435">Result Caching</a></dt></dl></dd><dt><a href="#id2924463">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2924471">Introduction</a></dt><dt><a href="#id2924538">Requirements</a></dt><dt><a href="#id2924632">Testing Things Out</a></dt></dl></dd><dt><a href="#id2926199">Conclusion</a></dt><dt><a href="#id2926218">Common Errors</a></dt><dd><dl><dt><a href="#id2926270">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2926379">Features and Benefits</a></dt><dt><a href="#id2926410">Remote Server Administration</a></dt><dt><a href="#id2926508">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2926526">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2926738">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2927010">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2927044">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2927123">Features and Benefits</a></dt><dt><a href="#id2927177">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2927288">Windows 9x/Me Policies</a></dt><dt><a href="#id2927384">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2927516">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2927780">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2927886">Samba Editreg Toolset</a></dt><dt><a href="#id2927925">Windows NT4/200x</a></dt><dt><a href="#id2927945">Samba PDC</a></dt></dl></dd><dt><a href="#id2927990">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2928140">Common Errors</a></dt><dd><dl><dt><a href="#id2928154">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2928255">Features and Benefits</a></dt><dt><a href="#id2928289">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2928330">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2928820">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2930060">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2930144">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2930397">Mandatory profiles</a></dt><dt><a href="#id2930455">Creating/Managing Group Profiles</a></dt><dt><a href="#id2930500">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2930520">MS Windows 9x/Me</a></dt><dt><a href="#id2930668">MS Windows NT4 Workstation</a></dt><dt><a href="#id2931222">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2931730">Common Errors</a></dt><dd><dl><dt><a href="#id2931743">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2931812">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2932026">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2932306">Features and Benefits</a></dt><dt><a href="#id2932554">Technical Discussion</a></dt><dd><dl><dt><a href="#id2932572">PAM Configuration Syntax</a></dt><dt><a href="#id2933235">Example System Configurations</a></dt><dt><a href="#id2933539">smb.conf PAM Configuration</a></dt><dt><a href="#id2933617">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2933706">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2934094">Common Errors</a></dt><dd><dl><dt><a href="#id2934108">pam_winbind problem</a></dt><dt><a href="#id2934194">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2934432">Features and Benefits</a></dt><dt><a href="#id2934457">Background Information</a></dt><dt><a href="#id2934521">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2934577">/etc/hosts</a></dt><dt><a href="#id2934718">/etc/resolv.conf</a></dt><dt><a href="#id2934762">/etc/host.conf</a></dt><dt><a href="#id2934813">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2934918">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2935185">The NetBIOS Name Cache</a></dt><dt><a href="#id2935248">The LMHOSTS file</a></dt><dt><a href="#id2935496">HOSTS file</a></dt><dt><a href="#id2935528">DNS Lookup</a></dt><dt><a href="#id2935560">WINS Lookup</a></dt></dl></dd><dt><a href="#id2935678">Common Errors</a></dt><dd><dl><dt><a href="#id2935694">Pinging works only in one way</a></dt><dt><a href="#id2935729">Very Slow Network Connections</a></dt><dt><a href="#id2935780">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2935983">Features and Benefits</a></dt><dt><a href="#id2936027">What are charsets and unicode?</a></dt><dt><a href="#id2936097">Samba and charsets</a></dt><dt><a href="#id2936224">Conversion from old names</a></dt><dt><a href="#id2936254">Japanese charsets</a></dt><dt><a href="#id2936392">Common errors</a></dt><dd><dl><dt><a href="#id2936398">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2936512">Note</a></dt><dt><a href="#id2936526">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2936596">Note</a></dt></dl></dd></dl></dd><dt>IV. <a href="#migration">Migration and Updating</a></dt><dd><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2936735">New Features in Samba-3</a></dt><dt><a href="#id2936865">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2936880">Removed Parameters</a></dt><dt><a href="#id2937006">New Parameters</a></dt><dt><a href="#id2937402">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2937476">New Functionality</a></dt><dd><dl><dt><a href="#id2937483">Databases</a></dt><dt><a href="#id2937718">Changes in Behavior</a></dt><dt><a href="#id2937767">Charsets</a></dt><dt><a href="#id2937791">Passdb Backends and Authentication</a></dt><dt><a href="#id2937909">Charsets</a></dt><dt><a href="#id2937933">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2938265">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2938290">Objectives</a></dt><dt><a href="#id2938728">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2938940">Migration Options</a></dt><dd><dl><dt><a href="#id2939031">Planning for Success</a></dt><dt><a href="#id2939287">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2939647">Features and Benefits</a></dt><dd><dl><dt><a href="#id2939686">Enabling SWAT for use</a></dt><dt><a href="#id2939924">Securing SWAT through SSL</a></dt><dt><a href="#id2940035">The SWAT Home Page</a></dt><dt><a href="#id2940097">Global Settings</a></dt><dt><a href="#id2940204">Share Settings</a></dt><dt><a href="#id2940268">Printers Settings</a></dt><dt><a href="#id2940332">The SWAT Wizard</a></dt><dt><a href="#id2940380">The Status Page</a></dt><dt><a href="#id2940432">The View Page</a></dt><dt><a href="#id2940455">The Password Change Page</a></dt></dl></dd></dl></dd></dl></dd><dt>V. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2940585">Introduction</a></dt><dt><a href="#id2940619">Assumptions</a></dt><dt><a href="#id2940846">The tests</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2942320">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2942341">Debugging with Samba itself</a></dt><dt><a href="#id2942454">Tcpdump</a></dt><dt><a href="#id2942476">Ethereal</a></dt><dt><a href="#id2942528">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2942845">Useful URLs</a></dt><dt><a href="#id2942886">Getting help from the mailing lists</a></dt><dt><a href="#id2870642">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2870770">Introduction</a></dt><dt><a href="#id2870833">General info</a></dt><dt><a href="#id2870870">Debug levels</a></dt><dt><a href="#id2871078">Internal errors</a></dt><dt><a href="#id2871212">Attaching to a running process</a></dt><dt><a href="#id2871258">Patches</a></dt></dl></dd></dl></dd><dt>VI. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>36. <a href="#compiling">How to compile Samba</a></dt><dd><dl><dt><a href="#id2871417">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2871434">Introduction</a></dt><dt><a href="#id2871464">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2871712">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2871776">Verifying Samba's PGP signature</a></dt><dt><a href="#id2871926">Building the Binaries</a></dt><dd><dl><dt><a href="#id2872104">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2872271">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2872378">Starting from inetd.conf</a></dt><dt><a href="#id2872625">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2872789">HPUX</a></dt><dt><a href="#id2872876">SCO UNIX</a></dt><dt><a href="#id2872906">DNIX</a></dt><dt><a href="#id2943012">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943056">AIX</a></dt><dd><dl><dt><a href="#id2943063">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943089">Solaris</a></dt><dd><dl><dt><a href="#id2943096">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2943249">Macintosh clients?</a></dt><dt><a href="#id2943327">OS2 Client</a></dt><dd><dl><dt><a href="#id2943334">Configuring OS/2 Warp Connect or 
-			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943403">Configuring OS/2 Warp 3 (not Connect), 
-			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943455">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943555">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943563">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943653">Delete .pwl files after password change</a></dt><dt><a href="#id2943683">Configuring WfW password handling</a></dt><dt><a href="#id2943736">Case handling of passwords</a></dt><dt><a href="#id2943774">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943791">Speed improvement</a></dt></dl></dd><dt><a href="#id2943837">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2943911">Speed improvement</a></dt></dl></dd><dt><a href="#id2943935">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944122">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2944254">Comparisons</a></dt><dt><a href="#id2944298">Socket options</a></dt><dt><a href="#id2944388">Read size</a></dt><dt><a href="#id2944438">Max xmit</a></dt><dt><a href="#id2944498">Log level</a></dt><dt><a href="#id2944528">Read raw</a></dt><dt><a href="#id2944612">Write raw</a></dt><dt><a href="#id2944675">Slow Logins</a></dt><dt><a href="#id2944704">Client tuning</a></dt><dt><a href="#id2944729">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944774">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2944876">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2944943">Websites</a></dt><dt><a href="#id2945351">Related updates from Microsoft</a></dt></dl></dd></dl></dd><dt><a href="#id2945421">Index</a></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="#domain-example">An Example Domain</a></dt><dt>10.1. <a href="#browsing1">Cross subnet browsing example</a></dt><dt>11.1. <a href="#idmap-diag">IDMAP</a></dt><dt>12.1. <a href="#idmap-group-diag">IDMAP groups</a></dt><dt>13.1. <a href="#access1">Overview of unix permissions field</a></dt><dt>16.1. <a href="#trusts1">Trusts overview</a></dt><dt>19.1. <a href="#small1">Windows Printing to a local Printer</a></dt><dt>19.2. <a href="#small2">Printing to a Postscript Printer</a></dt><dt>19.3. <a href="#small3">Ghostscript as a RIP for non-postscript printers</a></dt><dt>19.4. <a href="#small4">Prefiltering in CUPS to form Postscript</a></dt><dt>19.5. <a href="#small5">Adding Device-specific Print Options</a></dt><dt>19.6. <a href="#small6">Postscript to intermediate Raster format</a></dt><dt>19.7. <a href="#small7">CUPS-raster production using Ghostscript</a></dt><dt>19.8. <a href="#small8">Image format to CUPS-raster format conversion</a></dt><dt>19.9. <a href="#small9">Raster to Printer Specific formats</a></dt><dt>19.10. <a href="#small10">cupsomatic/foomatic processing versus Native CUPS</a></dt><dt>19.11. <a href="#pdftosocket">PDF to socket chain</a></dt><dt>19.12. <a href="#pdftoepsonusb">PDF to USB chain</a></dt><dt>19.13. <a href="#small11">Print Driver execution on the Client</a></dt><dt>19.14. <a href="#small12">Print Driver execution on the Server</a></dt><dt>19.15. <a href="#small13">Printing via CUPS/samba server</a></dt><dt>19.16. <a href="#small14">cupsaddsmb flowchart</a></dt><dt>19.17. <a href="#cups1">Filtering chain 1</a></dt><dt>19.18. <a href="#cups2">Filtering chain with cupsomatic</a></dt><dt>19.19. <a href="#a_small">CUPS Printing Overview</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id2876064">Assumptions</a></dt><dt>10.1. <a href="#id2881940">Browse subnet example 1</a></dt><dt>10.2. <a href="#id2882053">Browse subnet example 2</a></dt><dt>10.3. <a href="#id2882166">Browse subnet example 3</a></dt><dt>10.4. <a href="#id2882283">Browse subnet example 4</a></dt><dt>11.1. <a href="#id2885640">Attributes in the sambaSamAccount objectclass (LDAP)</a></dt><dt>11.2. <a href="#id2886434">Basic smb.conf options for MySQL passdb backend</a></dt><dt>11.3. <a href="#id2886566">MySQL field names for MySQL passdb backend</a></dt><dt>13.1. <a href="#id2889043">Managing directories with unix and windows</a></dt><dt>13.2. <a href="#id2889459">User and Group Based Controls</a></dt><dt>13.3. <a href="#id2889815">File and Directory Permission Based Controls</a></dt><dt>13.4. <a href="#id2890195">Other Controls</a></dt><dt>19.1. <a href="#id2912008">PPD's shipped with CUPS</a></dt><dt>20.1. <a href="#id2923214">Extended Auditing Log Information</a></dt><dt>24.1. <a href="#id2931019">User Shell Folder registry keys default values</a></dt><dt>24.2. <a href="#id2931163">Defaults of profile settings registry keys</a></dt><dt>24.3. <a href="#id2931418">Defaults of default user profile paths registry keys</a></dt><dt>25.1. <a href="#id2933738">Options recognized by pam_smbpass</a></dt><dt>26.1. <a href="#id2934950">Unique NetBIOS names</a></dt><dt>26.2. <a href="#id2935020">Group Names</a></dt><dt>30.1. <a href="#id2937502">TDB File Descriptions</a></dt><dt>31.1. <a href="#id2938955">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2939102">Nature of the Conversion Choices</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>2.1. <a href="#id2858491">Simplest possible smb.conf file</a></dt><dt>5.1. <a href="#pdc-example">smb.conf for being a PDC</a></dt><dt>5.2. <a href="#id2869056">smb.conf for being a PDC</a></dt><dt>6.1. <a href="#id2874200">Minimal smb.conf for being a PDC</a></dt><dt>6.2. <a href="#id2874479">Minimal setup for being a BDC</a></dt><dt>8.1. <a href="#id2877627">smb.conf for Reference Documentation Server</a></dt><dt>8.2. <a href="#id2877945">smb.conf for anonymous printing</a></dt><dt>10.1. <a href="#id2879534">Domain master browser smb.conf</a></dt><dt>10.2. <a href="#id2879624">Local master browser smb.conf</a></dt><dt>10.3. <a href="#id2879762">smb.conf for not being a master browser</a></dt><dt>10.4. <a href="#id2879868">Local master browser smb.conf</a></dt><dt>10.5. <a href="#id2879985">smb.conf for not being a master browser</a></dt><dt>11.1. <a href="#idmapbackendexample"></a></dt><dt>11.2. <a href="#id2885206">Configuration with LDAP</a></dt><dt>12.1. <a href="#id2888052">smbgrpadd.sh</a></dt><dt>13.1. <a href="#id2889268">Example File</a></dt><dt>14.1. <a href="#id2893990">Share with some files oplocked</a></dt><dt>14.2. <a href="#id2894131"></a></dt><dt>17.1. <a href="#id2896842">smb.conf with DFS configured</a></dt><dt>18.1. <a href="#id2897881">Simple configuration with BSD printing</a></dt><dt>18.2. <a href="#extbsdpr">Extended configuration with BSD printing</a></dt><dt>18.3. <a href="#id2901544">[print\$] example</a></dt><dt>19.1. <a href="#id2907869">Simplest printing-related smb.conf</a></dt><dt>19.2. <a href="#id2908047">Overriding global CUPS settings for one printer</a></dt><dt>19.3. <a href="#id2914041">smb.conf for cupsaddsmb usage</a></dt><dt>20.1. <a href="#id2922927">smb.conf with VFS modules</a></dt><dt>20.2. <a href="#id2923026">smb.conf with multiple VFS modules</a></dt><dt>21.1. <a href="#id2925020">smb.conf for winbind set-up</a></dt><dt>33.1. <a href="#id2940668">smb.conf with [tmp] share</a></dt><dt>38.1. <a href="#id2944007">Minimal profile share</a></dt></dl></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2799919"></a>Legal Notice</h2></div></div><div></div></div><p>
+ones</a></dt><dt><a href="#id2920314">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2920369">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2920538">Features and Benefits</a></dt><dt><a href="#id2920556">Discussion</a></dt><dt><a href="#id2920786">Included modules</a></dt><dd><dl><dt><a href="#id2920793">audit</a></dt><dt><a href="#id2920835">extd_audit</a></dt><dt><a href="#id2920965">fake_perms</a></dt><dt><a href="#id2920984">recycle</a></dt><dt><a href="#id2921153">netatalk</a></dt></dl></dd><dt><a href="#id2921198">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2921220">DatabaseFS</a></dt><dt><a href="#id2921286">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2921516">Features and Benefits</a></dt><dt><a href="#id2921611">Introduction</a></dt><dt><a href="#id2921688">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2921756">Target Uses</a></dt></dl></dd><dt><a href="#id2921786">How Winbind Works</a></dt><dd><dl><dt><a href="#id2921815">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2921849">Microsoft Active Directory Services</a></dt><dt><a href="#id2921872">Name Service Switch</a></dt><dt><a href="#id2922009">Pluggable Authentication Modules</a></dt><dt><a href="#id2922081">User and Group ID Allocation</a></dt><dt><a href="#id2922128">Result Caching</a></dt></dl></dd><dt><a href="#id2922156">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2922164">Introduction</a></dt><dt><a href="#id2922231">Requirements</a></dt><dt><a href="#id2922333">Testing Things Out</a></dt></dl></dd><dt><a href="#id2923890">Conclusion</a></dt><dt><a href="#id2923909">Common Errors</a></dt><dd><dl><dt><a href="#id2923962">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2924071">Features and Benefits</a></dt><dt><a href="#id2924101">Remote Server Administration</a></dt><dt><a href="#id2924200">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2924218">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2924438">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2924711">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2924744">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2924822">Features and Benefits</a></dt><dt><a href="#id2924888">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2924999">Windows 9x/Me Policies</a></dt><dt><a href="#id2925094">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2925227">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2925491">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2925596">Samba Editreg Toolset</a></dt><dt><a href="#id2925636">Windows NT4/200x</a></dt><dt><a href="#id2925655">Samba PDC</a></dt></dl></dd><dt><a href="#id2925700">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2925851">Common Errors</a></dt><dd><dl><dt><a href="#id2925865">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2925964">Features and Benefits</a></dt><dt><a href="#id2925999">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2926040">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2926530">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2927776">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2927861">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2928114">Mandatory profiles</a></dt><dt><a href="#id2928172">Creating/Managing Group Profiles</a></dt><dt><a href="#id2928216">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2928237">MS Windows 9x/Me</a></dt><dt><a href="#id2928385">MS Windows NT4 Workstation</a></dt><dt><a href="#id2928939">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2929447">Common Errors</a></dt><dd><dl><dt><a href="#id2929460">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2929529">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2929742">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2930024">Features and Benefits</a></dt><dt><a href="#id2930271">Technical Discussion</a></dt><dd><dl><dt><a href="#id2930288">PAM Configuration Syntax</a></dt><dt><a href="#id2930969">Example System Configurations</a></dt><dt><a href="#id2931283">smb.conf PAM Configuration</a></dt><dt><a href="#id2931361">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2931445">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2931826">Common Errors</a></dt><dd><dl><dt><a href="#id2931839">pam_winbind problem</a></dt><dt><a href="#id2931926">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2932164">Features and Benefits</a></dt><dt><a href="#id2932188">Background Information</a></dt><dt><a href="#id2932259">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2932315">/etc/hosts</a></dt><dt><a href="#id2932456">/etc/resolv.conf</a></dt><dt><a href="#id2932499">/etc/host.conf</a></dt><dt><a href="#id2932551">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2932655">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2932922">The NetBIOS Name Cache</a></dt><dt><a href="#id2932985">The LMHOSTS file</a></dt><dt><a href="#id2933234">HOSTS file</a></dt><dt><a href="#id2933266">DNS Lookup</a></dt><dt><a href="#id2933298">WINS Lookup</a></dt></dl></dd><dt><a href="#id2933416">Common Errors</a></dt><dd><dl><dt><a href="#id2933432">Pinging works only in one way</a></dt><dt><a href="#id2933465">Very Slow Network Connections</a></dt><dt><a href="#id2933517">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2933721">Features and Benefits</a></dt><dt><a href="#id2933765">What are charsets and unicode?</a></dt><dt><a href="#id2933835">Samba and charsets</a></dt><dt><a href="#id2933962">Conversion from old names</a></dt><dt><a href="#id2933992">Japanese charsets</a></dt><dt><a href="#id2934130">Common errors</a></dt><dd><dl><dt><a href="#id2934137">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2934250">Note</a></dt><dt><a href="#id2934264">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2934334">Note</a></dt></dl></dd></dl></dd><dt>IV. <a href="#migration">Migration and Updating</a></dt><dd><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2934473">New Features in Samba-3</a></dt><dt><a href="#id2934602">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2934617">Removed Parameters</a></dt><dt><a href="#id2934744">New Parameters</a></dt><dt><a href="#id2935140">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2935215">New Functionality</a></dt><dd><dl><dt><a href="#id2935222">Databases</a></dt><dt><a href="#id2935456">Changes in Behavior</a></dt><dt><a href="#id2935505">Charsets</a></dt><dt><a href="#id2935529">Passdb Backends and Authentication</a></dt><dt><a href="#id2935648">Charsets</a></dt><dt><a href="#id2935672">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2936004">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2936029">Objectives</a></dt><dt><a href="#id2936467">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2936679">Migration Options</a></dt><dd><dl><dt><a href="#id2936770">Planning for Success</a></dt><dt><a href="#id2937026">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2937386">Features and Benefits</a></dt><dd><dl><dt><a href="#id2937426">Enabling SWAT for use</a></dt><dt><a href="#id2937663">Securing SWAT through SSL</a></dt><dt><a href="#id2937775">The SWAT Home Page</a></dt><dt><a href="#id2937837">Global Settings</a></dt><dt><a href="#id2937944">Share Settings</a></dt><dt><a href="#id2938008">Printers Settings</a></dt><dt><a href="#id2938072">The SWAT Wizard</a></dt><dt><a href="#id2938120">The Status Page</a></dt><dt><a href="#id2938171">The View Page</a></dt><dt><a href="#id2938195">The Password Change Page</a></dt></dl></dd></dl></dd></dl></dd><dt>V. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2938325">Introduction</a></dt><dt><a href="#id2938359">Assumptions</a></dt><dt><a href="#id2938586">The tests</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2940060">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2940082">Debugging with Samba itself</a></dt><dt><a href="#id2940195">Tcpdump</a></dt><dt><a href="#id2940216">Ethereal</a></dt><dt><a href="#id2940268">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2940586">Useful URLs</a></dt><dt><a href="#id2940626">Getting help from the mailing lists</a></dt><dt><a href="#id2940778">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2940906">Introduction</a></dt><dt><a href="#id2940969">General info</a></dt><dt><a href="#id2941006">Debug levels</a></dt><dt><a href="#id2941215">Internal errors</a></dt><dt><a href="#id2941348">Attaching to a running process</a></dt><dt><a href="#id2941395">Patches</a></dt></dl></dd></dl></dd><dt>VI. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>36. <a href="#compiling">How to compile Samba</a></dt><dd><dl><dt><a href="#id2941554">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2941570">Introduction</a></dt><dt><a href="#id2941600">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2941849">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2941913">Verifying Samba's PGP signature</a></dt><dt><a href="#id2942063">Building the Binaries</a></dt><dd><dl><dt><a href="#id2942242">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2942409">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2942516">Starting from inetd.conf</a></dt><dt><a href="#id2942763">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2942927">HPUX</a></dt><dt><a href="#id2943015">SCO UNIX</a></dt><dt><a href="#id2943044">DNIX</a></dt><dt><a href="#id2943217">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943261">AIX</a></dt><dd><dl><dt><a href="#id2943268">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943294">Solaris</a></dt><dd><dl><dt><a href="#id2943299">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2943452">Macintosh clients?</a></dt><dt><a href="#id2943531">OS2 Client</a></dt><dd><dl><dt><a href="#id2943538">Configuring OS/2 Warp Connect or 
+			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943607">Configuring OS/2 Warp 3 (not Connect), 
+			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943660">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943760">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943768">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943858">Delete .pwl files after password change</a></dt><dt><a href="#id2943888">Configuring WfW password handling</a></dt><dt><a href="#id2943941">Case handling of passwords</a></dt><dt><a href="#id2943979">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943996">Speed improvement</a></dt></dl></dd><dt><a href="#id2944042">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2944116">Speed improvement</a></dt></dl></dd><dt><a href="#id2944140">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944326">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2944458">Comparisons</a></dt><dt><a href="#id2944501">Socket options</a></dt><dt><a href="#id2944592">Read size</a></dt><dt><a href="#id2944641">Max xmit</a></dt><dt><a href="#id2944701">Log level</a></dt><dt><a href="#id2944732">Read raw</a></dt><dt><a href="#id2944816">Write raw</a></dt><dt><a href="#id2944879">Slow Logins</a></dt><dt><a href="#id2944908">Client tuning</a></dt><dt><a href="#id2944932">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944965">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2945070">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2945137">Websites</a></dt><dt><a href="#id2945545">Related updates from Microsoft</a></dt></dl></dd></dl></dd><dt><a href="#id2945614">Index</a></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="#domain-example">An Example Domain</a></dt><dt>10.1. <a href="#browsing1">Cross subnet browsing example</a></dt><dt>11.1. <a href="#idmap-diag">IDMAP</a></dt><dt>12.1. <a href="#idmap-group-diag">IDMAP groups</a></dt><dt>13.1. <a href="#access1">Overview of unix permissions field</a></dt><dt>16.1. <a href="#trusts1">Trusts overview</a></dt><dt>19.1. <a href="#small1">Windows Printing to a local Printer</a></dt><dt>19.2. <a href="#small2">Printing to a Postscript Printer</a></dt><dt>19.3. <a href="#small3">Ghostscript as a RIP for non-postscript printers</a></dt><dt>19.4. <a href="#small4">Prefiltering in CUPS to form Postscript</a></dt><dt>19.5. <a href="#small5">Adding Device-specific Print Options</a></dt><dt>19.6. <a href="#small6">Postscript to intermediate Raster format</a></dt><dt>19.7. <a href="#small7">CUPS-raster production using Ghostscript</a></dt><dt>19.8. <a href="#small8">Image format to CUPS-raster format conversion</a></dt><dt>19.9. <a href="#small9">Raster to Printer Specific formats</a></dt><dt>19.10. <a href="#small10">cupsomatic/foomatic processing versus Native CUPS</a></dt><dt>19.11. <a href="#pdftosocket">PDF to socket chain</a></dt><dt>19.12. <a href="#pdftoepsonusb">PDF to USB chain</a></dt><dt>19.13. <a href="#small11">Print Driver execution on the Client</a></dt><dt>19.14. <a href="#small12">Print Driver execution on the Server</a></dt><dt>19.15. <a href="#small13">Printing via CUPS/samba server</a></dt><dt>19.16. <a href="#small14">cupsaddsmb flowchart</a></dt><dt>19.17. <a href="#cups1">Filtering chain 1</a></dt><dt>19.18. <a href="#cups2">Filtering chain with cupsomatic</a></dt><dt>19.19. <a href="#a_small">CUPS Printing Overview</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id2873569">Assumptions</a></dt><dt>10.1. <a href="#id2879437">Browse subnet example 1</a></dt><dt>10.2. <a href="#id2879550">Browse subnet example 2</a></dt><dt>10.3. <a href="#id2879662">Browse subnet example 3</a></dt><dt>10.4. <a href="#id2879779">Browse subnet example 4</a></dt><dt>11.1. <a href="#id2883118">Attributes in the sambaSamAccount objectclass (LDAP)</a></dt><dt>11.2. <a href="#id2883914">Basic smb.conf options for MySQL passdb backend</a></dt><dt>11.3. <a href="#id2884046">MySQL field names for MySQL passdb backend</a></dt><dt>13.1. <a href="#id2886508">Managing directories with unix and windows</a></dt><dt>13.2. <a href="#id2886925">User and Group Based Controls</a></dt><dt>13.3. <a href="#id2887281">File and Directory Permission Based Controls</a></dt><dt>13.4. <a href="#id2887661">Other Controls</a></dt><dt>19.1. <a href="#id2909623">PPD's shipped with CUPS</a></dt><dt>20.1. <a href="#id2920882">Extended Auditing Log Information</a></dt><dt>24.1. <a href="#id2928735">User Shell Folder registry keys default values</a></dt><dt>24.2. <a href="#id2928879">Defaults of profile settings registry keys</a></dt><dt>24.3. <a href="#id2929134">Defaults of default user profile paths registry keys</a></dt><dt>25.1. <a href="#id2931477">Options recognized by pam_smbpass</a></dt><dt>26.1. <a href="#id2932688">Unique NetBIOS names</a></dt><dt>26.2. <a href="#id2932758">Group Names</a></dt><dt>30.1. <a href="#id2935241">TDB File Descriptions</a></dt><dt>31.1. <a href="#id2936694">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2936841">Nature of the Conversion Choices</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>2.1. <a href="#id2802256">Simplest possible smb.conf file</a></dt><dt>5.1. <a href="#pdc-example">smb.conf for being a PDC</a></dt><dt>5.2. <a href="#id2870309">smb.conf for being a PDC</a></dt><dt>6.1. <a href="#id2871704">Minimal smb.conf for being a PDC</a></dt><dt>6.2. <a href="#id2871983">Minimal setup for being a BDC</a></dt><dt>8.1. <a href="#id2875123">smb.conf for Reference Documentation Server</a></dt><dt>8.2. <a href="#id2875442">smb.conf for anonymous printing</a></dt><dt>10.1. <a href="#id2877023">Domain master browser smb.conf</a></dt><dt>10.2. <a href="#id2877114">Local master browser smb.conf</a></dt><dt>10.3. <a href="#id2877252">smb.conf for not being a master browser</a></dt><dt>10.4. <a href="#id2877358">Local master browser smb.conf</a></dt><dt>10.5. <a href="#id2877475">smb.conf for not being a master browser</a></dt><dt>11.1. <a href="#idmapbackendexample"></a></dt><dt>11.2. <a href="#id2882685">Configuration with LDAP</a></dt><dt>12.1. <a href="#id2885526">smbgrpadd.sh</a></dt><dt>13.1. <a href="#id2886704">Example File</a></dt><dt>14.1. <a href="#id2891471">Share with some files oplocked</a></dt><dt>14.2. <a href="#id2891612"></a></dt><dt>17.1. <a href="#id2894342">smb.conf with DFS configured</a></dt><dt>18.1. <a href="#id2895382">Simple configuration with BSD printing</a></dt><dt>18.2. <a href="#extbsdpr">Extended configuration with BSD printing</a></dt><dt>18.3. <a href="#id2899046">[print\$] example</a></dt><dt>19.1. <a href="#id2905436">Simplest printing-related smb.conf</a></dt><dt>19.2. <a href="#id2905615">Overriding global CUPS settings for one printer</a></dt><dt>19.3. <a href="#id2911654">smb.conf for cupsaddsmb usage</a></dt><dt>20.1. <a href="#id2920594">smb.conf with VFS modules</a></dt><dt>20.2. <a href="#id2920694">smb.conf with multiple VFS modules</a></dt><dt>21.1. <a href="#id2922722">smb.conf for winbind set-up</a></dt><dt>33.1. <a href="#id2938408">smb.conf with [tmp] share</a></dt><dt>38.1. <a href="#id2944212">Minimal profile share</a></dt></dl></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2796910"></a>Legal Notice</h2></div></div><div></div></div><p>
 This documentation is distributed under the GNU General Public License (GPL) 
 version 2.  A copy of the license is included with the Samba source
 distribution.  A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a>
-</p></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2799941"></a>Attributions</h2></div></div><div></div></div><p><a href="#IntroSMB" title="Chapter�1.�Introduction to Samba">Introduction to Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>David Lechnyr &lt;<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>&gt;</p></li></ul></div><p><a href="#install" title="Chapter�2.�How to Install and Test SAMBA">How to Install and Test SAMBA</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Karl Auer</p></li></ul></div><p><a href="#FastStart" title="Chapter�3.�Fast Start for the Impatient">Fast Start for the Impatient</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ServerType" title="Chapter�4.�Server Types and Security Modes">Server Types and Security Modes</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#samba-pdc" title="Chapter�5.�Domain Control">Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>David Bannon &lt;<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>&gt;</p></li></ul></div><p><a href="#samba-bdc" title="Chapter�6.�Backup Domain Control">Backup Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Volker Lendecke &lt;<a href="mailto:Volker.Lendecke@SerNet.DE" target="_top">Volker.Lendecke@SerNet.DE</a>&gt;</p></li></ul></div><p><a href="#domain-member" title="Chapter�7.�Domain Membership">Domain Membership</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#StandAloneServer" title="Chapter�8.�Stand-Alone Servers">Stand-Alone Servers</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ClientConfig" title="Chapter�9.�MS Windows Network Configuration Guide">MS Windows Network Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Samba / MS Windows Network Browsing Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#passdb" title="Chapter�11.�Account Information Databases">Account Information Databases</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Olivier (lem) Lemaire &lt;<a href="mailto:olem@IDEALX.org" target="_top">olem@IDEALX.org</a>&gt;</p></li></ul></div><p><a href="#groupmapping" title="Chapter�12.�Mapping MS Windows and UNIX Groups">Mapping MS Windows and UNIX Groups</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jean Fran�ois Micouleau</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#AccessControls" title="Chapter�13.�File, Directory and Share Access Controls">File, Directory and Share Access Controls</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawing) </p></li></ul></div><p><a href="#locking" title="Chapter�14.�File and Record Locking">File and Record Locking</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Eric Roseme &lt;<a href="mailto:eric.roseme@hp.com" target="_top">eric.roseme@hp.com</a>&gt;</p></li></ul></div><p><a href="#securing-samba" title="Chapter�15.�Securing Samba">Securing Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#InterdomainTrusts" title="Chapter�16.�Interdomain Trust Relationships">Interdomain Trust Relationships</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Rafal Szczesniak &lt;<a href="mailto:mimir@samba.org" target="_top">mimir@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawing) </p></li><li><p>Stephen Langasek &lt;<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>&gt;</p></li></ul></div><p><a href="#msdfs" title="Chapter�17.�Hosting a Microsoft Distributed File System tree on Samba">Hosting a Microsoft Distributed File System tree on Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Shirish Kalele &lt;<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>&gt;</p></li></ul></div><p><a href="#printing" title="Chapter�18.�Classical Printing Support">Classical Printing Support</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle &lt;<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li></ul></div><p><a href="#CUPS-printing" title="Chapter�19.�CUPS Printing Support in Samba 3.0">CUPS Printing Support in Samba 3.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle &lt;<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>&gt;</p></li><li><p>Ciprian Vizitiu &lt;<a href="mailto:CVizitiu@gbif.org" target="_top">CVizitiu@gbif.org</a>&gt; (drawings) </p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawings) </p></li></ul></div><p><a href="#VFS" title="Chapter�20.�Stackable VFS modules">Stackable VFS modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Tim Potter</p></li><li><p>Simo Sorce (original vfs_skel README) </p></li><li><p>Alexander Bokovoy (original vfs_netatalk docs) </p></li><li><p>Stefan Metzmacher (Update for multiple modules) </p></li></ul></div><p><a href="#AdvancedNetworkManagement" title="Chapter�22.�Advanced Network Management">Advanced Network Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#PolicyMgmt" title="Chapter�23.�System and Account Policies">System and Account Policies</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ProfileMgmt" title="Chapter�24.�Desktop Profile Management">Desktop Profile Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#pam" title="Chapter�25.�PAM based Distributed Authentication">PAM based Distributed Authentication</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Stephen Langasek &lt;<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>&gt;</p></li></ul></div><p><a href="#integrate-ms-networks" title="Chapter�26.�Integrating MS Windows networks with Samba">Integrating MS Windows networks with Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#unicode" title="Chapter�27.�Unicode/Charsets">Unicode/Charsets</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>TAKAHASHI Motonobu &lt;<a href="mailto:monyo@home.monyo.com" target="_top">monyo@home.monyo.com</a>&gt;</p></li></ul></div><p><a href="#Backup" title="Chapter�28.�Samba Backup Techniques">Samba Backup Techniques</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#SambaHA" title="Chapter�29.�High Availability Options">High Availability Options</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#upgrading-to-3.0" title="Chapter�30.�Upgrading from Samba-2.x to Samba-3.0.0">Upgrading from Samba-2.x to Samba-3.0.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li></ul></div><p><a href="#NT4Migration" title="Chapter�31.�Migration from NT4 PDC to Samba-3 PDC">Migration from NT4 PDC to Samba-3 PDC</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#SWAT" title="Chapter�32.�SWAT - The Samba Web Administration Tool">SWAT - The Samba Web Administration Tool</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#diagnosis" title="Chapter�33.�The Samba checklist">The Samba checklist</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#problems" title="Chapter�34.�Analysing and solving samba problems">Analysing and solving samba problems</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>David Bannon &lt;<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>&gt;</p></li></ul></div><p><a href="#bugreport" title="Chapter�35.�Reporting Bugs">Reporting Bugs</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#compiling" title="Chapter�36.�How to compile Samba">How to compile Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#Portability" title="Chapter�37.�Portability">Portability</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#Other-Clients" title="Chapter�38.�Samba and other CIFS clients">Samba and other CIFS clients</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Jim McDonough &lt;<a href="mailto:jmcd@us.ibm.com" target="_top">jmcd@us.ibm.com</a>&gt; (OS/2) </p></li></ul></div><p><a href="#speed" title="Chapter�39.�Samba Performance Tuning">Samba Performance Tuning</a></p><div class="itemizedlist"><ul type="disc"><li><p>Paul Cochrane &lt;<a href="mailto:paulc@dth.scot.nhs.uk" target="_top">paulc@dth.scot.nhs.uk</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#DNSDHCP" title="Chapter�40.�DNS and DHCP Configuration Guide">DNS and DHCP Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#Further-Resources" title="Chapter�41.�Further Resources">Further Resources</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2798930"></a>Preparing Samba for Configuration</h1></div></div><div></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba 
+</p></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2799782"></a>Attributions</h2></div></div><div></div></div><p><a href="#IntroSMB" title="Chapter�1.�Introduction to Samba">Introduction to Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>David Lechnyr &lt;<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>&gt;</p></li></ul></div><p><a href="#install" title="Chapter�2.�How to Install and Test SAMBA">How to Install and Test SAMBA</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Karl Auer</p></li></ul></div><p><a href="#FastStart" title="Chapter�3.�Fast Start for the Impatient">Fast Start for the Impatient</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ServerType" title="Chapter�4.�Server Types and Security Modes">Server Types and Security Modes</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#samba-pdc" title="Chapter�5.�Domain Control">Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>David Bannon &lt;<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>&gt;</p></li></ul></div><p><a href="#samba-bdc" title="Chapter�6.�Backup Domain Control">Backup Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Volker Lendecke &lt;<a href="mailto:Volker.Lendecke@SerNet.DE" target="_top">Volker.Lendecke@SerNet.DE</a>&gt;</p></li></ul></div><p><a href="#domain-member" title="Chapter�7.�Domain Membership">Domain Membership</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#StandAloneServer" title="Chapter�8.�Stand-Alone Servers">Stand-Alone Servers</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ClientConfig" title="Chapter�9.�MS Windows Network Configuration Guide">MS Windows Network Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Samba / MS Windows Network Browsing Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#passdb" title="Chapter�11.�Account Information Databases">Account Information Databases</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Olivier (lem) Lemaire &lt;<a href="mailto:olem@IDEALX.org" target="_top">olem@IDEALX.org</a>&gt;</p></li></ul></div><p><a href="#groupmapping" title="Chapter�12.�Mapping MS Windows and UNIX Groups">Mapping MS Windows and UNIX Groups</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jean Fran�ois Micouleau</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#AccessControls" title="Chapter�13.�File, Directory and Share Access Controls">File, Directory and Share Access Controls</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawing) </p></li></ul></div><p><a href="#locking" title="Chapter�14.�File and Record Locking">File and Record Locking</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison &lt;<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Eric Roseme &lt;<a href="mailto:eric.roseme@hp.com" target="_top">eric.roseme@hp.com</a>&gt;</p></li></ul></div><p><a href="#securing-samba" title="Chapter�15.�Securing Samba">Securing Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#InterdomainTrusts" title="Chapter�16.�Interdomain Trust Relationships">Interdomain Trust Relationships</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Rafal Szczesniak &lt;<a href="mailto:mimir@samba.org" target="_top">mimir@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawing) </p></li><li><p>Stephen Langasek &lt;<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>&gt;</p></li></ul></div><p><a href="#msdfs" title="Chapter�17.�Hosting a Microsoft Distributed File System tree on Samba">Hosting a Microsoft Distributed File System tree on Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Shirish Kalele &lt;<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>&gt;</p></li></ul></div><p><a href="#printing" title="Chapter�18.�Classical Printing Support">Classical Printing Support</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle &lt;<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li></ul></div><p><a href="#CUPS-printing" title="Chapter�19.�CUPS Printing Support in Samba 3.0">CUPS Printing Support in Samba 3.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle &lt;<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>&gt;</p></li><li><p>Ciprian Vizitiu &lt;<a href="mailto:CVizitiu@gbif.org" target="_top">CVizitiu@gbif.org</a>&gt; (drawings) </p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt; (drawings) </p></li></ul></div><p><a href="#VFS" title="Chapter�20.�Stackable VFS modules">Stackable VFS modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Tim Potter</p></li><li><p>Simo Sorce (original vfs_skel README) </p></li><li><p>Alexander Bokovoy (original vfs_netatalk docs) </p></li><li><p>Stefan Metzmacher (Update for multiple modules) </p></li></ul></div><p><a href="#AdvancedNetworkManagement" title="Chapter�22.�Advanced Network Management">Advanced Network Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#PolicyMgmt" title="Chapter�23.�System and Account Policies">System and Account Policies</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#ProfileMgmt" title="Chapter�24.�Desktop Profile Management">Desktop Profile Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#pam" title="Chapter�25.�PAM based Distributed Authentication">PAM based Distributed Authentication</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Stephen Langasek &lt;<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>&gt;</p></li></ul></div><p><a href="#integrate-ms-networks" title="Chapter�26.�Integrating MS Windows networks with Samba">Integrating MS Windows networks with Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#unicode" title="Chapter�27.�Unicode/Charsets">Unicode/Charsets</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>TAKAHASHI Motonobu &lt;<a href="mailto:monyo@home.monyo.com" target="_top">monyo@home.monyo.com</a>&gt;</p></li></ul></div><p><a href="#Backup" title="Chapter�28.�Samba Backup Techniques">Samba Backup Techniques</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#SambaHA" title="Chapter�29.�High Availability Options">High Availability Options</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#upgrading-to-3.0" title="Chapter�30.�Upgrading from Samba-2.x to Samba-3.0.0">Upgrading from Samba-2.x to Samba-3.0.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li></ul></div><p><a href="#NT4Migration" title="Chapter�31.�Migration from NT4 PDC to Samba-3 PDC">Migration from NT4 PDC to Samba-3 PDC</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#SWAT" title="Chapter�32.�SWAT - The Samba Web Administration Tool">SWAT - The Samba Web Administration Tool</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#diagnosis" title="Chapter�33.�The Samba checklist">The Samba checklist</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#problems" title="Chapter�34.�Analysing and solving samba problems">Analysing and solving samba problems</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald (Jerry)  Carter &lt;<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>David Bannon &lt;<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>&gt;</p></li></ul></div><p><a href="#bugreport" title="Chapter�35.�Reporting Bugs">Reporting Bugs</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#compiling" title="Chapter�36.�How to compile Samba">How to compile Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Andrew Tridgell &lt;<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>&gt;</p></li></ul></div><p><a href="#Portability" title="Chapter�37.�Portability">Portability</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div><p><a href="#Other-Clients" title="Chapter�38.�Samba and other CIFS clients">Samba and other CIFS clients</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>Jim McDonough &lt;<a href="mailto:jmcd@us.ibm.com" target="_top">jmcd@us.ibm.com</a>&gt; (OS/2) </p></li></ul></div><p><a href="#speed" title="Chapter�39.�Samba Performance Tuning">Samba Performance Tuning</a></p><div class="itemizedlist"><ul type="disc"><li><p>Paul Cochrane &lt;<a href="mailto:paulc@dth.scot.nhs.uk" target="_top">paulc@dth.scot.nhs.uk</a>&gt;</p></li><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#DNSDHCP" title="Chapter�40.�DNS and DHCP Configuration Guide">DNS and DHCP Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H.  Terpstra &lt;<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>&gt;</p></li></ul></div><p><a href="#Further-Resources" title="Chapter�41.�Further Resources">Further Resources</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R.  Vernooij &lt;<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>&gt;</p></li></ul></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2801502"></a>Preparing Samba for Configuration</h1></div></div><div></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba 
 and how to configure the parts of samba you will most likely need.
-PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2799013">Background</a></dt><dt><a href="#id2799095">Terminology</a></dt><dt><a href="#id2858014">Related Projects</a></dt><dt><a href="#id2858083">SMB Methodology</a></dt><dt><a href="#id2858171">Epilogue</a></dt><dt><a href="#id2858244">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2858386">Obtaining and installing samba</a></dt><dt><a href="#id2858430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2858468">Example Configuration</a></dt><dt><a href="#id2858657">SWAT</a></dt></dl></dd><dt><a href="#id2858703">Try listing the shares available on your 
-	server</a></dt><dt><a href="#id2858761">Try connecting with the unix client</a></dt><dt><a href="#id2858878">Try connecting from another SMB client</a></dt><dt><a href="#id2858961">What If Things Don't Work?</a></dt><dt><a href="#id2858993">Common Errors</a></dt><dd><dl><dt><a href="#id2859006">Large number of smbd processes</a></dt><dt><a href="#id2859105">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2859124">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2867442">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Chapter�1.�Introduction to Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2799013">Background</a></dt><dt><a href="#id2799095">Terminology</a></dt><dt><a href="#id2858014">Related Projects</a></dt><dt><a href="#id2858083">SMB Methodology</a></dt><dt><a href="#id2858171">Epilogue</a></dt><dt><a href="#id2858244">Miscellaneous</a></dt></dl></div><p>&#8220;<span class="quote">
+PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2801584">Background</a></dt><dt><a href="#id2801642">Terminology</a></dt><dt><a href="#id2801779">Related Projects</a></dt><dt><a href="#id2801848">SMB Methodology</a></dt><dt><a href="#id2801936">Epilogue</a></dt><dt><a href="#id2802009">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2802151">Obtaining and installing samba</a></dt><dt><a href="#id2802195">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2802232">Example Configuration</a></dt><dt><a href="#id2866164">SWAT</a></dt></dl></dd><dt><a href="#id2866210">Try listing the shares available on your 
+	server</a></dt><dt><a href="#id2866267">Try connecting with the unix client</a></dt><dt><a href="#id2866384">Try connecting from another SMB client</a></dt><dt><a href="#id2866468">What If Things Don't Work?</a></dt><dt><a href="#id2866500">Common Errors</a></dt><dd><dl><dt><a href="#id2866513">Large number of smbd processes</a></dt><dt><a href="#id2866612">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2866630">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2866757">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Chapter�1.�Introduction to Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2801584">Background</a></dt><dt><a href="#id2801642">Terminology</a></dt><dt><a href="#id2801779">Related Projects</a></dt><dt><a href="#id2801848">SMB Methodology</a></dt><dt><a href="#id2801936">Epilogue</a></dt><dt><a href="#id2802009">Miscellaneous</a></dt></dl></div><p>&#8220;<span class="quote">
 "If you understand what you're doing, you're not learning anything." 
 -- Anonymous
 </span>&#8221;</p><p>
@@ -85,7 +85,7 @@ transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of
 strengths is that you can use it to blend your mix of Windows and Linux machines together
 without requiring a separate Windows NT/2000/2003 Server.  Samba is actively being developed
 by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2799013"></a>Background</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801584"></a>Background</h2></div></div><div></div></div><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
@@ -111,7 +111,7 @@ been dutifully waded through during the information-gathering stages of this pro
 are *still* many missing pieces... While often tedious, at least the way has been generously
 littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
 thinking?
-</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2799095"></a>Terminology</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801642"></a>Terminology</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
 	SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.
 	</p></li><li><p>
 	CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently
@@ -161,7 +161,7 @@ thinking?
 	W3K: Acronym for Windows 2003 Server
 	</p></li></ul></div><p>If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at 
 <a href="http://www.samba.org/" target="_top">http://www.samba.org</a>). 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858014"></a>Related Projects</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801779"></a>Related Projects</h2></div></div><div></div></div><p>
 There are currently two network filesystem client projects for Linux that are directly
 related to Samba: SMBFS and CIFS VFS.  These are both available in the Linux kernel itself.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -183,7 +183,7 @@ nothing to do with acting as a file and print server for SMB/CIFS clients.
 There are other Open Source CIFS client implementations, such as the 
 <a href="http://jcifs.samba.org/" target="_top">jCIFS project</a>
 which provides an SMB client toolkit written in Java.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858083"></a>SMB Methodology</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801848"></a>SMB Methodology</h2></div></div><div></div></div><p>
 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
@@ -215,7 +215,7 @@ up a single file. In general, SMB sessions are established in the following orde
 A good way to examine this process in depth is to try out 
 <a href="http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html" target="_top">SecurityFriday's SWB program</a>.
 It allows you to walk through the establishment of a SMB/CIFS session step by step.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858171"></a>Epilogue</h2></div></div><div></div></div><p>&#8220;<span class="quote">
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2801936"></a>Epilogue</h2></div></div><div></div></div><p>&#8220;<span class="quote">
 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
@@ -244,13 +244,13 @@ not the completely clueless user who probably sits there shivering thinking
 That's what's really irritating to me."
 </span>&#8221;</p><p>-- 
 <a href="http://hr.uoregon.edu/davidrl/boot.txt" target="_top">Linus Torvalds, from an interview with BOOT Magazine, Sept 1998</a>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858244"></a>Miscellaneous</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2802009"></a>Miscellaneous</h2></div></div><div></div></div><p>
 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" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter�2.�How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Karl</span> <span class="surname">Auer</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2858386">Obtaining and installing samba</a></dt><dt><a href="#id2858430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2858468">Example Configuration</a></dt><dt><a href="#id2858657">SWAT</a></dt></dl></dd><dt><a href="#id2858703">Try listing the shares available on your 
-	server</a></dt><dt><a href="#id2858761">Try connecting with the unix client</a></dt><dt><a href="#id2858878">Try connecting from another SMB client</a></dt><dt><a href="#id2858961">What If Things Don't Work?</a></dt><dt><a href="#id2858993">Common Errors</a></dt><dd><dl><dt><a href="#id2859006">Large number of smbd processes</a></dt><dt><a href="#id2859105">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2859124">"The network name cannot be found"</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858386"></a>Obtaining and installing samba</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter�2.�How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Karl</span> <span class="surname">Auer</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2802151">Obtaining and installing samba</a></dt><dt><a href="#id2802195">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2802232">Example Configuration</a></dt><dt><a href="#id2866164">SWAT</a></dt></dl></dd><dt><a href="#id2866210">Try listing the shares available on your 
+	server</a></dt><dt><a href="#id2866267">Try connecting with the unix client</a></dt><dt><a href="#id2866384">Try connecting from another SMB client</a></dt><dt><a href="#id2866468">What If Things Don't Work?</a></dt><dt><a href="#id2866500">Common Errors</a></dt><dd><dl><dt><a href="#id2866513">Large number of smbd processes</a></dt><dt><a href="#id2866612">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2866630">"The network name cannot be found"</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2802151"></a>Obtaining and installing samba</h2></div></div><div></div></div><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>.
@@ -258,21 +258,21 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 		<a href="#compiling" title="Chapter�36.�How to compile Samba">the chapter about compiling samba from scratch</a>.</p><p>If you have already installed samba, or if your operating system
 	was pre-installed with samba, then you may not need to bother with this
 	chapter. On the other hand, you may want to read this chapter anyhow
-	for information about updating samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858430"></a>Configuring samba (smb.conf)</h2></div></div><div></div></div><p>
+	for information about updating samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2802195"></a>Configuring samba (smb.conf)</h2></div></div><div></div></div><p>
 	Samba's configuration is stored in the <tt class="filename">smb.conf</tt> 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2858468"></a>Example Configuration</h3></div></div><div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2802232"></a>Example Configuration</h3></div></div><div></div></div><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>
 	The simplest useful configuration file would be something like this:
 	</p><p>
-	</p><div class="example"><a name="id2858491"></a><p class="title"><b>Example�2.1.�Simplest possible smb.conf file</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[homes]</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr></table></div><p>
+	</p><div class="example"><a name="id2802256"></a><p class="title"><b>Example�2.1.�Simplest possible smb.conf file</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[homes]</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr></table></div><p>
 	</p><p>
 	This will allow connections by anyone with an account on the server, using either
 	their login name or <i class="parameter"><tt>homes</tt></i>" as the service name.
@@ -284,7 +284,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 	For more information about security settings for the 
 	<i class="parameter"><tt>[homes]</tt></i> share please refer to 
 	<a href="#securing-samba" title="Chapter�15.�Securing Samba">"Securing Samba"</a>.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2858604"></a>Test your config file with <b class="command">testparm</b></h4></div></div><div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2866111"></a>Test your config file with <b class="command">testparm</b></h4></div></div><div></div></div><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.
@@ -292,7 +292,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 	Make sure it runs OK and that the services look reasonable before proceeding.
 	</p><p>
 	Always run testparm again when you change <tt class="filename">smb.conf</tt>!
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2858657"></a>SWAT</h3></div></div><div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866164"></a>SWAT</h3></div></div><div></div></div><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 separate package. Please read the swat manpage 
@@ -308,7 +308,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 	machine but connecting from a remote machine leaves your 
 	connection open to password sniffing as passwords will be sent 
 	in the clear over the wire. 
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858703"></a>Try listing the shares available on your 
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866210"></a>Try listing the shares available on your 
 	server</h2></div></div><div></div></div><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient -L <i class="replaceable"><tt>yourhostname</tt></i></tt></b>
 </pre><p>You should get back a list of shares available on 
@@ -319,7 +319,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 	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></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858761"></a>Try connecting with the unix client</h2></div></div><div></div></div><p>
+	with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866267"></a>Try connecting with the unix client</h2></div></div><div></div></div><p>
 </p><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient <i class="replaceable"><tt> //yourhostname/aservice</tt></i></tt></b>
 </pre><p>Typically the <i class="replaceable"><tt>yourhostname</tt></i> 
@@ -331,19 +331,19 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li
 	in <tt class="filename">smb.conf</tt>.</p><p>For example if your unix host is <i class="replaceable"><tt>bambi</tt></i>
 	and your login name is <i class="replaceable"><tt>fred</tt></i> you would type:</p><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient //<i class="replaceable"><tt>bambi</tt></i>/<i class="replaceable"><tt>fred</tt></i></tt></b>
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858878"></a>Try connecting from another SMB client</h2></div></div><div></div></div><p>Try mounting disks. from a DOS, Windows or OS/2 client, eg:</p><pre class="screen">
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866384"></a>Try connecting from another SMB client</h2></div></div><div></div></div><p>Try mounting disks. from a DOS, Windows or OS/2 client, eg:</p><pre class="screen">
 <tt class="prompt">C:\&gt; </tt><b class="userinput"><tt>net use d: \\servername\service</tt></b>
 </pre><p>Try printing. eg:</p><p>
 </p><pre class="screen">
 <tt class="prompt">C:\&gt; </tt><b class="userinput"><tt>net use lpt1:	\\servername\spoolservice</tt></b>
 </pre><p>
 </p><pre class="screen"><tt class="prompt">C:\&gt; </tt><b class="userinput"><tt>print filename</tt></b>
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858961"></a>What If Things Don't Work?</h2></div></div><div></div></div><p>Then you might read the file chapter <a href="#diagnosis" title="Chapter�33.�The Samba checklist">diagnosis</a>
+</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866468"></a>What If Things Don't Work?</h2></div></div><div></div></div><p>Then you might read the file chapter <a href="#diagnosis" title="Chapter�33.�The Samba checklist">diagnosis</a>
 	and the FAQ. If you are still stuck then refer to <a href="#problems" title="Chapter�34.�Analysing and solving samba problems">"Analysing and solving problems"</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><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2858993"></a>Common Errors</h2></div></div><div></div></div><p>
+	so maybe someone else has hit your problem and has overcome it.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866500"></a>Common Errors</h2></div></div><div></div></div><p>
 The following questions and issues get raised on the samba mailing list over and over again.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2859006"></a>Large number of smbd processes</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866513"></a>Large number of smbd processes</h3></div></div><div></div></div><p>
 Samba consists on three core programs:
 <span class="application">nmbd</span>, <span class="application">smbd</span>, <span class="application">winbindd</span>. <span class="application">nmbd</span> is the name server message daemon,
 <span class="application">smbd</span> is the server message daemon, <span class="application">winbindd</span> is the daemon that
@@ -358,19 +358,19 @@ connection made. That is why you are seeing so many of them, one (1) per client
 </p><p>
 <span class="application">winbindd</span> will run as one or two daemons, depending on whether or not it is being
 run in "split mode" (in which case there will be two instances).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2859105"></a>"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</h3></div></div><div></div></div><p>Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with 
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866612"></a>"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</h3></div></div><div></div></div><p>Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with 
 		the ip address 127.0.0.1. Read your OS documentation for details 
-	on how to configure the loopback on your system.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2859124"></a>"<span class="errorname">The network name cannot be found</span>"</h3></div></div><div></div></div><p>
+	on how to configure the loopback on your system.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866630"></a>"<span class="errorname">The network name cannot be found</span>"</h3></div></div><div></div></div><p>
 			This error can be caused by one of these misconfigurations:
-		</p><div class="itemizedlist"><ul type="disc"><li><p>You specified an nonexisting <a class="indexterm" name="id2867341"></a><i class="parameter"><tt>path</tt></i> for the share in <tt class="filename">smb.conf</tt> </p></li><li><p>The user you are trying to access the share with does not 
-					have sufficient permissions to access the <a class="indexterm" name="id2867369"></a><i class="parameter"><tt>path</tt></i> for the share. Both read (r) and access (x) should be possible.</p></li><li><p>The share you are trying to access does not exist.</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter�3.�Fast Start for the Impatient</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867442">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867442"></a>Note</h2></div></div><div></div></div><p>
+		</p><div class="itemizedlist"><ul type="disc"><li><p>You specified an nonexisting <a class="indexterm" name="id2866655"></a><i class="parameter"><tt>path</tt></i> for the share in <tt class="filename">smb.conf</tt> </p></li><li><p>The user you are trying to access the share with does not 
+					have sufficient permissions to access the <a class="indexterm" name="id2866684"></a><i class="parameter"><tt>path</tt></i> for the share. Both read (r) and access (x) should be possible.</p></li><li><p>The share you are trying to access does not exist.</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter�3.�Fast Start for the Impatient</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866757">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866757"></a>Note</h2></div></div><div></div></div><p>
 This chapter did not make it into this release.
 It is planned for the published release of this document.
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2867469"></a>First Steps in Server Configuration</h1></div></div><div></div></div><p>
+</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2866784"></a>First Steps in Server Configuration</h1></div></div><div></div></div><p>
 Samba can operate in various modes within SMB networks. This HOWTO section contains information on
 configuring samba to function as the type of server your network requires. Please read this
 section carefully.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2867622">Features and Benefits</a></dt><dt><a href="#id2867717">Server Types</a></dt><dt><a href="#id2867803">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867922">User Level Security</a></dt><dt><a href="#id2868060">Share Level Security</a></dt><dt><a href="#id2852162">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2852420">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2852521">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2869450">Password checking</a></dt><dt><a href="#id2869643">Common Errors</a></dt><dd><dl><dt><a href="#id2869671">What makes Samba a SERVER?</a></dt><dt><a href="#id2869710">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2869747">What makes Samba a Domain Member?</a></dt><dt><a href="#id2869786">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2870118">Features and Benefits</a></dt><dt><a href="#id2870332">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2870347">Domain Controller Types</a></dt><dt><a href="#id2870592">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2868460">Domain Control - Example Configuration</a></dt><dt><a href="#id2868947">Samba ADS Domain Control</a></dt><dt><a href="#id2868985">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2869000">Domain Network Logon Service</a></dt><dt><a href="#id2873169">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2873315">Common Errors</a></dt><dd><dl><dt><a href="#id2873322">'$' cannot be included in machine name</a></dt><dt><a href="#id2873381">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2873436">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2873520">The machine trust account not accessible</a></dt><dt><a href="#id2873592">Account disabled</a></dt><dt><a href="#id2873625">Domain Controller Unavailable</a></dt><dt><a href="#id2873647">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2873807">Features And Benefits</a></dt><dt><a href="#id2873997">Essential Background Information</a></dt><dd><dl><dt><a href="#id2874026">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2874268">Active Directory Domain Control</a></dt><dt><a href="#id2874289">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2874316">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2874329">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2874464">Example Configuration</a></dt></dl></dd><dt><a href="#id2874620">Common Errors</a></dt><dd><dl><dt><a href="#id2874633">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2874664">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2874691">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2874735">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2874943">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875556">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2875771">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875842">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2876053">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2876489">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2876674">Setup your smb.conf</a></dt><dt><a href="#id2876803">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2877177">Notes</a></dt></dl></dd><dt><a href="#id2877199">Common Errors</a></dt><dd><dl><dt><a href="#id2877226">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2877258">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2877459">Features and Benefits</a></dt><dt><a href="#id2877498">Background</a></dt><dt><a href="#id2877581">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2878101">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2878165">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter�4.�Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867622">Features and Benefits</a></dt><dt><a href="#id2867717">Server Types</a></dt><dt><a href="#id2867803">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867922">User Level Security</a></dt><dt><a href="#id2868060">Share Level Security</a></dt><dt><a href="#id2852162">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2852420">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2852521">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2869450">Password checking</a></dt><dt><a href="#id2869643">Common Errors</a></dt><dd><dl><dt><a href="#id2869671">What makes Samba a SERVER?</a></dt><dt><a href="#id2869710">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2869747">What makes Samba a Domain Member?</a></dt><dt><a href="#id2869786">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></div><p>
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2866937">Features and Benefits</a></dt><dt><a href="#id2867038">Server Types</a></dt><dt><a href="#id2867124">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867244">User Level Security</a></dt><dt><a href="#id2867382">Share Level Security</a></dt><dt><a href="#id2867518">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2867776">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2867877">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868158">Password checking</a></dt><dt><a href="#id2868359">Common Errors</a></dt><dd><dl><dt><a href="#id2868387">What makes Samba a SERVER?</a></dt><dt><a href="#id2868427">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868463">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868503">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2868835">Features and Benefits</a></dt><dt><a href="#id2869049">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869064">Domain Controller Types</a></dt><dt><a href="#id2869309">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2869698">Domain Control - Example Configuration</a></dt><dt><a href="#id2870186">Samba ADS Domain Control</a></dt><dt><a href="#id2870238">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870253">Domain Network Logon Service</a></dt><dt><a href="#id2870678">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2870825">Common Errors</a></dt><dd><dl><dt><a href="#id2870831">'$' cannot be included in machine name</a></dt><dt><a href="#id2870890">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2870945">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871029">The machine trust account not accessible</a></dt><dt><a href="#id2871102">Account disabled</a></dt><dt><a href="#id2871135">Domain Controller Unavailable</a></dt><dt><a href="#id2871156">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2871317">Features And Benefits</a></dt><dt><a href="#id2871494">Essential Background Information</a></dt><dd><dl><dt><a href="#id2871522">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2871772">Active Directory Domain Control</a></dt><dt><a href="#id2871793">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2871819">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2871833">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2871968">Example Configuration</a></dt></dl></dd><dt><a href="#id2872125">Common Errors</a></dt><dd><dl><dt><a href="#id2872138">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872169">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872196">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872240">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2872448">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873061">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873276">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873347">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2873558">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2873995">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874178">Setup your smb.conf</a></dt><dt><a href="#id2874307">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2874683">Notes</a></dt></dl></dd><dt><a href="#id2874706">Common Errors</a></dt><dd><dl><dt><a href="#id2874732">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2874764">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2874966">Features and Benefits</a></dt><dt><a href="#id2875004">Background</a></dt><dt><a href="#id2875078">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2875598">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2875663">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter�4.�Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866937">Features and Benefits</a></dt><dt><a href="#id2867038">Server Types</a></dt><dt><a href="#id2867124">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867244">User Level Security</a></dt><dt><a href="#id2867382">Share Level Security</a></dt><dt><a href="#id2867518">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2867776">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2867877">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868158">Password checking</a></dt><dt><a href="#id2868359">Common Errors</a></dt><dd><dl><dt><a href="#id2868387">What makes Samba a SERVER?</a></dt><dt><a href="#id2868427">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868463">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868503">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></div><p>
 This chapter provides information regarding the types of server that Samba may be
 configured to be. A Microsoft network administrator who wishes to migrate to or to
 use Samba will want to know what, within a Samba context, terms familiar to MS Windows
@@ -384,7 +384,7 @@ A question often asked is, "Why would I want to use Samba?" Most chapters contai
 that highlights features and benefits. We hope that the information provided will help to
 answer this question. Be warned though, we want to be fair and reasonable, so not all
 features are positive towards Samba so the benefit may be on the side of our competition.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867622"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866937"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It
 hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion
 and fury fitting his anguish. The other looked at the stone and said, that is a garnet - I
@@ -420,14 +420,14 @@ So now, what are the benefits of features mentioned in this chapter?
 	greater flexibility than MS Windows NT4 and in many cases a
 	significantly higher utility than Active Directory domains
 	with MS Windows 200x.
-	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867717"></a>Server Types</h2></div></div><div></div></div><p>Administrators of Microsoft networks often refer to three
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867038"></a>Server Types</h2></div></div><div></div></div><p>Administrators of Microsoft networks often refer to three
 different type of servers:</p><div class="itemizedlist"><ul type="disc"><li><p>Domain Controller</p><div class="itemizedlist"><ul type="circle"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div></li><li><p>Domain Member Server</p><div class="itemizedlist"><ul type="circle"><li><p>Active Directory Domain Server</p></li><li><p>NT4 Style Domain Domain Server</p></li></ul></div></li><li><p>Stand Alone Server</p></li></ul></div><p>
 The chapters covering Domain Control, Backup Domain Control and Domain Membership provide
 pertinent information regarding Samba configuration for each of these server roles.
 The reader is strongly encouraged to become intimately familiar with the information 
 presented.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867803"></a>Samba Security Modes</h2></div></div><div></div></div><p>
-In this section the function and purpose of Samba's <a class="indexterm" name="id2867815"></a><i class="parameter"><tt>security</tt></i>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867124"></a>Samba Security Modes</h2></div></div><div></div></div><p>
+In this section the function and purpose of Samba's <a class="indexterm" name="id2867135"></a><i class="parameter"><tt>security</tt></i>
 modes are described. An accurate understanding of how Samba implements each security
 mode as well as how to configure MS Windows clients for each mode will significantly
 reduce user complaints and administrator heartache.
@@ -450,7 +450,7 @@ the way the client then tries to authenticate itself. It does not directly affec
 but it fits in with the client/server approach of SMB. In SMB everything is initiated
 and controlled by the client, and the server can only tell the client what is
 available and whether an action is allowed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867922"></a>User Level Security</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867244"></a>User Level Security</h3></div></div><div></div></div><p>
 We will describe <span class="emphasis"><em>user level</em></span> security first, as it's simpler.
 In <span class="emphasis"><em>user level</em></span> security, the client will send a
 <span class="emphasis"><em>session setup</em></span> command directly after the protocol negotiation.
@@ -468,11 +468,11 @@ It is also possible for a client to send multiple <span class="emphasis"><em>ses
 requests. When the server responds, it gives the client a <span class="emphasis"><em>uid</em></span> to use
 as an authentication tag for that username/password. The client can maintain multiple
 authentication contexts in this way (WinDD is an example of an application that does this).
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868014"></a>Example Configuration</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867336"></a>Example Configuration</h4></div></div><div></div></div><p>
 The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>User Level Security</em></span> is:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr></table><p>
 This is the default setting since samba-2.2.x.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868060"></a>Share Level Security</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867382"></a>Share Level Security</h3></div></div><div></div></div><p>
 Ok, now for share level security. In share level security, the client authenticates
 itself separately for each share. It will send a password along with each 
 <span class="emphasis"><em>tree connection</em></span> (share mount). It does not explicitly send a
@@ -492,19 +492,19 @@ level security. They normally send a valid username but no password. Samba recor
 this username in a list of <span class="emphasis"><em>possible usernames</em></span>. When the client
 then does a <span class="emphasis"><em>tree connection</em></span> it also adds to this list the name
 of the share they try to connect to (useful for home directories) and any users
-listed in the <a class="indexterm" name="id2852085"></a><i class="parameter"><tt>user</tt></i> <tt class="filename">smb.conf</tt> line. The password is then checked
+listed in the <a class="indexterm" name="id2867441"></a><i class="parameter"><tt>user</tt></i> <tt class="filename">smb.conf</tt> line. The password is then checked
 in turn against these <span class="emphasis"><em>possible usernames</em></span>. If a match is found
 then the client is authenticated as that user.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2852114"></a>Example Configuration</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867470"></a>Example Configuration</h4></div></div><div></div></div><p>
 The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>Share Level Security</em></span> is:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = share</tt></i></td></tr></table><p>
 Please note that there are reports that recent MS Windows clients do not like to work
 with share mode security servers. You are strongly discouraged from using share level security.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2852162"></a>Domain Security Mode (User Level Security)</h3></div></div><div></div></div><p>
-When Samba is operating in <a class="indexterm" name="id2852174"></a><i class="parameter"><tt>security</tt></i> = domain mode,
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867518"></a>Domain Security Mode (User Level Security)</h3></div></div><div></div></div><p>
+When Samba is operating in <a class="indexterm" name="id2867530"></a><i class="parameter"><tt>security</tt></i> = domain mode,
 the Samba server has a domain security trust account (a machine account) and will cause
 all authentication requests to be passed through to the domain controllers.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2852193"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867549"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em>
 Samba as a Domain Member Server
 </em></span></p><p>
 This method involves addition of the following parameters in the <tt class="filename">smb.conf</tt> file:
@@ -537,7 +537,7 @@ An alternative to assigning UIDs to Windows users on a Samba member server is
 presented in <a href="#winbind" title="Chapter�21.�Winbind: Use of Domain Accounts">the chapter about winbind</a>.
 </p><p>
 	For more information of being a domain member, see <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter about domain membership</a>.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2852420"></a>ADS Security Mode (User Level Security)</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867776"></a>ADS Security Mode (User Level Security)</h3></div></div><div></div></div><p>
 Both Samba 2.2 and 3.0 can join an Active Directory domain. This is
 possible if the domain is run in native mode. Active Directory in
 native mode perfectly allows NT4-style domain members. This is contrary to
@@ -551,12 +551,12 @@ authentication protocols. All your machines are running Windows 2000
 and above and all use Kerberos. In this case Samba as a NT4-style
 domain would still require NT-compatible authentication data. Samba in
 AD-member mode can accept Kerberos tickets.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2852450"></a>Example Configuration</h4></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>realm = your.kerberos.REALM</tt></i></td></tr><tr><td><i class="parameter"><tt>security = ADS</tt></i></td></tr></table><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867806"></a>Example Configuration</h4></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>realm = your.kerberos.REALM</tt></i></td></tr><tr><td><i class="parameter"><tt>security = ADS</tt></i></td></tr></table><p>
 The following parameter may be required:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>ads server = your.kerberos.server</tt></i></td></tr></table><p>
 Please refer to <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter on domain membership</a>
 for more information regarding this configuration option.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2852521"></a>Server Security (User Level Security)</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867877"></a>Server Security (User Level Security)</h3></div></div><div></div></div><p>
 Server security mode is a left over from the time when Samba was not capable of acting
 as a domain member server. It is highly recommended NOT to use this feature. Server
 security mode has many draw backs. The draw backs include:
@@ -564,20 +564,20 @@ security mode has many draw backs. The draw backs include:
 In server security mode the Samba server reports to the client that it is in user level
 security. The client then does a <span class="emphasis"><em>session setup</em></span> as described earlier.
 The Samba server takes the username/password that the client sends and attempts to login to the
-<a class="indexterm" name="id2852593"></a><i class="parameter"><tt>password server</tt></i> by sending exactly the same username/password that
+<a class="indexterm" name="id2867950"></a><i class="parameter"><tt>password server</tt></i> by sending exactly the same username/password that
 it got from the client. If that server is in user level security and accepts the password,
 then Samba accepts the clients connection. This allows the Samba server to use another SMB
-server as the <a class="indexterm" name="id2852614"></a><i class="parameter"><tt>password server</tt></i>.
+server as the <a class="indexterm" name="id2867970"></a><i class="parameter"><tt>password server</tt></i>.
 </p><p>
 You should also note that at the very start of all this, where the server tells the client
 what security level it is in, it also tells the client if it supports encryption. If it
 does then it supplies the client with a random cryptkey. The client will then send all
 passwords in encrypted form. Samba supports this type of encryption by default.
 </p><p>
-The parameter <a class="indexterm" name="id2852642"></a><i class="parameter"><tt>security</tt></i> = server means that Samba reports to clients that
+The parameter <a class="indexterm" name="id2867997"></a><i class="parameter"><tt>security</tt></i> = server means that Samba reports to clients that
 it is running in <span class="emphasis"><em>user mode</em></span> but actually passes off all authentication
 requests to another <span class="emphasis"><em>user mode</em></span> server. This requires an additional
-parameter <a class="indexterm" name="id2852667"></a><i class="parameter"><tt>password server</tt></i> that points to the real authentication server.
+parameter <a class="indexterm" name="id2868023"></a><i class="parameter"><tt>password server</tt></i> that points to the real authentication server.
 That real authentication server can be another Samba server or can be a Windows NT server,
 the later natively capable of encrypted password support.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
@@ -588,7 +588,7 @@ lookups because the choice of the target authentication server is arbitrary and
 be determined from a domain name. In essence, a Samba server that is in
 <span class="emphasis"><em>server security mode</em></span> is operating in what used to be known as
 workgroup mode.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869360"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868067"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em>
 Using MS Windows NT as an authentication server
 </em></span></p><p>
 This method involves the additions of the following parameters in the <tt class="filename">smb.conf</tt> file:
@@ -605,7 +605,7 @@ certain number of failed authentication attempts this will result in user lockou
 </p><p>
 Use of this mode of authentication does require there to be a standard UNIX account
 for the user, though this account can be blocked to prevent logons by non-SMB/CIFS clients.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869450"></a>Password checking</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868158"></a>Password checking</h2></div></div><div></div></div><p>
 MS Windows clients may use encrypted passwords as part of a challenge/response
 authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear text strings for simple
 password based authentication. It should be realized that with the SMB protocol,
@@ -645,15 +645,15 @@ when using clear text authentication.
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password level = integer</tt></i></td></tr><tr><td><i class="parameter"><tt>username level = integer</tt></i></td></tr></table><p>
 By default Samba will lower case the username before attempting to lookup the user
 in the database of local system accounts.  Because UNIX usernames conventionally
-only contain lower-case character, the <a class="indexterm" name="id2869569"></a><i class="parameter"><tt>username level</tt></i> parameter
+only contain lower-case character, the <a class="indexterm" name="id2868286"></a><i class="parameter"><tt>username level</tt></i> parameter
 is rarely needed.
 </p><p>
 However, passwords on UNIX systems often make use of mixed-case characters.
 This means that in order for a user on a Windows 9x client to connect to a Samba
-server using clear text authentication, the <a class="indexterm" name="id2869592"></a><i class="parameter"><tt>password level</tt></i>
+server using clear text authentication, the <a class="indexterm" name="id2868308"></a><i class="parameter"><tt>password level</tt></i>
 must be set to the maximum number of upper case letters which <span class="emphasis"><em>could</em></span>
 appear in a password.  Note that if the server OS uses the traditional DES version
-of crypt(), a <a class="indexterm" name="id2869613"></a><i class="parameter"><tt>password level</tt></i> of 8 will result in case
+of crypt(), a <a class="indexterm" name="id2868330"></a><i class="parameter"><tt>password level</tt></i> of 8 will result in case
 insensitive passwords as seen from Windows users.  This will also result in longer
 login times as Samba has to compute the permutations of the password string and
 try them one by one until a match is located (or all combinations fail).
@@ -661,7 +661,7 @@ try them one by one until a match is located (or all combinations fail).
 The best option to adopt is to enable support for encrypted passwords wherever
 Samba is used. Most attempts to apply the registry change to re-enable plain text
 passwords will eventually lead to user complaints and unhappiness.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869643"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868359"></a>Common Errors</h2></div></div><div></div></div><p>
 We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places
 and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake
 made in a developmental test lab is expected.
@@ -671,19 +671,19 @@ on the Samba mailing lists. Many of these are avoidable by doing you homework be
 a Samba implementation. Some are the result of misunderstanding of the English language. The
 English language has many turns of phrase that are potentially vague and may be highly confusing
 to those for whom English is not their native tongue.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869671"></a>What makes Samba a SERVER?</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868387"></a>What makes Samba a SERVER?</h3></div></div><div></div></div><p>
 To some the nature of the Samba <span class="emphasis"><em>security</em></span> mode is very obvious, but entirely
-wrong all the same. It is assumed that <a class="indexterm" name="id2869687"></a><i class="parameter"><tt>security</tt></i> = server means that Samba
+wrong all the same. It is assumed that <a class="indexterm" name="id2868403"></a><i class="parameter"><tt>security</tt></i> = server means that Samba
 will act as a server. Not so! See above - this setting means that Samba will <span class="emphasis"><em>try</em></span>
 to use another SMB server as its source of user authentication alone.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869710"></a>What makes Samba a Domain Controller?</h3></div></div><div></div></div><p>
-The <tt class="filename">smb.conf</tt> parameter <a class="indexterm" name="id2869728"></a><i class="parameter"><tt>security</tt></i> = domain does NOT really make Samba behave
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868427"></a>What makes Samba a Domain Controller?</h3></div></div><div></div></div><p>
+The <tt class="filename">smb.conf</tt> parameter <a class="indexterm" name="id2868445"></a><i class="parameter"><tt>security</tt></i> = domain does NOT really make Samba behave
 as a Domain Controller! This setting means we want Samba to be a domain member!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869747"></a>What makes Samba a Domain Member?</h3></div></div><div></div></div><p>
-Guess! So many others do. But whatever you do, do NOT think that <a class="indexterm" name="id2869758"></a><i class="parameter"><tt>security</tt></i> = user
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868463"></a>What makes Samba a Domain Member?</h3></div></div><div></div></div><p>
+Guess! So many others do. But whatever you do, do NOT think that <a class="indexterm" name="id2868474"></a><i class="parameter"><tt>security</tt></i> = user
 makes Samba act as a domain member. Read the manufacturers manual before the warranty expires! See 
 <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter about domain membership</a> for more information.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869786"></a>Constantly Losing Connections to Password Server</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868503"></a>Constantly Losing Connections to Password Server</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">
 Why does server_validate() simply give up rather than re-establishing its connection to the
 password server?  Though I am not fluent in the SMB protocol, perhaps the cluster server
@@ -691,9 +691,9 @@ process passes along to its client workstation the session key it receives from
 server, which means the password hashes submitted by the client would not work on a subsequent
 connection, whose session key would be different.  So server_validate() must give up.</span>&#8221;
 </p><p>
-	Indeed. That's why <a class="indexterm" name="id2869814"></a><i class="parameter"><tt>security</tt></i> = server is at best a nasty hack. Please use <a class="indexterm" name="id2869828"></a><i class="parameter"><tt>security</tt></i> = domain.
-<a class="indexterm" name="id2869841"></a><i class="parameter"><tt>security</tt></i> = server mode is also known as pass-through authentication.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter�5.�Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2870118">Features and Benefits</a></dt><dt><a href="#id2870332">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2870347">Domain Controller Types</a></dt><dt><a href="#id2870592">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2868460">Domain Control - Example Configuration</a></dt><dt><a href="#id2868947">Samba ADS Domain Control</a></dt><dt><a href="#id2868985">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2869000">Domain Network Logon Service</a></dt><dt><a href="#id2873169">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2873315">Common Errors</a></dt><dd><dl><dt><a href="#id2873322">'$' cannot be included in machine name</a></dt><dt><a href="#id2873381">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2873436">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2873520">The machine trust account not accessible</a></dt><dt><a href="#id2873592">Account disabled</a></dt><dt><a href="#id2873625">Domain Controller Unavailable</a></dt><dt><a href="#id2873647">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></div><p><b><span class="emphasis"><em>The Essence of Learning:</em></span>�</b>
+	Indeed. That's why <a class="indexterm" name="id2868531"></a><i class="parameter"><tt>security</tt></i> = server is at best a nasty hack. Please use <a class="indexterm" name="id2868545"></a><i class="parameter"><tt>security</tt></i> = domain.
+<a class="indexterm" name="id2868558"></a><i class="parameter"><tt>security</tt></i> = server mode is also known as pass-through authentication.
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter�5.�Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2868835">Features and Benefits</a></dt><dt><a href="#id2869049">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869064">Domain Controller Types</a></dt><dt><a href="#id2869309">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2869698">Domain Control - Example Configuration</a></dt><dt><a href="#id2870186">Samba ADS Domain Control</a></dt><dt><a href="#id2870238">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870253">Domain Network Logon Service</a></dt><dt><a href="#id2870678">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2870825">Common Errors</a></dt><dd><dl><dt><a href="#id2870831">'$' cannot be included in machine name</a></dt><dt><a href="#id2870890">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2870945">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871029">The machine trust account not accessible</a></dt><dt><a href="#id2871102">Account disabled</a></dt><dt><a href="#id2871135">Domain Controller Unavailable</a></dt><dt><a href="#id2871156">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></div><p><b><span class="emphasis"><em>The Essence of Learning:</em></span>�</b>
 There are many who approach MS Windows networking with incredible misconceptions.
 That's OK, because it gives the rest of us plenty of opportunity to be of assistance.
 Those who really want help would be well advised to become familiar with information
@@ -723,7 +723,7 @@ burden on an organisation.
 Where is the right place to make mistakes? Only out of harm's way! If you are going to
 make mistakes, then please do this on a test network, away from users and in such a way as
 to not inflict pain on others. Do your learning on a test network.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870118"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868835"></a>Features and Benefits</h2></div></div><div></div></div><p>
 <span class="emphasis"><em>What is the key benefit of Microsoft Domain security?</em></span>
 </p><p>
 In a word, <span class="emphasis"><em>Single Sign On</em></span>, or SSO for short. To many, this is the holy
@@ -795,11 +795,11 @@ user and machine trust account information in a suitable backend data store.
 Refer <a href="#machine-trust-accounts" title="MS Windows Workstation/Server Machine Trust Accounts">to the section on machine trust accounts</a>. With Samba-3 there can be multiple
 back-ends for this. A complete discussion of account database backends can be found in
 <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on Account Information Databases</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870332"></a>Basics of Domain Control</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869049"></a>Basics of Domain Control</h2></div></div><div></div></div><p>
 Over the years, public perceptions of what Domain Control really is has taken on an
 almost mystical nature. Before we branch into a brief overview of Domain Control,
 there are three basic types of domain controllers:
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870347"></a>Domain Controller Types</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869064"></a>Domain Controller Types</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p>
 The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in the MS 
 Windows NT4. In Windows 200x Domain Control architecture this role is held by domain controllers.
 There is folk lore that dictates that because of it's role in the MS Windows
@@ -821,7 +821,7 @@ LDAP based user and machine account back end.
 </p><p>
 New to Samba-3 is the ability to use a back-end database that holds the same type of data as
 the NT4 style SAM (Security Account Manager) database (one of the registry files).
-<sup>[<a name="id2870424" href="#ftn.id2870424">1</a>]</sup>
+<sup>[<a name="id2869141" href="#ftn.id2869141">1</a>]</sup>
 </p><p>
 The <span class="emphasis"><em>Backup Domain Controller</em></span> or BDC plays a key role in servicing network
 authentication requests. The BDC is biased to answer logon requests in preference to the PDC.
@@ -852,7 +852,7 @@ management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP
 environment. However, there are certain compromises:
 
 </p><div class="itemizedlist"><ul type="disc"><li><p>No machine policy files</p></li><li><p>No Group Policy Objects</p></li><li><p>No synchronously executed AD logon scripts</p></li><li><p>Can't use ANY Active Directory management tools to manage users and machines</p></li><li><p>Registry changes tattoo the main registry, while with AD they do NOT. ie: Leave permanent changes in effect</p></li><li><p>Without AD you can not peprform the function of exporting specific applications to specific users or groups</p></li></ul></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870592"></a>Preparing for Domain Control</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869309"></a>Preparing for Domain Control</h3></div></div><div></div></div><p>
 There are two ways that MS Windows machines may interact with each other, with other servers,
 and with Domain Controllers: Either as <span class="emphasis"><em>Stand-Alone</em></span> systems, more commonly
 called <span class="emphasis"><em>Workgroup</em></span> members, or as full participants in a security system,
@@ -879,10 +879,10 @@ Domain, then it will operate like a workgroup (stand-alone) machine. Please refe
 </p></div><p>
 The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows
 NT4 / 200x / XP clients.
-</p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2868185"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Consistent configuration of Name Resolution (See chapter on <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Network Browsing</a> and on
+</p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2869424"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Consistent configuration of Name Resolution (See chapter on <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Network Browsing</a> and on
 	<a href="#integrate-ms-networks" title="Chapter�26.�Integrating MS Windows networks with Samba">Integrating Unix into Windows networks</a>)</p></li><li><p>Domain logons for Windows NT4 / 200x / XP Professional clients</p></li><li><p>Configuration of Roaming Profiles or explicit configuration to force local profile usage</p></li><li><p>Configuration of Network/System Policies</p></li><li><p>Adding and managing domain user accounts</p></li><li><p>Configuring MS Windows client machines to become domain members</p></li></ul></div><p>
 The following provisions are required to serve MS Windows 9x / Me Clients:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2868279"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Network Logon Configuration (Since Windows 9x / XP Home are not technically domain
+</p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2869517"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Network Logon Configuration (Since Windows 9x / XP Home are not technically domain
 	members, they do not really participate in  the security aspects of Domain logons as such)</p></li><li><p>Roaming Profile Configuration</p></li><li><p>Configuration of System Policy handling</p></li><li><p>Installation of the Network driver "Client for MS Windows Networks" and configuration
 	to log onto the domain</p></li><li><p>Placing Windows 9x / Me clients in user level security - if it is desired to allow
 	all client share access to be controlled according to domain user / group identities.</p></li><li><p>Adding and managing domain user accounts</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
@@ -904,15 +904,15 @@ A Domain Controller is an SMB/CIFS server that:
 	Provides a share called NETLOGON
 	</p></li></ul></div><p>
 For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide
-the NETLOGON service which Samba calls the <a class="indexterm" name="id2868409"></a><i class="parameter"><tt>domain logons</tt></i> functionality
+the NETLOGON service which Samba calls the <a class="indexterm" name="id2869647"></a><i class="parameter"><tt>domain logons</tt></i> functionality
 (after the name of the parameter in the <tt class="filename">smb.conf</tt> file). Additionally, one (1) server in a Samba-3
-Domain must advertise itself as the domain master browser<sup>[<a name="id2868434" href="#ftn.id2868434">2</a>]</sup>. This causes the Primary Domain Controller
+Domain must advertise itself as the domain master browser<sup>[<a name="id2869672" href="#ftn.id2869672">2</a>]</sup>. This causes the Primary Domain Controller
 to claim domain specific NetBIOS name that identifies it as a domain master browser for its given
 domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets
 then ask for a complete copy of the browse list for the whole wide area network. Browser clients
 will then contact their local master browser, and will receive the domain-wide browse list,
 instead of just the list for their broadcast-isolated subnet.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868460"></a>Domain Control - Example Configuration</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869698"></a>Domain Control - Example Configuration</h2></div></div><div></div></div><p>
 The first step in creating a working Samba PDC is to understand the parameters necessary
 in <tt class="filename">smb.conf</tt>.  An example <tt class="filename">smb.conf</tt> for acting as a PDC can be found in the example
 <a href="#pdc-example" title="Example�5.1.�smb.conf for being a PDC">for being a PDC</a>. 
@@ -960,7 +960,7 @@ of operation. The following <tt class="filename">smb.conf</tt> parameters are th
 </p><p>
 The additional parameters shown in the longer listing above just makes for
 more complete explanation.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868947"></a>Samba ADS Domain Control</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870186"></a>Samba ADS Domain Control</h2></div></div><div></div></div><p>
 Samba-3 is not, and can not act as, an Active Directory Server. It can not truly function as
 an Active Directory Primary Domain Controller. The protocols for some of the functionality
 the Active Directory Domain Controllers has been partially implemented on an experimental
@@ -975,15 +975,15 @@ domain controllers have. Samba-3 does NOT have all the capabilities of Windows N
 a number of features that Windows NT4 domain contollers do not have. In short, Samba-3 is not NT4 and it
 is not Windows Server 200x and it is not an Active Directory server. We hope this is plain and simple
 enough for all to understand.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868985"></a>Domain and Network Logon Configuration</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870238"></a>Domain and Network Logon Configuration</h2></div></div><div></div></div><p>
 The subject of Network or Domain Logons is discussed here because it forms
 an integral part of the essential functionality that is provided by a Domain Controller.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869000"></a>Domain Network Logon Service</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870253"></a>Domain Network Logon Service</h3></div></div><div></div></div><p>
 All Domain Controllers must run the netlogon service (<span class="emphasis"><em>domain logons</em></span>
-in Samba). One Domain Controller must be configured with <a class="indexterm" name="id2869017"></a><i class="parameter"><tt>domain master</tt></i> = Yes
-(the Primary Domain Controller); on ALL Backup Domain Controllers <a class="indexterm" name="id2869034"></a><i class="parameter"><tt>domain master</tt></i> = No
+in Samba). One Domain Controller must be configured with <a class="indexterm" name="id2870270"></a><i class="parameter"><tt>domain master</tt></i> = Yes
+(the Primary Domain Controller); on ALL Backup Domain Controllers <a class="indexterm" name="id2870287"></a><i class="parameter"><tt>domain master</tt></i> = No
 must be set.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869049"></a>Example Configuration</h4></div></div><div></div></div><div class="example"><a name="id2869056"></a><p class="title"><b>Example�5.2.�smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = (Yes on PDC, No on BDCs)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[netlogon]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Network Logon Service</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/netlogon</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869140"></a>The Special Case of MS Windows XP Home Edition</h4></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870302"></a>Example Configuration</h4></div></div><div></div></div><div class="example"><a name="id2870309"></a><p class="title"><b>Example�5.2.�smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = (Yes on PDC, No on BDCs)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[netlogon]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Network Logon Service</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/netlogon</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870393"></a>The Special Case of MS Windows XP Home Edition</h4></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 MS Windows XP Home Edition does not have the ability to join any type of Domain
 security facility. Unlike, MS Windows 9x / Me, MS Windows XP Home Edition also completely
 lacks the ability to log onto a network.
@@ -997,7 +997,7 @@ Now that this has been said, please do NOT ask the mailing list, or email any of
 Samba-Team members with your questions asking how to make this work. It can't be done.
 If it can be done, then to do so would violate your software license agreement with
 Microsoft, and we recommend that you do not do that.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869178"></a>The Special Case of Windows 9x / Me</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870431"></a>The Special Case of Windows 9x / Me</h4></div></div><div></div></div><p>
 A domain and a workgroup are exactly the same in terms of network
 browsing.  The difference is that a distributable authentication
 database is associated with a domain, for secure login access to a
@@ -1080,7 +1080,7 @@ network logon services that MS Windows 9x / Me expect to find.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Use of plain-text passwords is strongly discouraged. Where used they are easily detected
 using a sniffer tool to examine network traffic.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873169"></a>Security Mode and Master Browsers</h3></div></div><div></div></div><p>
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870678"></a>Security Mode and Master Browsers</h3></div></div><div></div></div><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
@@ -1101,21 +1101,21 @@ A DMB is a Domain Master Browser - see <a href="#DMB" title="Setting up WORKGROU
 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 <a class="indexterm" name="id2873238"></a><i class="parameter"><tt>security</tt></i> = user.  If a Samba host is configured to use 
+than <a class="indexterm" name="id2870747"></a><i class="parameter"><tt>security</tt></i> = 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 <a class="indexterm" name="id2873255"></a><i class="parameter"><tt>password server</tt></i>) knows more about the user than the Samba host.
+(the <a class="indexterm" name="id2870765"></a><i class="parameter"><tt>password server</tt></i>) knows more about the user than the Samba host.
 99% of the time, this other host is a domain controller.  Now 
-in order to operate in domain mode security, the <a class="indexterm" name="id2873272"></a><i class="parameter"><tt>workgroup</tt></i> parameter
+in order to operate in domain mode security, the <a class="indexterm" name="id2870782"></a><i class="parameter"><tt>workgroup</tt></i> parameter
 must be set to the name of the Windows NT domain (which already 
 has a domain controller). If the domain does NOT already have a Domain Controller
 then you do not yet have a Domain!
 </p><p>
 Configuring a Samba box as a DC for a domain that already by definition has a
 PDC is asking for trouble. Therefore, you should always configure the Samba DC
-to be the DMB for its domain and set <a class="indexterm" name="id2873297"></a><i class="parameter"><tt>security</tt></i> = user.
+to be the DMB for its domain and set <a class="indexterm" name="id2870806"></a><i class="parameter"><tt>security</tt></i> = user.
 This is the only officially supported mode of operation.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873315"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873322"></a>'$' cannot be included in machine name</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870825"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870831"></a>'$' cannot be included in machine name</h3></div></div><div></div></div><p>
 A 'machine account', (typically) stored in <tt class="filename">/etc/passwd</tt>,
 takes the form of the machine name with a '$' appended. FreeBSD (and other BSD 
 systems?) won't create a user with a '$' in their name.
@@ -1125,7 +1125,7 @@ Create a user without the '$'. Then use <b class="command">vipw</b> to edit the
 the '$'. Or create the whole entry with vipw if you like; make sure you use a unique User ID!
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 The UNIX tool <b class="command">vipw</b> is a common tool for directly editting the <tt class="filename">/etc/passwd</tt> file.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873381"></a>Joining domain fails because of existing machine account</h3></div></div><div></div></div><p>&#8220;<span class="quote">I get told "You already have a connection to the Domain...." 
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870890"></a>Joining domain fails because of existing machine account</h3></div></div><div></div></div><p>&#8220;<span class="quote">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.</span>&#8221;</p><p>
 This happens if you try to create a machine trust account from the 
@@ -1139,7 +1139,7 @@ Further, if the machine is already a 'member of a workgroup' that
 is the same name as the domain you are joining (bad idea) you will 
 get this message.  Change the workgroup name to something else, it 
 does not matter what, reboot, and try again.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873436"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>&#8220;<span class="quote">I joined the domain successfully but after upgrading 
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870945"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>&#8220;<span class="quote">I joined the domain successfully but after upgrading 
 to a newer version of the Samba code I get the message, <span class="errorname">The system 
 can not log you on (C000019B), Please try again or consult your 
 system administrator</span> when attempting to logon.</span>&#8221;
@@ -1162,13 +1162,13 @@ Workstation machine trust accounts work only with the Domain (or network) SID. I
 then domain members (workstations) will not be able to log onto the domain. The original Domain SID
 can be recovered from the secrets.tdb file. The alternative is to visit each workstation to re-join
 it to the domain.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873520"></a>The machine trust account not accessible</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871029"></a>The machine trust account not accessible</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">When I try to join the domain I get the message <span class="errorname">The machine account 
 for this computer either does not exist or is not accessible</span>. What's 
 wrong?</span>&#8221;
 </p><p>
 This problem is caused by the PDC not having a suitable machine trust account. 
-If you are using the <a class="indexterm" name="id2873546"></a><i class="parameter"><tt>add machine script</tt></i> method to create 
+If you are using the <a class="indexterm" name="id2871056"></a><i class="parameter"><tt>add machine script</tt></i> method to create 
 accounts then this would indicate that it has not worked. Ensure the domain 
 admin user system is working.
 </p><p>
@@ -1184,13 +1184,13 @@ Some people have also reported
 that inconsistent subnet masks between the Samba server and the NT 
 client can cause this problem.   Make sure that these are consistent 
 for both client and server.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873592"></a>Account disabled</h3></div></div><div></div></div><p>&#8220;<span class="quote">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871102"></a>Account disabled</h3></div></div><div></div></div><p>&#8220;<span class="quote">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
 			I get a message about my account being disabled.</span>&#8221;</p><p>
 Enable the user accounts with <b class="userinput"><tt>smbpasswd -e <i class="replaceable"><tt>username</tt></i>
 </tt></b>, this is normally done as an account is created.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873625"></a>Domain Controller Unavailable</h3></div></div><div></div></div><p>&#8220;<span class="quote">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</span>&#8221;</p><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871135"></a>Domain Controller Unavailable</h3></div></div><div></div></div><p>&#8220;<span class="quote">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</span>&#8221;</p><p>
 		A domain controller has to announce on the network who it is. This usually takes a while.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873647"></a>Can not log onto domain member workstation after joining domain</h3></div></div><div></div></div><p>After successfully joining the domain user logons fail with one of two messages:</p><p>One to the effect that the domain controller can not be found, the other claiming that the
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871156"></a>Can not log onto domain member workstation after joining domain</h3></div></div><div></div></div><p>After successfully joining the domain user logons fail with one of two messages:</p><p>One to the effect that the domain controller can not be found, the other claiming that the
 	account does not exist in the domain or that the password is incorrect.</p><p>This may be due to incompatible settings between
 	the Windows client and the Samba-3 server for <span class="emphasis"><em>schannel</em></span> (secure channel) settings
 	or <span class="emphasis"><em>smb signing</em></span> settings. Check your samba settings for <span class="emphasis"><em>
@@ -1202,10 +1202,10 @@ Enable the user accounts with <b class="userinput"><tt>smbpasswd -e <i class="re
 	<span class="emphasis"><em>Secure Channel: ..., and Digitally sign ...</em></span>.
 	</p><p>
 	It is important that these be set consistently with the Samba-3 server settings.
-	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2870424" href="#id2870424">1</a>] </sup>See also <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on Account Information Databases</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2868434" href="#id2868434">2</a>] </sup>See also <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">the chapter about network browsing</a></p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter�6.�Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2873807">Features And Benefits</a></dt><dt><a href="#id2873997">Essential Background Information</a></dt><dd><dl><dt><a href="#id2874026">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2874268">Active Directory Domain Control</a></dt><dt><a href="#id2874289">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2874316">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2874329">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2874464">Example Configuration</a></dt></dl></dd><dt><a href="#id2874620">Common Errors</a></dt><dd><dl><dt><a href="#id2874633">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2874664">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2874691">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2874735">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><p>
+	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2869141" href="#id2869141">1</a>] </sup>See also <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on Account Information Databases</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2869672" href="#id2869672">2</a>] </sup>See also <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">the chapter about network browsing</a></p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter�6.�Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2871317">Features And Benefits</a></dt><dt><a href="#id2871494">Essential Background Information</a></dt><dd><dl><dt><a href="#id2871522">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2871772">Active Directory Domain Control</a></dt><dt><a href="#id2871793">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2871819">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2871833">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2871968">Example Configuration</a></dt></dl></dd><dt><a href="#id2872125">Common Errors</a></dt><dd><dl><dt><a href="#id2872138">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872169">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872196">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872240">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><p>
 Before you continue reading in this section, please make sure that you are comfortable
 with configuring a Samba Domain Controller as described in <a href="#samba-pdc" title="Chapter�5.�Domain Control">chapter on setting up Samba as a PDC</a>.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873807"></a>Features And Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871317"></a>Features And Benefits</h2></div></div><div></div></div><p>
 This is one of the most difficult chapters to summarise. It does not matter what we say here
 for someone will still draw conclusions and / or approach the Samba-Team with expectations
 that are either not yet capable of being delivered, or that can be achieved far more
@@ -1267,7 +1267,7 @@ lets consider each possible option and look at the pro's and con's for each theo
 	Arguments Against: All machine trust accounts and user accounts will be locally
 	maintained. Domain users will NOT be able to roam from office to office. This is
 	a broken and flawed solution. Do NOT do this.
-	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873997"></a>Essential Background Information</h2></div></div><div></div></div><p>
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871494"></a>Essential Background Information</h2></div></div><div></div></div><p>
 A Domain Controller is a machine that is able to answer logon requests from network
 workstations. Microsoft LanManager and IBM LanServer were two early products that
 provided this capability. The technology has become known as the LanMan Netlogon service.
@@ -1277,7 +1277,7 @@ and with it a new form of the network logon service that has extended functional
 This service became known as the NT NetLogon Service. The nature of this service has
 changed with the evolution of MS Windows NT and today provides a very complex array of
 services that are implemented over a complex spectrum of technologies.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874026"></a>MS Windows NT4 Style Domain Control</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871522"></a>MS Windows NT4 Style Domain Control</h3></div></div><div></div></div><p>
 Whenever a user logs into a Windows NT4 / 200x / XP Professional Workstation,
 the workstation connects to a Domain Controller (authentication server) to validate
 the username and password that the user entered are valid. If the information entered
@@ -1335,29 +1335,29 @@ one of the BDCs can be promoted to a PDC. If this happens while the original PDC
 line then it is automatically demoted to a BDC. This is an important aspect of Domain
 Controller management. The tool that is used to affect a promotion or a demotion is the
 Server Manager for Domains.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874169"></a>Example PDC Configuration</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871673"></a>Example PDC Configuration</h4></div></div><div></div></div><p>
 Since version 2.2 Samba officially supports domain logons for all current Windows Clients,
 including Windows NT4, 2003 and XP Professional. For samba to be enabled as a PDC some
 parameters in the <i class="parameter"><tt>[global]</tt></i>-section of the <tt class="filename">smb.conf</tt> have to be set:
-</p><div class="example"><a name="id2874200"></a><p class="title"><b>Example�6.1.�Minimal smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2871704"></a><p class="title"><b>Example�6.1.�Minimal smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr></table></div><p>
 Several other things like a <i class="parameter"><tt>[homes]</tt></i> and a
 <i class="parameter"><tt>[netlogon]</tt></i> share also need to be set along with
 settings for the profile path, the users home drive, etc.. This will not be covered in this
 chapter, for more information please refer to <a href="#samba-pdc" title="Chapter�5.�Domain Control">the chapter about samba as a PDC</a>.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874268"></a>Active Directory Domain Control</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871772"></a>Active Directory Domain Control</h3></div></div><div></div></div><p>
 As of the release of MS Windows 2000 and Active Directory, this information is now stored
 in a directory that can be replicated and for which partial or full administrative control
 can be delegated. Samba-3 is NOT able to be a Domain Controller within an Active Directory
 tree, and it can not be an Active Directory server. This means that Samba-3 also can NOT
 act as a Backup Domain Controller to an Active Directory Domain Controller.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874289"></a>What qualifies a Domain Controller on the network?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871793"></a>What qualifies a Domain Controller on the network?</h3></div></div><div></div></div><p>
 Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS
 group name SAMBA&lt;#1c&gt; with the WINS server and/or by broadcast on the local network.
 The PDC also registers the unique NetBIOS name SAMBA&lt;#1b&gt; with the WINS server.
 The name type &lt;#1b&gt; name is normally reserved for the Domain Master Browser, a role
 that has nothing to do with anything related to authentication, but the Microsoft Domain
 implementation requires the domain master browser to be on the same machine as the PDC.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874316"></a>How does a Workstation find its domain controller?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871819"></a>How does a Workstation find its domain controller?</h3></div></div><div></div></div><p>
 An MS Windows NT4 / 200x / XP Professional workstation in the domain SAMBA that wants a
 local user to be authenticated has to find the domain controller for SAMBA. It does this
 by doing a NetBIOS name query for the group name SAMBA&lt;#1c&gt;. It assumes that each
@@ -1365,7 +1365,7 @@ of the machines it gets back from the queries is a domain controller and can ans
 requests. To not open security holes both the workstation and the selected domain controller
 authenticate each other. After that the workstation sends the user's credentials (name and
 password) to the local Domain Controller, for validation.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874329"></a>Backup Domain Controller Configuration</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871833"></a>Backup Domain Controller Configuration</h2></div></div><div></div></div><p>
 Several things have to be done:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 	The domain SID has to be the same on the PDC and the BDC. This used to
@@ -1400,14 +1400,14 @@ Several things have to be done:
 	BDC. This can be done manually whenever login scripts are changed,
 	or it can be done automatically together with the smbpasswd
 	synchronization.
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874464"></a>Example Configuration</h3></div></div><div></div></div><p>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871968"></a>Example Configuration</h3></div></div><div></div></div><p>
 Finally, the BDC has to be found by the workstations. This can be done by setting:
-</p><div class="example"><a name="id2874479"></a><p class="title"><b>Example�6.2.�Minimal setup for being a BDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap backend = ldapsam://slave-ldap.quenya.org</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2871983"></a><p class="title"><b>Example�6.2.�Minimal setup for being a BDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap backend = ldapsam://slave-ldap.quenya.org</tt></i></td></tr></table></div><p>
 In the <i class="parameter"><tt>[global]</tt></i>-section of the <tt class="filename">smb.conf</tt> of the BDC. This makes the BDC
 only register the name SAMBA&lt;#1c&gt; with the WINS server. This is no
 problem as the name SAMBA&lt;#1c&gt; is a NetBIOS group name that is meant to
 be registered by more than one machine. The parameter
-<a class="indexterm" name="id2874547"></a><i class="parameter"><tt>domain master</tt></i> = no
+<a class="indexterm" name="id2872052"></a><i class="parameter"><tt>domain master</tt></i> = no
 forces the BDC not to register SAMBA&lt;#1b&gt; which as a unique NetBIOS
 name is reserved for the Primary Domain Controller.
 </p><p>
@@ -1420,10 +1420,10 @@ SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Lin
 will be consistent on the PDC, all BDCs and all Domain Member servers. The parameter that controls this
 is called <i class="parameter"><tt>idmap backend</tt></i>. Please refer to the man page for <tt class="filename">smb.conf</tt> for more information
 regarding it's behaviour. Do NOT set this parameter except where an LDAP backend (ldapsam) is in use.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874620"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872125"></a>Common Errors</h2></div></div><div></div></div><p>
 As this is a rather new area for Samba there are not many examples that we may refer to. Keep
 watching for updates to this section.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874633"></a>Machine Accounts keep expiring, what can I do?</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872138"></a>Machine Accounts keep expiring, what can I do?</h3></div></div><div></div></div><p>
 This problem will occur when occur when the passdb (SAM) files are copied  from a central
 server but the local Backup Domain Controllers.  Local machine trust account password updates
 are not copied back to the central server. The newer machine account password is then over
@@ -1434,7 +1434,7 @@ to proceed and the account expiry error will be reported.
 </p><p>
 The solution: use a more robust passdb backend, such as the ldapsam backend, setting up
 an slave LDAP server for each BDC, and a master LDAP server for the PDC.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874664"></a>Can Samba be a Backup Domain Controller to an NT4 PDC?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872169"></a>Can Samba be a Backup Domain Controller to an NT4 PDC?</h3></div></div><div></div></div><p>
 With version 2.2, no. The native NT4 SAM replication protocols have not yet been fully
 implemented. The Samba Team is working on understanding and implementing the protocols,
 but this work has not been finished for Samba-3.
@@ -1442,7 +1442,7 @@ but this work has not been finished for Samba-3.
 Can I get the benefits of a BDC with Samba?  Yes, but only to a Samba PDC. The main reason for implementing a
 BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to
 service logon requests whenever the PDC is down.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874691"></a>How do I replicate the smbpasswd file?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872196"></a>How do I replicate the smbpasswd file?</h3></div></div><div></div></div><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.
@@ -1456,12 +1456,12 @@ to type a password.
 As said a few times before, use of this method is broken and flawed. Machine trust 
 accounts will go out of sync, resulting in a very broken domain. This method is
 <span class="emphasis"><em>not</em></span> recommended. Try using LDAP instead.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874735"></a>Can I do this all with LDAP?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872240"></a>Can I do this all with LDAP?</h3></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter�7.�Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2874943">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875556">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2875771">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2875842">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2876053">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2876489">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2876674">Setup your smb.conf</a></dt><dt><a href="#id2876803">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2877177">Notes</a></dt></dl></dd><dt><a href="#id2877199">Common Errors</a></dt><dd><dl><dt><a href="#id2877226">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2877258">Adding Machine to Domain Fails</a></dt></dl></dd></dl></div><p>
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter�7.�Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2872448">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873061">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873276">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873347">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2873558">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2873995">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874178">Setup your smb.conf</a></dt><dt><a href="#id2874307">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2874683">Notes</a></dt></dl></dd><dt><a href="#id2874706">Common Errors</a></dt><dd><dl><dt><a href="#id2874732">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2874764">Adding Machine to Domain Fails</a></dt></dl></dd></dl></div><p>
 Domain Membership is a subject of vital concern, Samba must be able to
 participate as a member server in a Microsoft Domain security context, and
 Samba must be capable of providing Domain machine member trust accounts,
@@ -1474,7 +1474,7 @@ within the current MS Windows networking world and particularly in the
 UNIX/Linux networking and administration world, a considerable level of
 mis-information, incorrect understanding, and a lack of knowledge. Hopefully
 this chapter will fill the voids.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874943"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872448"></a>Features and Benefits</h2></div></div><div></div></div><p>
 MS Windows workstations and servers that want to participate in domain security need to
 be made Domain members. Participating in Domain security is often called 
 <span class="emphasis"><em>Single Sign On</em></span> or <span class="acronym">SSO</span> for short. This
@@ -1510,7 +1510,7 @@ Domain membership has many advantages:
 	client or server, other than the central Domain database 
 	(either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an
 	LDAP directory, or via an Active Directory infrastructure)
-	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="machine-trust-accounts"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div><div></div></div><a class="indexterm" name="id2875074"></a><p>
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="machine-trust-accounts"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div><div></div></div><a class="indexterm" name="id2872579"></a><p>
 A machine trust account is an account that is used to authenticate a client
 machine
 (rather than a user) to the Domain Controller server.  In Windows terminology,
@@ -1535,7 +1535,7 @@ as follows:
 
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 	A Domain Security Account (stored in the 
-	<a class="indexterm" name="id2875124"></a><i class="parameter"><tt>passdb backend</tt></i> that has been configured in the
+	<a class="indexterm" name="id2872629"></a><i class="parameter"><tt>passdb backend</tt></i> that has been configured in the
 	<tt class="filename">smb.conf</tt> file. The precise nature of the account information that is
 	stored depends on the type of backend database that has been chosen.
 	</p><p>
@@ -1554,13 +1554,13 @@ as follows:
 	simplified mode of operation that does not require UNIX user accounts, but
 	this may not be a feature of the early releases of Samba-3.
 	</p></li></ul></div><p>
-</p><a class="indexterm" name="id2875206"></a><p>
+</p><a class="indexterm" name="id2872712"></a><p>
 There are three ways to create machine trust accounts:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 	Manual creation from the UNIX/Linux command line. Here, both the Samba and
 	corresponding UNIX account are created by hand.
 	</p></li><li><p>
-	<a class="indexterm" name="id2875239"></a>
+	<a class="indexterm" name="id2872744"></a>
 	Using the MS Windows NT4 Server Manager (either from an NT4 Domain member
 	server, or using the Nexus toolkit available from the Microsoft web site.
 	This tool can be run from any MS Windows machine so long as the user is
@@ -1570,13 +1570,13 @@ There are three ways to create machine trust accounts:
 	created by Samba at the time the client is joined to the domain.
 	(For security, this is the recommended method.) The corresponding UNIX
 	account may be created automatically or manually. 
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875264"></a>Manual Creation of Machine Trust Accounts</h3></div></div><div></div></div><p>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872769"></a>Manual Creation of Machine Trust Accounts</h3></div></div><div></div></div><p>
 The first step in manually creating a machine trust account is to manually
 create the corresponding UNIX account in <tt class="filename">/etc/passwd</tt>. 
 This can be done using <b class="command">vipw</b> or another 'add user' command
 that is normally used to create new UNIX accounts.  The following is an example for a Linux based Samba server:
-<a class="indexterm" name="id2875294"></a>
-<a class="indexterm" name="id2875302"></a>
+<a class="indexterm" name="id2872799"></a>
+<a class="indexterm" name="id2872808"></a>
 
 
 </p><p>
@@ -1587,7 +1587,7 @@ that is normally used to create new UNIX accounts.  The following is an example
 <tt class="prompt">root# </tt><b class="userinput"><tt>passwd -l <i class="replaceable"><tt>machine_name</tt></i>$</tt></b>
 </pre><p>
 </p><p>
-<a class="indexterm" name="id2875364"></a>
+<a class="indexterm" name="id2872869"></a>
 On *BSD systems, this can be done using the <b class="command">chpass</b> utility:
 </p><p>
 </p><pre class="screen">
@@ -1625,14 +1625,14 @@ the corresponding UNIX account.
 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p>
 	Manually creating a machine trust account using this method is the 
 	equivalent of creating a machine trust account on a Windows NT PDC using 
-	<a class="indexterm" name="id2875530"></a>
+	<a class="indexterm" name="id2873036"></a>
 	the <span class="application">Server Manager</span>.  From the time at which the 
 	account is created to the time which the client joins the domain and 
 	changes the password, your domain is vulnerable to an intruder joining 
 	your domain using a machine with the same NetBIOS name.  A PDC inherently 
 	trusts members of the domain and will serve out a large degree of user 
 	information to such clients.  You have been warned!
-	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875556"></a>Using NT4 Server Manager to Add Machine Accounts to the Domain</h3></div></div><div></div></div><p>
+	</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873061"></a>Using NT4 Server Manager to Add Machine Accounts to the Domain</h3></div></div><div></div></div><p>
 If the machine from which you are trying to manage the domain is an 
 <span class="application">MS Windows NT4 workstation or MS Windows 200x / XP Professional</span>
 then the tool of choice is the package called <b class="command">SRVTOOLS.EXE</b>. 
@@ -1666,7 +1666,7 @@ Launch the <b class="command">srvmgr.exe</b> (Server Manager for Domains) and fo
 	<span class="guilabel">Add NT Workstation of Server</span>, then
 	enter the machine name in the field provided, then click the 
 	<span class="guibutton">Add</span> button.
-	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875771"></a>"On-the-Fly" Creation of Machine Trust Accounts</h3></div></div><div></div></div><p>
+	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873276"></a>"On-the-Fly" Creation of Machine Trust Accounts</h3></div></div><div></div></div><p>
 The second (and recommended) way of creating machine trust accounts is
 simply to allow the Samba server to create them as needed when the client
 is joined to the domain.
@@ -1677,10 +1677,10 @@ add machine script option in
 accounts may also be created manually.
 </p><p>
 Below is an example for a RedHat Linux system.
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># &lt;...remainder of parameters...&gt;</td></tr><tr><td><i class="parameter"><tt>add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875842"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div><div></div></div><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># &lt;...remainder of parameters...&gt;</td></tr><tr><td><i class="parameter"><tt>add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873347"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div><div></div></div><p>
 The procedure for making an MS Windows workstation of server a member of the domain varies
 with the version of Windows:
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875855"></a>Windows 200x XP Professional</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873360"></a>Windows 200x XP Professional</h4></div></div><div></div></div><p>
 	When the user elects to make the client a domain member, Windows 200x prompts for
 	an account and password that has privileges to create  machine accounts in the domain.
 	A Samba administrative account (i.e., a Samba account that has root privileges on the
@@ -1694,13 +1694,13 @@ with the version of Windows:
 	The name of the account that is used to create domain member machine accounts can be
 	anything the network administrator may choose. If it is other than <span class="emphasis"><em>root</em></span>
 	then this is easily mapped to root using the file pointed to be the <tt class="filename">smb.conf</tt> parameter
-	<a class="indexterm" name="id2875906"></a><i class="parameter"><tt>username map</tt></i> = /etc/samba/smbusers.
+	<a class="indexterm" name="id2873412"></a><i class="parameter"><tt>username map</tt></i> = /etc/samba/smbusers.
 	</p><p>
 	The session key of the Samba administrative account acts as an
 	encryption key for setting the password of the machine trust
 	account. The machine trust account will be created on-the-fly, or
 	updated if it already exists.
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875931"></a>Windows NT4</h4></div></div><div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873436"></a>Windows NT4</h4></div></div><div></div></div><p>
 	If the machine trust account was created manually, on the
 	Identification Changes menu enter the domain name, but do not
 	check the box <span class="guilabel">Create a Computer Account in the Domain</span>.
@@ -1713,7 +1713,7 @@ with the version of Windows:
 	Domain</span>.  In this case, joining the domain proceeds as above
 	for Windows 2000 (i.e., you must supply a Samba administrative account when
 	prompted).
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875971"></a>Samba</h4></div></div><div></div></div><p>Joining a Samba client to a domain is documented in 
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873477"></a>Samba</h4></div></div><div></div></div><p>Joining a Samba client to a domain is documented in 
 		<a href="#domain-member-server" title="Domain Member Server">the domain member chapter</a>.
 	</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domain-member-server"></a>Domain Member Server</h2></div></div><div></div></div><p>
 This mode of server operation involves the Samba machine being made a member
@@ -1735,19 +1735,19 @@ for more information regarding how to create a domain
 machine account for a domain member server as well as for information
 regarding how to enable the Samba domain member machine to join the domain and
 to be fully trusted by it.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876053"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><p>
-	</p><div class="table"><a name="id2876064"></a><p class="title"><b>Table�7.1.�Assumptions</b></p><table summary="Assumptions" border="1"><colgroup><col><col></colgroup><tbody><tr><td align="left">NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="left">Win2K/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="left">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="left">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873558"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><p>
+	</p><div class="table"><a name="id2873569"></a><p class="title"><b>Table�7.1.�Assumptions</b></p><table summary="Assumptions" border="1"><colgroup><col><col></colgroup><tbody><tr><td align="left">NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="left">Win2K/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="left">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="left">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div><p>
 </p><p>
 First, you must edit your <tt class="filename">smb.conf</tt> file to tell Samba it should
 now use domain security.
 </p><p>
 	Change (or add) your 
-	<a class="indexterm" name="id2876137"></a><i class="parameter"><tt>security</tt></i> line in the [global] section 
+	<a class="indexterm" name="id2873642"></a><i class="parameter"><tt>security</tt></i> line in the [global] section 
 of your <tt class="filename">smb.conf</tt> to read:
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = domain</tt></i></td></tr></table><p>
 </p><p>
-Next change the <a class="indexterm" name="id2876180"></a><i class="parameter"><tt>workgroup</tt></i> line in the <i class="parameter"><tt>[global]</tt></i>
+Next change the <a class="indexterm" name="id2873686"></a><i class="parameter"><tt>workgroup</tt></i> line in the <i class="parameter"><tt>[global]</tt></i>
 section to read: 
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr></table><p>
@@ -1755,10 +1755,10 @@ section to read:
 as this is the name of the domain we are joining.
 </p><p>
 You must also have the parameter
-<a class="indexterm" name="id2876230"></a><i class="parameter"><tt>encrypt passwords</tt></i> set to <tt class="constant">yes
+<a class="indexterm" name="id2873735"></a><i class="parameter"><tt>encrypt passwords</tt></i> set to <tt class="constant">yes
 </tt> in order for your users to authenticate to the NT PDC.
 </p><p>
-Finally, add (or modify) a <a class="indexterm" name="id2876255"></a><i class="parameter"><tt>password server</tt></i> line in the [global]
+Finally, add (or modify) a <a class="indexterm" name="id2873760"></a><i class="parameter"><tt>password server</tt></i> line in the [global]
 section to read: 
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password server = DOMPDC DOMBDC1 DOMBDC2</tt></i></td></tr></table><p>
@@ -1824,7 +1824,7 @@ samba daemons depends on your distribution, but in most cases running
 	<tt class="prompt">root# </tt>/etc/init.d/samba restart
 </pre><p>
 does the job.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876489"></a>Why is this better than security = server?</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873995"></a>Why is this better than security = server?</h3></div></div><div></div></div><p>
 Currently, domain security in Samba doesn't free you from 
 having to create local UNIX users to represent the users attaching 
 to your server. This means that if domain user <tt class="constant">DOM\fred
@@ -1846,11 +1846,11 @@ exactly the same way NT servers do (i.e., you can add Samba servers into
 a resource domain and have the authentication passed on from a resource
 domain PDC to an account domain PDC).
 </p><p>
-In addition, with <a class="indexterm" name="id2876545"></a><i class="parameter"><tt>security</tt></i> = server every Samba 
+In addition, with <a class="indexterm" name="id2874050"></a><i class="parameter"><tt>security</tt></i> = server every Samba 
 daemon on a server has to keep a connection open to the 
 authenticating server for as long as that daemon lasts. This can drain 
 the connection resources on a Microsoft NT server and cause it to run 
-out of available connections. With <a class="indexterm" name="id2876564"></a><i class="parameter"><tt>security</tt></i> = domain, 
+out of available connections. With <a class="indexterm" name="id2874069"></a><i class="parameter"><tt>security</tt></i> = domain, 
 however, the Samba daemons connect to the PDC/BDC only for as long 
 as is necessary to authenticate the user, and then drop the connection, 
 thus conserving PDC connection resources.
@@ -1864,22 +1864,22 @@ Much of the text of this document
 was first published in the Web magazine 
 <a href="http://www.linuxworld.com" target="_top">LinuxWorld</a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">Doing 
 the NIS/NT Samba</a>.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ads-member"></a>Samba ADS Domain Membership</h2></div></div><div></div></div><a class="indexterm" name="id2876631"></a><a class="indexterm" name="id2876640"></a><a class="indexterm" name="id2876651"></a><a class="indexterm" name="id2876659"></a><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ads-member"></a>Samba ADS Domain Membership</h2></div></div><div></div></div><a class="indexterm" name="id2874135"></a><a class="indexterm" name="id2874144"></a><a class="indexterm" name="id2874155"></a><a class="indexterm" name="id2874163"></a><p>
 This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a
 Windows2000 KDC. A familiarity with Kerberos is assumed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876674"></a>Setup your <tt class="filename">smb.conf</tt></h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874178"></a>Setup your <tt class="filename">smb.conf</tt></h3></div></div><div></div></div><p>
 You must use at least the following 3 options in <tt class="filename">smb.conf</tt>:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>realm = your.kerberos.REALM</tt></i></td></tr><tr><td><i class="parameter"><tt>security = ADS</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr></table><p>
 In case samba can't figure out your ads server using your realm name, use the 
-<a class="indexterm" name="id2876735"></a><i class="parameter"><tt>ads server</tt></i> option in <tt class="filename">smb.conf</tt>:
+<a class="indexterm" name="id2874239"></a><i class="parameter"><tt>ads server</tt></i> option in <tt class="filename">smb.conf</tt>:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>ads server = your.kerberos.server</tt></i></td></tr></table><p>
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 You do <span class="emphasis"><em>not</em></span> need a smbpasswd file, and older clients will be authenticated as 
-if <a class="indexterm" name="id2876782"></a><i class="parameter"><tt>security</tt></i> = domain, although it won't do any harm and 
+if <a class="indexterm" name="id2874286"></a><i class="parameter"><tt>security</tt></i> = domain, although it won't do any harm and 
 allows you to have local users not in the domain. It is expected that the above 
 required options will change soon when active directory integration will get 
 better.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876803"></a>Setup your <tt class="filename">/etc/krb5.conf</tt></h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874307"></a>Setup your <tt class="filename">/etc/krb5.conf</tt></h3></div></div><div></div></div><p>
 The minimal configuration for <tt class="filename">krb5.conf</tt> is:
 </p><pre class="programlisting">
 [libdefaults]
@@ -1889,7 +1889,7 @@ The minimal configuration for <tt class="filename">krb5.conf</tt> is:
 	YOUR.KERBEROS.REALM = {
 	kdc = your.kerberos.server
 	    }
-</pre><a class="indexterm" name="id2876839"></a><p>
+</pre><a class="indexterm" name="id2874343"></a><p>
 Test your config by doing a <b class="userinput"><tt>kinit
 <i class="replaceable"><tt>USERNAME</tt></i>@<i class="replaceable"><tt>REALM</tt></i></tt></b> and
 making sure that your password is accepted by the Win2000 KDC.
@@ -1924,7 +1924,7 @@ As a user that has write permission on the Samba private directory
 </p><pre class="screen">
 <tt class="prompt">root# </tt> <b class="userinput"><tt>net ads join -U Administrator%password</tt></b>
 </pre><p>
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2877020"></a>Possible errors</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874526"></a>Possible errors</h4></div></div><div></div></div><p>
 </p><div class="variablelist"><dl><dt><span class="term"><span class="errorname">ADS support not compiled in</span></span></dt><dd><p>Samba must be reconfigured (remove config.cache) and recompiled
 	(make clean all install) after the Kerberos libs and headers are installed.
 	</p></dd><dt><span class="term"><span class="errorname">net ads join prompts for user name</span></span></dt><dd><p>You need to login to the domain using <b class="userinput"><tt>kinit
@@ -1940,17 +1940,17 @@ On a Windows 2000 client try <b class="userinput"><tt>net use * \\server\share</
 be logged in with Kerberos without needing to know a password. If
 this fails then run <b class="userinput"><tt>klist tickets</tt></b>. Did you get a ticket for the
 server? Does it have an encoding type of DES-CBC-MD5 ? 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-smbclient"></a>Testing with <span class="application">smbclient</span></h3></div></div><div></div></div><a class="indexterm" name="id2877145"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-smbclient"></a>Testing with <span class="application">smbclient</span></h3></div></div><div></div></div><a class="indexterm" name="id2874651"></a><p>
 On your Samba server try to login to a Win2000 server or your Samba
 server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but
 specify the <tt class="option">-k</tt> option to choose Kerberos authentication.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877177"></a>Notes</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874683"></a>Notes</h3></div></div><div></div></div><p>
 You must change administrator password at least once after DC 
 install, to create the right encoding types
 </p><p>
 W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
 their defaults DNS setup. Maybe this will be fixed later in service packs.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877199"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874706"></a>Common Errors</h2></div></div><div></div></div><p>
 In the process of adding / deleting / re-adding domain member machine accounts there are
 many traps for the unwary player and there are many &#8220;<span class="quote">little</span>&#8221; things that can go wrong.
 It is particularly interesting how often subscribers on the samba mailing list have concluded
@@ -1958,7 +1958,7 @@ after repeated failed attempts to add a machine account that it is necessary to
 MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type
 of problem. The real solution is often very simple, and with understanding of how MS Windows
 networking functions easy to overcome.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877226"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874732"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p>
 &#8220;<span class="quote"> A Windows workstation was reinstalled. The original domain machine
 account was deleted and added immediately. The workstation will not join the domain if I use 
 the same machine name. Attempts to add the machine fail with a message that the machine already
@@ -1967,14 +1967,14 @@ exists on the network - I know it doesn't. Why is this failing?</span>&#8221;
 The original name is still in the NetBIOS name cache and must expire after machine account
 deletion BEFORE adding that same name as a domain member again. The best advice is to delete
 the old account and then to add the machine with a new name.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877258"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874764"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
 message that, <span class="errorname">The machine could not be added at this time, there is a network problem.
 	Please try again later.</span> Why?</span>&#8221;
 </p><p>
-You should check that there is an <a class="indexterm" name="id2877285"></a><i class="parameter"><tt>add machine script</tt></i> in your <tt class="filename">smb.conf</tt>
+You should check that there is an <a class="indexterm" name="id2874791"></a><i class="parameter"><tt>add machine script</tt></i> in your <tt class="filename">smb.conf</tt>
 file. If there is not, please add one that is appropriate for your OS platform. If a script
-has been defined you will need to debug it's operation. Increase the <a class="indexterm" name="id2877310"></a><i class="parameter"><tt>log level</tt></i>
+has been defined you will need to debug it's operation. Increase the <a class="indexterm" name="id2874816"></a><i class="parameter"><tt>log level</tt></i>
 in the <tt class="filename">smb.conf</tt> file to level 10, then try to rejoin the domain. Check the logs to see which
 operation is failing.
 </p><p>
@@ -1992,12 +1992,12 @@ Possible causes include:
 	then make sure that the machine name you are trying to add can be added using this
 	tool. <b class="command">Useradd</b> on some systems will not allow any upper case characters
 	nor will it allow spaces in the name.
-	</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter�8.�Stand-Alone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877459">Features and Benefits</a></dt><dt><a href="#id2877498">Background</a></dt><dt><a href="#id2877581">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2878101">Common Errors</a></dt></dl></div><p>
+	</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter�8.�Stand-Alone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2874966">Features and Benefits</a></dt><dt><a href="#id2875004">Background</a></dt><dt><a href="#id2875078">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2875598">Common Errors</a></dt></dl></div><p>
 Stand-Alone servers are independent of Domain Controllers on the network.
 They are NOT domain members and function more like workgroup servers. In many
 cases a stand-alone server is configured with a minimum of security control
 with the intent that all data served will be readily accessible to all users.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877459"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874966"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Stand-Alone servers can be as secure or as insecure as needs dictate. They can
 have simple or complex configurations. Above all, despite the hoopla about
 Domain security they remain a very common installation.
@@ -2014,7 +2014,7 @@ that are queued off a single central server. Everyone needs to be able to print
 to the printers, there is no need to affect any access controls and no files will
 be served from the print server. Again a share mode stand-alone server makes
 a great solution.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877498"></a>Background</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875004"></a>Background</h2></div></div><div></div></div><p>
 The term <span class="emphasis"><em>stand-alone server</em></span> means that the server
 will provide local authentication and access control for all resources
 that are available from it. In general this means that there will be a
@@ -2043,7 +2043,7 @@ This means that the Samba server may use the local UNIX/Linux system password da
 local smbpasswd file, or may use
 an LDAP back end, or even via PAM and Winbind another CIFS/SMB server
 for authentication.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877581"></a>Example Configuration</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875078"></a>Example Configuration</h2></div></div><div></div></div><p>
 The following examples are designed to inspire simplicity. It is too easy to
 attempt a high level of creativity and to introduce too much complexity in
 server and network design.
@@ -2053,7 +2053,7 @@ Here is the smb.conf file that will do this. Assume that all the reference docum
 are stored in the directory /export, that the documents are owned by a user other than
 nobody. No home directories are shared, that are no users in the <tt class="filename">/etc/passwd</tt>
 UNIX system database. This is a very simple system to administer.
-</p><div class="example"><a name="id2877627"></a><p class="title"><b>Example�8.1.�smb.conf for Reference Documentation Server</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = 192.168.1.1</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[data]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Data</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export</tt></i></td></tr><tr><td><i class="parameter"><tt>guest only = Yes</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2875123"></a><p class="title"><b>Example�8.1.�smb.conf for Reference Documentation Server</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = 192.168.1.1</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[data]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Data</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export</tt></i></td></tr><tr><td><i class="parameter"><tt>guest only = Yes</tt></i></td></tr></table></div><p>
 In the above example the machine name is set to REFDOCS, the workgroup is set to the name
 of the local workgroup so that the machine will appear in with systems users are familiar
 with. The only password backend required is the "guest" backend so as to allow default
@@ -2099,48 +2099,48 @@ the anonymous (guest) user, two things will be required:
 <tt class="prompt">root# </tt><b class="userinput"><tt>chmod a+rwt /var/spool/samba</tt></b>
 </pre><p>
 	</p></li></ul></div><p>
-	</p><div class="example"><a name="id2877945"></a><p class="title"><b>Example�8.2.�smb.conf for anonymous printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = noldor</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>use client driver = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div><p>
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878101"></a>Common Errors</h2></div></div><div></div></div><p>
+	</p><div class="example"><a name="id2875442"></a><p class="title"><b>Example�8.2.�smb.conf for anonymous printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td>#  Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = noldor</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>use client driver = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875598"></a>Common Errors</h2></div></div><div></div></div><p>
 The greatest mistake so often made is to make a network configuration too complex.
 It pays to use the simplest solution that will meet the needs of the moment.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�9.�MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878165">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878165"></a>Note</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�9.�MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2875663">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875663"></a>Note</h2></div></div><div></div></div><p>
 This chapter did not make it into this release.
 It is planned for the published release of this document.
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2878194"></a>Valuable Nuts and Bolts Information</h1></div></div><div></div></div><p>
+</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2875691"></a>Valuable Nuts and Bolts Information</h1></div></div><div></div></div><p>
 Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2878319">Features and Benefits</a></dt><dt><a href="#id2878408">What is Browsing?</a></dt><dt><a href="#id2878720">Discussion</a></dt><dd><dl><dt><a href="#id2878736">NetBIOS over TCP/IP</a></dt><dt><a href="#id2878972">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2879137">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2879284">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2879819">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2880217">Making Samba the domain master</a></dt><dt><a href="#id2880395">Note about broadcast addresses</a></dt><dt><a href="#id2880412">Multiple interfaces</a></dt><dt><a href="#id2880448">Use of the Remote Announce parameter</a></dt><dt><a href="#id2880607">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2880684">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2880872">Setting up a WINS server</a></dt><dt><a href="#id2881128">WINS Replication</a></dt><dt><a href="#id2881154">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2881238">Helpful Hints</a></dt><dd><dl><dt><a href="#id2881252">Windows Networking Protocols</a></dt><dt><a href="#id2881317">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2881481">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2881541">Browsing support in Samba</a></dt><dt><a href="#id2881662">Problem resolution</a></dt><dt><a href="#id2881749">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2882439">Common Errors</a></dt><dd><dl><dt><a href="#id2882454">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2882497">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2882539">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2882820">Features and Benefits</a></dt><dd><dl><dt><a href="#id2882834">Backwards Compatibility Backends</a></dt><dt><a href="#id2882936">New Backends</a></dt></dl></dd><dt><a href="#id2883109">Technical Information</a></dt><dd><dl><dt><a href="#id2883235">Important Notes About Security</a></dt><dt><a href="#id2883502">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2883688">The smbpasswd Command</a></dt><dt><a href="#id2883959">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2884197">Password Backends</a></dt><dd><dl><dt><a href="#id2884238">Plain Text</a></dt><dt><a href="#id2884279">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2884392">tdbsam</a></dt><dt><a href="#id2884420">ldapsam</a></dt><dt><a href="#id2886247">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2887095">Common Errors</a></dt><dd><dl><dt><a href="#id2887102">Users can not logon</a></dt><dt><a href="#id2887147">Users being added to wrong backend database</a></dt><dt><a href="#id2887258">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2887487">Features and Benefits</a></dt><dt><a href="#id2887722">Discussion</a></dt><dd><dl><dt><a href="#id2887948">Example Configuration</a></dt></dl></dd><dt><a href="#id2888015">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2888029">Sample smb.conf add group script</a></dt><dt><a href="#id2888108">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2888184">Common Errors</a></dt><dd><dl><dt><a href="#id2888199">Adding Groups Fails</a></dt><dt><a href="#id2888268">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2888294">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2888551">Features and Benefits</a></dt><dt><a href="#id2888688">File System Access Controls</a></dt><dd><dl><dt><a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2889023">Managing Directories</a></dt><dt><a href="#id2889117">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2889345">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2889373">User and Group Based Controls</a></dt><dt><a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2890173">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2890553">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2890626">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2890925">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2890933">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2890978">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2891057">Viewing file ownership</a></dt><dt><a href="#id2891188">Viewing File or Directory Permissions</a></dt><dt><a href="#id2891423">Modifying file or directory permissions</a></dt><dt><a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt><a href="#id2891979">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2892060">Common Errors</a></dt><dd><dl><dt><a href="#id2892074">Users can not write to a public share</a></dt><dt><a href="#id2892503">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2892555">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2892803">Features and Benefits</a></dt><dt><a href="#id2892860">Discussion</a></dt><dd><dl><dt><a href="#id2893002">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2893677">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2893787">Example Configuration</a></dt></dl></dd><dt><a href="#id2894184">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2894410">Workstation Service Entries</a></dt><dt><a href="#id2894437">Server Service Entries</a></dt></dl></dd><dt><a href="#id2894516">Persistent Data Corruption</a></dt><dt><a href="#id2894546">Common Errors</a></dt><dd><dl><dt><a href="#id2894619">locking.tdb error messages</a></dt><dt><a href="#id2894658">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2894680">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2894712">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2894878">Introduction</a></dt><dt><a href="#id2894910">Features and Benefits</a></dt><dt><a href="#id2894983">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2895003">Using host based protection</a></dt><dt><a href="#id2895102">User based protection</a></dt><dt><a href="#id2895162">Using interface protection</a></dt><dt><a href="#id2895230">Using a firewall</a></dt><dt><a href="#id2895287">Using a IPC$ share deny</a></dt><dt><a href="#id2895375">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2895433">Upgrading Samba</a></dt><dt><a href="#id2895457">Common Errors</a></dt><dd><dl><dt><a href="#id2895476">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2895500">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2895790">Features and Benefits</a></dt><dt><a href="#id2895819">Trust Relationship Background</a></dt><dt><a href="#id2895908">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2895935">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2896007">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2896054">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2896233">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2896417">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2896555">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2896661">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2896731">Features and Benefits</a></dt><dt><a href="#id2897006">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2897126">Features and Benefits</a></dt><dt><a href="#id2897192">Technical Introduction</a></dt><dd><dl><dt><a href="#id2897230">What happens if you send a Job from a Client</a></dt><dt><a href="#id2897302">Printing Related Configuration Parameters</a></dt><dt><a href="#id2897387">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2897853">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2898017">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2898105">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2898438">Extended Sample Configuration to Print</a></dt><dt><a href="#id2898769">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2898782">The [global] Section</a></dt><dt><a href="#id2899274">The [printers] Section</a></dt><dt><a href="#id2899717">Any [my_printer_name] Section</a></dt><dt><a href="#id2900032">Print Commands</a></dt><dt><a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2900758">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2901088">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2901237">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2901389">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2901502">Creating the [print$] Share</a></dt><dt><a href="#id2901686">Parameters in the [print$] Section</a></dt><dt><a href="#id2901973">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2902140">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2902234">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2902432">Setting Drivers for existing Printers with
-rpcclient</a></dt></dl></dd><dt><a href="#id2904055">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2904073">The first Client Driver Installation</a></dt><dt><a href="#id2904269">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2904576">Further Client Driver Install Procedures</a></dt><dt><a href="#id2904670">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2904838">Other Gotchas</a></dt><dd><dl><dt><a href="#id2904870">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2905319">Supporting large Numbers of Printers</a></dt><dt><a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2905915">Weird Error Message Cannot connect under a
-different Name</a></dt><dt><a href="#id2906013">Be careful when assembling Driver Files</a></dt><dt><a href="#id2906300">Samba and Printer Ports</a></dt><dt><a href="#id2906377">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2906398">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2906443">What is Imprints?</a></dt><dt><a href="#id2906484">Creating Printer Driver Packages</a></dt><dt><a href="#id2906504">The Imprints Server</a></dt><dt><a href="#id2906528">The Installation Client</a></dt></dl></dd><dt><a href="#id2906681">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2907000">The addprinter command</a></dt><dt><a href="#id2907046">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2907213">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2907227">Common Errors</a></dt><dd><dl><dt><a href="#id2907234">I give my root password but I don't get access</a></dt><dt><a href="#id2907268">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2907403">Introduction</a></dt><dd><dl><dt><a href="#id2907410">Features and Benefits</a></dt><dt><a href="#id2907453">Overview</a></dt></dl></dd><dt><a href="#id2907507">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2907600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2907841">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2908016">More complex smb.conf Settings for
-CUPS</a></dt></dl></dd><dt><a href="#id2908362">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2908382">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2908431">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2908485">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2908552">Explicitly enable "raw" printing for
-application/octet-stream!</a></dt><dt><a href="#id2908739">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2908865">Using CUPS/Samba in an advanced Way -- intelligent printing
-with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2909034">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2909441">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2909567">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2909654">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2909760">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2909782">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2909959">MIME types and CUPS Filters</a></dt><dt><a href="#id2910165">MIME type Conversion Rules</a></dt><dt><a href="#id2910315">Filter Requirements</a></dt><dt><a href="#id2910493">Prefilters</a></dt><dt><a href="#id2910595">pstops</a></dt><dt><a href="#id2910704">pstoraster</a></dt><dt><a href="#id2910875">imagetops and imagetoraster</a></dt><dt><a href="#id2910938">rasterto [printers specific]</a></dt><dt><a href="#id2911090">CUPS Backends</a></dt><dt><a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2911562">The Complete Picture</a></dt><dt><a href="#id2911576">mime.convs</a></dt><dt><a href="#id2911630">"Raw" printing</a></dt><dt><a href="#id2911697">"application/octet-stream" printing</a></dt><dt><a href="#id2911929">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a></dt><dt><a href="#id2912410">Examples for filtering Chains</a></dt><dt><a href="#id2912731">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2912872">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2912949">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2912965">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2913020">Driver Execution on the Client</a></dt><dt><a href="#id2913090">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2913201">Network Printing (Windows clients -- UNIX/Samba Print
-Servers)</a></dt><dd><dl><dt><a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2913432">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2913594">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2913643">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2913717">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2913734">Printer Drivers running in "Kernel Mode" cause many
-Problems</a></dt><dt><a href="#id2913768">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2913789">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2913833">PostScript Drivers with no major problems -- even in Kernel
-Mode</a></dt></dl></dd><dt><a href="#id2913895">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2913913">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2914014">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2914516">Recognize the different Driver Files</a></dt><dt><a href="#id2914656">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2914689">ESP Print Pro Package of "PostScript Driver for
-WinNT/2k/XP"</a></dt><dt><a href="#id2914749">Caveats to be considered</a></dt><dt><a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2915344">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2915567">Understanding cupsaddsmb</a></dt><dt><a href="#id2915714">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2915798">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2915877">cupsaddsmb Flowchart</a></dt><dt><a href="#id2915946">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2916097">Avoiding critical PostScript Driver Settings on the
-Client</a></dt></dl></dd><dt><a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a></dt><dd><dl><dt><a href="#id2916423">A Check of the rpcclient man Page</a></dt><dt><a href="#id2916536">Understanding the rpcclient man page</a></dt><dt><a href="#id2916644">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2916790">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2918021">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2918418">Trivial DataBase Files</a></dt><dt><a href="#id2918497">Binary Format</a></dt><dt><a href="#id2918559">Losing *.tdb Files</a></dt><dt><a href="#id2918617">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2918890">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2919583">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2920055">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2920098">Setting up Quotas</a></dt><dt><a href="#id2920162">Correct and incorrect Accounting</a></dt><dt><a href="#id2920202">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2920282">The page_log File Syntax</a></dt><dt><a href="#id2920392">Possible Shortcomings</a></dt><dt><a href="#id2920463">Future Developments</a></dt><dt><a href="#id2920510">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2920525">Additional Material</a></dt><dt><a href="#id2920734">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2920792">CUPS Configuration Settings explained</a></dt><dt><a href="#id2920874">Pre-conditions</a></dt><dt><a href="#id2921030">Manual Configuration</a></dt></dl></dd><dt><a href="#id2921088">In Case of Trouble.....</a></dt><dt><a href="#id2921154">Printing from CUPS to Windows attached
-Printers</a></dt><dt><a href="#id2921434">More CUPS filtering Chains</a></dt><dt><a href="#id2921535">Common Errors</a></dt><dd><dl><dt><a href="#id2921542">Win9x client can't install driver</a></dt><dt><a href="#id2921558">"cupsaddsmb" keeps asking for root password in
-			neverending loop</a></dt><dt><a href="#id2921604">"cupsaddsmb" gives "No PPD file for printer..."
-			message while PPD file is present</a></dt><dt><a href="#id2921660">Client can't connect to Samba printer</a></dt><dt><a href="#id2921688">Can't reconnect to Samba under new account
-			from Win2K/XP</a></dt><dt><a href="#id2921914">Avoid being connected to the Samba server as the
-		"wrong" user</a></dt><dt><a href="#id2921967">Upgrading to CUPS drivers from Adobe drivers on
-		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2921981">Can't use "cupsaddsmb" on Samba server which is
-		a PDC</a></dt><dt><a href="#id2922010">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2922027">Win2K/XP "Local Security
-		Policies"</a></dt><dt><a href="#id2922043">WinXP clients: "Administrator can not install
-		printers for all local users"</a></dt><dt><a href="#id2922065">"Print Change Notify" functions on
-		NT-clients</a></dt><dt><a href="#id2922084">WinXP-SP1</a></dt><dt><a href="#id2922126">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2922400">Most common blunders in driver
-		settings on Windows clients</a></dt><dt><a href="#id2922445">cupsaddsmb does not work
-		with newly installed printer</a></dt><dt><a href="#id2922506">Permissions on
+</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2875816">Features and Benefits</a></dt><dt><a href="#id2875904">What is Browsing?</a></dt><dt><a href="#id2876217">Discussion</a></dt><dd><dl><dt><a href="#id2876233">NetBIOS over TCP/IP</a></dt><dt><a href="#id2876469">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2876635">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2876781">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877309">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2877716">Making Samba the domain master</a></dt><dt><a href="#id2877893">Note about broadcast addresses</a></dt><dt><a href="#id2877911">Multiple interfaces</a></dt><dt><a href="#id2877946">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878104">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878182">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878371">Setting up a WINS server</a></dt><dt><a href="#id2878627">WINS Replication</a></dt><dt><a href="#id2878652">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2878737">Helpful Hints</a></dt><dd><dl><dt><a href="#id2878750">Windows Networking Protocols</a></dt><dt><a href="#id2878822">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2878986">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879046">Browsing support in Samba</a></dt><dt><a href="#id2879168">Problem resolution</a></dt><dt><a href="#id2879254">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2879936">Common Errors</a></dt><dd><dl><dt><a href="#id2879950">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2879979">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880021">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2880302">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880315">Backwards Compatibility Backends</a></dt><dt><a href="#id2880417">New Backends</a></dt></dl></dd><dt><a href="#id2880590">Technical Information</a></dt><dd><dl><dt><a href="#id2880717">Important Notes About Security</a></dt><dt><a href="#id2880966">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881151">The smbpasswd Command</a></dt><dt><a href="#id2881423">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2881676">Password Backends</a></dt><dd><dl><dt><a href="#id2881717">Plain Text</a></dt><dt><a href="#id2881758">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2881871">tdbsam</a></dt><dt><a href="#id2881898">ldapsam</a></dt><dt><a href="#id2883727">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2884575">Common Errors</a></dt><dd><dl><dt><a href="#id2884582">Users can not logon</a></dt><dt><a href="#id2884627">Users being added to wrong backend database</a></dt><dt><a href="#id2884738">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2884967">Features and Benefits</a></dt><dt><a href="#id2885202">Discussion</a></dt><dd><dl><dt><a href="#id2885422">Example Configuration</a></dt></dl></dd><dt><a href="#id2885489">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2885503">Sample smb.conf add group script</a></dt><dt><a href="#id2885582">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2885658">Common Errors</a></dt><dd><dl><dt><a href="#id2885674">Adding Groups Fails</a></dt><dt><a href="#id2885742">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2885768">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2886024">Features and Benefits</a></dt><dt><a href="#id2886154">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2886489">Managing Directories</a></dt><dt><a href="#id2886582">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2886810">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2886837">User and Group Based Controls</a></dt><dt><a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2887639">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888020">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888092">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2888391">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2888399">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2888444">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2888523">Viewing file ownership</a></dt><dt><a href="#id2888655">Viewing File or Directory Permissions</a></dt><dt><a href="#id2888889">Modifying file or directory permissions</a></dt><dt><a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt><a href="#id2889446">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2889526">Common Errors</a></dt><dd><dl><dt><a href="#id2889540">Users can not write to a public share</a></dt><dt><a href="#id2889969">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890022">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2890270">Features and Benefits</a></dt><dt><a href="#id2890336">Discussion</a></dt><dd><dl><dt><a href="#id2890479">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891158">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2891268">Example Configuration</a></dt></dl></dd><dt><a href="#id2891665">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2891896">Workstation Service Entries</a></dt><dt><a href="#id2891924">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892003">Persistent Data Corruption</a></dt><dt><a href="#id2892032">Common Errors</a></dt><dd><dl><dt><a href="#id2892106">locking.tdb error messages</a></dt><dt><a href="#id2892144">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892167">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892198">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2892365">Introduction</a></dt><dt><a href="#id2892398">Features and Benefits</a></dt><dt><a href="#id2892471">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2892490">Using host based protection</a></dt><dt><a href="#id2892590">User based protection</a></dt><dt><a href="#id2892650">Using interface protection</a></dt><dt><a href="#id2892717">Using a firewall</a></dt><dt><a href="#id2892774">Using a IPC$ share deny</a></dt><dt><a href="#id2892867">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2892926">Upgrading Samba</a></dt><dt><a href="#id2892950">Common Errors</a></dt><dd><dl><dt><a href="#id2892968">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2892992">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2893283">Features and Benefits</a></dt><dt><a href="#id2893311">Trust Relationship Background</a></dt><dt><a href="#id2893400">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2893428">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2893500">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2893547">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2893725">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2893918">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894055">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894162">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2894231">Features and Benefits</a></dt><dt><a href="#id2894506">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2894626">Features and Benefits</a></dt><dt><a href="#id2894693">Technical Introduction</a></dt><dd><dl><dt><a href="#id2894730">What happens if you send a Job from a Client</a></dt><dt><a href="#id2894801">Printing Related Configuration Parameters</a></dt><dt><a href="#id2894888">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2895354">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2895518">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2895606">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2895939">Extended Sample Configuration to Print</a></dt><dt><a href="#id2896270">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2896282">The [global] Section</a></dt><dt><a href="#id2896767">The [printers] Section</a></dt><dt><a href="#id2897210">Any [my_printer_name] Section</a></dt><dt><a href="#id2897534">Print Commands</a></dt><dt><a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2898261">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2898591">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2898740">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2898892">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2899004">Creating the [print$] Share</a></dt><dt><a href="#id2899189">Parameters in the [print$] Section</a></dt><dt><a href="#id2899475">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2899643">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2899736">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2899935">Setting Drivers for existing Printers with
+rpcclient</a></dt></dl></dd><dt><a href="#id2901625">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2901643">The first Client Driver Installation</a></dt><dt><a href="#id2901839">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2902136">Further Client Driver Install Procedures</a></dt><dt><a href="#id2902231">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2902399">Other Gotchas</a></dt><dd><dl><dt><a href="#id2902431">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2902874">Supporting large Numbers of Printers</a></dt><dt><a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2903470">Weird Error Message Cannot connect under a
+different Name</a></dt><dt><a href="#id2903569">Be careful when assembling Driver Files</a></dt><dt><a href="#id2903854">Samba and Printer Ports</a></dt><dt><a href="#id2903932">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2903954">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2903998">What is Imprints?</a></dt><dt><a href="#id2904040">Creating Printer Driver Packages</a></dt><dt><a href="#id2904059">The Imprints Server</a></dt><dt><a href="#id2904083">The Installation Client</a></dt></dl></dd><dt><a href="#id2904236">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2904556">The addprinter command</a></dt><dt><a href="#id2904602">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2904779">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2904793">Common Errors</a></dt><dd><dl><dt><a href="#id2904800">I give my root password but I don't get access</a></dt><dt><a href="#id2904834">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2904970">Introduction</a></dt><dd><dl><dt><a href="#id2904977">Features and Benefits</a></dt><dt><a href="#id2905020">Overview</a></dt></dl></dd><dt><a href="#id2905074">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2905167">Linking of smbd with libcups.so</a></dt><dt><a href="#id2905408">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2905584">More complex smb.conf Settings for
+CUPS</a></dt></dl></dd><dt><a href="#id2905929">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2905949">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2905999">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2906051">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2906119">Explicitly enable "raw" printing for
+application/octet-stream!</a></dt><dt><a href="#id2906306">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2906432">Using CUPS/Samba in an advanced Way -- intelligent printing
+with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2906600">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2907029">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2907154">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2907241">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2907348">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2907370">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2907545">MIME types and CUPS Filters</a></dt><dt><a href="#id2907752">MIME type Conversion Rules</a></dt><dt><a href="#id2907903">Filter Requirements</a></dt><dt><a href="#id2908080">Prefilters</a></dt><dt><a href="#id2908183">pstops</a></dt><dt><a href="#id2908292">pstoraster</a></dt><dt><a href="#id2908476">imagetops and imagetoraster</a></dt><dt><a href="#id2908539">rasterto [printers specific]</a></dt><dt><a href="#id2908691">CUPS Backends</a></dt><dt><a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2909176">The Complete Picture</a></dt><dt><a href="#id2909191">mime.convs</a></dt><dt><a href="#id2909245">"Raw" printing</a></dt><dt><a href="#id2909312">"application/octet-stream" printing</a></dt><dt><a href="#id2909544">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a></dt><dt><a href="#id2910018">Examples for filtering Chains</a></dt><dt><a href="#id2910331">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2910470">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2910560">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2910577">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2910632">Driver Execution on the Client</a></dt><dt><a href="#id2910701">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2910813">Network Printing (Windows clients -- UNIX/Samba Print
+Servers)</a></dt><dd><dl><dt><a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2911043">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2911206">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2911255">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2911328">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2911345">Printer Drivers running in "Kernel Mode" cause many
+Problems</a></dt><dt><a href="#id2911379">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2911400">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2911445">PostScript Drivers with no major problems -- even in Kernel
+Mode</a></dt></dl></dd><dt><a href="#id2911506">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2911524">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2911625">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2912128">Recognize the different Driver Files</a></dt><dt><a href="#id2912268">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2912301">ESP Print Pro Package of "PostScript Driver for
+WinNT/2k/XP"</a></dt><dt><a href="#id2912362">Caveats to be considered</a></dt><dt><a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2912958">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2913117">Understanding cupsaddsmb</a></dt><dt><a href="#id2913264">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2913349">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2913427">cupsaddsmb Flowchart</a></dt><dt><a href="#id2913497">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2913646">Avoiding critical PostScript Driver Settings on the
+Client</a></dt></dl></dd><dt><a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a></dt><dd><dl><dt><a href="#id2913973">A Check of the rpcclient man Page</a></dt><dt><a href="#id2914086">Understanding the rpcclient man page</a></dt><dt><a href="#id2914186">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2914333">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2915566">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2915962">Trivial DataBase Files</a></dt><dt><a href="#id2916041">Binary Format</a></dt><dt><a href="#id2916103">Losing *.tdb Files</a></dt><dt><a href="#id2916162">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2916436">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2917129">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2917602">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2917645">Setting up Quotas</a></dt><dt><a href="#id2917708">Correct and incorrect Accounting</a></dt><dt><a href="#id2917748">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2917829">The page_log File Syntax</a></dt><dt><a href="#id2917938">Possible Shortcomings</a></dt><dt><a href="#id2918010">Future Developments</a></dt><dt><a href="#id2918058">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2918072">Additional Material</a></dt><dt><a href="#id2918267">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2918326">CUPS Configuration Settings explained</a></dt><dt><a href="#id2918407">Pre-conditions</a></dt><dt><a href="#id2918564">Manual Configuration</a></dt></dl></dd><dt><a href="#id2918622">In Case of Trouble.....</a></dt><dt><a href="#id2918682">Printing from CUPS to Windows attached
+Printers</a></dt><dt><a href="#id2918955">More CUPS filtering Chains</a></dt><dt><a href="#id2796634">Common Errors</a></dt><dd><dl><dt><a href="#id2796642">Win9x client can't install driver</a></dt><dt><a href="#id2919061">"cupsaddsmb" keeps asking for root password in
+			neverending loop</a></dt><dt><a href="#id2919107">"cupsaddsmb" gives "No PPD file for printer..."
+			message while PPD file is present</a></dt><dt><a href="#id2919163">Client can't connect to Samba printer</a></dt><dt><a href="#id2919497">Can't reconnect to Samba under new account
+			from Win2K/XP</a></dt><dt><a href="#id2919582">Avoid being connected to the Samba server as the
+		"wrong" user</a></dt><dt><a href="#id2919635">Upgrading to CUPS drivers from Adobe drivers on
+		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2919649">Can't use "cupsaddsmb" on Samba server which is
+		a PDC</a></dt><dt><a href="#id2919678">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2919695">Win2K/XP "Local Security
+		Policies"</a></dt><dt><a href="#id2919711">WinXP clients: "Administrator can not install
+		printers for all local users"</a></dt><dt><a href="#id2919733">"Print Change Notify" functions on
+		NT-clients</a></dt><dt><a href="#id2919752">WinXP-SP1</a></dt><dt><a href="#id2919794">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2920067">Most common blunders in driver
+		settings on Windows clients</a></dt><dt><a href="#id2920114">cupsaddsmb does not work
+		with newly installed printer</a></dt><dt><a href="#id2920175">Permissions on
 /var/spool/samba/ get reset after each
-reboot</a></dt><dt><a href="#id2922615">Printer named "lp"
+reboot</a></dt><dt><a href="#id2920284">Printer named "lp"
 intermittently swallows jobs and spits out completely different
-ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2922701">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2922871">Features and Benefits</a></dt><dt><a href="#id2922889">Discussion</a></dt><dt><a href="#id2923117">Included modules</a></dt><dd><dl><dt><a href="#id2923124">audit</a></dt><dt><a href="#id2923166">extd_audit</a></dt><dt><a href="#id2923296">fake_perms</a></dt><dt><a href="#id2923316">recycle</a></dt><dt><a href="#id2923485">netatalk</a></dt></dl></dd><dt><a href="#id2923530">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2923552">DatabaseFS</a></dt><dt><a href="#id2923606">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2923836">Features and Benefits</a></dt><dt><a href="#id2923931">Introduction</a></dt><dt><a href="#id2924016">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2924076">Target Uses</a></dt></dl></dd><dt><a href="#id2924107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2924136">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2924169">Microsoft Active Directory Services</a></dt><dt><a href="#id2924192">Name Service Switch</a></dt><dt><a href="#id2924320">Pluggable Authentication Modules</a></dt><dt><a href="#id2924402">User and Group ID Allocation</a></dt><dt><a href="#id2924435">Result Caching</a></dt></dl></dd><dt><a href="#id2924463">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2924471">Introduction</a></dt><dt><a href="#id2924538">Requirements</a></dt><dt><a href="#id2924632">Testing Things Out</a></dt></dl></dd><dt><a href="#id2926199">Conclusion</a></dt><dt><a href="#id2926218">Common Errors</a></dt><dd><dl><dt><a href="#id2926270">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2926379">Features and Benefits</a></dt><dt><a href="#id2926410">Remote Server Administration</a></dt><dt><a href="#id2926508">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2926526">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2926738">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2927010">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2927044">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2927123">Features and Benefits</a></dt><dt><a href="#id2927177">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2927288">Windows 9x/Me Policies</a></dt><dt><a href="#id2927384">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2927516">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2927780">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2927886">Samba Editreg Toolset</a></dt><dt><a href="#id2927925">Windows NT4/200x</a></dt><dt><a href="#id2927945">Samba PDC</a></dt></dl></dd><dt><a href="#id2927990">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2928140">Common Errors</a></dt><dd><dl><dt><a href="#id2928154">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2928255">Features and Benefits</a></dt><dt><a href="#id2928289">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2928330">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2928820">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2930060">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2930144">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2930397">Mandatory profiles</a></dt><dt><a href="#id2930455">Creating/Managing Group Profiles</a></dt><dt><a href="#id2930500">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2930520">MS Windows 9x/Me</a></dt><dt><a href="#id2930668">MS Windows NT4 Workstation</a></dt><dt><a href="#id2931222">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2931730">Common Errors</a></dt><dd><dl><dt><a href="#id2931743">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2931812">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2932026">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2932306">Features and Benefits</a></dt><dt><a href="#id2932554">Technical Discussion</a></dt><dd><dl><dt><a href="#id2932572">PAM Configuration Syntax</a></dt><dt><a href="#id2933235">Example System Configurations</a></dt><dt><a href="#id2933539">smb.conf PAM Configuration</a></dt><dt><a href="#id2933617">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2933706">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2934094">Common Errors</a></dt><dd><dl><dt><a href="#id2934108">pam_winbind problem</a></dt><dt><a href="#id2934194">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2934432">Features and Benefits</a></dt><dt><a href="#id2934457">Background Information</a></dt><dt><a href="#id2934521">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2934577">/etc/hosts</a></dt><dt><a href="#id2934718">/etc/resolv.conf</a></dt><dt><a href="#id2934762">/etc/host.conf</a></dt><dt><a href="#id2934813">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2934918">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2935185">The NetBIOS Name Cache</a></dt><dt><a href="#id2935248">The LMHOSTS file</a></dt><dt><a href="#id2935496">HOSTS file</a></dt><dt><a href="#id2935528">DNS Lookup</a></dt><dt><a href="#id2935560">WINS Lookup</a></dt></dl></dd><dt><a href="#id2935678">Common Errors</a></dt><dd><dl><dt><a href="#id2935694">Pinging works only in one way</a></dt><dt><a href="#id2935729">Very Slow Network Connections</a></dt><dt><a href="#id2935780">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2935983">Features and Benefits</a></dt><dt><a href="#id2936027">What are charsets and unicode?</a></dt><dt><a href="#id2936097">Samba and charsets</a></dt><dt><a href="#id2936224">Conversion from old names</a></dt><dt><a href="#id2936254">Japanese charsets</a></dt><dt><a href="#id2936392">Common errors</a></dt><dd><dl><dt><a href="#id2936398">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2936512">Note</a></dt><dt><a href="#id2936526">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2936596">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter�10.�Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878319">Features and Benefits</a></dt><dt><a href="#id2878408">What is Browsing?</a></dt><dt><a href="#id2878720">Discussion</a></dt><dd><dl><dt><a href="#id2878736">NetBIOS over TCP/IP</a></dt><dt><a href="#id2878972">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2879137">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2879284">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2879819">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2880217">Making Samba the domain master</a></dt><dt><a href="#id2880395">Note about broadcast addresses</a></dt><dt><a href="#id2880412">Multiple interfaces</a></dt><dt><a href="#id2880448">Use of the Remote Announce parameter</a></dt><dt><a href="#id2880607">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2880684">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2880872">Setting up a WINS server</a></dt><dt><a href="#id2881128">WINS Replication</a></dt><dt><a href="#id2881154">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2881238">Helpful Hints</a></dt><dd><dl><dt><a href="#id2881252">Windows Networking Protocols</a></dt><dt><a href="#id2881317">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2881481">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2881541">Browsing support in Samba</a></dt><dt><a href="#id2881662">Problem resolution</a></dt><dt><a href="#id2881749">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2882439">Common Errors</a></dt><dd><dl><dt><a href="#id2882454">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2882497">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2882539">I get an Unable to browse the network error</a></dt></dl></dd></dl></div><p>
+ones</a></dt><dt><a href="#id2920314">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2920369">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2920538">Features and Benefits</a></dt><dt><a href="#id2920556">Discussion</a></dt><dt><a href="#id2920786">Included modules</a></dt><dd><dl><dt><a href="#id2920793">audit</a></dt><dt><a href="#id2920835">extd_audit</a></dt><dt><a href="#id2920965">fake_perms</a></dt><dt><a href="#id2920984">recycle</a></dt><dt><a href="#id2921153">netatalk</a></dt></dl></dd><dt><a href="#id2921198">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2921220">DatabaseFS</a></dt><dt><a href="#id2921286">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2921516">Features and Benefits</a></dt><dt><a href="#id2921611">Introduction</a></dt><dt><a href="#id2921688">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2921756">Target Uses</a></dt></dl></dd><dt><a href="#id2921786">How Winbind Works</a></dt><dd><dl><dt><a href="#id2921815">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2921849">Microsoft Active Directory Services</a></dt><dt><a href="#id2921872">Name Service Switch</a></dt><dt><a href="#id2922009">Pluggable Authentication Modules</a></dt><dt><a href="#id2922081">User and Group ID Allocation</a></dt><dt><a href="#id2922128">Result Caching</a></dt></dl></dd><dt><a href="#id2922156">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2922164">Introduction</a></dt><dt><a href="#id2922231">Requirements</a></dt><dt><a href="#id2922333">Testing Things Out</a></dt></dl></dd><dt><a href="#id2923890">Conclusion</a></dt><dt><a href="#id2923909">Common Errors</a></dt><dd><dl><dt><a href="#id2923962">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2924071">Features and Benefits</a></dt><dt><a href="#id2924101">Remote Server Administration</a></dt><dt><a href="#id2924200">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2924218">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2924438">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2924711">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2924744">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2924822">Features and Benefits</a></dt><dt><a href="#id2924888">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2924999">Windows 9x/Me Policies</a></dt><dt><a href="#id2925094">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2925227">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2925491">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2925596">Samba Editreg Toolset</a></dt><dt><a href="#id2925636">Windows NT4/200x</a></dt><dt><a href="#id2925655">Samba PDC</a></dt></dl></dd><dt><a href="#id2925700">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2925851">Common Errors</a></dt><dd><dl><dt><a href="#id2925865">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2925964">Features and Benefits</a></dt><dt><a href="#id2925999">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2926040">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2926530">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2927776">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2927861">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2928114">Mandatory profiles</a></dt><dt><a href="#id2928172">Creating/Managing Group Profiles</a></dt><dt><a href="#id2928216">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2928237">MS Windows 9x/Me</a></dt><dt><a href="#id2928385">MS Windows NT4 Workstation</a></dt><dt><a href="#id2928939">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2929447">Common Errors</a></dt><dd><dl><dt><a href="#id2929460">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2929529">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2929742">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2930024">Features and Benefits</a></dt><dt><a href="#id2930271">Technical Discussion</a></dt><dd><dl><dt><a href="#id2930288">PAM Configuration Syntax</a></dt><dt><a href="#id2930969">Example System Configurations</a></dt><dt><a href="#id2931283">smb.conf PAM Configuration</a></dt><dt><a href="#id2931361">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2931445">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2931826">Common Errors</a></dt><dd><dl><dt><a href="#id2931839">pam_winbind problem</a></dt><dt><a href="#id2931926">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2932164">Features and Benefits</a></dt><dt><a href="#id2932188">Background Information</a></dt><dt><a href="#id2932259">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2932315">/etc/hosts</a></dt><dt><a href="#id2932456">/etc/resolv.conf</a></dt><dt><a href="#id2932499">/etc/host.conf</a></dt><dt><a href="#id2932551">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2932655">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2932922">The NetBIOS Name Cache</a></dt><dt><a href="#id2932985">The LMHOSTS file</a></dt><dt><a href="#id2933234">HOSTS file</a></dt><dt><a href="#id2933266">DNS Lookup</a></dt><dt><a href="#id2933298">WINS Lookup</a></dt></dl></dd><dt><a href="#id2933416">Common Errors</a></dt><dd><dl><dt><a href="#id2933432">Pinging works only in one way</a></dt><dt><a href="#id2933465">Very Slow Network Connections</a></dt><dt><a href="#id2933517">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2933721">Features and Benefits</a></dt><dt><a href="#id2933765">What are charsets and unicode?</a></dt><dt><a href="#id2933835">Samba and charsets</a></dt><dt><a href="#id2933962">Conversion from old names</a></dt><dt><a href="#id2933992">Japanese charsets</a></dt><dt><a href="#id2934130">Common errors</a></dt><dd><dl><dt><a href="#id2934137">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2934250">Note</a></dt><dt><a href="#id2934264">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2934334">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter�10.�Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2875816">Features and Benefits</a></dt><dt><a href="#id2875904">What is Browsing?</a></dt><dt><a href="#id2876217">Discussion</a></dt><dd><dl><dt><a href="#id2876233">NetBIOS over TCP/IP</a></dt><dt><a href="#id2876469">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2876635">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2876781">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877309">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2877716">Making Samba the domain master</a></dt><dt><a href="#id2877893">Note about broadcast addresses</a></dt><dt><a href="#id2877911">Multiple interfaces</a></dt><dt><a href="#id2877946">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878104">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878182">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878371">Setting up a WINS server</a></dt><dt><a href="#id2878627">WINS Replication</a></dt><dt><a href="#id2878652">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2878737">Helpful Hints</a></dt><dd><dl><dt><a href="#id2878750">Windows Networking Protocols</a></dt><dt><a href="#id2878822">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2878986">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879046">Browsing support in Samba</a></dt><dt><a href="#id2879168">Problem resolution</a></dt><dt><a href="#id2879254">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2879936">Common Errors</a></dt><dd><dl><dt><a href="#id2879950">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2879979">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880021">I get an Unable to browse the network error</a></dt></dl></dd></dl></div><p>
 This document contains detailed information as well as a fast track guide to
 implementing browsing across subnets and / or across workgroups (or domains).
 WINS is the best tool for resolution of NetBIOS names to IP addresses. WINS is
@@ -2151,11 +2151,11 @@ over TCP/IP. Samba-3 and later also supports this mode of operation.
 When the use of NetBIOS over TCP/IP has been disabled then the primary
 means for resolution of MS Windows machine names is via DNS and Active Directory.
 The following information assumes that your site is running NetBIOS over TCP/IP.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878319"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875816"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Someone once referred to the past in terms of: <span class="emphasis"><em>They were the worst of times,
 they were the best of times. The more we look back, them more we long for what was and
 hope it never returns!</em></span>.
-</p><a class="indexterm" name="id2878340"></a><p>
+</p><a class="indexterm" name="id2875837"></a><p>
 For many MS Windows network administrators, that statement sums up their feelings about
 NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle
 nature was just par for the course. For those who never quite managed to tame its
@@ -2184,7 +2184,7 @@ support for NetBIOS, in which case WINS is of no relevance. Samba supports this
 </p><p>
 For those networks on which NetBIOS has been disabled (ie: WINS is NOT required)
 the use of DNS is necessary for host name resolution.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878408"></a>What is Browsing?</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875904"></a>What is Browsing?</h2></div></div><div></div></div><p>
 To most people browsing means that they can see the MS Windows and Samba servers
 in the Network Neighborhood, and when the computer icon for a particular server is
 clicked, it opens up and shows the shares and printers available on the target server.
@@ -2194,41 +2194,41 @@ The technologies (or methods) employed in making all of this work includes:
 </p><div class="itemizedlist"><ul type="disc"><li><p>MS Windows machines register their presence to the network</p></li><li><p>Machines announce themselves to other machines on the network</p></li><li><p>One or more machine on the network collates the local announcements</p></li><li><p>The client machine finds the machine that has the collated list of machines</p></li><li><p>The client machine is able to resolve the machine names to IP addresses</p></li><li><p>The client machine is able to connect to a target machine</p></li></ul></div><p>
 The Samba application that controls browse list management and name resolution is
 called <tt class="filename">nmbd</tt>. The configuration parameters involved in nmbd's operation are:
-</p><p>Browsing options: <a class="indexterm" name="id2878491"></a><i class="parameter"><tt>os level</tt></i>(*),
-	<a class="indexterm" name="id2878505"></a><i class="parameter"><tt>lm announce</tt></i>,
-	<a class="indexterm" name="id2878519"></a><i class="parameter"><tt>lm interval</tt></i>,
-	<a class="indexterm" name="id2878532"></a><i class="parameter"><tt>preferred master</tt></i>(*),
-	<a class="indexterm" name="id2878547"></a><i class="parameter"><tt>local master</tt></i>(*),
-	<a class="indexterm" name="id2878561"></a><i class="parameter"><tt>domain master</tt></i>(*),
-	<a class="indexterm" name="id2878575"></a><i class="parameter"><tt>browse list</tt></i>,
-	<a class="indexterm" name="id2878588"></a><i class="parameter"><tt>enhanced browsing</tt></i>.
+</p><p>Browsing options: <a class="indexterm" name="id2875988"></a><i class="parameter"><tt>os level</tt></i>(*),
+	<a class="indexterm" name="id2876002"></a><i class="parameter"><tt>lm announce</tt></i>,
+	<a class="indexterm" name="id2876016"></a><i class="parameter"><tt>lm interval</tt></i>,
+	<a class="indexterm" name="id2876030"></a><i class="parameter"><tt>preferred master</tt></i>(*),
+	<a class="indexterm" name="id2876044"></a><i class="parameter"><tt>local master</tt></i>(*),
+	<a class="indexterm" name="id2876058"></a><i class="parameter"><tt>domain master</tt></i>(*),
+	<a class="indexterm" name="id2876072"></a><i class="parameter"><tt>browse list</tt></i>,
+	<a class="indexterm" name="id2876085"></a><i class="parameter"><tt>enhanced browsing</tt></i>.
 </p><p>Name Resolution Method:
-	<a class="indexterm" name="id2878607"></a><i class="parameter"><tt>name resolve order</tt></i>(*).
+	<a class="indexterm" name="id2876103"></a><i class="parameter"><tt>name resolve order</tt></i>(*).
 </p><p>WINS options:
-	<a class="indexterm" name="id2878625"></a><i class="parameter"><tt>dns proxy</tt></i>,
-	<a class="indexterm" name="id2878639"></a><i class="parameter"><tt>wins proxy</tt></i>,
-	<a class="indexterm" name="id2878652"></a><i class="parameter"><tt>wins server</tt></i>(*),
-	<a class="indexterm" name="id2878666"></a><i class="parameter"><tt>wins support</tt></i>(*),
-	<a class="indexterm" name="id2878680"></a><i class="parameter"><tt>wins hook</tt></i>.
-</p><a class="indexterm" name="id2878696"></a><p>
+	<a class="indexterm" name="id2876122"></a><i class="parameter"><tt>dns proxy</tt></i>,
+	<a class="indexterm" name="id2876136"></a><i class="parameter"><tt>wins proxy</tt></i>,
+	<a class="indexterm" name="id2876150"></a><i class="parameter"><tt>wins server</tt></i>(*),
+	<a class="indexterm" name="id2876163"></a><i class="parameter"><tt>wins support</tt></i>(*),
+	<a class="indexterm" name="id2876178"></a><i class="parameter"><tt>wins hook</tt></i>.
+</p><a class="indexterm" name="id2876193"></a><p>
 For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with
 an '*' are the only options that commonly MAY need to be modified. Even if not one of these
 parameters is set <tt class="filename">nmbd</tt> will still do it's job.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878720"></a>Discussion</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876217"></a>Discussion</h2></div></div><div></div></div><p>
 Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging.
 SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports
 NetBIOS over TCP/IP for backwards compatibility. Microsoft is intent on phasing out NetBIOS
 support.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878736"></a>NetBIOS over TCP/IP</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876233"></a>NetBIOS over TCP/IP</h3></div></div><div></div></div><p>
 Samba implements NetBIOS, as does MS Windows NT / 200x / XP, by encapsulating it over TCP/IP.
 MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to
 affect browse list management. When running NetBIOS over TCP/IP, this uses UDP based messaging.
 UDP messages can be broadcast or unicast.
-</p><a class="indexterm" name="id2878754"></a><p>
+</p><a class="indexterm" name="id2876251"></a><p>
 Normally, only unicast UDP messaging can be forwarded by routers. The
-<a class="indexterm" name="id2878766"></a><i class="parameter"><tt>remote announce</tt></i> parameter to smb.conf helps to project browse announcements
+<a class="indexterm" name="id2876262"></a><i class="parameter"><tt>remote announce</tt></i> parameter to smb.conf helps to project browse announcements
 to remote network segments via unicast UDP. Similarly, the 
-<a class="indexterm" name="id2878783"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of <tt class="filename">smb.conf</tt>
+<a class="indexterm" name="id2876280"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of <tt class="filename">smb.conf</tt>
 implements browse list collation using unicast UDP.
 </p><p>
 Secondly, in those networks where Samba is the only SMB server technology,
@@ -2236,13 +2236,13 @@ wherever possible <tt class="filename">nmbd</tt> should be configured on one (1)
 server. This makes it easy to manage the browsing environment. If each network
 segment is configured with it's own Samba WINS server, then the only way to
 get cross segment browsing to work is by using the 
-<a class="indexterm" name="id2878822"></a><i class="parameter"><tt>remote announce</tt></i> and the <a class="indexterm" name="id2878836"></a><i class="parameter"><tt>remote browse sync</tt></i>
+<a class="indexterm" name="id2876319"></a><i class="parameter"><tt>remote announce</tt></i> and the <a class="indexterm" name="id2876333"></a><i class="parameter"><tt>remote browse sync</tt></i>
 parameters to your <tt class="filename">smb.conf</tt> file.
 </p><p>
-<a class="indexterm" name="id2878861"></a>
+<a class="indexterm" name="id2876359"></a>
 If only one WINS server is used for an entire multi-segment network then
-the use of the <a class="indexterm" name="id2878871"></a><i class="parameter"><tt>remote announce</tt></i> and the 
-<a class="indexterm" name="id2878885"></a><i class="parameter"><tt>remote browse sync</tt></i> parameters should NOT be necessary.
+the use of the <a class="indexterm" name="id2876368"></a><i class="parameter"><tt>remote announce</tt></i> and the 
+<a class="indexterm" name="id2876382"></a><i class="parameter"><tt>remote browse sync</tt></i> 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. This is NOT a supported feature
@@ -2253,7 +2253,7 @@ Right now Samba WINS does not support MS-WINS replication. This means that
 when setting up Samba as a WINS server there must only be one <tt class="filename">nmbd</tt>
 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 
-<a class="indexterm" name="id2878925"></a><i class="parameter"><tt>remote browse sync</tt></i> and <a class="indexterm" name="id2878939"></a><i class="parameter"><tt>remote announce</tt></i>
+<a class="indexterm" name="id2876422"></a><i class="parameter"><tt>remote browse sync</tt></i> and <a class="indexterm" name="id2876436"></a><i class="parameter"><tt>remote announce</tt></i>
 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
@@ -2264,10 +2264,10 @@ Lastly, take note that browse lists are a collection of unreliable broadcast
 messages that are repeated at intervals of not more than 15 minutes. This means
 that it will take time to establish a browse list and it can take up to 45
 minutes to stabilise, particularly across network segments.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878972"></a>TCP/IP - without NetBIOS</h3></div></div><div></div></div><p>
-<a class="indexterm" name="id2878983"></a>
-<a class="indexterm" name="id2878991"></a>
-<a class="indexterm" name="id2879000"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876469"></a>TCP/IP - without NetBIOS</h3></div></div><div></div></div><p>
+<a class="indexterm" name="id2876480"></a>
+<a class="indexterm" name="id2876488"></a>
+<a class="indexterm" name="id2876497"></a>
 All TCP/IP using systems use various forms of host name resolution. The primary
 methods for TCP/IP hostname resolutions involves either a static file (<tt class="filename">/etc/hosts
 </tt>) or DNS (the Domain Name System). DNS is the technology that makes
@@ -2290,7 +2290,7 @@ it follows a defined path:
         </p></li><li><p>
 	Looks up entries in LMHOSTS. It is located in
         <tt class="filename">C:\WinNT\System32\Drivers\etc</tt>.
-        </p></li></ol></div><a class="indexterm" name="id2879097"></a><p>
+        </p></li></ol></div><a class="indexterm" name="id2876594"></a><p>
 Windows 200x / XP can register it's host name with a Dynamic DNS server. You can
 force register with a Dynamic DNS server in Windows 200x / XP using:
 <b class="command">ipconfig /registerdns</b>
@@ -2303,7 +2303,7 @@ consequently network services will be severely impaired.
 The use of Dynamic DNS is highly recommended with Active Directory, in which case
 the use of BIND9 is preferred for it's ability to adequately support the SRV (service)
 records that are needed for Active Directory.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879137"></a>DNS and Active Directory</h3></div></div><div></div></div><a class="indexterm" name="id2879145"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876635"></a>DNS and Active Directory</h3></div></div><div></div></div><a class="indexterm" name="id2876642"></a><p>
 Occasionally we hear from UNIX network administrators who want to use a UNIX based Dynamic
 DNS server in place of the Microsoft DNS server. While this might be desirable to some, the
 MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible
@@ -2325,7 +2325,7 @@ The following are some of the default service records that Active Directory requ
                 </p></li><li><p>_ldap._tcp.<span class="emphasis"><em>Site</em></span>.gc.ms-dcs.<span class="emphasis"><em>DomainTree</em></span></p><p>
 		Used by MS Windows clients to locate site configuration dependent
 		Global Catalog server.
-		</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879284"></a>How Browsing Functions</h2></div></div><div></div></div><p>
+		</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876781"></a>How Browsing Functions</h2></div></div><div></div></div><p>
 MS Windows machines register their NetBIOS names 
 (ie: the machine name for each service type in operation) on start 
 up. The exact method by which this name registration 
@@ -2339,7 +2339,7 @@ resolution to the local subnet, unless LMHOSTS is used to list all
 names and IP addresses. In such situations Samba provides a means by 
 which the Samba server name may be forcibly injected into the browse 
 list of a remote MS Windows network (using the 
-<a class="indexterm" name="id2879321"></a><i class="parameter"><tt>remote announce</tt></i> parameter).
+<a class="indexterm" name="id2876810"></a><i class="parameter"><tt>remote announce</tt></i> parameter).
 </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 
@@ -2367,12 +2367,12 @@ will annoy users because they will have to put up with protracted
 inability to use the network services.
 </p><p>
 Samba supports a feature that allows forced synchronisation 
-of browse lists across routed networks using the <a class="indexterm" name="id2879384"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. 
+of browse lists across routed networks using the <a class="indexterm" name="id2876873"></a><i class="parameter"><tt>remote browse sync</tt></i> 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 <a class="indexterm" name="id2879412"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter provides browse list synchronisation - and 
+based name resolution, but it should be noted that the <a class="indexterm" name="id2876902"></a><i class="parameter"><tt>remote browse sync</tt></i> 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. 
@@ -2403,7 +2403,7 @@ The domain master browser should also preferably be the local master
 browser for its own subnet.  In order to achieve this set the following
 options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file :
 </p><p>
-	</p><div class="example"><a name="id2879534"></a><p class="title"><b>Example�10.1.�Domain master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
+	</p><div class="example"><a name="id2877023"></a><p class="title"><b>Example�10.1.�Domain master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
 </p><p>
 The domain master browser may be the same machine as the WINS
 server, if you require.
@@ -2417,15 +2417,15 @@ to use these).  To make a Samba server a local master browser
 set the following options in the <i class="parameter"><tt>[global]</tt></i> section of the
 <tt class="filename">smb.conf</tt> file :
 </p><p>
-</p><div class="example"><a name="id2879624"></a><p class="title"><b>Example�10.2.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2877114"></a><p class="title"><b>Example�10.2.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
 </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 <a class="indexterm" name="id2879690"></a><i class="parameter"><tt>local master</tt></i> parameter allows Samba to act as a
-local master browser.  The <a class="indexterm" name="id2879707"></a><i class="parameter"><tt>preferred master</tt></i> causes nmbd
-to force a browser election on startup and the <a class="indexterm" name="id2879722"></a><i class="parameter"><tt>os level</tt></i>
+The <a class="indexterm" name="id2877180"></a><i class="parameter"><tt>local master</tt></i> parameter allows Samba to act as a
+local master browser.  The <a class="indexterm" name="id2877196"></a><i class="parameter"><tt>preferred master</tt></i> causes nmbd
+to force a browser election on startup and the <a class="indexterm" name="id2877212"></a><i class="parameter"><tt>os level</tt></i>
 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
@@ -2434,8 +2434,8 @@ becoming a local master browser by setting the following
 options in the <i class="parameter"><tt>[global]</tt></i> section of the 
 <tt class="filename">smb.conf</tt> file :
 </p><p>
-</p><div class="example"><a name="id2879762"></a><p class="title"><b>Example�10.3.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879819"></a>Setting up DOMAIN Browsing</h3></div></div><div></div></div><p>
+</p><div class="example"><a name="id2877252"></a><p class="title"><b>Example�10.3.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877309"></a>Setting up DOMAIN Browsing</h3></div></div><div></div></div><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
@@ -2450,10 +2450,10 @@ described.  To make a Samba server a local master browser set
 the following options in the <i class="parameter"><tt>[global]</tt></i> section 
 of the <tt class="filename">smb.conf</tt> file :
 </p><p>
-	</p><div class="example"><a name="id2879868"></a><p class="title"><b>Example�10.4.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
+	</p><div class="example"><a name="id2877358"></a><p class="title"><b>Example�10.4.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p>
 </p><p>
 If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the <a class="indexterm" name="id2879929"></a><i class="parameter"><tt>os level</tt></i> parameter
+on the same subnet you may set the <a class="indexterm" name="id2877419"></a><i class="parameter"><tt>os level</tt></i> 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" title="Forcing Samba to be the master">
@@ -2467,7 +2467,7 @@ ever becoming a local master browser by setting following options
 in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt>
 file :
 </p><p>
-</p><div class="example"><a name="id2879985"></a><p class="title"><b>Example�10.5.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2877475"></a><p class="title"><b>Example�10.5.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p>
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="browse-force-master"></a>Forcing Samba to be the master</h3></div></div><div></div></div><p>
 Who becomes the master browser is determined by an election
 process using broadcasts.  Each election packet contains a number of parameters
@@ -2475,25 +2475,25 @@ 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 <a class="indexterm" name="id2880069"></a><i class="parameter"><tt>os level</tt></i> global
+If you want Samba to win elections then just set the <a class="indexterm" name="id2877559"></a><i class="parameter"><tt>os level</tt></i> 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 <a class="indexterm" name="id2880096"></a><i class="parameter"><tt>os level</tt></i> of 2 would make it beat WfWg and Win95, but not MS Windows
+A <a class="indexterm" name="id2877585"></a><i class="parameter"><tt>os level</tt></i> 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
-<a class="indexterm" name="id2880121"></a><i class="parameter"><tt>preferred master</tt></i> global option in <tt class="filename">smb.conf</tt> to <tt class="constant">yes</tt>.  Samba will
+<a class="indexterm" name="id2877610"></a><i class="parameter"><tt>preferred master</tt></i> global option in <tt class="filename">smb.conf</tt> to <tt class="constant">yes</tt>.  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 <a class="indexterm" name="id2880151"></a><i class="parameter"><tt>preferred master</tt></i> to
+Samba) on the same local subnet both set with <a class="indexterm" name="id2877641"></a><i class="parameter"><tt>preferred master</tt></i> to
 <tt class="constant">yes</tt>, 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 <span class="emphasis"><em>domain master browser</em></span>, then it is
-recommended that you also set <a class="indexterm" name="id2880180"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, because
+recommended that you also set <a class="indexterm" name="id2877670"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, 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.
@@ -2505,10 +2505,10 @@ attempt to become the domain master browser every 5 minutes.  They
 will find that another Samba server is already the domain master
 browser and will fail.  This provides automatic redundancy, should
 the current domain master browser fail.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880217"></a>Making Samba the domain master</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877716"></a>Making Samba the domain master</h3></div></div><div></div></div><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 <a class="indexterm" name="id2880231"></a><i class="parameter"><tt>domain master</tt></i> = yes
+make Samba act as the domain master by setting <a class="indexterm" name="id2877730"></a><i class="parameter"><tt>domain master</tt></i> = yes
 in <tt class="filename">smb.conf</tt>.  By default it will not be a domain master.
 </p><p>
 Note that you should <span class="emphasis"><em>not</em></span> set Samba to be the domain master for a
@@ -2520,8 +2520,8 @@ 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 <a class="indexterm" name="id2880277"></a><i class="parameter"><tt>os level</tt></i> high enough to make sure it wins elections, and set
-<a class="indexterm" name="id2880292"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, to get Samba to force an election on
+the <a class="indexterm" name="id2877774"></a><i class="parameter"><tt>os level</tt></i> high enough to make sure it wins elections, and set
+<a class="indexterm" name="id2877790"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, to get Samba to force an election on
 startup.
 </p><p>
 Note that all your servers (including Samba) and clients should be
@@ -2547,20 +2547,20 @@ If, however, both Samba and your clients are using a WINS server, then:
 	resolve the NetBIOS name of that host.  as long as that host has
 	registered its NetBIOS name with the same WINS server, the user will
 	be able to see that host.  
-	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880395"></a>Note about broadcast addresses</h3></div></div><div></div></div><p>
+	</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877893"></a>Note about broadcast addresses</h3></div></div><div></div></div><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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880412"></a>Multiple interfaces</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877911"></a>Multiple interfaces</h3></div></div><div></div></div><p>
 Samba now supports machines with multiple network interfaces.  If you
-have multiple interfaces then you will need to use the <a class="indexterm" name="id2880425"></a><i class="parameter"><tt>interfaces</tt></i>
+have multiple interfaces then you will need to use the <a class="indexterm" name="id2877922"></a><i class="parameter"><tt>interfaces</tt></i>
 option in <tt class="filename">smb.conf</tt> to configure them. 
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880448"></a>Use of the Remote Announce parameter</h3></div></div><div></div></div><p>
-The <a class="indexterm" name="id2880458"></a><i class="parameter"><tt>remote announce</tt></i> parameter of 
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877946"></a>Use of the Remote Announce parameter</h3></div></div><div></div></div><p>
+The <a class="indexterm" name="id2877956"></a><i class="parameter"><tt>remote announce</tt></i> 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 <a class="indexterm" name="id2880482"></a><i class="parameter"><tt>remote announce</tt></i> parameter is:
+The syntax of the <a class="indexterm" name="id2877981"></a><i class="parameter"><tt>remote announce</tt></i> parameter is:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote announce = a.b.c.d [e.f.g.h] ...</tt></i></td></tr></table><p>
 <span class="emphasis"><em>or</em></span>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</tt></i></td></tr></table><p>
@@ -2568,8 +2568,8 @@ The syntax of the <a class="indexterm" name="id2880482"></a><i class="parameter"
 where:
 </p><div class="variablelist"><dl><dt><span class="term"><i class="replaceable"><tt>a.b.c.d</tt></i> and 
 <i class="replaceable"><tt>e.f.g.h</tt></i></span></dt><dd><p>
-		<a class="indexterm" name="id2880552"></a>
-<a class="indexterm" name="id2880563"></a>
+		<a class="indexterm" name="id2878051"></a>
+<a class="indexterm" name="id2878062"></a>
 
 		is either the LMB (Local Master Browser) IP address
 or the broadcast address of the remote network.
@@ -2587,20 +2587,20 @@ NetBIOS machine names will end up looking like
 they belong to that workgroup, this may cause
 name resolution problems and should be avoided.
 </p></dd></dl></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880607"></a>Use of the Remote Browse Sync parameter</h3></div></div><div></div></div><p>
-The <a class="indexterm" name="id2880617"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of 
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878104"></a>Use of the Remote Browse Sync parameter</h3></div></div><div></div></div><p>
+The <a class="indexterm" name="id2878115"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of 
 <tt class="filename">smb.conf</tt> is used to announce to
 another LMB that it must synchronise its NetBIOS name list with our
 Samba LMB. It works ONLY if the Samba server that has this option is
 simultaneously the LMB on its network segment.
 </p><p>
-The syntax of the <a class="indexterm" name="id2880646"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter is:
+The syntax of the <a class="indexterm" name="id2878144"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter is:
 
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote browse sync = a.b.c.d</tt></i></td></tr></table><p>
 
 where <i class="replaceable"><tt>a.b.c.d</tt></i> is either the IP address of the
 remote LMB or else is the network broadcast address of the remote segment.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880684"></a>WINS - The Windows Internetworking Name Server</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878182"></a>WINS - The Windows Internetworking Name Server</h2></div></div><div></div></div><p>
 Use of WINS (either Samba WINS <span class="emphasis"><em>or</em></span> MS Windows NT Server WINS) is highly
 recommended. Every NetBIOS machine registers its name together with a
 name_type value for each of several types of service it has available.
@@ -2641,17 +2641,17 @@ lookup attempts by other clients and will therefore cause workstation access
 errors.
 </p><p>
 To configure Samba as a WINS server just add 
-<a class="indexterm" name="id2880774"></a><i class="parameter"><tt>wins support</tt></i> = yes to the <tt class="filename">smb.conf</tt>
+<a class="indexterm" name="id2878272"></a><i class="parameter"><tt>wins support</tt></i> = yes to the <tt class="filename">smb.conf</tt>
 file [global] section.
 </p><p>
 To configure Samba to register with a WINS server just add
-<a class="indexterm" name="id2880801"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d to your <tt class="filename">smb.conf</tt> file <i class="parameter"><tt>[global]</tt></i> section.
+<a class="indexterm" name="id2878300"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d to your <tt class="filename">smb.conf</tt> file <i class="parameter"><tt>[global]</tt></i> section.
 </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
-Never use both <a class="indexterm" name="id2880833"></a><i class="parameter"><tt>wins support</tt></i> = yes together
-with <a class="indexterm" name="id2880849"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d
+Never use both <a class="indexterm" name="id2878332"></a><i class="parameter"><tt>wins support</tt></i> = yes together
+with <a class="indexterm" name="id2878348"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d
 particularly not using it's own IP address.
 Specifying both will cause <span class="application">nmbd</span> to refuse to start!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880872"></a>Setting up a WINS server</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878371"></a>Setting up a WINS server</h3></div></div><div></div></div><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 :
@@ -2664,11 +2664,11 @@ 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 <a class="indexterm" name="id2880931"></a><i class="parameter"><tt>wins support</tt></i> = yes will keep a list of 
+Machines with <a class="indexterm" name="id2878430"></a><i class="parameter"><tt>wins support</tt></i> = yes 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
-<a class="indexterm" name="id2880953"></a><i class="parameter"><tt>wins support</tt></i> = yes option on more than one Samba 
+<a class="indexterm" name="id2878452"></a><i class="parameter"><tt>wins support</tt></i> = yes 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
@@ -2680,7 +2680,7 @@ participate in these replications.  It is possible in the future that
 a Samba-&gt;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 
-<a class="indexterm" name="id2880988"></a><i class="parameter"><tt>wins support</tt></i> = yes parameter set.
+<a class="indexterm" name="id2878487"></a><i class="parameter"><tt>wins support</tt></i> = yes parameter set.
 </p><p>
 After the WINS server has been configured you must ensure that all
 machines participating on the network are configured with the address
@@ -2698,8 +2698,8 @@ 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
-<a class="indexterm" name="id2881086"></a><i class="parameter"><tt>wins support</tt></i> = yes option and the 
-<a class="indexterm" name="id2881101"></a><i class="parameter"><tt>wins server</tt></i> = &lt;name&gt; option then
+<a class="indexterm" name="id2878585"></a><i class="parameter"><tt>wins support</tt></i> = yes option and the 
+<a class="indexterm" name="id2878600"></a><i class="parameter"><tt>wins server</tt></i> = &lt;name&gt; option then
 nmbd will fail to start.
 </p><p>
 There are two possible scenarios for setting up cross subnet browsing.
@@ -2707,12 +2707,12 @@ 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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881128"></a>WINS Replication</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878627"></a>WINS Replication</h3></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881154"></a>Static WINS Entries</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878652"></a>Static WINS Entries</h3></div></div><div></div></div><p>
 Adding static entries to your Samba WINS server is actually fairly easy.
 All you have to do is add a line to <tt class="filename">wins.dat</tt>, typically
 located in <tt class="filename">/usr/local/samba/var/locks</tt>.
@@ -2742,10 +2742,10 @@ To make it static, all that has to be done is set the TTL to 0:
 Though this method works with early Samba-3 versions, there's a
 possibility that it may change in future versions if WINS replication
 is added.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2881238"></a>Helpful Hints</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878737"></a>Helpful Hints</h2></div></div><div></div></div><p>
 The following hints should be carefully considered as they are stumbling points
 for many new network administrators.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881252"></a>Windows Networking Protocols</h3></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878750"></a>Windows Networking Protocols</h3></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 Do NOT use more than one (1) protocol on MS Windows machines
 </p></div><p>
 A very common cause of browsing problems results from installing more than
@@ -2775,7 +2775,7 @@ 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.
 </em></span></p><p>
 The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881317"></a>Name Resolution Order</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878822"></a>Name Resolution Order</h3></div></div><div></div></div><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:
@@ -2793,9 +2793,9 @@ The default is:
 where "host" refers to 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="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2881481"></a>Technical Overview of browsing</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878986"></a>Technical Overview of browsing</h2></div></div><div></div></div><p>
 SMB networking provides a mechanism by which clients can access a list
-of machines in a network, a so-called <a class="indexterm" name="id2881493"></a><i class="parameter"><tt>browse list</tt></i>.  This list
+of machines in a network, a so-called <a class="indexterm" name="id2878999"></a><i class="parameter"><tt>browse list</tt></i>.  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
@@ -2813,7 +2813,7 @@ Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
 recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
 WINS allows remote segment clients to obtain NetBIOS name_type information
 that can NOT be provided by any other means of name resolution.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881541"></a>Browsing support in Samba</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879046"></a>Browsing support in Samba</h3></div></div><div></div></div><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
@@ -2840,15 +2840,15 @@ WINS server capabilities.  In a Samba-only environment, it is
 recommended that you use one and only one Samba server as your WINS server.
 </p></div><p>
 To get browsing to work you need to run nmbd as usual, but will need
-to use the <a class="indexterm" name="id2881609"></a><i class="parameter"><tt>workgroup</tt></i> option in <tt class="filename">smb.conf</tt>
+to use the <a class="indexterm" name="id2879114"></a><i class="parameter"><tt>workgroup</tt></i> 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 <a class="indexterm" name="id2881639"></a><i class="parameter"><tt>remote announce</tt></i> in the 
+example.  See <a class="indexterm" name="id2879144"></a><i class="parameter"><tt>remote announce</tt></i> in the 
 <tt class="filename">smb.conf</tt> man page.  
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881662"></a>Problem resolution</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879168"></a>Problem resolution</h3></div></div><div></div></div><p>
 If something doesn't work then hopefully the log.nmbd file will help
 you track down the problem.  Try a debug level of 2 or 3 for finding
 problems. Also note that the current browse list usually gets stored
@@ -2859,7 +2859,7 @@ 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
-<a class="indexterm" name="id2881704"></a><i class="parameter"><tt>guest account</tt></i> set to a valid account.  Remember that the
+<a class="indexterm" name="id2879209"></a><i class="parameter"><tt>guest account</tt></i> 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"><em>
@@ -2873,7 +2873,7 @@ server resources.
 The other big problem people have is that their broadcast address,
 netmask or IP address is wrong (specified with the "interfaces" option
 in <tt class="filename">smb.conf</tt>)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881749"></a>Browsing across subnets</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879254"></a>Browsing across subnets</h3></div></div><div></div></div><p>
 Since the release of Samba 1.9.17(alpha1), Samba has supported the
 replication of browse lists across subnet boundaries. This section
 describes how to set this feature up in different settings.
@@ -2894,7 +2894,7 @@ 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="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881798"></a>How does cross subnet browsing work ?</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2879303"></a>How does cross subnet browsing work ?</h4></div></div><div></div></div><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.
@@ -2943,7 +2943,7 @@ At this point the browse lists look as follows (these are
 the machines you would see in your network neighborhood if
 you looked in it on a particular network right now).
 </p><p>
-</p><div class="table"><a name="id2881940"></a><p class="title"><b>Table�10.1.�Browse subnet example 1</b></p><table summary="Browse subnet example 1" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p>
+</p><div class="table"><a name="id2879437"></a><p class="title"><b>Table�10.1.�Browse subnet example 1</b></p><table summary="Browse subnet example 1" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p>
 </p><p>
 Note that at this point all the subnets are separate, no
 machine is seen across any of the subnets.
@@ -2965,7 +2965,7 @@ 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>
-</p><div class="table"><a name="id2882053"></a><p class="title"><b>Table�10.2.�Browse subnet example 2</b></p><table summary="Browse subnet example 2" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E,
+</p><div class="table"><a name="id2879550"></a><p class="title"><b>Table�10.2.�Browse subnet example 2</b></p><table summary="Browse subnet example 2" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E,
 N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), 
 N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p>
 
@@ -2982,7 +2982,7 @@ 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>
-</p><div class="table"><a name="id2882166"></a><p class="title"><b>Table�10.3.�Browse subnet example 3</b></p><table summary="Browse subnet example 3" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E, 
+</p><div class="table"><a name="id2879662"></a><p class="title"><b>Table�10.3.�Browse subnet example 3</b></p><table summary="Browse subnet example 3" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">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(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), 
 N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">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(*)</td></tr></tbody></table></div><p>
@@ -2998,7 +2998,7 @@ with the domain master browser (N1_C) and will receive the missing
 server entries.  Finally - and as a steady state (if no machines
 are removed or shut off) the browse lists will look like :
 </p><p>
-</p><div class="table"><a name="id2882283"></a><p class="title"><b>Table�10.4.�Browse subnet example 4</b></p><table summary="Browse subnet example 4" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E,
+</p><div class="table"><a name="id2879779"></a><p class="title"><b>Table�10.4.�Browse subnet example 4</b></p><table summary="Browse subnet example 4" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">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(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), 
 N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), 
@@ -3025,11 +3025,11 @@ If either router R1 or R2 fails the following will occur:
 	be able to access servers on its local subnet, by using subnet-isolated
 	broadcast NetBIOS name resolution.  The effects are similar to that of
 	losing access to a DNS server.
-	</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882439"></a>Common Errors</h2></div></div><div></div></div><p>
+	</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879936"></a>Common Errors</h2></div></div><div></div></div><p>
 Many questions are asked on the mailing lists regarding browsing. The majority of browsing
 problems originate out of incorrect configuration of NetBIOS name resolution. Some are of
 particular note.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882454"></a>How can one flush the Samba NetBIOS name cache without restarting Samba?</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879950"></a>How can one flush the Samba NetBIOS name cache without restarting Samba?</h3></div></div><div></div></div><p>
 Samba's nmbd process controls all browse list handling. Under normal circumstances it is
 safe to restart nmbd. This will effectively flush the Samba NetBIOS name cache and cause it
 to be rebuilt. Note that this does NOT make certain that a rogue machine name will not re-appear
@@ -3039,14 +3039,14 @@ want to clear a rogue machine from the list then every machine on the network wi
 shut down and restarted at after all machines are down. Failing a complete restart, the only
 other thing you can do is wait until the entry times out and is then flushed from the list.
 This may take a long time on some networks (months).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882497"></a>My client reports "This server is not configured to list shared resources"</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879979"></a>My client reports "This server is not configured to list shared resources"</h3></div></div><div></div></div><p>
 Your guest account is probably invalid for some reason. Samba uses the
 guest account for browsing in smbd.  Check that your guest account is
 valid.
-</p><p>See also <a class="indexterm" name="id2882516"></a><i class="parameter"><tt>guest account</tt></i> in the <tt class="filename">smb.conf</tt> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882539"></a>I get an <span class="errorname">Unable to browse the network</span> error</h3></div></div><div></div></div><p>This error can have multiple causes:</p><div class="itemizedlist"><ul type="disc"><li><p>There is no local master browser. Configure <span class="application">nmbd</span> 
+</p><p>See also <a class="indexterm" name="id2879997"></a><i class="parameter"><tt>guest account</tt></i> in the <tt class="filename">smb.conf</tt> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880021"></a>I get an <span class="errorname">Unable to browse the network</span> error</h3></div></div><div></div></div><p>This error can have multiple causes:</p><div class="itemizedlist"><ul type="disc"><li><p>There is no local master browser. Configure <span class="application">nmbd</span> 
 			or any other machine to serve as local master browser.</p></li><li><p>You can not log onto the machine that is the local master 
 			browser. Can you logon to it as guest user? </p></li><li><p>There is no IP connectivity to the local master browser. 
-			Can you reach it by broadcast?</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter�11.�Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2882820">Features and Benefits</a></dt><dd><dl><dt><a href="#id2882834">Backwards Compatibility Backends</a></dt><dt><a href="#id2882936">New Backends</a></dt></dl></dd><dt><a href="#id2883109">Technical Information</a></dt><dd><dl><dt><a href="#id2883235">Important Notes About Security</a></dt><dt><a href="#id2883502">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2883688">The smbpasswd Command</a></dt><dt><a href="#id2883959">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2884197">Password Backends</a></dt><dd><dl><dt><a href="#id2884238">Plain Text</a></dt><dt><a href="#id2884279">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2884392">tdbsam</a></dt><dt><a href="#id2884420">ldapsam</a></dt><dt><a href="#id2886247">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2887095">Common Errors</a></dt><dd><dl><dt><a href="#id2887102">Users can not logon</a></dt><dt><a href="#id2887147">Users being added to wrong backend database</a></dt><dt><a href="#id2887258">auth methods does not work</a></dt></dl></dd></dl></div><p>
+			Can you reach it by broadcast?</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter�11.�Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2880302">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880315">Backwards Compatibility Backends</a></dt><dt><a href="#id2880417">New Backends</a></dt></dl></dd><dt><a href="#id2880590">Technical Information</a></dt><dd><dl><dt><a href="#id2880717">Important Notes About Security</a></dt><dt><a href="#id2880966">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881151">The smbpasswd Command</a></dt><dt><a href="#id2881423">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2881676">Password Backends</a></dt><dd><dl><dt><a href="#id2881717">Plain Text</a></dt><dt><a href="#id2881758">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2881871">tdbsam</a></dt><dt><a href="#id2881898">ldapsam</a></dt><dt><a href="#id2883727">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2884575">Common Errors</a></dt><dd><dl><dt><a href="#id2884582">Users can not logon</a></dt><dt><a href="#id2884627">Users being added to wrong backend database</a></dt><dt><a href="#id2884738">auth methods does not work</a></dt></dl></dd></dl></div><p>
 Samba 3 implements a new capability to work concurrently with multiple account backends.
 The possible new combinations of password backends allows Samba 3 a degree of flexibility
 and scalability that previously could be achieved only with MS Windows Active Directory.
@@ -3056,7 +3056,7 @@ In the course of development of Samba-3, a number of requests were received to p
 ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide
 matching UNIX/Linux accounts. We called this the <span class="emphasis"><em>Non UNIX Accounts (NUA)</em></span>
 capability. The intent was that an administrator could decide to use the <span class="emphasis"><em>tdbsam</em></span>
-backend and by simply specifying <a class="indexterm" name="id2882788"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam_nua
+backend and by simply specifying <a class="indexterm" name="id2880269"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam_nua
 this would allow Samba-3 to implement a solution that did not use UNIX accounts per se. Late
 in the development cycle, the team doing this work hit upon some obstacles that prevents this
 solution from being used. Given the delays with Samba-3 release a decision was made to NOT
@@ -3065,10 +3065,10 @@ SIDs could be found. This feature may thus return during the life cycle for the
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Samba-3 does NOT support Non-UNIX Account (NUA) operation for user accounts.
 Samba-3 does support NUA operation for machine accounts.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882820"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880302"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality
 as follows:
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882834"></a>Backwards Compatibility Backends</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Plain Text:</span></dt><dd><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880315"></a>Backwards Compatibility Backends</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Plain Text:</span></dt><dd><p>
 			This option uses nothing but the UNIX/Linux <tt class="filename">/etc/passwd</tt>
 			style back end. On systems that have PAM (Pluggable Authentication Modules)
 			support all PAM modules are supported. The behaviour is just as it was with
@@ -3091,7 +3091,7 @@ as follows:
 			This option is provided primarily as a migration tool, although there is
 			no reason to force migration at this time. Note that this tool will eventually
 			be deprecated.
-			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882936"></a>New Backends</h3></div></div><div></div></div><p>
+			</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880417"></a>New Backends</h3></div></div><div></div></div><p>
 Samba-3 introduces the following new password backend capabilities:
 </p><div class="variablelist"><dl><dt><span class="term">tdbsam:</span></dt><dd><p>
 			This backend provides a rich database backend for local servers. This
@@ -3135,7 +3135,7 @@ Samba-3 introduces the following new password backend capabilities:
 			The xmlsam option can be useful for account migration between database
 			backends or backups. Use of this tool will allow the data to be edited before migration
 			into another backend format.
-			</p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883109"></a>Technical Information</h2></div></div><div></div></div><p>
+			</p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880590"></a>Technical Information</h2></div></div><div></div></div><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>
@@ -3150,10 +3150,10 @@ Samba-3 introduces the following new password backend capabilities:
 	In addition to differently encrypted passwords, windows also stores certain data for each
 	user that is not stored in a unix user database. e.g: workstations the user may logon from,
 	the location where the users' profile is stored, and so on. Samba retrieves and stores this
-	information using a <a class="indexterm" name="id2883150"></a><i class="parameter"><tt>passdb backend</tt></i>.  Commonly available backends are LDAP, plain text
+	information using a <a class="indexterm" name="id2880630"></a><i class="parameter"><tt>passdb backend</tt></i>.  Commonly available backends are LDAP, plain text
 	file, MySQL and nisplus.  For more information, see the man page for <tt class="filename">smb.conf</tt> regarding the 
-	<a class="indexterm" name="id2883172"></a><i class="parameter"><tt>passdb backend</tt></i> parameter.
-	</p><div class="figure"><a name="idmap-diag"></a><p class="title"><b>Figure�11.1.�IDMAP</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap.png" width="270" alt="IDMAP"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883235"></a>Important Notes About Security</h3></div></div><div></div></div><p>
+	<a class="indexterm" name="id2880654"></a><i class="parameter"><tt>passdb backend</tt></i> parameter.
+	</p><div class="figure"><a name="idmap-diag"></a><p class="title"><b>Figure�11.1.�IDMAP</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap.png" width="270" alt="IDMAP"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880717"></a>Important Notes About Security</h3></div></div><div></div></div><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
@@ -3195,7 +3195,7 @@ Samba-3 introduces the following new password backend capabilities:
 		(broken) only the cached (encrypted) password will be sent to the resource server to
 		affect a auto-reconnect. If the resource server does not support encrypted passwords the
 		auto-reconnect will fail. <span class="emphasis"><em>USE OF ENCRYPTED PASSWORDS IS STRONGLY ADVISED.</em></span>
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883412"></a>Advantages of Encrypted Passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not passed across 
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2880875"></a>Advantages of Encrypted Passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not passed across 
 				the network. Someone using a network sniffer cannot just 
 				record passwords going to the SMB server.</p></li><li><p>Plain text passwords are not stored anywhere in
 				memory or on disk.</p></li><li><p>WinNT doesn't like talking to a server 
@@ -3206,18 +3206,18 @@ Samba-3 introduces the following new password backend capabilities:
 				only things you can do to stop this is to use SMB encryption.
 				</p></li><li><p>Encrypted password support allows automatic share
 				(resource) reconnects.</p></li><li><p>Encrypted passwords are essential for PDC/BDC
-				operation.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883466"></a>Advantages of non-encrypted passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not kept 
+				operation.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2880929"></a>Advantages of non-encrypted passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not kept 
 				on disk, and are NOT cached in memory. </p></li><li><p>Uses same password file as other unix 
 				services such as login and ftp</p></li><li><p>Use of other services (such as telnet and ftp) which
 				send plain text passwords over the net, so sending them for SMB
-				isn't such a big deal.</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883502"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div><div></div></div><p>
+				isn't such a big deal.</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880966"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div><div></div></div><p>
 	Every operation in UNIX/Linux requires a user identifier (UID), just as in
 	MS Windows NT4 / 200x this requires a Security Identifier (SID). Samba provides
 	two means for mapping an MS Windows user to a UNIX/Linux UID.
 	</p><p>
 	Firstly, all Samba SAM (Security Account Manager database) accounts require
 	a UNIX/Linux UID that the account will map to. As users are added to the account
-	information database, Samba will call the <a class="indexterm" name="id2883525"></a><i class="parameter"><tt>add user script</tt></i>
+	information database, Samba will call the <a class="indexterm" name="id2880988"></a><i class="parameter"><tt>add user script</tt></i>
 	interface to add the account to the Samba host OS. In essence all accounts in
 	the local SAM require a local user account.
 	</p><p>
@@ -3243,7 +3243,7 @@ called <b class="command">smbpasswd</b> and <b class="command">pdbedit</b>. A th
 development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK
 GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will
 be announced in time for the Samba-3.0.1 release.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883688"></a>The <span class="emphasis"><em>smbpasswd</em></span> Command</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881151"></a>The <span class="emphasis"><em>smbpasswd</em></span> Command</h3></div></div><div></div></div><p>
 		The smbpasswd utility is a utility similar to the <b class="command">passwd</b>
 		or <b class="command">yppasswd</b> programs.  It maintains the two 32 byte password
 		fields in the passdb backend.
@@ -3289,7 +3289,7 @@ be announced in time for the Samba-3.0.1 release.
 		</p><p>
 		For more details on using <b class="command">smbpasswd</b> refer to the man page (the
 		definitive reference).
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883959"></a>The <span class="emphasis"><em>pdbedit</em></span> Command</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881423"></a>The <span class="emphasis"><em>pdbedit</em></span> Command</h3></div></div><div></div></div><p>
 		<b class="command">pdbedit</b> is a tool that can be used only by root. It is used to
 		manage the passdb backend. <b class="command">pdbedit</b> can be used to:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>add, remove or modify user accounts</p></li><li><p>listing user accounts</p></li><li><p>migrate user accounts</p></li></ul></div><p>
@@ -3331,7 +3331,7 @@ Password must change: Mon, 18 Jan 2038 20:14:07 GMT
 		old <tt class="filename">smbpasswd</tt> database to a <i class="parameter"><tt>tdbsam</tt></i>
 		backend:
 		</p><div class="procedure"><ol type="1"><li><p>
-			Set the <a class="indexterm" name="id2884127"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam, smbpasswd.
+			Set the <a class="indexterm" name="id2881606"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam, smbpasswd.
 			</p></li><li><p>
 			Execute:
 </p><pre class="screen">
@@ -3340,7 +3340,7 @@ Password must change: Mon, 18 Jan 2038 20:14:07 GMT
 			</p></li><li><p>
 			Now remove the <i class="parameter"><tt>smbpasswd</tt></i> from the passdb backend
 			configuration in <tt class="filename">smb.conf</tt>.
-			</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884197"></a>Password Backends</h2></div></div><div></div></div><p>
+			</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2881676"></a>Password Backends</h2></div></div><div></div></div><p>
 Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server
 technology available today. The flexibility is immediately obvious as one begins to explore this
 capability.
@@ -3349,15 +3349,15 @@ It is possible to specify not only multiple different password backends, but eve
 backends of the same type. For example, to use two different tdbsam databases:
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>passdb backend = tdbsam:/etc/samba/passdb.tdb, tdbsam:/etc/samba/old-passdb.tdb</tt></i></td></tr></table><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884238"></a>Plain Text</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881717"></a>Plain Text</h3></div></div><div></div></div><p>
 		Older versions of Samba retrieved user information from the unix user database 
 		and eventually some other fields from the file <tt class="filename">/etc/samba/smbpasswd</tt>
 		or <tt class="filename">/etc/smbpasswd</tt>. When password encryption is disabled, no 
 		SMB specific data is stored at all. Instead all operations are conducted via the way
 		that the Samba host OS will access its <tt class="filename">/etc/passwd</tt> database.
 		eg: On Linux systems that is done via PAM.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884279"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p>
-		Traditionally, when configuring <a class="indexterm" name="id2884289"></a><i class="parameter"><tt>encrypt passwords</tt></i> = yes in Samba's <tt class="filename">smb.conf</tt> file, user account
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881758"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p>
+		Traditionally, when configuring <a class="indexterm" name="id2881768"></a><i class="parameter"><tt>encrypt passwords</tt></i> = yes in Samba's <tt class="filename">smb.conf</tt> file, user account
 		information such as username, LM/NT password hashes, password change times, and account
 		flags have been stored in the <tt class="filename">smbpasswd(5)</tt> file.  There are several
 		disadvantages to this approach for sites with very large numbers of users (counted
@@ -3386,7 +3386,7 @@ backends of the same type. For example, to use two different tdbsam databases:
 		Samba provides an enhanced set of passdb backends that overcome the deficiencies
 		of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam.
 		Of these ldapsam will be of most interest to large corporate or enterprise sites.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884392"></a>tdbsam</h3></div></div><div></div></div><p>Samba can store user and machine account data in a "TDB" (Trivial Database).
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881871"></a>tdbsam</h3></div></div><div></div></div><p>Samba can store user and machine account data in a "TDB" (Trivial Database).
 		Using this backend doesn't require any additional configuration. This backend is
 		recommended for new installations that do not require LDAP.
 		</p><p>
@@ -3394,7 +3394,7 @@ backends of the same type. For example, to use two different tdbsam databases:
 		that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
 		in sites that require PDB/BDC implementations that requires replication of the account
 		database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884420"></a>ldapsam</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881898"></a>ldapsam</h3></div></div><div></div></div><p>
 		There are a few points to stress that the ldapsam does not provide. The LDAP
 		support referred to in the this documentation does not include:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from
@@ -3422,12 +3422,12 @@ backends of the same type. For example, to use two different tdbsam databases:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a>
 			maintained by Ignacio Coupeau.</p></li><li><p>The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are
 			geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
-			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884572"></a>Supported LDAP Servers</h4></div></div><div></div></div><p>
+			</p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882050"></a>Supported LDAP Servers</h4></div></div><div></div></div><p>
 			The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and
 			client libraries.  The same code should work with Netscape's Directory Server and client SDK.
 			However, there are bound to be compile errors and bugs. These should not be hard to fix.
 			Please submit fixes via <a href="#bugreport" title="Chapter�35.�Reporting Bugs">Bug reporting facility</a>.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884598"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882076"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div><div></div></div><p>
 			Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
 			<tt class="filename">examples/LDAP/samba.schema</tt>.  The sambaSamAccount objectclass is given here:
 			</p><p>
@@ -3464,7 +3464,7 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
 			and functioning correctly.  This division of information makes it possible to
 			store all Samba account information in LDAP, but still maintain UNIX account
 			information in NIS while the network is transitioning to a full LDAP infrastructure.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884708"></a>OpenLDAP configuration</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882187"></a>OpenLDAP configuration</h4></div></div><div></div></div><p>
 			To include support for the sambaSamAccount object in an OpenLDAP directory
 			server, first copy the samba.schema file to slapd's configuration directory.
 			The samba.schema file can be found in the directory <tt class="filename">examples/LDAP</tt>
@@ -3533,7 +3533,7 @@ index   default               sub
 </p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>/etc/init.d/slapd restart</tt></b>
 </pre><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884903"></a>Initialise the LDAP database</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882382"></a>Initialise the LDAP database</h4></div></div><div></div></div><p>
 		Before you can add accounts to the LDAP database you must create the account containers
 		that they will be stored in. The following LDIF file should be modified to match your
 		needs (ie: Your DNS entries, etc.).
@@ -3585,28 +3585,28 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 </p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -w <i class="replaceable"><tt>secret</tt></i></tt></b>
 </pre><p>
-		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885030"></a>Configuring Samba</h4></div></div><div></div></div><p>
+		</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882509"></a>Configuring Samba</h4></div></div><div></div></div><p>
 			The following parameters are available in smb.conf only if your
 			version of samba was built with LDAP support. Samba automatically builds with LDAP support if the
 			LDAP libraries are found.
 			</p><p>LDAP related smb.conf options: 
-				<a class="indexterm" name="id2885048"></a><i class="parameter"><tt>passdb backend</tt></i> = ldapsam:url,
-			<a class="indexterm" name="id2885064"></a><i class="parameter"><tt>ldap ssl</tt></i>,
-			<a class="indexterm" name="id2885077"></a><i class="parameter"><tt>ldap admin dn</tt></i>,
-			<a class="indexterm" name="id2885091"></a><i class="parameter"><tt>ldap suffix</tt></i>,
-			<a class="indexterm" name="id2885104"></a><i class="parameter"><tt>ldap filter</tt></i>,
-			<a class="indexterm" name="id2885118"></a><i class="parameter"><tt>ldap machine suffix</tt></i>,
-			<a class="indexterm" name="id2885132"></a><i class="parameter"><tt>ldap user suffix</tt></i>,
-			<a class="indexterm" name="id2885146"></a><i class="parameter"><tt>ldap delete dn</tt></i>,
-			<a class="indexterm" name="id2885160"></a><i class="parameter"><tt>ldap passwd sync</tt></i>,
-			<a class="indexterm" name="id2885174"></a><i class="parameter"><tt>ldap trust ids</tt></i>.
+				<a class="indexterm" name="id2882527"></a><i class="parameter"><tt>passdb backend</tt></i> = ldapsam:url,
+			<a class="indexterm" name="id2882543"></a><i class="parameter"><tt>ldap ssl</tt></i>,
+			<a class="indexterm" name="id2882556"></a><i class="parameter"><tt>ldap admin dn</tt></i>,
+			<a class="indexterm" name="id2882570"></a><i class="parameter"><tt>ldap suffix</tt></i>,
+			<a class="indexterm" name="id2882583"></a><i class="parameter"><tt>ldap filter</tt></i>,
+			<a class="indexterm" name="id2882597"></a><i class="parameter"><tt>ldap machine suffix</tt></i>,
+			<a class="indexterm" name="id2882611"></a><i class="parameter"><tt>ldap user suffix</tt></i>,
+			<a class="indexterm" name="id2882625"></a><i class="parameter"><tt>ldap delete dn</tt></i>,
+			<a class="indexterm" name="id2882639"></a><i class="parameter"><tt>ldap passwd sync</tt></i>,
+			<a class="indexterm" name="id2882653"></a><i class="parameter"><tt>ldap trust ids</tt></i>.
 		</p><p>
 			These are described in the <tt class="filename">smb.conf</tt> man
 			page and so will not be repeated here.  However, a sample smb.conf file for
 			use with an LDAP directory could appear as
 			</p><p>
-</p><div class="example"><a name="id2885206"></a><p class="title"><b>Example�11.2.�Configuration with LDAP</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = TASHTEGO</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = NARNIA</tt></i></td></tr><tr><td># ldap related parameters</td></tr><tr><td># define the DN to use when binding to the directory servers</td></tr><tr><td># The password for this DN is not stored in smb.conf.  Rather it</td></tr><tr><td># must be set by using 'smbpasswd -w <i class="replaceable"><tt>secretpw</tt></i>' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.  If the "ldap admin dn" values</td></tr><tr><td># change, this password will need to be reset.</td></tr><tr><td><i class="parameter"><tt>ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td># Define the SSL option when connecting to the directory</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><i class="parameter"><tt>ldap ssl = start tls</tt></i></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><i class="parameter"><tt>passdb backend = ldapsam:ldap://funball.samba.org</tt></i></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><i class="parameter"><tt>ldap delete dn = no</tt></i></td></tr><tr><td># the machine and user suffix added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><i class="parameter"><tt>ldap user suffix = ou=People</tt></i></td></tr><tr><td><i class="parameter"><tt>ldap machine suffix = ou=Systems</tt></i></td></tr><tr><td># Trust unix account information in LDAP</td></tr><tr><td>#  (see the smb.conf manpage for details)</td></tr><tr><td><i class="parameter"><tt>ldap trust ids = Yes</tt></i></td></tr><tr><td>#  specify the base DN to use when searching the directory</td></tr><tr><td><i class="parameter"><tt>ldap suffix = "ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td>#  generally the default ldap search filter is ok</td></tr><tr><td><i class="parameter"><tt>ldap filter = "(&amp;(uid=%u)(objectclass=sambaSamAccount))"</tt></i></td></tr></table></div><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885427"></a>Accounts and Groups management</h4></div></div><div></div></div><p>
+</p><div class="example"><a name="id2882685"></a><p class="title"><b>Example�11.2.�Configuration with LDAP</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = TASHTEGO</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = NARNIA</tt></i></td></tr><tr><td># ldap related parameters</td></tr><tr><td># define the DN to use when binding to the directory servers</td></tr><tr><td># The password for this DN is not stored in smb.conf.  Rather it</td></tr><tr><td># must be set by using 'smbpasswd -w <i class="replaceable"><tt>secretpw</tt></i>' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.  If the "ldap admin dn" values</td></tr><tr><td># change, this password will need to be reset.</td></tr><tr><td><i class="parameter"><tt>ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td># Define the SSL option when connecting to the directory</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><i class="parameter"><tt>ldap ssl = start tls</tt></i></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><i class="parameter"><tt>passdb backend = ldapsam:ldap://funball.samba.org</tt></i></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><i class="parameter"><tt>ldap delete dn = no</tt></i></td></tr><tr><td># the machine and user suffix added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><i class="parameter"><tt>ldap user suffix = ou=People</tt></i></td></tr><tr><td><i class="parameter"><tt>ldap machine suffix = ou=Systems</tt></i></td></tr><tr><td># Trust unix account information in LDAP</td></tr><tr><td>#  (see the smb.conf manpage for details)</td></tr><tr><td><i class="parameter"><tt>ldap trust ids = Yes</tt></i></td></tr><tr><td>#  specify the base DN to use when searching the directory</td></tr><tr><td><i class="parameter"><tt>ldap suffix = "ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td>#  generally the default ldap search filter is ok</td></tr><tr><td><i class="parameter"><tt>ldap filter = "(&amp;(uid=%u)(objectclass=sambaSamAccount))"</tt></i></td></tr></table></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882906"></a>Accounts and Groups management</h4></div></div><div></div></div><p>
 			As users accounts are managed through the sambaSamAccount objectclass, you should
 			modify your existing administration tools to deal with sambaSamAccount attributes.
 			</p><p>
@@ -3622,7 +3622,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 			groups. This means that Samba makes use of the posixGroup objectclass.
 			For now, there is no NT-like group system management (global and local
 			groups).
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885464"></a>Security and sambaSamAccount</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882943"></a>Security and sambaSamAccount</h4></div></div><div></div></div><p>
 			There are two important points to remember when discussing the security
 			of sambaSamAccount entries in the directory.
 			</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the lmPassword or
@@ -3633,13 +3633,13 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 			on the details of LM/NT password hashes, refer to the
 			<a href="#passdb" title="Chapter�11.�Account Information Databases">Account Information Database</a> section of this chapter.
 			</p><p>
-				To remedy the first security issue, the <a class="indexterm" name="id2885524"></a><i class="parameter"><tt>ldap ssl</tt></i> <tt class="filename">smb.conf</tt> parameter defaults
-			to require an encrypted session (<a class="indexterm" name="id2885545"></a><i class="parameter"><tt>ldap ssl</tt></i> = on) using
+				To remedy the first security issue, the <a class="indexterm" name="id2883003"></a><i class="parameter"><tt>ldap ssl</tt></i> <tt class="filename">smb.conf</tt> parameter defaults
+			to require an encrypted session (<a class="indexterm" name="id2883024"></a><i class="parameter"><tt>ldap ssl</tt></i> = on) using
 			the default port of <tt class="constant">636</tt>
 			when contacting the directory server.  When using an OpenLDAP server, it
 			is possible to use the use the StartTLS LDAP extended  operation in the place of
 			LDAPS.  In either case, you are strongly discouraged to disable this security
-			(<a class="indexterm" name="id2885567"></a><i class="parameter"><tt>ldap ssl</tt></i> = off).
+			(<a class="indexterm" name="id2883046"></a><i class="parameter"><tt>ldap ssl</tt></i> = off).
 			</p><p>
 			Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
 			extended operation.  However, the OpenLDAP library still provides support for
@@ -3655,10 +3655,10 @@ access to attrs=lmPassword,ntPassword
      by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write
      by * none
 </pre><p>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885623"></a>LDAP special attributes for sambaSamAccounts</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883102"></a>LDAP special attributes for sambaSamAccounts</h4></div></div><div></div></div><p>
 			The sambaSamAccount objectclass is composed of the following attributes:
 			</p><p>
-			</p><div class="table"><a name="id2885640"></a><p class="title"><b>Table�11.1.�Attributes in the sambaSamAccount objectclass (LDAP)</b></p><table summary="Attributes in the sambaSamAccount objectclass (LDAP)" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><tt class="constant">sambaLMPassword</tt></td><td align="justify">the LANMAN password 16-byte hash stored as a character
+			</p><div class="table"><a name="id2883118"></a><p class="title"><b>Table�11.1.�Attributes in the sambaSamAccount objectclass (LDAP)</b></p><table summary="Attributes in the sambaSamAccount objectclass (LDAP)" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><tt class="constant">sambaLMPassword</tt></td><td align="justify">the LANMAN password 16-byte hash stored as a character
 representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">sambaNTPassword</tt></td><td align="justify">the NT password hash 16-byte stored as a character
 						representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">sambaPwdLastSet</tt></td><td align="justify">The integer time in seconds since 1970 when the
 						<tt class="constant">sambaLMPassword</tt> and <tt class="constant">sambaNTPassword</tt> attributes were last set.
@@ -3670,10 +3670,10 @@ representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class=
 				where X is the letter of the drive to map. Refer to the "logon drive" parameter in the
 				smb.conf(5) man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaLogonScript</tt></td><td align="justify">The sambaLogonScript property specifies the path of
 				the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
-				is relative to the netlogon share.  Refer to the <a class="indexterm" name="id2885808"></a><i class="parameter"><tt>logon script</tt></i> parameter in the
+				is relative to the netlogon share.  Refer to the <a class="indexterm" name="id2883286"></a><i class="parameter"><tt>logon script</tt></i> parameter in the
 				<tt class="filename">smb.conf</tt> man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaProfilePath</tt></td><td align="justify">specifies a path to the user's profile.
 				This value can be a null string, a local absolute path, or a UNC path.  Refer to the
-				<a class="indexterm" name="id2885841"></a><i class="parameter"><tt>logon path</tt></i> parameter in the <tt class="filename">smb.conf</tt> man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaHomePath</tt></td><td align="justify">The sambaHomePath property specifies the path of
+				<a class="indexterm" name="id2883321"></a><i class="parameter"><tt>logon path</tt></i> parameter in the <tt class="filename">smb.conf</tt> man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaHomePath</tt></td><td align="justify">The sambaHomePath property specifies the path of
 the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies
 a drive letter, sambaHomePath should be a UNC path. The path must be a network
 UNC path of the form <tt class="filename">\\server\share\directory</tt>. This value can be a null string.
@@ -3689,15 +3689,15 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 			</p><div class="itemizedlist"><ul type="disc"><li><p>sambaHomePath</p></li><li><p>sambaLogonScript</p></li><li><p>sambaProfilePath</p></li><li><p>sambaHomeDrive</p></li></ul></div><p>
 			These attributes are only stored with the sambaSamAccount entry if
 			the values are non-default values.  For example, assume TASHTEGO has now been
-			configured as a PDC and that <a class="indexterm" name="id2885997"></a><i class="parameter"><tt>logon home</tt></i> = \\%L\%u was defined in
+			configured as a PDC and that <a class="indexterm" name="id2883477"></a><i class="parameter"><tt>logon home</tt></i> = \\%L\%u was defined in
 			its <tt class="filename">smb.conf</tt> file. When a user named "becky" logons to the domain,
-			the <a class="indexterm" name="id2886020"></a><i class="parameter"><tt>logon home</tt></i> string is expanded to \\TASHTEGO\becky.
+			the <a class="indexterm" name="id2883500"></a><i class="parameter"><tt>logon home</tt></i> string is expanded to \\TASHTEGO\becky.
 			If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org",
 			this value is used.  However, if this attribute does not exist, then the value
-			of the <a class="indexterm" name="id2886038"></a><i class="parameter"><tt>logon home</tt></i> parameter is used in its place.  Samba
+			of the <a class="indexterm" name="id2883517"></a><i class="parameter"><tt>logon home</tt></i> parameter is used in its place.  Samba
 			will only write the attribute value to the directory entry if the value is
 			something other than the default (e.g. <tt class="filename">\\MOBY\becky</tt>).
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886064"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883543"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div><div></div></div><p>
 			The following is a working LDIF with the inclusion of the posixAccount objectclass:
 			</p><p>
 	</p><pre class="programlisting">
@@ -3744,20 +3744,20 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 	sambaPwdMustChange: 2147483647
 	sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
 </pre><p>
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886130"></a>Password synchronisation</h4></div></div><div></div></div><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883609"></a>Password synchronisation</h4></div></div><div></div></div><p>
 		Since version 3.0 samba can update the non-samba (LDAP) password stored with an account. When
 		using pam_ldap, this allows changing both unix and windows passwords at once.
-		</p><p>The <a class="indexterm" name="id2886148"></a><i class="parameter"><tt>ldap passwd sync</tt></i> options can have the following values:</p><div class="variablelist"><dl><dt><span class="term">yes</span></dt><dd><p>When the user changes his password, update
+		</p><p>The <a class="indexterm" name="id2883627"></a><i class="parameter"><tt>ldap passwd sync</tt></i> options can have the following values:</p><div class="variablelist"><dl><dt><span class="term">yes</span></dt><dd><p>When the user changes his password, update
 					       <tt class="constant">ntPassword</tt>, <tt class="constant">lmPassword</tt>
-					       and the <tt class="constant">password</tt> fields.</p></dd><dt><span class="term">no</span></dt><dd><p>Only update <tt class="constant">ntPassword</tt> and <tt class="constant">lmPassword</tt>.</p></dd><dt><span class="term">only</span></dt><dd><p>Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers. <sup>[<a name="id2886231" href="#ftn.id2886231">3</a>]</sup></p></dd></dl></div><p>More information can be found in the smb.conf manpage.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886247"></a>MySQL</h3></div></div><div></div></div><p>
+					       and the <tt class="constant">password</tt> fields.</p></dd><dt><span class="term">no</span></dt><dd><p>Only update <tt class="constant">ntPassword</tt> and <tt class="constant">lmPassword</tt>.</p></dd><dt><span class="term">only</span></dt><dd><p>Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers. <sup>[<a name="id2883711" href="#ftn.id2883711">3</a>]</sup></p></dd></dl></div><p>More information can be found in the smb.conf manpage.
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883727"></a>MySQL</h3></div></div><div></div></div><p>
 	Every so often someone will come along with a great new idea. Storing of user accounts in an
 	SQL backend is one of them. Those who want to do this are in the best position to know what the
 	specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt
 	to document every nitty little detail why certain things of marginal utility to the bulk of
 	Samba users might make sense to the rest. In any case, the following instructions should help
 	the determined SQL user to implement a working system.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886268"></a>Creating the database</h4></div></div><div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883748"></a>Creating the database</h4></div></div><div></div></div><p>
 			You either can set up your own table and specify the field names to pdb_mysql (see below
 			for the column names) or use the default table. The file <tt class="filename">examples/pdb/mysql/mysql.dump</tt> 
 			contains the correct queries to create the required tables. Use the command :
@@ -3766,29 +3766,29 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 <tt class="prompt">$ </tt><b class="userinput"><tt>mysql -u<i class="replaceable"><tt>username</tt></i> -h<i class="replaceable"><tt>hostname</tt></i> -p<i class="replaceable"><tt>password</tt></i> \
 <i class="replaceable"><tt>databasename</tt></i> &lt; <tt class="filename">/path/to/samba/examples/pdb/mysql/mysql.dump</tt></tt></b>
 </pre><p>
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886336"></a>Configuring</h4></div></div><div></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><p>Add a the following to the <a class="indexterm" name="id2886352"></a><i class="parameter"><tt>passdb backend</tt></i> variable in your <tt class="filename">smb.conf</tt>:
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883816"></a>Configuring</h4></div></div><div></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><p>Add a the following to the <a class="indexterm" name="id2883830"></a><i class="parameter"><tt>passdb backend</tt></i> variable in your <tt class="filename">smb.conf</tt>:
 				</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>passdb backend = [other-plugins] mysql:identifier [other-plugins]</tt></i></td></tr></table><p>
 			</p><p>The identifier can be any string you like, as long as it doesn't collide with 
 			the identifiers of other plugins or other instances of pdb_mysql. If you 
-			specify multiple pdb_mysql.so entries in <a class="indexterm" name="id2886395"></a><i class="parameter"><tt>passdb backend</tt></i>, you also need to 
+			specify multiple pdb_mysql.so entries in <a class="indexterm" name="id2883875"></a><i class="parameter"><tt>passdb backend</tt></i>, you also need to 
 			use different identifiers!
 			</p><p>
 				Additional options can be given through the <tt class="filename">smb.conf</tt> file in the <i class="parameter"><tt>[global]</tt></i> section.
 			</p><p>
-			</p><div class="table"><a name="id2886434"></a><p class="title"><b>Table�11.2.�Basic smb.conf options for MySQL passdb backend</b></p><table summary="Basic smb.conf options for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">mysql host</td><td align="justify">host name, defaults to 'localhost'</td></tr><tr><td align="left">mysql password</td><td align="justify">�</td></tr><tr><td align="left">mysql user</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql database</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql port</td><td align="justify">defaults to 3306</td></tr><tr><td align="left">table</td><td align="justify">Name of the table containing users</td></tr></tbody></table></div><p>
+			</p><div class="table"><a name="id2883914"></a><p class="title"><b>Table�11.2.�Basic smb.conf options for MySQL passdb backend</b></p><table summary="Basic smb.conf options for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">mysql host</td><td align="justify">host name, defaults to 'localhost'</td></tr><tr><td align="left">mysql password</td><td align="justify">�</td></tr><tr><td align="left">mysql user</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql database</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql port</td><td align="justify">defaults to 3306</td></tr><tr><td align="left">table</td><td align="justify">Name of the table containing users</td></tr></tbody></table></div><p>
 		</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 			Since the password for the MySQL user is stored in the 
 			<tt class="filename">smb.conf</tt> file, you should make the <tt class="filename">smb.conf</tt> file 
 			readable only to the user that runs Samba This is considered a security 
 			bug and will be fixed soon.
 			</p></div><p>Names of the columns in this table (I've added column types those columns should have first):</p><p>
-			</p><div class="table"><a name="id2886566"></a><p class="title"><b>Table�11.3.�MySQL field names for MySQL passdb backend</b></p><table summary="MySQL field names for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="left">Type</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">logon time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">logoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">kickoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass last set time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass can change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass must change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">username column</td><td align="left">varchar(255)</td><td align="justify">unix username</td></tr><tr><td align="left">domain column</td><td align="left">varchar(255)</td><td align="justify">NT domain user is part of</td></tr><tr><td align="left">nt username column</td><td align="left">varchar(255)</td><td align="justify">NT username</td></tr><tr><td align="left">fullname column</td><td align="left">varchar(255)</td><td align="justify">Full name of user</td></tr><tr><td align="left">home dir column</td><td align="left">varchar(255)</td><td align="justify">UNIX homedir path</td></tr><tr><td align="left">dir drive column</td><td align="left">varchar(2)</td><td align="justify">Directory drive path (eg: 'H:')</td></tr><tr><td align="left">logon script column</td><td align="left">varchar(255)</td><td align="justify">Batch file to run on client side when logging on</td></tr><tr><td align="left">profile path column</td><td align="left">varchar(255)</td><td align="justify">Path of profile</td></tr><tr><td align="left">acct desc column</td><td align="left">varchar(255)</td><td align="justify">Some ASCII NT user data</td></tr><tr><td align="left">workstations column</td><td align="left">varchar(255)</td><td align="justify">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="left">unknown string column</td><td align="left">varchar(255)</td><td align="justify">unknown string</td></tr><tr><td align="left">munged dial column</td><td align="left">varchar(255)</td><td align="justify">?</td></tr><tr><td align="left">user sid column</td><td align="left">varchar(255)</td><td align="justify">NT user SID</td></tr><tr><td align="left">group sid column</td><td align="left">varchar(255)</td><td align="justify">NT group ID</td></tr><tr><td align="left">lanman pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted lanman password</td></tr><tr><td align="left">nt pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted nt passwd</td></tr><tr><td align="left">plain pass column</td><td align="left">varchar(255)</td><td align="justify">plaintext password</td></tr><tr><td align="left">acct control column</td><td align="left">int(9)</td><td align="justify">nt user data</td></tr><tr><td align="left">unknown 3 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">logon divs column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">hours len column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">unknown 5 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">unknown 6 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr></tbody></table></div><p>
+			</p><div class="table"><a name="id2884046"></a><p class="title"><b>Table�11.3.�MySQL field names for MySQL passdb backend</b></p><table summary="MySQL field names for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="left">Type</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">logon time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">logoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">kickoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass last set time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass can change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass must change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">username column</td><td align="left">varchar(255)</td><td align="justify">unix username</td></tr><tr><td align="left">domain column</td><td align="left">varchar(255)</td><td align="justify">NT domain user is part of</td></tr><tr><td align="left">nt username column</td><td align="left">varchar(255)</td><td align="justify">NT username</td></tr><tr><td align="left">fullname column</td><td align="left">varchar(255)</td><td align="justify">Full name of user</td></tr><tr><td align="left">home dir column</td><td align="left">varchar(255)</td><td align="justify">UNIX homedir path</td></tr><tr><td align="left">dir drive column</td><td align="left">varchar(2)</td><td align="justify">Directory drive path (eg: 'H:')</td></tr><tr><td align="left">logon script column</td><td align="left">varchar(255)</td><td align="justify">Batch file to run on client side when logging on</td></tr><tr><td align="left">profile path column</td><td align="left">varchar(255)</td><td align="justify">Path of profile</td></tr><tr><td align="left">acct desc column</td><td align="left">varchar(255)</td><td align="justify">Some ASCII NT user data</td></tr><tr><td align="left">workstations column</td><td align="left">varchar(255)</td><td align="justify">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="left">unknown string column</td><td align="left">varchar(255)</td><td align="justify">unknown string</td></tr><tr><td align="left">munged dial column</td><td align="left">varchar(255)</td><td align="justify">?</td></tr><tr><td align="left">user sid column</td><td align="left">varchar(255)</td><td align="justify">NT user SID</td></tr><tr><td align="left">group sid column</td><td align="left">varchar(255)</td><td align="justify">NT group ID</td></tr><tr><td align="left">lanman pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted lanman password</td></tr><tr><td align="left">nt pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted nt passwd</td></tr><tr><td align="left">plain pass column</td><td align="left">varchar(255)</td><td align="justify">plaintext password</td></tr><tr><td align="left">acct control column</td><td align="left">int(9)</td><td align="justify">nt user data</td></tr><tr><td align="left">unknown 3 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">logon divs column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">hours len column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">unknown 5 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">unknown 6 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr></tbody></table></div><p>
 		</p><p>
 			Eventually, you can put a colon (:) after the name of each column, which 
 			should specify the column to update when updating the table. You can also
 			specify nothing behind the colon - then the data from the field will not be 
 			updated. 
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886956"></a>Using plaintext passwords or encrypted password</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884435"></a>Using plaintext passwords or encrypted password</h4></div></div><div></div></div><p>
 			I strongly discourage the use of plaintext passwords, however, you can use them:
 			</p><p>
 			If you would like to use plaintext passwords, set
@@ -3798,7 +3798,7 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 			</p><p>
 			If you use encrypted passwords, set the 'identifier:plain pass
 			column' to 'NULL' (without the quotes). This is the default.
-			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2886986"></a>Getting non-column data from the table</h4></div></div><div></div></div><p>
+			</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884465"></a>Getting non-column data from the table</h4></div></div><div></div></div><p>
 			It is possible to have not all data in the database and making some 'constant'.
 			</p><p>
 			For example, you can set 'identifier:fullname column' to : 
@@ -3813,7 +3813,7 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 		</p><p>
 		To import data, use:
 		<tt class="prompt">$ </tt> <b class="userinput"><tt>pdbedit -i xml:filename</tt></b>
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2887095"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887102"></a>Users can not logon</h3></div></div><div></div></div><p>&#8220;<span class="quote">I've installed samba, but now I can't log on with my unix account!</span>&#8221;</p><p>Make sure your user has been added to the current samba <a class="indexterm" name="id2887120"></a><i class="parameter"><tt>passdb backend</tt></i>. Read the section <a href="#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887147"></a>Users being added to wrong backend database</h3></div></div><div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884575"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884582"></a>Users can not logon</h3></div></div><div></div></div><p>&#8220;<span class="quote">I've installed samba, but now I can't log on with my unix account!</span>&#8221;</p><p>Make sure your user has been added to the current samba <a class="indexterm" name="id2884600"></a><i class="parameter"><tt>passdb backend</tt></i>. Read the section <a href="#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884627"></a>Users being added to wrong backend database</h3></div></div><div></div></div><p>
 	A few complaints have been received from users that just moved to Samba-3. The following
 	<tt class="filename">smb.conf</tt> file entries were causing problems, new accounts were being added to the old
 	smbpasswd file, not to the tdbsam passdb.tdb file:
@@ -3824,34 +3824,34 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 	parameter entry. If you want to update to the tdbsam, then change the entry to:
 	</p><p>
 		</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[globals]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>passdb backend = tdbsam, smbpasswd</tt></i></td></tr><tr><td>...</td></tr></table><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887258"></a>auth methods does not work</h3></div></div><div></div></div><p>
-		If you explicitly set an <a class="indexterm" name="id2887269"></a><i class="parameter"><tt>auth methods</tt></i> parameter, guest must be specified as the first
-	entry on the line. Eg: <a class="indexterm" name="id2887285"></a><i class="parameter"><tt>auth methods</tt></i> = guest sam.
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884738"></a>auth methods does not work</h3></div></div><div></div></div><p>
+		If you explicitly set an <a class="indexterm" name="id2884749"></a><i class="parameter"><tt>auth methods</tt></i> parameter, guest must be specified as the first
+	entry on the line. Eg: <a class="indexterm" name="id2884756"></a><i class="parameter"><tt>auth methods</tt></i> = guest sam.
 	</p><p>
-	This is the exact opposite of the requirement for the <a class="indexterm" name="id2887304"></a><i class="parameter"><tt>passdb backend</tt></i>
+	This is the exact opposite of the requirement for the <a class="indexterm" name="id2884784"></a><i class="parameter"><tt>passdb backend</tt></i>
 	option, where it must be the <span class="emphasis"><em>LAST</em></span> parameter on the line.
-	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2886231" href="#id2886231">3</a>] </sup>Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter�12.�Mapping MS Windows and UNIX Groups</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jean Fran�ois</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2887487">Features and Benefits</a></dt><dt><a href="#id2887722">Discussion</a></dt><dd><dl><dt><a href="#id2887948">Example Configuration</a></dt></dl></dd><dt><a href="#id2888015">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2888029">Sample smb.conf add group script</a></dt><dt><a href="#id2888108">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2888184">Common Errors</a></dt><dd><dl><dt><a href="#id2888199">Adding Groups Fails</a></dt><dt><a href="#id2888268">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2888294">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></div><a class="indexterm" name="id2887415"></a><p>
+	</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2883711" href="#id2883711">3</a>] </sup>Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter�12.�Mapping MS Windows and UNIX Groups</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jean Fran�ois</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884967">Features and Benefits</a></dt><dt><a href="#id2885202">Discussion</a></dt><dd><dl><dt><a href="#id2885422">Example Configuration</a></dt></dl></dd><dt><a href="#id2885489">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2885503">Sample smb.conf add group script</a></dt><dt><a href="#id2885582">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2885658">Common Errors</a></dt><dd><dl><dt><a href="#id2885674">Adding Groups Fails</a></dt><dt><a href="#id2885742">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2885768">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></div><a class="indexterm" name="id2884895"></a><p>
 	Starting with Samba-3, new group mapping functionality is available to create associations
 	between Windows group SIDs and UNIX groups. The <b class="command">groupmap</b> subcommand
 	included with the <span class="application">net</span> tool can be used to manage these associations.
 	</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 	The first immediate reason to use the group mapping on a Samba PDC, is that
-	<a class="indexterm" name="id2887455"></a>
+	<a class="indexterm" name="id2884936"></a>
 	the <i class="parameter"><tt>domain admin group</tt></i> has been removed and should no longer
 	be specified in <tt class="filename">smb.conf</tt>. This parameter was used to give the listed users membership
 	in the <tt class="constant">Domain Admins</tt> Windows group which gave local admin rights on their workstations
 	(in default configurations).
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2887487"></a>Features and Benefits</h2></div></div><div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884967"></a>Features and Benefits</h2></div></div><div></div></div><p>
 	Samba allows the administrator to create MS Windows NT4 / 200x group accounts and to
 	arbitrarily associate them with UNIX/Linux group accounts.
-	</p><a class="indexterm" name="id2887502"></a><a class="indexterm" name="id2887511"></a><p>
+	</p><a class="indexterm" name="id2884983"></a><a class="indexterm" name="id2884991"></a><p>
 	Group accounts can be managed using the MS Windows NT4 or MS Windows 200x  / XP Professional MMC tools.
 	Appropriate interface scripts should be provided in <tt class="filename">smb.conf</tt> if it is desired that UNIX / Linux system
 	accounts should be automatically created when these tools are used. In the absence of these scripts, and
 	so long as winbind is running, Samba accounts group accounts that are created using these tools will be
-	allocated UNIX UIDs/GIDs from the parameters set by the <a class="indexterm" name="id2887538"></a><i class="parameter"><tt>idmap uid</tt></i>/<a class="indexterm" name="id2887550"></a><i class="parameter"><tt>idmap gid</tt></i> settings
+	allocated UNIX UIDs/GIDs from the parameters set by the <a class="indexterm" name="id2885018"></a><i class="parameter"><tt>idmap uid</tt></i>/<a class="indexterm" name="id2885031"></a><i class="parameter"><tt>idmap gid</tt></i> settings
 	in the <tt class="filename">smb.conf</tt> file.
-	</p><div class="figure"><a name="idmap-group-diag"></a><p class="title"><b>Figure�12.1.�IDMAP groups</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap-groups.png" width="270" alt="IDMAP groups"></div></div><a class="indexterm" name="id2887620"></a><a class="indexterm" name="id2887628"></a><p>
+	</p><div class="figure"><a name="idmap-group-diag"></a><p class="title"><b>Figure�12.1.�IDMAP groups</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap-groups.png" width="270" alt="IDMAP groups"></div></div><a class="indexterm" name="id2885101"></a><a class="indexterm" name="id2885108"></a><p>
 	Administrators should be aware that where <tt class="filename">smb.conf</tt> group interface scripts make
 	direct calls to the UNIX/Linux system tools (eg: the shadow utilities, <b class="command">groupadd</b>,
 	<b class="command">groupdel</b>, <b class="command">groupmod</b>) then the resulting UNIX/Linux group names will be subject
@@ -3859,7 +3859,7 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 	or space characters, then the creation of an MS Windows NT4 / 200x style group of
 	<span class="emphasis"><em>Engineering Managers</em></span> will attempt to create an identically named
 	UNIX/Linux group, an attempt that will of course fail!
-	</p><a class="indexterm" name="id2887680"></a><a class="indexterm" name="id2887689"></a><p>
+	</p><a class="indexterm" name="id2885160"></a><a class="indexterm" name="id2885168"></a><p>
 	There are several possible work-arounds for the operating system tools limitation. One
 	method is to use a script that generates a name for the UNIX/Linux system group that
 	fits the operating system limits, and that then just passes the UNIX/Linux group id (GID)
@@ -3868,13 +3868,13 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 	Another work-around is to manually create a UNIX/Linux group, then manually create the
 	MS Windows NT4 / 200x group on the Samba server and then use the <b class="command">net groupmap</b>
 	tool to connect the two to each other.
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2887722"></a>Discussion</h2></div></div><div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885202"></a>Discussion</h2></div></div><div></div></div><p>
 	When installing <span class="application">MS Windows NT4 / 200x</span> on a computer, the installation
 	program creates default users and groups, notably the <tt class="constant">Administrators</tt> group,
 	and gives that group privileges necessary privileges to perform essential system tasks.
 	eg: Ability to change the date and time or to kill (or close) any process running on the
 	local machine.
-	</p><a class="indexterm" name="id2887752"></a><p>
+	</p><a class="indexterm" name="id2885231"></a><p>
 	The 'Administrator' user is a member of the 'Administrators' group, and thus inherits
 	'Administrators' group privileges. If a 'joe' user is created to be a member of the
 	'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
@@ -3899,12 +3899,12 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 </p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</tt></b>
 </pre><p>
-		</p><a class="indexterm" name="id2887862"></a><p>
+		</p><a class="indexterm" name="id2885344"></a><p>
 		The quotes around "Domain Admins" are necessary due to the space in the group name.
 		Also make sure to leave no whitespace surrounding the equal character (=).
 		</p></li></ol></div><p>
 	Now joe, john and mary are domain administrators!
-	</p><a class="indexterm" name="id2887884"></a><p>
+	</p><a class="indexterm" name="id2885365"></a><p>
 	It is possible to map any arbitrary UNIX group to any Windows NT4 / 200x group as well as
 	making any UNIX group a Windows domain group.  For example, if you wanted to include a
 	UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine,
@@ -3919,7 +3919,7 @@ Refer to the <b class="command">logon home</b> parameter in the <tt class="filen
 	to a user.  Verifying this is done differently depending on the passdb backend 
 	you are using.  Future versions of the tools may perform the verification automatically,
 	but for now the burden is on you.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887948"></a>Example Configuration</h3></div></div><div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885422"></a>Example Configuration</h3></div></div><div></div></div><p>
 		You can list the various groups in the mapping database by executing 
 		<b class="command">net groupmap list</b>.  Here is an example:
 		</p><p>
@@ -3932,13 +3932,13 @@ Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -&gt; domguest
 </pre><p>
 		</p><p>
 		For complete details on <b class="command">net groupmap</b>, refer to the net(8) man page.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888015"></a>Configuration Scripts</h2></div></div><div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885489"></a>Configuration Scripts</h2></div></div><div></div></div><p>
 	Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
 	(ie: prepared by someone else for general use). 
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888029"></a>Sample <tt class="filename">smb.conf</tt> add group script</h3></div></div><div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885503"></a>Sample <tt class="filename">smb.conf</tt> add group script</h3></div></div><div></div></div><p>
 		A script to create complying group names for use by the Samba group interfaces:
 		</p><p>
-</p><div class="example"><a name="id2888052"></a><p class="title"><b>Example�12.1.�smbgrpadd.sh</b></p><pre class="programlisting">
+</p><div class="example"><a name="id2885526"></a><p class="title"><b>Example�12.1.�smbgrpadd.sh</b></p><pre class="programlisting">
 
 #!/bin/bash
 
@@ -3958,7 +3958,7 @@ exit 0
 </p><p>
 		The <tt class="filename">smb.conf</tt> entry for the above script would look like:
 		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>add group script = /path_to_tool/smbgrpadd.sh %g</tt></i></td></tr></table><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888108"></a>Script to configure Group Mapping</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885582"></a>Script to configure Group Mapping</h3></div></div><div></div></div><p>
 		In our example we have created a UNIX/Linux group called <span class="emphasis"><em>ntadmin</em></span>.
 		Our script will create the additional groups <span class="emphasis"><em>Orks</em></span>, <span class="emphasis"><em>Elves</em></span>, <span class="emphasis"><em>Gnomes</em></span>:
 	</p><p>
@@ -3990,13 +3990,13 @@ net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d
 	Of course it is expected that the administrator will modify this to suit local needs.
 	For information regarding the use of the <b class="command">net groupmap</b> tool please
 	refer to the man page.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888184"></a>Common Errors</h2></div></div><div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885658"></a>Common Errors</h2></div></div><div></div></div><p>
 At this time there are many little surprises for the unwary administrator. In a real sense
 it is imperative that every step of automated control scripts must be carefully tested
 manually before putting them into active service.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888199"></a>Adding Groups Fails</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885674"></a>Adding Groups Fails</h3></div></div><div></div></div><p>
 		This is a common problem when the <b class="command">groupadd</b> is called directly
-		by the Samba interface script for the <a class="indexterm" name="id2888220"></a><i class="parameter"><tt>add group script</tt></i> in
+		by the Samba interface script for the <a class="indexterm" name="id2885694"></a><i class="parameter"><tt>add group script</tt></i> in
 		the <tt class="filename">smb.conf</tt> file.
 		</p><p>
 		The most common cause of failure is an attempt to add an MS Windows group account
@@ -4008,9 +4008,9 @@ manually before putting them into active service.
 		third option is to manually create a UNIX/Linux group account that can substitute
 		for the MS Windows group name, then use the procedure listed above to map that group
 		to the MS Windows group.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888268"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><a class="indexterm" name="id2888277"></a><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885742"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><a class="indexterm" name="id2885751"></a><p>
 		Samba-3 does NOT support nested groups from the MS Windows control environment.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888294"></a>Adding <span class="emphasis"><em>Domain Users</em></span> to the <span class="emphasis"><em>Power Users</em></span> group</h3></div></div><div></div></div><p>&#8220;<span class="quote">
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885768"></a>Adding <span class="emphasis"><em>Domain Users</em></span> to the <span class="emphasis"><em>Power Users</em></span> group</h3></div></div><div></div></div><p>&#8220;<span class="quote">
 		What must I do to add Domain Users to the Power Users group?
 		</span>&#8221;</p><p>
 		The Power Users group is a group that is local to each Windows
@@ -4018,15 +4018,15 @@ manually before putting them into active service.
 		group automatically, this must be done on each workstation by logging in as the local workstation 
 		<span class="emphasis"><em>administrator</em></span> and then using click on Start / Control Panel / Users and Passwords
 		now click on the 'Advanced' tab, then on the 'Advanced' Button.
-		</p><a class="indexterm" name="id2888333"></a><p>
+		</p><a class="indexterm" name="id2885807"></a><p>
 		Now click on 'Groups', then double click on 'Power Users'. This will launch the panel to add users
 		or groups to the local machine 'Power Uses' group. Click on the 'Add' button, select the domain
 		from which the 'Domain Users' group is to be added, double click on the 'Domain Users' group, then
 		click on the 'Ok' button. Note: If a logon box is presented during this process please remember to
 		enter the connect as DOMAIN\UserName. ie: For the domain MIDEARTH and the user 'root' enter
 		MIDEARTH\root.
-		</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter�13.�File, Directory and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2888551">Features and Benefits</a></dt><dt><a href="#id2888688">File System Access Controls</a></dt><dd><dl><dt><a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2889023">Managing Directories</a></dt><dt><a href="#id2889117">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2889345">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2889373">User and Group Based Controls</a></dt><dt><a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2890173">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2890553">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2890626">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2890925">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2890933">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2890978">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2891057">Viewing file ownership</a></dt><dt><a href="#id2891188">Viewing File or Directory Permissions</a></dt><dt><a href="#id2891423">Modifying file or directory permissions</a></dt><dt><a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt><a href="#id2891979">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2892060">Common Errors</a></dt><dd><dl><dt><a href="#id2892074">Users can not write to a public share</a></dt><dt><a href="#id2892503">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2892555">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></div><a class="indexterm" name="id2888473"></a><p>
+		</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter�13.�File, Directory and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2886024">Features and Benefits</a></dt><dt><a href="#id2886154">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2886489">Managing Directories</a></dt><dt><a href="#id2886582">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2886810">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2886837">User and Group Based Controls</a></dt><dt><a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2887639">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888020">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888092">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2888391">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2888399">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2888444">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2888523">Viewing file ownership</a></dt><dt><a href="#id2888655">Viewing File or Directory Permissions</a></dt><dt><a href="#id2888889">Modifying file or directory permissions</a></dt><dt><a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt><a href="#id2889446">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2889526">Common Errors</a></dt><dd><dl><dt><a href="#id2889540">Users can not write to a public share</a></dt><dt><a href="#id2889969">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890022">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></div><a class="indexterm" name="id2885947"></a><p>
 Advanced MS Windows users are frequently perplexed when file, directory and share manipulation of
 resources shared via Samba do not behave in the manner they might expect. MS Windows network
 administrators are often confused regarding network access controls and how to
@@ -4039,7 +4039,7 @@ and directory access permissions.
 The problem lies in the differences in how file and directory permissions and controls work
 between the two environments. This difference is one that Samba can not completely hide, even
 though it does try to bridge the chasm to a degree.
-</p><a class="indexterm" name="id2888509"></a><p>
+</p><a class="indexterm" name="id2885983"></a><p>
 POSIX Access Control List technology has been available (along with Extended Attributes)
 for UNIX for many years, yet there is little evidence today of any significant use. This
 explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows
@@ -4055,7 +4055,7 @@ and interchange of data between differing operating environments. Samba has no i
 UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient
 level of exchange of data between the two environments.  What is available today extends well
 beyond early plans and expectations, yet the gap continues to shrink.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888551"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886024"></a>Features and Benefits</h2></div></div><div></div></div><p>
 	Samba offers a lot of flexibility in file system access management. These are the key access control
 	facilities present in Samba today:
 	</p><div class="itemizedlist"><p class="title"><b>Samba Access Control Facilities</b></p><ul type="disc"><li><p>
@@ -4095,12 +4095,12 @@ beyond early plans and expectations, yet the gap continues to shrink.
 			this also. Sadly, few Linux platforms ship today with native ACLs and
 			Extended Attributes enabled. This chapter has pertinent information
 			for users of platforms that support them.
-			</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888688"></a>File System Access Controls</h2></div></div><div></div></div><p>
+			</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886154"></a>File System Access Controls</h2></div></div><div></div></div><p>
 Perhaps the most important recognition to be made is the simple fact that MS Windows NT4 / 200x / XP
 implement a totally divergent file system technology from what is provided in the UNIX operating system
 environment. Firstly we should consider what the most significant differences are, then we shall look
 at how Samba helps to bridge the differences.
-</p><a class="indexterm" name="id2888708"></a><a class="indexterm" name="id2888716"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888724"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div><div></div></div><p>
+</p><a class="indexterm" name="id2886173"></a><a class="indexterm" name="id2886182"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886190"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div><div></div></div><p>
 	Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions
 	and permissions. It also means that if the MS Windows networking environment requires file system
 	behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating
@@ -4117,7 +4117,7 @@ at how Samba helps to bridge the differences.
 		</p><p>
 		What MS Windows calls a Folder, UNIX calls a directory.
 		</p></dd><dt><span class="term">Case Sensitivity</span></dt><dd><p>
-		<a class="indexterm" name="id2888810"></a>
+		<a class="indexterm" name="id2886276"></a>
 		MS Windows file names are generally upper case if made up of 8.3 (ie: 8 character file name
 		and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case
 		Insensitive.
@@ -4153,9 +4153,9 @@ at how Samba helps to bridge the differences.
 		either start up files for various UNIX applications, or they may be files that contain
 		start-up configuration data.
 		</p></dd><dt><span class="term">Links and Short-Cuts</span></dt><dd><p>
-		<a class="indexterm" name="id2888961"></a>
-		<a class="indexterm" name="id2888972"></a>
-		<a class="indexterm" name="id2888983"></a>
+		<a class="indexterm" name="id2886426"></a>
+		<a class="indexterm" name="id2886437"></a>
+		<a class="indexterm" name="id2886448"></a>
 
 		MS Windows make use of "links and Short-Cuts" that are actually special types of files that will
 		redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory
@@ -4169,10 +4169,10 @@ at how Samba helps to bridge the differences.
 	There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort
 	in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the
 	purpose of UNIX/Linux training/education.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889023"></a>Managing Directories</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886489"></a>Managing Directories</h3></div></div><div></div></div><p>
 	There are three basic operations for managing directories, <b class="command">create, delete, rename</b>.
-	</p><div class="table"><a name="id2889043"></a><p class="title"><b>Table�13.1.�Managing directories with unix and windows</b></p><table summary="Managing directories with unix and windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">UNIX Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div><p>
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889117"></a>File and Directory Access Control</h3></div></div><div></div></div><p>
+	</p><div class="table"><a name="id2886508"></a><p class="title"><b>Table�13.1.�Managing directories with unix and windows</b></p><table summary="Managing directories with unix and windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">UNIX Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886582"></a>File and Directory Access Control</h3></div></div><div></div></div><p>
 	The network administrator is strongly advised to read foundational training manuals and reference materials
 	regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions
 	without having to resort to more complex facilities like POSIX Access Control Lists (ACLs) or Extended
@@ -4205,7 +4205,7 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	</p><div class="figure"><a name="access1"></a><p class="title"><b>Figure�13.1.�Overview of unix permissions field</b></p><div class="mediaobject"><img src="projdoc/imagefiles/access1.png" width="270" alt="Overview of unix permissions field"></div></div><p>
 	Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character.
 
-	</p><div class="example"><a name="id2889268"></a><p class="title"><b>Example�13.1.�Example File</b></p><pre class="programlisting">
+	</p><div class="example"><a name="id2886704"></a><p class="title"><b>Example�13.1.�Example File</b></p><pre class="programlisting">
 		-rwxr-x---   Means: The owner (user) can read, write, execute
 		                    the group can read and execute
 		                    everyone else can NOT do anything with it
@@ -4231,101 +4231,101 @@ drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
 	the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the
 	directory but can NOT create new files. NOTE: If files in the directory are set to be readable and writable for the group, then
 	group members will be able to write to (or delete) them.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2889345"></a>Share Definition Access Controls</h2></div></div><div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886810"></a>Share Definition Access Controls</h2></div></div><div></div></div><p>
 The following parameters in the <tt class="filename">smb.conf</tt> file sections that define a share control or affect access controls.
 Before using any of the following options please refer to the man page for <tt class="filename">smb.conf</tt>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889373"></a>User and Group Based Controls</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886837"></a>User and Group Based Controls</h3></div></div><div></div></div><p>
 	User and group based controls can prove very useful. In some situations it is distinctly desirable to affect all
-	file system operations as if a single user is doing this, the use of the <a class="indexterm" name="id2889387"></a><i class="parameter"><tt>force user</tt></i> and 
-	<a class="indexterm" name="id2889400"></a><i class="parameter"><tt>force group</tt></i> behaviour will achieve this. In other situations it may be necessary to affect a
+	file system operations as if a single user is doing this, the use of the <a class="indexterm" name="id2886852"></a><i class="parameter"><tt>force user</tt></i> and 
+	<a class="indexterm" name="id2886865"></a><i class="parameter"><tt>force group</tt></i> behaviour will achieve this. In other situations it may be necessary to affect a
 	paranoia level of control to ensure that only particular authorised persons will be able to access a share or
-	it's contents, here the use of the <a class="indexterm" name="id2889418"></a><i class="parameter"><tt>valid users</tt></i> or the <a class="indexterm" name="id2889431"></a><i class="parameter"><tt>invalid users</tt></i> may
+	it's contents, here the use of the <a class="indexterm" name="id2886884"></a><i class="parameter"><tt>valid users</tt></i> or the <a class="indexterm" name="id2886897"></a><i class="parameter"><tt>invalid users</tt></i> may
 	be most useful.
 	</p><p>
 	As always, it is highly advisable to use the least difficult to maintain and the least ambiguous method for
 	controlling access. Remember, that when you leave the scene someone else will need to provide assistance and
 	if that person finds too great a mess, or if they do not understand what you have done then there is risk of
 	Samba being removed and an alternative solution being adopted.
-	</p><div class="table"><a name="id2889459"></a><p class="title"><b>Table�13.2.�User and Group Based Controls</b></p><table summary="User and Group Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2889516"></a><i class="parameter"><tt>admin users</tt></i></td><td align="justify"><p>
+	</p><div class="table"><a name="id2886925"></a><p class="title"><b>Table�13.2.�User and Group Based Controls</b></p><table summary="User and Group Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2886982"></a><i class="parameter"><tt>admin users</tt></i></td><td align="justify"><p>
 			List of users who will be granted administrative privileges on the share.
 			They will do all file operations as the super-user (root).  
 			Any user in this list will be able to do anything they like on the share,
 			irrespective of file permissions.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889546"></a><i class="parameter"><tt>force group</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887012"></a><i class="parameter"><tt>force group</tt></i></td><td align="justify"><p>
 			Specifies a UNIX group name that will be assigned as the default primary group
 			for all users connecting to this service.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889573"></a><i class="parameter"><tt>force user</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887039"></a><i class="parameter"><tt>force user</tt></i></td><td align="justify"><p>
 			Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service.
 			This is useful for sharing files. Incorrect use can cause security problems.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889602"></a><i class="parameter"><tt>guest ok</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887068"></a><i class="parameter"><tt>guest ok</tt></i></td><td align="justify"><p>
 			If this parameter is set for a service, then no password is required to connect to the service. Privileges will be 
 			those of the  guest account.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889629"></a><i class="parameter"><tt>invalid users</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887095"></a><i class="parameter"><tt>invalid users</tt></i></td><td align="justify"><p>
 			List of users that should not be allowed to login to this service.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889655"></a><i class="parameter"><tt>only user</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887121"></a><i class="parameter"><tt>only user</tt></i></td><td align="justify"><p>
 			Controls whether connections with usernames not in the user list will be allowed.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889682"></a><i class="parameter"><tt>read list</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887148"></a><i class="parameter"><tt>read list</tt></i></td><td align="justify"><p>
 			List of users that are given read-only access to a service. Users in this list
 			will not be given write access, no matter what the  read only  option is set to. 
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889710"></a><i class="parameter"><tt>username</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887176"></a><i class="parameter"><tt>username</tt></i></td><td align="justify"><p>
 			Refer to the <tt class="filename">smb.conf</tt> man page for more information - this is a complex and potentially misused parameter.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889743"></a><i class="parameter"><tt>valid users</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887208"></a><i class="parameter"><tt>valid users</tt></i></td><td align="justify"><p>
 			List of users that should be allowed to login to this service.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889769"></a><i class="parameter"><tt>write list</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887235"></a><i class="parameter"><tt>write list</tt></i></td><td align="justify"><p>
 			List of users that are given read-write access to a service.
-			</p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889794"></a>File and Directory Permissions Based Controls</h3></div></div><div></div></div><p>
+			</p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887260"></a>File and Directory Permissions Based Controls</h3></div></div><div></div></div><p>
 	The following file and directory permission based controls, if misused, can result in considerable difficulty to
 	diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one
 	undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually
 	re-introduce them in a controlled fashion.
-	</p><div class="table"><a name="id2889815"></a><p class="title"><b>Table�13.3.�File and Directory Permission Based Controls</b></p><table summary="File and Directory Permission Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2889870"></a><i class="parameter"><tt>create mask</tt></i></td><td align="justify"><p>
+	</p><div class="table"><a name="id2887281"></a><p class="title"><b>Table�13.3.�File and Directory Permission Based Controls</b></p><table summary="File and Directory Permission Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2887336"></a><i class="parameter"><tt>create mask</tt></i></td><td align="justify"><p>
 			Refer to the <tt class="filename">smb.conf</tt> man page.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889902"></a><i class="parameter"><tt>directory mask</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887367"></a><i class="parameter"><tt>directory mask</tt></i></td><td align="justify"><p>
 			The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories.
 			See also: directory security mask.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889928"></a><i class="parameter"><tt>dos filemode</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887394"></a><i class="parameter"><tt>dos filemode</tt></i></td><td align="justify"><p>
 			Enabling this parameter allows a user who has write access to the file to modify the permissions on it.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889955"></a><i class="parameter"><tt>force create mode</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887421"></a><i class="parameter"><tt>force create mode</tt></i></td><td align="justify"><p>
 			This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2889982"></a><i class="parameter"><tt>force directory mode</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887447"></a><i class="parameter"><tt>force directory mode</tt></i></td><td align="justify"><p>
 			This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890010"></a><i class="parameter"><tt>force directory security mode</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887476"></a><i class="parameter"><tt>force directory security mode</tt></i></td><td align="justify"><p>
 			Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890038"></a><i class="parameter"><tt>force security mode</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887504"></a><i class="parameter"><tt>force security mode</tt></i></td><td align="justify"><p>
 			Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890065"></a><i class="parameter"><tt>hide unreadable</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887530"></a><i class="parameter"><tt>hide unreadable</tt></i></td><td align="justify"><p>
 			Prevents clients from seeing the existence of files that cannot be read.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890091"></a><i class="parameter"><tt>hide unwriteable files</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887557"></a><i class="parameter"><tt>hide unwriteable files</tt></i></td><td align="justify"><p>
 			Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. 
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890119"></a><i class="parameter"><tt>nt acl support</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887585"></a><i class="parameter"><tt>nt acl support</tt></i></td><td align="justify"><p>
 			This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists.
-			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2890146"></a><i class="parameter"><tt>security mask</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="left"><a class="indexterm" name="id2887611"></a><i class="parameter"><tt>security mask</tt></i></td><td align="justify"><p>
 			Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file.
-			</p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890173"></a>Miscellaneous Controls</h3></div></div><div></div></div><p>
+			</p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887639"></a>Miscellaneous Controls</h3></div></div><div></div></div><p>
 	The following are documented because of the prevalence of administrators creating inadvertent barriers to file
 	access by not understanding the full implications of <tt class="filename">smb.conf</tt> file settings.
-	</p><div class="table"><a name="id2890195"></a><p class="title"><b>Table�13.4.�Other Controls</b></p><table summary="Other Controls" border="1"><colgroup><col align="justify"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="justify"><a class="indexterm" name="id2890250"></a><i class="parameter"><tt>case sensitive</tt></i>, <a class="indexterm" name="id2890264"></a><i class="parameter"><tt>default case</tt></i>, <a class="indexterm" name="id2890278"></a><i class="parameter"><tt>short preserve case</tt></i></td><td align="justify"><p>
+	</p><div class="table"><a name="id2887661"></a><p class="title"><b>Table�13.4.�Other Controls</b></p><table summary="Other Controls" border="1"><colgroup><col align="justify"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="justify"><a class="indexterm" name="id2887716"></a><i class="parameter"><tt>case sensitive</tt></i>, <a class="indexterm" name="id2887730"></a><i class="parameter"><tt>default case</tt></i>, <a class="indexterm" name="id2887744"></a><i class="parameter"><tt>short preserve case</tt></i></td><td align="justify"><p>
 			This means that all file name lookup will be done in a case sensitive manner. 
 			Files will be created with the precise filename Samba received from the MS Windows client.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890306"></a><i class="parameter"><tt>csc policy</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887772"></a><i class="parameter"><tt>csc policy</tt></i></td><td align="justify"><p>
 			Client Side Caching Policy - parallels MS Windows client side file caching capabilities.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890333"></a><i class="parameter"><tt>dont descend</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887799"></a><i class="parameter"><tt>dont descend</tt></i></td><td align="justify"><p>
 			Allows to specify a comma-delimited list of directories that the server should always show as empty.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890360"></a><i class="parameter"><tt>dos filetime resolution</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887826"></a><i class="parameter"><tt>dos filetime resolution</tt></i></td><td align="justify"><p>
 			This option is mainly used as a compatibility option for Visual C++ when used against Samba shares.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890387"></a><i class="parameter"><tt>dos filetimes</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887853"></a><i class="parameter"><tt>dos filetimes</tt></i></td><td align="justify"><p>
 			DOS and Windows allows users to change file time stamps if they can write to the file. POSIX semantics prevent this.
 			This options allows DOS and Windows behaviour.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890416"></a><i class="parameter"><tt>fake oplocks</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887882"></a><i class="parameter"><tt>fake oplocks</tt></i></td><td align="justify"><p>
 			Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an
 			oplock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890445"></a><i class="parameter"><tt>hide dot files</tt></i>, <a class="indexterm" name="id2890460"></a><i class="parameter"><tt>hide files</tt></i>, <a class="indexterm" name="id2890473"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887912"></a><i class="parameter"><tt>hide dot files</tt></i>, <a class="indexterm" name="id2887926"></a><i class="parameter"><tt>hide files</tt></i>, <a class="indexterm" name="id2887939"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p>
 			Note: MS Windows Explorer allows over-ride of files marked as hidden so they will still be visible.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890500"></a><i class="parameter"><tt>read only</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887966"></a><i class="parameter"><tt>read only</tt></i></td><td align="justify"><p>
 			If this parameter is yes, then users of a service may not create or modify files in the service's directory.
-			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2890527"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p>
+			</p></td></tr><tr><td align="justify"><a class="indexterm" name="id2887993"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p>
 			List of files and directories that are neither visible nor accessible.
-			</p></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890553"></a>Access Controls on Shares</h2></div></div><div></div></div><p>
+			</p></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888020"></a>Access Controls on Shares</h2></div></div><div></div></div><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
@@ -4342,9 +4342,9 @@ Before using any of the following options please refer to the man page for <tt c
 	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: <b class="userinput"><tt>tdbdump share_info.tdb</tt></b>.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890626"></a>Share Permissions Management</h3></div></div><div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888092"></a>Share Permissions Management</h3></div></div><div></div></div><p>
 		The best tool for the task is platform dependant. Choose the best tool for your environment.
-		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890639"></a>Windows NT4 Workstation/Server</h4></div></div><div></div></div><p>
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888105"></a>Windows NT4 Workstation/Server</h4></div></div><div></div></div><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.
@@ -4354,7 +4354,7 @@ Before using any of the following options please refer to the man page for <tt c
 			</p></li><li><p>
 			Now click on the share that you wish to manage, then click on the <span class="guilabel">Properties</span> tab, next click on
 			the <span class="guilabel">Permissions</span> tab. Now you can add or change access control settings as you wish.
-			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890722"></a>Windows 200x/XP</h4></div></div><div></div></div><p>
+			</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888188"></a>Windows 200x/XP</h4></div></div><div></div></div><p>
 			On <span class="application">MS Windows NT4/200x/XP</span> system access control lists on the share itself are set using native
 			tools, usually from file manager. For example, in Windows 200x: right click on the shared folder,
 			then select <span class="guimenuitem">Sharing</span>, then click on <span class="guilabel">Permissions</span>. The default 
@@ -4383,7 +4383,7 @@ Before using any of the following options please refer to the man page for <tt c
 			then effectively no user will be able to access the share. This is a result of what is known as
 			ACL precedence. ie: Everyone with <span class="emphasis"><em>no access</em></span> means that MaryK who is part of the group 
 			<tt class="constant">Everyone</tt> will have no access even if this user is given explicit full control access.
-			</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890925"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890933"></a>Managing UNIX permissions Using NT Security Dialogs</h3></div></div><div></div></div><p>
+			</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888391"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888399"></a>Managing UNIX permissions Using NT Security Dialogs</h3></div></div><div></div></div><p>
 		Windows NT clients can use their native security settings dialog box to view and modify the
 		underlying UNIX permissions.
 		</p><p>
@@ -4397,7 +4397,7 @@ Before using any of the following options please refer to the man page for <tt c
 		When trying to figure out file access problems it is vitally important to find the identity of the Windows
 		user as it is presented by Samba at the point of file access. This can best be determined from the
 		Samba log files.
-		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890978"></a>Viewing File Security on a Samba Share</h3></div></div><div></div></div><p>
+		</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888444"></a>Viewing File Security on a Samba Share</h3></div></div><div></div></div><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="guilabel">Properties</span>
 		entry at the bottom of the menu. This brings up the file properties dialog box. Click on the tab
@@ -4408,7 +4408,7 @@ Before using any of the following options please refer to the man page for <tt c
 		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 <span class="guibutton">Add</span>
 		button will not currently allow a list of users to be seen.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891057"></a>Viewing file ownership</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888523"></a>Viewing file ownership</h3></div></div><div></div></div><p>
 		Clicking on the <span class="guibutton">Ownership</span> button brings up a dialog box telling you who owns
 		the given file. The owner name will be of the form:
 		</p><p>
@@ -4419,7 +4419,7 @@ Before using any of the following options please refer to the man page for <tt c
 		descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).
 		Click on the <span class="guibutton">Close </span> button to remove this dialog.
 		</p><p>
-		If the parameter <a class="indexterm" name="id2891120"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt>
+		If the parameter <a class="indexterm" name="id2888586"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt>
 		then the file owner will be shown as the NT user <tt class="constant">"Everyone"</tt>.
 		</p><p>
 		The <span class="guibutton">Take Ownership</span> button will not allow you to change the ownership of this file to
@@ -4431,7 +4431,7 @@ Before using any of the following options please refer to the man page for <tt c
 		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="application">Seclib</span> NT security library written
-		by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891188"></a>Viewing File or Directory Permissions</h3></div></div><div></div></div><p>
+		by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888655"></a>Viewing File or Directory Permissions</h3></div></div><div></div></div><p>
 		The third button is the <span class="guibutton">Permissions</span> 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">"<i class="replaceable"><tt>SERVER</tt></i>\
@@ -4440,13 +4440,13 @@ Before using any of the following options please refer to the man page for <tt c
 		<i class="replaceable"><tt>user</tt></i> is the user name of the UNIX user who owns the file, and
 		<i class="replaceable"><tt>(Long name)</tt></i> is the descriptive string identifying the user (normally found in the
 		GECOS field of the UNIX password database).</p><p>
-		If the parameter <a class="indexterm" name="id2891254"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt>
+		If the parameter <a class="indexterm" name="id2888720"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt>
 		then the file owner will be shown as the NT user <tt class="constant">"Everyone"</tt> 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="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891287"></a>File Permissions</h4></div></div><div></div></div><p>The standard UNIX user/group/world triplet and 
+		</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888753"></a>File Permissions</h4></div></div><div></div></div><p>The standard UNIX user/group/world triplet and 
 			the corresponding "read", "write", "execute" permissions 
 			triplets are mapped by Samba into a three element NT ACL 
 			with the 'r', 'w', and 'x' bits mapped into the corresponding 
@@ -4468,7 +4468,7 @@ Before using any of the following options please refer to the man page for <tt c
 			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="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891379"></a>Directory Permissions</h4></div></div><div></div></div><p>Directories on an NT NTFS file system have two 
+			be given below.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888845"></a>Directory Permissions</h4></div></div><div></div></div><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 <tt class="constant">"RW"</tt> 
@@ -4479,12 +4479,12 @@ Before using any of the following options please refer to the man page for <tt c
 			inherited</tt> 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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891423"></a>Modifying file or directory permissions</h3></div></div><div></div></div><p>Modifying file and directory permissions is as simple 
+			created by Samba on this share would receive.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888889"></a>Modifying file or directory permissions</h3></div></div><div></div></div><p>Modifying file and directory permissions is as simple 
 		as changing the displayed permissions in the dialog box, and 
 		clicking the <span class="guibutton">OK</span> 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 <a class="indexterm" name="id2891452"></a><i class="parameter"><tt>nt acl support</tt></i>
+		attributes that need to also be taken into account.</p><p>If the parameter <a class="indexterm" name="id2888918"></a><i class="parameter"><tt>nt acl support</tt></i>
 		is set to <tt class="constant">false</tt> then any attempt to set 
 		security permissions will fail with an <span class="errorname">"Access Denied"
 		</span> message.</p><p>The first thing to note is that the <span class="guibutton">"Add"</span> 
@@ -4513,52 +4513,52 @@ Before using any of the following options please refer to the man page for <tt c
 		component and click the <span class="guibutton">Remove</span> button, 
 		or set the component to only have the special <tt class="constant">Take
 		Ownership</tt> permission (displayed as <b class="command">"O"
-		</b>) highlighted.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891583"></a>Interaction with the standard Samba create mask 
+		</b>) highlighted.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889049"></a>Interaction with the standard Samba create mask 
 		parameters</h3></div></div><div></div></div><p>There are four parameters 
 		to control interaction with the standard Samba create mask parameters.
 		These are :
 
-		</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2891603"></a><i class="parameter"><tt>security mask</tt></i></p></li><li><p><a class="indexterm" name="id2891620"></a><i class="parameter"><tt>force security mode</tt></i></p></li><li><p><a class="indexterm" name="id2891636"></a><i class="parameter"><tt>directory security mask</tt></i></p></li><li><p><a class="indexterm" name="id2891653"></a><i class="parameter"><tt>force directory security mode</tt></i></p></li></ul></div><p>
+		</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2889069"></a><i class="parameter"><tt>security mask</tt></i></p></li><li><p><a class="indexterm" name="id2889086"></a><i class="parameter"><tt>force security mode</tt></i></p></li><li><p><a class="indexterm" name="id2889103"></a><i class="parameter"><tt>directory security mask</tt></i></p></li><li><p><a class="indexterm" name="id2889120"></a><i class="parameter"><tt>force directory security mode</tt></i></p></li></ul></div><p>
 
 		</p><p>Once a user clicks <span class="guibutton">OK</span> to apply the 
 		permissions Samba maps the given permissions into a user/group/world 
 		r/w/x triplet set, and then will check the changed permissions for a 
 		file against the bits set in the  
-		<a class="indexterm" name="id2891683"></a><i class="parameter"><tt>security mask</tt></i> parameter. Any bits that 
+		<a class="indexterm" name="id2889150"></a><i class="parameter"><tt>security mask</tt></i> 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 <a class="indexterm" name="id2891704"></a><i class="parameter"><tt>security mask</tt></i>
+		in the file permissions.</p><p>Essentially, zero bits in the <a class="indexterm" name="id2889171"></a><i class="parameter"><tt>security mask</tt></i>
 		mask may be treated as a set of bits the user is <span class="emphasis"><em>not</em></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 class="indexterm" name="id2891730"></a><i class="parameter"><tt>create mask</tt></i>	parameter. To allow a user to modify all the
+			the <a class="indexterm" name="id2889196"></a><i class="parameter"><tt>create mask</tt></i>	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 class="indexterm" name="id2891751"></a><i class="parameter"><tt>force security mode</tt></i> parameter. Any bits 
+		<a class="indexterm" name="id2889218"></a><i class="parameter"><tt>force security mode</tt></i> 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 <i class="parameter"><tt>force security mode
 		</tt></i> 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 class="indexterm" name="id2891787"></a><i class="parameter"><tt>force create mode</tt></i> parameter.
+			as the <a class="indexterm" name="id2889253"></a><i class="parameter"><tt>force create mode</tt></i> 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 <a class="indexterm" name="id2891807"></a><i class="parameter"><tt>security mask</tt></i> and <i class="parameter"><tt>force 
+		with no restrictions set this parameter to 000.</p><p>The <a class="indexterm" name="id2889274"></a><i class="parameter"><tt>security mask</tt></i> and <i class="parameter"><tt>force 
 		security mode</tt></i> 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 <i class="parameter"><tt>
 		directory security mask</tt></i> instead of <i class="parameter"><tt>security 
 		mask</tt></i>, and <i class="parameter"><tt>force directory security mode
 		</tt></i> parameter instead of <i class="parameter"><tt>force security mode
-		</tt></i>.</p><p>The <a class="indexterm" name="id2891869"></a><i class="parameter"><tt>directory security mask</tt></i> parameter 
+		</tt></i>.</p><p>The <a class="indexterm" name="id2889335"></a><i class="parameter"><tt>directory security mask</tt></i> parameter 
 		by default is set to the same value as the <i class="parameter"><tt>directory mask
 		</tt></i> parameter and the <i class="parameter"><tt>force directory security 
 		mode</tt></i> parameter by default is set to the same value as 
-		the <a class="indexterm" name="id2891900"></a><i class="parameter"><tt>force directory mode</tt></i> parameter. </p><p>In this way Samba enforces the permission restrictions that 
+		the <a class="indexterm" name="id2889366"></a><i class="parameter"><tt>force directory mode</tt></i> 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><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode = 0</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode = 0</tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891979"></a>Interaction with the standard Samba file attribute mapping</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Samba maps some of the DOS attribute bits (such as "read 
+		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode = 0</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode = 0</tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889446"></a>Interaction with the standard Samba file attribute mapping</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><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.
@@ -4574,10 +4574,10 @@ Before using any of the following options please refer to the man page for <tt c
 		permissions and clicking <span class="guibutton">OK</span> to get back to the 
 		attributes dialog you should always hit <span class="guibutton">Cancel</span> 
 		rather than <span class="guibutton">OK</span> to ensure that your changes 
-		are not overridden.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892060"></a>Common Errors</h2></div></div><div></div></div><p>
+		are not overridden.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2889526"></a>Common Errors</h2></div></div><div></div></div><p>
 File, Directory and Share access problems are very common on the mailing list. The following
 are examples taken from the mailing list in recent times.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892074"></a>Users can not write to a public share</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889540"></a>Users can not write to a public share</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">
 	We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root),
 	and there's a public share, on which everyone needs to have permission to create / modify files, but only
@@ -4643,10 +4643,10 @@ drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
 		</p></div><p>
 		An alternative is to set in the <tt class="filename">smb.conf</tt> entry for the share:
 		</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>force user = jack</tt></i></td></tr><tr><td><i class="parameter"><tt>force group = engr</tt></i></td></tr></table><p>
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892503"></a>I have set force user but Samba still makes <span class="emphasis"><em>root</em></span> the owner of all the files I touch!</h3></div></div><div></div></div><p>
-			When you have a user in <a class="indexterm" name="id2892519"></a><i class="parameter"><tt>admin users</tt></i>, samba will always do file operations for
-			this user as <span class="emphasis"><em>root</em></span>, even if <a class="indexterm" name="id2892539"></a><i class="parameter"><tt>force user</tt></i> has been set.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892555"></a>MS Word with Samba changes owner of file</h3></div></div><div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889969"></a>I have set force user but Samba still makes <span class="emphasis"><em>root</em></span> the owner of all the files I touch!</h3></div></div><div></div></div><p>
+			When you have a user in <a class="indexterm" name="id2889986"></a><i class="parameter"><tt>admin users</tt></i>, samba will always do file operations for
+			this user as <span class="emphasis"><em>root</em></span>, even if <a class="indexterm" name="id2890005"></a><i class="parameter"><tt>force user</tt></i> has been set.
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890022"></a>MS Word with Samba changes owner of file</h3></div></div><div></div></div><p>
 		<span class="emphasis"><em>Question:</em></span> &#8220;<span class="quote">When userB saves a word document that is owned by userA the updated file is now owned by userB.
 		Why is Samba doing this? How do I fix this?</span>&#8221;
 		</p><p>
@@ -4665,10 +4665,10 @@ drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
 		</p><p>
 		These two settings will ensure that all directories and files that get created in the share will be read/writable by the
 		owner and group set on the directory itself.
-		</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter�14.�File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Roseme</span></h3><div class="affiliation"><span class="orgname">HP Oplocks Usage Recommendations Whitepaper<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2892803">Features and Benefits</a></dt><dt><a href="#id2892860">Discussion</a></dt><dd><dl><dt><a href="#id2893002">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2893677">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2893787">Example Configuration</a></dt></dl></dd><dt><a href="#id2894184">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2894410">Workstation Service Entries</a></dt><dt><a href="#id2894437">Server Service Entries</a></dt></dl></dd><dt><a href="#id2894516">Persistent Data Corruption</a></dt><dt><a href="#id2894546">Common Errors</a></dt><dd><dl><dt><a href="#id2894619">locking.tdb error messages</a></dt><dt><a href="#id2894658">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2894680">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2894712">Additional Reading</a></dt></dl></div><p>
+		</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter�14.�File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Roseme</span></h3><div class="affiliation"><span class="orgname">HP Oplocks Usage Recommendations Whitepaper<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2890270">Features and Benefits</a></dt><dt><a href="#id2890336">Discussion</a></dt><dd><dl><dt><a href="#id2890479">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891158">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2891268">Example Configuration</a></dt></dl></dd><dt><a href="#id2891665">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2891896">Workstation Service Entries</a></dt><dt><a href="#id2891924">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892003">Persistent Data Corruption</a></dt><dt><a href="#id2892032">Common Errors</a></dt><dd><dl><dt><a href="#id2892106">locking.tdb error messages</a></dt><dt><a href="#id2892144">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892167">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892198">Additional Reading</a></dt></dl></div><p>
 One area which causes trouble for many network administrators is locking.
 The extent of the problem is readily evident from searches over the internet.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892803"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890270"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Samba provides all the same locking semantics that MS Windows clients expect
 and that MS Windows NT4 / 200x servers provide also.
 </p><p>
@@ -4690,7 +4690,7 @@ settings on the MS Windows client.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Sometimes it is necessary to disable locking control settings BOTH on the Samba
 server as well as on each MS Windows client!
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892860"></a>Discussion</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890336"></a>Discussion</h2></div></div><div></div></div><p>
 There are two types of locking which need to be performed by a SMB server.
 The first is <span class="emphasis"><em>record locking</em></span> which allows a client to lock
 a range of bytes in a open file.  The second is the <span class="emphasis"><em>deny modes</em></span>
@@ -4715,10 +4715,10 @@ a file. Unfortunately with the way fcntl() works this can be slow and may over-s
 the <b class="command">rpc.lockd</b>. 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 <a class="indexterm" name="id2892927"></a><i class="parameter"><tt>strict locking</tt></i> = yes then it
+to by a client, but if you set <a class="indexterm" name="id2890404"></a><i class="parameter"><tt>strict locking</tt></i> = yes then it
 will make lock checking calls on every read and write.
 </p><p>
-You can also disable byte range locking completely using <a class="indexterm" name="id2892947"></a><i class="parameter"><tt>locking</tt></i> = no.
+You can also disable byte range locking completely using <a class="indexterm" name="id2890424"></a><i class="parameter"><tt>locking</tt></i> = 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.
@@ -4729,7 +4729,7 @@ access should be allowed simultaneously with its open. A client may ask for
 <tt class="constant">DENY_NONE</tt>, <tt class="constant">DENY_READ</tt>, 
 <tt class="constant">DENY_WRITE</tt> or <tt class="constant">DENY_ALL</tt>. There are also special compatibility
 modes called <tt class="constant">DENY_FCB</tt> and <tt class="constant">DENY_DOS</tt>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893002"></a>Opportunistic Locking Overview</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890479"></a>Opportunistic Locking Overview</h3></div></div><div></div></div><p>
 Opportunistic locking (Oplocks) is invoked by the Windows file system
 (as opposed to an API) via registry entries (on the server AND client)
 for the purpose of enhancing network performance when accessing a file
@@ -4852,7 +4852,7 @@ In mission critical high availability environments, careful attention
 should be given to opportunistic locking.  Ideally, comprehensive
 testing should be done with all affected applications with oplocks
 enabled and disabled.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893304"></a>Exclusively Accessed Shares</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890780"></a>Exclusively Accessed Shares</h4></div></div><div></div></div><p>
 Opportunistic locking is most effective when it is confined to shares
 that are exclusively accessed by a single user, or by only one user at
 a time.  Because the true value of opportunistic locking is the local
@@ -4861,7 +4861,7 @@ mechanism will cause a delay.
 </p><p>
 Home directories are the most obvious examples of where the performance
 benefit of opportunistic locking can be safely realized.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893335"></a>Multiple-Accessed Shares or Files</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890805"></a>Multiple-Accessed Shares or Files</h4></div></div><div></div></div><p>
 As each additional user accesses a file in a share with opportunistic
 locking enabled, the potential for delays and resulting perceived poor
 performance increases.  When multiple users are accessing a file on a
@@ -4873,7 +4873,7 @@ of the caching user.
 As each additional client attempts to access a file with oplocks set,
 the potential performance improvement is negated and eventually results
 in a performance bottleneck.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893363"></a>UNIX or NFS Client Accessed Files</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890834"></a>UNIX or NFS Client Accessed Files</h4></div></div><div></div></div><p>
 Local UNIX and NFS clients access files without a mandatory
 file locking mechanism.  Thus, these client platforms are incapable of
 initiating an oplock break request from the server to a Windows client
@@ -4883,7 +4883,7 @@ exposes the file to likely data corruption.
 </p><p>
 If files are shared between Windows clients, and either local UNIX 
 or NFS users, then turn opportunistic locking off.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893390"></a>Slow and/or Unreliable Networks</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890860"></a>Slow and/or Unreliable Networks</h4></div></div><div></div></div><p>
 The biggest potential performance improvement for opportunistic locking
 occurs when the client-side caching of reads and writes delivers the
 most differential over sending those reads and writes over the wire.
@@ -4898,7 +4898,7 @@ the most advantageous scenario to utilize opportunistic locking.
 If the network is slow, unreliable, or a WAN, then do not configure
 opportunistic locking if there is any chance of multiple users
 regularly opening the same file.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893423"></a>Multi-User Databases</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890894"></a>Multi-User Databases</h4></div></div><div></div></div><p>
 Multi-user databases clearly pose a risk due to their very nature -
 they are typically heavily accessed by numerous users at random
 intervals.  Placing a multi-user database on a share with opportunistic
@@ -4906,7 +4906,7 @@ locking enabled will likely result in a locking management bottleneck
 on the Samba server.  Whether the database application is developed
 in-house or a commercially available product, ensure that the share
 has opportunistic locking disabled.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893444"></a>PDM Data Shares</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890914"></a>PDM Data Shares</h4></div></div><div></div></div><p>
 Process Data Management (PDM) applications such as IMAN, Enovia, and
 Clearcase, are increasing in usage with Windows client platforms, and
 therefore SMB data stores.  PDM applications manage multi-user
@@ -4919,8 +4919,8 @@ application and PDM server to negotiate and maintain.  It is
 appropriate to eliminate the client OS from any caching tasks, and the
 server from any oplock management, by disabling opportunistic locking on
 the share.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893471"></a>Beware of Force User</h4></div></div><div></div></div><p>
-Samba includes an <tt class="filename">smb.conf</tt> parameter called <a class="indexterm" name="id2893490"></a><i class="parameter"><tt>force user</tt></i> that changes
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2890942"></a>Beware of Force User</h4></div></div><div></div></div><p>
+Samba includes an <tt class="filename">smb.conf</tt> parameter called <a class="indexterm" name="id2890960"></a><i class="parameter"><tt>force user</tt></i> that changes
 the user accessing a share from the incoming user to whatever user is
 defined by the smb.conf variable.  If opportunistic locking is enabled
 on a share, the change in user access causes an oplock break to be sent
@@ -4932,26 +4932,26 @@ to overcome the lost oplock break.
 </p><p>
 Avoid the combination of the following: 
 </p><div class="itemizedlist"><ul type="disc"><li><p>
-	<a class="indexterm" name="id2893526"></a><i class="parameter"><tt>force user</tt></i> in the <tt class="filename">smb.conf</tt> share configuration.
+	<a class="indexterm" name="id2891007"></a><i class="parameter"><tt>force user</tt></i> in the <tt class="filename">smb.conf</tt> share configuration.
 	</p></li><li><p>
 	Slow or unreliable networks
 	</p></li><li><p>
 	Opportunistic Locking Enabled
-	</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893563"></a>Advanced Samba Opportunistic Locking Parameters</h4></div></div><div></div></div><p>
+	</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891044"></a>Advanced Samba Opportunistic Locking Parameters</h4></div></div><div></div></div><p>
 Samba provides opportunistic locking parameters that allow the
 administrator to adjust various properties of the oplock mechanism to
 account for timing and usage levels.  These parameters provide good
 versatility for implementing oplocks in environments where they would
 likely cause problems.  The parameters are: 
-<a class="indexterm" name="id2893580"></a><i class="parameter"><tt>oplock break wait time</tt></i>,
-<a class="indexterm" name="id2893594"></a><i class="parameter"><tt>oplock contention limit</tt></i>.
+<a class="indexterm" name="id2891061"></a><i class="parameter"><tt>oplock break wait time</tt></i>,
+<a class="indexterm" name="id2891075"></a><i class="parameter"><tt>oplock contention limit</tt></i>.
 </p><p>
 For most users, administrators, and environments, if these parameters
 are required, then the better option is to simply turn oplocks off.
 The samba SWAT help text for both parameters reads "DO NOT CHANGE THIS
 PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE."
 This is good advice.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893620"></a>Mission Critical High Availability</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891101"></a>Mission Critical High Availability</h4></div></div><div></div></div><p>
 In mission critical high availability environments, data integrity is
 often a priority.  Complex and expensive configurations are implemented
 to ensure that if a client loses connectivity with a file server, a
@@ -4981,7 +4981,7 @@ In mission critical high availability environments, careful attention
 should be given to opportunistic locking.  Ideally, comprehensive
 testing should be done with all affected applications with oplocks
 enabled and disabled.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893677"></a>Samba Opportunistic Locking Control</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891158"></a>Samba Opportunistic Locking Control</h2></div></div><div></div></div><p>
 Opportunistic Locking is a unique Windows file locking feature.  It is
 not really file locking, but is included in most discussions of Windows
 file locking, so is considered a de facto locking feature.
@@ -5031,9 +5031,9 @@ of your client sending oplock breaks and will instead want to disable oplocks fo
 </p><p>
 Another factor to consider is the perceived performance of file access. If oplocks provide no
 measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893787"></a>Example Configuration</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891268"></a>Example Configuration</h3></div></div><div></div></div><p>
 In the following we examine two distinct aspects of Samba locking controls.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893800"></a>Disabling Oplocks</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891281"></a>Disabling Oplocks</h4></div></div><div></div></div><p>
 You can disable oplocks on a per-share basis with the following:
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[acctdata]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplocks = False</tt></i></td></tr><tr><td><i class="parameter"><tt>level2 oplocks = False</tt></i></td></tr></table><p>
@@ -5047,7 +5047,7 @@ Alternately, you could disable oplocks on a per-file basis within the share:
 </p><p>
 If you are experiencing problems with oplocks as apparent from Samba's log entries,
 you may want to play it safe and disable oplocks and level2 oplocks.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893897"></a>Disabling Kernel OpLocks</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891378"></a>Disabling Kernel OpLocks</h4></div></div><div></div></div><p>
 Kernel OpLocks is an <tt class="filename">smb.conf</tt> parameter that notifies Samba (if
 the UNIX kernel has the capability to send a Windows client an oplock
 break) when a UNIX process is attempting to open the file that is
@@ -5075,9 +5075,9 @@ caching without the risk of data corruption.  Veto Oplocks can be
 enabled on a per-share basis, or globally for the entire server, in the
 <tt class="filename">smb.conf</tt> file:
 </p><p>
-</p><div class="example"><a name="id2893990"></a><p class="title"><b>Example�14.1.�Share with some files oplocked</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /filename.htm/*.txt/</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /*.exe/filename.ext/</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2891471"></a><p class="title"><b>Example�14.1.�Share with some files oplocked</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /filename.htm/*.txt/</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /*.exe/filename.ext/</tt></i></td></tr></table></div><p>
 </p><p>
-	<a class="indexterm" name="id2894044"></a><i class="parameter"><tt>oplock break wait time</tt></i> is an <tt class="filename">smb.conf</tt> parameter that adjusts the time
+	<a class="indexterm" name="id2891525"></a><i class="parameter"><tt>oplock break wait time</tt></i> is an <tt class="filename">smb.conf</tt> parameter that adjusts the time
 interval for Samba to reply to an oplock break request.  Samba
 recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND
 UNDERSTOOD THE SAMBA OPLOCK CODE."  Oplock Break Wait Time can only be
@@ -5093,8 +5093,8 @@ HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE."  Oplock Break
 Contention Limit can be enable on a per-share basis, or globally for
 the entire server, in the <tt class="filename">smb.conf</tt> file:
 </p><p>
-	</p><div class="example"><a name="id2894131"></a><p class="title"><b>Example�14.2.�</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit =  2 (default)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit =  2 (default)</tt></i></td></tr></table></div><p>
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894184"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><div></div></div><p>
+	</p><div class="example"><a name="id2891612"></a><p class="title"><b>Example�14.2.�</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit =  2 (default)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit =  2 (default)</tt></i></td></tr></table></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891665"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><div></div></div><p>
 There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP
 workstation computer that can affect any application attempting to access shared database files
 across a network. This is a result of a default setting configured in the Windows 2000/XP
@@ -5186,7 +5186,7 @@ An illustration of how level II oplocks work:
 	station holds any oplock on the file. Because the workstations can have no cached
 	writes or locks at this point, they need not respond to the break-to-none advisory;
 	all they need do is invalidate locally cashed read-ahead data.
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894410"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting">
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891896"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting">
 	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanWorkstation\Parameters
 
@@ -5195,7 +5195,7 @@ An illustration of how level II oplocks work:
 </pre><p>
 Indicates whether the redirector should use opportunistic-locking (oplock) performance
 enhancement. This parameter should be disabled only to isolate problems.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894437"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting">
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891924"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting">
 	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanServer\Parameters
 
@@ -5224,7 +5224,7 @@ the server disables raw I/O and opportunistic locking for this connection.
 Specifies the time that the server waits for a client to respond to an oplock break
 request. Smaller values can allow detection of crashed clients more quickly but can
 potentially cause loss of cached data.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894516"></a>Persistent Data Corruption</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892003"></a>Persistent Data Corruption</h2></div></div><div></div></div><p>
 If you have applied all of the settings discussed in this chapter but data corruption problems
 and other symptoms persist, here are some additional things to check out:
 </p><p>
@@ -5235,7 +5235,7 @@ rebuild the data files in question. This involves creating a new data file with
 same definition as the file to be rebuilt and transferring the data from the old file
 to the new one. There are several known methods for doing this that can be found in
 our Knowledge Base.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894546"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892032"></a>Common Errors</h2></div></div><div></div></div><p>
 In some sites locking problems surface as soon as a server is installed, in other sites
 locking problems may not surface for a long time. Almost without exception, when a locking
 problem does surface it will cause embarrassment and potential data corruption.
@@ -5265,7 +5265,7 @@ so far:
 	report on https://bugzilla.samba.org without delay. Make sure that you give as much
 	information as you possibly can to help isolate the cause and to allow reproduction
 	of the problem (an essential step in problem isolation and correction).
-	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894619"></a>locking.tdb error messages</h3></div></div><div></div></div><p>
+	</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892106"></a>locking.tdb error messages</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">
 	We are seeing lots of errors in the samba logs like:
 </span>&#8221;
@@ -5278,10 +5278,10 @@ tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
 	</span>&#8221;
 	</p><p>
 	Corrupted tdb.  Stop all instances of smbd, delete locking.tdb, restart smbd.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894658"></a>Problems saving files in MS Office on Windows XP</h3></div></div><div></div></div><p>This is a bug in Windows XP. More information can be 
-			found in <a href="http://support.microsoft.com/?id=812937" target="_top">Microsoft Knowledge Base article 812937</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894680"></a>Long delays deleting files over network with XP SP1</h3></div></div><div></div></div><p>&#8220;<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied</span>&#8221;</p><p>This is a bug in Windows XP. More information can be 
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892144"></a>Problems saving files in MS Office on Windows XP</h3></div></div><div></div></div><p>This is a bug in Windows XP. More information can be 
+			found in <a href="http://support.microsoft.com/?id=812937" target="_top">Microsoft Knowledge Base article 812937</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892167"></a>Long delays deleting files over network with XP SP1</h3></div></div><div></div></div><p>&#8220;<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied</span>&#8221;</p><p>This is a bug in Windows XP. More information can be 
 			found in <a href="http://support.microsoft.com/?id=811492" target="_top">
-				Microsoft Knowledge Base article 811492</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894712"></a>Additional Reading</h2></div></div><div></div></div><p>
+				Microsoft Knowledge Base article 811492</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892198"></a>Additional Reading</h2></div></div><div></div></div><p>
 You may want to check for an updated version of this white paper on our Web site from
 time to time. Many of our white papers are updated as information changes. For those papers,
 the Last Edited date is always at the top of the paper.
@@ -5301,7 +5301,7 @@ Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default
 </p><p>
 Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT",
  Microsoft Corporation, April 1995, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</a>.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter�15.�Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 26, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2894878">Introduction</a></dt><dt><a href="#id2894910">Features and Benefits</a></dt><dt><a href="#id2894983">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2895003">Using host based protection</a></dt><dt><a href="#id2895102">User based protection</a></dt><dt><a href="#id2895162">Using interface protection</a></dt><dt><a href="#id2895230">Using a firewall</a></dt><dt><a href="#id2895287">Using a IPC$ share deny</a></dt><dt><a href="#id2895375">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2895433">Upgrading Samba</a></dt><dt><a href="#id2895457">Common Errors</a></dt><dd><dl><dt><a href="#id2895476">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2895500">Why can users access home directories of other users?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894878"></a>Introduction</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter�15.�Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 26, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2892365">Introduction</a></dt><dt><a href="#id2892398">Features and Benefits</a></dt><dt><a href="#id2892471">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2892490">Using host based protection</a></dt><dt><a href="#id2892590">User based protection</a></dt><dt><a href="#id2892650">Using interface protection</a></dt><dt><a href="#id2892717">Using a firewall</a></dt><dt><a href="#id2892774">Using a IPC$ share deny</a></dt><dt><a href="#id2892867">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2892926">Upgrading Samba</a></dt><dt><a href="#id2892950">Common Errors</a></dt><dd><dl><dt><a href="#id2892968">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2892992">Why can users access home directories of other users?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892365"></a>Introduction</h2></div></div><div></div></div><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.
@@ -5313,7 +5313,7 @@ on it!"
 Security concerns are just like that: You need to know a little about the subject to appreciate
 how obvious most of it really is. The challenge for most of us is to discover that first morsel
 of knowledge with which we may unlock the secrets of the masters.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894910"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892398"></a>Features and Benefits</h2></div></div><div></div></div><p>
 There are three level at which security principals must be observed in order to render a site
 at least moderately secure. These are: the perimeter firewall, the configuration of the host
 server that is running Samba, and Samba itself.
@@ -5332,21 +5332,21 @@ TCP/IP connections.
 Another method by which Samba may be secured is by way of setting Access Control Entries in an Access 
 Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access
 Control.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894983"></a>Technical Discussion of Protective Measures and Issues</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892471"></a>Technical Discussion of Protective Measures and Issues</h2></div></div><div></div></div><p>
 The key challenge of security is the fact that protective measures suffice at best
 only to close the door on known exploits and breach techniques. Never assume that
 because you have followed these few measures that the Samba server is now an impenetrable
 fortress! Given the history of information systems so far, it is only a matter of time
 before someone will find yet another vulnerability.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895003"></a>Using host based protection</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892490"></a>Using host based protection</h3></div></div><div></div></div><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 <a class="indexterm" name="id2895024"></a><i class="parameter"><tt>hosts allow</tt></i> and
-	<a class="indexterm" name="id2895039"></a><i class="parameter"><tt>hosts deny</tt></i> options in the Samba <tt class="filename">smb.conf</tt> configuration file to only
+	One of the simplest fixes in this case is to use the <a class="indexterm" name="id2892512"></a><i class="parameter"><tt>hosts allow</tt></i> and
+	<a class="indexterm" name="id2892526"></a><i class="parameter"><tt>hosts deny</tt></i> 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><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0/0</tt></i></td></tr></table><p>
@@ -5355,13 +5355,13 @@ before someone will find yet another vulnerability.
 	192.168.3. All other connections will be refused as soon
 	as the client sends its first packet. The refusal will be marked as a
 	<span class="errorname">not listening on called name</span> error.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895102"></a>User based protection</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892590"></a>User based protection</h3></div></div><div></div></div><p>
 	If you want to restrict access to your server to valid users only then the following
 	method may be of use. In the <tt class="filename">smb.conf</tt> <i class="parameter"><tt>[global]</tt></i> section put:
 	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>valid users = @smbusers, jacko</tt></i></td></tr></table><p>
 	What this does is, it restricts all server access to either the user <span class="emphasis"><em>jacko</em></span>
 	or to members of the system group <span class="emphasis"><em>smbusers</em></span>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895162"></a>Using interface protection</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892650"></a>Using interface protection</h3></div></div><div></div></div><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
@@ -5380,7 +5380,7 @@ before someone will find yet another vulnerability.
 	connection refused reply. In that case no Samba code is run at all as
 	the operating system has been told not to pass connections from that
 	interface to any samba process.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895230"></a>Using a firewall</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892717"></a>Using a firewall</h3></div></div><div></div></div><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
@@ -5393,7 +5393,7 @@ before someone will find yet another vulnerability.
 	The last one is important as many older firewall setups may not be
 	aware of it, given that this port was only added to the protocol in
 	recent years. 
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895287"></a>Using a IPC$ share deny</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892774"></a>Using a IPC$ share deny</h3></div></div><div></div></div><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
@@ -5416,7 +5416,7 @@ before someone will find yet another vulnerability.
 	</p><p>
 	This is not recommended unless you cannot use one of the other
 	methods listed above for some reason.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895375"></a>NTLMv2 Security</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892867"></a>NTLMv2 Security</h3></div></div><div></div></div><p>
 	To configure NTLMv2 authentication the following registry keys are worth knowing about:
 	</p><p>
 		</p><pre class="screen">
@@ -5436,24 +5436,24 @@ before someone will find yet another vulnerability.
 		0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
 		NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
 		session security is not negotiated.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895433"></a>Upgrading Samba</h2></div></div><div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892926"></a>Upgrading Samba</h2></div></div><div></div></div><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. Check with your OS vendor for OS specific upgrades.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895457"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892950"></a>Common Errors</h2></div></div><div></div></div><p>
 If all of samba and host platform configuration were really as intuitive as one might like then this
 section would not be necessary. Security issues are often vexing for a support person to resolve, not
 because of the complexity of the problem, but for reason that most administrators who post what turns
 out to be a security problem request are totally convinced that the problem is with Samba.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895476"></a>Smbclient works on localhost, but the network is dead</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892968"></a>Smbclient works on localhost, but the network is dead</h3></div></div><div></div></div><p>
 	This is a very common problem. Red Hat Linux (as do others) will install a default firewall.
 	With the default firewall in place only traffic on the loopback adapter (IP address 127.0.0.1)
 	will be allowed through the firewall.
 	</p><p>
 	The solution is either to remove the firewall (stop it) or to modify the firewall script to
 	allow SMB networking traffic through. See section above in this chapter.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895500"></a>Why can users access home directories of other users?</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892992"></a>Why can users access home directories of other users?</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">
 	We are unable to keep individual users from mapping to any other user's
 	home directory once they have supplied a valid password! They only need
@@ -5482,7 +5482,7 @@ out to be a security problem request are totally convinced that the problem is w
 	the policies and permissions he or she desires.
 	</p><p>
 	Samba does allow the setup you require when you have set the
-	<a class="indexterm" name="id2895560"></a><i class="parameter"><tt>only user</tt></i> = yes option on the share, is that you have not set the
+	<a class="indexterm" name="id2893052"></a><i class="parameter"><tt>only user</tt></i> = yes option on the share, is that you have not set the
 	valid users list for the share.
 	</p><p>
 	Note that only user works in conjunction with the users= list,
@@ -5492,14 +5492,14 @@ out to be a security problem request are totally convinced that the problem is w
 	</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>valid users = %S</tt></i></td></tr></table><p>
 	to the definition of the <i class="parameter"><tt>[homes]</tt></i> share, as recommended in
 	the <tt class="filename">smb.conf</tt> man page.
-	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter�16.�Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Rafal</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:mimir@samba.org">mimir@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2895790">Features and Benefits</a></dt><dt><a href="#id2895819">Trust Relationship Background</a></dt><dt><a href="#id2895908">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2895935">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2896007">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2896054">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2896233">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2896417">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2896555">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2896661">Common Errors</a></dt></dl></div><a class="indexterm" name="id2895770"></a><p>
+	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter�16.�Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Rafal</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:mimir@samba.org">mimir@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2893283">Features and Benefits</a></dt><dt><a href="#id2893311">Trust Relationship Background</a></dt><dt><a href="#id2893400">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2893428">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2893500">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2893547">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2893725">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2893918">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894055">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894162">Common Errors</a></dt></dl></div><a class="indexterm" name="id2893263"></a><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 trust NT4 (and vice versa), as well as to create Samba3-to-Samba3 
 trusts.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895790"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893283"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4 style
 trust relationships. This imparts to Samba similar scalability as is possible with
 MS Windows NT4.
@@ -5509,7 +5509,7 @@ database such as LDAP, and given it's ability to run in Primary as well as Backu
 modes, the administrator would be well advised to consider alternatives to the use of
 Interdomain trusts simply because by the very nature of how this works it is fragile.
 That was, after all, a key reason for the development and adoption of Microsoft Active Directory.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895819"></a>Trust Relationship Background</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893311"></a>Trust Relationship Background</h2></div></div><div></div></div><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 namespace that results from
@@ -5545,13 +5545,13 @@ domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each
 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895908"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893400"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><div></div></div><p>
 There are two steps to creating an interdomain trust relationship.  To effect a two-way trust
 relationship it is necessary for each domain administrator to create a trust account for the 
 other domain to use in verifying security credentials.
 
-<a class="indexterm" name="id2895924"></a>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895935"></a>Creating an NT4 Domain Trust</h3></div></div><div></div></div><p>
+<a class="indexterm" name="id2893417"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893428"></a>Creating an NT4 Domain Trust</h3></div></div><div></div></div><p>
 For MS Windows NT4, all domain trust relationships are configured using the 
 <span class="application">Domain User Manager</span>. This is done from the Domain User Manager Policies
 entry on the menu bar. From the <span class="guimenu">Policy</span> menu, select
@@ -5562,15 +5562,15 @@ to enter the name of the remote domain that will be able to assign access rights
 your domain.  You will also need to enter a password for this trust relationship, which the 
 trusting domain will use when authenticating users from the trusted domain.
 The password needs to be typed twice (for standard confirmation).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896007"></a>Completing an NT4 Domain Trust</h3></div></div><div></div></div><p>
-<a class="indexterm" name="id2896018"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893500"></a>Completing an NT4 Domain Trust</h3></div></div><div></div></div><p>
+<a class="indexterm" name="id2893511"></a>
 A trust relationship will work only when the other (trusting) domain makes the appropriate connections
 with the trusted domain. To consummate the trust relationship the administrator will launch the
 Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
 <span class="guibutton">Add</span> button that is next to the box that is labelled 
 <span class="guilabel">Trusted Domains</span>. 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 class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896054"></a>Inter-Domain Trust Facilities</h3></div></div><div></div></div><a class="indexterm" name="id2896062"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893547"></a>Inter-Domain Trust Facilities</h3></div></div><div></div></div><a class="indexterm" name="id2893555"></a><p>
 A two-way trust relationship is created when two one-way trusts are created, one in each direction.
 Where a one-way trust has been established between two MS Windows NT4 domains (let's call them
 DomA and DomB) the following facilities are created:
@@ -5610,7 +5610,7 @@ DomA and DomB) the following facilities are created:
 	</p></li><li><p>
 	Global Groups from the trusted domain CAN be made members in Local Groups on
 	MS Windows domain member machines.
-	</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896233"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><div></div></div><p>
+	</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893725"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><div></div></div><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.
@@ -5648,7 +5648,7 @@ After the command returns successfully, you can look at the entry for the new ac
 (in the standard way as appropriate for your configuration) and see that account's name is
 really RUMBA$ and it has the 'I' flag set in the flags field. Now you're ready to confirm
 the trust by establishing it from Windows NT Server.
-</p><a class="indexterm" name="id2896356"></a><p>
+</p><a class="indexterm" name="id2893856"></a><p>
 Open <span class="application">User Manager for Domains</span> and from the
 <span class="guimenu">Policies</span> menu, select <span class="guimenuitem">Trust Relationships...</span>.
 Right beside the <span class="guilabel">Trusted domains</span> list box press the 
@@ -5658,12 +5658,12 @@ the name of the remote domain, and the password used at the time of account crea
 Press OK and, if everything went without incident, you will see 
 <tt class="computeroutput">Trusted domain relationship successfully 
 established</tt> message.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896417"></a>Samba as the Trusting Domain</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893918"></a>Samba as the Trusting Domain</h3></div></div><div></div></div><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>
 The very first step is to add an account for the SAMBA domain on RUMBA's PDC.
-</p><a class="indexterm" name="id2896438"></a><p>
+</p><a class="indexterm" name="id2893939"></a><p>
 Launch the <span class="application">Domain User Manager</span>, then from the menu select
 <span class="guimenu">Policies</span>, <span class="guimenuitem">Trust Relationships</span>.
 Now, next to the <span class="guilabel">Trusted Domains</span> box press the <span class="guibutton">Add</span>
@@ -5689,7 +5689,7 @@ Congratulations! Your trust relationship has just been established.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Note that you have to run this command as root because you must have write access to
 the <tt class="filename">secrets.tdb</tt> file.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896555"></a>NT4-style Domain Trusts with Windows 2000</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894055"></a>NT4-style Domain Trusts with Windows 2000</h2></div></div><div></div></div><p>
 Although <span class="application">Domain User Manager</span> is not present in Windows 2000, it is 
 also possible to establish an NT4-style trust relationship with a Windows 2000 domain 
 controller running in mixed mode as the trusting server.  It should also be possible for 
@@ -5710,13 +5710,13 @@ will be prompted for the trusted domain name and the relationship password.  Pre
 after a moment, Active Directory will respond with <tt class="computeroutput">The trusted domain has 
 been added and the trust has been verified.</tt>  Your Samba users can now be 
 granted acess to resources in the AD domain.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896661"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894162"></a>Common Errors</h2></div></div><div></div></div><p>
 Interdomain trust relationships should NOT be attempted on networks that are unstable
 or that suffer regular outages. Network stability and integrity are key concerns with
 distributed trusted domains.
 </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="msdfs"></a>Chapter�17.�Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Shirish</span> <span class="surname">Kalele</span></h3><div class="affiliation"><span class="orgname">Samba Team &amp; Veritas Software<br></span><div class="address"><p><br>
 				<tt class="email">&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt><br>
-			</p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2896731">Features and Benefits</a></dt><dt><a href="#id2897006">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896731"></a>Features and Benefits</h2></div></div><div></div></div><p>
+			</p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2894231">Features and Benefits</a></dt><dt><a href="#id2894506">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894231"></a>Features and Benefits</h2></div></div><div></div></div><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
@@ -5730,9 +5730,9 @@ distributed trusted domains.
 	</p><p>
 		To enable SMB-based DFS for Samba, configure it with the <tt class="option">--with-msdfs</tt>
 	option. Once built, a Samba server can be made a DFS server by setting the global 
-	boolean <a class="indexterm" name="id2896778"></a><i class="parameter"><tt>host msdfs</tt></i>
+	boolean <a class="indexterm" name="id2894278"></a><i class="parameter"><tt>host msdfs</tt></i>
 	parameter in the <tt class="filename">smb.conf</tt> file. You designate a share as a DFS
-	root using the share level boolean <a class="indexterm" name="id2896800"></a><i class="parameter"><tt>msdfs root</tt></i> parameter. A DFS root directory on Samba hosts DFS
+	root using the share level boolean <a class="indexterm" name="id2894300"></a><i class="parameter"><tt>msdfs root</tt></i> 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-&gt;msdfs:storage1\share1</tt> in the share directory acts
 	as the DFS junction. When DFS-aware clients attempt to access the junction link,
@@ -5741,7 +5741,7 @@ distributed trusted domains.
 	DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.
 	</p><p>
 	Here's an example of setting up a DFS tree on a Samba server.
-	</p><div class="example"><a name="id2896842"></a><p class="title"><b>Example�17.1.�smb.conf with DFS configured</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>host msdfs   = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[dfs]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export/dfsroot</tt></i></td></tr><tr><td><i class="parameter"><tt>msdfs root = yes</tt></i></td></tr></table></div><p>In the /export/dfsroot directory we set up our DFS links to 
+	</p><div class="example"><a name="id2894342"></a><p class="title"><b>Example�17.1.�smb.conf with DFS configured</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>host msdfs   = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[dfs]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export/dfsroot</tt></i></td></tr><tr><td><i class="parameter"><tt>msdfs root = yes</tt></i></td></tr></table></div><p>In the /export/dfsroot directory we set up our DFS links to 
 	other servers on the network.</p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>cd /export/dfsroot</tt></b>
 <tt class="prompt">root# </tt><b class="userinput"><tt>chown root /export/dfsroot</tt></b>
@@ -5757,16 +5757,16 @@ distributed trusted domains.
 	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><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2897006"></a>Common Errors</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted 
+	takes users directly to the appropriate shares on the network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894506"></a>Common Errors</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><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><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter�18.�Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2897126">Features and Benefits</a></dt><dt><a href="#id2897192">Technical Introduction</a></dt><dd><dl><dt><a href="#id2897230">What happens if you send a Job from a Client</a></dt><dt><a href="#id2897302">Printing Related Configuration Parameters</a></dt><dt><a href="#id2897387">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2897853">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2898017">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2898105">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2898438">Extended Sample Configuration to Print</a></dt><dt><a href="#id2898769">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2898782">The [global] Section</a></dt><dt><a href="#id2899274">The [printers] Section</a></dt><dt><a href="#id2899717">Any [my_printer_name] Section</a></dt><dt><a href="#id2900032">Print Commands</a></dt><dt><a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2900758">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2901088">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2901237">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2901389">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2901502">Creating the [print$] Share</a></dt><dt><a href="#id2901686">Parameters in the [print$] Section</a></dt><dt><a href="#id2901973">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2902140">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2902234">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2902432">Setting Drivers for existing Printers with
-rpcclient</a></dt></dl></dd><dt><a href="#id2904055">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2904073">The first Client Driver Installation</a></dt><dt><a href="#id2904269">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2904576">Further Client Driver Install Procedures</a></dt><dt><a href="#id2904670">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2904838">Other Gotchas</a></dt><dd><dl><dt><a href="#id2904870">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2905319">Supporting large Numbers of Printers</a></dt><dt><a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2905915">Weird Error Message Cannot connect under a
-different Name</a></dt><dt><a href="#id2906013">Be careful when assembling Driver Files</a></dt><dt><a href="#id2906300">Samba and Printer Ports</a></dt><dt><a href="#id2906377">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2906398">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2906443">What is Imprints?</a></dt><dt><a href="#id2906484">Creating Printer Driver Packages</a></dt><dt><a href="#id2906504">The Imprints Server</a></dt><dt><a href="#id2906528">The Installation Client</a></dt></dl></dd><dt><a href="#id2906681">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2907000">The addprinter command</a></dt><dt><a href="#id2907046">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2907213">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2907227">Common Errors</a></dt><dd><dl><dt><a href="#id2907234">I give my root password but I don't get access</a></dt><dt><a href="#id2907268">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2897126"></a>Features and Benefits</h2></div></div><div></div></div><p>
+		modify the symbolic links in the directory.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter�18.�Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2894626">Features and Benefits</a></dt><dt><a href="#id2894693">Technical Introduction</a></dt><dd><dl><dt><a href="#id2894730">What happens if you send a Job from a Client</a></dt><dt><a href="#id2894801">Printing Related Configuration Parameters</a></dt><dt><a href="#id2894888">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2895354">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2895518">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2895606">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2895939">Extended Sample Configuration to Print</a></dt><dt><a href="#id2896270">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2896282">The [global] Section</a></dt><dt><a href="#id2896767">The [printers] Section</a></dt><dt><a href="#id2897210">Any [my_printer_name] Section</a></dt><dt><a href="#id2897534">Print Commands</a></dt><dt><a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2898261">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2898591">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2898740">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2898892">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2899004">Creating the [print$] Share</a></dt><dt><a href="#id2899189">Parameters in the [print$] Section</a></dt><dt><a href="#id2899475">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2899643">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2899736">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2899935">Setting Drivers for existing Printers with
+rpcclient</a></dt></dl></dd><dt><a href="#id2901625">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2901643">The first Client Driver Installation</a></dt><dt><a href="#id2901839">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2902136">Further Client Driver Install Procedures</a></dt><dt><a href="#id2902231">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2902399">Other Gotchas</a></dt><dd><dl><dt><a href="#id2902431">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2902874">Supporting large Numbers of Printers</a></dt><dt><a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2903470">Weird Error Message Cannot connect under a
+different Name</a></dt><dt><a href="#id2903569">Be careful when assembling Driver Files</a></dt><dt><a href="#id2903854">Samba and Printer Ports</a></dt><dt><a href="#id2903932">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2903954">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2903998">What is Imprints?</a></dt><dt><a href="#id2904040">Creating Printer Driver Packages</a></dt><dt><a href="#id2904059">The Imprints Server</a></dt><dt><a href="#id2904083">The Installation Client</a></dt></dl></dd><dt><a href="#id2904236">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2904556">The addprinter command</a></dt><dt><a href="#id2904602">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2904779">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2904793">Common Errors</a></dt><dd><dl><dt><a href="#id2904800">I give my root password but I don't get access</a></dt><dt><a href="#id2904834">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894626"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Printing is often a mission-critical service for the users.  Samba can
 provide this service reliably and seamlessly for a client network
 consisting of Windows workstations.
@@ -5802,7 +5802,7 @@ Professional clients. Where this document describes the responses to
 commands given, bear in mind that Windows 2000 clients are very
 similar, but may differ in details. Windows NT is somewhat different
 again.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2897192"></a>Technical Introduction</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894693"></a>Technical Introduction</h2></div></div><div></div></div><p>
 Samba's printing support always relies on the installed print
 subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes
 printfiles from Windows (or other SMB) clients and passes them to the
@@ -5820,7 +5820,7 @@ the next chapter covers in great detail the more modern
 </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>CUPS users, be warned: don't just jump on to the next
 chapter. You might miss important information contained only
 here!</p></div><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897230"></a>What happens if you send a Job from a Client</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894730"></a>What happens if you send a Job from a Client</h3></div></div><div></div></div><p>
 To successfully print a job from a Windows client via a Samba
 print server to a UNIX printer, there are 6 (potentially 7)
 stages:
@@ -5828,7 +5828,7 @@ stages:
 into Samba's spooling area</p></li><li><p>Windows closes the connection again</p></li><li><p>Samba invokes the print command to hand the file over
 to the UNIX print subsystem's spooling area</p></li><li><p>The UNIX print subsystem processes the print
 job</p></li><li><p>The printfile may need to be explicitly deleted
-from the Samba spooling area.</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897302"></a>Printing Related Configuration Parameters</h3></div></div><div></div></div><p>
+from the Samba spooling area.</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894801"></a>Printing Related Configuration Parameters</h3></div></div><div></div></div><p>
 There are a number of configuration parameters in
  controlling Samba's printing
 behaviour. Please also refer to the man page for smb.conf to
@@ -5842,43 +5842,43 @@ behaviour of all individual or service level shares (provided those
 don't have a different setting defined for the same parameter, thus
 overriding the global default).</p></dd><dt><span class="term">Global Parameters</span></dt><dd><p>These <span class="emphasis"><em>may not</em></span> go into individual
 shares.  If they go in by error, the "testparm" utility can discover
-this (if you run it) and tell you so.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897387"></a>Parameters Recommended for Use</h3></div></div><div></div></div><p>The following <tt class="filename">smb.conf</tt> parameters directly
+this (if you run it) and tell you so.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894888"></a>Parameters Recommended for Use</h3></div></div><div></div></div><p>The following <tt class="filename">smb.conf</tt> parameters directly
 related to printing are used in Samba. See also the
 <tt class="filename">smb.conf</tt> man page for detailed explanations:
-</p><p>Global level parameters: <a class="indexterm" name="id2897417"></a><i class="parameter"><tt>addprinter command</tt></i>, 
-<a class="indexterm" name="id2897432"></a><i class="parameter"><tt>deleteprinter command</tt></i>,
-<a class="indexterm" name="id2897446"></a><i class="parameter"><tt>disable spoolss</tt></i>,
-<a class="indexterm" name="id2897460"></a><i class="parameter"><tt>enumports command</tt></i>,
-<a class="indexterm" name="id2897474"></a><i class="parameter"><tt>load printers</tt></i>,
-<a class="indexterm" name="id2897488"></a><i class="parameter"><tt>lpq cache time</tt></i>,
-<a class="indexterm" name="id2897502"></a><i class="parameter"><tt>os2 driver map</tt></i>,
-<a class="indexterm" name="id2897516"></a><i class="parameter"><tt>printcap name</tt></i>, <a class="indexterm" name="id2897530"></a><i class="parameter"><tt>printcap</tt></i>,
-<a class="indexterm" name="id2897543"></a><i class="parameter"><tt>show add printer wizard</tt></i>,
-<a class="indexterm" name="id2897558"></a><i class="parameter"><tt>total print jobs</tt></i>,
-<a class="indexterm" name="id2897572"></a><i class="parameter"><tt>use client driver</tt></i>.
-</p><p>Service level parameters: <a class="indexterm" name="id2897590"></a><i class="parameter"><tt>hosts allow</tt></i>,
-<a class="indexterm" name="id2897604"></a><i class="parameter"><tt>hosts deny</tt></i>,
-<a class="indexterm" name="id2897617"></a><i class="parameter"><tt>lppause command</tt></i>,
-<a class="indexterm" name="id2897632"></a><i class="parameter"><tt>lpq command</tt></i>,
-<a class="indexterm" name="id2897645"></a><i class="parameter"><tt>lpresume command</tt></i>,
-<a class="indexterm" name="id2897659"></a><i class="parameter"><tt>lprm command</tt></i>,
-<a class="indexterm" name="id2897673"></a><i class="parameter"><tt>max print jobs</tt></i>,
-<a class="indexterm" name="id2897687"></a><i class="parameter"><tt>min print space</tt></i>,
-<a class="indexterm" name="id2897701"></a><i class="parameter"><tt>print command</tt></i>,
-<a class="indexterm" name="id2897715"></a><i class="parameter"><tt>printable</tt></i>, <a class="indexterm" name="id2897729"></a><i class="parameter"><tt>print ok </tt></i>,
-<a class="indexterm" name="id2897742"></a><i class="parameter"><tt>printer name</tt></i>, <a class="indexterm" name="id2897757"></a><i class="parameter"><tt>printer</tt></i>,
-<a class="indexterm" name="id2897770"></a><i class="parameter"><tt>printer admin</tt></i>,
-<a class="indexterm" name="id2897784"></a><i class="parameter"><tt>printing</tt></i> = [cups|bsd|lprng...],
-<a class="indexterm" name="id2897798"></a><i class="parameter"><tt>queuepause command</tt></i>,
-<a class="indexterm" name="id2897812"></a><i class="parameter"><tt>queueresume command</tt></i>,
-<a class="indexterm" name="id2897826"></a><i class="parameter"><tt>total print jobs</tt></i>.
+</p><p>Global level parameters: <a class="indexterm" name="id2894917"></a><i class="parameter"><tt>addprinter command</tt></i>, 
+<a class="indexterm" name="id2894932"></a><i class="parameter"><tt>deleteprinter command</tt></i>,
+<a class="indexterm" name="id2894946"></a><i class="parameter"><tt>disable spoolss</tt></i>,
+<a class="indexterm" name="id2894960"></a><i class="parameter"><tt>enumports command</tt></i>,
+<a class="indexterm" name="id2894974"></a><i class="parameter"><tt>load printers</tt></i>,
+<a class="indexterm" name="id2894988"></a><i class="parameter"><tt>lpq cache time</tt></i>,
+<a class="indexterm" name="id2895002"></a><i class="parameter"><tt>os2 driver map</tt></i>,
+<a class="indexterm" name="id2895016"></a><i class="parameter"><tt>printcap name</tt></i>, <a class="indexterm" name="id2895030"></a><i class="parameter"><tt>printcap</tt></i>,
+<a class="indexterm" name="id2895044"></a><i class="parameter"><tt>show add printer wizard</tt></i>,
+<a class="indexterm" name="id2895058"></a><i class="parameter"><tt>total print jobs</tt></i>,
+<a class="indexterm" name="id2895072"></a><i class="parameter"><tt>use client driver</tt></i>.
+</p><p>Service level parameters: <a class="indexterm" name="id2895090"></a><i class="parameter"><tt>hosts allow</tt></i>,
+<a class="indexterm" name="id2895104"></a><i class="parameter"><tt>hosts deny</tt></i>,
+<a class="indexterm" name="id2895118"></a><i class="parameter"><tt>lppause command</tt></i>,
+<a class="indexterm" name="id2895132"></a><i class="parameter"><tt>lpq command</tt></i>,
+<a class="indexterm" name="id2895146"></a><i class="parameter"><tt>lpresume command</tt></i>,
+<a class="indexterm" name="id2895160"></a><i class="parameter"><tt>lprm command</tt></i>,
+<a class="indexterm" name="id2895174"></a><i class="parameter"><tt>max print jobs</tt></i>,
+<a class="indexterm" name="id2895188"></a><i class="parameter"><tt>min print space</tt></i>,
+<a class="indexterm" name="id2895202"></a><i class="parameter"><tt>print command</tt></i>,
+<a class="indexterm" name="id2895216"></a><i class="parameter"><tt>printable</tt></i>, <a class="indexterm" name="id2895229"></a><i class="parameter"><tt>print ok </tt></i>,
+<a class="indexterm" name="id2895242"></a><i class="parameter"><tt>printer name</tt></i>, <a class="indexterm" name="id2895258"></a><i class="parameter"><tt>printer</tt></i>,
+<a class="indexterm" name="id2895271"></a><i class="parameter"><tt>printer admin</tt></i>,
+<a class="indexterm" name="id2895285"></a><i class="parameter"><tt>printing</tt></i> = [cups|bsd|lprng...],
+<a class="indexterm" name="id2895299"></a><i class="parameter"><tt>queuepause command</tt></i>,
+<a class="indexterm" name="id2895313"></a><i class="parameter"><tt>queueresume command</tt></i>,
+<a class="indexterm" name="id2895327"></a><i class="parameter"><tt>total print jobs</tt></i>.
 </p><p>
 Samba's printing support implements the Microsoft Remote Procedure
 Calls (MS-RPC) methods for printing. These are used by Windows NT (and
 later) print servers. The old "LanMan" protocol is still supported as
 a fallback resort, and for older clients to use.  More details will
 follow further beneath.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2897853"></a>A simple Configuration to Print</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895354"></a>A simple Configuration to Print</h2></div></div><div></div></div><p>
 Here is a very simple example configuration for print related settings
 in the  file. If you compare it with your own system's , you probably find some
 additional parameters included there (as pre-configured by your OS
@@ -5886,7 +5886,7 @@ vendor). Further below is a discussion and explanation of the
 parameters. Note, that this example doesn't use many parameters.
 However, in many environments these are enough to provide a valid
 <tt class="filename">smb.conf</tt> file which enables all clients to print.
-</p><div class="example"><a name="id2897881"></a><p class="title"><b>Example�18.1.�Simple configuration with BSD printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = bsd</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2895382"></a><p class="title"><b>Example�18.1.�Simple configuration with BSD printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = bsd</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr></table></div><p>
 This is only an example configuration. Samba assigns default values to all
 configuration parameters. On the whole the defaults are conservative and
 sensible. When a parameter is specified in the <tt class="filename">smb.conf</tt> file this overwrites
@@ -5903,7 +5903,7 @@ reminder: It even tolerates some spelling errors (like "browsable"
 instead of "browseable"). Most spelling is case-insensitive. Also, you
 can use "Yes|No" or "True|False" for boolean settings. Lists of names
 may be separated by commas, spaces or tabs.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898017"></a>Verification of "Settings in Use" with <b class="command">testparm</b></h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895518"></a>Verification of "Settings in Use" with <b class="command">testparm</b></h3></div></div><div></div></div><p>
 To see all (or at least most) printing related settings in Samba,
 including the implicitly used ones, try the command outlined below
 (hit "ENTER" twice!). It greps for all occurrences of "lp", "print",
@@ -5957,11 +5957,11 @@ be important in your future dealings with Samba.</em></span>
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> testparm in samba 3 behaves differently from 2.2.x: used
 without the "-v" switch it only shows you the settings actually
 written into ! To see the complete
-configuration used, add the "-v" parameter to testparm.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898105"></a>A little Experiment to warn you</h3></div></div><div></div></div><p>
+configuration used, add the "-v" parameter to testparm.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895606"></a>A little Experiment to warn you</h3></div></div><div></div></div><p>
 Should you need to troubleshoot at any stage, please always come back
 to this point first and verify if "testparm" shows the parameters you
 expect! To give you an example from personal experience as a warning,
-try to just "comment out" the <a class="indexterm" name="id2898120"></a><i class="parameter"><tt>load printers</tt></i>"
+try to just "comment out" the <a class="indexterm" name="id2895621"></a><i class="parameter"><tt>load printers</tt></i>"
 parameter. If your 2.2.x system behaves like mine, you'll see this:
 </p><pre class="screen">
 <tt class="prompt">root# </tt>grep "load printers" /etc/samba/smb.conf
@@ -5988,7 +5988,7 @@ any more... at least not by this ;-)
 
 </pre><p>
 Only when setting the parameter explicitly to
-"<a class="indexterm" name="id2898214"></a><i class="parameter"><tt>load printers</tt></i> = No"
+"<a class="indexterm" name="id2895714"></a><i class="parameter"><tt>load printers</tt></i> = No"
 would Samba recognize my intentions. So my strong advice is:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Never rely on "commented out" parameters!</p></li><li><p>Always set it up explicitly as you intend it to
 behave.</p></li><li><p>Use <b class="command">testparm</b> to uncover hidden
@@ -6064,7 +6064,7 @@ line consisting of, for example,
 will regard the whole of the string after the "="
 sign as the value you want to define. And this is an invalid value
 that will be ignored, and a default value used instead.]
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2898438"></a>Extended Sample Configuration to Print</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895939"></a>Extended Sample Configuration to Print</h2></div></div><div></div></div><p>
 	In <a href="#extbsdpr" title="Example�18.2.�Extended configuration with BSD printing">the extended BSD configuration example</a> we show a more verbose example configuration for print related
 	settings in BSD-printing style environment . Below is a discussion
 and explanation of the various parameters. We chose to use BSD-style
@@ -6083,9 +6083,9 @@ default, because these have been compiled in. To see all settings, let
 root use the <b class="command">testparm</b>
 utility. <b class="command">testparm</b> also gives warnings if you have
 mis-configured certain things..
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2898769"></a>Detailed Explanation of the Example's Settings</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896270"></a>Detailed Explanation of the Example's Settings</h2></div></div><div></div></div><p>
 Following is a discussion of the settings from above shown example.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898782"></a>The [global] Section</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896282"></a>The [global] Section</h3></div></div><div></div></div><p>
 The <i class="parameter"><tt>[global]</tt></i> section is one of 4 special
 sections (along with [<i class="parameter"><tt>[homes]</tt></i>,
 <i class="parameter"><tt>[printers]</tt></i> and
@@ -6097,17 +6097,17 @@ sections and shares. This way you can simplify the configuration and
 avoid setting the same value repeatedly. (Within each individual
 section or share you may however override these globally set "share
 level" settings and specify other values).
-</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2898846"></a><i class="parameter"><tt>printing</tt></i> = bsd</span></dt><dd><p> this causes Samba to use default print commands
+</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2896338"></a><i class="parameter"><tt>printing</tt></i> = bsd</span></dt><dd><p> this causes Samba to use default print commands
 applicable for the BSD (a.k.a. RFC 1179 style or LPR/LPD) printing
 system. In general, the "printing" parameter informs Samba about the
 print subsystem it should expect. Samba supports CUPS, LPD, LPRNG,
 SYSV, HPUX, AIX, QNX and PLP. Each of these systems defaults to a
-different <a class="indexterm" name="id2898872"></a><i class="parameter"><tt>print command</tt></i> (and other queue control
-commands).</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>The <a class="indexterm" name="id2898892"></a><i class="parameter"><tt>printing</tt></i> parameter is
+different <a class="indexterm" name="id2896364"></a><i class="parameter"><tt>print command</tt></i> (and other queue control
+commands).</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>The <a class="indexterm" name="id2896384"></a><i class="parameter"><tt>printing</tt></i> parameter is
 normally a service level parameter. Since it is included here in the
 <i class="parameter"><tt>[global]</tt></i> section, it will take effect for all
 printer shares that are not defined differently. Samba 3 no longer
-supports the SOFTQ printing system.</p></div></dd><dt><span class="term"><a class="indexterm" name="id2898921"></a><i class="parameter"><tt>load printers</tt></i> = yes</span></dt><dd><p> this tells Samba to create automatically all
+supports the SOFTQ printing system.</p></div></dd><dt><span class="term"><a class="indexterm" name="id2896413"></a><i class="parameter"><tt>load printers</tt></i> = yes</span></dt><dd><p> this tells Samba to create automatically all
 available printer shares. "Available" printer shares are discovered by
 scanning the printcap file. All created printer shares are also loaded
 for browsing. If you use this parameter, you do not need to specify
@@ -6116,7 +6116,7 @@ share will clone the configuration options found in the
 <i class="parameter"><tt>[printers]</tt></i> section. (A <i class="parameter"><tt>load printers
 = no</tt></i> setting will allow you to specify each UNIX printer
 you want to share separately, leaving out some you don't want to be
-publicly visible and available).  </p></dd><dt><span class="term"><a class="indexterm" name="id2898970"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes </span></dt><dd><p> this setting is normally
+publicly visible and available).  </p></dd><dt><span class="term"><a class="indexterm" name="id2896462"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes </span></dt><dd><p> this setting is normally
 enabled by default (even if the parameter is not written into the
 ). It makes the <span class="guiicon">Add Printer Wizard</span> icon
 show up in the <span class="guiicon">Printers</span> folder of the Samba host's
@@ -6127,38 +6127,38 @@ will not suffice!). The Add Printer Wizard lets you upload printer
 drivers to the <i class="parameter"><tt>[print$]</tt></i> share and associate it
 with a printer (if the respective queue exists there before the
 action), or exchange a printer's driver against any other previously
-uploaded driver.  </p></dd><dt><span class="term"><a class="indexterm" name="id2899039"></a><i class="parameter"><tt>total print jobs</tt></i> = 100</span></dt><dd><p> this setting sets the upper limit to 100 print jobs
+uploaded driver.  </p></dd><dt><span class="term"><a class="indexterm" name="id2896532"></a><i class="parameter"><tt>total print jobs</tt></i> = 100</span></dt><dd><p> this setting sets the upper limit to 100 print jobs
 being active on the Samba server at any one time. Should a client
 submit a job which exceeds this number, a &#8220;<span class="quote">no more space
 available on server</span>&#8221; type of error message will be returned by
 Samba to the client. A setting of "0" (the default) means there is
 <span class="emphasis"><em>no</em></span> limit at all!
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899078"></a><i class="parameter"><tt>printcap name</tt></i> = /etc/printcap</span></dt><dd><p> this tells Samba where to look for a list of
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896570"></a><i class="parameter"><tt>printcap name</tt></i> = /etc/printcap</span></dt><dd><p> this tells Samba where to look for a list of
 available printer names. (If you use CUPS, make sure that a printcap
 file is written: this is controlled by the "Printcap" directive of
 <tt class="filename">cupsd.conf</tt>).
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899112"></a><i class="parameter"><tt>printer admin</tt></i> = @ntadmin</span></dt><dd><p> members of the ntadmin group should be able to add
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896604"></a><i class="parameter"><tt>printer admin</tt></i> = @ntadmin</span></dt><dd><p> members of the ntadmin group should be able to add
 drivers and set printer properties ("ntadmin" is only an example name,
 it needs to be a valid UNIX group name); root is implicitly always a
-<a class="indexterm" name="id2899136"></a><i class="parameter"><tt>printer admin</tt></i>. The "@" sign precedes group names in
+<a class="indexterm" name="id2896628"></a><i class="parameter"><tt>printer admin</tt></i>. The "@" sign precedes group names in
 . A printer admin can do anything to
 printers via the remote administration interfaces offered by MS-RPC
-(see below).  Note that the <a class="indexterm" name="id2899153"></a><i class="parameter"><tt>printer admin</tt></i>
+(see below).  Note that the <a class="indexterm" name="id2896646"></a><i class="parameter"><tt>printer admin</tt></i>
 parameter is normally a share level parameter, so you may associate
 different groups to different printer shares in larger installations,
-if you use the <a class="indexterm" name="id2899170"></a><i class="parameter"><tt>printer admin</tt></i> parameter on the
+if you use the <a class="indexterm" name="id2896661"></a><i class="parameter"><tt>printer admin</tt></i> parameter on the
 share levels).
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899188"></a><i class="parameter"><tt>lpq cache time</tt></i> = 20</span></dt><dd><p> this controls the cache time for the results of the
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896681"></a><i class="parameter"><tt>lpq cache time</tt></i> = 20</span></dt><dd><p> this controls the cache time for the results of the
 lpq command. It prevents the lpq command being called too often and
 reduces load on a heavily used print server.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899215"></a><i class="parameter"><tt>use client driver</tt></i> = no</span></dt><dd><p> if set to <tt class="constant">yes</tt>, this setting only 
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896707"></a><i class="parameter"><tt>use client driver</tt></i> = no</span></dt><dd><p> if set to <tt class="constant">yes</tt>, this setting only 
 takes effect for Win NT/2k/XP clients (and not for Win 95/98/ME). Its
 default value is <tt class="constant">No</tt> (or <tt class="constant">False</tt>).
 It must <span class="emphasis"><em>not</em></span> be enabled on print shares 
 (with a <tt class="constant">yes</tt> or <tt class="constant">true</tt> setting) which
 have valid drivers installed on the Samba server! For more detailed
 explanations see the man page of <tt class="filename">smb.conf</tt>.
-</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899274"></a>The [printers] Section</h3></div></div><div></div></div><p>
+</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896767"></a>The [printers] Section</h3></div></div><div></div></div><p>
 This is the second special section. If a section with this name
 appears in the <tt class="filename">smb.conf</tt>, users are able to
 connect to any printer specified in the Samba host's printcap file,
@@ -6169,39 +6169,39 @@ minimal configuration. It is also a container for settings which
 should apply as default to all printers. (For more details see the
 <tt class="filename">smb.conf</tt> man page.) Settings inside this
 container must be share level parameters.
-</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2899316"></a><i class="parameter"><tt>comment</tt></i> = All printers</span></dt><dd><p> the <a class="indexterm" name="id2899336"></a><i class="parameter"><tt>comment</tt></i> is shown next to
+</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2896809"></a><i class="parameter"><tt>comment</tt></i> = All printers</span></dt><dd><p> the <a class="indexterm" name="id2896828"></a><i class="parameter"><tt>comment</tt></i> is shown next to
 the share if a client queries the server, either via <span class="guiicon">Network
 Neighbourhood</span> or with the <b class="command">net view</b> command to list
 available shares.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899369"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p> please note well, that the
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896862"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p> please note well, that the
 <i class="parameter"><tt>[printers]</tt></i> service <span class="emphasis"><em>must</em></span> be
 declared as printable. If you specify otherwise, smbd will refuse to
 load  at startup. This parameter allows
 connected clients to open, write to and submit spool files into the
-directory specified with the <a class="indexterm" name="id2899403"></a><i class="parameter"><tt>path</tt></i> parameter for
+directory specified with the <a class="indexterm" name="id2896896"></a><i class="parameter"><tt>path</tt></i> parameter for
 this service. It is used by Samba to differentiate printer shares from
-file shares.  </p></dd><dt><span class="term"><a class="indexterm" name="id2899424"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba</span></dt><dd><p>this must point to a directory used by Samba to spool
+file shares.  </p></dd><dt><span class="term"><a class="indexterm" name="id2896916"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba</span></dt><dd><p>this must point to a directory used by Samba to spool
 incoming print files. <span class="emphasis"><em>It must not be the same as the spool
 directory specified in the configuration of your UNIX print
 subsystem!</em></span> The path would typically point to a directory
 which is world writeable, with the "sticky" bit set to it.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899457"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this is always set to <tt class="constant">no</tt> if
-<a class="indexterm" name="id2899481"></a><i class="parameter"><tt>printable</tt></i> = yes. It makes the 
+</p></dd><dt><span class="term"><a class="indexterm" name="id2896949"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this is always set to <tt class="constant">no</tt> if
+<a class="indexterm" name="id2896973"></a><i class="parameter"><tt>printable</tt></i> = yes. It makes the 
 <i class="parameter"><tt>[printer]</tt></i> share itself invisible in the
 list of available shares in a <b class="command">net view</b> command or
 in the Explorer browse list. (Note that you will of course see the
 individual printers).
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899515"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p>
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897007"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p>
 if set to <tt class="constant">yes</tt>, then no password is required to
 connect to the printers service. Access will be granted with the
-privileges of the <a class="indexterm" name="id2899541"></a><i class="parameter"><tt>guest account</tt></i>. On many systems the
+privileges of the <a class="indexterm" name="id2897033"></a><i class="parameter"><tt>guest account</tt></i>. On many systems the
 guest account will map to a user named "nobody". This user is in the UNIX
 passwd file with an empty password, but with no valid UNIX login.
 (Note: on some systems the guest account might not have the
 privilege to be able to print. Test this by logging in as your
 guest user using <b class="command">su - guest</b> and run a system print
 command like
-</p><p><b class="userinput"><tt>lpr -P printername /etc/motd</tt></b></p></dd><dt><span class="term"><a class="indexterm" name="id2899582"></a><i class="parameter"><tt>public</tt></i> = yes</span></dt><dd><p> this is a synonym for <a class="indexterm" name="id2899602"></a><i class="parameter"><tt>guest ok</tt></i> = yes. Since we have <a class="indexterm" name="id2899616"></a><i class="parameter"><tt>guest ok</tt></i> = yes,
+</p><p><b class="userinput"><tt>lpr -P printername /etc/motd</tt></b></p></dd><dt><span class="term"><a class="indexterm" name="id2897074"></a><i class="parameter"><tt>public</tt></i> = yes</span></dt><dd><p> this is a synonym for <a class="indexterm" name="id2897094"></a><i class="parameter"><tt>guest ok</tt></i> = yes. Since we have <a class="indexterm" name="id2897108"></a><i class="parameter"><tt>guest ok</tt></i> = yes,
 it really doesn't need to be here! (This leads to the interesting
 question: &#8220;<span class="quote">What, if I by accident have to contradictory settings
 for the same share?</span>&#8221; The answer is: the last one encountered by
@@ -6210,16 +6210,16 @@ complain about different settings of the same parameter for the same
 share! You can test this by setting up multiple lines for the "guest
 account" parameter with different usernames, and then run testparm to
 see which one is actually used by Samba.)
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899647"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>this normally (for other types of shares) prevents
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897139"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>this normally (for other types of shares) prevents
 users creating or modifying files in the service's directory. However,
 in a "printable" service, it is <span class="emphasis"><em>always</em></span> allowed to
 write to the directory (if user privileges allow the connection), but
 only via print spooling operations. "Normal" write operations are not
-allowed.  </p></dd><dt><span class="term"><a class="indexterm" name="id2899681"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p>
-synonym for <a class="indexterm" name="id2899700"></a><i class="parameter"><tt>read only</tt></i> = yes
-</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899717"></a>Any [my_printer_name] Section</h3></div></div><div></div></div><p>
+allowed.  </p></dd><dt><span class="term"><a class="indexterm" name="id2897173"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p>
+synonym for <a class="indexterm" name="id2897193"></a><i class="parameter"><tt>read only</tt></i> = yes
+</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897210"></a>Any [my_printer_name] Section</h3></div></div><div></div></div><p>
 If a section appears in the , which is
-tagged as <a class="indexterm" name="id2899729"></a><i class="parameter"><tt>printable</tt></i> = yes, Samba presents it as
+tagged as <a class="indexterm" name="id2897220"></a><i class="parameter"><tt>printable</tt></i> = yes, Samba presents it as
 a printer share to its clients. Note, that Win95/98/ME clients may
 have problems with connecting or loading printer drivers if the share
 name has more than 8 characters! Also be very careful if you give a
@@ -6228,36 +6228,36 @@ client's connection request to a certain sharename, Samba always tries
 to find file shares with that name first; if it finds one, it will
 connect to this and will never ultimately connect to a printer with
 the same name!
-</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2899759"></a><i class="parameter"><tt>comment</tt></i> = Printer with Restricted Access</span></dt><dd><p> the comment says it all.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899784"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba_my_printer</span></dt><dd><p> here we set the spooling area for this printer to
+</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2897262"></a><i class="parameter"><tt>comment</tt></i> = Printer with Restricted Access</span></dt><dd><p> the comment says it all.
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897287"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba_my_printer</span></dt><dd><p> here we set the spooling area for this printer to
 another directory than the default. It is not a requirement to set it
 differently, but the option is available.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899811"></a><i class="parameter"><tt>printer admin</tt></i> = kurt</span></dt><dd><p> the printer admin definition is different for this
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897314"></a><i class="parameter"><tt>printer admin</tt></i> = kurt</span></dt><dd><p> the printer admin definition is different for this
 explicitly defined printer share from the general
 <i class="parameter"><tt>[printers]</tt></i> share. It is not a requirement; we
 did it to show that it is possible if you want it.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899844"></a><i class="parameter"><tt>browseable</tt></i> = yes</span></dt><dd><p> we also made this printer browseable (so that the
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897347"></a><i class="parameter"><tt>browseable</tt></i> = yes</span></dt><dd><p> we also made this printer browseable (so that the
 clients may conveniently find it when browsing the <span class="guiicon">Network
 Neighbourhood</span>).
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899877"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p>see explanation in last subsection.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899901"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p>see explanation in last subsection.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899925"></a><i class="parameter"><tt>hosts allow</tt></i> = 10.160.50.,10.160.51.</span></dt><dd><p>here we exercise a certain degree of access control
-by using the <a class="indexterm" name="id2899947"></a><i class="parameter"><tt>hosts allow</tt></i> and <a class="indexterm" name="id2899960"></a><i class="parameter"><tt>hosts deny</tt></i> parameters. Note, that
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897380"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p>see explanation in last subsection.
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897403"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p>see explanation in last subsection.
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897427"></a><i class="parameter"><tt>hosts allow</tt></i> = 10.160.50.,10.160.51.</span></dt><dd><p>here we exercise a certain degree of access control
+by using the <a class="indexterm" name="id2897449"></a><i class="parameter"><tt>hosts allow</tt></i> and <a class="indexterm" name="id2897463"></a><i class="parameter"><tt>hosts deny</tt></i> parameters. Note, that
 this is not by any means a safe bet. It is not a way to secure your
 printers. This line accepts all clients from a certain subnet in a
 first evaluation of access control
-</p></dd><dt><span class="term"><a class="indexterm" name="id2899982"></a><i class="parameter"><tt>hosts deny</tt></i> = turbo_xp,10.160.50.23,10.160.51.60</span></dt><dd><p>all listed hosts are not allowed here (even if they
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897484"></a><i class="parameter"><tt>hosts deny</tt></i> = turbo_xp,10.160.50.23,10.160.51.60</span></dt><dd><p>all listed hosts are not allowed here (even if they
 belong to the "allowed subnets"). As you can see, you could name IP
 addresses as well as NetBIOS hostnames
 here.
-</p></dd><dt><span class="term"><a class="indexterm" name="id2900008"></a><i class="parameter"><tt>guest ok</tt></i> = no</span></dt><dd><p>this printer is not open for the guest account!
-</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900032"></a>Print Commands</h3></div></div><div></div></div><p>
+</p></dd><dt><span class="term"><a class="indexterm" name="id2897510"></a><i class="parameter"><tt>guest ok</tt></i> = no</span></dt><dd><p>this printer is not open for the guest account!
+</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897534"></a>Print Commands</h3></div></div><div></div></div><p>
 In each section defining a printer (or in the
 <i class="parameter"><tt>[printers]</tt></i> section), a <i class="parameter"><tt>print
 command</tt></i> parameter may be defined. It sets a command to
 process the files which have been placed into the Samba print spool
 directory for that printer. (That spool directory was, if you
-remember, set up with the <a class="indexterm" name="id2900061"></a><i class="parameter"><tt>path</tt></i>
+remember, set up with the <a class="indexterm" name="id2897564"></a><i class="parameter"><tt>path</tt></i>
 parameter). Typically, this command will submit the spool file to the
 Samba host's print subsystem, using the suitable system print
 command. But there is no requirement that this needs to be the
@@ -6269,24 +6269,24 @@ your own print commands (or even develop print command shell scripts),
 make sure you pay attention to the need to remove the files from the
 Samba spool directory. Otherwise your hard disk may soon suffer from
 shortage of free space.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900090"></a>Default Print Commands for various UNIX Print Subsystems</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897592"></a>Default Print Commands for various UNIX Print Subsystems</h3></div></div><div></div></div><p>
 You learned earlier on, that Samba in most cases uses its built-in
 settings for many parameters if it can not find an explicitly stated
 one in its configuration file. The same is true for the
-<a class="indexterm" name="id2900103"></a><i class="parameter"><tt>print command</tt></i>. The default print command varies
-depending on the <a class="indexterm" name="id2900120"></a><i class="parameter"><tt>printing</tt></i> parameter
+<a class="indexterm" name="id2897606"></a><i class="parameter"><tt>print command</tt></i>. The default print command varies
+depending on the <a class="indexterm" name="id2897622"></a><i class="parameter"><tt>printing</tt></i> parameter
 setting. In the commands listed below, you will notice some parameters
 of the form <span class="emphasis"><em>%X</em></span> where <span class="emphasis"><em>X</em></span> is
 <span class="emphasis"><em>p, s, J</em></span> etc. These letters stand for
 "printername", "spoolfile" and "job ID" respectively.  They are
 explained in more detail further below. Here is an overview (excluding
 the special case of CUPS, which is discussed in the next chapter):
-</p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th align="left">If this setting is active...</th><th align="left">...this is used in lieu of an explicit command:</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2900198"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">print command is <b class="command">lpr -r -P%p %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900228"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">print command is <b class="command">lp -c -P%p %s; rm %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900261"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">print command is <b class="command">lp -r -P%p -s %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900291"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900322"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpq command is <b class="command">lpstat -o%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900352"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900382"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lprm command is <b class="command">lprm -P%p %j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900413"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900444"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900474"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lppause command is <b class="command">lp -i %p-%j -H hold</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900505"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2900530"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2900556"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpresume command is <b class="command">lp -i %p-%j -H resume</b></td></tr><tr><td align="left"><a class="indexterm" name="id2900587"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpresume command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2900612"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpresume command   (...is empty)</td></tr></tbody></table></div><p>
+</p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th align="left">If this setting is active...</th><th align="left">...this is used in lieu of an explicit command:</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2897700"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">print command is <b class="command">lpr -r -P%p %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897731"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">print command is <b class="command">lp -c -P%p %s; rm %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897762"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">print command is <b class="command">lp -r -P%p -s %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897794"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897824"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpq command is <b class="command">lpstat -o%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897855"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897885"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lprm command is <b class="command">lprm -P%p %j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897916"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897947"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2897977"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lppause command is <b class="command">lp -i %p-%j -H hold</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898008"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2898033"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lppause command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2898058"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpresume command is <b class="command">lp -i %p-%j -H resume</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898090"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpresume command   (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2898115"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpresume command   (...is empty)</td></tr></tbody></table></div><p>
 We excluded the special CUPS case here, because it is discussed in the
 next chapter. Just a short summary. For <i class="parameter"><tt>printing =
 CUPS</tt></i>: If SAMBA is compiled against libcups, it uses the
 CUPS API to submit jobs, etc. (It is a good idea also to set
-<a class="indexterm" name="id2900650"></a><i class="parameter"><tt>printcap</tt></i> = cups in case your
+<a class="indexterm" name="id2898153"></a><i class="parameter"><tt>printcap</tt></i> = cups in case your
 <tt class="filename">cupsd.conf</tt> is set to write its autogenerated
 printcap file to an unusual place). Otherwise Samba maps to the System
 V printing commands with the -oraw option for printing, i.e. it uses
@@ -6309,9 +6309,9 @@ check which command takes effect. Then check that this command is
 adequate and actually works for your installed print subsystem. It is
 always a good idea to explicitly set up your configuration files the
 way you want them to work and not rely on any built-in defaults.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900758"></a>Setting up your own Print Commands</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898261"></a>Setting up your own Print Commands</h3></div></div><div></div></div><p>
 After a print job has finished spooling to a service, the
-<a class="indexterm" name="id2900770"></a><i class="parameter"><tt>print command</tt></i> will be used by Samba via a
+<a class="indexterm" name="id2898273"></a><i class="parameter"><tt>print command</tt></i> will be used by Samba via a
 <span class="emphasis"><em>system()</em></span> call to process the spool file.  Usually
 the command specified will submit the spool file to the host's
 printing subsystem. But there is no requirement at all that this must
@@ -6364,16 +6364,16 @@ expand the included environment variables as usual. (The syntax to
 include a UNIX environment variable <i class="parameter"><tt>$variable</tt></i>
 in  or in the Samba print command is
 <i class="parameter"><tt>%$variable</tt></i>.) To give you a working
-<a class="indexterm" name="id2900989"></a><i class="parameter"><tt>print command</tt></i> example, the following will log a
+<a class="indexterm" name="id2898492"></a><i class="parameter"><tt>print command</tt></i> example, the following will log a
 print job to <tt class="filename">/tmp/print.log</tt>, print the file, then
 remove it. Note that ';' is the usual separator for commands in shell
 scripts:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>print command = echo Printing %s &gt;&gt; /tmp/print.log; lpr -P %p %s; rm %s</tt></i></td></tr></table><p>
 You may have to vary your own command considerably from this example
 depending on how you normally print files on your system.  The default
-for the <a class="indexterm" name="id2901038"></a><i class="parameter"><tt>print command</tt></i> parameter varies depending on the setting of
-the <a class="indexterm" name="id2901055"></a><i class="parameter"><tt>printing</tt></i> parameter. Another example is:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>print command = /usr/local/samba/bin/myprintscript %p %s</tt></i></td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2901088"></a>Innovations in Samba Printing since 2.2</h2></div></div><div></div></div><p>
+for the <a class="indexterm" name="id2898541"></a><i class="parameter"><tt>print command</tt></i> parameter varies depending on the setting of
+the <a class="indexterm" name="id2898557"></a><i class="parameter"><tt>printing</tt></i> parameter. Another example is:
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>print command = /usr/local/samba/bin/myprintscript %p %s</tt></i></td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2898591"></a>Innovations in Samba Printing since 2.2</h2></div></div><div></div></div><p>
 Before version 2.2.0, Samba's print server support for Windows clients
 was limited to the level of <span class="emphasis"><em>LanMan</em></span> printing
 calls. This is the same protocol level as Windows 9x PCs offer when
@@ -6412,7 +6412,7 @@ default permissions assigned by Windows NT to a printer gives the
 "Print" permissions to the well-known <span class="emphasis"><em>Everyone</em></span>
 group. (The older clients of type Win9x can only print to "shared"
 printers).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901237"></a>Client Drivers on Samba Server for <span class="emphasis"><em>Point'n'Print</em></span></h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898740"></a>Client Drivers on Samba Server for <span class="emphasis"><em>Point'n'Print</em></span></h3></div></div><div></div></div><p>
 There is still confusion about what all this means: <span class="emphasis"><em>Is it or
 is it not a requirement for printer drivers to be installed on a Samba
 host in order to support printing from Windows clients?</em></span> The
@@ -6450,7 +6450,7 @@ by Samba. The clients use these drivers to generate print files in the
 format the printer (or the UNIX print system) requires. Print files
 received by Samba are handed over to the UNIX printing system, which
 is responsible for all further processing, if needed.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901389"></a>The [printer$] Section is removed from Samba 3</h3></div></div><div></div></div><p><b>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898892"></a>The [printer$] Section is removed from Samba 3</h3></div></div><div></div></div><p><b>
 <i class="parameter"><tt>[print$]</tt></i> vs. <i class="parameter"><tt>[printer$]</tt></i>
 .�</b>
 Versions of Samba prior to 2.2 made it possible to use a share
@@ -6476,7 +6476,7 @@ access (in the context of its ACLs) in order to support printer driver
 down- and uploads.  Don't fear -- this does not mean Windows 9x
 clients are thrown aside now. They can use Samba's
 <i class="parameter"><tt>[print$]</tt></i> share support just fine.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901502"></a>Creating the [print$] Share</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899004"></a>Creating the [print$] Share</h3></div></div><div></div></div><p>
 In order to support the up- and downloading of printer driver files,
 you must first configure a file share named
 <i class="parameter"><tt>[print$]</tt></i>. The "public" name of this share is
@@ -6490,25 +6490,25 @@ add the global parameters and create the
 <i class="parameter"><tt>[print$]</tt></i> 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><div class="example"><a name="id2901544"></a><p class="title"><b>Example�18.3.�[print\$] example</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># members of the ntadmin group should be able to add drivers and set</td></tr><tr><td># printer properties. root is implicitly always a 'printer admin'.</td></tr><tr><td><i class="parameter"><tt>printer admin = @ntadmin</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[print$]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer Driver Download Area</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /etc/samba/drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = @ntadmin, root</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2899046"></a><p class="title"><b>Example�18.3.�[print\$] example</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># members of the ntadmin group should be able to add drivers and set</td></tr><tr><td># printer properties. root is implicitly always a 'printer admin'.</td></tr><tr><td><i class="parameter"><tt>printer admin = @ntadmin</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[print$]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer Driver Download Area</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /etc/samba/drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = @ntadmin, root</tt></i></td></tr></table></div><p>
 Of course, you also need to ensure that the directory named by the
-<a class="indexterm" name="id2901670"></a><i class="parameter"><tt>path</tt></i> parameter exists on the UNIX file system.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901686"></a>Parameters in the [print$] Section</h3></div></div><div></div></div><p>
+<a class="indexterm" name="id2899172"></a><i class="parameter"><tt>path</tt></i> parameter exists on the UNIX file system.
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899189"></a>Parameters in the [print$] Section</h3></div></div><div></div></div><p>
 <i class="parameter"><tt>[print$]</tt></i> is a special section in
 . It contains settings relevant to
 potential printer driver download and local installation by clients.
-</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2901714"></a><i class="parameter"><tt>comment</tt></i> = Printer Driver
+</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2899217"></a><i class="parameter"><tt>comment</tt></i> = Printer Driver
 					Download Area</span></dt><dd><p> the comment appears next to the share name if it is
 listed in a share list (usually Windows clients won't see it often but
 it will also appear up in a <b class="command">smbclient -L sambaserver
-</b> output). </p></dd><dt><span class="term"><a class="indexterm" name="id2901749"></a><i class="parameter"><tt>path</tt></i> = /etc/samba/printers</span></dt><dd><p> this is the path to the location of the Windows
+</b> output). </p></dd><dt><span class="term"><a class="indexterm" name="id2899252"></a><i class="parameter"><tt>path</tt></i> = /etc/samba/printers</span></dt><dd><p> this is the path to the location of the Windows
 driver file deposit from the UNIX point of
-view.</p></dd><dt><span class="term"><a class="indexterm" name="id2901775"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this makes the <i class="parameter"><tt>[print$]</tt></i> share
+view.</p></dd><dt><span class="term"><a class="indexterm" name="id2899277"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this makes the <i class="parameter"><tt>[print$]</tt></i> share
 "invisible" in Network Neighbourhood to clients. However, you can
 still "mount" it from any client using the <b class="command">net use
 g:\\sambaserver\print$</b> command in a "DOS box" or the
 "Connect network drive" menu from Windows
-Explorer.</p></dd><dt><span class="term"><a class="indexterm" name="id2901816"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p>this gives read only access to this share for all
+Explorer.</p></dd><dt><span class="term"><a class="indexterm" name="id2899319"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p>this gives read only access to this share for all
 guest users. Access may be used to download and install printer
 drivers on clients. The requirement for <i class="parameter"><tt>guest ok =
 yes</tt></i> depends upon how your site is configured. If users
@@ -6521,13 +6521,13 @@ validated by the Domain Controller in order to logon to the Windows NT
 session), then guest access is not necessary. Of course, in a
 workgroup environment where you just want to be able to print without
 worrying about silly accounts and security, then configure the share
-for guest access. You'll probably want to add <a class="indexterm" name="id2901863"></a><i class="parameter"><tt>map to guest</tt></i> = Bad User in the
+for guest access. You'll probably want to add <a class="indexterm" name="id2899365"></a><i class="parameter"><tt>map to guest</tt></i> = Bad User in the
 <i class="parameter"><tt>[global]</tt></i> section
 as well. Make sure you understand what this parameter does before
 using it.
-</p></div></dd><dt><span class="term"><a class="indexterm" name="id2901890"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>as we don't want everybody to upload driver files (or
+</p></div></dd><dt><span class="term"><a class="indexterm" name="id2899392"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>as we don't want everybody to upload driver files (or
 even change driver settings) we tagged this share as not
-writeable.</p></dd><dt><span class="term"><a class="indexterm" name="id2901916"></a><i class="parameter"><tt>write list</tt></i> = @ntadmin,root</span></dt><dd><p>since the <i class="parameter"><tt>[print$]</tt></i> was made
+writeable.</p></dd><dt><span class="term"><a class="indexterm" name="id2899418"></a><i class="parameter"><tt>write list</tt></i> = @ntadmin,root</span></dt><dd><p>since the <i class="parameter"><tt>[print$]</tt></i> was made
 read only by the previous setting, we need to create a "write list"
 also. UNIX groups (denoted with a leading "@" character) and users
 listed here are allowed write access (as an exception to the general
@@ -6536,13 +6536,13 @@ share.  Normally you will want to only name administrative level user
 accounts in this setting. Check the file system permissions to make
 sure these accounts can copy files to the share. If this is a non-root
 account, then the account should also be mentioned in the global
-<a class="indexterm" name="id2901953"></a><i class="parameter"><tt>printer admin </tt></i> parameter.  See the
+<a class="indexterm" name="id2899455"></a><i class="parameter"><tt>printer admin </tt></i> parameter.  See the
  man page for more information on
-configuring file shares.  </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901973"></a>Subdirectory Structure in [print$]</h3></div></div><div></div></div><p>
+configuring file shares.  </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899475"></a>Subdirectory Structure in [print$]</h3></div></div><div></div></div><p>
 In order for a Windows NT print server to support the downloading of
 driver files by multiple client architectures, you must create several
 subdirectories within the <i class="parameter"><tt>[print$]</tt></i> service
-(i.e. the UNIX directory named by the <a class="indexterm" name="id2901993"></a><i class="parameter"><tt>path</tt></i>
+(i.e. the UNIX directory named by the <a class="indexterm" name="id2899495"></a><i class="parameter"><tt>path</tt></i>
 parameter). These correspond to each of the supported client
 architectures. Samba follows this model as well. Just like the name of
 the <i class="parameter"><tt>[print$]</tt></i> share itself, the subdirectories
@@ -6577,7 +6577,7 @@ client workstation. Open <span class="guiicon">Network Neighbourhood</span> or
 Once you have located the server, navigate to its <span class="guiicon">Printers and
 Faxes</span> folder.  You should see an initial listing of printers
 that matches the printer shares defined on your Samba host.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902140"></a>Installing Drivers into [print$]</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2899643"></a>Installing Drivers into [print$]</h2></div></div><div></div></div><p>
 You have successfully created the <i class="parameter"><tt>[print$]</tt></i>
 share in ?  And Samba has re-read its
 configuration? Good. But you are not yet ready to take off. The
@@ -6595,7 +6595,7 @@ Properties</em></span> and <span class="emphasis"><em>Add Printer Wizard</em></s
 from any Windows NT/2k/XP client workstation.</p></li></ul></div><p>
 The latter option is probably the easier one (even if the only
 entrance to this realm seems a little bit weird at first).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902234"></a>Setting Drivers for existing Printers with a Client GUI</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899736"></a>Setting Drivers for existing Printers with a Client GUI</h3></div></div><div></div></div><p>
 The initial listing of printers in the Samba host's
 <span class="guiicon">Printers</span> folder accessed from a client's Explorer
 will have no real printer driver assigned to them. By default
@@ -6630,18 +6630,18 @@ Once the APW is started, the procedure is exactly the same as the one
 you are familiar with in Windows (we assume here that you are
 familiar with the printer driver installations procedure on Windows
 NT). Make sure your connection is in fact setup as a user with
-<a class="indexterm" name="id2902368"></a><i class="parameter"><tt>printer admin</tt></i> privileges (if in doubt, use
+<a class="indexterm" name="id2899872"></a><i class="parameter"><tt>printer admin</tt></i> privileges (if in doubt, use
 <b class="command">smbstatus</b> to check for this). If you wish to
 install printer drivers for client operating systems other than
 <span class="application">Windows NT x86</span>, you will need to use the
 <span class="guilabel">Sharing</span> tab of the printer properties dialog.
 </p><p>
 Assuming you have connected with an administrative (or root) account
-(as named by the <a class="indexterm" name="id2902410"></a><i class="parameter"><tt>printer admin</tt></i> parameter),
+(as named by the <a class="indexterm" name="id2899914"></a><i class="parameter"><tt>printer admin</tt></i> parameter),
 you will also be able to modify other printer properties such as ACLs
 and default device settings using this dialog. For the default device
 settings, please consider the advice given further below.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902432"></a>Setting Drivers for existing Printers with
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899935"></a>Setting Drivers for existing Printers with
 <b class="command">rpcclient</b></h3></div></div><div></div></div><p>
 The second way to install printer drivers into
 <i class="parameter"><tt>[print$]</tt></i> and set them up in a valid way can be
@@ -6656,7 +6656,7 @@ time with the <b class="command">setdriver</b>
 subcommand.</p></li></ol></div><p>
 We will provide detailed hints for each of these steps in the next few
 paragraphs.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902540"></a>Identifying the Driver Files</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900043"></a>Identifying the Driver Files</h4></div></div><div></div></div><p>
 To find out about the driver files, you have two options: you could
 investigate the driver CD which comes with your printer.  Study the
 <tt class="filename">*.inf</tt> file on the CD, if it is contained. This
@@ -6759,7 +6759,7 @@ Windows 2000 changed this. While it still can use the Kernel Mode
 drivers (if this is enabled by the Admin), its native mode for printer
 drivers is User Mode execution. This requires drivers designed for
 this. These type of drivers install into the "3" subdirectory.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902865"></a>Collecting the Driver Files from a Windows Host's
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900368"></a>Collecting the Driver Files from a Windows Host's
 [print$] Share</h4></div></div><div></div></div><p>
 Now we need to collect all the driver files we identified. in our
 previous step. Where do we get them from? Well, why not retrieve them
@@ -6795,7 +6795,7 @@ files for these architectures are in the WIN40/0/ subdir. Once we are
 complete, we can run <b class="command">smbclient ...  put</b> to store
 the collected files on the Samba server's
 <i class="parameter"><tt>[print$]</tt></i> share.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903015"></a>Depositing the Driver Files into [print$]</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900518"></a>Depositing the Driver Files into [print$]</h4></div></div><div></div></div><p>
 So, now we are going to put the driver files into the
 <i class="parameter"><tt>[print$]</tt></i> share. Remember, the UNIX path to this
 share has been defined previously in your
@@ -6856,7 +6856,7 @@ re-location will automatically be done by the
 don't forget to also put the files for the Win95/98/ME architecture
 into the <tt class="filename">WIN40/</tt> subdirectory should you need
 them).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903206"></a>Check if the Driver Files are there (with smbclient)</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900731"></a>Check if the Driver Files are there (with smbclient)</h4></div></div><div></div></div><p>
 For now we verify that our files are there. This can be done with
 <b class="command">smbclient</b> too (but of course you can log in via SSH
 also and do this through a standard UNIX shell access too):
@@ -6909,7 +6909,7 @@ Point'n'Print. The reason is: Samba doesn't know yet that these files
 are something special, namely <span class="emphasis"><em>printer driver
 files</em></span> and it doesn't know yet to which print queue(s) these
 driver files belong.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903366"></a>Running <b class="command">rpcclient</b> with
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900890"></a>Running <b class="command">rpcclient</b> with
 <b class="command">adddriver</b></h4></div></div><div></div></div><p>
 So, next you must tell Samba about the special category of the files
 you just uploaded into the <i class="parameter"><tt>[print$]</tt></i> share. This
@@ -6946,7 +6946,7 @@ files successfully, but render the driver unworkable. So take care!
 Hints about the syntax of the adddriver command are in the man
 page. The CUPS printing chapter of this HOWTO collection provides a
 more detailed description, if you should need it.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903466"></a>Check how Driver Files have been moved after
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900990"></a>Check how Driver Files have been moved after
 <b class="command">adddriver</b> finished</h4></div></div><div></div></div><p>
 One indication for Samba's recognition of the files as driver files is
 the <tt class="computeroutput">successfully installed</tt> message.
@@ -6994,7 +6994,7 @@ subdirectory. You can check this again with
 </pre><p>
 Another verification is that the timestamp of the printing TDB files
 is now updated (and possibly their filesize has increased).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903590"></a>Check if the Driver is recognized by Samba</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901159"></a>Check if the Driver is recognized by Samba</h4></div></div><div></div></div><p>
 Now the driver should be registered with Samba. We can easily verify
 this, and will do so in a moment. However, this driver is
 <span class="emphasis"><em>not yet</em></span> associated with a particular
@@ -7038,7 +7038,7 @@ time. Our new driver only shows up for
 <span class="application">Windows NT 4.0 or 2000</span>. To
 have it present for <span class="application">Windows 95, 98 and ME</span> you'll
 have to repeat the whole procedure with the WIN40 architecture and subdirectory.
-</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903793"></a>A side note: you are not bound to specific driver names</h4></div></div><div></div></div><p>
+</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901363"></a>A side note: you are not bound to specific driver names</h4></div></div><div></div></div><p>
 You can name the driver as you like. If you repeat the
 <b class="command">adddriver</b> step, with the same files as before, but
 with a different driver name, it will work the same:
@@ -7072,7 +7072,7 @@ repeatedly. Each run "consumes" the files you had put into the
 respective subdirectories. So you <span class="emphasis"><em>must</em></span> precede an
 <b class="command">smbclient ... put</b> command before each
 <b class="command">rpcclient ...  adddriver</b>" command.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2903904"></a>Running <b class="command">rpcclient</b> with
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901473"></a>Running <b class="command">rpcclient</b> with
 <b class="command">setdriver</b></h4></div></div><div></div></div><p>
 Samba still needs to know <span class="emphasis"><em>which</em></span> printer's driver
 this is.  It needs to create a mapping of the driver to a printer, and
@@ -7102,12 +7102,12 @@ known to
 Samba already. A bug in 2.2.x prevented Samba from recognizing freshly
 installed printers. You had to restart Samba, or at least send a HUP
 signal to all running smbd processes to work around this:
-<b class="userinput"><tt>kill -HUP `pidof smbd`</tt></b>.  </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904055"></a>Client Driver Install Procedure</h2></div></div><div></div></div><p>
+<b class="userinput"><tt>kill -HUP `pidof smbd`</tt></b>.  </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2901625"></a>Client Driver Install Procedure</h2></div></div><div></div></div><p>
 A famous philosopher said once: &#8220;<span class="quote">The Proof of the Pudding lies
 in the Eating</span>&#8221;. The proof for our setup lies in the printing.
 So let's install the printer driver onto the client PCs. This is not
 as straightforward as it may seem. Read on.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904073"></a>The first Client Driver Installation</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901643"></a>The first Client Driver Installation</h3></div></div><div></div></div><p>
 Especially important is the installation onto the first client PC (for
 each architectural platform separately). Once this is done correctly,
 all further clients are easy to setup and shouldn't need further
@@ -7150,7 +7150,7 @@ Data" set is still incomplete.
 </p><p>
 You must now make sure that a valid "Device Mode" is set for the
 driver. Don't fear -- we will explain now what that means.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904269"></a>IMPORTANT! Setting Device Modes on new Printers</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901839"></a>IMPORTANT! Setting Device Modes on new Printers</h3></div></div><div></div></div><p>
 In order for a printer to be truly usable by a Windows NT/2K/XP
 client, it must possess:
 </p><div class="itemizedlist"><ul type="disc"><li><p>a valid <span class="emphasis"><em>Device Mode</em></span> generated by
@@ -7177,7 +7177,7 @@ This can be achieved by accessing the drivers remotely from an NT (or
 2k/XP) client, as is discussed in the next paragraphs.
 </p><p>
 Be aware, that a valid Device Mode can only be initiated by a
-<a class="indexterm" name="id2904365"></a><i class="parameter"><tt>printer admin</tt></i>, or root (the reason should be
+<a class="indexterm" name="id2901935"></a><i class="parameter"><tt>printer admin</tt></i>, or root (the reason should be
 obvious). Device Modes can only correctly be set by executing the
 printer driver program itself. Since Samba can not execute this Win32
 platform driver code, it sets this field initially to NULL (which is
@@ -7222,7 +7222,7 @@ properties. Others may crash the client's spooler service. So use this
 parameter with caution. It is always better to have the client
 generate a valid device mode for the printer and store it on the
 server for you.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904576"></a>Further Client Driver Install Procedures</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902136"></a>Further Client Driver Install Procedures</h3></div></div><div></div></div><p>
 Every further driver may be done by any user, along the lines
 described above: Browse network, open printers folder on Samba server,
 right-click printer and choose <span class="guimenuitem">Connect...</span>. Once
@@ -7242,12 +7242,12 @@ rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2
 You can enter the commands either inside a <span class="guilabel">DOS box</span> window 
 or in the <span class="guimenuitem">Run command...</span> field from the 
 <span class="guimenu">Start</span> menu.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904670"></a>Always make first Client Connection as root or "printer admin"</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902231"></a>Always make first Client Connection as root or "printer admin"</h3></div></div><div></div></div><p>
 After you installed the driver on the Samba server (in its
 <i class="parameter"><tt>[print$]</tt></i> share, you should always make sure
 that your first client installation completes correctly. Make it a habit for
 yourself to build that the very first connection from a client as
-<a class="indexterm" name="id2904692"></a><i class="parameter"><tt>printer admin</tt></i>. This is to make sure that:
+<a class="indexterm" name="id2902252"></a><i class="parameter"><tt>printer admin</tt></i>. This is to make sure that:
 </p><div class="itemizedlist"><ul type="disc"><li><p> a first valid <span class="emphasis"><em>Device Mode</em></span> is
 really initialized (see above for more explanation details), and
 that</p></li><li><p> the default print settings of your printer for all
@@ -7270,14 +7270,14 @@ You will be prompted for root's Samba-password; type it, wait a few
 seconds, click on <span class="guibutton">Printing Defaults...</span> and
 proceed to set the job options as should be used as defaults by all
 clients. Alternatively, instead of root you can name one other member
-of the <a class="indexterm" name="id2904809"></a><i class="parameter"><tt>printer admin</tt></i> from the setting.
+of the <a class="indexterm" name="id2902370"></a><i class="parameter"><tt>printer admin</tt></i> from the setting.
 </p><p>
 Now all the other users downloading and installing the driver
 the same way (called <span class="emphasis"><em>Point'n'Print</em></span>) will
 have the same defaults set for them. If you miss this step you'll
 get a lot of helpdesk calls from your users. But maybe you like to
 talk to people.... ;-)
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904838"></a>Other Gotchas</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902399"></a>Other Gotchas</h2></div></div><div></div></div><p>
 Your driver is installed. It is ready for
 <span class="emphasis"><em>Point'n'Print</em></span> installation by the clients
 now. You <span class="emphasis"><em>may</em></span> have tried to download and use it
@@ -7287,7 +7287,7 @@ example, suppose you didn't manage to "set the defaults" on the
 printer, as advised in the preceding paragraphs? And your users
 complain about various issues (such as &#8220;<span class="quote">We need to set the paper
 size for each job from Letter to A4 and it won't store it!</span>&#8221;)
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904870"></a>Setting Default Print Options for the Client Drivers</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902431"></a>Setting Default Print Options for the Client Drivers</h3></div></div><div></div></div><p>
 The last sentence might be viewed with mixed feelings by some users and
 admins. They have struggled for hours and hours and couldn't arrive at
 a point were their settings seemed to be saved.  It is not their
@@ -7342,7 +7342,7 @@ either. However, only the last one, which you arrived at with steps
 C.1.-6. will permanently save any settings which will then become the
 defaults for new users. If you want all clients to have the same
 defaults, you need to conduct these steps as administrator
-(<a class="indexterm" name="id2905156"></a><i class="parameter"><tt>printer admin</tt></i> in )
+(<a class="indexterm" name="id2902717"></a><i class="parameter"><tt>printer admin</tt></i> in )
 <span class="emphasis"><em>before</em></span> a client downloads the driver (the clients
 can later set their own <span class="emphasis"><em>per-user defaults</em></span> by
 following the procedures <span class="emphasis"><em>A.</em></span>
@@ -7376,7 +7376,7 @@ to see the tab with the <span class="guilabel">Printing Preferences...</span>
 button (the one which doesn't set system-wide defaults). You can
 start the commands from inside a DOS box" or from the <span class="guimenu">Start</span>
 -- <span class="guimenuitem">Run...</span> menu.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905319"></a>Supporting large Numbers of Printers</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902874"></a>Supporting large Numbers of Printers</h3></div></div><div></div></div><p>
 One issue that has arisen during the recent development phase of Samba
 is the need to support driver downloads for 100's of printers. Using
 Windows NT APW here is somewhat awkward (to say the least). If you
@@ -7466,7 +7466,7 @@ commas in the "description" field). After the
 <b class="command">setdriver</b> command succeeded, all is well.  (The
 CUPS Printing chapter has more info about the installation of printer
 drivers with the help of <b class="command">rpcclient</b>).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905621"></a>Adding new Printers with the Windows NT APW</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903177"></a>Adding new Printers with the Windows NT APW</h3></div></div><div></div></div><p>
 By default, Samba exhibits all printer shares defined in
 <tt class="filename">smb.conf</tt> in the
 <span class="guiicon">Printers...</span> folder. Also located in this folder
@@ -7474,27 +7474,27 @@ is the Windows NT Add Printer Wizard icon. The APW will be shown only
 if:
 </p><div class="itemizedlist"><ul type="disc"><li><p>...the connected user is able to successfully execute
 an <b class="command">OpenPrinterEx(\\server)</b> with administrative
-privileges (i.e. root or <a class="indexterm" name="id2905667"></a><i class="parameter"><tt>printer admin</tt></i>).
+privileges (i.e. root or <a class="indexterm" name="id2903223"></a><i class="parameter"><tt>printer admin</tt></i>).
 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Try this from a Windows 2K/XP DOS box command prompt:
 </p><p><b class="userinput"><tt>
 runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printersharename</tt></i>
 </tt></b></p><p>
 and click on <span class="guibutton">Printing Preferences...</span>
 </p></div></li><li><p>... contains the setting
-<a class="indexterm" name="id2905722"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes (the
+<a class="indexterm" name="id2903277"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes (the
 default).</p></li></ul></div><p>
 The APW can do various things:
 </p><div class="itemizedlist"><ul type="disc"><li><p>upload a new driver to the Samba
 <i class="parameter"><tt>[print$]</tt></i> share;</p></li><li><p>associate an uploaded driver with an existing (but
 still "driverless") print queue;</p></li><li><p>exchange the currently used driver for an existing
 print queue with one that has been uploaded before;</p></li><li><p>add an entirely new printer to the Samba host (only in
-conjunction with a working <a class="indexterm" name="id2905779"></a><i class="parameter"><tt>add printer command</tt></i>;
-a corresponding <a class="indexterm" name="id2905795"></a><i class="parameter"><tt>delete printer command</tt></i> for
+conjunction with a working <a class="indexterm" name="id2903334"></a><i class="parameter"><tt>add printer command</tt></i>;
+a corresponding <a class="indexterm" name="id2903350"></a><i class="parameter"><tt>delete printer command</tt></i> for
 removing entries from the <span class="guiicon">Printers...</span> folder
 may be provided too)</p></li></ul></div><p>
 The last one (add a new printer) requires more effort than the
 previous ones. In order to use the APW to successfully add a printer
-to a Samba server, the <a class="indexterm" name="id2905824"></a><i class="parameter"><tt>add printer command</tt></i> must
+to a Samba server, the <a class="indexterm" name="id2903380"></a><i class="parameter"><tt>add printer command</tt></i> must
 have a defined value. The program hook must successfully add the
 printer to the UNIX print system (i.e. to
 <tt class="filename">/etc/printcap</tt>,
@@ -7506,11 +7506,11 @@ exist, smbd will execute the <i class="parameter"><tt>add printer
 command</tt></i> and reparse to the 
 to attempt to locate the new printer share. If the share is still not
 defined, an error of <span class="errorname">Access Denied</span> is
-returned to the client.  Note that the <a class="indexterm" name="id2905874"></a><i class="parameter"><tt>add printer command</tt></i> is executed under the context of the connected
-user, not necessarily a root account. A <a class="indexterm" name="id2905891"></a><i class="parameter"><tt>map to guest</tt></i> = bad user may have connected you unwittingly under the wrong
+returned to the client.  Note that the <a class="indexterm" name="id2903429"></a><i class="parameter"><tt>add printer command</tt></i> is executed under the context of the connected
+user, not necessarily a root account. A <a class="indexterm" name="id2903446"></a><i class="parameter"><tt>map to guest</tt></i> = bad user may have connected you unwittingly under the wrong
 privilege; you should check it by using the
 <b class="command">smbstatus</b> command.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905915"></a>Weird Error Message <span class="errorname">Cannot connect under a
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903470"></a>Weird Error Message <span class="errorname">Cannot connect under a
 different Name</span></h3></div></div><div></div></div><p>
 Once you are connected with the wrong credentials, there is no means
 to reverse the situation other than to close all Explorer windows, and
@@ -7540,7 +7540,7 @@ message. You close all Explorer Windows and start it again. You try to
 connect - and this times it works!  Windows seems to cache connection
 info somewhere and doesn't keep it up to date (if you are unlucky you
 might need to reboot to get rid of the error message).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906013"></a>Be careful when assembling Driver Files</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903569"></a>Be careful when assembling Driver Files</h3></div></div><div></div></div><p>
 You need to be very careful when you take notes about the files and
 belonging to a particular driver. Don't confuse the files for driver
 version "0" (for Win95/98/ME, going into
@@ -7681,7 +7681,7 @@ In my example were even more differences than shown here.  Conclusion:
 you must be very careful to select the correct driver files for each
 driver version. Don't rely on the names alone. Don't interchange files
 belonging to different driver versions.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906300"></a>Samba and Printer Ports</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903854"></a>Samba and Printer Ports</h3></div></div><div></div></div><p>
 Windows NT/2000 print servers associate a port with each
 printer. These normally take the form of <tt class="filename">LPT1:</tt>,
 <tt class="filename">COM1:</tt>, <tt class="filename">FILE:</tt>, etc. Samba
@@ -7700,16 +7700,16 @@ multiple ports as a form of load balancing or fail over.
 If you require that multiple ports be defined for some reason or
 another (&#8220;<span class="quote">My users and my Boss should not know that they are
 working with Samba</span>&#8221;),  possesses a
-<a class="indexterm" name="id2906359"></a><i class="parameter"><tt>enumports command</tt></i> which can be used to define
+<a class="indexterm" name="id2903913"></a><i class="parameter"><tt>enumports command</tt></i> which can be used to define
 an external program that generates a listing of ports on a system.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906377"></a>Avoiding the most common Misconfigurations of the Client Driver</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903932"></a>Avoiding the most common Misconfigurations of the Client Driver</h3></div></div><div></div></div><p>
 So - printing works, but there are still problems. Most jobs print
 well, some don't print at all. Some jobs have problems with fonts,
 which don't look good at all. Some jobs print fast, and some are
 dead-slow. We can't cover it all; but we want to encourage you to read
 the little paragraph about "Avoiding the wrong PostScript Driver
 Settings" in the CUPS Printing part of this document.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2906398"></a>The Imprints Toolset</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2903954"></a>The Imprints Toolset</h2></div></div><div></div></div><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
@@ -7726,20 +7726,20 @@ coordinate your efforts on the samba-technical mailing list. The
 toolset is still in usable form; but only for a series of older
 printer models, where there are prepared packages to use. Packages for
 more up to date print devices are needed if Imprints should have a
-future.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906443"></a>What is Imprints?</h3></div></div><div></div></div><p>
+future.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903998"></a>What is Imprints?</h3></div></div><div></div></div><p>
 Imprints is a collection of tools for supporting these goals:
 </p><div class="itemizedlist"><ul type="disc"><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
 printer drivers from a central internet (or intranet) Imprints Server
 repository and install them on remote Samba and Windows NT4 print
-servers.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906484"></a>Creating Printer Driver Packages</h3></div></div><div></div></div><p>
+servers.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904040"></a>Creating Printer Driver Packages</h3></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906504"></a>The Imprints Server</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904059"></a>The Imprints Server</h3></div></div><div></div></div><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
@@ -7747,7 +7747,7 @@ package is digitally signed via GnuPG which can be used to verify that
 package downloaded is actually the one referred in the Imprints
 database. It is strongly recommended that this security check
 <span class="emphasis"><em>not</em></span> be disabled.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906528"></a>The Installation Client</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904083"></a>The Installation Client</h3></div></div><div></div></div><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.
@@ -7788,7 +7788,7 @@ if is has not already been installed?
 The way of sidestepping this limitation is to require that all
 Imprints printer driver packages include both the Intel Windows NT and
 95/98 printer drivers and that NT driver is installed first.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2906681"></a>Add Network Printers at Logon without User Interaction</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904236"></a>Add Network Printers at Logon without User Interaction</h2></div></div><div></div></div><p>
 The following MS Knowledge Base article may be of some help if you
 need to handle Windows 2000 clients: <span class="emphasis"><em>How to Add Printers
 with No User Interaction in Windows 2000.</em></span> ( <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;189105</a>
@@ -7857,7 +7857,7 @@ at logon time will not really be noticeable. Printers can be centrally
 added, changed, and deleted at will on the server with no user
 intervention required on the clients (you just need to keep the logon
 scripts up to date).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907000"></a>The <b class="command">addprinter</b> command</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904556"></a>The <b class="command">addprinter</b> command</h2></div></div><div></div></div><p>
 The <b class="command">addprinter</b> command can be configured to be a
 shell script or program executed by Samba. It is triggered by running
 the APW from a client against the Samba print server. The APW asks the
@@ -7869,7 +7869,7 @@ on legacy systems, or execute the <b class="command">lpadmin</b> command
 on more modern systems) and create the associated share in
 , then the APW will in effect really
 create a new printer on Samba and the UNIX print subsystem!
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907046"></a>Migration of "Classical" printing to Samba</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904602"></a>Migration of "Classical" printing to Samba</h2></div></div><div></div></div><p>
 The basic "NT-style" printer driver management has not changed
 considerably in 3.0 over the 2.2.x releases (apart from many small
 improvements). Here migration should be quite easy, especially if you
@@ -7905,9 +7905,9 @@ rpcclient. See the Imprints installation client at:
 	<a href="http://imprints.sourceforge.net/" target="_top">http://imprints.sourceforge.net/</a>
 </p><p>
 for an example. See also the discussion of rpcclient usage in the
-"CUPS Printing" section.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907213"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div><div></div></div><p>
+"CUPS Printing" section.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904779"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div><div></div></div><p>
 We will publish an update to this section shortly.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907227"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907234"></a>I give my root password but I don't get access</h3></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904793"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904800"></a>I give my root password but I don't get access</h3></div></div><div></div></div><p>
 Don't confuse the root password which is valid for the UNIX system
 (and in most cases stored in the form of a one-way hash in a file
 named <tt class="filename">/etc/shadow</tt>) with the password used to
@@ -7915,40 +7915,40 @@ authenticate against Samba!. Samba doesn't know the UNIX password; for
 root to access Samba resources via Samba-type access, a Samba account
 for root must be created first. This is often done with the
 <b class="command">smbpasswd</b> command.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907268"></a>My printjobs get spooled into the spooling directory, but then get lost</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904834"></a>My printjobs get spooled into the spooling directory, but then get lost</h3></div></div><div></div></div><p>
 Don't use the existing UNIX print system spool directory for the Samba
 spool directory. It may seem convenient and a saving of space, but it
 only leads to problems. The two <span class="emphasis"><em>must</em></span> be separate.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter�19.�CUPS Printing Support in Samba 3.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (3 June 2003) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2907403">Introduction</a></dt><dd><dl><dt><a href="#id2907410">Features and Benefits</a></dt><dt><a href="#id2907453">Overview</a></dt></dl></dd><dt><a href="#id2907507">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2907600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2907841">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2908016">More complex smb.conf Settings for
-CUPS</a></dt></dl></dd><dt><a href="#id2908362">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2908382">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2908431">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2908485">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2908552">Explicitly enable "raw" printing for
-application/octet-stream!</a></dt><dt><a href="#id2908739">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2908865">Using CUPS/Samba in an advanced Way -- intelligent printing
-with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2909034">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2909441">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2909567">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2909654">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2909760">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2909782">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2909959">MIME types and CUPS Filters</a></dt><dt><a href="#id2910165">MIME type Conversion Rules</a></dt><dt><a href="#id2910315">Filter Requirements</a></dt><dt><a href="#id2910493">Prefilters</a></dt><dt><a href="#id2910595">pstops</a></dt><dt><a href="#id2910704">pstoraster</a></dt><dt><a href="#id2910875">imagetops and imagetoraster</a></dt><dt><a href="#id2910938">rasterto [printers specific]</a></dt><dt><a href="#id2911090">CUPS Backends</a></dt><dt><a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2911562">The Complete Picture</a></dt><dt><a href="#id2911576">mime.convs</a></dt><dt><a href="#id2911630">"Raw" printing</a></dt><dt><a href="#id2911697">"application/octet-stream" printing</a></dt><dt><a href="#id2911929">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a></dt><dt><a href="#id2912410">Examples for filtering Chains</a></dt><dt><a href="#id2912731">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2912872">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2912949">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2912965">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2913020">Driver Execution on the Client</a></dt><dt><a href="#id2913090">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2913201">Network Printing (Windows clients -- UNIX/Samba Print
-Servers)</a></dt><dd><dl><dt><a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2913432">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2913594">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2913643">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2913717">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2913734">Printer Drivers running in "Kernel Mode" cause many
-Problems</a></dt><dt><a href="#id2913768">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2913789">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2913833">PostScript Drivers with no major problems -- even in Kernel
-Mode</a></dt></dl></dd><dt><a href="#id2913895">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2913913">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2914014">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2914516">Recognize the different Driver Files</a></dt><dt><a href="#id2914656">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2914689">ESP Print Pro Package of "PostScript Driver for
-WinNT/2k/XP"</a></dt><dt><a href="#id2914749">Caveats to be considered</a></dt><dt><a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2915344">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2915567">Understanding cupsaddsmb</a></dt><dt><a href="#id2915714">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2915798">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2915877">cupsaddsmb Flowchart</a></dt><dt><a href="#id2915946">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2916097">Avoiding critical PostScript Driver Settings on the
-Client</a></dt></dl></dd><dt><a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a></dt><dd><dl><dt><a href="#id2916423">A Check of the rpcclient man Page</a></dt><dt><a href="#id2916536">Understanding the rpcclient man page</a></dt><dt><a href="#id2916644">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2916790">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2918021">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2918418">Trivial DataBase Files</a></dt><dt><a href="#id2918497">Binary Format</a></dt><dt><a href="#id2918559">Losing *.tdb Files</a></dt><dt><a href="#id2918617">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2918890">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2919583">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2920055">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2920098">Setting up Quotas</a></dt><dt><a href="#id2920162">Correct and incorrect Accounting</a></dt><dt><a href="#id2920202">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2920282">The page_log File Syntax</a></dt><dt><a href="#id2920392">Possible Shortcomings</a></dt><dt><a href="#id2920463">Future Developments</a></dt><dt><a href="#id2920510">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2920525">Additional Material</a></dt><dt><a href="#id2920734">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2920792">CUPS Configuration Settings explained</a></dt><dt><a href="#id2920874">Pre-conditions</a></dt><dt><a href="#id2921030">Manual Configuration</a></dt></dl></dd><dt><a href="#id2921088">In Case of Trouble.....</a></dt><dt><a href="#id2921154">Printing from CUPS to Windows attached
-Printers</a></dt><dt><a href="#id2921434">More CUPS filtering Chains</a></dt><dt><a href="#id2921535">Common Errors</a></dt><dd><dl><dt><a href="#id2921542">Win9x client can't install driver</a></dt><dt><a href="#id2921558">"cupsaddsmb" keeps asking for root password in
-			neverending loop</a></dt><dt><a href="#id2921604">"cupsaddsmb" gives "No PPD file for printer..."
-			message while PPD file is present</a></dt><dt><a href="#id2921660">Client can't connect to Samba printer</a></dt><dt><a href="#id2921688">Can't reconnect to Samba under new account
-			from Win2K/XP</a></dt><dt><a href="#id2921914">Avoid being connected to the Samba server as the
-		"wrong" user</a></dt><dt><a href="#id2921967">Upgrading to CUPS drivers from Adobe drivers on
-		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2921981">Can't use "cupsaddsmb" on Samba server which is
-		a PDC</a></dt><dt><a href="#id2922010">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2922027">Win2K/XP "Local Security
-		Policies"</a></dt><dt><a href="#id2922043">WinXP clients: "Administrator can not install
-		printers for all local users"</a></dt><dt><a href="#id2922065">"Print Change Notify" functions on
-		NT-clients</a></dt><dt><a href="#id2922084">WinXP-SP1</a></dt><dt><a href="#id2922126">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2922400">Most common blunders in driver
-		settings on Windows clients</a></dt><dt><a href="#id2922445">cupsaddsmb does not work
-		with newly installed printer</a></dt><dt><a href="#id2922506">Permissions on
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter�19.�CUPS Printing Support in Samba 3.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (3 June 2003) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2904970">Introduction</a></dt><dd><dl><dt><a href="#id2904977">Features and Benefits</a></dt><dt><a href="#id2905020">Overview</a></dt></dl></dd><dt><a href="#id2905074">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2905167">Linking of smbd with libcups.so</a></dt><dt><a href="#id2905408">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2905584">More complex smb.conf Settings for
+CUPS</a></dt></dl></dd><dt><a href="#id2905929">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2905949">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2905999">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2906051">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2906119">Explicitly enable "raw" printing for
+application/octet-stream!</a></dt><dt><a href="#id2906306">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2906432">Using CUPS/Samba in an advanced Way -- intelligent printing
+with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2906600">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2907029">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2907154">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2907241">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2907348">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2907370">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2907545">MIME types and CUPS Filters</a></dt><dt><a href="#id2907752">MIME type Conversion Rules</a></dt><dt><a href="#id2907903">Filter Requirements</a></dt><dt><a href="#id2908080">Prefilters</a></dt><dt><a href="#id2908183">pstops</a></dt><dt><a href="#id2908292">pstoraster</a></dt><dt><a href="#id2908476">imagetops and imagetoraster</a></dt><dt><a href="#id2908539">rasterto [printers specific]</a></dt><dt><a href="#id2908691">CUPS Backends</a></dt><dt><a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2909176">The Complete Picture</a></dt><dt><a href="#id2909191">mime.convs</a></dt><dt><a href="#id2909245">"Raw" printing</a></dt><dt><a href="#id2909312">"application/octet-stream" printing</a></dt><dt><a href="#id2909544">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a></dt><dt><a href="#id2910018">Examples for filtering Chains</a></dt><dt><a href="#id2910331">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2910470">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2910560">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2910577">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2910632">Driver Execution on the Client</a></dt><dt><a href="#id2910701">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2910813">Network Printing (Windows clients -- UNIX/Samba Print
+Servers)</a></dt><dd><dl><dt><a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2911043">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2911206">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2911255">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2911328">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2911345">Printer Drivers running in "Kernel Mode" cause many
+Problems</a></dt><dt><a href="#id2911379">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2911400">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2911445">PostScript Drivers with no major problems -- even in Kernel
+Mode</a></dt></dl></dd><dt><a href="#id2911506">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2911524">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2911625">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2912128">Recognize the different Driver Files</a></dt><dt><a href="#id2912268">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2912301">ESP Print Pro Package of "PostScript Driver for
+WinNT/2k/XP"</a></dt><dt><a href="#id2912362">Caveats to be considered</a></dt><dt><a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2912958">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2913117">Understanding cupsaddsmb</a></dt><dt><a href="#id2913264">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2913349">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2913427">cupsaddsmb Flowchart</a></dt><dt><a href="#id2913497">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2913646">Avoiding critical PostScript Driver Settings on the
+Client</a></dt></dl></dd><dt><a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a></dt><dd><dl><dt><a href="#id2913973">A Check of the rpcclient man Page</a></dt><dt><a href="#id2914086">Understanding the rpcclient man page</a></dt><dt><a href="#id2914186">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2914333">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2915566">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2915962">Trivial DataBase Files</a></dt><dt><a href="#id2916041">Binary Format</a></dt><dt><a href="#id2916103">Losing *.tdb Files</a></dt><dt><a href="#id2916162">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2916436">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2917129">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2917602">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2917645">Setting up Quotas</a></dt><dt><a href="#id2917708">Correct and incorrect Accounting</a></dt><dt><a href="#id2917748">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2917829">The page_log File Syntax</a></dt><dt><a href="#id2917938">Possible Shortcomings</a></dt><dt><a href="#id2918010">Future Developments</a></dt><dt><a href="#id2918058">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2918072">Additional Material</a></dt><dt><a href="#id2918267">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2918326">CUPS Configuration Settings explained</a></dt><dt><a href="#id2918407">Pre-conditions</a></dt><dt><a href="#id2918564">Manual Configuration</a></dt></dl></dd><dt><a href="#id2918622">In Case of Trouble.....</a></dt><dt><a href="#id2918682">Printing from CUPS to Windows attached
+Printers</a></dt><dt><a href="#id2918955">More CUPS filtering Chains</a></dt><dt><a href="#id2796634">Common Errors</a></dt><dd><dl><dt><a href="#id2796642">Win9x client can't install driver</a></dt><dt><a href="#id2919061">"cupsaddsmb" keeps asking for root password in
+			neverending loop</a></dt><dt><a href="#id2919107">"cupsaddsmb" gives "No PPD file for printer..."
+			message while PPD file is present</a></dt><dt><a href="#id2919163">Client can't connect to Samba printer</a></dt><dt><a href="#id2919497">Can't reconnect to Samba under new account
+			from Win2K/XP</a></dt><dt><a href="#id2919582">Avoid being connected to the Samba server as the
+		"wrong" user</a></dt><dt><a href="#id2919635">Upgrading to CUPS drivers from Adobe drivers on
+		NT/2K/XP clients gives problems</a></dt><dt><a href="#id2919649">Can't use "cupsaddsmb" on Samba server which is
+		a PDC</a></dt><dt><a href="#id2919678">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2919695">Win2K/XP "Local Security
+		Policies"</a></dt><dt><a href="#id2919711">WinXP clients: "Administrator can not install
+		printers for all local users"</a></dt><dt><a href="#id2919733">"Print Change Notify" functions on
+		NT-clients</a></dt><dt><a href="#id2919752">WinXP-SP1</a></dt><dt><a href="#id2919794">Print options for all	users can't be set on Win2K/XP</a></dt><dt><a href="#id2920067">Most common blunders in driver
+		settings on Windows clients</a></dt><dt><a href="#id2920114">cupsaddsmb does not work
+		with newly installed printer</a></dt><dt><a href="#id2920175">Permissions on
 /var/spool/samba/ get reset after each
-reboot</a></dt><dt><a href="#id2922615">Printer named "lp"
+reboot</a></dt><dt><a href="#id2920284">Printer named "lp"
 intermittently swallows jobs and spits out completely different
-ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2922701">An Overview of the CUPS Printing Processes</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907403"></a>Introduction</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907410"></a>Features and Benefits</h3></div></div><div></div></div><p>
+ones</a></dt><dt><a href="#id2920314">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2920369">An Overview of the CUPS Printing Processes</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904970"></a>Introduction</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904977"></a>Features and Benefits</h3></div></div><div></div></div><p>
 			The Common UNIX Print System (<a href="http://www.cups.org/" target="_top">CUPS</a>) has become very popular. All
 			major Linux distributions now ship it as their default printing
 			system. To many it is still a very mystical tool.  Mostly, it
@@ -7966,7 +7966,7 @@ ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files
 			from the beginning. This documentation will lead you to a
 			complete understanding of CUPS. Let's start with the most basic
 			things first.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907453"></a>Overview</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905020"></a>Overview</h3></div></div><div></div></div><p>
 			CUPS is more than just a print spooling system. It is a complete
 			printer management system that complies with the new IPP
 			(<span class="emphasis"><em>Internet Printing Protocol</em></span>). IPP is an industry
@@ -7986,10 +7986,10 @@ ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files
 			argue that CUPS is better! In any case, let us now move on to
 			explore how one may configure CUPS for interfacing with MS Windows
 			print clients via Samba.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907507"></a>Basic Configuration of CUPS support</h2></div></div><div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905074"></a>Basic Configuration of CUPS support</h2></div></div><div></div></div><p>
 		Printing with CUPS in the most basic <tt class="filename">smb.conf</tt> setup in Samba 3.0 (as was true for 2.2.x) only needs two
-		settings: <a class="indexterm" name="id2907526"></a><i class="parameter"><tt>printing</tt></i> = cups and
-		<a class="indexterm" name="id2907540"></a><i class="parameter"><tt>printcap</tt></i> = cups. CUPS does not need a printcap file.
+		settings: <a class="indexterm" name="id2905093"></a><i class="parameter"><tt>printing</tt></i> = cups and
+		<a class="indexterm" name="id2905107"></a><i class="parameter"><tt>printcap</tt></i> = cups. CUPS does not need a printcap file.
 		However, the <tt class="filename">cupsd.conf</tt> configuration file knows of two related directives that control
 		how such a file will be automatically created and maintained by CUPS for the convenience of third party
 		applications (example: <i class="parameter"><tt>Printcap /etc/printcap</tt></i> and <i class="parameter"><tt>PrintcapFormat BSD</tt></i>).
@@ -7997,7 +7997,7 @@ ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files
 		print. Make sure CUPS is set to generate and maintain a printcap file! For details see
 		<b class="command">man cupsd.conf</b> and other CUPS-related documentation, like the wealth of documents on your CUPS server
 		itself: <a href="http://localhost:631/documentation.html" target="_top">http://localhost:631/documentation.html</a>.
-	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907600"></a>Linking of smbd with libcups.so</h3></div></div><div></div></div><p>
+	</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905167"></a>Linking of smbd with libcups.so</h3></div></div><div></div></div><p>
 			Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support.
 			Most recent installations have this support enabled. Per default CUPS linking is compiled
 			into smbd and other Samba binaries. Of course, you can use CUPS even
@@ -8005,7 +8005,7 @@ ones</a></dt><dt><a href="#id2922646">Location of Adobe PostScript driver files
 			there are some differences in required or supported configuration
 			then.
 		</p><p>
-			When Samba is compiled against libcups, <a class="indexterm" name="id2907630"></a><i class="parameter"><tt>printcap</tt></i> = cups
+			When Samba is compiled against libcups, <a class="indexterm" name="id2905197"></a><i class="parameter"><tt>printcap</tt></i> = cups
 			uses the CUPS API to list printers, submit jobs, query queues, etc.  Otherwise it maps to the System V
 			commands with an additional <b class="command">-oraw</b> option for printing. On a Linux
 			system, you can use the <b class="command">ldd</b> utility to find out details (ldd may not be present on
@@ -8022,17 +8022,17 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 			is set, then <span class="emphasis"><em>any otherwise manually set print command in <tt class="filename">smb.conf</tt> is ignored</em></span>.
 			This is an important point to remember!
 		</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Should it be necessary, for any reason, to set your own print commands, you can do this by setting
-		<a class="indexterm" name="id2907724"></a><i class="parameter"><tt>printing</tt></i> = sysv. However, you will loose all the benefits
+		<a class="indexterm" name="id2905291"></a><i class="parameter"><tt>printing</tt></i> = sysv. However, you will loose all the benefits
 		of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands
-		(most important: <a class="indexterm" name="id2907741"></a><i class="parameter"><tt>print command</tt></i>; other commands are
-				<a class="indexterm" name="id2907755"></a><i class="parameter"><tt>lppause command</tt></i>,
-				<a class="indexterm" name="id2907769"></a><i class="parameter"><tt>lpresume command</tt></i>,
-				<a class="indexterm" name="id2907783"></a><i class="parameter"><tt>lpq command</tt></i>,
-				<a class="indexterm" name="id2907796"></a><i class="parameter"><tt>lprm command</tt></i>,
-				<a class="indexterm" name="id2907811"></a><i class="parameter"><tt>queuepause command</tt></i> and
-				<a class="indexterm" name="id2907825"></a><i class="parameter"><tt>queue resume command</tt></i>).</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907841"></a>Simple <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p>
+		(most important: <a class="indexterm" name="id2905308"></a><i class="parameter"><tt>print command</tt></i>; other commands are
+				<a class="indexterm" name="id2905322"></a><i class="parameter"><tt>lppause command</tt></i>,
+				<a class="indexterm" name="id2905336"></a><i class="parameter"><tt>lpresume command</tt></i>,
+				<a class="indexterm" name="id2905350"></a><i class="parameter"><tt>lpq command</tt></i>,
+				<a class="indexterm" name="id2905364"></a><i class="parameter"><tt>lprm command</tt></i>,
+				<a class="indexterm" name="id2905378"></a><i class="parameter"><tt>queuepause command</tt></i> and
+				<a class="indexterm" name="id2905392"></a><i class="parameter"><tt>queue resume command</tt></i>).</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905408"></a>Simple <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p>
 			To summarize, here is the simplest printing-related setup for <tt class="filename">smb.conf</tt> to enable basic CUPS support:
-		</p><div class="example"><a name="id2907869"></a><p class="title"><b>Example�19.1.�Simplest printing-related smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root, @ntadmins</tt></i></td></tr></table></div><p>
+		</p><div class="example"><a name="id2905436"></a><p class="title"><b>Example�19.1.�Simplest printing-related smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root, @ntadmins</tt></i></td></tr></table></div><p>
 			This is all you need for basic printing setup for CUPS. It will print
 			all Graphic, Text, PDF and PostScript file submitted from Windows
 			clients. However, most of your Windows users would not know how to
@@ -8047,26 +8047,26 @@ libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
 			printer is not a PostScript device, the print data stream is "binary",
 			sensible only for the target printer. Read on to learn which problem
 			this may cause and how to avoid it.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908016"></a>More complex <tt class="filename">smb.conf</tt> Settings for
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905584"></a>More complex <tt class="filename">smb.conf</tt> Settings for
 CUPS</h3></div></div><div></div></div><p>
 Here is a slightly more complex printing-related setup
 for <tt class="filename">smb.conf</tt>. It enables general CUPS printing
 support for all printers, but defines one printer share which is set
 up differently.
-</p><div class="example"><a name="id2908047"></a><p class="title"><b>Example�19.2.�Overriding global CUPS settings for one printer</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root, @ntadmins</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[special_printer]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = A special printer with his own settings</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba-special</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = sysv</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap = lpstat</tt></i></td></tr><tr><td><i class="parameter"><tt>print command = echo "NEW: `date`: printfile %f" &gt;&gt; /tmp/smbprn.log ; \</tt></i></td></tr><tr><td><i class="parameter"><tt>echo "     `date`: p-%p s-%s f-%f" &gt;&gt; /tmp/smbprn.log ; \</tt></i></td></tr><tr><td><i class="parameter"><tt>echo "     `date`: j-%j J-%J z-%z c-%c" &gt;&gt; /tmp/smbprn.log : rm %f</tt></i></td></tr><tr><td><i class="parameter"><tt>public = no</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = kurt</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2905615"></a><p class="title"><b>Example�19.2.�Overriding global CUPS settings for one printer</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root, @ntadmins</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[special_printer]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = A special printer with his own settings</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba-special</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = sysv</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap = lpstat</tt></i></td></tr><tr><td><i class="parameter"><tt>print command = echo "NEW: `date`: printfile %f" &gt;&gt; /tmp/smbprn.log ; \</tt></i></td></tr><tr><td><i class="parameter"><tt>echo "     `date`: p-%p s-%s f-%f" &gt;&gt; /tmp/smbprn.log ; \</tt></i></td></tr><tr><td><i class="parameter"><tt>echo "     `date`: j-%j J-%J z-%z c-%c" &gt;&gt; /tmp/smbprn.log : rm %f</tt></i></td></tr><tr><td><i class="parameter"><tt>public = no</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = kurt</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</tt></i></td></tr></table></div><p>
 This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters
 known to Samba into the <tt class="filename">/tmp/smbprn.log</tt> file and deletes the jobfile. Moreover, the
-<a class="indexterm" name="id2908312"></a><i class="parameter"><tt>printer admin</tt></i> of this share is "kurt" (not the "@ntadmins" group);
+<a class="indexterm" name="id2905879"></a><i class="parameter"><tt>printer admin</tt></i> of this share is "kurt" (not the "@ntadmins" group);
 guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only
 allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set
-<a class="indexterm" name="id2908332"></a><i class="parameter"><tt>printing</tt></i> = sysv and
-<a class="indexterm" name="id2908345"></a><i class="parameter"><tt>printcap</tt></i> = lpstat.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2908362"></a>Advanced Configuration</h2></div></div><div></div></div><p>
+<a class="indexterm" name="id2905899"></a><i class="parameter"><tt>printing</tt></i> = sysv and
+<a class="indexterm" name="id2905912"></a><i class="parameter"><tt>printcap</tt></i> = lpstat.
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905929"></a>Advanced Configuration</h2></div></div><div></div></div><p>
 Before we delve into all the configuration options, let us clarify a few
 points. <span class="emphasis"><em>Network printing needs to be organized and setup
 correctly</em></span>. Often this is not done correctly. Legacy systems
 or small business LAN environments often lack design and good housekeeping.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908382"></a>Central spooling vs. "Peer-to-Peer" printing</h3></div></div><div></div></div><a class="indexterm" name="id2908391"></a><a class="indexterm" name="id2908402"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905949"></a>Central spooling vs. "Peer-to-Peer" printing</h3></div></div><div></div></div><a class="indexterm" name="id2905958"></a><a class="indexterm" name="id2905970"></a><p>
 Many small office or home networks, as well as badly organized larger
 environments, allow each client a direct access to available network
 printers. This is generally a bad idea. It often blocks one client's
@@ -8078,8 +8078,8 @@ is the usage of a "print server": it routes all jobs through one
 central system, which responds immediately, takes jobs from multiple
 concurrent clients at the same time and in turn transfers them to the
 printer(s) in the correct order.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908431"></a>CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</h3></div></div><div></div></div><a class="indexterm" name="id2908441"></a><a class="indexterm" name="id2908450"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905999"></a>CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</h3></div></div><div></div></div><a class="indexterm" name="id2906008"></a><a class="indexterm" name="id2906017"></a><p>
 Most traditionally configured UNIX print servers acting on behalf of
 Samba's Windows clients represented a really simple setup. Their only
 task was to manage the "raw" spooling of all jobs handed to them by
@@ -8097,14 +8097,14 @@ sent in a format that is suitable for direct delivery to the
 printer. Clients need to run the vendor-provided drivers to do
 this. In this case CUPS will NOT do any print file format conversion
 work.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908485"></a>Driver Installation Methods on Windows Clients</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906051"></a>Driver Installation Methods on Windows Clients</h3></div></div><div></div></div><p>
 The printer drivers on the Windows clients may be installed
 in two functionally different ways:
 </p><div class="itemizedlist"><ul type="disc"><li><p>manually install the drivers locally on each client,
 one by one; this yields the old <span class="emphasis"><em>LanMan</em></span> style
 printing; it uses a <tt class="filename">\\sambaserver\printershare</tt>
 type of connection.</p></li><li><p>
-<a class="indexterm" name="id2908527"></a>
+<a class="indexterm" name="id2906094"></a>
 		deposit and prepare the drivers (for later download) on
 the print server (Samba); this enables the clients to use
 "Point and Print" to get drivers semi-automatically installed the
@@ -8112,8 +8112,8 @@ first time they access the printer; with this method NT/2K/XP
 clients use the <span class="emphasis"><em>SPOOLSS/MS-RPC</em></span>
 type printing calls.</p></li></ul></div><p>
 The second method is recommended for use over the first.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908552"></a>Explicitly enable "raw" printing for
-<span class="emphasis"><em>application/octet-stream</em></span>!</h3></div></div><div></div></div><a class="indexterm" name="id2908565"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906119"></a>Explicitly enable "raw" printing for
+<span class="emphasis"><em>application/octet-stream</em></span>!</h3></div></div><div></div></div><a class="indexterm" name="id2906132"></a><p>
 If you use the first option (drivers are installed on the client
 side), there is one setting to take care of: CUPS needs to be told
 that it should allow "raw" printing of deliberate (binary) file
@@ -8130,7 +8130,7 @@ present:
 </pre><p>
 In <tt class="filename">/etc/cups/mime.convs</tt>,
 have this line:
-</p><a class="indexterm" name="id2908633"></a><pre class="screen">
+</p><a class="indexterm" name="id2906200"></a><pre class="screen">
  application/octet-stream   application/vnd.cups-raw   0   - 
 </pre><p>
 If these two files are not set up correctly for raw Windows client
@@ -8140,7 +8140,7 @@ convert file 0</tt> in your CUPS error_log file.
 <tt class="filename">mime.types</tt> file does not
 <span class="emphasis"><em>enforce</em></span> "raw" printing, it only
 <span class="emphasis"><em>allows</em></span> it.
-</p></div><p><b>Background.�</b><a class="indexterm" name="id2908698"></a>
+</p></div><p><b>Background.�</b><a class="indexterm" name="id2906266"></a>
 CUPS being a more security-aware printing system than traditional ones
 does not by default allow a user to send deliberate (possibly binary)
 data to printing devices. This could be easily abused to launch a
@@ -8157,7 +8157,7 @@ This is all you need to know to get the CUPS/Samba combo printing
 locally installed. If you are not interested in background information about
 more advanced CUPS/Samba printing, simply skip the remaining sections
 of this chapter.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908739"></a>Three familiar Methods for driver upload plus a new one</h3></div></div><div></div></div><a class="indexterm" name="id2908747"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906306"></a>Three familiar Methods for driver upload plus a new one</h3></div></div><div></div></div><a class="indexterm" name="id2906315"></a><p>
 If you want to use the MS-RPC type printing, you must upload the
 drivers onto the Samba server first (<i class="parameter"><tt>[print$]</tt></i>
 share). For a discussion on how to deposit printer drivers on the
@@ -8165,24 +8165,24 @@ Samba host (so that the Windows clients can download and use them via
 "Point'n'Print") please also refer to the previous chapter of this
 HOWTO Collection. There you will find a description or reference to
 three methods of preparing the client drivers on the Samba server:
-</p><a class="indexterm" name="id2908775"></a><div class="itemizedlist"><ul type="disc"><li><p>the GUI, "Add Printer Wizard"
+</p><a class="indexterm" name="id2906342"></a><div class="itemizedlist"><ul type="disc"><li><p>the GUI, "Add Printer Wizard"
 <span class="emphasis"><em>upload-from-a-Windows-client</em></span>
 method;</p></li><li><p>the commandline, "smbclient/rpcclient"
 <span class="emphasis"><em>upload-from-a-UNIX-workstation</em></span>
 method;</p></li><li><p>
-<a class="indexterm" name="id2908813"></a>
+<a class="indexterm" name="id2906380"></a>
 		the <span class="emphasis"><em>Imprints</em></span> Toolset
 method.</p></li></ul></div><p>
 These 3 methods apply to CUPS all the same. A new and more
 convenient way to load the Windows drivers into Samba is provided
 if you use CUPS:
-</p><a class="indexterm" name="id2908834"></a><div class="itemizedlist"><ul type="disc"><li><p>the <span class="emphasis"><em>cupsaddsmb</em></span>
+</p><a class="indexterm" name="id2906402"></a><div class="itemizedlist"><ul type="disc"><li><p>the <span class="emphasis"><em>cupsaddsmb</em></span>
 utility.</p></li></ul></div><p>
 cupsaddsmb is discussed in much detail further below. But we will
 first explore the CUPS filtering system and compare the Windows and
 UNIX printing architectures.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2908865"></a>Using CUPS/Samba in an advanced Way -- intelligent printing
-with PostScript Driver Download</h2></div></div><div></div></div><a class="indexterm" name="id2908874"></a><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2906432"></a>Using CUPS/Samba in an advanced Way -- intelligent printing
+with PostScript Driver Download</h2></div></div><div></div></div><a class="indexterm" name="id2906442"></a><p>
 Are you still following this? Good. Let's go into more detail then. We now know
 how to set up a "dump" printserver, that is, a server which is spooling
 printjobs "raw", leaving the print data untouched.
@@ -8206,11 +8206,11 @@ how CUPS works and how you can enable its features.
 What follows is the comparison of some fundamental concepts for
 Windows and UNIX printing; then is the time for a description of the
 CUPS filtering system, how it works and how you can tweak it.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gdipost"></a>GDI on Windows -- PostScript on UNIX</h3></div></div><div></div></div><a class="indexterm" name="id2908964"></a><a class="indexterm" name="id2908972"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gdipost"></a>GDI on Windows -- PostScript on UNIX</h3></div></div><div></div></div><a class="indexterm" name="id2906532"></a><a class="indexterm" name="id2906540"></a><p>
 Network printing is one of the most complicated and error-prone
 day-to-day tasks any user or an administrator may encounter. This is
 true for all OS platforms. And there are reasons for this.
-</p><a class="indexterm" name="id2908988"></a><a class="indexterm" name="id2908997"></a><p>
+</p><a class="indexterm" name="id2906556"></a><a class="indexterm" name="id2906564"></a><p>
 You can't expect for most file formats to just throw them towards
 printers and they get printed. There needs to be a file format
 conversion in between. The problem is: there is no common standard for
@@ -8222,7 +8222,7 @@ into semi-official "standards", by being the most widely used PDLs
 many manufacturers who "roll their own" (their reasons may be
 unacceptable license fees for using printer-embedded PostScript
 interpreters, etc.).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909034"></a>Windows Drivers, GDI and EMF</h3></div></div><div></div></div><a class="indexterm" name="id2909042"></a><a class="indexterm" name="id2909050"></a><a class="indexterm" name="id2909058"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906600"></a>Windows Drivers, GDI and EMF</h3></div></div><div></div></div><a class="indexterm" name="id2906609"></a><a class="indexterm" name="id2906618"></a><a class="indexterm" name="id2906626"></a><p>
 In Windows OS, the format conversion job is done by the printer
 drivers. On MS Windows OS platforms all application programmers have
 at their disposal a built-in API, the GDI (<span class="emphasis"><em>Graphical Device
@@ -8239,7 +8239,7 @@ the GDI, produces often a file format called EMF (<span class="emphasis"><em>Enh
 MetaFile</em></span>). The EMF is processed by the printer driver and
 converted to the printer-specific file format.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2909108"></a>
+<a class="indexterm" name="id2906676"></a>
 To the GDI foundation in MS Windows, Apple has chosen to
 put paper and screen output on a common foundation for their
 (BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating
@@ -8248,7 +8248,7 @@ Systems. Their <span class="emphasis"><em>Core Graphic Engine</em></span> uses a
 </p></div><p>
 
 </p><div class="figure"><a name="small1"></a><p class="title"><b>Figure�19.1.�Windows Printing to a local Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" width="270" alt="Windows Printing to a local Printer"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909175"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div><div></div></div><a class="indexterm" name="id2909182"></a><a class="indexterm" name="id2909191"></a><a class="indexterm" name="id2909199"></a><a class="indexterm" name="id2909207"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906741"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div><div></div></div><a class="indexterm" name="id2906749"></a><a class="indexterm" name="id2906757"></a><a class="indexterm" name="id2906766"></a><a class="indexterm" name="id2906774"></a><p>
 In UNIX and Linux, there is no comparable layer built into the OS
 kernel(s) or the X (screen display) server. Every application is
 responsible for itself to create its print output.  Fortunately, most
@@ -8268,7 +8268,7 @@ ready for prime time.) You can see this unfavorable inheritance up to
 the present day by looking into the various "font" directories on your
 system; there are separate ones for fonts used for X display and fonts
 to be used on paper.
-</p><p><b>Background.�</b><a class="indexterm" name="id2909253"></a>
+</p><p><b>Background.�</b><a class="indexterm" name="id2906821"></a>
 The PostScript programming language is an "invention" by Adobe Inc.,
 but its specifications have been published to the full. Its strength
 lies in its powerful abilities to describe graphical objects (fonts,
@@ -8284,7 +8284,7 @@ form and you will be reading its PostScript code, the language
 instructions which need to be interpreted by a rasterizer. Rasterizers
 produce pixel images, which may be displayed on screen by a viewer
 program or on paper by a printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="post-and-ghost"></a>PostScript and Ghostscript</h3></div></div><div></div></div><a class="indexterm" name="id2909299"></a><a class="indexterm" name="id2909306"></a><a class="indexterm" name="id2909318"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="post-and-ghost"></a>PostScript and Ghostscript</h3></div></div><div></div></div><a class="indexterm" name="id2906885"></a><a class="indexterm" name="id2906893"></a><a class="indexterm" name="id2906904"></a><p>
 So, UNIX is lacking a common ground for printing on paper and
 displaying on screen. Despite this unfavorable legacy for UNIX, basic
 printing is fairly easy: if you have PostScript printers at your
@@ -8297,7 +8297,7 @@ converting the PostScript drawing commands into a bitmap picture as
 you see it on paper, in a resolution as done by your printer. This is
 no different to PostScript printing of a file from a Windows origin.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2909355"></a>
+<a class="indexterm" name="id2906942"></a>
 Traditional UNIX programs and printing systems -- while
 using PostScript -- are largely not PPD-aware. PPDs are "PostScript
 Printer Description" files. They enable you to specify and control all
@@ -8307,7 +8307,7 @@ device and job options, unlike Windows or Apple users. But now there
 is CUPS....
 </p></div><p>
 	</p><div class="figure"><a name="small2"></a><p class="title"><b>Figure�19.2.�Printing to a Postscript Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/2small.png" width="270" alt="Printing to a Postscript Printer"></div></div><p>
-</p><a class="indexterm" name="id2909405"></a><p>
+</p><a class="indexterm" name="id2907006"></a><p>
 However, there are other types of printers out there. These don't know
 how to print PostScript. They use their own <span class="emphasis"><em>Page Description
 Language</em></span> (PDL, often proprietary). To print to them is much
@@ -8315,7 +8315,7 @@ more demanding. Since your UNIX applications mostly produce
 PostScript, and since these devices don't understand PostScript, you
 need to convert the printfiles to a format suitable for your printer
 on the host, before you can send it away.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909441"></a>Ghostscript -- the Software RIP for non-PostScript Printers</h3></div></div><div></div></div><a class="indexterm" name="id2909450"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907029"></a>Ghostscript -- the Software RIP for non-PostScript Printers</h3></div></div><div></div></div><a class="indexterm" name="id2907037"></a><p>
 Here is where <span class="emphasis"><em>Ghostscript</em></span> kicks in. Ghostscript is
 the traditional (and quite powerful) PostScript interpreter used on
 UNIX platforms. It is a RIP in software, capable to do a
@@ -8337,12 +8337,12 @@ intervals, now by artofcode LLC. They are initially put under the
 "AFPL" license, but re-released under the GNU GPL as soon as the next
 AFPL version appears. GNU Ghostscript is probably the version
 installed on most Samba systems. But it has got some
-deficiencies. <a class="indexterm" name="id2909498"></a>Therefore ESP Ghostscript was developed as an
+deficiencies. <a class="indexterm" name="id2907085"></a>Therefore ESP Ghostscript was developed as an
 enhancement over GNU Ghostscript, with lots of bug-fixes, additional
 devices and improvements. It is jointly maintained by developers from
 CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes
 the "cups" device (essential to print to non-PS printers from CUPS).
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909567"></a>PostScript Printer Description (PPD) Specification</h3></div></div><div></div></div><a class="indexterm" name="id2909575"></a><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907154"></a>PostScript Printer Description (PPD) Specification</h3></div></div><div></div></div><a class="indexterm" name="id2907162"></a><p>
 While PostScript in essence is a <span class="emphasis"><em>Page Description
 Language</em></span> (PDL) to represent the page layout in a
 <span class="emphasis"><em>device independent</em></span> way, real world print jobs are
@@ -8368,13 +8368,13 @@ user selections are somehow written (in the form of special
 PostScript, PJL, JCL or vendor-dependent commands) into the PostScript
 file created by the driver.
 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2909638"></a>
+<a class="indexterm" name="id2907224"></a>
 A PostScript file that was created to contain device-specific commands
 for achieving a certain print job output (e.g. duplexed, stapled and
 punched) on a specific target machine, may not print as expected, or
 may not be printable at all on other models; it also may not be fit
 for further processing by software (e.g. by a PDF distilling program).
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909654"></a>CUPS can use all Windows-formatted Vendor PPDs</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907241"></a>CUPS can use all Windows-formatted Vendor PPDs</h3></div></div><div></div></div><p>
 CUPS can handle all spec-compliant PPDs as supplied by the
 manufacturers for their PostScript models. Even if a
 UNIX/Linux-illiterate vendor might not have mentioned our favorite
@@ -8389,8 +8389,8 @@ immediately. CUPS in all versions after 1.1.19 has a much more strict
 internal PPD parsing and checking code enabled; in case of printing
 trouble this online resource should be one of your first pitstops.
 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-<a class="indexterm" name="id2909702"></a>
-<a class="indexterm" name="id2909710"></a>
+<a class="indexterm" name="id2907289"></a>
+<a class="indexterm" name="id2907297"></a>
 For real PostScript printers <span class="emphasis"><em>don't</em></span> use the
 <span class="emphasis"><em>Foomatic</em></span> or <span class="emphasis"><em>cupsomatic</em></span>
 PPDs from Linuxprinting.org. With these devices the original
@@ -8403,7 +8403,7 @@ your LAN has the PostScript driver installed, just use
 access the Windows directory where all printer driver files are
 stored. First look in the <tt class="filename">W32X86/2</tt> subdir for
 the PPD you are seeking.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909760"></a>CUPS also uses PPDs for non-PostScript Printers</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907348"></a>CUPS also uses PPDs for non-PostScript Printers</h3></div></div><div></div></div><p>
 CUPS also uses specially crafted PPDs to handle non-PostScript
 printers. These PPDs are usually not available from the vendors (and
 no, you can't just take the PPD of a Postscript printer with the same
@@ -8411,7 +8411,7 @@ model name and hope it works for the non-PostScript version too). To
 understand how these PPDs work for non-PS printers we first need to
 dive deeply into the CUPS filtering and file format conversion
 architecture. Stay tuned.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2909782"></a>The CUPS Filtering Architecture</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907370"></a>The CUPS Filtering Architecture</h2></div></div><div></div></div><p>
 The core of the CUPS filtering system is based on
 <span class="emphasis"><em>Ghostscript</em></span>. In addition to Ghostscript, CUPS
 uses some other filters of its own. You (or your OS vendor) may have
@@ -8437,27 +8437,27 @@ Make sure your Ghostscript version has the "cups" device compiled in
 may encounter the dreaded <tt class="computeroutput">Unable to convert file
 0</tt> in your CUPS error_log file. To have "cups" as a
 device in your Ghostscript, you either need to <span class="emphasis"><em>patch GNU
-Ghostscript</em></span> and re-compile or use <a class="indexterm" name="id2909875"></a><a href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The
+Ghostscript</em></span> and re-compile or use <a class="indexterm" name="id2907462"></a><a href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The
 superior alternative is ESP Ghostscript: it supports not just CUPS,
 but 300 other devices too (while GNU Ghostscript supports only about
 180). Because of this broad output device support, ESP Ghostscript is
 the first choice for non-CUPS spoolers too. It is now recommended by
 Linuxprinting.org for all spoolers.
 </p><p>
-<a class="indexterm" name="id2909903"></a>
-<a class="indexterm" name="id2909911"></a>
+<a class="indexterm" name="id2907490"></a>
+<a class="indexterm" name="id2907498"></a>
 CUPS printers may be setup to use <span class="emphasis"><em>external</em></span>
 rendering paths. One of the most common ones is provided by the
 <span class="emphasis"><em>Foomatic/cupsomatic</em></span> concept, from <a href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a>.  This
 uses the classical Ghostscript approach, doing everything in one
 step. It doesn't use the "cups" device, but one of the many
 others. However, even for Foomatic/cupsomatic usage, best results and
-<a class="indexterm" name="id2909940"></a>
+<a class="indexterm" name="id2907528"></a>
 broadest printer model support is provided by ESP Ghostscript (more
 about cupsomatic/Foomatic, particularly the new version called now
 <span class="emphasis"><em>foomatic-rip</em></span>, follows below).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909959"></a>MIME types and CUPS Filters</h3></div></div><div></div></div><p>
-	<a class="indexterm" name="id2909970"></a>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907545"></a>MIME types and CUPS Filters</h3></div></div><div></div></div><p>
+	<a class="indexterm" name="id2907557"></a>
 CUPS reads the file <tt class="filename">/etc/cups/mime.types</tt>
 (and all other files carrying a <tt class="filename">*.types</tt> suffix
 in the same directory) upon startup. These files contain the MIME
@@ -8467,7 +8467,7 @@ for <tt class="filename">mime.types</tt> and in the comments section of the
 <tt class="filename">mime.types</tt> file itself. A simple rule reads
 like this:
 </p><p>
-<a class="indexterm" name="id2910015"></a>
+<a class="indexterm" name="id2907602"></a>
 </p><pre class="screen">
  application/pdf         pdf string(0,%PDF)
 </pre><p>
@@ -8508,7 +8508,7 @@ CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a
 lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster,
 PNM, PBM, SGI-RGB and some more) and their associated MIME types
 with its filters.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910165"></a>MIME type Conversion Rules</h3></div></div><div></div></div><a class="indexterm" name="id2910173"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907752"></a>MIME type Conversion Rules</h3></div></div><div></div></div><a class="indexterm" name="id2907760"></a><p>
 CUPS reads the file <tt class="filename">/etc/cups/mime.convs</tt>
 (and all other files named with a <tt class="filename">*.convs</tt>
 suffix in the same directory) upon startup. These files contain
@@ -8524,16 +8524,16 @@ This means that the <span class="emphasis"><em>pdftops</em></span> filter will t
 <span class="emphasis"><em>application/postscript</em></span> as output, the virtual
 cost of this operation is 33 CUPS-$. The next filter is more
 expensive, costing 66 CUPS-$:
-</p><a class="indexterm" name="id2910234"></a><pre class="screen">
+</p><a class="indexterm" name="id2907822"></a><pre class="screen">
  application/vnd.hp-HPGL application/postscript   66   hpgltops
 </pre><p>
 This is the <span class="emphasis"><em>hpgltops</em></span>, which processes HP-GL
 plotter files to PostScript.
-</p><a class="indexterm" name="id2910262"></a><pre class="screen">
+</p><a class="indexterm" name="id2907849"></a><pre class="screen">
  application/octet-stream
 </pre><p>
 Here are two more examples: 
-</p><a class="indexterm" name="id2910284"></a><pre class="screen">
+</p><a class="indexterm" name="id2907872"></a><pre class="screen">
  application/x-shell     application/postscript   33    texttops
  text/plain              application/postscript   33    texttops
 </pre><p>
@@ -8541,7 +8541,7 @@ The last two examples name the <span class="emphasis"><em>texttops</em></span> f
 to work on "text/plain" as well as on "application/x-shell". (Hint:
 this differentiation is needed for the syntax highlighting feature of
 "texttops").
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910315"></a>Filter Requirements</h3></div></div><div></div></div><a class="indexterm" name="id2910322"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907903"></a>Filter Requirements</h3></div></div><div></div></div><a class="indexterm" name="id2907910"></a><p>
 There are many more combinations named in mime.convs.  However, you
 are not limited to use the ones pre-defined there. You can plug in any
 filter you like into the CUPS framework. It must meet, or must be made
@@ -8562,7 +8562,7 @@ attribute</p></dd><dt><span class="term">title</span></dt><dd><p>The string from
 attribute</p></dd><dt><span class="term">options</span></dt><dd><p>The job options</p></dd><dt><span class="term">filename</span></dt><dd><p>(Optionally) The print request file (if missing,
 filters expected data fed through <tt class="filename">stdin</tt>). In most
 cases it is very easy to write a simple wrapper script around existing
-filters to make them work with CUPS.</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910493"></a>Prefilters</h3></div></div><div></div></div><a class="indexterm" name="id2910500"></a><p>
+filters to make them work with CUPS.</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908080"></a>Prefilters</h3></div></div><div></div></div><a class="indexterm" name="id2908088"></a><p>
 As was said, PostScript is the central file format to any UNIX based
 printing system. From PostScript, CUPS generates raster data to feed
 non-PostScript printers.
@@ -8581,7 +8581,7 @@ MIME type <span class="emphasis"><em>application/vnd.cups-postscript</em></span>
 print options already embedded into the file.
 </p><p>
 	</p><div class="figure"><a name="small4"></a><p class="title"><b>Figure�19.4.�Prefiltering in CUPS to form Postscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/4small.png" width="270" alt="Prefiltering in CUPS to form Postscript"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910595"></a>pstops</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908183"></a>pstops</h3></div></div><div></div></div><p>
 <span class="emphasis"><em>pstops</em></span>is the filter to convert
 <span class="emphasis"><em>application/postscript</em></span> to
 <span class="emphasis"><em>application/vnd.cups-postscript</em></span>. It was said
@@ -8601,7 +8601,7 @@ putting 2 or more logical pages on one sheet of paper (the
 so-called "number-up" function)
 </p></li><li><p>counting the pages of the job to insert the accounting
 information into the <tt class="filename">/var/log/cups/page_log</tt>
-</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910704"></a>pstoraster</h3></div></div><div></div></div><p>
+</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908292"></a>pstoraster</h3></div></div><div></div></div><p>
 <span class="emphasis"><em>pstoraster</em></span> is at the core of the CUPS filtering
 system. It is responsible for the first stage of the rasterization
 process. Its input is of MIME type application/vnd.cups-postscript;
@@ -8637,7 +8637,7 @@ integrated back into Ghostscript (now based on GNU Ghostscript version
 parameter. If your Ghostscript doesn't show a success on asking for
 <b class="command">gs -h |grep cups</b>, you might not be able to
 print. Update your Ghostscript then!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910875"></a>imagetops and imagetoraster</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908476"></a>imagetops and imagetoraster</h3></div></div><div></div></div><p>
 Above in the section about prefilters, we mentioned the prefilter
 that generates PostScript from image formats. The imagetoraster
 filter is used to convert directly from image to raster, without the
@@ -8646,7 +8646,7 @@ mentioned prefilters. Here is a summarizing flowchart of image file
 filtering:
 </p><p>
 	</p><div class="figure"><a name="small8"></a><p class="title"><b>Figure�19.8.�Image format to CUPS-raster format conversion</b></p><div class="mediaobject"><img src="projdoc/imagefiles/8small.png" width="270" alt="Image format to CUPS-raster format conversion"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910938"></a>rasterto [printers specific]</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908539"></a>rasterto [printers specific]</h3></div></div><div></div></div><p>
 CUPS ships with quite some different raster drivers processing CUPS
 raster. On my system I find in /usr/lib/cups/filter/ these:
 <i class="parameter"><tt>rastertoalps</tt></i>, <i class="parameter"><tt>rastertobj</tt></i>, <i class="parameter"><tt>rastertoepson</tt></i>, <i class="parameter"><tt>rastertoescp</tt></i>,
@@ -8660,7 +8660,7 @@ development projects (such as Gimp-Print) wanting to cooperate as
 closely as possible with CUPS.
 </p><p>
 	</p><div class="figure"><a name="small9"></a><p class="title"><b>Figure�19.9.�Raster to Printer Specific formats</b></p><div class="mediaobject"><img src="projdoc/imagefiles/9small.png" width="270" alt="Raster to Printer Specific formats"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911090"></a>CUPS Backends</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2908691"></a>CUPS Backends</h3></div></div><div></div></div><p>
 The last part of any CUPS filtering chain is a "backend".  Backends
 are special programs that send the print-ready file to the final
 device. There is a separate backend program for any transfer
@@ -8745,7 +8745,7 @@ utility. Used with the <tt class="option">-v</tt> parameter, it lists
 all available backends:
 </p><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>lpinfo -v</tt></b>
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911412"></a>cupsomatic/Foomatic -- how do they fit into the Picture?</h3></div></div><div></div></div><a class="indexterm" name="id2911420"></a><a class="indexterm" name="id2911428"></a><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909039"></a>cupsomatic/Foomatic -- how do they fit into the Picture?</h3></div></div><div></div></div><a class="indexterm" name="id2909047"></a><a class="indexterm" name="id2909055"></a><p>
 "cupsomatic" filters may be the most widely used on CUPS
 installations. You must be clear about the fact that these were not
 developed by the CUPS people. They are a "Third Party" add-on to
@@ -8768,7 +8768,7 @@ the driver description. cupsomatic is a Perl script that runs
 Ghostscript, with all the complicated commandline options
 auto-constructed from the selected PPD and commandline options give to
 the printjob.
-</p><a class="indexterm" name="id2911495"></a><p>
+</p><a class="indexterm" name="id2909122"></a><p>
 However, cupsomatic is now deprecated. Its PPDs (especially the first
 generation of them, still in heavy use out there) are not meeting the
 Adobe specifications. You might also suffer difficulties when you try
@@ -8793,11 +8793,11 @@ print-options from page to page, in the middle of a job. And the
 best thing is: the new foomatic-rip now works seamlessly with all
 legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing
 for them access to use PPDs for their printing!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911562"></a>The Complete Picture</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909176"></a>The Complete Picture</h3></div></div><div></div></div><p>
 If you want to see an overview over all the filters and how they
 relate to each other, the complete picture of the puzzle is at the end
 of this document.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911576"></a><tt class="filename">mime.convs</tt></h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909191"></a><tt class="filename">mime.convs</tt></h3></div></div><div></div></div><p>
 CUPS auto-constructs all possible filtering chain paths for any given
 MIME type, and every printer installed. But how does it decide in
 favor or against a specific alternative?  (There may often be cases,
@@ -8814,7 +8814,7 @@ cost. This is a very efficient way to limit the load of any CUPS
 server by setting an appropriate "FilterLimit" value. A FilterLimit of
 200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows
 approximately 5 jobs maximum at a time.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911630"></a>"Raw" printing</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909245"></a>"Raw" printing</h3></div></div><div></div></div><p>
 You can tell CUPS to print (nearly) any file "raw". "Raw" means it
 will not be filtered. CUPS will send the file to the printer "as is"
 without bothering if the printer is able to digest it. Users need to
@@ -8835,7 +8835,7 @@ CUPS will automatically treat each job sent to a queue as a "raw" one,
 if it can't find a PPD associated with the queue.  However, CUPS will
 only send known MIME types (as defined in its own mime.types file) and
 refuse others.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911697"></a>"application/octet-stream" printing</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909312"></a>"application/octet-stream" printing</h3></div></div><div></div></div><p>
 Any MIME type with no rule in the
 <tt class="filename">/etc/cups/mime.types</tt> file is regarded as unknown
 or <span class="emphasis"><em>application/octet-stream</em></span> and will not be
@@ -8853,7 +8853,7 @@ Both contain entries (at the end of the respective files) which must
 be uncommented to allow RAW mode operation for
 application/octet-stream. In <tt class="filename">/etc/cups/mime.types</tt>
 make sure this line is present:
-</p><a class="indexterm" name="id2911780"></a><pre class="screen">
+</p><a class="indexterm" name="id2909395"></a><pre class="screen">
  application/octet-stream
 </pre><p>
 This line (with no specific auto-typing rule set) makes all files
@@ -8862,7 +8862,7 @@ not otherwise auto-typed a member of application/octet-stream. In
 line: 
 </p><pre class="screen">
  application/octet-stream   application/vnd.cups-raw   0   -
-</pre><a class="indexterm" name="id2911820"></a><p>
+</pre><a class="indexterm" name="id2909435"></a><p>
 This line tells CUPS to use the <span class="emphasis"><em>Null Filter</em></span>
 (denoted as "-", doing... nothing at all) on
 <span class="emphasis"><em>application/octet-stream</em></span>, and tag the result as
@@ -8887,7 +8887,7 @@ be one that is known to CUPS and an allowed one. The file
 recognizes MIME types. The file
 <tt class="filename">/etc/cups/mime.convs</tt> decides which file
 conversion filter(s) may be applied to which MIME types.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911929"></a>PostScript Printer Descriptions (PPDs) for non-PS Printers</h3></div></div><div></div></div><a class="indexterm" name="id2911937"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909544"></a>PostScript Printer Descriptions (PPDs) for non-PS Printers</h3></div></div><div></div></div><a class="indexterm" name="id2909552"></a><p>
 Originally PPDs were meant to be used for PostScript printers
 only. Here, they help to send device-specific commands and settings
 to the RIP which processes the jobfile. CUPS has extended this
@@ -8900,7 +8900,7 @@ printers the Ghostscript RIP runs on the host computer.
 </p><p>
 PPDs for a non-PS printer have a few lines that are unique to
 CUPS. The most important one looks similar to this:
-</p><a class="indexterm" name="id2911967"></a><pre class="screen">
+</p><a class="indexterm" name="id2909582"></a><pre class="screen">
  *cupsFilter: application/vnd.cups-raster  66   rastertoprinter
 </pre><p>
 It is the last piece in the CUPS filtering puzzle. This line tells the
@@ -8917,12 +8917,12 @@ CUPS by default ships only a few generic PPDs, but they are good for
 several hundred printer models. You may not be able to control
 different paper trays, or you may get larger margins than your
 specific model supports):
-</p><div class="table"><a name="id2912008"></a><p class="title"><b>Table�19.1.�PPD's shipped with CUPS</b></p><table summary="PPD's shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.  </td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912192"></a>Difference between <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> and
-<span class="emphasis"><em>native CUPS</em></span> printing</h3></div></div><div></div></div><a class="indexterm" name="id2912210"></a><a class="indexterm" name="id2912218"></a><p>
+</p><div class="table"><a name="id2909623"></a><p class="title"><b>Table�19.1.�PPD's shipped with CUPS</b></p><table summary="PPD's shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.  </td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2909807"></a>Difference between <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> and
+<span class="emphasis"><em>native CUPS</em></span> printing</h3></div></div><div></div></div><a class="indexterm" name="id2909825"></a><a class="indexterm" name="id2909833"></a><p>
 Native CUPS rasterization works in two steps.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 First is the "pstoraster" step. It uses the special "cups"
-<a class="indexterm" name="id2912241"></a>
+<a class="indexterm" name="id2909856"></a>
 device from ESP Ghostscript 7.05.x as its tool
 </p></li><li><p>
 Second comes the "rasterdriver" step. It uses various
@@ -8946,8 +8946,8 @@ other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly
 advised, especially if you are upgrading to a recent version of CUPS
 too.
 </p><p>
-	<a class="indexterm" name="id2912350"></a>
-	<a class="indexterm" name="id2912359"></a>
+	<a class="indexterm" name="id2909965"></a>
+	<a class="indexterm" name="id2909974"></a>
 Both the cupsomatic (old) and the foomatic-rip (new) methods from
 Linuxprinting.org use the traditional Ghostscript print file
 processing, doing everything in a single step. It therefore relies on
@@ -8969,7 +8969,7 @@ installation: Therefore the printfile bypasses the "pstoraster" filter
 cupsomatic hands the rendered file directly to the CUPS backend. The
 flowchart above illustrates the difference between native CUPS
 rendering and the Foomatic/cupsomatic method.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912410"></a>Examples for filtering Chains</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910018"></a>Examples for filtering Chains</h3></div></div><div></div></div><p>
 Here are a few examples of commonly occurring filtering chains to
 illustrate the workings of CUPS.
 </p><p>
@@ -9015,11 +9015,11 @@ printer-specific raster data and embedding any user-selected
 print-options into the print data stream;</p></li><li><p>the file goes to the <span class="emphasis"><em>usb</em></span> backend,
 which transfers the job to the printers.</p></li></ul></div><p>
 	The resulting filter chain therefore is as drawn in <a href="#pdftoepsonusb" title="Figure�19.12.�PDF to USB chain">the image below</a>.
-</p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure�19.12.�PDF to USB chain</b></p><div class="mediaobject"><img src="projdoc/imagefiles/pdftoepsonusb.png" width="270" alt="PDF to USB chain"></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912731"></a>Sources of CUPS drivers / PPDs</h3></div></div><div></div></div><p>
+</p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure�19.12.�PDF to USB chain</b></p><div class="mediaobject"><img src="projdoc/imagefiles/pdftoepsonusb.png" width="270" alt="PDF to USB chain"></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910331"></a>Sources of CUPS drivers / PPDs</h3></div></div><div></div></div><p>
 On the internet you can find now many thousand CUPS-PPD files
 (with their companion filters), in many national languages,
 supporting more than 1000 non-PostScript models.
-</p><div class="itemizedlist"><a class="indexterm" name="id2912747"></a><a class="indexterm" name="id2912757"></a><ul type="disc"><li><p><a href="http://wwwl.easysw.com/printpro/" target="_top">ESP
+</p><div class="itemizedlist"><a class="indexterm" name="id2910347"></a><a class="indexterm" name="id2910357"></a><ul type="disc"><li><p><a href="http://wwwl.easysw.com/printpro/" target="_top">ESP
 PrintPro</a> (commercial,
 non-Free) is packaged with more than 3000 PPDs, ready for
 successful use "out of the box" on Linux, Mac OS X, IBM-AIX,
@@ -9050,7 +9050,7 @@ HPIJS).</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-r
 The cupsomatic/Foomatic trick from Linuxprinting.org works
 differently from the other drivers. This is explained elsewhere in this
 document.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912872"></a>Printing with Interface Scripts</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910470"></a>Printing with Interface Scripts</h3></div></div><div></div></div><p>
 CUPS also supports the usage of "interface scripts" as known from
 System V AT&amp;T printing systems. These are often used for PCL
 printers, from applications that generate PCL print jobs.  Interface
@@ -9071,21 +9071,21 @@ with CUPS they provide the most easy way to plug in your own
 custom-written filtering script or program into one specific print
 queue (some information about the traditional usage of interface scripts is
 to be found at <a href="http://playground.sun.com/printing/documentation/interface.html" target="_top">http://playground.sun.com/printing/documentation/interface.html</a>).
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912949"></a>Network printing (purely Windows)</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910560"></a>Network printing (purely Windows)</h2></div></div><div></div></div><p>
 Network printing covers a lot of ground. To understand what exactly
 goes on with Samba when it is printing on behalf of its Windows
 clients, let's first look at a "purely Windows" setup: Windows clients
 with a Windows NT print server.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912965"></a>From Windows Clients to an NT Print Server</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910577"></a>From Windows Clients to an NT Print Server</h3></div></div><div></div></div><p>
 Windows clients printing to an NT-based print server have two
 options. They may
-</p><a class="indexterm" name="id2912979"></a><a class="indexterm" name="id2912987"></a><div class="itemizedlist"><ul type="disc"><li><p>execute the driver locally and render the GDI output
+</p><a class="indexterm" name="id2910590"></a><a class="indexterm" name="id2910598"></a><div class="itemizedlist"><ul type="disc"><li><p>execute the driver locally and render the GDI output
 (EMF) into the printer specific format on their own,
 or</p></li><li><p>send the GDI output (EMF) to the server, where the
 driver is executed to render the printer specific
 output.</p></li></ul></div><p>
 Both print paths are shown in the flowcharts below.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913020"></a>Driver Execution on the Client</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910632"></a>Driver Execution on the Client</h3></div></div><div></div></div><p>
 In the first case the print server must spool the file as "raw",
 meaning it shouldn't touch the jobfile and try to convert it in any
 way. This is what traditional UNIX-based print server can do too; and
@@ -9097,7 +9097,7 @@ to have the Windows client drivers available and installed on the
 clients.
 </p><p>
 	</p><div class="figure"><a name="small11"></a><p class="title"><b>Figure�19.13.�Print Driver execution on the Client</b></p><div class="mediaobject"><img src="projdoc/imagefiles/11small.png" width="270" alt="Print Driver execution on the Client"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913090"></a>Driver Execution on the Server</h3></div></div><div></div></div><a class="indexterm" name="id2913095"></a><a class="indexterm" name="id2913104"></a><a class="indexterm" name="id2913112"></a><a class="indexterm" name="id2913120"></a><a class="indexterm" name="id2913129"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910701"></a>Driver Execution on the Server</h3></div></div><div></div></div><a class="indexterm" name="id2910707"></a><a class="indexterm" name="id2910715"></a><a class="indexterm" name="id2910724"></a><a class="indexterm" name="id2910732"></a><a class="indexterm" name="id2910740"></a><p>
 The other path executes the printer driver on the server. The clients
 transfers print files in EMF format to the server. The server uses the
 PostScript, PCL, ESC/P or other driver to convert the EMF file into
@@ -9109,14 +9109,14 @@ understand.
 	</p><div class="figure"><a name="small12"></a><p class="title"><b>Figure�19.14.�Print Driver execution on the Server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/12small.png" width="270" alt="Print Driver execution on the Server"></div></div><p>
 </p><p>
 However, there is something similar possible with CUPS. Read on...
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913201"></a>Network Printing (Windows clients -- UNIX/Samba Print
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910813"></a>Network Printing (Windows clients -- UNIX/Samba Print
 Servers)</h2></div></div><div></div></div><p>
 Since UNIX print servers <span class="emphasis"><em>cannot</em></span> execute the Win32
 program code on their platform, the picture is somewhat
 different. However, this doesn't limit your options all that
 much. In the contrary, you may have a way here to implement printing
 features which are not possible otherwise.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913221"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910833"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div><div></div></div><p>
 Here is a simple recipe showing how you can take advantage of CUPS
 powerful features for the benefit of your Windows network printing
 clients:
@@ -9130,9 +9130,9 @@ printer is a non-PostScript model. It also requires that you have a
 Firstly, to enable CUPS based printing through Samba the
 following options should be set in your <tt class="filename">smb.conf</tt> file [global]
 section:
-</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2913280"></a><i class="parameter"><tt>printing</tt></i> = cups</p></li><li><p><a class="indexterm" name="id2913298"></a><i class="parameter"><tt>printcap</tt></i> = cups</p></li></ul></div><p>
+</p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2910891"></a><i class="parameter"><tt>printing</tt></i> = cups</p></li><li><p><a class="indexterm" name="id2910909"></a><i class="parameter"><tt>printcap</tt></i> = cups</p></li></ul></div><p>
 When these parameters are specified, all manually set print directives
-(like <a class="indexterm" name="id2913318"></a><i class="parameter"><tt>print command</tt></i>, or <a class="indexterm" name="id2913332"></a><i class="parameter"><tt>lppause command</tt></i>) in <tt class="filename">smb.conf</tt> (as well as
+(like <a class="indexterm" name="id2910929"></a><i class="parameter"><tt>print command</tt></i>, or <a class="indexterm" name="id2910943"></a><i class="parameter"><tt>lppause command</tt></i>) in <tt class="filename">smb.conf</tt> (as well as
 in samba itself) will be ignored. Instead, Samba will directly
 interface with CUPS through it's application program interface (API) -
 as long as Samba has been compiled with CUPS library (libcups)
@@ -9141,12 +9141,12 @@ other print commands are set up, then printing will use the
 <span class="emphasis"><em>System V</em></span> AT&amp;T command set, with the -oraw
 option automatically passing through (if you want your own defined
 print commands to work with a Samba that has CUPS support compiled in,
-simply use <a class="indexterm" name="id2913370"></a><i class="parameter"><tt>printing</tt></i> = sysv).
+simply use <a class="indexterm" name="id2910981"></a><i class="parameter"><tt>printing</tt></i> = sysv).
 </p><p>
 </p><div class="figure"><a name="small13"></a><p class="title"><b>Figure�19.15.�Printing via CUPS/samba server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/13small.png" width="270" alt="Printing via CUPS/samba server"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913432"></a>Samba receiving Jobfiles and passing them to CUPS</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911043"></a>Samba receiving Jobfiles and passing them to CUPS</h3></div></div><div></div></div><p>
 Samba <span class="emphasis"><em>must</em></span> use its own spool directory (it is set
-by a line similar to <a class="indexterm" name="id2913446"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba,
+by a line similar to <a class="indexterm" name="id2911058"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba,
 in the <i class="parameter"><tt>[printers]</tt></i> or
 <i class="parameter"><tt>[printername]</tt></i> section of
 <tt class="filename">smb.conf</tt>). Samba receives the job in its own
@@ -9162,8 +9162,8 @@ A Windows user authenticates only to Samba (by whatever means is
 configured). If Samba runs on the same host as CUPS, you only need to
 allow "localhost" to print. If they run on different machines, you
 need to make sure the Samba host gets access to printing on CUPS.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913513"></a>Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</h2></div></div><div></div></div><a class="indexterm" name="id2913523"></a><a class="indexterm" name="id2913531"></a><a class="indexterm" name="id2913540"></a><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911125"></a>Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</h2></div></div><div></div></div><a class="indexterm" name="id2911135"></a><a class="indexterm" name="id2911143"></a><a class="indexterm" name="id2911151"></a><p>
 PPDs can control all print device options. They are usually provided
 by the manufacturer; if you own a PostScript printer, that is. PPD
 files (PostScript Printer Descriptions) are always a component of
@@ -9182,7 +9182,7 @@ or see if you have lphelp on your system). There are also some
 different GUI frontends on Linux/UNIX, which can present PPD options
 to users. PPD options are normally meant to be evaluated by the
 PostScript RIP on the real PostScript printer.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913594"></a>PPDs for non-PS Printers on UNIX</h3></div></div><div></div></div><a class="indexterm" name="id2913602"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911206"></a>PPDs for non-PS Printers on UNIX</h3></div></div><div></div></div><a class="indexterm" name="id2911214"></a><p>
 CUPS doesn't limit itself to "real" PostScript printers in its usage
 of PPDs. The CUPS developers have extended the scope of the PPD
 concept, to also describe available device and driver options for
@@ -9199,7 +9199,7 @@ the supplied PostScript. Thus CUPS lets all its printers appear as
 PostScript devices to its clients, because it can act as a PostScript
 RIP for those printers, processing the received PostScript code into a
 proper raster print format.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913643"></a>PPDs for non-PS Printers on Windows</h3></div></div><div></div></div><a class="indexterm" name="id2913651"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911255"></a>PPDs for non-PS Printers on Windows</h3></div></div><div></div></div><a class="indexterm" name="id2911263"></a><p>
 CUPS-PPDs can also be used on Windows-Clients, on top of a
 "core" PostScript driver (now recommended is the "CUPS PostScript
 Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with
@@ -9215,13 +9215,13 @@ which always remain unfiltered per definition;</p></li><li><p>enable clients to
 driver, even for many different target printers.</p></li></ul></div><p>
 Using CUPS PPDs on Windows clients enables these to control
 all print job settings just as a UNIX client can do too.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913717"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911328"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div><div></div></div><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.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913734"></a>Printer Drivers running in "Kernel Mode" cause many
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911345"></a>Printer Drivers running in "Kernel Mode" cause many
 Problems</h3></div></div><div></div></div><p>
 The reason is that in Win NT printer drivers run in "Kernel
 Mode", this introduces a high risk for the stability of the system
@@ -9238,7 +9238,7 @@ might be because there have so far only been 2 different PostScript
 drivers: the ones from Adobe and the one from Microsoft. Both are
 very well tested and are as stable as you ever can imagine on
 Windows. The CUPS driver is derived from the Microsoft one.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913768"></a>Workarounds impose Heavy Limitations</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911379"></a>Workarounds impose Heavy Limitations</h3></div></div><div></div></div><p>
 In many cases, in an attempt to work around this problem, site
 administrators have resorted to restrict the allowed drivers installed
 on their WTS to one generic PCL- and one PostScript driver. This
@@ -9246,7 +9246,7 @@ however restricts the clients in the amount of printer options
 available for them; often they can't get out more than simplex
 prints from one standard paper tray, while their devices could do much
 better, if driven by a different driver! )
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913789"></a>CUPS: a "Magical Stone"?</h3></div></div><div></div></div><a class="indexterm" name="id2913798"></a><a class="indexterm" name="id2913806"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911400"></a>CUPS: a "Magical Stone"?</h3></div></div><div></div></div><a class="indexterm" name="id2911410"></a><a class="indexterm" name="id2911418"></a><p>
 Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very
 elegant way to overcome all these shortcomings. There are, depending
 on the version of Windows OS you use, up to 3 different PostScript
@@ -9258,8 +9258,8 @@ is a certain price for this too: a CUPS server acting as a PostScript
 RIP for its clients requires more CPU and RAM than when just acting as
 a "raw spooling" device.  Plus, this setup is not yet widely tested,
 although the first feedbacks look very promising.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913833"></a>PostScript Drivers with no major problems -- even in Kernel
-Mode</h3></div></div><div></div></div><a class="indexterm" name="id2913842"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911445"></a>PostScript Drivers with no major problems -- even in Kernel
+Mode</h3></div></div><div></div></div><a class="indexterm" name="id2911454"></a><p>
 More recent printer drivers on W2K and XP don't run in Kernel mode
 (unlike Win NT) any more. However, both operating systems can still
 use the NT drivers, running in Kernel mode (you can roughly tell which
@@ -9275,14 +9275,14 @@ development efforts. This is what the CUPS people have done. The
 license doesn't allow them to publish the whole of the source code.
 However, they have released the "diff" under the GPL, and if you are
 owner of an "MS DDK for Win NT", you can check the driver yourself.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913895"></a>Setting up CUPS for driver Download</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911506"></a>Setting up CUPS for driver Download</h2></div></div><div></div></div><p>
 As we have said before: all previously known methods to prepare client
 printer drivers on the Samba server for download and "Point'n'Print"
 convenience of Windows workstations are working with CUPS too. These
 methods were described in the previous chapter. In reality, this is a
 pure Samba business, and only relates to the Samba/Win client
 relationship.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913913"></a><span class="emphasis"><em>cupsaddsmb</em></span>: the unknown Utility</h3></div></div><div></div></div><a class="indexterm" name="id2913924"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911524"></a><span class="emphasis"><em>cupsaddsmb</em></span>: the unknown Utility</h3></div></div><div></div></div><a class="indexterm" name="id2911536"></a><p>
 The cupsaddsmb utility (shipped with all current CUPS versions) is an
 alternative method to transfer printer drivers into the Samba
 <i class="parameter"><tt>[print$]</tt></i> share. Remember, this share is where
@@ -9307,10 +9307,10 @@ job-billing)</p></li></ul></div><p>
 However, currently only Windows NT, 2000, and XP are supported by the
 CUPS drivers. You will need to get the respective part of Adobe driver
 too if you need to support Windows 95, 98, and ME clients.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914014"></a>Prepare your <tt class="filename">smb.conf</tt> for cupsaddsmb</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911625"></a>Prepare your <tt class="filename">smb.conf</tt> for cupsaddsmb</h3></div></div><div></div></div><p>
 Prior to running cupsaddsmb, you need the following settings in
 <tt class="filename">smb.conf</tt>:
-</p><div class="example"><a name="id2914041"></a><p class="title"><b>Example�19.3.�smb.conf for cupsaddsmb usage</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[print$]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer Drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /etc/samba/drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = root</tt></i></td></tr></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914233"></a>CUPS Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><a class="indexterm" name="id2914242"></a><p>
+</p><div class="example"><a name="id2911654"></a><p class="title"><b>Example�19.3.�smb.conf for cupsaddsmb usage</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[print$]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer Drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /etc/samba/drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = root</tt></i></td></tr></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911845"></a>CUPS Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><a class="indexterm" name="id2911854"></a><p>
 CUPS users may get the exactly same packages from <a href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>.
 It is a separate package from the CUPS base software files, tagged as
 <span class="emphasis"><em>CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba
@@ -9325,8 +9325,8 @@ cups-samba.readme
 cups-samba.remove
 cups-samba.ss
 </pre><p>
-<a class="indexterm" name="id2914304"></a>
-<a class="indexterm" name="id2914315"></a>
+<a class="indexterm" name="id2911916"></a>
+<a class="indexterm" name="id2911927"></a>
 These have been packaged with the ESP meta packager software
 "EPM". The <tt class="filename">*.install</tt> and
 <tt class="filename">*.remove</tt> files are simple shell scripts, which
@@ -9363,7 +9363,7 @@ copy/move the file (after running the
 right place.
 </p></div><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/</tt></b>
-</pre><a class="indexterm" name="id2914490"></a><p>
+</pre><a class="indexterm" name="id2912102"></a><p>
 This new CUPS PostScript driver is currently binary-only, but free of
 charge. No complete source code is provided (yet). The reason is this:
 it has been developed with the help of the <span class="emphasis"><em>Microsoft Driver
@@ -9372,7 +9372,7 @@ Studio 6. Driver developers are not allowed to distribute the whole of
 the source code as Free Software. However, CUPS developers released
 the "diff" in source code under the GPL, so anybody with a license of
 Visual Studio and a DDK will be able to compile for him/herself.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914516"></a>Recognize the different Driver Files</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912128"></a>Recognize the different Driver Files</h3></div></div><div></div></div><p>
 The CUPS drivers don't support the "older" Windows 95/98/ME, but only
 the Windows NT/2000/XP client:
 </p><p>Windows NT, 2000, and XP are supported by:</p><p>
@@ -9392,7 +9392,7 @@ support of WinNT/2k/XP are present in , the Adobe ones will be ignored
 and the CUPS ones will be used. If you prefer -- for whatever reason
 -- to use Adobe-only drivers, move away the 3 CUPS driver files. The
 Win95/98/ME clients use the Adobe drivers in any case.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914656"></a>Acquiring the Adobe Driver Files</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912268"></a>Acquiring the Adobe Driver Files</h3></div></div><div></div></div><p>
 Acquiring the Adobe driver files seems to be unexpectedly difficult
 for many users. They are not available on the Adobe website as single
 files and the self-extracting and/or self-installing Windows-exe is
@@ -9405,8 +9405,8 @@ Generic PostScript printer.  After this, the client's
 where you can get them with smbclient from the CUPS host. A more
 detailed description about this is in the next (the CUPS printing)
 chapter.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914689"></a>ESP Print Pro Package of "PostScript Driver for
-WinNT/2k/XP"</h3></div></div><div></div></div><a class="indexterm" name="id2914698"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912301"></a>ESP Print Pro Package of "PostScript Driver for
+WinNT/2k/XP"</h3></div></div><div></div></div><a class="indexterm" name="id2912311"></a><p>
 Users of the ESP Print Pro software are able to install their "Samba
 Drivers" package for this purpose with no problem. Retrieve the driver
 files from the normal download area of the ESP Print Pro software
@@ -9421,7 +9421,7 @@ driver files; i.e.  mainly setup the <i class="parameter"><tt>[print$]</tt></i>
 share, etc. The ESP Print Pro package includes the CUPS driver files
 as well as a (licensed) set of Adobe drivers for the Windows 95/98/ME
 client family.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914749"></a>Caveats to be considered</h3></div></div><div></div></div><a class="indexterm" name="id2914759"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912362"></a>Caveats to be considered</h3></div></div><div></div></div><a class="indexterm" name="id2912371"></a><p>
 Once you have run the install script (and possibly manually
 moved the <tt class="filename">cups.hlp</tt> file to
 <tt class="filename">/usr/share/cups/drivers/</tt>), the driver is
@@ -9432,7 +9432,7 @@ tree with <span class="emphasis"><em>WIN40</em></span> and
 "cupsaddsmb" (see also <b class="command">man cupsaddsmb</b> for
 CUPS since release 1.1.16).
 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
-<a class="indexterm" name="id2914823"></a>
+<a class="indexterm" name="id2912436"></a>
 You may need to put root into the smbpasswd file by running
 <b class="command">smbpasswd</b>; this is especially important if you
 should run this whole procedure for the first time, and are not
@@ -9454,7 +9454,7 @@ installations in the <tt class="filename">/usr/share/cups/drivers/</tt>
 directory. The new <span class="emphasis"><em>cupsaddsmb</em></span> (from 1.1.16) will
 automatically prefer "its own" drivers if it finds both.
 </p></li><li><p>
-<a class="indexterm" name="id2914920"></a>
+<a class="indexterm" name="id2912533"></a>
 Should your Win clients have had the old <tt class="filename">ADOBE*.*</tt>
 files for the Adobe PostScript driver installed, the download and
 installation of the new CUPS PostScript driver for Windows NT/2k/XP
@@ -9472,7 +9472,7 @@ which uses that particular driver. You need to "delete" all printers
 using this driver in the "Printers" folder first. You will need
 Administrator privileges to do this.
 </p></li><li><p>
-<a class="indexterm" name="id2914975"></a>
+<a class="indexterm" name="id2912587"></a>
 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 in <a href="#printing" title="Chapter�18.�Classical Printing Support">the printing chapter</a>: either change
@@ -9480,14 +9480,14 @@ a driver for an existing printer by running the "Printer Properties"
 dialog, or use <b class="command">rpcclient</b> with the
 <b class="command">setdriver</b> sub-command.
 </p></li></ol></div><p>
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915016"></a>Benefits of using "CUPS PostScript Driver for
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912629"></a>Benefits of using "CUPS PostScript Driver for
 Windows NT/2k/XP" instead of Adobe Driver</h3></div></div><div></div></div><p>
 You are interested in a comparison between the CUPS and the Adobe
 PostScript drivers? For our purposes these are the most important
 items which weigh in favor of the CUPS ones:
 </p><div class="itemizedlist"><ul type="disc"><li><p>no hassle with the Adobe EULA</p></li><li><p>no hassle with the question &#8220;<span class="quote">Where do I
 get the ADOBE*.* driver files from?</span>&#8221;</p></li><li><p>
-<a class="indexterm" name="id2915056"></a>
+<a class="indexterm" name="id2912669"></a>
 		the Adobe drivers (on request of the printer PPD
 associated with them) often put a PJL header in front of the main
 PostScript part of the print file. Thus the printfile starts with
@@ -9497,10 +9497,10 @@ of <i class="parameter"><tt>%!PS</tt></i>). This leads to the
 CUPS daemon auto-typing the incoming file as a print-ready file,
 not initiating a pass through the "pstops" filter (to speak more
 technically, it is not regarded as the generic MIME type 
-<a class="indexterm" name="id2915093"></a>
+<a class="indexterm" name="id2912706"></a>
 <span class="emphasis"><em>application/postscript</em></span>, but as
 the more special MIME type
-<a class="indexterm" name="id2915107"></a>
+<a class="indexterm" name="id2912720"></a>
 <span class="emphasis"><em>application/cups.vnd-postscript</em></span>),
 which therefore also leads to the page accounting in
 <span class="emphasis"><em>/var/log/cups/page_log</em></span> not
@@ -9530,7 +9530,7 @@ not disturb any other applications as they will regard it as a comment
 and simply ignore it).</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></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915223"></a>Run "cupsaddsmb" (quiet Mode)</h3></div></div><div></div></div><a class="indexterm" name="id2915231"></a><a class="indexterm" name="id2915239"></a><p>
+1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912835"></a>Run "cupsaddsmb" (quiet Mode)</h3></div></div><div></div></div><a class="indexterm" name="id2912844"></a><a class="indexterm" name="id2912852"></a><p>
 The cupsaddsmb command copies the needed files into your
 <i class="parameter"><tt>[print$]</tt></i> share. Additionally, the PPD
 associated with this printer is copied from
@@ -9539,7 +9539,7 @@ associated with this printer is copied from
 Windows client installations via Point'n'Print. Before we can run the
 command successfully, we need to be sure that we can authenticate
 towards Samba. If you have a small network you are probably using user
-level security (<a class="indexterm" name="id2915277"></a><i class="parameter"><tt>security</tt></i> = user). 
+level security (<a class="indexterm" name="id2912890"></a><i class="parameter"><tt>security</tt></i> = user). 
 </p><p>
 Here is an example of a successfully run cupsaddsmb command. 
 </p><pre class="screen">
@@ -9550,7 +9550,7 @@ To share <span class="emphasis"><em>all</em></span> printers and drivers, use th
 <tt class="option">-a</tt> parameter instead of a printer name. Since
 cupsaddsmb "exports" the printer drivers to Samba, it should be
 obvious that it only works for queues with a CUPS driver associated.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915344"></a>Run "cupsaddsmb" with verbose Output</h3></div></div><div></div></div><a class="indexterm" name="id2915352"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912958"></a>Run "cupsaddsmb" with verbose Output</h3></div></div><div></div></div><a class="indexterm" name="id2912965"></a><p>
 Probably you want to see what's going on. Use the
 <tt class="option">-v</tt> parameter to get a more verbose output. The
 output below was edited for better readability: all "\" at the end of
@@ -9559,7 +9559,7 @@ indentation here:
 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 You will see the root password for the Samba account printed on
 screen. 
-</p></div><a class="indexterm" name="id2915380"></a><a class="indexterm" name="id2915391"></a><pre class="screen">
+</p></div><a class="indexterm" name="id2912994"></a><a class="indexterm" name="id2913004"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>cupsaddsmb -U root -v infotec_2105</tt></b>
 Password for root required to access localhost via GANDALF:
 Running command: smbclient //localhost/print\$ -N -U'root%secret' \
@@ -9626,11 +9626,11 @@ you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in
 between. They occur, because the directories WIN40 and W32X86 already
 existed in the <i class="parameter"><tt>[print$]</tt></i> driver download share
 (from a previous driver installation). They are harmless here.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915567"></a>Understanding cupsaddsmb</h3></div></div><div></div></div><a class="indexterm" name="id2915576"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913117"></a>Understanding cupsaddsmb</h3></div></div><div></div></div><a class="indexterm" name="id2913126"></a><p>
 What has happened? What did cupsaddsmb do? There are five stages of
 the procedure
 </p><div class="orderedlist"><ol type="1"><li><p>
-	<a class="indexterm" name="id2915603"></a>
+	<a class="indexterm" name="id2913153"></a>
 			call the CUPS server via IPP and request the
 driver files and the PPD file for the named printer;</p></li><li><p>store the files temporarily in the local
 TEMPDIR (as defined in
@@ -9638,11 +9638,11 @@ TEMPDIR (as defined in
  <i class="parameter"><tt>[print$]</tt></i> share and put the files into the
  share's WIN40 (for Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub
  directories;</p></li><li><p>
-<a class="indexterm" name="id2915647"></a>
+<a class="indexterm" name="id2913197"></a>
 		connect via rpcclient to the Samba server and
 execute the "adddriver" command with the correct
 parameters;</p></li><li><p>
-<a class="indexterm" name="id2915666"></a>
+<a class="indexterm" name="id2913216"></a>
 		connect via rpcclient to the Samba server a second
 time and execute the "setdriver" command.</p></li></ol></div><p>
 Note, that you can run the cupsaddsmb utility with parameters to
@@ -9653,7 +9653,7 @@ life most people will have their CUPS and Samba servers run on the
 same host):
 </p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>cupsaddsmb -H sambaserver -h cupsserver -v printername</tt></b>
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915714"></a>How to recognize if cupsaddsmb completed successfully</h3></div></div><div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913264"></a>How to recognize if cupsaddsmb completed successfully</h3></div></div><div></div></div><p>
 You <span class="emphasis"><em>must</em></span> always check if the utility completed
 successfully in all fields. You need as a minimum these 3 messages
 amongst the output:
@@ -9674,7 +9674,7 @@ It is impossible to see any diagnostic output if you don't run
 cupsaddsmb in verbose mode.  Therefore we strongly recommend to not
 use the default quiet mode.  It will hide any problems from you which
 might occur.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915798"></a>cupsaddsmb with a Samba PDC</h3></div></div><div></div></div><a class="indexterm" name="id2915806"></a><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913349"></a>cupsaddsmb with a Samba PDC</h3></div></div><div></div></div><a class="indexterm" name="id2913357"></a><p>
 You can't get the standard cupsaddsmb command to run on a Samba PDC?
 You are asked for the password credential all over again and again and
 the command just will not take off at all? Try one of these
@@ -9686,18 +9686,18 @@ variations:
 </pre><p>
 (Note the two backslashes: the first one is required to
 "escape" the second one).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915877"></a>cupsaddsmb Flowchart</h3></div></div><div></div></div><a class="indexterm" name="id2915885"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913427"></a>cupsaddsmb Flowchart</h3></div></div><div></div></div><a class="indexterm" name="id2913435"></a><p>
 Here is a chart about the procedures, commandflows and
 dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is
 not intended to, and does not work with, "raw" queues!
 </p><p>
 	</p><div class="figure"><a name="small14"></a><p class="title"><b>Figure�19.16.�cupsaddsmb flowchart</b></p><div class="mediaobject"><img src="projdoc/imagefiles/14small.png" width="270" alt="cupsaddsmb flowchart"></div></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915946"></a>Installing the PostScript Driver on a Client</h3></div></div><div></div></div><a class="indexterm" name="id2915953"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913497"></a>Installing the PostScript Driver on a Client</h3></div></div><div></div></div><a class="indexterm" name="id2913504"></a><p>
 After cupsaddsmb completed, your driver is prepared for the clients to
 use. Here are the steps you must perform to download and install it
 via "Point'n'Print". From a Windows client, browse to the CUPS/Samba
 server;
-</p><div class="itemizedlist"><a class="indexterm" name="id2915973"></a><ul type="disc"><li><p>open the <span class="emphasis"><em>Printers</em></span>
+</p><div class="itemizedlist"><a class="indexterm" name="id2913522"></a><ul type="disc"><li><p>open the <span class="emphasis"><em>Printers</em></span>
 share of Samba in Network Neighbourhood;</p></li><li><p>right-click on the printer in
 question;</p></li><li><p>from the opening context-menu select
 <span class="emphasis"><em>Install...</em></span> or 
@@ -9712,7 +9712,7 @@ an application like Winword, the new printer will appears in a
 <tt class="filename">\\SambaServer\PrinterName</tt> entry in the
 dropdown list of available printers.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2916045"></a>
+<a class="indexterm" name="id2913594"></a>
 cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher
 and Samba from 2.2.4. If it doesn't work, or if the automatic printer
 driver download to the clients doesn't succeed, you can still manually
@@ -9727,7 +9727,7 @@ functions. (Note that user "ntadmin" needs to be a valid Samba user
 with the required privileges to access the printershare) This would
 set up the printer connection in the traditional
 <span class="emphasis"><em>LanMan</em></span> way (not using MS-RPC).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916097"></a>Avoiding critical PostScript Driver Settings on the
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913646"></a>Avoiding critical PostScript Driver Settings on the
 Client</h3></div></div><div></div></div><p>
 Soooo: printing works, but there are still problems. Most jobs print
 well, some don't print at all. Some jobs have problems with fonts,
@@ -9753,7 +9753,7 @@ get a printout at all) (Adobe)</p></li><li><p>Sometimes you can choose <span cla
 Level</em></span>: in case of problems try <span class="emphasis"><em>2</em></span>
 instead of <span class="emphasis"><em>3</em></span> (the latest ESP Ghostscript package
 handles Level 3 PostScript very well) (Adobe).</p></li><li><p>Say <span class="emphasis"><em>Yes</em></span> to <span class="emphasis"><em>PostScript
-Error Handler</em></span> (Adobe)</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2916229"></a>Installing PostScript Driver Files manually (using
+Error Handler</em></span> (Adobe)</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913780"></a>Installing PostScript Driver Files manually (using
 rpcclient)</h2></div></div><div></div></div><p>
 Of course you can run all the commands which are embedded into the
 cupsaddsmb convenience utility yourself, one by one, and hereby upload
@@ -9762,17 +9762,17 @@ and prepare the driver files for future client downloads.
 printer should be there. We are providing the driver
 now);</p></li><li><p>copy all files to
 		<i class="parameter"><tt>[print$]</tt></i></p></li><li><p>
-<a class="indexterm" name="id2916279"></a>
+<a class="indexterm" name="id2913829"></a>
 		run <b class="command">rpcclient adddriver</b>
 (for each client architecture you want to support):</p></li><li><p>
-<a class="indexterm" name="id2916303"></a>
+<a class="indexterm" name="id2913853"></a>
 		run <b class="command">rpcclient
 setdriver.</b></p></li></ol></div><p>
-<a class="indexterm" name="id2916325"></a>
-<a class="indexterm" name="id2916336"></a>
-<a class="indexterm" name="id2916347"></a>
-<a class="indexterm" name="id2916358"></a>
-<a class="indexterm" name="id2916369"></a>
+<a class="indexterm" name="id2913875"></a>
+<a class="indexterm" name="id2913886"></a>
+<a class="indexterm" name="id2913897"></a>
+<a class="indexterm" name="id2913908"></a>
+<a class="indexterm" name="id2913919"></a>
 We are going to do this now. First, read the man page on "rpcclient"
 to get a first idea. Look at all the printing related
 sub-commands. <b class="command">enumprinters</b>,
@@ -9783,7 +9783,7 @@ the MS-RPC protocol. You can use it to query (and command) a Win NT
 (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other
 things, to benefit from the "Point'n'Print" features. Samba can now
 mimic this too.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916423"></a>A Check of the rpcclient man Page</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913973"></a>A Check of the rpcclient man Page</h3></div></div><div></div></div><p>
 First let's have a little check of the rpcclient man page. Here are
 two relevant passages:
 </p><p>
@@ -9816,13 +9816,13 @@ printer driver associated with an installed printer. The printer
 driver must already be correctly installed on the print server.
 </p><p> See also the enumprinters and enumdrivers commands for
 obtaining a list of installed printers and drivers.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916536"></a>Understanding the rpcclient man page</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914086"></a>Understanding the rpcclient man page</h3></div></div><div></div></div><p>
 The <span class="emphasis"><em>exact</em></span> format isn't made too clear by the man
 page, since you have to deal with some parameters containing
 spaces. Here is a better description for it. We have line-broken the
 command and indicated the breaks with "\". Usually you would type the
 command in one line without the linebreaks:
-</p><a class="indexterm" name="id2916558"></a><pre class="screen">
+</p><a class="indexterm" name="id2914109"></a><pre class="screen">
  adddriver "Architecture" \
            "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
            LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
@@ -9850,9 +9850,9 @@ box now, and access it from a UNIX workstation. We will query it
 with <b class="command">rpcclient</b> to see what it tells us and
 try to understand the man page more clearly which we've read just
 now.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916644"></a>Producing an Example by querying a Windows Box</h3></div></div><div></div></div><p>
-	<a class="indexterm" name="id2916655"></a>
-	<a class="indexterm" name="id2916666"></a>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914186"></a>Producing an Example by querying a Windows Box</h3></div></div><div></div></div><p>
+	<a class="indexterm" name="id2914198"></a>
+	<a class="indexterm" name="id2914209"></a>
 We could run <b class="command">rpcclient</b> with a
 <b class="command">getdriver</b> or a <b class="command">getprinter</b>
 subcommand (in level 3 verbosity) against it. Just sit down at UNIX or
@@ -9863,7 +9863,7 @@ following command:
 </pre><p>
 From the result it should become clear which is which. Here is an
 example from my installation:
-</p><a class="indexterm" name="id2916729"></a><pre class="screen">
+</p><a class="indexterm" name="id2914272"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'Danka%xxxx' W2KSERVER \
 	-c'getdriver "DANKA InfoStream Virtual Printer" 3'</tt></b>
  cmd = getdriver "DANKA InfoStream Virtual Printer" 3
@@ -9895,16 +9895,16 @@ Some printer drivers list additional files under the label
 <span class="emphasis"><em>ListOfFiles,Comma-separated</em></span>. For the CUPS
 PostScript drivers we don't need any (nor would we for the Adobe
 PostScript driver): therefore the field will get a "NULL" entry.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916790"></a>What is required for adddriver and setdriver to succeed</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914333"></a>What is required for adddriver and setdriver to succeed</h3></div></div><div></div></div><p>
 From the manpage (and from the quoted output
 of <span class="emphasis"><em>cupsaddsmb</em></span>, above) it becomes clear that you
 need to have certain conditions in order to make the manual uploading
 and initializing of the driver files succeed. The two rpcclient
-<a class="indexterm" name="id2916810"></a>
+<a class="indexterm" name="id2914353"></a>
 subcommands (<b class="command">adddriver</b> and
 <b class="command">setdriver</b>) need to encounter the following
 pre-conditions to complete successfully:
-</p><div class="itemizedlist"><ul type="disc"><li><p>you are connected as <a class="indexterm" name="id2916845"></a><i class="parameter"><tt>printer admin</tt></i>, or root (note,
+</p><div class="itemizedlist"><ul type="disc"><li><p>you are connected as <a class="indexterm" name="id2914387"></a><i class="parameter"><tt>printer admin</tt></i>, or root (note,
 that this is <span class="emphasis"><em>not</em></span> the "Printer Operators" group in
 NT, but the <span class="emphasis"><em>printer admin</em></span> group, as defined in
 the <i class="parameter"><tt>[global]</tt></i> section of
@@ -9920,8 +9920,8 @@ root</b>);</p></li><li><p>the user you're connecting as must be able to write to
 the <i class="parameter"><tt>[print$]</tt></i> share and create
 subdirectories;</p></li><li><p>the printer you are going to setup for the Windows
 clients, needs to be installed in CUPS already;</p></li><li><p>
-	<a class="indexterm" name="id2916953"></a>
-	<a class="indexterm" name="id2916964"></a>
+	<a class="indexterm" name="id2914496"></a>
+	<a class="indexterm" name="id2914508"></a>
 		the CUPS printer must be known to Samba, otherwise the
 <b class="command">setdriver</b> subcommand fails with an
 NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by
@@ -9930,7 +9930,7 @@ rpcclient. A long-standing bug prevented a proper update of the
 printer list until every smbd process had received a SIGHUP or was
 restarted. Remember this in case you've created the CUPS printer just
 shortly ago and encounter problems: try restarting
-Samba.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917000"></a>Manual Driver Installation in 15 Steps</h3></div></div><div></div></div><p>
+Samba.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914542"></a>Manual Driver Installation in 15 Steps</h3></div></div><div></div></div><p>
 We are going to install a printer driver now by manually executing all
 required commands. As this may seem a rather complicated process at
 first, we go through the procedure step by step, explaining every
@@ -9943,7 +9943,7 @@ to the CUPS system. The printer is accessed via a socket
 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 for this step
 </p></li><li><p class="title"><b>(optional) Check if the Printer is recognized by
-Samba</b></p><a class="indexterm" name="id2917080"></a><pre class="screen">
+Samba</b></p><a class="indexterm" name="id2914623"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn</tt></b>
 flags:[0x800000]
 name:[\\kde-bitshop\mysmbtstprn]
@@ -9961,7 +9961,7 @@ following steps. Alternatively you can authenticate as one of the
 users from the "write list" as defined in <tt class="filename">smb.conf</tt> for
 <i class="parameter"><tt>[print$]</tt></i>.
 </p></li><li><p class="title"><b>(optional) Check if Samba knows a Driver for the
-Printer</b></p><a class="indexterm" name="id2917168"></a><a class="indexterm" name="id2917178"></a><pre class="screen">
+Printer</b></p><a class="indexterm" name="id2914711"></a><a class="indexterm" name="id2914722"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
 			| grep driver </tt></b>
 drivername:[]
@@ -10018,7 +10018,7 @@ The driver files now are in the W32X86 architecture "root" of
 <i class="parameter"><tt>[print$]</tt></i>.
 </p></li><li><p class="title"><b>Tell Samba that these are
 <span class="emphasis"><em>Driver</em></span> Files
-(<b class="command">adddriver</b>)</b></p><a class="indexterm" name="id2917388"></a><pre class="screen">
+(<b class="command">adddriver</b>)</b></p><a class="indexterm" name="id2914932"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
   cupsdrvr.dll:mysmbtstprn.PPD: \
   cupsui.dll:cups.hlp:NULL:RAW:NULL" \
@@ -10051,7 +10051,7 @@ total 5039
 Notice how step 6 did also move the driver files to the appropriate
 subdirectory. Compare with the situation after step 5.
 </p></li><li><p class="title"><b>(optional) Verify if Samba now recognizes the
-Driver</b></p><a class="indexterm" name="id2917510"></a><pre class="screen">
+Driver</b></p><a class="indexterm" name="id2915053"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
 	| grep -B2 -A5 mydrivername</tt></b>
 Printer Driver Info 3:
@@ -10066,7 +10066,7 @@ Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 Remember, this command greps for the name you did choose for the
 driver in step Six. This command must succeed before you can proceed.
 </p></li><li><p class="title"><b>Tell Samba which Printer should use these Driver
-Files (<b class="command">setdriver</b>)</b></p><a class="indexterm" name="id2917574"></a><pre class="screen">
+Files (<b class="command">setdriver</b>)</b></p><a class="indexterm" name="id2915118"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost</tt></b>
 Successfully set mysmbtstprn to driver mydrivername
 </pre><p>
@@ -10077,7 +10077,7 @@ setdriver command to succeed. The only pre-conditions are:
 <b class="command">enumdrivers</b> must find the driver and
 <b class="command">enumprinters</b> must find the printer.
 </p></li><li><p class="title"><b>(optional) Verify if Samba has this Association
-recognized</b></p><a class="indexterm" name="id2917642"></a><a class="indexterm" name="id2917653"></a><a class="indexterm" name="id2917664"></a><pre class="screen">
+recognized</b></p><a class="indexterm" name="id2915186"></a><a class="indexterm" name="id2915197"></a><a class="indexterm" name="id2915208"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
   | grep driver</tt></b>
 drivername:[mydrivername]
@@ -10115,14 +10115,14 @@ Printer Driver Info 3:
      comment:[mysmbtstprn]
 
 </pre><p>
-<a class="indexterm" name="id2917757"></a>
+<a class="indexterm" name="id2915300"></a>
 Compare these results with the ones from steps 2 and 3. Note that
 every single of these commands show the driver is installed.  Even
 the <b class="command">enumprinters</b> command now lists the driver
 on the "description" line.
 </p></li><li><p class="title"><b>(optional) Tickle the Driver into a correct
 Device Mode</b></p><p>
-<a class="indexterm" name="id2917794"></a>
+<a class="indexterm" name="id2915338"></a>
 You certainly know how to install the driver on the client.  In case
 you are not particularly familiar with Windows, here is a short
 recipe: browse the Network Neighbourhood, go to the Samba server, look
@@ -10146,7 +10146,7 @@ Change any printer setting once (like changing <span class="emphasis"><em>"portr
 	"landscape"</em></span>), click <span class="guibutton">Apply</span>; change the setting
 back.
 </p></li><li><p class="title"><b>Install the Printer on a Client
-("Point'n'Print")</b></p><a class="indexterm" name="id2917882"></a><pre class="screen">
+("Point'n'Print")</b></p><a class="indexterm" name="id2915426"></a><pre class="screen">
 <tt class="prompt">C:\&gt; </tt><b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"</tt></b>
 </pre><p>
 If it doesn't work it could be a permission problem with the
@@ -10164,7 +10164,7 @@ RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
 </p></li><li><p class="title"><b>Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
 Success</b></p><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>echo "Cheeeeerioooooo! Success..." &gt;&gt; /var/log/samba/log.smbd</tt></b>
-</pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918021"></a>Troubleshooting revisited</h3></div></div><div></div></div><p>
+</pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915566"></a>Troubleshooting revisited</h3></div></div><div></div></div><p>
 The setdriver command will fail, if in Samba's mind the queue is not
 already there. You had promising messages about the:
 </p><pre class="screen">
@@ -10179,7 +10179,7 @@ a disappointing message like this one beneath?
  result was NT_STATUS_UNSUCCESSFUL
 
 </pre><p>
-<a class="indexterm" name="id2918062"></a>
+<a class="indexterm" name="id2915607"></a>
 It is not good enough that you
 can see the queue <span class="emphasis"><em>in CUPS</em></span>, using
 the <b class="command">lpstat -p ir85wm</b> command. A
@@ -10189,12 +10189,12 @@ fails unless you re-start Samba or send a HUP to all smbd
 processes. To verify if this is the reason why Samba doesn't
 execute the setdriver command successfully, check if Samba "sees"
 the printer: 
-</p><a class="indexterm" name="id2918090"></a><pre class="screen">
+</p><a class="indexterm" name="id2915634"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm</tt></b>
         printername:[ir85wm]
 </pre><p>
 An alternative command could be this: 
-</p><a class="indexterm" name="id2918128"></a><pre class="screen">
+</p><a class="indexterm" name="id2915673"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </tt></b>
         cmd = getprinter ir85wm
         flags:[0x800000]
@@ -10204,20 +10204,20 @@ An alternative command could be this:
 </pre><p>
 BTW, you can use these commands, plus a few more, of course,
 to install drivers on remote Windows NT print servers too!
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918173"></a>The printing <tt class="filename">*.tdb</tt> Files</h2></div></div><div></div></div><p>
-<a class="indexterm" name="id2918190"></a>
-<a class="indexterm" name="id2918198"></a>
-<a class="indexterm" name="id2918209"></a>
-<a class="indexterm" name="id2918220"></a>
-<a class="indexterm" name="id2918232"></a>
-<a class="indexterm" name="id2918243"></a>
-<a class="indexterm" name="id2918254"></a>
-<a class="indexterm" name="id2918265"></a>
-<a class="indexterm" name="id2918276"></a>
-<a class="indexterm" name="id2918287"></a>
-<a class="indexterm" name="id2918299"></a>
-<a class="indexterm" name="id2918310"></a>
-<a class="indexterm" name="id2918321"></a>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915718"></a>The printing <tt class="filename">*.tdb</tt> Files</h2></div></div><div></div></div><p>
+<a class="indexterm" name="id2915734"></a>
+<a class="indexterm" name="id2915743"></a>
+<a class="indexterm" name="id2915754"></a>
+<a class="indexterm" name="id2915765"></a>
+<a class="indexterm" name="id2915776"></a>
+<a class="indexterm" name="id2915788"></a>
+<a class="indexterm" name="id2915799"></a>
+<a class="indexterm" name="id2915810"></a>
+<a class="indexterm" name="id2915821"></a>
+<a class="indexterm" name="id2915832"></a>
+<a class="indexterm" name="id2915843"></a>
+<a class="indexterm" name="id2915854"></a>
+<a class="indexterm" name="id2915866"></a>
 Some mystery is associated with the series of files with a
 tdb-suffix appearing in every Samba installation. They are
 <tt class="filename">connections.tdb</tt>,
@@ -10232,7 +10232,7 @@ tdb-suffix appearing in every Samba installation. They are
 <tt class="filename">ntprinters.tdb</tt>,
 <tt class="filename">sessionid.tdb</tt> and
 <tt class="filename">secrets.tdb</tt>. What is their purpose?
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918418"></a>Trivial DataBase Files</h3></div></div><div></div></div><a class="indexterm" name="id2918426"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915962"></a>Trivial DataBase Files</h3></div></div><div></div></div><a class="indexterm" name="id2915970"></a><p>
 A Windows NT (Print) Server keeps track of all information needed to serve
 its duty toward its clients by storing entries in the Windows
 "Registry". Client queries are answered by reading from the registry,
@@ -10245,7 +10245,7 @@ or <tt class="filename">/var/lock/samba/</tt> . The printing related files
 are <tt class="filename">ntprinters.tdb</tt>,
 <tt class="filename">printing.tdb</tt>,<tt class="filename">ntforms.tdb</tt> and
 <tt class="filename">ntdrivers.tdb</tt>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918497"></a>Binary Format</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916041"></a>Binary Format</h3></div></div><div></div></div><p>
 <tt class="filename">*.tdb</tt> files are not human readable. They are
 written in a binary format. "Why not ASCII?", you may ask. "After all,
 ASCII configuration files are a good and proofed tradition on UNIX."
@@ -10258,7 +10258,7 @@ same time</em></span>. The file format of Samba's
 <tt class="filename">*.tdb</tt> files allows for this provision. Many smbd
 processes may write to the same <tt class="filename">*.tdb</tt> file at the
 same time. This wouldn't be possible with pure ASCII files.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918559"></a>Losing <tt class="filename">*.tdb</tt> Files</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916103"></a>Losing <tt class="filename">*.tdb</tt> Files</h3></div></div><div></div></div><p>
 It is very important that all <tt class="filename">*.tdb</tt> files remain
 consistent over all write and read accesses. However, it may happen
 that these files <span class="emphasis"><em>do</em></span> get corrupted. (A
@@ -10268,7 +10268,7 @@ etc.). In cases of trouble, a deletion of the old printing-related
 <tt class="filename">*.tdb</tt> files may be the only option. You need to
 re-create all print related setup after that.  Or you have made a
 backup of the <tt class="filename">*.tdb</tt> files in time.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918617"></a>Using <span class="emphasis"><em>tdbbackup</em></span></h3></div></div><div></div></div><a class="indexterm" name="id2918627"></a><a class="indexterm" name="id2918641"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916162"></a>Using <span class="emphasis"><em>tdbbackup</em></span></h3></div></div><div></div></div><a class="indexterm" name="id2916172"></a><a class="indexterm" name="id2916186"></a><p>
 Samba ships with a little utility which helps the root user of your
 system to back up your <tt class="filename">*.tdb</tt> files. If you run it
 with no argument, it prints a little usage message:
@@ -10297,10 +10297,10 @@ ntprinters.tdb sessionid.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb.bak
 
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918753"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div><div></div></div><a class="indexterm" name="id2918760"></a><p>
+</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2916297"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div><div></div></div><a class="indexterm" name="id2916305"></a><p>
 CUPS ships with good support for HP LaserJet type printers.  You can
 install the generic driver as follows:
-</p><a class="indexterm" name="id2918774"></a><pre class="screen">
+</p><a class="indexterm" name="id2916320"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</tt></b>
 </pre><p>
 The <tt class="option">-m</tt> switch will retrieve the
@@ -10319,7 +10319,7 @@ best used for each printer. Its database is kept current by the
 tireless work of Till Kamppeter from MandrakeSoft, who is also the
 principal author of the foomatic-rip utility.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2918861"></a>
+<a class="indexterm" name="id2916407"></a>
 The former "cupsomatic" concept is now be replaced by the new, much
 more powerful "foomatic-rip". foomatic-rip is the successor of
 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
@@ -10330,7 +10330,7 @@ not work with PPDs generated for the old cupsomatic. The new-style
 PPDs are 100% compliant to the Adobe PPD specification. They are
 intended to be used by Samba and the cupsaddsmb utility also, to
 provide the driver files for the Windows clients also!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918890"></a>foomatic-rip and Foomatic explained</h3></div></div><div></div></div><a class="indexterm" name="id2918898"></a><a class="indexterm" name="id2918907"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916436"></a>foomatic-rip and Foomatic explained</h3></div></div><div></div></div><a class="indexterm" name="id2916444"></a><a class="indexterm" name="id2916452"></a><p>
 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
 to create their printing related software (which, BTW, works on all
 UNIXes and on Mac OS X or Darwin too). It is not known as well as it
@@ -10347,7 +10347,7 @@ its <a href="http://www.linuxprinting.org/foomatic.html" target="_top">Foomatic<
 database. Currently there are <a href="http://www.linuxprinting.org/driver_list.cgi" target="_top">245 drivers</a>
 in the database: many drivers support various models, and many models
 may be driven by different drivers; it's your choice!
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2918963"></a>690 "perfect" Printers</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916477"></a>690 "perfect" Printers</h4></div></div><div></div></div><p>
 At present there are 690 devices dubbed as working "perfectly", 181
 "mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
 that most of these are non-PostScript models (PostScript printers are
@@ -10358,7 +10358,7 @@ doesn't also scan and copy and fax under GNU/Linux: then this is a
 truly astonishing achievement. Three years ago the number was not
 more than 500, and Linux or UNIX "printing" at the time wasn't
 anywhere near the quality it is today!
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2918986"></a>How the "Printing HOWTO" started it all</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916531"></a>How the "Printing HOWTO" started it all</h4></div></div><div></div></div><p>
 A few years ago <a href="http://www2.picante.com:81/~gtaylor/" target="_top">Grant Taylor</a>
 started it all. The roots of today's Linuxprinting.org are in the
 first <a href="http://www.linuxprinting.org/foomatic2.9/howto/" target="_top">Linux Printing
@@ -10372,7 +10372,7 @@ hardware and driver zoo that made up Linux printing of the time. This
 database became the core component of today's Foomatic collection of
 tools and data. In the meantime it has moved to an XML representation
 of the data.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919032"></a>Foomatic's strange Name</h4></div></div><div></div></div><a class="indexterm" name="id2919040"></a><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916577"></a>Foomatic's strange Name</h4></div></div><div></div></div><a class="indexterm" name="id2916586"></a><p>
 "Why the funny name?", you ask. When it really took off, around spring
 2000, CUPS was far less popular than today, and most systems used LPD,
 LPRng or even PDQ to print. CUPS shipped with a few generic "drivers"
@@ -10395,7 +10395,7 @@ developments available for CUPS;</p></li><li><p>It made available a lot of addit
 to CUPS users (because often the "traditional" Ghostscript way of
 printing was the only one available);</p></li><li><p>It gave all the advanced CUPS options (web interface,
 GUI driver configurations) to users wanting (or needing) to use
-Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919108"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div><div></div></div><a class="indexterm" name="id2919116"></a><a class="indexterm" name="id2919124"></a><a class="indexterm" name="id2919132"></a><p>
+Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916653"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div><div></div></div><a class="indexterm" name="id2916661"></a><a class="indexterm" name="id2916670"></a><a class="indexterm" name="id2916678"></a><p>
 CUPS worked through a quickly-hacked up filter script named <a href="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&amp;show=0" target="_top">cupsomatic</a>.
 cupsomatic ran the printfile through Ghostscript, constructing
 automatically the rather complicated command line needed. It just
@@ -10429,8 +10429,8 @@ Foomatic up to versions 2.0.x required (ugly) Perl data structures
 attached the Linuxprinting.org PPDs for CUPS. It had a different
 "*omatic" script for every spooler, as well as different printer
 configuration files..
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919272"></a>The <span class="emphasis"><em>Grand Unification</em></span>
-achieved...</h4></div></div><div></div></div><a class="indexterm" name="id2919284"></a><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916817"></a>The <span class="emphasis"><em>Grand Unification</em></span>
+achieved...</h4></div></div><div></div></div><a class="indexterm" name="id2916829"></a><p>
 This all has changed in Foomatic versions 2.9 (Beta) and released as
 "stable" 3.0. This has now achieved the convergence of all *omatic
 scripts: it is called the <a href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&amp;show=0" target="_top">foomatic-rip</a>.
@@ -10465,7 +10465,7 @@ sizes for many printers; and it will support printing on media drawn
 from different paper trays within the same job (in both cases: even
 where there is no support for this from Windows-based vendor printer
 drivers).
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919366"></a>Driver Development outside</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916912"></a>Driver Development outside</h4></div></div><div></div></div><p>
 Most driver development itself does not happen within
 Linuxprinting.org. Drivers are written by independent maintainers.
 Linuxprinting.org just pools all the information, and stores it in its
@@ -10488,7 +10488,7 @@ effort, started by Michael Sweet (also lead developer for CUPS), now
 directed by Robert Krawitz, which has achieved an amazing level of
 photo print quality (many Epson users swear that its quality is
 better than the vendor drivers provided by Epson for the Microsoft
-platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919448"></a>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
+platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2916991"></a>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
 commercial UNIX</h4></div></div><div></div></div><p>
 Linuxprinting.org today is the one-stop "shop" to download printer
 drivers. Look for printer information and <a href="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/" target="_top">tutorials</a>
@@ -10509,7 +10509,7 @@ of the Foomatic project.
 Till Kamppeter from MandrakeSoft is doing an excellent job in his
 spare time to maintain Linuxprinting.org and Foomatic. So if you use
 it often, please send him a note showing your appreciation.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2919519"></a>Foomatic Database generated PPDs</h4></div></div><div></div></div><p>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2917064"></a>Foomatic Database generated PPDs</h4></div></div><div></div></div><p>
 The Foomatic database is an amazing piece of ingenuity in itself. Not
 only does it keep the printer and driver information, but it is
 organized in a way that it can generate "PPD" files "on the fly" from
@@ -10534,7 +10534,7 @@ GUI tools (like KDE's marvellous <a href="http://printing.kde.org/overview/kprin
 or the GNOME <a href="http://gtklp.sourceforge.net/" target="_top">"gtklp"</a>, "xpp" and the CUPS
 web interface) read the PPD too and use this information to present
 the available settings to the user as an intuitive menu selection.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919583"></a>foomatic-rip and Foomatic-PPD Download and Installation</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917129"></a>foomatic-rip and Foomatic-PPD Download and Installation</h3></div></div><div></div></div><p>
 Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus"
 compatible printer in CUPS (note that recent distributions of SuSE,
 UnitedLinux and Mandrake may ship with a complete package of
@@ -10631,7 +10631,7 @@ the driver/model) contain support for a certain "device", representing
 the selected "driver" for your model (as shown by "gs
 -h")</p></li><li><p>foomatic-rip needs a new version of PPDs (PPD versions
 produced for cupsomatic don't work with
-foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920055"></a>Page Accounting with CUPS</h2></div></div><div></div></div><a class="indexterm" name="id2920064"></a><p>
+foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2917602"></a>Page Accounting with CUPS</h2></div></div><div></div></div><a class="indexterm" name="id2917611"></a><p>
 Often there are questions regarding "print quotas" wherein Samba users
 (that is, Windows clients) should not be able to print beyond a
 certain amount of pages or data volume per day, week or month. This
@@ -10644,17 +10644,17 @@ Of course one could "hack" things with one's own scripts. But then
 there is CUPS. CUPS supports "quotas" which can be based on sizes of
 jobs or on the number of pages or both, and are spanning any time
 period you want.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920098"></a>Setting up Quotas</h3></div></div><div></div></div><a class="indexterm" name="id2920107"></a><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917645"></a>Setting up Quotas</h3></div></div><div></div></div><a class="indexterm" name="id2917653"></a><p>
 This is an example command how root would set a print quota in CUPS,
 assuming an existing printer named "quotaprinter":
-</p><a class="indexterm" name="id2920124"></a><pre class="screen">
+</p><a class="indexterm" name="id2917671"></a><pre class="screen">
 <tt class="prompt">root# </tt><b class="userinput"><tt>lpadmin -p quotaprinter -o job-quota-period=604800 \
 	-o job-k-limit=1024 -o job-page-limit=100</tt></b>
 </pre><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></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920162"></a>Correct and incorrect Accounting</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917708"></a>Correct and incorrect Accounting</h3></div></div><div></div></div><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
@@ -10669,7 +10669,7 @@ printer is a non-PostScript model, you need to let CUPS do the job to
 convert the file to a print-ready format for the target printer. This
 will be working for currently about 1,000 different printer models,
 see <a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">the driver list at linuxprinting.org/</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920202"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917748"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div><div></div></div><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 through the "pstops" filter on the CUPS/Samba side, and
@@ -10682,14 +10682,14 @@ From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for
 Windows NT/2K/XP clients" (which is tagged in the download area of
 http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). It does
 <span class="emphasis"><em>not</em></span> work for Win9x/ME clients. But it guarantees:
-</p><div class="itemizedlist"><a class="indexterm" name="id2920239"></a><ul type="disc"><li><p>to not write an PJL-header</p></li><li><p>to still read and support all PJL-options named in the
+</p><div class="itemizedlist"><a class="indexterm" name="id2917786"></a><ul type="disc"><li><p>to not write an PJL-header</p></li><li><p>to still read and support all PJL-options named in the
 driver PPD with its own means</p></li><li><p> that the file will pass through the "pstops" filter
 on the CUPS/Samba server</p></li><li><p>to page-count correctly the
 printfile</p></li></ul></div><p>
 You can read more about the setup of this combination in the manpage
 for "cupsaddsmb" (which is only present with CUPS installed, and only
 current from CUPS 1.1.16).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920282"></a>The page_log File Syntax</h3></div></div><div></div></div><a class="indexterm" name="id2920291"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917829"></a>The page_log File Syntax</h3></div></div><div></div></div><a class="indexterm" name="id2917838"></a><p>
 These are the items CUPS logs in the "page_log" for every
 single <span class="emphasis"><em>page</em></span> of a job:
 </p><div class="itemizedlist"><ul type="disc"><li><p>Printer name</p></li><li><p>User name</p></li><li><p>Job ID</p></li><li><p>Time of printing</p></li><li><p>the page number</p></li><li><p>the number of copies</p></li><li><p>a billing information string
@@ -10709,7 +10709,7 @@ This was job ID "401", printed on "infotec_IS2027" by user "kurt", a
 from IP address 10.160.50.13. The next job had ID "402", was sent by
 user "boss" from IP address 10.160.51.33,printed from one page 440
 copies and is set to be billed to "finance-dep".
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920392"></a>Possible Shortcomings</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917938"></a>Possible Shortcomings</h3></div></div><div></div></div><p>
 What flaws or shortcomings are there with this quota system?
 </p><div class="itemizedlist"><ul type="disc"><li><p>the ones named above (wrongly logged job in case of
 printer hardware failure, etc.)</p></li><li><p>in reality, CUPS counts the job pages that are being
@@ -10723,7 +10723,7 @@ groups</p></li><li><p>no means to read out the current balance or the
 "used-up" number of current quota</p></li><li><p>a user having used up 99 sheets of 100 quota will
 still be able to send and print a 1,000 sheet job</p></li><li><p>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".</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920463"></a>Future Developments</h3></div></div><div></div></div><p>
+"client-error-not-possible".</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918010"></a>Future Developments</h3></div></div><div></div></div><p>
 This is the best system currently available, and there are huge
 improvements under development for CUPS 1.2:
 </p><div class="itemizedlist"><ul type="disc"><li><p>page counting will go into the "backends" (these talk
@@ -10731,9 +10731,9 @@ directly to the printer and will increase the count in sync with the
 actual printing process: thus a jam at the 5th sheet will lead to a
 stop in the counting)</p></li><li><p>quotas will be handled more flexibly</p></li><li><p>probably there will be support for users to inquire
 their "accounts" in advance</p></li><li><p>probably there will be support for some other tools
-around this topic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920510"></a>Other Accounting Tools</h3></div></div><div></div></div><p>
+around this topic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918058"></a>Other Accounting Tools</h3></div></div><div></div></div><p>
 PrintAnalyzer, pyKota, printbill, LogReport.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920525"></a>Additional Material</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918072"></a>Additional Material</h2></div></div><div></div></div><p>
 A printer queue with <span class="emphasis"><em>no</em></span> PPD associated to it is a
 "raw" printer and all files will go directly there as received by the
 spooler. The exceptions are file types "application/octet-stream"
@@ -10803,15 +10803,15 @@ the jobs of hundreds of users on some big machine, where no user is
 allowed to have direct access (such as when the operators often need
 to load the proper paper type before running the 10,000 page job
 requested by marketing for the mailing, etc.).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920734"></a>Auto-Deletion or Preservation of CUPS Spool Files</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918267"></a>Auto-Deletion or Preservation of CUPS Spool Files</h2></div></div><div></div></div><p>
 Samba print files pass through two "spool" directories. One is the
-incoming directory managed by Samba, (set in the <a class="indexterm" name="id2920747"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba directive in the
+incoming directory managed by Samba, (set in the <a class="indexterm" name="id2918280"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba directive in the
 <i class="parameter"><tt>[printers]</tt></i> section of
 <tt class="filename">smb.conf</tt>). The other is the spool directory of
 your UNIX print subsystem. For CUPS it is normally
 <tt class="filename">/var/spool/cups/</tt>, as set by the cupsd.conf
 directive <tt class="filename">RequestRoot /var/spool/cups</tt>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920792"></a>CUPS Configuration Settings explained</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918326"></a>CUPS Configuration Settings explained</h3></div></div><div></div></div><p>
 Some important parameter settings in the CUPS configuration file
 <tt class="filename">cupsd.conf</tt> are:
 </p><div class="variablelist"><dl><dt><span class="term">PreserveJobHistory Yes</span></dt><dd><p>
@@ -10835,26 +10835,26 @@ maximum to 0 disables this functionality. The default setting is
 </p></dd></dl></div><p>
 (There are also additional settings for "MaxJobsPerUser" and
 "MaxJobsPerPrinter"...)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920874"></a>Pre-conditions</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918407"></a>Pre-conditions</h3></div></div><div></div></div><p>
 For everything to work as announced, you need to have three
 things:
 </p><div class="itemizedlist"><ul type="disc"><li><p>a Samba-smbd which is compiled against "libcups" (Check
 on Linux by running "ldd `which smbd`")</p></li><li><p>a Samba-<tt class="filename">smb.conf</tt> setting of
-		<a class="indexterm" name="id2920908"></a><i class="parameter"><tt>printing</tt></i> = cups</p></li><li><p>another Samba-<tt class="filename">smb.conf</tt> setting of
-		<a class="indexterm" name="id2920935"></a><i class="parameter"><tt>printcap</tt></i> = cups</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+		<a class="indexterm" name="id2918443"></a><i class="parameter"><tt>printing</tt></i> = cups</p></li><li><p>another Samba-<tt class="filename">smb.conf</tt> setting of
+		<a class="indexterm" name="id2918469"></a><i class="parameter"><tt>printcap</tt></i> = cups</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 In this case all other manually set printing-related commands (like
-<a class="indexterm" name="id2920956"></a><i class="parameter"><tt>print command</tt></i>, 
-<a class="indexterm" name="id2920970"></a><i class="parameter"><tt>lpq command</tt></i>, 
-<a class="indexterm" name="id2920983"></a><i class="parameter"><tt>lprm command</tt></i>, 
-<a class="indexterm" name="id2920998"></a><i class="parameter"><tt>lppause command</tt></i> or
-<a class="indexterm" name="id2921012"></a><i class="parameter"><tt>lpresume command</tt></i>) are ignored and they should normally have no
+<a class="indexterm" name="id2918490"></a><i class="parameter"><tt>print command</tt></i>, 
+<a class="indexterm" name="id2918504"></a><i class="parameter"><tt>lpq command</tt></i>, 
+<a class="indexterm" name="id2918518"></a><i class="parameter"><tt>lprm command</tt></i>, 
+<a class="indexterm" name="id2918532"></a><i class="parameter"><tt>lppause command</tt></i> or
+<a class="indexterm" name="id2918546"></a><i class="parameter"><tt>lpresume command</tt></i>) are ignored and they should normally have no
 influence what-so-ever on your printing.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921030"></a>Manual Configuration</h3></div></div><div></div></div><p>
-If you want to do things manually, replace the <a class="indexterm" name="id2921040"></a><i class="parameter"><tt>printing</tt></i> = cups
-by <a class="indexterm" name="id2921054"></a><i class="parameter"><tt>printing</tt></i> = bsd. Then your manually set commands may work
-(haven't tested this), and a <a class="indexterm" name="id2921069"></a><i class="parameter"><tt>print command</tt></i> = lp -d %P %s; rm %s"
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918564"></a>Manual Configuration</h3></div></div><div></div></div><p>
+If you want to do things manually, replace the <a class="indexterm" name="id2918574"></a><i class="parameter"><tt>printing</tt></i> = cups
+by <a class="indexterm" name="id2918588"></a><i class="parameter"><tt>printing</tt></i> = bsd. Then your manually set commands may work
+(haven't tested this), and a <a class="indexterm" name="id2918604"></a><i class="parameter"><tt>print command</tt></i> = lp -d %P %s; rm %s"
 may do what you need.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921088"></a>In Case of Trouble.....</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918622"></a>In Case of Trouble.....</h2></div></div><div></div></div><p>
 If you have more problems, post the output of these commands
 to the CUPS or Samba mailing lists (choose the one which seems more
 relevant to your problem):
@@ -10868,7 +10868,7 @@ compact way. Don't forget to name the CUPS and Samba versions you
 are using! This saves bandwidth and makes for easier readability
 for experts (and you are expecting experts to read them, right?
 ;-)
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921154"></a>Printing <span class="emphasis"><em>from</em></span> CUPS to Windows attached
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918682"></a>Printing <span class="emphasis"><em>from</em></span> CUPS to Windows attached
 Printers</h2></div></div><div></div></div><p>
 From time to time the question arises, how you can print
 <span class="emphasis"><em>to</em></span> a Windows attached printer
@@ -10945,22 +10945,22 @@ doesn't require a password! Printing will only work if you have a
 working netbios name resolution up and running. Note that this is a
 feature of CUPS and you don't necessarily need to have smbd running
 (but who wants that? :-).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921434"></a>More CUPS filtering Chains</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2918955"></a>More CUPS filtering Chains</h2></div></div><div></div></div><p>
 The following diagrams reveal how CUPS handles print jobs.
 </p><div class="figure"><a name="cups1"></a><p class="title"><b>Figure�19.17.�Filtering chain 1</b></p><div class="mediaobject"><img src="projdoc/imagefiles/cups1.png" width="270" alt="Filtering chain 1"></div></div><div class="figure"><a name="cups2"></a><p class="title"><b>Figure�19.18.�Filtering chain with cupsomatic</b></p><div class="mediaobject"><img src="projdoc/imagefiles/cups2.png" width="270" alt="Filtering chain with cupsomatic"></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
 CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921535"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921542"></a>Win9x client can't install driver</h3></div></div><div></div></div><p>For Win9x clients require the printer names to be 8
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2796634"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2796642"></a>Win9x client can't install driver</h3></div></div><div></div></div><p>For Win9x clients require the printer names to be 8
 chars (or "8 plus 3 chars suffix") max; otherwise the driver files
 won't get transferred when you want to download them from
-Samba.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921558"></a>"cupsaddsmb" keeps asking for root password in
-			neverending loop</h3></div></div><div></div></div><p>Have you <a class="indexterm" name="id2921569"></a><i class="parameter"><tt>security</tt></i> = user? Have
+Samba.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919061"></a>"cupsaddsmb" keeps asking for root password in
+			neverending loop</h3></div></div><div></div></div><p>Have you <a class="indexterm" name="id2919072"></a><i class="parameter"><tt>security</tt></i> = user? Have
 you used <b class="command">smbpasswd</b> to give root a Samba account?
 You can do 2 things: open another terminal and execute
 <b class="command">smbpasswd -a root</b> to create the account, and
 continue with entering the password into the first terminal. Or break
 out of the loop by hitting ENTER twice (without trying to type a
-password).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921604"></a>"cupsaddsmb" gives "No PPD file for printer..."
+password).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919107"></a>"cupsaddsmb" gives "No PPD file for printer..."
 			message while PPD file is present</h3></div></div><div></div></div><p>Have you enabled printer sharing on CUPS? This means:
 do you have a <i class="parameter"><tt>&lt;Location
 /printers&gt;....&lt;/Location&gt;</tt></i> section in CUPS
@@ -10973,13 +10973,13 @@ an issue if you use cupsaddsmb remotely, or if you use it with a
 "TempDir" directive in
 <span class="emphasis"><em>cupsd.conf</em></span>
 set to a valid value and is it writeable?
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921660"></a>Client can't connect to Samba printer</h3></div></div><div></div></div><p>Use <b class="command">smbstatus</b> to check which user
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919163"></a>Client can't connect to Samba printer</h3></div></div><div></div></div><p>Use <b class="command">smbstatus</b> to check which user
 you are from Samba's point of view. Do you have the privileges to
 write into the <i class="parameter"><tt>[print$]</tt></i>
-share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921688"></a>Can't reconnect to Samba under new account
+share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919497"></a>Can't reconnect to Samba under new account
 			from Win2K/XP</h3></div></div><div></div></div><p>Once you are connected as the "wrong" user (for
 example as "nobody", which often occurs if you have 
-<a class="indexterm" name="id2921701"></a><i class="parameter"><tt>map to guest</tt></i> = bad user), Windows Explorer will not accept an
+<a class="indexterm" name="id2919510"></a><i class="parameter"><tt>map to guest</tt></i> = bad user), Windows Explorer will not accept an
 attempt to connect again as a different user. There won't be any byte
 transfered on the wire to Samba, but still you'll see a stupid error
 message which makes you think that Samba has denied access. Use
@@ -10997,32 +10997,32 @@ with <b class="command">smbstatus</b> that you are connected under a
 different account. Now open the "Printers" folder (on the Samba server
 in the <span class="emphasis"><em>Network Neighbourhood</em></span>), right-click the
 printer in question and select
-<span class="emphasis"><em>Connect...</em></span></p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921914"></a>Avoid being connected to the Samba server as the
+<span class="emphasis"><em>Connect...</em></span></p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919582"></a>Avoid being connected to the Samba server as the
 		"wrong" user</h3></div></div><div></div></div><p>You see per <b class="command">smbstatus</b> that you are
 connected as user "nobody"; while you wanted to be "root" or
 "printeradmin"? This is probably due to 
-<a class="indexterm" name="id2921934"></a><i class="parameter"><tt>map to guest</tt></i> = bad user, which silently connects you under the guest account,
+<a class="indexterm" name="id2919603"></a><i class="parameter"><tt>map to guest</tt></i> = bad user, which silently connects you under the guest account,
 when you gave (maybe by accident) an incorrect username. Remove
-<a class="indexterm" name="id2921951"></a><i class="parameter"><tt>map to guest</tt></i>, if you want to prevent
-this.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921967"></a>Upgrading to CUPS drivers from Adobe drivers on
+<a class="indexterm" name="id2919619"></a><i class="parameter"><tt>map to guest</tt></i>, if you want to prevent
+this.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919635"></a>Upgrading to CUPS drivers from Adobe drivers on
 		NT/2K/XP clients gives problems</h3></div></div><div></div></div><p>First delete all "old" Adobe-using printers. Then
 delete all "old" Adobe drivers. (On Win2K/XP, right-click in
 background of "Printers" folder, select "Server Properties...", select
-tab "Drivers" and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921981"></a>Can't use "cupsaddsmb" on Samba server which is
+tab "Drivers" and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919649"></a>Can't use "cupsaddsmb" on Samba server which is
 		a PDC</h3></div></div><div></div></div><p>Do you use the "naked" root user name? Try to do it
 this way: <b class="userinput"><tt>cupsaddsmb -U <i class="replaceable"><tt>DOMAINNAME</tt></i>\\root -v
 <i class="replaceable"><tt>printername</tt></i></tt></b>&gt; (note the two backslashes: the first one is
-required to "escape" the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922010"></a>Deleted Win2K printer driver is still shown</h3></div></div><div></div></div><p>Deleting a printer on the client won't delete the
+required to "escape" the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919678"></a>Deleted Win2K printer driver is still shown</h3></div></div><div></div></div><p>Deleting a printer on the client won't delete the
 driver too (to verify, right-click on the white background of the
 "Printers" folder, select "Server Properties" and click on the
 "Drivers" tab). These same old drivers will be re-used when you try to
 install a printer with the same name. If you want to update to a new
 driver, delete the old ones first. Deletion is only possible if no
-other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922027"></a>Win2K/XP "Local Security
+other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919695"></a>Win2K/XP "Local Security
 		Policies"</h3></div></div><div></div></div><p><span class="emphasis"><em>Local Security Policies</em></span> may not
 allow the installation of unsigned drivers. "Local Security Policies"
 may not allow the installation of printer drivers at
-all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922043"></a>WinXP clients: "Administrator can not install
+all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919711"></a>WinXP clients: "Administrator can not install
 		printers for all local users"</h3></div></div><div></div></div><p>Windows XP handles SMB printers on a "per-user" basis.
 This means every user needs to install the printer himself. To have a
 printer available for everybody, you might want to use the built-in
@@ -11030,11 +11030,11 @@ IPP client capabilities of WinXP. Add a printer with the print path of
 <span class="emphasis"><em>http://cupsserver:631/printers/printername</em></span>.
 Still looking into this one: maybe a "logon script" could
 automatically install printers for all
-users.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922065"></a>"Print Change Notify" functions on
+users.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919733"></a>"Print Change Notify" functions on
 		NT-clients</h3></div></div><div></div></div><p>For "print change notify" functions on NT++ clients,
 these need to run the "Server" service first (re-named to
 <span class="emphasis"><em>File &amp; Print Sharing for MS Networks</em></span> in
-XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922084"></a>WinXP-SP1</h3></div></div><div></div></div><p>WinXP-SP1 introduced a <span class="emphasis"><em>Point and Print
+XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919752"></a>WinXP-SP1</h3></div></div><div></div></div><p>WinXP-SP1 introduced a <span class="emphasis"><em>Point and Print
 Restriction Policy</em></span> (this restriction doesn't apply to
 "Administrator" or "Power User" groups of users).  In Group Policy
 Object Editor: go to <span class="emphasis"><em>User Configuration,
@@ -11044,7 +11044,7 @@ Printers</em></span>. The policy is automatically set to
 and Print to machines in their Forest</em></span> . You probably need
 to change it to <span class="emphasis"><em>Disabled</em></span> or <span class="emphasis"><em>Users can
 only Point and Print to these servers</em></span> in order to make
-driver downloads from Samba possible.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922126"></a>Print options for all	users can't be set on Win2K/XP</h3></div></div><div></div></div><p>How are you doing it? I bet the wrong way (it is not
+driver downloads from Samba possible.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919794"></a>Print options for all	users can't be set on Win2K/XP</h3></div></div><div></div></div><p>How are you doing it? I bet the wrong way (it is not
 very easy to find out, though). There are 3 different ways to bring
 you to a dialog that <span class="emphasis"><em>seems</em></span> to set everything. All
 three dialogs <span class="emphasis"><em>look</em></span> the same. Only one of them
@@ -11084,12 +11084,12 @@ Do you see any difference? I don't either... However, only the last
 one, which you arrived at with steps "C.1.-6." will save any settings
 permanently and be the defaults for new users. If you want all clients
 to get the same defaults, you need to conduct these steps <span class="emphasis"><em>as
-Administrator</em></span> (<a class="indexterm" name="id2922359"></a><i class="parameter"><tt>printer admin</tt></i> in
+Administrator</em></span> (<a class="indexterm" name="id2920027"></a><i class="parameter"><tt>printer admin</tt></i> in
 <tt class="filename">smb.conf</tt>) <span class="emphasis"><em>before</em></span> a client
 downloads the driver (the clients can later set their own
 <span class="emphasis"><em>per-user defaults</em></span> by following the
 procedures <span class="emphasis"><em>A.</em></span> or <span class="emphasis"><em>B.</em></span>
-above).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922400"></a>Most common blunders in driver
+above).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920067"></a>Most common blunders in driver
 		settings on Windows clients</h3></div></div><div></div></div><p>Don't use <span class="emphasis"><em>Optimize for
 Speed</em></span>: use <span class="emphasis"><em>Optimize for
 Portability</em></span> instead (Adobe PS Driver) Don't use
@@ -11102,7 +11102,7 @@ printer</em></span> (Adobe PS Driver). For
 <span class="emphasis"><em>TrueType Download Options</em></span>
 choose <span class="emphasis"><em>Outline</em></span>. Use PostScript
 Level 2, if you are having trouble with a non-PS printer, and if
-there is a choice.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922445"></a><b class="command">cupsaddsmb</b> does not work
+there is a choice.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920114"></a><b class="command">cupsaddsmb</b> does not work
 		with newly installed printer</h3></div></div><div></div></div><p>Symptom: the last command of
 <b class="command">cupsaddsmb</b> doesn't complete successfully:
 <b class="command">cmd = setdriver printername printername</b> result was
@@ -11112,20 +11112,20 @@ Neighbourhood</em></span>? Did it show up in <b class="command">rpcclient
 hostname -c 'enumprinters'</b>? Restart smbd (or send a
 <b class="command">kill -HUP</b> to all processes listed by
 <b class="command">smbstatus</b> and try
-again.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922506"></a>Permissions on
+again.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920175"></a>Permissions on
 <tt class="filename">/var/spool/samba/</tt> get reset after each
 reboot</h3></div></div><div></div></div><p>Have you by accident set the CUPS spool directory to
 the same location? (<i class="parameter"><tt>RequestRoot
 /var/spool/samba/</tt></i> in <tt class="filename">cupsd.conf</tt> or
 the other way round: <tt class="filename">/var/spool/cups/</tt> is set as
-<a class="indexterm" name="id2922545"></a><i class="parameter"><tt>path</tt></i>&gt; in the <i class="parameter"><tt>[printers]</tt></i>
+<a class="indexterm" name="id2920213"></a><i class="parameter"><tt>path</tt></i>&gt; in the <i class="parameter"><tt>[printers]</tt></i>
 section). These <span class="emphasis"><em>must</em></span> be different. Set
 <i class="parameter"><tt>RequestRoot /var/spool/cups/</tt></i> in
-<tt class="filename">cupsd.conf</tt> and <a class="indexterm" name="id2922584"></a><i class="parameter"><tt>path</tt></i> = 
+<tt class="filename">cupsd.conf</tt> and <a class="indexterm" name="id2920252"></a><i class="parameter"><tt>path</tt></i> = 
 /var/spool/samba in the <i class="parameter"><tt>[printers]</tt></i>
 section of <tt class="filename">smb.conf</tt>. Otherwise cupsd will
 sanitize permissions to its spool directory with each restart, and
-printing will not work reliably.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922615"></a>Printer named "lp"
+printing will not work reliably.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920284"></a>Printer named "lp"
 intermittently swallows jobs and spits out completely different
 ones</h3></div></div><div></div></div><p>It is a very bad idea to name any printer "lp". This
 is the traditional UNIX name for the default printer. CUPS may be set
@@ -11137,28 +11137,28 @@ receive his jobs and send your own to his device unwittingly. To have
 tight control over the printer names, set <i class="parameter"><tt>BrowseShortNames
 No</tt></i>. It will present any printer as "printername@cupshost"
 then, giving you a better control over what may happen in a large
-networked environment.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922646"></a>Location of Adobe PostScript driver files necessary for "cupsaddsmb"</h3></div></div><div></div></div><p>Use <b class="command">smbclient</b> to connect to any
+networked environment.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920314"></a>Location of Adobe PostScript driver files necessary for "cupsaddsmb"</h3></div></div><div></div></div><p>Use <b class="command">smbclient</b> to connect to any
 Windows box with a shared PostScript printer: <b class="command">smbclient
 //windowsbox/print\$ -U guest</b>. You can navigate to the
 <tt class="filename">W32X86/2</tt> subdir to <b class="command">mget ADOBE*</b>
 and other files or to <tt class="filename">WIN40/0</tt> to do the same. --
 Another option is to download the <tt class="filename">*.exe</tt> packaged
-files from the Adobe website.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2922701"></a>An Overview of the CUPS Printing Processes</h2></div></div><div></div></div><div class="figure"><a name="a_small"></a><p class="title"><b>Figure�19.19.�CUPS Printing Overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/a_small.png" width="270" alt="CUPS Printing Overview"></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter�20.�Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="surname">Potter</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Simo</span> <span class="surname">Sorce</span></h3><span class="contrib">original vfs_skel README</span></div></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><span class="contrib">original vfs_netatalk docs</span></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><span class="contrib">Update for multiple modules</span></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2922871">Features and Benefits</a></dt><dt><a href="#id2922889">Discussion</a></dt><dt><a href="#id2923117">Included modules</a></dt><dd><dl><dt><a href="#id2923124">audit</a></dt><dt><a href="#id2923166">extd_audit</a></dt><dt><a href="#id2923296">fake_perms</a></dt><dt><a href="#id2923316">recycle</a></dt><dt><a href="#id2923485">netatalk</a></dt></dl></dd><dt><a href="#id2923530">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2923552">DatabaseFS</a></dt><dt><a href="#id2923606">vscan</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2922871"></a>Features and Benefits</h2></div></div><div></div></div><p>
+files from the Adobe website.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920369"></a>An Overview of the CUPS Printing Processes</h2></div></div><div></div></div><div class="figure"><a name="a_small"></a><p class="title"><b>Figure�19.19.�CUPS Printing Overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/a_small.png" width="270" alt="CUPS Printing Overview"></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter�20.�Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="surname">Potter</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Simo</span> <span class="surname">Sorce</span></h3><span class="contrib">original vfs_skel README</span></div></div><div><div class="author"><h3 class="author"><span class="firstname">Alexander</span> <span class="surname">Bokovoy</span></h3><span class="contrib">original vfs_netatalk docs</span></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stefan</span> <span class="surname">Metzmacher</span></h3><span class="contrib">Update for multiple modules</span></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2920538">Features and Benefits</a></dt><dt><a href="#id2920556">Discussion</a></dt><dt><a href="#id2920786">Included modules</a></dt><dd><dl><dt><a href="#id2920793">audit</a></dt><dt><a href="#id2920835">extd_audit</a></dt><dt><a href="#id2920965">fake_perms</a></dt><dt><a href="#id2920984">recycle</a></dt><dt><a href="#id2921153">netatalk</a></dt></dl></dd><dt><a href="#id2921198">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2921220">DatabaseFS</a></dt><dt><a href="#id2921286">vscan</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920538"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Since Samba-3, there is support for stackable VFS(Virtual File System) modules.  
 Samba passes each request to access the unix file system thru the loaded VFS modules. 
 This chapter covers all the modules that come with the samba source and references to 
 some external modules.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2922889"></a>Discussion</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920556"></a>Discussion</h2></div></div><div></div></div><p>
 If not supplied with your platform distribution binary Samba package you may have problems
 to compile these modules, as shared libraries are compiled and linked in different ways
 on different systems.  They currently have been tested against GNU/Linux and IRIX.
 </p><p>
 To use the VFS modules, create a share similar to the one below.  The
-important parameter is the <a class="indexterm" name="id2922910"></a><i class="parameter"><tt>vfs objects</tt></i> parameter where
+important parameter is the <a class="indexterm" name="id2920577"></a><i class="parameter"><tt>vfs objects</tt></i> parameter where
 you can list one or more VFS modules by name. For example, to log all access 
 to files and put deleted files in a recycle bin:
 
-</p><div class="example"><a name="id2922927"></a><p class="title"><b>Example�20.1.�smb.conf with VFS modules</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[audit]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Audited /data directory</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /data</tt></i></td></tr><tr><td><i class="parameter"><tt>vfs objects = audit recycle</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2920594"></a><p class="title"><b>Example�20.1.�smb.conf with VFS modules</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[audit]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Audited /data directory</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /data</tt></i></td></tr><tr><td><i class="parameter"><tt>vfs objects = audit recycle</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr></table></div><p>
 </p><p>
 The modules are used in the order in which they are specified.
 </p><p>
@@ -11170,25 +11170,25 @@ directory in the root directory of the samba installation (usually
 Some modules can be used twice for the same share.
 This can be done using a configuration similar to the one below.
 
-</p><div class="example"><a name="id2923026"></a><p class="title"><b>Example�20.2.�smb.conf with multiple VFS modules</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[test]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = VFS TEST</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /data</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>vfs objects = example:example1 example example:test</tt></i></td></tr><tr><td><i class="parameter"><tt>example1: parameter = 1</tt></i></td></tr><tr><td><i class="parameter"><tt>example:  parameter = 5</tt></i></td></tr><tr><td><i class="parameter"><tt>test:	  parameter = 7</tt></i></td></tr></table></div><p>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923117"></a>Included modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923124"></a>audit</h3></div></div><div></div></div><p>
+</p><div class="example"><a name="id2920694"></a><p class="title"><b>Example�20.2.�smb.conf with multiple VFS modules</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[test]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = VFS TEST</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /data</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>vfs objects = example:example1 example example:test</tt></i></td></tr><tr><td><i class="parameter"><tt>example1: parameter = 1</tt></i></td></tr><tr><td><i class="parameter"><tt>example:  parameter = 5</tt></i></td></tr><tr><td><i class="parameter"><tt>test:	  parameter = 7</tt></i></td></tr></table></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2920786"></a>Included modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920793"></a>audit</h3></div></div><div></div></div><p>
 		A simple module to audit file access to the syslog
 		facility.  The following operations are logged:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>share</p></li><li><p>connect/disconnect</p></li><li><p>directory opens/create/remove</p></li><li><p>file open/close/rename/unlink/chmod</p></li></ul></div><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923166"></a>extd_audit</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920835"></a>extd_audit</h3></div></div><div></div></div><p>
 		This module is identical with the <span class="emphasis"><em>audit</em></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. 
 		</p><p>
 		The logging information that will be written to the smbd log file is controlled by
-		the <a class="indexterm" name="id2923190"></a><i class="parameter"><tt>log level</tt></i> parameter in <tt class="filename">smb.conf</tt>. The
+		the <a class="indexterm" name="id2920859"></a><i class="parameter"><tt>log level</tt></i> parameter in <tt class="filename">smb.conf</tt>. The
 		following information will be recorded:
-		</p><div class="table"><a name="id2923214"></a><p class="title"><b>Table�20.1.�Extended Auditing Log Information</b></p><table summary="Extended Auditing Log Information" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Log Level</th><th align="center">Log Details - File and Directory Operations</th></tr></thead><tbody><tr><td align="center">0</td><td align="left">Creation / Deletion</td></tr><tr><td align="center">1</td><td align="left">Create / Delete / Rename / Permission Changes</td></tr><tr><td align="center">2</td><td align="left">Create / Delete / Rename / Perm Change / Open / Close</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923296"></a>fake_perms</h3></div></div><div></div></div><p>
+		</p><div class="table"><a name="id2920882"></a><p class="title"><b>Table�20.1.�Extended Auditing Log Information</b></p><table summary="Extended Auditing Log Information" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Log Level</th><th align="center">Log Details - File and Directory Operations</th></tr></thead><tbody><tr><td align="center">0</td><td align="left">Creation / Deletion</td></tr><tr><td align="center">1</td><td align="left">Create / Delete / Rename / Permission Changes</td></tr><tr><td align="center">2</td><td align="left">Create / Delete / Rename / Perm Change / Open / Close</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920965"></a>fake_perms</h3></div></div><div></div></div><p>
 		This module was created to allow Roaming Profile files and directories to be set (on the Samba server
 		under Unix) as read only. This module will if installed on the Profiles share will report to the client
 		that the Profile files and directories are writable. This satisfies the client even though the files
 		will never be overwritten as the client logs out or shuts down.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923316"></a>recycle</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920984"></a>recycle</h3></div></div><div></div></div><p>
 		A recycle-bin like module. When used any unlink call
 		will be intercepted and files moved to the recycle
 		directory instead of being deleted. This gives the same 
@@ -11210,12 +11210,12 @@ This can be done using a configuration similar to the one below.
 					these directories are deleted, they are not put into the 
 					recycle bin, but deleted in the regular way. 
 			</p></dd><dt><span class="term">recycle:noversions</span></dt><dd><p>Opposite of <i class="parameter"><tt>recycle:versions</tt></i>. If both options are specified, this one takes precedence.</p></dd></dl></div><p>
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923485"></a>netatalk</h3></div></div><div></div></div><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921153"></a>netatalk</h3></div></div><div></div></div><p>
 		A netatalk module, that will ease co-existence of samba and
 		netatalk file sharing services.
 		</p><p>Advantages compared to the old netatalk module:
 		</p><div class="itemizedlist"><ul type="disc"><li><p>it doesn't care about creating of .AppleDouble forks, just keeps them in sync</p></li><li><p>if a share in <tt class="filename">smb.conf</tt> doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</p></li></ul></div><p>
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923530"></a>VFS modules available elsewhere</h2></div></div><div></div></div><p>
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921198"></a>VFS modules available elsewhere</h2></div></div><div></div></div><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 or another (e.g. it is easy for the maintainer 
@@ -11223,7 +11223,7 @@ to have his or her own CVS tree).
 </p><p>
 No statements about the stability or functionality of any module
 should be implied due to its presence here.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923552"></a>DatabaseFS</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921220"></a>DatabaseFS</h3></div></div><div></div></div><p>
 		URL: <a href="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" target="_top">http://www.css.tayloru.edu/~elorimer/databasefs/index.php</a>
 		</p><p>By <a href="mailto:elorimer@css.tayloru.edu" target="_top">Eric Lorimer</a>.</p><p>
 		I have created a VFS module which implements a fairly complete read-only
@@ -11238,13 +11238,13 @@ should be implied due to its presence here.
 		Any feedback would be appreciated: comments, suggestions, patches,
 		etc...  If nothing else, hopefully it might prove useful for someone
 		else who wishes to create a virtual filesystem.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923606"></a>vscan</h3></div></div><div></div></div><p>URL: <a href="http://www.openantivirus.org/" target="_top">http://www.openantivirus.org/</a></p><p>
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921286"></a>vscan</h3></div></div><div></div></div><p>URL: <a href="http://www.openantivirus.org/" target="_top">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 course, 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" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter�21.�Winbind: Use of Domain Accounts</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div><p class="pubdate">27 June 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2923836">Features and Benefits</a></dt><dt><a href="#id2923931">Introduction</a></dt><dt><a href="#id2924016">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2924076">Target Uses</a></dt></dl></dd><dt><a href="#id2924107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2924136">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2924169">Microsoft Active Directory Services</a></dt><dt><a href="#id2924192">Name Service Switch</a></dt><dt><a href="#id2924320">Pluggable Authentication Modules</a></dt><dt><a href="#id2924402">User and Group ID Allocation</a></dt><dt><a href="#id2924435">Result Caching</a></dt></dl></dd><dt><a href="#id2924463">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2924471">Introduction</a></dt><dt><a href="#id2924538">Requirements</a></dt><dt><a href="#id2924632">Testing Things Out</a></dt></dl></dd><dt><a href="#id2926199">Conclusion</a></dt><dt><a href="#id2926218">Common Errors</a></dt><dd><dl><dt><a href="#id2926270">NSCD Problem Warning</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923836"></a>Features and Benefits</h2></div></div><div></div></div><p>
+		</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter�21.�Winbind: Use of Domain Accounts</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div><p class="pubdate">27 June 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2921516">Features and Benefits</a></dt><dt><a href="#id2921611">Introduction</a></dt><dt><a href="#id2921688">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2921756">Target Uses</a></dt></dl></dd><dt><a href="#id2921786">How Winbind Works</a></dt><dd><dl><dt><a href="#id2921815">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2921849">Microsoft Active Directory Services</a></dt><dt><a href="#id2921872">Name Service Switch</a></dt><dt><a href="#id2922009">Pluggable Authentication Modules</a></dt><dt><a href="#id2922081">User and Group ID Allocation</a></dt><dt><a href="#id2922128">Result Caching</a></dt></dl></dd><dt><a href="#id2922156">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2922164">Introduction</a></dt><dt><a href="#id2922231">Requirements</a></dt><dt><a href="#id2922333">Testing Things Out</a></dt></dl></dd><dt><a href="#id2923890">Conclusion</a></dt><dt><a href="#id2923909">Common Errors</a></dt><dd><dl><dt><a href="#id2923962">NSCD Problem Warning</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921516"></a>Features and Benefits</h2></div></div><div></div></div><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.
@@ -11278,7 +11278,7 @@ should be implied due to its presence here.
 	If winbindd is not running, then smbd (which calls winbindd) will fall back to
 	using purely local information from /etc/passwd and /etc/group and no dynamic
 	mapping will be used.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923931"></a>Introduction</h2></div></div><div></div></div><p>It is well known that UNIX and Microsoft Windows NT have 
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921611"></a>Introduction</h2></div></div><div></div></div><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 
@@ -11299,7 +11299,7 @@ should be implied due to its presence here.
 	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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924016"></a>What Winbind Provides</h2></div></div><div></div></div><p>Winbind unifies UNIX and Windows NT account management by 
+	problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921688"></a>What Winbind Provides</h2></div></div><div></div></div><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 
@@ -11323,7 +11323,7 @@ should be implied due to its presence here.
 	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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924076"></a>Target Uses</h3></div></div><div></div></div><p>Winbind is targeted at organizations that have an 
+	location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921756"></a>Target Uses</h3></div></div><div></div></div><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 
@@ -11333,12 +11333,12 @@ should be implied due to its presence here.
 		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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924107"></a>How Winbind Works</h2></div></div><div></div></div><p>The winbind system is designed around a client/server 
+		the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921786"></a>How Winbind Works</h2></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924136"></a>Microsoft Remote Procedure Calls</h3></div></div><div></div></div><p>Over the last few years, efforts have been underway 
+	in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921815"></a>Microsoft Remote Procedure Calls</h3></div></div><div></div></div><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 
@@ -11351,7 +11351,7 @@ should be implied due to its presence here.
 		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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924169"></a>Microsoft Active Directory Services</h3></div></div><div></div></div><p>
+		NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921849"></a>Microsoft Active Directory Services</h3></div></div><div></div></div><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.
@@ -11360,7 +11360,7 @@ should be implied due to its presence here.
                 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924192"></a>Name Service Switch</h3></div></div><div></div></div><p>The Name Service Switch, or NSS, is a feature that is 
+                </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921872"></a>Name Service Switch</h3></div></div><div></div></div><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 
@@ -11397,7 +11397,7 @@ passwd: files example
 		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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924320"></a>Pluggable Authentication Modules</h3></div></div><div></div></div><p>Pluggable Authentication Modules, also known as PAM, 
+		resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922009"></a>Pluggable Authentication Modules</h3></div></div><div></div></div><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 
@@ -11422,7 +11422,7 @@ passwd: files example
 		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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924402"></a>User and Group ID Allocation</h3></div></div><div></div></div><p>When a user or group is created under Windows NT 
+		for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922081"></a>User and Group ID Allocation</h3></div></div><div></div></div><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 
@@ -11435,7 +11435,7 @@ passwd: files example
 		time, winbind will have mapped all Windows NT users and groups
 		to UNIX user ids and group ids.</p><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924435"></a>Result Caching</h3></div></div><div></div></div><p>An active system can generate a lot of user and group 
+		RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922128"></a>Result Caching</h3></div></div><div></div></div><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 
@@ -11446,7 +11446,7 @@ passwd: files example
 		the PDC and compared against the sequence number of the cached entry. 
 		If the sequence numbers do not match, then the cached information 
 		is discarded and up to date information is requested directly 
-		from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924463"></a>Installation and Configuration</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924471"></a>Introduction</h3></div></div><div></div></div><p>
+		from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2922156"></a>Installation and Configuration</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922164"></a>Introduction</h3></div></div><div></div></div><p>
 This section describes the procedures used to get winbind up and 
 running.  Winbind is capable of providing access 
 and authentication control for Windows Domain users through an NT 
@@ -11467,7 +11467,7 @@ well for SAMBA services.
 	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></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924538"></a>Requirements</h3></div></div><div></div></div><p>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922231"></a>Requirements</h3></div></div><div></div></div><p>
 If you have a Samba configuration file that you are currently 
 using... <span class="emphasis"><em>BACK IT UP!</em></span>  If your system already uses PAM, 
 <span class="emphasis"><em>back up the <tt class="filename">/etc/pam.d</tt> directory 
@@ -11494,7 +11494,7 @@ 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924632"></a>Testing Things Out</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922333"></a>Testing Things Out</h3></div></div><div></div></div><p>
 Before starting, it is probably best to kill off all the SAMBA 
 related daemons running on your server.  Kill off all <span class="application">smbd</span>, 
 <span class="application">nmbd</span>, and <span class="application">winbindd</span> processes that may 
@@ -11505,7 +11505,7 @@ 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. 
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2924694"></a>Configure <tt class="filename">nsswitch.conf</tt> and the 
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922395"></a>Configure <tt class="filename">nsswitch.conf</tt> and the 
 winbind libraries on Linux and Solaris</h4></div></div><div></div></div><p>
 The libraries needed to run the <span class="application">winbindd</span> daemon 
 through nsswitch need to be copied to their proper locations, so
@@ -11540,7 +11540,7 @@ is faster (and you don't need to reboot) if you do it manually:
 </p><p>
 This makes <tt class="filename">libnss_winbind</tt> available to winbindd 
 and echos back a check to you.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2924902"></a>NSS Winbind on AIX</h4></div></div><div></div></div><p>(This section is only for those running AIX)</p><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922602"></a>NSS Winbind on AIX</h4></div></div><div></div></div><p>(This section is only for those running AIX)</p><p>
 The winbind AIX identification module gets built as libnss_winbind.so in the
 nsswitch directory of the samba source.  This file can be copied to
 /usr/lib/security, and the AIX naming convention would indicate that it
@@ -11560,14 +11560,14 @@ Programming Concepts for AIX": <a href="http://publibn.boulder.ibm.com/doc_link/
 Chapter 18. Loadable Authentication Module Programming Interface</a> 
 and more information on administering the  modules at <a href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm" target="_top">
 "System Management Guide: Operating System and Devices"</a>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2924974"></a>Configure smb.conf</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922674"></a>Configure smb.conf</h4></div></div><div></div></div><p>
 Several parameters are needed in the smb.conf file to control 
 the behavior of <span class="application">winbindd</span>. Configure 
 <tt class="filename">smb.conf</tt> These are described in more detail in 
 the <a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> man page.  My 
 <tt class="filename">smb.conf</tt> file was modified to
 include the following entries in the [global] section:
-</p><div class="example"><a name="id2925020"></a><p class="title"><b>Example�21.1.�smb.conf for winbind set-up</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td>...</td></tr><tr><td>#  separate domain and username with '+', like DOMAIN+username</td></tr><tr><td><i class="parameter"><tt>winbind separator = +</tt></i></td></tr><tr><td>#  use uids from 10000 to 20000 for domain users</td></tr><tr><td><i class="parameter"><tt>idmap uid = 10000-20000</tt></i></td></tr><tr><td>#  use gids from 10000 to 20000 for domain groups</td></tr><tr><td><i class="parameter"><tt>winbind gid = 10000-20000</tt></i></td></tr><tr><td>#  allow enumeration of winbind users and groups</td></tr><tr><td><i class="parameter"><tt>winbind enum users = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>winbind enum groups = yes</tt></i></td></tr><tr><td>#  give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><i class="parameter"><tt>template homedir = /home/winnt/%D/%U</tt></i></td></tr><tr><td><i class="parameter"><tt>template shell = /bin/bash</tt></i></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925132"></a>Join the SAMBA server to the PDC domain</h4></div></div><div></div></div><p>
+</p><div class="example"><a name="id2922722"></a><p class="title"><b>Example�21.1.�smb.conf for winbind set-up</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td>...</td></tr><tr><td>#  separate domain and username with '+', like DOMAIN+username</td></tr><tr><td><i class="parameter"><tt>winbind separator = +</tt></i></td></tr><tr><td>#  use uids from 10000 to 20000 for domain users</td></tr><tr><td><i class="parameter"><tt>idmap uid = 10000-20000</tt></i></td></tr><tr><td>#  use gids from 10000 to 20000 for domain groups</td></tr><tr><td><i class="parameter"><tt>winbind gid = 10000-20000</tt></i></td></tr><tr><td>#  allow enumeration of winbind users and groups</td></tr><tr><td><i class="parameter"><tt>winbind enum users = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>winbind enum groups = yes</tt></i></td></tr><tr><td>#  give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><i class="parameter"><tt>template homedir = /home/winnt/%D/%U</tt></i></td></tr><tr><td><i class="parameter"><tt>template shell = /bin/bash</tt></i></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922833"></a>Join the SAMBA server to the PDC domain</h4></div></div><div></div></div><p>
 Enter the following command to make the SAMBA server join the 
 PDC domain, where <i class="replaceable"><tt>DOMAIN</tt></i> is the name of 
 your Windows domain and <i class="replaceable"><tt>Administrator</tt></i> is 
@@ -11578,7 +11578,7 @@ a domain user who has administrative privileges in the domain.
 The proper response to the command should be: "Joined the domain 
 <i class="replaceable"><tt>DOMAIN</tt></i>" where <i class="replaceable"><tt>DOMAIN</tt></i> 
 is your DOMAIN name.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925188"></a>Start up the winbindd daemon and test it!</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922889"></a>Start up the winbindd daemon and test it!</h4></div></div><div></div></div><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
@@ -11620,7 +11620,7 @@ your PDC.  For example, I get the following response:
 	CEO+krbtgt
 	CEO+TsInternetUser
 </pre><p>
-	Obviously, I have named my domain 'CEO' and my <a class="indexterm" name="id2925332"></a><i class="parameter"><tt>winbind separator</tt></i> is '+'.
+	Obviously, I have named my domain 'CEO' and my <a class="indexterm" name="id2923034"></a><i class="parameter"><tt>winbind separator</tt></i> is '+'.
 </p><p>
 You can do the same sort of thing to get group information from 
 the PDC:
@@ -11649,7 +11649,7 @@ directories and default shells.
 The same thing can be done for groups with the command
 </p><p>
 <tt class="prompt">root# </tt><b class="userinput"><tt>getent group</tt></b>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925436"></a>Fix the init.d startup scripts</h4></div></div><div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2925443"></a>Linux</h5></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923138"></a>Fix the init.d startup scripts</h4></div></div><div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2923145"></a>Linux</h5></div></div><div></div></div><p>
 The <span class="application">winbindd</span> daemon needs to start up after the 
 <span class="application">smbd</span> and <span class="application">nmbd</span> daemons are running.  
 To accomplish this task, you need to modify the startup scripts of your system.
@@ -11715,7 +11715,7 @@ stop() {
         echo ""
         return $RETVAL
 }
-</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2925606"></a>Solaris</h5></div></div><div></div></div><p>Winbind doesn't work on Solaris 9, see the <a href="#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><p>On Solaris, you need to modify the 
+</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2923308"></a>Solaris</h5></div></div><div></div></div><p>Winbind doesn't work on Solaris 9, see the <a href="#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><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>, 
@@ -11778,11 +11778,11 @@ in the script above with:
 </p><pre class="programlisting">
 	/usr/local/samba/bin/winbindd -B
 </pre><p>
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2925716"></a>Restarting</h5></div></div><div></div></div><p>
+</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2923426"></a>Restarting</h5></div></div><div></div></div><p>
 If you restart the <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> 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" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925753"></a>Configure Winbind and PAM</h4></div></div><div></div></div><p>
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923462"></a>Configure Winbind and PAM</h4></div></div><div></div></div><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
@@ -11802,7 +11802,7 @@ your other pam security modules.  On my RedHat system, this was the
 modules reside in <tt class="filename">/usr/lib/security</tt>.
 </p><p>
 <tt class="prompt">root# </tt><b class="userinput"><tt>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</tt></b>
-</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2925859"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><div></div></div><p>
+</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2923568"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><div></div></div><p>
 The <tt class="filename">/etc/pam.d/samba</tt> file does not need to be changed. I 
 just left this file as it was:
 </p><pre class="programlisting">
@@ -11829,7 +11829,7 @@ have individual directories for the domain users already present on
 the server, or change the home directory template to a general
 directory for all domain users.  These can be easily set using 
 the <tt class="filename">smb.conf</tt> global entry 
-<a class="indexterm" name="id2925966"></a><i class="parameter"><tt>template homedir</tt></i>.
+<a class="indexterm" name="id2923675"></a><i class="parameter"><tt>template homedir</tt></i>.
 </p><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
@@ -11865,7 +11865,7 @@ above it, to disallow root logins over the network.  I also added a
 </p><pre class="programlisting">sufficient /lib/security/pam_unix.so use_first_pass</pre><p>
 line after the <b class="command">winbind.so</b> line to get rid of annoying 
 double prompts for passwords.
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2926090"></a>Solaris-specific configuration</h5></div></div><div></div></div><p>
+</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2923800"></a>Solaris-specific configuration</h5></div></div><div></div></div><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
@@ -11937,12 +11937,12 @@ 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926199"></a>Conclusion</h2></div></div><div></div></div><p>The winbind system, through the use of the Name Service 
+</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923890"></a>Conclusion</h2></div></div><div></div></div><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 class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926218"></a>Common Errors</h2></div></div><div></div></div><p>Winbind has a number of limitations in its current 
+	cost of running a mixed UNIX and NT network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923909"></a>Common Errors</h2></div></div><div></div></div><p>Winbind has a number of limitations in its current 
 	released version that we hope to overcome in future 
 	releases:</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind is currently only available for 
 		the Linux, Solaris, AIX and IRIX operating systems, although ports to other operating 
@@ -11957,18 +11957,18 @@ configured in the pam.conf.
 		containing this information is corrupted or destroyed.</p></li><li><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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926270"></a>NSCD Problem Warning</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+		instead up to the PDC to enforce.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923962"></a>NSCD Problem Warning</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 	Do NOT under ANY circumstances run <b class="command">nscd</b> on any system
 	on which <b class="command">winbind</b> is running.
 	</p></div><p>
 	If <b class="command">nscd</b> is running on the UNIX/Linux system, then
 	even though NSSWITCH is correctly configured it will NOT be possible to resolve
 	domain users and groups for file and directory controls.
-	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter�22.�Advanced Network Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2926379">Features and Benefits</a></dt><dt><a href="#id2926410">Remote Server Administration</a></dt><dt><a href="#id2926508">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2926526">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2926738">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2927010">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2927044">Common Errors</a></dt></dl></div><p>
+	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter�22.�Advanced Network Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2924071">Features and Benefits</a></dt><dt><a href="#id2924101">Remote Server Administration</a></dt><dt><a href="#id2924200">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2924218">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2924438">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2924711">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2924744">Common Errors</a></dt></dl></div><p>
 This section documents peripheral issues that are of great importance to network
 administrators who want to improve network resource access control, to automate the user
 environment, and to make their lives a little easier.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926379"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924071"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Often the difference between a working network environment and a well appreciated one can
 best be measured by the <span class="emphasis"><em>little things</em></span> that makes everything work more
 harmoniously. A key part of every network environment solution is the ability to remotely
@@ -11978,7 +11978,7 @@ network operations.
 </p><p>
 This chapter presents information on each of these area. They are placed here, and not in
 other chapters, for ease of reference.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926410"></a>Remote Server Administration</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924101"></a>Remote Server Administration</h2></div></div><div></div></div><p>
 <span class="emphasis"><em>How do I get 'User Manager' and 'Server Manager'?</em></span>
 </p><p>
 	Since I don't need to buy an <span class="application">NT4 Server</span>, how do I get the 'User Manager for Domains',
@@ -11992,12 +11992,12 @@ Click here to download the archived file <a href="ftp://ftp.microsoft.com/Softli
 The <span class="application">Windows NT 4.0</span> 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926508"></a>Remote Desktop Management</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924200"></a>Remote Desktop Management</h2></div></div><div></div></div><p>
 There are a number of possible remote desktop management solutions that range from free
 through costly. Do not let that put you off. Sometimes the most costly solutions is the
 most cost effective. In any case, you will need to draw your own conclusions as to which
 is the best tool in your network environment.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926526"></a>Remote Management from NoMachines.Com</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924218"></a>Remote Management from NoMachines.Com</h3></div></div><div></div></div><p>
 	The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003.
 	It is presented in slightly edited form (with author details omitted for privacy reasons).
 	The entire answer is reproduced below with some comments removed.
@@ -12085,7 +12085,7 @@ is the best tool in your network environment.
 		NoMachine are encouraging and offering help to OSS/Free Software implementations
 		for such a frontend too, even if it means competition to them (they have written
 		to this effect even to the LTSP, KDE and GNOME developer mailing lists)
-		</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926738"></a>Network Logon Script Magic</h2></div></div><div></div></div><p>
+		</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924438"></a>Network Logon Script Magic</h2></div></div><div></div></div><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>
@@ -12175,7 +12175,7 @@ This is the <tt class="filename">genlogon.pl</tt> file:
 </pre><p>
 </p><p>
 Those wishing to use more elaborate or capable logon processing system should check out the following sites:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></td></tr><tr><td><a href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></td></tr><tr><td><a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.asp?scid=kb;en-us;189105</a></td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927010"></a>Adding printers without user intervention</h3></div></div><div></div></div><p>
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></td></tr><tr><td><a href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></td></tr><tr><td><a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.asp?scid=kb;en-us;189105</a></td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924711"></a>Adding printers without user intervention</h3></div></div><div></div></div><p>
 Printers may be added automatically during logon script processing through the use of:
 
 </p><pre class="programlisting">
@@ -12183,17 +12183,17 @@ Printers may be added automatically during logon script processing through the u
 </pre><p>
 
 See the documentation in the <a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">Microsoft knowledgebase article no: 189105</a>.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927044"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924744"></a>Common Errors</h2></div></div><div></div></div><p>
 The information provided in this chapter has been reproduced from postings on the samba@samba.org
 mailing list. No implied endorsement or recommendation is offered. Administrators should conduct 
 their own evaluation of alternatives and are encouraged to draw their own conclusions.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter�23.�System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2927123">Features and Benefits</a></dt><dt><a href="#id2927177">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2927288">Windows 9x/Me Policies</a></dt><dt><a href="#id2927384">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2927516">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2927780">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2927886">Samba Editreg Toolset</a></dt><dt><a href="#id2927925">Windows NT4/200x</a></dt><dt><a href="#id2927945">Samba PDC</a></dt></dl></dd><dt><a href="#id2927990">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2928140">Common Errors</a></dt><dd><dl><dt><a href="#id2928154">Policy Does Not Work</a></dt></dl></dd></dl></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter�23.�System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2924822">Features and Benefits</a></dt><dt><a href="#id2924888">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2924999">Windows 9x/Me Policies</a></dt><dt><a href="#id2925094">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2925227">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2925491">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2925596">Samba Editreg Toolset</a></dt><dt><a href="#id2925636">Windows NT4/200x</a></dt><dt><a href="#id2925655">Samba PDC</a></dt></dl></dd><dt><a href="#id2925700">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2925851">Common Errors</a></dt><dd><dl><dt><a href="#id2925865">Policy Does Not Work</a></dt></dl></dd></dl></div><p>
 This chapter summarises the current state of knowledge derived from personal
 practice and knowledge from samba mailing list subscribers. Before reproduction
 of posted information effort has been made to validate the information provided.
 Where additional information was uncovered through this validation it is provided
 also.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927123"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924822"></a>Features and Benefits</h2></div></div><div></div></div><p>
 When MS Windows NT3.5 was introduced the hot new topic was the ability to implement
 Group Policies for users and group. Then along came MS Windows NT4 and a few sites
 started to adopt this capability. How do we know that? By way of the number of "booboos"
@@ -12214,7 +12214,7 @@ network client workstations.
 </p><p>
 A tool new to Samba may become an important part of the future Samba Administrators'
 arsenal. The <b class="command">editreg</b> tool is described in this document.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927177"></a>Creating and Managing System Policies</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924888"></a>Creating and Managing System Policies</h2></div></div><div></div></div><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
@@ -12249,7 +12249,7 @@ be read and understood. Try searching on the Microsoft web site for "Group Polic
 </p><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927288"></a>Windows 9x/Me Policies</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924999"></a>Windows 9x/Me Policies</h3></div></div><div></div></div><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
@@ -12275,7 +12275,7 @@ here is incomplete - you are warned.
 	<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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927384"></a>Windows NT4 Style Policy Files</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925094"></a>Windows NT4 Style Policy Files</h3></div></div><div></div></div><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"><em>not NT Workstation</em></span>. There is a Policy Editor on a NT4
@@ -12296,14 +12296,14 @@ here is incomplete - you are warned.
 	be extracted as well.  It is also possible to downloaded the policy template
 	files for Office97 and get a copy of the policy editor.  Another possible
 	location is with the Zero Administration Kit available for download from Microsoft.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2927493"></a>Registry Spoiling</h4></div></div><div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925205"></a>Registry Spoiling</h4></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927516"></a>MS Windows 200x / XP Professional Policies</h3></div></div><div></div></div><p>
+			</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925227"></a>MS Windows 200x / XP Professional Policies</h3></div></div><div></div></div><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.
@@ -12340,7 +12340,7 @@ here is incomplete - you are warned.
 	to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows
 	the administrator to also set filters over the policy settings. No such equivalent capability
 	exists with NT4 style policy files.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2927629"></a>Administration of Win2K / XP Policies</h4></div></div><div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2925328"></a>Administration of Win2K / XP Policies</h4></div></div><div></div></div><p>
 		Instead of using the tool called <span class="application">The System Policy Editor</span>, commonly called Poledit (from the
 		executable name <b class="command">poledit.exe</b>), <span class="acronym">GPOs</span> are created and managed using a 
 		<span class="application">Microsoft Management Console</span> <span class="acronym">(MMC)</span> snap-in as follows:</p><div class="procedure"><ol type="1"><li><p>
@@ -12366,7 +12366,7 @@ here is incomplete - you are warned.
 		The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
 		to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
 		use this powerful tool. Please refer to the resource kit manuals for specific usage information.
-		</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927780"></a>Managing Account/User Policies</h2></div></div><div></div></div><p>
+		</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2925491"></a>Managing Account/User Policies</h2></div></div><div></div></div><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 necessary.
@@ -12393,7 +12393,7 @@ MS Windows NT4/200x/XP allows per domain as well as per user account restriction
 Common restrictions that are frequently used includes:
 </p><p>
 </p><div class="itemizedlist"><ul type="disc"><li><p>Logon Hours</p></li><li><p>Password Aging</p></li><li><p>Permitted Logon from certain machines only</p></li><li><p>Account type (Local or Global)</p></li><li><p>User Rights</p></li></ul></div><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927886"></a>Samba Editreg Toolset</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925596"></a>Samba Editreg Toolset</h3></div></div><div></div></div><p>
 	A new tool called <b class="command">editreg</b> is under development. This tool can be used
 	to edit registry files (called NTUser.DAT) that are stored in user and group profiles.
 	NTConfig.POL files have the same structure as the NTUser.DAT file and can be editted using
@@ -12402,17 +12402,17 @@ Common restrictions that are frequently used includes:
 	extended capabilities. It is proving difficult to realise this capability, so do not be surprised
 	if this feature does not materialise. Formal capabilities will be announced at the time that
 	this tool is released for production use.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927925"></a>Windows NT4/200x</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925636"></a>Windows NT4/200x</h3></div></div><div></div></div><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 Management Console (MMC) with appropriate
 	"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927945"></a>Samba PDC</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925655"></a>Samba PDC</h3></div></div><div></div></div><p>
 	With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
 	<b class="command">smbpasswd</b>, <b class="command">pdbedit</b>, <b class="command">net</b>, <b class="command">rpcclient</b>. 
 	The administrator should read the
 	man pages for these tools and become familiar with their use.
-	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927990"></a>System Startup and Logon Processing Overview</h2></div></div><div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2925700"></a>System Startup and Logon Processing Overview</h2></div></div><div></div></div><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><div class="orderedlist"><ol type="1"><li><p>
@@ -12442,10 +12442,10 @@ reboot and as part of the user logon:
 	</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="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928140"></a>Common Errors</h2></div></div><div></div></div><p>
+	</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2925851"></a>Common Errors</h2></div></div><div></div></div><p>
 Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following
 collection demonstrates only basic issues.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928154"></a>Policy Does Not Work</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925865"></a>Policy Does Not Work</h3></div></div><div></div></div><p>
 	&#8220;<span class="quote">We have created the <tt class="filename">config.pol</tt> file and put it in the <span class="emphasis"><em>NETLOGON</em></span> share.
 It has made no difference to our Win XP Pro machines, they just don't see it. IT worked fine with Win 98 but does not
 work any longer since we upgraded to Win XP Pro. Any hints?</span>&#8221;
@@ -12453,7 +12453,7 @@ work any longer since we upgraded to Win XP Pro. Any hints?</span>&#8221;
 Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based
 platforms. You need to use the NT4 Group Policy Editor to create a file called <tt class="filename">NTConfig.POL</tt> so that
 it is in the correct format for your MS Windows XP Pro clients.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�24.�Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2928255">Features and Benefits</a></dt><dt><a href="#id2928289">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2928330">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2928820">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2930060">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2930144">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2930397">Mandatory profiles</a></dt><dt><a href="#id2930455">Creating/Managing Group Profiles</a></dt><dt><a href="#id2930500">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2930520">MS Windows 9x/Me</a></dt><dt><a href="#id2930668">MS Windows NT4 Workstation</a></dt><dt><a href="#id2931222">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2931730">Common Errors</a></dt><dd><dl><dt><a href="#id2931743">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2931812">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2932026">Changing the default profile</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928255"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�24.�Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2925964">Features and Benefits</a></dt><dt><a href="#id2925999">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2926040">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2926530">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2927776">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2927861">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2928114">Mandatory profiles</a></dt><dt><a href="#id2928172">Creating/Managing Group Profiles</a></dt><dt><a href="#id2928216">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2928237">MS Windows 9x/Me</a></dt><dt><a href="#id2928385">MS Windows NT4 Workstation</a></dt><dt><a href="#id2928939">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2929447">Common Errors</a></dt><dd><dl><dt><a href="#id2929460">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2929529">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2929742">Changing the default profile</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2925964"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for
 some administrators.
 </p><p>
@@ -12466,7 +12466,7 @@ problem to others. In particular, users of mobile computing tools, where often t
 be a sustained network connection, are often better served by purely Local Profiles.
 This chapter provides information to help the Samba administrator to deal with those
 situations also.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928289"></a>Roaming Profiles</h2></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2925999"></a>Roaming Profiles</h2></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
 Roaming profiles support is different for Win9x / Me and Windows NT4/200x.
 </p></div><p>
 Before discussing how to configure roaming profiles, it is useful to see how
@@ -12479,9 +12479,9 @@ 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928330"></a>Samba Configuration for Profile Handling</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926040"></a>Samba Configuration for Profile Handling</h3></div></div><div></div></div><p>
 This section documents how to configure Samba for MS Windows client profile support.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928342"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2926053"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p>
 To support Windows NT4/200x clients, in the [global] section of smb.conf set the
 following (for example):
 </p><p>
@@ -12502,8 +12502,8 @@ semantics of %L and %N, as well as %U and %u.
 MS Windows NT/2K clients at times do not disconnect a connection to a server
 between logons. It is recommended to NOT use the <i class="parameter"><tt>homes</tt></i>
 meta-service name as part of the profile share path.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928450"></a>Windows 9x / Me User Profiles</h4></div></div><div></div></div><p>
-	To support Windows 9x / Me clients, you must use the <a class="indexterm" name="id2928462"></a><i class="parameter"><tt>logon home</tt></i> parameter. Samba has
+</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2926161"></a>Windows 9x / Me User Profiles</h4></div></div><div></div></div><p>
+	To support Windows 9x / Me clients, you must use the <a class="indexterm" name="id2926173"></a><i class="parameter"><tt>logon home</tt></i> parameter. Samba has
 now been fixed so that <b class="userinput"><tt>net use /home</tt></b> now works as well, and it, too, relies
 on the <b class="command">logon home</b> parameter.
 </p><p>
@@ -12517,11 +12517,11 @@ of your home directory called <tt class="filename">.profiles</tt> (thus making t
 Not only that, but <b class="userinput"><tt>net use /home</tt></b> 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 <tt class="filename">\\%L\%U</tt> for <a class="indexterm" name="id2928566"></a><i class="parameter"><tt>logon home</tt></i>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928582"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p>
+specified <tt class="filename">\\%L\%U</tt> for <a class="indexterm" name="id2926277"></a><i class="parameter"><tt>logon home</tt></i>.
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2926293"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p>
 You can support profiles for both Win9X and WinNT clients by setting both the
-<a class="indexterm" name="id2928594"></a><i class="parameter"><tt>logon home</tt></i> and <a class="indexterm" name="id2928608"></a><i class="parameter"><tt>logon path</tt></i> parameters. For example:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon home = \\%L\%u\.profiles</tt></i></td></tr><tr><td><i class="parameter"><tt>logon path = \\%L\profiles\%u</tt></i></td></tr></table></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928649"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p>
+<a class="indexterm" name="id2926306"></a><i class="parameter"><tt>logon home</tt></i> and <a class="indexterm" name="id2926319"></a><i class="parameter"><tt>logon path</tt></i> parameters. For example:
+</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon home = \\%L\%u\.profiles</tt></i></td></tr><tr><td><i class="parameter"><tt>logon path = \\%L\profiles\%u</tt></i></td></tr></table></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2926360"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p>
 	A question often asked is &#8220;<span class="quote">How may I enforce use of local profiles?</span>&#8221; or
 	&#8220;<span class="quote">How do I disable Roaming Profiles?</span>&#8221;
 </p><p>
@@ -12556,15 +12556,15 @@ profiles.
 The specifics of how to convert a local profile to a roaming profile, or a roaming profile
 to a local one vary according to the version of MS Windows you are running. Consult the
 Microsoft MS Windows Resource Kit for your version of Windows for specific information.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928820"></a>Windows Client Profile Configuration Information</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928828"></a>Windows 9x / Me Profile Setup</h4></div></div><div></div></div><p>
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926530"></a>Windows Client Profile Configuration Information</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2926538"></a>Windows 9x / Me Profile Setup</h4></div></div><div></div></div><p>
 When a user first logs in on Windows 9X, the file user.DAT is created,
 as are folders <tt class="filename">Start Menu</tt>, <tt class="filename">Desktop</tt>, 
 <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt>.
 These directories and their contents will be merged with the local
 versions stored in <tt class="filename">c:\windows\profiles\username</tt> on subsequent logins,
 taking the most recent from each.  You will need to use the <i class="parameter"><tt>[global]</tt></i>
-options <a class="indexterm" name="id2928884"></a><i class="parameter"><tt>preserve case</tt></i> = yes, <a class="indexterm" name="id2928898"></a><i class="parameter"><tt>short preserve case</tt></i> = yes and
-<a class="indexterm" name="id2928912"></a><i class="parameter"><tt>case sensitive</tt></i> = no in order to maintain capital letters in shortcuts
+options <a class="indexterm" name="id2926594"></a><i class="parameter"><tt>preserve case</tt></i> = yes, <a class="indexterm" name="id2926609"></a><i class="parameter"><tt>short preserve case</tt></i> = yes and
+<a class="indexterm" name="id2926623"></a><i class="parameter"><tt>case sensitive</tt></i> = no in order to maintain capital letters in shortcuts
 in any of the profile folders.
 </p><p>
 The user.DAT file contains all the user's preferences.  If you wish to
@@ -12601,7 +12601,7 @@ will inform you that <tt class="computeroutput">The user has not logged on befor
 <tt class="computeroutput">Do you wish to save the user's preferences?</tt>. Select <span class="guibutton">yes</span>.
 </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 <a class="indexterm" name="id2929100"></a><i class="parameter"><tt>logon path</tt></i>
+to examine the contents of the directory specified in the <a class="indexterm" name="id2926811"></a><i class="parameter"><tt>logon path</tt></i>
 on the samba server and verify that the <tt class="filename">Desktop</tt>, <tt class="filename">Start Menu</tt>,
 <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt> folders have been created.
 </p><p>
@@ -12650,7 +12650,7 @@ they will be told that they are logging in "for the first time".
         </p></li><li><p>
         log off the windows 9x / Me client.
         </p></li><li><p>
-			check the contents of the profile path (see <a class="indexterm" name="id2929306"></a><i class="parameter"><tt>logon path</tt></i> described
+			check the contents of the profile path (see <a class="indexterm" name="id2927017"></a><i class="parameter"><tt>logon path</tt></i> described
 			above), and delete the <tt class="filename">user.DAT</tt> or <tt class="filename">user.MAN</tt> file for the user,
         making a backup if required.
         </p></li></ol></div><p>
@@ -12662,14 +12662,14 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof
 and / or netlogons on the Windows NT4/200x server.  Make a packet trace, or examine
 the example packet traces provided with Windows NT4/200x server, and see what the
 differences are with the equivalent samba trace.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2929364"></a>Windows NT4 Workstation</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2927080"></a>Windows NT4 Workstation</h4></div></div><div></div></div><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 <a class="indexterm" name="id2929377"></a><i class="parameter"><tt>logon path</tt></i> parameter.
+through the <a class="indexterm" name="id2927093"></a><i class="parameter"><tt>logon path</tt></i> parameter.
 </p><p>
 There is a parameter that is now available for use with NT Profiles:
-<a class="indexterm" name="id2929396"></a><i class="parameter"><tt>logon drive</tt></i>.  This should be set to <tt class="filename">H:</tt> or any other drive, and
-should be used in conjunction with the new <a class="indexterm" name="id2929418"></a><i class="parameter"><tt>logon home</tt></i> parameter.
+<a class="indexterm" name="id2927113"></a><i class="parameter"><tt>logon drive</tt></i>.  This should be set to <tt class="filename">H:</tt> or any other drive, and
+should be used in conjunction with the new <a class="indexterm" name="id2927135"></a><i class="parameter"><tt>logon home</tt></i> 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
@@ -12691,7 +12691,7 @@ turns a profile into a mandatory one.
 </p><p>
 The case of the profile is significant.  The file must be called
 <tt class="filename">NTuser.DAT</tt> or, for a mandatory profile, <tt class="filename">NTuser.MAN</tt>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2929549"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2927266"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p>
 You must first convert the profile from a local profile to a domain
 profile on the MS Windows workstation as follows:
 </p><div class="procedure"><ol type="1"><li><p>
@@ -12740,7 +12740,7 @@ On the XP workstation log in with an Administrator account.
 </p></li><li><p>Click: <span class="guimenu">Start</span>, <span class="guimenuitem">Run</span></p></li><li><p>Type: <b class="userinput"><tt>mmc</tt></b></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click: <span class="guimenu">File</span>, <span class="guimenuitem">Add/Remove Snap-in...</span>, <span class="guimenuitem">Add</span></p></li><li><p>Double-Click: <span class="guiicon">Group Policy</span></p></li><li><p>Click: <span class="guibutton">Finish</span>, <span class="guibutton">Close</span></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>In the "Console Root" window:</p></li><li><p>Expand: <span class="guiicon">Local Computer Policy</span>, <span class="guiicon">Computer Configuration</span>, 
 			<span class="guiicon">Administrative Templates</span>, <span class="guiicon">System</span>, <span class="guiicon">User Profiles</span></p></li><li><p>Double-Click: <span class="guilabel">Do not check for user ownership of Roaming Profile Folders</span></p></li><li><p>Select: <span class="guilabel">Enabled</span></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>Close the whole console.  You do not need to save the settings (this
 	refers to the console settings rather than the policies you have
-	changed).</p></li><li><p>Reboot</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930060"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><div></div></div><p>
+	changed).</p></li><li><p>Reboot</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927776"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><div></div></div><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
@@ -12752,17 +12752,17 @@ on again with the newer version of MS Windows.
 </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 <tt class="filename">smb.conf</tt> parameters
-that need to be common are <a class="indexterm" name="id2930096"></a><i class="parameter"><tt>logon path</tt></i> and
-<a class="indexterm" name="id2930110"></a><i class="parameter"><tt>logon home</tt></i>.
+that need to be common are <a class="indexterm" name="id2927812"></a><i class="parameter"><tt>logon path</tt></i> and
+<a class="indexterm" name="id2927827"></a><i class="parameter"><tt>logon home</tt></i>.
 </p><p>
 If you have this set up correctly, you will find separate <tt class="filename">user.DAT</tt> and
 <tt class="filename">NTuser.DAT</tt> files in the same profile directory.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930144"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927861"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930161"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2927878"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><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>
@@ -12779,13 +12779,13 @@ domain is not a member of a trust relationship with your NT4 PDC.</p></div></li>
 	<tt class="filename">c:\temp\foobar</tt></p></li><li><p>Click on the button <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li><p>Click on the group 'Everyone' and then click <span class="guibutton">OK</span>. This closes the
 	'choose user' box.</p></li><li><p>Now click <span class="guibutton">OK</span>.</p></li></ol></div><p>
 Follow the above for every profile you need to migrate.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930326"></a>Side bar Notes</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928042"></a>Side bar Notes</h4></div></div><div></div></div><p>
 You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930340"></a>moveuser.exe</h4></div></div><div></div></div><p>
+this. Read the man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928057"></a>moveuser.exe</h4></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930356"></a>Get SID</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928073"></a>Get SID</h4></div></div><div></div></div><p>
 You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
 Resource Kit.
 </p><p>
@@ -12798,7 +12798,7 @@ users who have logged on to this computer. (To find the profile information
 for the user whose locally cached profile you want to move, find the SID for
 the user with the GetSID.exe utility.) Inside of the appropriate user's
 subkey, you will see a string value named ProfileImagePath.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2930397"></a>Mandatory profiles</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928114"></a>Mandatory profiles</h2></div></div><div></div></div><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
@@ -12814,7 +12814,7 @@ file in the copied profile and rename it to NTUser.MAN.
 </p><p>
 For MS Windows 9x / Me it is the <tt class="filename">User.DAT</tt> file that must be renamed to <tt class="filename">User.MAN</tt> to
 affect a mandatory profile.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2930455"></a>Creating/Managing Group Profiles</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928172"></a>Creating/Managing Group Profiles</h2></div></div><div></div></div><p>
 Most organisations are arranged into departments. There is a nice benefit in
 this fact since usually most users in a department will require the same desktop
 applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
@@ -12829,14 +12829,14 @@ the now modified profile.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><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></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2930500"></a>Default Profile for Windows Users</h2></div></div><div></div></div><p>
+	</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2928216"></a>Default Profile for Windows Users</h2></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930520"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928237"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p>
 To enable default per use profiles in Windows 9x / Me you can either use the <span class="application">Windows 98 System
 Policy Editor</span> or change the registry directly.
 </p><p>
@@ -12848,7 +12848,7 @@ select <span class="guilabel">User Profiles</span>, click on the enable box. Do
 To modify the registry directly, launch the <span class="application">Registry Editor</span> (<b class="command">regedit.exe</b>), 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="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930619"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928336"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><div></div></div><p>
 When a user logs on to a Windows 9x / Me machine, the local profile path, 
 <tt class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked
 for an existing entry for that user:
@@ -12864,7 +12864,7 @@ If a User Profile is not found in either location, the Default User Profile from
 machine is used and is copied to a newly created folder for the logged on user. At log off, any
 changes that the user made are written to the user's local profile. If the user has a roaming
 profile, the changes are written to the user's profile on the server.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930668"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928385"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><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
@@ -12927,7 +12927,7 @@ are controlled by entries on Windows NT4 is:
 </p><p>
 The above hive key contains a list of automatically managed folders. The default entries are:
 </p><p>
-</p><div class="table"><a name="id2931019"></a><p class="title"><b>Table�24.1.�User Shell Folder registry keys default values</b></p><table summary="User Shell Folder registry keys default values" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu </td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
+</p><div class="table"><a name="id2928735"></a><p class="title"><b>Table�24.1.�User Shell Folder registry keys default values</b></p><table summary="User Shell Folder registry keys default values" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu </td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
 </p><p>
 The registry key that contains the location of the default profile settings is:
 </p><p>
@@ -12935,8 +12935,8 @@ The registry key that contains the location of the default profile settings is:
 </p><p>
 The default entries are:
 
-</p><div class="table"><a name="id2931163"></a><p class="title"><b>Table�24.2.�Defaults of profile settings registry keys</b></p><table summary="Defaults of profile settings registry keys" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Common Desktop</td><td>%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td>Common Programs</td><td>%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td>Common Start Menu</td><td>%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td>Common Startup</td><td>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931222"></a>MS Windows 200x/XP</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+</p><div class="table"><a name="id2928879"></a><p class="title"><b>Table�24.2.�Defaults of profile settings registry keys</b></p><table summary="Defaults of profile settings registry keys" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Common Desktop</td><td>%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td>Common Programs</td><td>%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td>Common Start Menu</td><td>%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td>Common Startup</td><td>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2928939"></a>MS Windows 200x/XP</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><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
@@ -12985,7 +12985,7 @@ are controlled by entries on Windows 200x/XP is:
 </p><p>
 The above hive key contains a list of automatically managed folders. The default entries are:
 </p><p>
-</p><div class="table"><a name="id2931418"></a><p class="title"><b>Table�24.3.�Defaults of default user profile paths registry keys</b></p><table summary="Defaults of default user profile paths registry keys" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Cache</td><td>%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td>Cookies</td><td>%USERPROFILE%\Cookies</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>History</td><td>%USERPROFILE%\Local Settings\History</td></tr><tr><td>Local AppData</td><td>%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td>Local Settings</td><td>%USERPROFILE%\Local Settings</td></tr><tr><td>My Pictures</td><td>%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>Personal</td><td>%USERPROFILE%\My Documents</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu</td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td>Templates</td><td>%USERPROFILE%\Templates</td></tr></tbody></table></div><p>
+</p><div class="table"><a name="id2929134"></a><p class="title"><b>Table�24.3.�Defaults of default user profile paths registry keys</b></p><table summary="Defaults of default user profile paths registry keys" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Cache</td><td>%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td>Cookies</td><td>%USERPROFILE%\Cookies</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>History</td><td>%USERPROFILE%\Local Settings\History</td></tr><tr><td>Local AppData</td><td>%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td>Local Settings</td><td>%USERPROFILE%\Local Settings</td></tr><tr><td>My Pictures</td><td>%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>Personal</td><td>%USERPROFILE%\My Documents</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu</td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td>Templates</td><td>%USERPROFILE%\Templates</td></tr></tbody></table></div><p>
 </p><p>
 There is also an entry called "Default" that has no value set. The default entry is of type <tt class="constant">REG_SZ</tt>, all
 the others are of type <tt class="constant">REG_EXPAND_SZ</tt>.
@@ -13013,9 +13013,9 @@ A roaming profile will be cached locally unless the following registry key is cr
 HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
 	winlogon\"DeleteRoamingCache"=dword:00000001</pre><p>
 In which case, the local cache copy will be deleted on logout.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2931730"></a>Common Errors</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2929447"></a>Common Errors</h2></div></div><div></div></div><p>
 The following are some typical errors/problems/questions that have been asked.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931743"></a>Setting up roaming profiles for just a few user's or group's?</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929460"></a>Setting up roaming profiles for just a few user's or group's?</h3></div></div><div></div></div><p>
 With samba-2.2.x the choice you have is to enable or disable roaming
 profiles support. It is a global only setting. The default is to have
 roaming profiles and the default path will locate them in the user's home
@@ -13033,7 +13033,7 @@ using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).
 </p><p>
 In any case, you can configure only one profile per user. That profile can
 be either:
-</p><div class="itemizedlist"><ul type="disc"><li><p>A profile unique to that user</p></li><li><p>A mandatory profile (one the user can not change)</p></li><li><p>A group profile (really should be mandatory ie:unchangable)</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931812"></a>Can NOT use Roaming Profiles</h3></div></div><div></div></div><p>
+</p><div class="itemizedlist"><ul type="disc"><li><p>A profile unique to that user</p></li><li><p>A mandatory profile (one the user can not change)</p></li><li><p>A group profile (really should be mandatory ie:unchangable)</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929529"></a>Can NOT use Roaming Profiles</h3></div></div><div></div></div><p>
 A user requested the following:
 &#8220;<span class="quote">
 I do not want Roaming profiles to be implemented. I want to give users a local profile alone.  ... 
@@ -13079,7 +13079,7 @@ Exchange Server back-end. This removes the need for a PST file.
 LOCAL profiles mean:
 </p><div class="itemizedlist"><ul type="disc"><li><p>If each machine is used my many users then much local disk storage is needed for local profiles</p></li><li><p>Every workstation the user logs into has it's own profile, these can be very different from machine to machine</p></li></ul></div><p>
 On the other hand, use of roaming profiles means:
-</p><div class="itemizedlist"><ul type="disc"><li><p>The network administrator can control the desktop environment of all users.</p></li><li><p>Use of mandatory profiles drasitcally reduces network management overheads.</p></li><li><p>In the long run users will be experience fewer problems.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932026"></a>Changing the default profile</h3></div></div><div></div></div><p>
+</p><div class="itemizedlist"><ul type="disc"><li><p>The network administrator can control the desktop environment of all users.</p></li><li><p>Use of mandatory profiles drasitcally reduces network management overheads.</p></li><li><p>In the long run users will be experience fewer problems.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929742"></a>Changing the default profile</h3></div></div><div></div></div><p>
 <span class="emphasis"><em>Question:</em></span>
 &#8220;<span class="quote">
 When the client logs onto the domain controller it searches for a profile to download,
@@ -13104,7 +13104,7 @@ they do not interoperate with domain profiles.
 For roaming profiles add to <tt class="filename">smb.conf</tt>:
 </p><p>
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon path = \\%N\profiles\%U</tt></i></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><i class="parameter"><tt>logon drive = H:</tt></i></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table><p>
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter�25.�PAM based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2932306">Features and Benefits</a></dt><dt><a href="#id2932554">Technical Discussion</a></dt><dd><dl><dt><a href="#id2932572">PAM Configuration Syntax</a></dt><dt><a href="#id2933235">Example System Configurations</a></dt><dt><a href="#id2933539">smb.conf PAM Configuration</a></dt><dt><a href="#id2933617">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2933706">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2934094">Common Errors</a></dt><dd><dl><dt><a href="#id2934108">pam_winbind problem</a></dt><dt><a href="#id2934194">Winbind is not resolving users and groups</a></dt></dl></dd></dl></div><p>
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter�25.�PAM based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2930024">Features and Benefits</a></dt><dt><a href="#id2930271">Technical Discussion</a></dt><dd><dl><dt><a href="#id2930288">PAM Configuration Syntax</a></dt><dt><a href="#id2930969">Example System Configurations</a></dt><dt><a href="#id2931283">smb.conf PAM Configuration</a></dt><dt><a href="#id2931361">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2931445">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2931826">Common Errors</a></dt><dd><dl><dt><a href="#id2931839">pam_winbind problem</a></dt><dt><a href="#id2931926">Winbind is not resolving users and groups</a></dt></dl></dd></dl></div><p>
 This chapter you should help you to deploy winbind based authentication on any PAM enabled
 UNIX/Linux system. Winbind can be used to enable user level application access authentication
 from any MS Windows NT Domain, MS Windows 200x Active Directory based domain, or any Samba
@@ -13115,7 +13115,7 @@ In addition to knowing how to configure winbind into PAM, you will learn generic
 possibilities and in particular how to deploy tools like pam_smbpass.so to your advantage.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 The use of Winbind require more than PAM configuration alone. Please refer to <a href="#winbind" title="Chapter�21.�Winbind: Use of Domain Accounts">the Winbind chapter</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932306"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2930024"></a>Features and Benefits</h2></div></div><div></div></div><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
@@ -13173,12 +13173,12 @@ of distributed samba domain controllers that can provide wide are network bandwi
 efficient authentication services for PAM capable systems. In effect, this allows the
 deployment of centrally managed and maintained distributed authentication from a single
 user account database.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932554"></a>Technical Discussion</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2930271"></a>Technical Discussion</h2></div></div><div></div></div><p>
 PAM is designed to provide the system administrator with a great deal of flexibility in
 configuration of the privilege granting applications of their system. The local
 configuration of system security controlled by PAM is contained in one of two places:
 either the single system file, /etc/pam.conf; or the /etc/pam.d/ directory.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932572"></a>PAM Configuration Syntax</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930288"></a>PAM Configuration Syntax</h3></div></div><div></div></div><p>
 In this section we discuss the correct syntax of and generic options respected by entries to these files.
 PAM specific tokens in the configuration file are case insensitive. The module paths, however, are case
 sensitive since they indicate a file's name and reflect the case dependence of typical file-systems.
@@ -13196,7 +13196,7 @@ is located outside the default then the path must be specified as:
 </p><pre class="programlisting">
 auth  required  /other_path/pam_strange_module.so
 </pre><p>
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2932629"></a>Anatomy of <tt class="filename">/etc/pam.d</tt> Entries</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2930347"></a>Anatomy of <tt class="filename">/etc/pam.d</tt> Entries</h4></div></div><div></div></div><p>
 The remaining information in this subsection was taken from the documentation of the Linux-PAM
 project. For more information on PAM, see 
 <a href="http://ftp.kernel.org/pub/linux/libs/pam/" target="_top">The Official Linux-PAM home page</a>
@@ -13365,13 +13365,13 @@ squid auth required pam_mysql.so user=passwd_query passwd=mada \
 		Any line in (one of) the configuration file(s), that is not formatted correctly, will generally tend (erring on the
 		side of caution) to make the authentication process fail. A corresponding error is written to the system log files
 		with a call to syslog(3). 
-		</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933235"></a>Example System Configurations</h3></div></div><div></div></div><p>
+		</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930969"></a>Example System Configurations</h3></div></div><div></div></div><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><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2933266"></a>PAM: original login config</h4></div></div><div></div></div><pre class="programlisting">
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931000"></a>PAM: original login config</h4></div></div><div></div></div><pre class="programlisting">
 #%PAM-1.0
 # The PAM configuration file for the `login' service
 #
@@ -13386,7 +13386,7 @@ 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></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2933293"></a>PAM: login using pam_smbpass</h4></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931038"></a>PAM: login using pam_smbpass</h4></div></div><div></div></div><p>
 PAM allows use of replaceable modules. Those available on a sample system include:
 </p><p><tt class="prompt">$</tt><b class="userinput"><tt>/bin/ls /lib/security</tt></b>
 </p><pre class="programlisting">
@@ -13465,8 +13465,8 @@ authentication to be configured in a single central file. The
 on the basis that it allows for easier administration. As with all issues in 
 life though, every decision makes trade-offs, so you may want examine the 
 PAM documentation for further helpful information.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933539"></a>smb.conf PAM Configuration</h3></div></div><div></div></div><p>
-	There is an option in smb.conf called <a class="indexterm" name="id2933548"></a><i class="parameter"><tt>obey pam restrictions</tt></i>.
+</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931283"></a>smb.conf PAM Configuration</h3></div></div><div></div></div><p>
+	There is an option in smb.conf called <a class="indexterm" name="id2931292"></a><i class="parameter"><tt>obey pam restrictions</tt></i>.
 The following is from the on-line help for this option in SWAT;
 </p><p>
 When Samba is configured to enable PAM support (i.e. 
@@ -13476,11 +13476,11 @@ 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 class="indexterm" name="id2933579"></a><i class="parameter"><tt>encrypt passwords</tt></i> = yes. 
+<a class="indexterm" name="id2931323"></a><i class="parameter"><tt>encrypt passwords</tt></i> = yes. 
 The reason is that PAM modules cannot support the challenge/response 
 authentication mechanism needed in the presence of SMB 
 password encryption. 
-</p><p>Default: <a class="indexterm" name="id2933600"></a><i class="parameter"><tt>obey pam restrictions</tt></i> = no</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933617"></a>Remote CIFS Authentication using winbindd.so</h3></div></div><div></div></div><p>
+</p><p>Default: <a class="indexterm" name="id2931344"></a><i class="parameter"><tt>obey pam restrictions</tt></i> = no</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931361"></a>Remote CIFS Authentication using winbindd.so</h3></div></div><div></div></div><p>
 All operating systems depend on the provision of users credentials acceptable to the platform.
 UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID).
 These are both simple integer type numbers that are obtained from a password backend such
@@ -13506,7 +13506,7 @@ Microsoft Active Directory Service (ADS) in so far as reduction of wide area net
 The rid to unix id database is the only location where the user and group  mappings are 
 stored by winbindd.  If this file is deleted or corrupted, there is no way for winbindd
 to determine which user and group ids correspond to Windows NT user and group rids.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933706"></a>Password Synchronization using pam_smbpass.so</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931445"></a>Password Synchronization using pam_smbpass.so</h3></div></div><div></div></div><p>
 pam_smbpass is a PAM module which can be used on conforming systems to
 keep the smbpasswd (Samba password) database in sync with the unix
 password file. PAM (Pluggable Authentication Modules) is an API supported
@@ -13519,7 +13519,7 @@ concerned about the presence of suid root binaries on your system, it is
 recommended that you use pam_winbind instead.
 </p><p>
 Options recognized by this module are as follows:
-</p><div class="table"><a name="id2933738"></a><p class="title"><b>Table�25.1.�Options recognized by pam_smbpass</b></p><table summary="Options recognized by pam_smbpass" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">debug</td><td align="justify">log more debugging info</td></tr><tr><td align="left">audit</td><td align="justify">like debug, but also logs unknown usernames</td></tr><tr><td align="left">use_first_pass</td><td align="justify">don't prompt the user for passwords; take them from PAM_ items instead</td></tr><tr><td align="left">try_first_pass</td><td align="justify">try to get the password from a previous PAM module, fall back to prompting the user</td></tr><tr><td align="left">use_authtok</td><td align="justify">like try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)</td></tr><tr><td align="left">not_set_pass</td><td align="justify">don't make passwords used by this module available to other modules.</td></tr><tr><td align="left">nodelay</td><td align="justify">don't insert ~1 second delays on authentication failure.</td></tr><tr><td align="left">nullok</td><td align="justify">null passwords are allowed.</td></tr><tr><td align="left">nonull</td><td align="justify">null passwords are not allowed. Used to override the Samba configuration.</td></tr><tr><td align="left">migrate</td><td align="justify">only meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.</td></tr><tr><td align="left">smbconf=<i class="replaceable"><tt>file</tt></i></td><td align="justify">specify an alternate path to the <tt class="filename">smb.conf</tt> file.</td></tr></tbody></table></div><p>
+</p><div class="table"><a name="id2931477"></a><p class="title"><b>Table�25.1.�Options recognized by pam_smbpass</b></p><table summary="Options recognized by pam_smbpass" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">debug</td><td align="justify">log more debugging info</td></tr><tr><td align="left">audit</td><td align="justify">like debug, but also logs unknown usernames</td></tr><tr><td align="left">use_first_pass</td><td align="justify">don't prompt the user for passwords; take them from PAM_ items instead</td></tr><tr><td align="left">try_first_pass</td><td align="justify">try to get the password from a previous PAM module, fall back to prompting the user</td></tr><tr><td align="left">use_authtok</td><td align="justify">like try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)</td></tr><tr><td align="left">not_set_pass</td><td align="justify">don't make passwords used by this module available to other modules.</td></tr><tr><td align="left">nodelay</td><td align="justify">don't insert ~1 second delays on authentication failure.</td></tr><tr><td align="left">nullok</td><td align="justify">null passwords are allowed.</td></tr><tr><td align="left">nonull</td><td align="justify">null passwords are not allowed. Used to override the Samba configuration.</td></tr><tr><td align="left">migrate</td><td align="justify">only meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.</td></tr><tr><td align="left">smbconf=<i class="replaceable"><tt>file</tt></i></td><td align="justify">specify an alternate path to the <tt class="filename">smb.conf</tt> file.</td></tr></tbody></table></div><p>
 </p><p>
 </p><div class="itemizedlist"><ul type="disc"><li><p><a href="mailto:morgan@transmeta.com" target="_top">Andrew Morgan</a>, for providing the Linux-PAM
 			framework, without which none of this would have happened</p></li><li><p><a href="mailto:gafton@redhat.com" target="_top">Christian Gafton</a> and Andrew Morgan again, for the
@@ -13530,7 +13530,7 @@ Options recognized by this module are as follows:
 The following are examples of the use of pam_smbpass.so in the format of Linux
 <tt class="filename">/etc/pam.d/</tt> files structure. Those wishing to implement this
 tool on other platforms will need to adapt this appropriately.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2933951"></a>Password Synchronisation Configuration</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931691"></a>Password Synchronisation Configuration</h4></div></div><div></div></div><p>
 A sample PAM configuration that shows the use of pam_smbpass to make
 sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow)
 is changed.  Useful when an expired password might be changed by an
@@ -13546,7 +13546,7 @@ password   requisite    pam_cracklib.so retry=3
 password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
 password   required     pam_smbpass.so nullok use_authtok try_first_pass
 session    required     pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2933985"></a>Password Migration Configuration</h4></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931724"></a>Password Migration Configuration</h4></div></div><div></div></div><p>
 A sample PAM configuration that shows the use of pam_smbpass to migrate
 from plaintext to encrypted passwords for Samba.  Unlike other methods,
 this can be used for users who have never connected to Samba shares:
@@ -13565,7 +13565,7 @@ password   requisite   pam_cracklib.so retry=3
 password   requisite   pam_unix.so shadow md5 use_authtok try_first_pass
 password   optional    pam_smbpass.so nullok use_authtok try_first_pass
 session    required    pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2934021"></a>Mature Password Configuration</h4></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931759"></a>Mature Password Configuration</h4></div></div><div></div></div><p>
 A sample PAM configuration for a 'mature' smbpasswd installation.
 private/smbpasswd is fully populated, and we consider it an error if
 the smbpasswd doesn't exist or doesn't match the UNIX password.
@@ -13580,7 +13580,7 @@ password   requisite    pam_cracklib.so retry=3
 password   requisite    pam_unix.so shadow md5 use_authtok try_first_pass
 password   required     pam_smbpass.so use_authtok use_first_pass
 session    required     pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2934053"></a>Kerberos Password Integration Configuration</h4></div></div><div></div></div><p>
+</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2931790"></a>Kerberos Password Integration Configuration</h4></div></div><div></div></div><p>
 A sample PAM configuration that shows pam_smbpass used together with
 pam_krb5.  This could be useful on a Samba PDC that is also a member of
 a Kerberos realm.
@@ -13596,10 +13596,10 @@ password   requisite   pam_cracklib.so retry=3
 password   optional    pam_smbpass.so nullok use_authtok try_first_pass
 password   required    pam_krb5.so use_authtok try_first_pass
 session    required    pam_krb5.so
-</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934094"></a>Common Errors</h2></div></div><div></div></div><p>
+</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2931826"></a>Common Errors</h2></div></div><div></div></div><p>
 PAM can be a very fickle and sensitive to configuration glitches. Here we look at a few cases from
 the Samba mailing list.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934108"></a>pam_winbind problem</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931839"></a>pam_winbind problem</h3></div></div><div></div></div><p>
 		&#8220;<span class="quote">
 			I have the following PAM configuration:
 		</span>&#8221;
@@ -13627,11 +13627,11 @@ password required /lib/security/pam_stack.so service=system-auth
 	<tt class="filename">/etc/pam.d/system-auth</tt> and copy only what you need from it into your
 	<tt class="filename">/etc/pam.d/login</tt> file.  Alternatively, if you want all services to use
 	winbind, you can put the winbind-specific stuff in <tt class="filename">/etc/pam.d/system-auth</tt>.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934194"></a>Winbind is not resolving users and groups</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931926"></a>Winbind is not resolving users and groups</h3></div></div><div></div></div><p>
 		&#8220;<span class="quote">
 	My smb.conf file is correctly configured. I have specified 
-	<a class="indexterm" name="id2934208"></a><i class="parameter"><tt>idmap uid</tt></i> = 12000, 
-	and <a class="indexterm" name="id2934222"></a><i class="parameter"><tt>idmap gid</tt></i> = 3000-3500
+	<a class="indexterm" name="id2931940"></a><i class="parameter"><tt>idmap uid</tt></i> = 12000, 
+	and <a class="indexterm" name="id2931955"></a><i class="parameter"><tt>idmap gid</tt></i> = 3000-3500
 	and <b class="command">winbind</b> is running. When I do the following it all works fine.
 </span>&#8221;
 	</p><pre class="screen">
@@ -13668,7 +13668,7 @@ This is driving me nuts! What can be wrong?
 	</p><p>
 	Your system is likely running <b class="command">nscd</b>, the name service
 	caching daemon. Shut it down, do NOT restart it! You will find your problem resolved.
-	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter�26.�Integrating MS Windows networks with Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2934432">Features and Benefits</a></dt><dt><a href="#id2934457">Background Information</a></dt><dt><a href="#id2934521">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2934577">/etc/hosts</a></dt><dt><a href="#id2934718">/etc/resolv.conf</a></dt><dt><a href="#id2934762">/etc/host.conf</a></dt><dt><a href="#id2934813">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2934918">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2935185">The NetBIOS Name Cache</a></dt><dt><a href="#id2935248">The LMHOSTS file</a></dt><dt><a href="#id2935496">HOSTS file</a></dt><dt><a href="#id2935528">DNS Lookup</a></dt><dt><a href="#id2935560">WINS Lookup</a></dt></dl></dd><dt><a href="#id2935678">Common Errors</a></dt><dd><dl><dt><a href="#id2935694">Pinging works only in one way</a></dt><dt><a href="#id2935729">Very Slow Network Connections</a></dt><dt><a href="#id2935780">Samba server name change problem</a></dt></dl></dd></dl></div><a class="indexterm" name="id2934399"></a><p>
+	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter�26.�Integrating MS Windows networks with Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2932164">Features and Benefits</a></dt><dt><a href="#id2932188">Background Information</a></dt><dt><a href="#id2932259">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2932315">/etc/hosts</a></dt><dt><a href="#id2932456">/etc/resolv.conf</a></dt><dt><a href="#id2932499">/etc/host.conf</a></dt><dt><a href="#id2932551">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2932655">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2932922">The NetBIOS Name Cache</a></dt><dt><a href="#id2932985">The LMHOSTS file</a></dt><dt><a href="#id2933234">HOSTS file</a></dt><dt><a href="#id2933266">DNS Lookup</a></dt><dt><a href="#id2933298">WINS Lookup</a></dt></dl></dd><dt><a href="#id2933416">Common Errors</a></dt><dd><dl><dt><a href="#id2933432">Pinging works only in one way</a></dt><dt><a href="#id2933465">Very Slow Network Connections</a></dt><dt><a href="#id2933517">Samba server name change problem</a></dt></dl></dd></dl></div><a class="indexterm" name="id2932131"></a><p>
 This section deals with NetBIOS over TCP/IP name to IP address resolution. If
 your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
 section does not apply to your installation. If your installation involves use of
@@ -13679,7 +13679,7 @@ NetBIOS over TCP/IP then this section may help you to resolve networking problem
 	to NOT run NetBEUI at all. Note also that there is NO such thing as
 	NetBEUI over TCP/IP - the existence of such a protocol is a complete
 	and utter mis-apprehension.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934432"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932164"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Many MS Windows network administrators have never been exposed to basic TCP/IP
 networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and
 Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP based
@@ -13687,7 +13687,7 @@ networking (and may have no desire to be either).
 </p><p>
 This chapter gives a short introduction to the basics of how a name can be resolved to 
 it's IP address for each operating system environment.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934457"></a>Background Information</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932188"></a>Background Information</h2></div></div><div></div></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
@@ -13700,14 +13700,14 @@ Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print
 </p></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
-<a class="indexterm" name="id2934495"></a>
+<a class="indexterm" name="id2932233"></a>
 Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
-<a class="indexterm" name="id2934508"></a>
+<a class="indexterm" name="id2932246"></a>
 Use of DHCP with ADS is recommended as a further means of maintaining central control
 over client workstation network configuration.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934521"></a>Name Resolution in a pure UNIX/Linux world</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932259"></a>Name Resolution in a pure UNIX/Linux world</h2></div></div><div></div></div><p>
 The key configuration files covered in this section are:
-</p><div class="itemizedlist"><ul type="disc"><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><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934577"></a><tt class="filename">/etc/hosts</tt></h3></div></div><div></div></div><p>
+</p><div class="itemizedlist"><ul type="disc"><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><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932315"></a><tt class="filename">/etc/hosts</tt></h3></div></div><div></div></div><p>
 Contains a static list of IP addresses and names.
 eg:
 </p><pre class="programlisting">
@@ -13723,7 +13723,7 @@ 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><a class="indexterm" name="id2934627"></a><p>
+</p><a class="indexterm" name="id2932364"></a><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
@@ -13756,7 +13756,7 @@ 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><a class="indexterm" name="id2934691"></a><p>
+</p><a class="indexterm" name="id2932429"></a><p>
 The <tt class="filename">/etc/hosts</tt> file is foundational to all 
 UNIX/Linux TCP/IP installations and as a minimum will contain 
 the localhost and local network interface IP addresses and the 
@@ -13764,7 +13764,7 @@ 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934718"></a><tt class="filename">/etc/resolv.conf</tt></h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932456"></a><tt class="filename">/etc/resolv.conf</tt></h3></div></div><div></div></div><p>
 This file tells the name resolution libraries:
 </p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine 
 	belongs
@@ -13774,7 +13774,7 @@ This file tells the name resolution libraries:
 	</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><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934762"></a><tt class="filename">/etc/host.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2934774"></a><p>
+	</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932499"></a><tt class="filename">/etc/host.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2932512"></a><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 
@@ -13785,7 +13785,7 @@ multi on
 </pre><p>
 then both addresses should be returned. Please refer to the 
 man page for host.conf for further details.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934813"></a><tt class="filename">/etc/nsswitch.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2934825"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932551"></a><tt class="filename">/etc/nsswitch.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2932563"></a><p>
 This file controls the actual name resolution targets. The 
 file typically has resolver object specifications as follows:
 </p><pre class="programlisting">
@@ -13816,7 +13816,7 @@ facilities and/or services are correctly configured.
 It should be noted that unless a network request/message must be 
 sent, TCP/IP networks are silent. All TCP/IP communications assumes a 
 principal of speaking only when necessary.
-</p><a class="indexterm" name="id2934870"></a><p>
+</p><a class="indexterm" name="id2932608"></a><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 
@@ -13829,7 +13829,7 @@ the <tt class="filename">/etc/nsswitch.conf</tt> file. At this point it
 will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, so long as that machine is within the workgroup to 
 which both the samba machine and the MS Windows machine belong.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934918"></a>Name resolution as used within MS Windows networking</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932655"></a>Name resolution as used within MS Windows networking</h2></div></div><div></div></div><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", 
@@ -13844,14 +13844,14 @@ 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><div class="table"><a name="id2934950"></a><p class="title"><b>Table�26.1.�Unique NetBIOS names</b></p><table summary="Unique NetBIOS names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">MACHINENAME&lt;00&gt;</td><td align="justify">Server Service is running on MACHINENAME</td></tr><tr><td align="left">MACHINENAME&lt;03&gt;</td><td align="justify">Generic Machine Name (NetBIOS name)</td></tr><tr><td align="left">MACHINENAME&lt;20&gt;</td><td align="justify">LanMan Server service is running on MACHINENAME</td></tr><tr><td align="left">WORKGROUP&lt;1b&gt;</td><td align="justify">Domain Master Browser</td></tr></tbody></table></div><div class="table"><a name="id2935020"></a><p class="title"><b>Table�26.2.�Group Names</b></p><table summary="Group Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">WORKGROUP&lt;03&gt;</td><td align="justify">Generic Name registered by all members of WORKGROUP</td></tr><tr><td align="left">WORKGROUP&lt;1c&gt;</td><td align="justify">Domain Controllers / Netlogon Servers</td></tr><tr><td align="left">WORKGROUP&lt;1d&gt;</td><td align="justify">Local Master Browsers</td></tr><tr><td align="left">WORKGROUP&lt;1e&gt;</td><td align="justify">Internet Name Resolvers</td></tr></tbody></table></div><p>
-<a class="indexterm" name="id2935092"></a>
+</p><div class="table"><a name="id2932688"></a><p class="title"><b>Table�26.1.�Unique NetBIOS names</b></p><table summary="Unique NetBIOS names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">MACHINENAME&lt;00&gt;</td><td align="justify">Server Service is running on MACHINENAME</td></tr><tr><td align="left">MACHINENAME&lt;03&gt;</td><td align="justify">Generic Machine Name (NetBIOS name)</td></tr><tr><td align="left">MACHINENAME&lt;20&gt;</td><td align="justify">LanMan Server service is running on MACHINENAME</td></tr><tr><td align="left">WORKGROUP&lt;1b&gt;</td><td align="justify">Domain Master Browser</td></tr></tbody></table></div><div class="table"><a name="id2932758"></a><p class="title"><b>Table�26.2.�Group Names</b></p><table summary="Group Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">WORKGROUP&lt;03&gt;</td><td align="justify">Generic Name registered by all members of WORKGROUP</td></tr><tr><td align="left">WORKGROUP&lt;1c&gt;</td><td align="justify">Domain Controllers / Netlogon Servers</td></tr><tr><td align="left">WORKGROUP&lt;1d&gt;</td><td align="justify">Local Master Browsers</td></tr><tr><td align="left">WORKGROUP&lt;1e&gt;</td><td align="justify">Internet Name Resolvers</td></tr></tbody></table></div><p>
+<a class="indexterm" name="id2932830"></a>
 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><a class="indexterm" name="id2935107"></a><p>
+</p><a class="indexterm" name="id2932845"></a><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 
@@ -13889,7 +13889,7 @@ NBT or NetBT, the NetBIOS over TCP/IP.
 MS Windows machines use a complex array of name resolution mechanisms. 
 Since we are primarily concerned with TCP/IP this demonstration is 
 limited to this area.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935185"></a>The NetBIOS Name Cache</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932922"></a>The NetBIOS Name Cache</h3></div></div><div></div></div><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 
@@ -13903,11 +13903,11 @@ an attempt to exchange a message with that machine will be subject
 to time-out delays. i.e.: Its name is in the cache, so a name resolution 
 lookup will succeed, but the machine can not respond. This can be 
 frustrating for users - but it is a characteristic of the protocol.
-</p><a class="indexterm" name="id2935217"></a><a class="indexterm" name="id2935225"></a><p>
+</p><a class="indexterm" name="id2932955"></a><a class="indexterm" name="id2932963"></a><p>
 The MS Windows utility that allows examination of the NetBIOS 
 name cache is called "nbtstat". The Samba equivalent of this 
 is called <b class="command">nmblookup</b>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935248"></a>The LMHOSTS file</h3></div></div><div></div></div><a class="indexterm" name="id2935255"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932985"></a>The LMHOSTS file</h3></div></div><div></div></div><a class="indexterm" name="id2932993"></a><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 
@@ -13993,14 +13993,14 @@ It typically looks like:
 # 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></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935496"></a>HOSTS file</h3></div></div><div></div></div><p>
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933234"></a>HOSTS file</h3></div></div><div></div></div><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935528"></a>DNS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2935536"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933266"></a>DNS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2933274"></a><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 is dependant on how the NetBIOS 
@@ -14011,7 +14011,7 @@ 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935560"></a>WINS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2935569"></a><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933298"></a>WINS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2933306"></a><p>
 A WINS (Windows Internet Name Server) service is the equivalent of the 
 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores 
 the names and IP addresses that are registered by a Windows client 
@@ -14026,11 +14026,11 @@ needed in the <tt class="filename">smb.conf</tt> file:
 where <i class="replaceable"><tt>xxx.xxx.xxx.xxx</tt></i> is the IP address 
 of the WINS server.
 </p><p>For information about setting up Samba as a WINS server, read 
-	<a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">the chapter on network browsing</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2935678"></a>Common Errors</h2></div></div><div></div></div><p>
+	<a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">the chapter on network browsing</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933416"></a>Common Errors</h2></div></div><div></div></div><p>
 TCP/IP network configuration problems find every network administrator sooner or later.
 The cause can be anything from keyboard mishaps, forgetfulness, simple mistakes, and
 carelessness. Of course, no one is every deliberately careless!
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935694"></a>Pinging works only in one way</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933432"></a>Pinging works only in one way</h3></div></div><div></div></div><p>
 		&#8220;<span class="quote">I can ping my samba server from Windows, but I can
 			not ping my Windows machine from the samba server.</span>&#8221;
 	</p><p>
@@ -14040,9 +14040,9 @@ carelessness. Of course, no one is every deliberately careless!
 	</p><p>
 	Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while
 	the Samba server was on network 192.168.1.128/25 - logically a different network.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935729"></a>Very Slow Network Connections</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933465"></a>Very Slow Network Connections</h3></div></div><div></div></div><p>
 	A common causes of slow network response includes:
-	</p><div class="itemizedlist"><ul type="disc"><li><p>Client is configured to use DNS and DNS server is down</p></li><li><p>Client is configured to use remote DNS server, but remote connection is down</p></li><li><p>Client is configured to use a WINS server, but there is no WINS server</p></li><li><p>Client is NOT configured to use a WINS server, but there is a WINS server</p></li><li><p>Firewall is filtering our DNS or WINS traffic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935780"></a>Samba server name change problem</h3></div></div><div></div></div><p>
+	</p><div class="itemizedlist"><ul type="disc"><li><p>Client is configured to use DNS and DNS server is down</p></li><li><p>Client is configured to use remote DNS server, but remote connection is down</p></li><li><p>Client is configured to use a WINS server, but there is no WINS server</p></li><li><p>Client is NOT configured to use a WINS server, but there is a WINS server</p></li><li><p>Firewall is filtering our DNS or WINS traffic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933517"></a>Samba server name change problem</h3></div></div><div></div></div><p>
 		&#8220;<span class="quote">The name of the samba server was changed, samba was restarted, samba server can not be
 	pinged by new name from MS Windows NT4 Workstation, but it does still respond to ping using
 	the old name. Why?</span>&#8221;
@@ -14082,7 +14082,7 @@ GANDALF	&lt;20&gt;  UNIQUE      192.168.1.1          240
 	The first listing shows the contents of the Local Name Table (i.e.: Identity information on
 	the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache.
 	The name cache contains the remote machines known to this workstation.
-	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter�27.�Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2935983">Features and Benefits</a></dt><dt><a href="#id2936027">What are charsets and unicode?</a></dt><dt><a href="#id2936097">Samba and charsets</a></dt><dt><a href="#id2936224">Conversion from old names</a></dt><dt><a href="#id2936254">Japanese charsets</a></dt><dt><a href="#id2936392">Common errors</a></dt><dd><dl><dt><a href="#id2936398">CP850.so can't be found</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2935983"></a>Features and Benefits</h2></div></div><div></div></div><p>
+	</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter�27.�Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">TAKAHASHI</span> <span class="surname">Motonobu</span></h3><div class="affiliation"><div class="address"><p><tt class="email">&lt;<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2933721">Features and Benefits</a></dt><dt><a href="#id2933765">What are charsets and unicode?</a></dt><dt><a href="#id2933835">Samba and charsets</a></dt><dt><a href="#id2933962">Conversion from old names</a></dt><dt><a href="#id2933992">Japanese charsets</a></dt><dt><a href="#id2934130">Common errors</a></dt><dd><dl><dt><a href="#id2934137">CP850.so can't be found</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933721"></a>Features and Benefits</h2></div></div><div></div></div><p>
 Every industry eventually matures. One of the great areas of maturation is in
 the focus that has been given over the past decade to make it possible for anyone
 anywhere to use a computer. It has not always been that way, in fact, not so long
@@ -14096,7 +14096,7 @@ special mention.
 Samba-2.x supported a single locale through a mechanism called 
 <span class="emphasis"><em>codepages</em></span>. Samba-3 is destined to become a truly trans-global
 file and printer sharing platform.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936027"></a>What are charsets and unicode?</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933765"></a>What are charsets and unicode?</h2></div></div><div></div></div><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"><em>character set(charset)
@@ -14122,46 +14122,46 @@ communicating.
 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 older client.
 Newer clients (Windows NT, 2K, XP) talk unicode over the wire.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936097"></a>Samba and charsets</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933835"></a>Samba and charsets</h2></div></div><div></div></div><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><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2936119"></a><i class="parameter"><tt>unix charset</tt></i></span></dt><dd><p>
+</p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2933856"></a><i class="parameter"><tt>unix charset</tt></i></span></dt><dd><p>
 		This is the charset used internally by your operating system. 
 		The default is <tt class="constant">UTF-8</tt>, which is fine for most 
 		systems. The default in previous samba releases was <tt class="constant">ASCII</tt>. 
-		</p></dd><dt><span class="term"><a class="indexterm" name="id2936155"></a><i class="parameter"><tt>display charset</tt></i></span></dt><dd><p>This is the charset samba will use to print messages
+		</p></dd><dt><span class="term"><a class="indexterm" name="id2933893"></a><i class="parameter"><tt>display charset</tt></i></span></dt><dd><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><span class="term"><a class="indexterm" name="id2936190"></a><i class="parameter"><tt>dos charset</tt></i></span></dt><dd><p>This is the charset samba uses when communicating with 
+		</p></dd><dt><span class="term"><a class="indexterm" name="id2933927"></a><i class="parameter"><tt>dos charset</tt></i></span></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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936224"></a>Conversion from old names</h2></div></div><div></div></div><p>Because previous samba versions did not do any charset conversion, 
+		</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933962"></a>Conversion from old names</h2></div></div><div></div></div><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>Bjoern Jacke has written a utility named <a href="http://j3e.de/linux/convmv/" target="_top">convm</a> that can convert whole directory 
 	structures to different charsets with one single command. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936254"></a>Japanese charsets</h2></div></div><div></div></div><p>Samba doesn't work correctly with Japanese charsets yet. Here are
-points of attention when setting it up:</p><div class="itemizedlist"><ul type="disc"><li><p>You should set <a class="indexterm" name="id2936275"></a><i class="parameter"><tt>mangling method</tt></i> = hash</p></li><li><p>There are various iconv() implementations around and not
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933992"></a>Japanese charsets</h2></div></div><div></div></div><p>Samba doesn't work correctly with Japanese charsets yet. Here are
+points of attention when setting it up:</p><div class="itemizedlist"><ul type="disc"><li><p>You should set <a class="indexterm" name="id2934012"></a><i class="parameter"><tt>mangling method</tt></i> = hash</p></li><li><p>There are various iconv() implementations around and not
 all of  them work equally well. glibc2's iconv() has a critical problem
 in CP932.  libiconv-1.8 works with CP932 but still has some problems and
-does not  work with EUC-JP.</p></li><li><p>You should set <a class="indexterm" name="id2936304"></a><i class="parameter"><tt>dos charset</tt></i> = CP932, not
-Shift_JIS, SJIS...</p></li><li><p>Currently only <a class="indexterm" name="id2936324"></a><i class="parameter"><tt>unix charset</tt></i> = CP932
+does not  work with EUC-JP.</p></li><li><p>You should set <a class="indexterm" name="id2934042"></a><i class="parameter"><tt>dos charset</tt></i> = CP932, not
+Shift_JIS, SJIS...</p></li><li><p>Currently only <a class="indexterm" name="id2934062"></a><i class="parameter"><tt>unix charset</tt></i> = CP932
 will work (but still has some problems...) because of iconv() issues.
-<a class="indexterm" name="id2936340"></a><i class="parameter"><tt>unix charset</tt></i> = EUC-JP doesn't work well because of
-iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <a class="indexterm" name="id2936360"></a><i class="parameter"><tt>unix charset</tt></i> = UTF8-MAC/CAP/HEX/JIS*</p></li></ul></div><p>More information (in Japanese) is available at: <a href="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html" target="_top">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936392"></a>Common errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936398"></a>CP850.so can't be found</h3></div></div><div></div></div><p>&#8220;<span class="quote">Samba is complaining about a missing <tt class="filename">CP850.so</tt> file</span>&#8221;.</p><p>CP850 is the default <a class="indexterm" name="id2936424"></a><i class="parameter"><tt>dos charset</tt></i>. The <a class="indexterm" name="id2936437"></a><i class="parameter"><tt>dos charset</tt></i> is used to convert data to the codepage used by your dos clients. If you don't have any dos clients, you can safely ignore this message. </p><p>CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter�28.�Samba Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2936512">Note</a></dt><dt><a href="#id2936526">Features and Benefits</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936512"></a>Note</h2></div></div><div></div></div><p>
+<a class="indexterm" name="id2934077"></a><i class="parameter"><tt>unix charset</tt></i> = EUC-JP doesn't work well because of
+iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <a class="indexterm" name="id2934098"></a><i class="parameter"><tt>unix charset</tt></i> = UTF8-MAC/CAP/HEX/JIS*</p></li></ul></div><p>More information (in Japanese) is available at: <a href="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html" target="_top">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934130"></a>Common errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934137"></a>CP850.so can't be found</h3></div></div><div></div></div><p>&#8220;<span class="quote">Samba is complaining about a missing <tt class="filename">CP850.so</tt> file</span>&#8221;.</p><p>CP850 is the default <a class="indexterm" name="id2934162"></a><i class="parameter"><tt>dos charset</tt></i>. The <a class="indexterm" name="id2934176"></a><i class="parameter"><tt>dos charset</tt></i> is used to convert data to the codepage used by your dos clients. If you don't have any dos clients, you can safely ignore this message. </p><p>CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter�28.�Samba Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2934250">Note</a></dt><dt><a href="#id2934264">Features and Benefits</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934250"></a>Note</h2></div></div><div></div></div><p>
 This chapter did not make it into this release.
 It is planned for the published release of this document.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936526"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934264"></a>Features and Benefits</h2></div></div><div></div></div><p>
 We need feedback from people who are backing up samba servers.
 We would like to know what software tools you are using to backup
 your samba server/s.
 </p><p>
 In particular, if you have any success and / or failure stories you could
 share with other users this would be appreciated.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter�29.�High Availability Options</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2936596">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936596"></a>Note</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter�29.�High Availability Options</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2934334">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934334"></a>Note</h2></div></div><div></div></div><p>
 This chapter did not make it into this release.
 It is planned for the published release of this document.
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Migration and Updating</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2936735">New Features in Samba-3</a></dt><dt><a href="#id2936865">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2936880">Removed Parameters</a></dt><dt><a href="#id2937006">New Parameters</a></dt><dt><a href="#id2937402">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2937476">New Functionality</a></dt><dd><dl><dt><a href="#id2937483">Databases</a></dt><dt><a href="#id2937718">Changes in Behavior</a></dt><dt><a href="#id2937767">Charsets</a></dt><dt><a href="#id2937791">Passdb Backends and Authentication</a></dt><dt><a href="#id2937909">Charsets</a></dt><dt><a href="#id2937933">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2938265">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2938290">Objectives</a></dt><dt><a href="#id2938728">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2938940">Migration Options</a></dt><dd><dl><dt><a href="#id2939031">Planning for Success</a></dt><dt><a href="#id2939287">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2939647">Features and Benefits</a></dt><dd><dl><dt><a href="#id2939686">Enabling SWAT for use</a></dt><dt><a href="#id2939924">Securing SWAT through SSL</a></dt><dt><a href="#id2940035">The SWAT Home Page</a></dt><dt><a href="#id2940097">Global Settings</a></dt><dt><a href="#id2940204">Share Settings</a></dt><dt><a href="#id2940268">Printers Settings</a></dt><dt><a href="#id2940332">The SWAT Wizard</a></dt><dt><a href="#id2940380">The Status Page</a></dt><dt><a href="#id2940432">The View Page</a></dt><dt><a href="#id2940455">The Password Change Page</a></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter�30.�Upgrading from Samba-2.x to Samba-3.0.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">June 30, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2936735">New Features in Samba-3</a></dt><dt><a href="#id2936865">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2936880">Removed Parameters</a></dt><dt><a href="#id2937006">New Parameters</a></dt><dt><a href="#id2937402">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2937476">New Functionality</a></dt><dd><dl><dt><a href="#id2937483">Databases</a></dt><dt><a href="#id2937718">Changes in Behavior</a></dt><dt><a href="#id2937767">Charsets</a></dt><dt><a href="#id2937791">Passdb Backends and Authentication</a></dt><dt><a href="#id2937909">Charsets</a></dt><dt><a href="#id2937933">LDAP</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936735"></a>New Features in Samba-3</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Migration and Updating</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2934473">New Features in Samba-3</a></dt><dt><a href="#id2934602">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2934617">Removed Parameters</a></dt><dt><a href="#id2934744">New Parameters</a></dt><dt><a href="#id2935140">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2935215">New Functionality</a></dt><dd><dl><dt><a href="#id2935222">Databases</a></dt><dt><a href="#id2935456">Changes in Behavior</a></dt><dt><a href="#id2935505">Charsets</a></dt><dt><a href="#id2935529">Passdb Backends and Authentication</a></dt><dt><a href="#id2935648">Charsets</a></dt><dt><a href="#id2935672">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2936004">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2936029">Objectives</a></dt><dt><a href="#id2936467">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2936679">Migration Options</a></dt><dd><dl><dt><a href="#id2936770">Planning for Success</a></dt><dt><a href="#id2937026">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2937386">Features and Benefits</a></dt><dd><dl><dt><a href="#id2937426">Enabling SWAT for use</a></dt><dt><a href="#id2937663">Securing SWAT through SSL</a></dt><dt><a href="#id2937775">The SWAT Home Page</a></dt><dt><a href="#id2937837">Global Settings</a></dt><dt><a href="#id2937944">Share Settings</a></dt><dt><a href="#id2938008">Printers Settings</a></dt><dt><a href="#id2938072">The SWAT Wizard</a></dt><dt><a href="#id2938120">The Status Page</a></dt><dt><a href="#id2938171">The View Page</a></dt><dt><a href="#id2938195">The Password Change Page</a></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter�30.�Upgrading from Samba-2.x to Samba-3.0.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">June 30, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2934473">New Features in Samba-3</a></dt><dt><a href="#id2934602">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2934617">Removed Parameters</a></dt><dt><a href="#id2934744">New Parameters</a></dt><dt><a href="#id2935140">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2935215">New Functionality</a></dt><dd><dl><dt><a href="#id2935222">Databases</a></dt><dt><a href="#id2935456">Changes in Behavior</a></dt><dt><a href="#id2935505">Charsets</a></dt><dt><a href="#id2935529">Passdb Backends and Authentication</a></dt><dt><a href="#id2935648">Charsets</a></dt><dt><a href="#id2935672">LDAP</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934473"></a>New Features in Samba-3</h2></div></div><div></div></div><p>
 Major new features:
 </p><div class="orderedlist"><ol type="1"><li><p>
 	Active Directory support. This release is able to join a ADS realm
@@ -14207,20 +14207,20 @@ Major new features:
 	Major updates to the Samba documentation tree.
 	</p></li></ol></div><p>
 Plus lots of other improvements!
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936865"></a>Configuration Parameter Changes</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2934602"></a>Configuration Parameter Changes</h2></div></div><div></div></div><p>
 This section contains a brief listing of changes to smb.conf options
 in the 3.0.0 release.  Please refer to the smb.conf(5) man page for
 complete descriptions of new or modified parameters.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936880"></a>Removed Parameters</h3></div></div><div></div></div><p>(order alphabetically):</p><div class="itemizedlist"><ul type="disc"><li><p>admin log </p></li><li><p>alternate permissions </p></li><li><p>character set </p></li><li><p>client codepage </p></li><li><p>code page directory </p></li><li><p>coding system </p></li><li><p>domain admin group </p></li><li><p>domain guest group </p></li><li><p>force unknown acl user </p></li><li><p>nt smb support </p></li><li><p>post script </p></li><li><p>printer driver </p></li><li><p>printer driver file </p></li><li><p>printer driver location </p></li><li><p>status </p></li><li><p>total print jobs </p></li><li><p>use rhosts </p></li><li><p>valid chars </p></li><li><p>vfs options </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937006"></a>New Parameters</h3></div></div><div></div></div><p>(new parameters have been grouped by function):</p><p>Remote management</p><div class="itemizedlist"><ul type="disc"><li><p>abort shutdown script </p></li><li><p>shutdown script </p></li></ul></div><p>User and Group Account Management</p><div class="itemizedlist"><ul type="disc"><li><p>add group script </p></li><li><p>add machine script </p></li><li><p>add user to group script </p></li><li><p>algorithmic rid base </p></li><li><p>delete group script </p></li><li><p>delete user from group script </p></li><li><p>passdb backend </p></li><li><p>set primary group script </p></li></ul></div><p>Authentication</p><div class="itemizedlist"><ul type="disc"><li><p>auth methods </p></li><li><p>ads server </p></li><li><p>realm </p></li></ul></div><p>Protocol Options</p><div class="itemizedlist"><ul type="disc"><li><p>client lanman auth </p></li><li><p>client NTLMv2 auth </p></li><li><p>client schannel </p></li><li><p>client signing </p></li><li><p>client use spnego </p></li><li><p>disable netbios </p></li><li><p>ntlm auth </p></li><li><p>paranoid server security </p></li><li><p>server schannel </p></li><li><p>smb ports </p></li><li><p>use spnego </p></li></ul></div><p>File Service</p><div class="itemizedlist"><ul type="disc"><li><p>get quota command </p></li><li><p>hide special files </p></li><li><p>hide unwriteable files </p></li><li><p>hostname lookups </p></li><li><p>kernel change notify </p></li><li><p>mangle prefix </p></li><li><p>msdfs proxy </p></li><li><p>set quota command </p></li><li><p>use sendfile </p></li><li><p>vfs objects </p></li></ul></div><p>Printing</p><div class="itemizedlist"><ul type="disc"><li><p>max reported print jobs </p></li></ul></div><p>UNICODE and Character Sets</p><div class="itemizedlist"><ul type="disc"><li><p>display charset </p></li><li><p>dos charset </p></li><li><p>unicode </p></li><li><p>unix charset </p></li></ul></div><p>SID to uid/gid Mappings</p><div class="itemizedlist"><ul type="disc"><li><p>idmap backend </p></li><li><p>idmap gid </p></li><li><p>idmap only </p></li><li><p>idmap uid </p></li></ul></div><p>LDAP</p><div class="itemizedlist"><ul type="disc"><li><p>ldap delete dn </p></li><li><p>ldap group suffix </p></li><li><p>ldap idmap suffix </p></li><li><p>ldap machine suffix </p></li><li><p>ldap passwd sync </p></li><li><p>ldap trust ids </p></li><li><p>ldap user suffix </p></li></ul></div><p>General Configuration</p><div class="itemizedlist"><ul type="disc"><li><p>preload modules </p></li><li><p>privatedir </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937402"></a>Modified Parameters (changes in behavior):</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>encrypt passwords (enabled by default) </p></li><li><p>mangling method (set to 'hash2' by default) </p></li><li><p>passwd chat </p></li><li><p>passwd program </p></li><li><p>restrict anonymous (integer value) </p></li><li><p>security (new 'ads' value) </p></li><li><p>strict locking (enabled by default) </p></li><li><p>winbind cache time (increased to 5 minutes) </p></li><li><p>winbind uid (deprecated in favor of 'idmap uid') </p></li><li><p>winbind gid (deprecated in favor of 'idmap gid') </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2937476"></a>New Functionality</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937483"></a>Databases</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934617"></a>Removed Parameters</h3></div></div><div></div></div><p>(order alphabetically):</p><div class="itemizedlist"><ul type="disc"><li><p>admin log </p></li><li><p>alternate permissions </p></li><li><p>character set </p></li><li><p>client codepage </p></li><li><p>code page directory </p></li><li><p>coding system </p></li><li><p>domain admin group </p></li><li><p>domain guest group </p></li><li><p>force unknown acl user </p></li><li><p>nt smb support </p></li><li><p>post script </p></li><li><p>printer driver </p></li><li><p>printer driver file </p></li><li><p>printer driver location </p></li><li><p>status </p></li><li><p>total print jobs </p></li><li><p>use rhosts </p></li><li><p>valid chars </p></li><li><p>vfs options </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2934744"></a>New Parameters</h3></div></div><div></div></div><p>(new parameters have been grouped by function):</p><p>Remote management</p><div class="itemizedlist"><ul type="disc"><li><p>abort shutdown script </p></li><li><p>shutdown script </p></li></ul></div><p>User and Group Account Management</p><div class="itemizedlist"><ul type="disc"><li><p>add group script </p></li><li><p>add machine script </p></li><li><p>add user to group script </p></li><li><p>algorithmic rid base </p></li><li><p>delete group script </p></li><li><p>delete user from group script </p></li><li><p>passdb backend </p></li><li><p>set primary group script </p></li></ul></div><p>Authentication</p><div class="itemizedlist"><ul type="disc"><li><p>auth methods </p></li><li><p>ads server </p></li><li><p>realm </p></li></ul></div><p>Protocol Options</p><div class="itemizedlist"><ul type="disc"><li><p>client lanman auth </p></li><li><p>client NTLMv2 auth </p></li><li><p>client schannel </p></li><li><p>client signing </p></li><li><p>client use spnego </p></li><li><p>disable netbios </p></li><li><p>ntlm auth </p></li><li><p>paranoid server security </p></li><li><p>server schannel </p></li><li><p>smb ports </p></li><li><p>use spnego </p></li></ul></div><p>File Service</p><div class="itemizedlist"><ul type="disc"><li><p>get quota command </p></li><li><p>hide special files </p></li><li><p>hide unwriteable files </p></li><li><p>hostname lookups </p></li><li><p>kernel change notify </p></li><li><p>mangle prefix </p></li><li><p>msdfs proxy </p></li><li><p>set quota command </p></li><li><p>use sendfile </p></li><li><p>vfs objects </p></li></ul></div><p>Printing</p><div class="itemizedlist"><ul type="disc"><li><p>max reported print jobs </p></li></ul></div><p>UNICODE and Character Sets</p><div class="itemizedlist"><ul type="disc"><li><p>display charset </p></li><li><p>dos charset </p></li><li><p>unicode </p></li><li><p>unix charset </p></li></ul></div><p>SID to uid/gid Mappings</p><div class="itemizedlist"><ul type="disc"><li><p>idmap backend </p></li><li><p>idmap gid </p></li><li><p>idmap only </p></li><li><p>idmap uid </p></li></ul></div><p>LDAP</p><div class="itemizedlist"><ul type="disc"><li><p>ldap delete dn </p></li><li><p>ldap group suffix </p></li><li><p>ldap idmap suffix </p></li><li><p>ldap machine suffix </p></li><li><p>ldap passwd sync </p></li><li><p>ldap trust ids </p></li><li><p>ldap user suffix </p></li></ul></div><p>General Configuration</p><div class="itemizedlist"><ul type="disc"><li><p>preload modules </p></li><li><p>privatedir </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935140"></a>Modified Parameters (changes in behavior):</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>encrypt passwords (enabled by default) </p></li><li><p>mangling method (set to 'hash2' by default) </p></li><li><p>passwd chat </p></li><li><p>passwd program </p></li><li><p>restrict anonymous (integer value) </p></li><li><p>security (new 'ads' value) </p></li><li><p>strict locking (enabled by default) </p></li><li><p>winbind cache time (increased to 5 minutes) </p></li><li><p>winbind uid (deprecated in favor of 'idmap uid') </p></li><li><p>winbind gid (deprecated in favor of 'idmap gid') </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2935215"></a>New Functionality</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935222"></a>Databases</h3></div></div><div></div></div><p>
 	This section contains brief descriptions of any new databases
 	introduced in Samba 3.0.  Please remember to backup your existing
 	${lock directory}/*tdb before upgrading to Samba 3.0.  Samba will
 	upgrade databases as they are opened (if necessary), but downgrading
 	from 3.0 to 2.2 is an unsupported path.
-	</p><div class="table"><a name="id2937502"></a><p class="title"><b>Table�30.1.�TDB File Descriptions</b></p><table summary="TDB File Descriptions" border="1"><colgroup><col align="left"><col align="justify"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="justify">Description</th><th align="center">Backup?</th></tr></thead><tbody><tr><td align="left">account_policy</td><td align="justify">User policy settings</td><td align="left">yes</td></tr><tr><td align="left">gencache</td><td align="justify">Generic caching db</td><td align="left">no</td></tr><tr><td align="left">group_mapping</td><td align="justify"><p>Mapping table from Windows groups/SID to unix groups</p></td><td align="left">yes</td></tr><tr><td align="left">idmap</td><td align="justify"><p>new ID map table from SIDS to UNIX uids/gids</p></td><td align="left">yes</td></tr><tr><td align="left">namecache</td><td align="justify">Name resolution cache entries</td><td align="left">no</td></tr><tr><td align="left">netlogon_unigrp</td><td align="justify"><p>Cache of universal group membership obtained when operating
+	</p><div class="table"><a name="id2935241"></a><p class="title"><b>Table�30.1.�TDB File Descriptions</b></p><table summary="TDB File Descriptions" border="1"><colgroup><col align="left"><col align="justify"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="justify">Description</th><th align="center">Backup?</th></tr></thead><tbody><tr><td align="left">account_policy</td><td align="justify">User policy settings</td><td align="left">yes</td></tr><tr><td align="left">gencache</td><td align="justify">Generic caching db</td><td align="left">no</td></tr><tr><td align="left">group_mapping</td><td align="justify"><p>Mapping table from Windows groups/SID to unix groups</p></td><td align="left">yes</td></tr><tr><td align="left">idmap</td><td align="justify"><p>new ID map table from SIDS to UNIX uids/gids</p></td><td align="left">yes</td></tr><tr><td align="left">namecache</td><td align="justify">Name resolution cache entries</td><td align="left">no</td></tr><tr><td align="left">netlogon_unigrp</td><td align="justify"><p>Cache of universal group membership obtained when operating
 				as a member of a Windows domain</p></td><td align="left">no</td></tr><tr><td align="left">printing/*.tdb</td><td align="justify"><p>Cached output from 'lpq command' created on a per print 
 				service basis</p></td><td align="left">no</td></tr><tr><td align="left">registry</td><td align="justify"><p>Read-only samba registry skeleton that provides support for
-				exporting various db tables via the winreg RPCs</p></td><td align="left">no</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937718"></a>Changes in Behavior</h3></div></div><div></div></div><p>
+				exporting various db tables via the winreg RPCs</p></td><td align="left">no</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935456"></a>Changes in Behavior</h3></div></div><div></div></div><p>
 	The following issues are known changes in behavior between Samba 2.2 and
 	Samba 3.0 that may affect certain installations of Samba.
 	</p><div class="orderedlist"><ol type="1"><li><p>
@@ -14236,11 +14236,11 @@ complete descriptions of new or modified parameters.
 		script' that must be specified for this purpose.  Samba 3.0 will
 		not fall back to using the 'add user script' in the absence of
 		an 'add machine script'
-		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937767"></a>Charsets</h3></div></div><div></div></div><p>
+		</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935505"></a>Charsets</h3></div></div><div></div></div><p>
 	You might experience problems with special characters when communicating with old DOS
 	clients. Codepage support has changed in samba 3.0. Read the chapter
 	<a href="#unicode" title="Chapter�27.�Unicode/Charsets">Unicode support</a> for details.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937791"></a>Passdb Backends and Authentication</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935529"></a>Passdb Backends and Authentication</h3></div></div><div></div></div><p>
 	There have been a few new changes that Samba administrators should be
 	aware of when moving to Samba 3.0.
 	</p><div class="orderedlist"><ol type="1"><li><p>
@@ -14250,15 +14250,15 @@ complete descriptions of new or modified parameters.
 		must be created for each user, or (b) 'encrypt passwords = no'
 		must be explicitly defined in smb.conf.
 		</p></li><li><p>
-				Inclusion of new <a class="indexterm" name="id2937829"></a><i class="parameter"><tt>security</tt></i> = ads option for integration
+				Inclusion of new <a class="indexterm" name="id2935568"></a><i class="parameter"><tt>security</tt></i> = ads option for integration
 		with an Active Directory domain using the native Windows
 		Kerberos 5 and LDAP protocols.
 		</p></li></ol></div><p>
 	Samba 3.0 also includes the possibility of setting up chains
 	of authentication methods 
-	(<a class="indexterm" name="id2937851"></a><i class="parameter"><tt>auth methods</tt></i>) and account
+	(<a class="indexterm" name="id2935590"></a><i class="parameter"><tt>auth methods</tt></i>) and account
 	storage backends 
-	(<a class="indexterm" name="id2937866"></a><i class="parameter"><tt>passdb backend</tt></i>). 
+	(<a class="indexterm" name="id2935605"></a><i class="parameter"><tt>passdb backend</tt></i>). 
 	Please refer to the <tt class="filename">smb.conf</tt>
 	man page and <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter about account information databases</a> for details.  While both parameters assume sane default
 	values, it is likely that you will need to understand what the
@@ -14267,13 +14267,13 @@ complete descriptions of new or modified parameters.
 	Certain functions of the smbpasswd(8) tool have been split between the
 	new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8)
 	utility.  See the respective man pages for details.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937909"></a>Charsets</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935648"></a>Charsets</h3></div></div><div></div></div><p>
 	You might experience problems with special characters when communicating with old DOS
 	clients. Codepage support has changed in samba 3.0. Read the chapter
 	<a href="#unicode" title="Chapter�27.�Unicode/Charsets">Unicode support</a> for details.
-	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937933"></a>LDAP</h3></div></div><div></div></div><p>
+	</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2935672"></a>LDAP</h3></div></div><div></div></div><p>
 	This section outlines the new features affecting Samba / LDAP integration.
-	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2937945"></a>New Schema</h4></div></div><div></div></div><p>
+	</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2935684"></a>New Schema</h4></div></div><div></div></div><p>
 		A new object class (sambaSamAccount) has been introduced to replace
 		the old sambaAccount.  This change aids us in the renaming of attributes
 		to prevent clashes with attributes from other vendors.  There is a
@@ -14315,7 +14315,7 @@ complete descriptions of new or modified parameters.
 			sambaIdmapEntry - object storing a mapping between a
 			SID and a UNIX uid/gid.  These objects are created by the
 			idmap_ldap module as needed.
-			</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938057"></a>New Suffix for Searching</h4></div></div><div></div></div><p>
+			</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2935797"></a>New Suffix for Searching</h4></div></div><div></div></div><p>
 		The following new smb.conf parameters have been added to aid in directing
 		certain LDAP queries when 'passdb backend = ldapsam://...' has been
 		specified.
@@ -14327,7 +14327,7 @@ complete descriptions of new or modified parameters.
 		</p><p>
 		Due to a limitation in Samba's smb.conf parsing, you should not surround
 		the DN's with quotation marks.
-		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938124"></a>IdMap LDAP support</h4></div></div><div></div></div><p>
+		</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2935863"></a>IdMap LDAP support</h4></div></div><div></div></div><p>
 		Samba 3.0 supports an ldap backend for the idmap subsystem.  The
 		following options would inform Samba that the idmap table should be
 		stored on the directory server onterose in the "ou=idmap,dc=plainjoe,
@@ -14336,10 +14336,10 @@ complete descriptions of new or modified parameters.
 		This configuration allows winbind installations on multiple servers to
 		share a uid/gid number space, thus avoiding the interoperability problems
 		with NFS that were present in Samba 2.2.
-		</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter�31.�Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2938265">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2938290">Objectives</a></dt><dt><a href="#id2938728">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2938940">Migration Options</a></dt><dd><dl><dt><a href="#id2939031">Planning for Success</a></dt><dt><a href="#id2939287">Samba-3 Implementation Choices</a></dt></dl></dd></dl></div><p>
+		</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter�31.�Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2936004">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2936029">Objectives</a></dt><dt><a href="#id2936467">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2936679">Migration Options</a></dt><dd><dl><dt><a href="#id2936770">Planning for Success</a></dt><dt><a href="#id2937026">Samba-3 Implementation Choices</a></dt></dl></dd></dl></div><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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2938265"></a>Planning and Getting Started</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936004"></a>Planning and Getting Started</h2></div></div><div></div></div><p>
 In the IT world there is often a saying that all problems are encountered because of
 poor planning. The corollary to this saying is that not all problems can be anticipated
 and planned for. Then again, good planning will anticipate most show stopper type situations.
@@ -14347,7 +14347,7 @@ and planned for. Then again, good planning will anticipate most show stopper typ
 Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
 environment would do well to develop a detailed migration plan. So here are a few pointers to
 help migration get under way.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938290"></a>Objectives</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936029"></a>Objectives</h3></div></div><div></div></div><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
@@ -14373,7 +14373,7 @@ Before migrating a network from MS Windows NT4 to Samba-3 consider all necessary
 should be educated about changes they may experience so that the change will be a welcome one
 and not become an obstacle to the work they need to do. The following are factors that will 
 help ensure a successful migration:
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938501"></a>Domain Layout</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2936240"></a>Domain Layout</h4></div></div><div></div></div><p>
 Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called
 a secondary controller), a domain member, or as a stand-alone server. The Windows network security
 domain context should be sized and scoped before implementation. Particular attention needs to be
@@ -14393,7 +14393,7 @@ serve multiple routed network segments may result in severe performance problems
 response time (eg: ping timing) between the remote segment and the PDC. If long (more than 100 ms)
 locate a backup controller (BDC) on the remote segmanet to serve as the local authentication and
 access control server.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938551"></a>Server Share and Directory Layout</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2936290"></a>Server Share and Directory Layout</h4></div></div><div></div></div><p>
 There are cardinal rules to effective network design. These can not be broken with impunity.
 The most important rule: Simplicity is king in every well controlled network. Every part of
 the infrastructure must be managed, the more complex it is, the greater will be the demand
@@ -14418,32 +14418,32 @@ Remember, job security through complex design and implementation may cause loss
 and downtime to users as the new administrator learns to untangle your knots. Keep access
 controls simple and effective and make sure that users will never be interrupted by stupid
 complexity.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938611"></a>Logon Scripts</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2936350"></a>Logon Scripts</h4></div></div><div></div></div><p>
 Logon scripts can help to ensure that all users gain share and printer connections they need.
 </p><p>
 Logon scripts can be created 'on-the-fly' so that all commands executed are specific to the
 rights and priviliges granted to the user. The preferred controls should be affected through
 group membership so that group information can be used to custom create a logon script using
-the <a class="indexterm" name="id2938632"></a><i class="parameter"><tt>root preexec</tt></i> parameters to the <i class="parameter"><tt>NETLOGON</tt></i> share.
+the <a class="indexterm" name="id2936371"></a><i class="parameter"><tt>root preexec</tt></i> parameters to the <i class="parameter"><tt>NETLOGON</tt></i> share.
 </p><p>
 Some sites prefer to use a tool such as <b class="command">kixstart</b> to establish a controlled
 user environment. In any case you may wish to do a google search for logon script process controls.
 In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that
 deals with how to add printers without user intervention via the logon script process.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938674"></a>Profile Migration/Creation</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2936413"></a>Profile Migration/Creation</h4></div></div><div></div></div><p>
 User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile
 Management.
 </p><p>
 Profiles may also be managed using the Samba-3 tool <b class="command">profiles</b>. This tool allows
 the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file
 to be changed to the SID of the Samba-3 domain.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2938704"></a>User and Group Accounts</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2936443"></a>User and Group Accounts</h4></div></div><div></div></div><p>
 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
 attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
 groups that are present on the MS Windows NT4 domain <span class="emphasis"><em>AND</em></span> to map these to
 suitable Unix/Linux groups. By following this simple advice all user and group attributes
 should migrate painlessly.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938728"></a>Steps In Migration Process</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936467"></a>Steps In Migration Process</h3></div></div><div></div></div><p>
 The approximate migration process is described below.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
 You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
@@ -14470,10 +14470,10 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d rid=3220
 </pre><p>
 	</p></li><li><p><b class="userinput"><tt>net groupmap list</tt></b></p><ol type="a"><li><p>Now check that all groups are recognised</p></li></ol></li></ol></div><p>
 Now migrate all the profiles, then migrate all policy files.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2938940"></a>Migration Options</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936679"></a>Migration Options</h2></div></div><div></div></div><p>
 Sites that wish to migrate from MS Windows NT4 Domain Control to a Samba based solution
 generally fit into three basic categories.
-</p><div class="table"><a name="id2938955"></a><p class="title"><b>Table�31.1.�The 3 Major Site Types</b></p><table summary="The 3 Major Site Types" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Number of Users</th><th align="justify">Description</th></tr></thead><tbody><tr><td align="left">&lt; 50</td><td align="justify"><p>Want simple conversion with NO pain</p></td></tr><tr><td align="left">50 - 250</td><td align="justify"><p>Want new features, can manage some in-house complexity</p></td></tr><tr><td align="left">&gt; 250</td><td align="justify"><p>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</p></td></tr></tbody></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939031"></a>Planning for Success</h3></div></div><div></div></div><p>
+</p><div class="table"><a name="id2936694"></a><p class="title"><b>Table�31.1.�The 3 Major Site Types</b></p><table summary="The 3 Major Site Types" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Number of Users</th><th align="justify">Description</th></tr></thead><tbody><tr><td align="left">&lt; 50</td><td align="justify"><p>Want simple conversion with NO pain</p></td></tr><tr><td align="left">50 - 250</td><td align="justify"><p>Want new features, can manage some in-house complexity</p></td></tr><tr><td align="left">&gt; 250</td><td align="justify"><p>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</p></td></tr></tbody></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936770"></a>Planning for Success</h3></div></div><div></div></div><p>
 There are three basic choices for sites that intend to migrate from MS Windows NT4
 to Samba-3.
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -14492,7 +14492,7 @@ Minimise down-stream problems by:
 	Test ALL assumptions
 	</p></li><li><p>
 	Test full roll-out program, including workstation deployment
-	</p></li></ul></div><div class="table"><a name="id2939102"></a><p class="title"><b>Table�31.2.�Nature of the Conversion Choices</b></p><table summary="Nature of the Conversion Choices" border="1"><colgroup><col align="justify"><col align="justify"><col align="justify"></colgroup><thead><tr><th align="justify">Simple</th><th align="justify">Upgraded</th><th align="justify">Redesign</th></tr></thead><tbody><tr><td align="justify"><p>Make use of minimal OS specific features</p></td><td align="justify"><p>Translate NT4 features to new host OS features</p></td><td align="justify"><p>Decide:</p></td></tr><tr><td align="justify"><p>Suck all accounts from NT4 into Samba-3</p></td><td align="justify"><p>Copy and improve:</p></td><td align="justify"><p>Authentication Regime (database location and access)</p></td></tr><tr><td align="justify"><p>Make least number of operational changes</p></td><td align="justify"><p>Make progressive improvements</p></td><td align="justify"><p>Desktop Management Methods</p></td></tr><tr><td align="justify"><p>Take least amount of time to migrate</p></td><td align="justify"><p>Minimise user impact</p></td><td align="justify"><p>Better Control of Desktops / Users</p></td></tr><tr><td align="justify"><p>Live versus Isolated Conversion</p></td><td align="justify"><p>Maximise functionality</p></td><td align="justify"><p>Identify Needs for: Manageability, Scalability, Security, Availability</p></td></tr><tr><td align="justify"><p>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</p></td><td align="justify"><p>Take advantage of lower maintenance opportunity</p></td><td align="justify"><p></p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939287"></a>Samba-3 Implementation Choices</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Authentication database/back end:</span></dt><dd><p>
+	</p></li></ul></div><div class="table"><a name="id2936841"></a><p class="title"><b>Table�31.2.�Nature of the Conversion Choices</b></p><table summary="Nature of the Conversion Choices" border="1"><colgroup><col align="justify"><col align="justify"><col align="justify"></colgroup><thead><tr><th align="justify">Simple</th><th align="justify">Upgraded</th><th align="justify">Redesign</th></tr></thead><tbody><tr><td align="justify"><p>Make use of minimal OS specific features</p></td><td align="justify"><p>Translate NT4 features to new host OS features</p></td><td align="justify"><p>Decide:</p></td></tr><tr><td align="justify"><p>Suck all accounts from NT4 into Samba-3</p></td><td align="justify"><p>Copy and improve:</p></td><td align="justify"><p>Authentication Regime (database location and access)</p></td></tr><tr><td align="justify"><p>Make least number of operational changes</p></td><td align="justify"><p>Make progressive improvements</p></td><td align="justify"><p>Desktop Management Methods</p></td></tr><tr><td align="justify"><p>Take least amount of time to migrate</p></td><td align="justify"><p>Minimise user impact</p></td><td align="justify"><p>Better Control of Desktops / Users</p></td></tr><tr><td align="justify"><p>Live versus Isolated Conversion</p></td><td align="justify"><p>Maximise functionality</p></td><td align="justify"><p>Identify Needs for: Manageability, Scalability, Security, Availability</p></td></tr><tr><td align="justify"><p>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</p></td><td align="justify"><p>Take advantage of lower maintenance opportunity</p></td><td align="justify"><p></p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937026"></a>Samba-3 Implementation Choices</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Authentication database/back end:</span></dt><dd><p>
 		Samba-3 can use an external authentication backend:
 		</p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind (external Samba or NT4/200x server)</p></li><li><p>External server could use Active Directory or NT4 Domain</p></li><li><p>Can use pam_mkhomedir.so to auto-create home dirs</p></li></ul></div><p>
@@ -14513,7 +14513,7 @@ Minimise down-stream problems by:
 				Linux limit is 16 char, no spaces and no upper case chars (groupadd)</p></li></ul></div></dd><dt><span class="term">Migration Tools:</span></dt><dd><p>
 		Domain Control (NT4 Style) Profiles, Policies, Access Controls, Security
 		</p><div class="itemizedlist"><ul type="disc"><li><p>Samba: net, rpcclient, smbpasswd, pdbedit, profiles</p></li><li><p>Windows: NT4 Domain User Manager, Server Manager (NEXUS)</p></li></ul></div><p>
-                </p></dd></dl></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter�32.�SWAT - The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2939647">Features and Benefits</a></dt><dd><dl><dt><a href="#id2939686">Enabling SWAT for use</a></dt><dt><a href="#id2939924">Securing SWAT through SSL</a></dt><dt><a href="#id2940035">The SWAT Home Page</a></dt><dt><a href="#id2940097">Global Settings</a></dt><dt><a href="#id2940204">Share Settings</a></dt><dt><a href="#id2940268">Printers Settings</a></dt><dt><a href="#id2940332">The SWAT Wizard</a></dt><dt><a href="#id2940380">The Status Page</a></dt><dt><a href="#id2940432">The View Page</a></dt><dt><a href="#id2940455">The Password Change Page</a></dt></dl></dd></dl></div><p>
+                </p></dd></dl></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter�32.�SWAT - The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2937386">Features and Benefits</a></dt><dd><dl><dt><a href="#id2937426">Enabling SWAT for use</a></dt><dt><a href="#id2937663">Securing SWAT through SSL</a></dt><dt><a href="#id2937775">The SWAT Home Page</a></dt><dt><a href="#id2937837">Global Settings</a></dt><dt><a href="#id2937944">Share Settings</a></dt><dt><a href="#id2938008">Printers Settings</a></dt><dt><a href="#id2938072">The SWAT Wizard</a></dt><dt><a href="#id2938120">The Status Page</a></dt><dt><a href="#id2938171">The View Page</a></dt><dt><a href="#id2938195">The Password Change Page</a></dt></dl></dd></dl></div><p>
 There are many and varied opinions regarding the usefulness or otherwise of SWAT.
 No matter how hard one tries to produce the perfect configuration tool it remains
 an object of personal taste. SWAT is a tool that will allow web based configuration
@@ -14521,7 +14521,7 @@ of samba. It has a wizard that may help to get samba configured quickly, it has
 sensitive help on each smb.conf parameter, it provides for monitoring of current state
 of connection information, and it allows network wide MS Windows network password
 management.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2939647"></a>Features and Benefits</h2></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2937386"></a>Features and Benefits</h2></div></div><div></div></div><p>
 There are network administrators who believe that it is a good idea to write systems
 documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT
 does not store the configuration file in any intermediate form, rather, it stores only the
@@ -14533,7 +14533,7 @@ internal ordering.
 So before using SWAT please be warned - SWAT will completely replace your smb.conf with
 a fully optimised file that has been stripped of all comments you might have placed there
 and only non-default settings will be written to the file.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939686"></a>Enabling SWAT for use</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937426"></a>Enabling SWAT for use</h3></div></div><div></div></div><p>
 SWAT should be installed to run via the network super daemon. Depending on which system
 your UNIX/Linux system has you will have either an <b class="command">inetd</b> or
 <b class="command">xinetd</b> based system.
@@ -14587,7 +14587,7 @@ So long as you log onto SWAT as the user <span class="emphasis"><em>root</em></s
 full change and commit ability. The buttons that will be exposed includes:
 <span class="guibutton">HOME</span>, <span class="guibutton">GLOBALS</span>, <span class="guibutton">SHARES</span>, <span class="guibutton">PRINTERS</span>, 
 <span class="guibutton">WIZARD</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, <span class="guibutton">PASSWORD</span>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939924"></a>Securing SWAT through SSL</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937663"></a>Securing SWAT through SSL</h3></div></div><div></div></div><p>
 Lots of people have asked about how to setup SWAT with SSL to allow for secure remote
 administration of Samba. Here is a method that works, courtesy of Markus Krieger
 </p><p>
@@ -14612,7 +14612,7 @@ Modifications to the swat setup are as following:
 </pre></li></ol></div><p>
 afterwords simply contact to swat by using the URL <a href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate
 and the SSL connection is up.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940035"></a>The SWAT Home Page</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937775"></a>The SWAT Home Page</h3></div></div><div></div></div><p>
 The SWAT title page provides access to the latest Samba documentation. The manual page for
 each samba component is accessible from this page as are the Samba-HOWTO-Collection (this 
 document) as well as the O'Reilly book "Using Samba".
@@ -14627,7 +14627,7 @@ as it runs SWAT without authentication and with full administrative ability. ie:
 changes to smb.conf as well as general operation with root privileges. The option that
 creates this ability is the <tt class="option">-a</tt> flag to swat. <span class="emphasis"><em>Do not use this in any 
 production environment.</em></span>
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940097"></a>Global Settings</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937837"></a>Global Settings</h3></div></div><div></div></div><p>
 The Globals button will expose a page that allows configuration of the global parameters
 in smb.conf. There are three levels of exposure of the parameters:
 </p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -14649,7 +14649,7 @@ your changes will be immediately lost.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 SWAT has context sensitive help. To find out what each parameter is for simply click the
 <span class="guibutton">Help</span> link to the left of the configuration parameter.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940204"></a>Share Settings</h3></div></div><div></div></div><p>
+</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937944"></a>Share Settings</h3></div></div><div></div></div><p>
 To affect a currently configured share, simply click on the pull down button between the
 <span class="guibutton">Choose Share</span> and the <span class="guibutton">Delete Share</span> buttons,
 select the share you wish to operate on, then to edit the settings click on the
@@ -14659,7 +14659,7 @@ select the share you wish to operate on, then to edit the settings click on the
 To create a new share, next to the button labelled <span class="guibutton">Create Share</span> enter
 into the text field the name of the share to be created, then click on the 
 <span class="guibutton">Create Share</span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940268"></a>Printers Settings</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938008"></a>Printers Settings</h3></div></div><div></div></div><p>
 To affect a currently configured printer, simply click on the pull down button between the
 <span class="guibutton">Choose Printer</span> and the <span class="guibutton">Delete Printer</span> buttons,
 select the printer you wish to operate on, then to edit the settings click on the
@@ -14669,7 +14669,7 @@ select the printer you wish to operate on, then to edit the settings click on th
 To create a new printer, next to the button labelled <span class="guibutton">Create Printer</span> enter
 into the text field the name of the share to be created, then click on the 
 <span class="guibutton">Create Printer</span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940332"></a>The SWAT Wizard</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938072"></a>The SWAT Wizard</h3></div></div><div></div></div><p>
 The purpose if the SWAT Wizard is to help the Microsoft knowledgeable network administrator
 to configure Samba with a minimum of effort.
 </p><p>
@@ -14685,7 +14685,7 @@ Finally, there are a limited set of options that will determine what type of ser
 will be configured for, whether it will be a WINS server, participate as a WINS client, or
 operate with no WINS support. By clicking on one button you can elect to expose (or not) user
 home directories.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940380"></a>The Status Page</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938120"></a>The Status Page</h3></div></div><div></div></div><p>
 The status page serves a limited purpose. Firstly, it allows control of the samba daemons.
 The key daemons that create the samba server environment are: <span class="application">smbd</span>, <span class="application">nmbd</span>, <span class="application">winbindd</span>.
 </p><p>
@@ -14696,11 +14696,11 @@ conditions with minimal effort.
 </p><p>
 Lastly, the Status page may be used to terminate specific smbd client connections in order to
 free files that may be locked.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940432"></a>The View Page</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938171"></a>The View Page</h3></div></div><div></div></div><p>
 This page allows the administrator to view the optimised <tt class="filename">smb.conf</tt> file and, if you are
 particularly masochistic, will permit you also to see all possible global configuration
 parameters and their settings.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940455"></a>The Password Change Page</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938195"></a>The Password Change Page</h3></div></div><div></div></div><p>
 The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation
 and reactivation of MS Windows networking users on the local machine. Alternatively, you can use
 this tool to change a local password for a user account.
@@ -14711,7 +14711,7 @@ required.
 </p><p>
 One popular use for this tool is to change user passwords across a range of remote MS Windows
 servers.
-</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2940585">Introduction</a></dt><dt><a href="#id2940619">Assumptions</a></dt><dt><a href="#id2940846">The tests</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2942320">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2942341">Debugging with Samba itself</a></dt><dt><a href="#id2942454">Tcpdump</a></dt><dt><a href="#id2942476">Ethereal</a></dt><dt><a href="#id2942528">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2942845">Useful URLs</a></dt><dt><a href="#id2942886">Getting help from the mailing lists</a></dt><dt><a href="#id2870642">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2870770">Introduction</a></dt><dt><a href="#id2870833">General info</a></dt><dt><a href="#id2870870">Debug levels</a></dt><dt><a href="#id2871078">Internal errors</a></dt><dt><a href="#id2871212">Attaching to a running process</a></dt><dt><a href="#id2871258">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter�33.�The Samba checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2940585">Introduction</a></dt><dt><a href="#id2940619">Assumptions</a></dt><dt><a href="#id2940846">The tests</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940585"></a>Introduction</h2></div></div><div></div></div><p>
+</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2938325">Introduction</a></dt><dt><a href="#id2938359">Assumptions</a></dt><dt><a href="#id2938586">The tests</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2940060">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2940082">Debugging with Samba itself</a></dt><dt><a href="#id2940195">Tcpdump</a></dt><dt><a href="#id2940216">Ethereal</a></dt><dt><a href="#id2940268">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2940586">Useful URLs</a></dt><dt><a href="#id2940626">Getting help from the mailing lists</a></dt><dt><a href="#id2940778">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2940906">Introduction</a></dt><dt><a href="#id2940969">General info</a></dt><dt><a href="#id2941006">Debug levels</a></dt><dt><a href="#id2941215">Internal errors</a></dt><dt><a href="#id2941348">Attaching to a running process</a></dt><dt><a href="#id2941395">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter�33.�The Samba checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2938325">Introduction</a></dt><dt><a href="#id2938359">Assumptions</a></dt><dt><a href="#id2938586">The tests</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2938325"></a>Introduction</h2></div></div><div></div></div><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
@@ -14726,7 +14726,7 @@ to solve a problem.
 If you send one of the samba mailing lists  an email saying "it doesn't work"
 and you have not followed this test procedure then you should not be surprised
 if your email is ignored.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940619"></a>Assumptions</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2938359"></a>Assumptions</h2></div></div><div></div></div><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><p>
@@ -14736,7 +14736,7 @@ 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 <i class="replaceable"><tt>tmp</tt></i>.
 You can add a <i class="replaceable"><tt>tmp</tt></i> share like this by adding the
 following to <tt class="filename">smb.conf</tt>:
-</p><div class="example"><a name="id2940668"></a><p class="title"><b>Example�33.1.�smb.conf with [tmp] share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[tmp]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = temporary files </tt></i></td></tr><tr><td><i class="parameter"><tt>path = /tmp</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2938408"></a><p class="title"><b>Example�33.1.�smb.conf with [tmp] share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[tmp]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = temporary files </tt></i></td></tr><tr><td><i class="parameter"><tt>path = /tmp</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr></table></div><p>
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 These tests assume version 3.0 or later of the samba suite.
 Some commands shown did not exist in earlier versions. 
@@ -14749,7 +14749,7 @@ file points to name servers that really do exist.
 Also, if you do not have DNS server access for name resolution please check
 that the settings for your <tt class="filename">smb.conf</tt> file results in <b class="command">dns proxy = no</b>. The
 best way to check this is with <b class="userinput"><tt>testparm smb.conf</tt></b>.
-</p><a class="indexterm" name="id2940768"></a><p>
+</p><a class="indexterm" name="id2938508"></a><p>
 It is helpful to monitor the log files during testing by using the
 <b class="command">tail -F <i class="replaceable"><tt>log_file_name</tt></i></b> in a separate
 terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). 
@@ -14760,7 +14760,7 @@ depending on how or if you specified logging in your <tt class="filename">smb.co
 </p><p>
 If you make changes to your <tt class="filename">smb.conf</tt> file while going through these test,
 don't forget to restart <span class="application">smbd</span> and <span class="application">nmbd</span>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940846"></a>The tests</h2></div></div><div></div></div><div class="procedure"><p class="title"><b>Procedure�33.1.�Diagnosing your samba server</b></p><a class="indexterm" name="id2940862"></a><ol type="1"><li><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2938586"></a>The tests</h2></div></div><div></div></div><div class="procedure"><p class="title"><b>Procedure�33.1.�Diagnosing your samba server</b></p><a class="indexterm" name="id2938602"></a><ol type="1"><li><p>
 In the directory in which you store your <tt class="filename">smb.conf</tt> file, run the command
 <b class="userinput"><tt>testparm smb.conf</tt></b>. If it reports any errors then your <tt class="filename">smb.conf</tt>
 configuration file is faulty.
@@ -14806,8 +14806,8 @@ that file incorrectly. If you installed it as a daemon then check that
 it is running, and check that the netbios-ssn port is in a LISTEN
 state using <b class="userinput"><tt>netstat -a</tt></b>.
 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<a class="indexterm" name="id2941120"></a>
-<a class="indexterm" name="id2941129"></a>
+<a class="indexterm" name="id2938860"></a>
+<a class="indexterm" name="id2938869"></a>
 Some Unix / Linux systems use <b class="command">xinetd</b> in place of
 <b class="command">inetd</b>. Check your system documentation for the location
 of the control file/s for your particular system implementation of
@@ -14829,15 +14829,15 @@ In the above, no allowance has been made for any session requests that
 will automatically translate to the loopback adapter address 127.0.0.1.
 To solve this problem change these lines to:
 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>hosts deny = ALL</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = xxx.xxx.xxx.xxx/yy 127.</tt></i></td></tr></table><p>
-Do <span class="emphasis"><em>not</em></span> use the <a class="indexterm" name="id2941285"></a><i class="parameter"><tt>bind interfaces only</tt></i> parameter where you 
+Do <span class="emphasis"><em>not</em></span> use the <a class="indexterm" name="id2939025"></a><i class="parameter"><tt>bind interfaces only</tt></i> parameter where you 
 may wish to
 use the samba password change facility, or where <span class="application">smbclient</span> may need to
 access a local service for name resolution or for local resource
-connections. (Note: the <a class="indexterm" name="id2941311"></a><i class="parameter"><tt>bind interfaces only</tt></i> parameter deficiency
+connections. (Note: the <a class="indexterm" name="id2939051"></a><i class="parameter"><tt>bind interfaces only</tt></i> parameter deficiency
 where it will not allow connections to the loopback address will be
 fixed soon).
 </p><p>
-<a class="indexterm" name="id2941331"></a>
+<a class="indexterm" name="id2939072"></a>
 Another common cause of these two errors is having something already running 
 on port <tt class="constant">139</tt>, such as Samba 
 (ie: <span class="application">smbd</span> is running from <span class="application">inetd</span> already) or
@@ -14880,7 +14880,7 @@ messages from several hosts.
 If this doesn't give a similar result to the previous test then
 nmblookup isn't correctly getting your broadcast address through its
 automatic mechanism. In this case you should experiment with the
-<a class="indexterm" name="id2941502"></a><i class="parameter"><tt>interfaces</tt></i> option in <tt class="filename">smb.conf</tt> to manually configure your IP
+<a class="indexterm" name="id2939242"></a><i class="parameter"><tt>interfaces</tt></i> option in <tt class="filename">smb.conf</tt> to manually configure your IP
 address, broadcast and netmask. 
 </p><p>
 If your PC and server aren't on the same subnet then you will need to
@@ -14889,7 +14889,7 @@ 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><a class="indexterm" name="id2941549"></a><p>
+</p></li><li><a class="indexterm" name="id2939290"></a><p>
 Run the command <b class="userinput"><tt>smbclient //BIGSERVER/TMP</tt></b>. 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
@@ -14910,11 +14910,11 @@ If it says <span class="errorname">bad password</span> then the likely causes ar
 	you have shadow passwords (or some other password system) but didn't
 	compile in support for them in <span class="application">smbd</span>
 	</p></li><li><p>
-	your <a class="indexterm" name="id2941671"></a><i class="parameter"><tt>valid users</tt></i> configuration is incorrect
+	your <a class="indexterm" name="id2939411"></a><i class="parameter"><tt>valid users</tt></i> configuration is incorrect
 	</p></li><li><p>
-	you have a mixed case password and you haven't enabled the <a class="indexterm" name="id2941694"></a><i class="parameter"><tt>password level</tt></i> option at a high enough level
+	you have a mixed case password and you haven't enabled the <a class="indexterm" name="id2939433"></a><i class="parameter"><tt>password level</tt></i> option at a high enough level
 	</p></li><li><p>
-	the <a class="indexterm" name="id2941717"></a><i class="parameter"><tt>path</tt></i> line in <tt class="filename">smb.conf</tt> is incorrect. Check it with <span class="application">testparm</span>
+	the <a class="indexterm" name="id2939457"></a><i class="parameter"><tt>path</tt></i> line in <tt class="filename">smb.conf</tt> is incorrect. Check it with <span class="application">testparm</span>
 	</p></li><li><p>
 		you enabled password encryption but didn't map unix to samba users. Run </p><pre class="screen"><b class="userinput"><tt>smbpasswd -a <i class="replaceable"><tt>username</tt></i></tt></b></pre><p>.
 	</p></li></ol></div><p>
@@ -14966,13 +14966,13 @@ installed or your smb.conf is incorrect. make sure your <b class="command">hosts
 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 <a class="indexterm" name="id2942003"></a><i class="parameter"><tt>user</tt></i> = username to the <i class="parameter"><tt>[tmp]</tt></i> section of 
+connect you as. To see if this is the problem add the line <a class="indexterm" name="id2939744"></a><i class="parameter"><tt>user</tt></i> = username to the <i class="parameter"><tt>[tmp]</tt></i> section of 
 <tt class="filename">smb.conf</tt> where <i class="replaceable"><tt>username</tt></i> 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 <a class="indexterm" name="id2942043"></a><i class="parameter"><tt>encrypt passwords</tt></i> = no in <tt class="filename">smb.conf</tt>
+and you have <a class="indexterm" name="id2939783"></a><i class="parameter"><tt>encrypt passwords</tt></i> = no in <tt class="filename">smb.conf</tt>
 Turn it back on to fix.
 </p></li><li><p>
 Run the command <b class="userinput"><tt>nmblookup -M <i class="replaceable"><tt>testgroup</tt></i></tt></b> where 
@@ -14983,7 +14983,7 @@ master browser for that workgroup.
 If you don't then the election process has failed. Wait a minute to
 see if it is just being slow then try again. If it still fails after
 that then look at the browsing options you have set in <tt class="filename">smb.conf</tt>. Make
-sure you have <a class="indexterm" name="id2942107"></a><i class="parameter"><tt>preferred master</tt></i> = yes to ensure that 
+sure you have <a class="indexterm" name="id2939847"></a><i class="parameter"><tt>preferred master</tt></i> = yes to ensure that 
 an election is held at startup.
 </p></li><li><p>
 From file manager try to browse the server. Your samba server should
@@ -14993,23 +14993,23 @@ 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
-<a class="indexterm" name="id2942148"></a><i class="parameter"><tt>security</tt></i> = server AND 
-<a class="indexterm" name="id2942162"></a><i class="parameter"><tt>password server</tt></i> = Windows_NT_Machine in your
-<tt class="filename">smb.conf</tt> file, or make sure <a class="indexterm" name="id2942184"></a><i class="parameter"><tt>encrypt passwords</tt></i> is
+<a class="indexterm" name="id2939889"></a><i class="parameter"><tt>security</tt></i> = server AND 
+<a class="indexterm" name="id2939902"></a><i class="parameter"><tt>password server</tt></i> = Windows_NT_Machine in your
+<tt class="filename">smb.conf</tt> file, or make sure <a class="indexterm" name="id2939924"></a><i class="parameter"><tt>encrypt passwords</tt></i> is
 set to "yes".
-</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter�34.�Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2942320">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2942341">Debugging with Samba itself</a></dt><dt><a href="#id2942454">Tcpdump</a></dt><dt><a href="#id2942476">Ethereal</a></dt><dt><a href="#id2942528">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2942845">Useful URLs</a></dt><dt><a href="#id2942886">Getting help from the mailing lists</a></dt><dt><a href="#id2870642">How to get off the mailing lists</a></dt></dl></div><p>
+</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter�34.�Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2940060">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2940082">Debugging with Samba itself</a></dt><dt><a href="#id2940195">Tcpdump</a></dt><dt><a href="#id2940216">Ethereal</a></dt><dt><a href="#id2940268">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2940586">Useful URLs</a></dt><dt><a href="#id2940626">Getting help from the mailing lists</a></dt><dt><a href="#id2940778">How to get off the mailing lists</a></dt></dl></div><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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942320"></a>Diagnostics tools</h2></div></div><div></div></div><p>With SMB networking, it is often not immediately clear what 
+general SMB topics such as browsing.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940060"></a>Diagnostics tools</h2></div></div><div></div></div><p>With SMB networking, it is often not immediately clear what 
 the cause is of a certain problem. Samba itself provides rather 
 useful information, but in some cases you might have to fall back 
 to using a <span class="emphasis"><em>sniffer</em></span>. A sniffer is a program that 
 listens on your LAN, analyses the data sent on it and displays it 
-on the screen.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942341"></a>Debugging with Samba itself</h3></div></div><div></div></div><p>
+on the screen.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940082"></a>Debugging with Samba itself</h3></div></div><div></div></div><p>
 One of the best diagnostic tools for debugging problems is Samba itself.  
 You can use the <tt class="option">-d option</tt> for both <span class="application">smbd</span> and <span class="application">nmbd</span> to specify what 
-<a class="indexterm" name="id2942372"></a><i class="parameter"><tt>debug level</tt></i> at which to run.  See the man pages on smbd, nmbd  and 
+<a class="indexterm" name="id2940113"></a><i class="parameter"><tt>debug level</tt></i> 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>
@@ -15030,17 +15030,17 @@ Some useful samba commands worth investigating:
 </p><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>testparm | more</tt></b>
 <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient -L //{netbios name of server}</tt></b>
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942454"></a>Tcpdump</h3></div></div><div></div></div><p><a href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first 
+</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940195"></a>Tcpdump</h3></div></div><div></div></div><p><a href="http://www.tcpdump.org/" target="_top">Tcpdump</a> was the first 
 unix sniffer with SMB support. It is a command-line utility and 
 nowadays, it's SMB support is somewhat less then that of ethereal 
-and tethereal.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942476"></a>Ethereal</h3></div></div><div></div></div><p>
+and tethereal.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940216"></a>Ethereal</h3></div></div><div></div></div><p>
 <a href="http://www.ethereal.com/" target="_top">Ethereal</a> is a graphical 
 sniffer, available for both unix (Gtk) and Windows. Ethereal's 
 SMB support is very good.</p><p>For details on the use of ethereal, read the well-written 
 ethereal User Guide.</p><p>
 Listen for data on ports 137, 138, 139 and 445. E.g. 
 use the filter <b class="userinput"><tt>port 137 or port 138 or port 139 or port 445</tt></b>.</p><p>A console version of ethereal is available as well and is called 
-<b class="command">tethereal</b>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942528"></a>The Windows Network Monitor</h3></div></div><div></div></div><p>
+<b class="command">tethereal</b>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940268"></a>The Windows Network Monitor</h3></div></div><div></div></div><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 
@@ -15050,7 +15050,7 @@ The version on the NT Server install CD will only allow monitoring
 of network traffic directed to the local NT box and broadcasts on the 
 local subnet.  Be aware that Ethereal can read and write netmon 
 formatted files.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2942549"></a>Installing 'Network Monitor' on an NT Workstation</h4></div></div><div></div></div><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2940289"></a>Installing 'Network Monitor' on an NT Workstation</h4></div></div><div></div></div><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 
@@ -15083,17 +15083,17 @@ Now copy the files from the NT Server in <tt class="filename">%SYSTEMROOT%\Syste
 to <tt class="filename">%SYSTEMROOT%\System32\netmon\*.*</tt> 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></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2942818"></a>Installing 'Network Monitor' on an 9x Workstation</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2940558"></a>Installing 'Network Monitor' on an 9x Workstation</h4></div></div><div></div></div><p>
 To install Netmon on a Windows 9x box install the network monitor agent 
 from the Windows 9x CD (<tt class="filename">\admin\nettools\netmon</tt>).  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></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942845"></a>Useful URLs</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at 
+</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940586"></a>Useful URLs</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><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>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></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942886"></a>Getting help from the mailing lists</h2></div></div><div></div></div><p>
+       ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940626"></a>Getting help from the mailing lists</h2></div></div><div></div></div><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>.
@@ -15127,14 +15127,14 @@ error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace (
 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></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870642"></a>How to get off the mailing lists</h2></div></div><div></div></div><p>To have your name removed from a samba mailing list, go to the
+smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940778"></a>How to get off the mailing lists</h2></div></div><div></div></div><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>. 
 </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></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter�35.�Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2870770">Introduction</a></dt><dt><a href="#id2870833">General info</a></dt><dt><a href="#id2870870">Debug levels</a></dt><dt><a href="#id2871078">Internal errors</a></dt><dt><a href="#id2871212">Attaching to a running process</a></dt><dt><a href="#id2871258">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870770"></a>Introduction</h2></div></div><div></div></div><p>Please report bugs using
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter�35.�Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2940906">Introduction</a></dt><dt><a href="#id2940969">General info</a></dt><dt><a href="#id2941006">Debug levels</a></dt><dt><a href="#id2941215">Internal errors</a></dt><dt><a href="#id2941348">Attaching to a running process</a></dt><dt><a href="#id2941395">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940906"></a>Introduction</h2></div></div><div></div></div><p>Please report bugs using
 	<a href="https://bugzilla.samba.org/" target="_top">bugzilla</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
@@ -15156,7 +15156,7 @@ that list that may be able to help you.
 You may also like to look though the recent mailing list archives,
 which are conveniently accessible on the Samba web pages
 at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870833"></a>General info</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940969"></a>General info</h2></div></div><div></div></div><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
@@ -15168,14 +15168,14 @@ This is very important.
 If you include part of a log file with your bug report then be sure to
 annotate it with exactly what you were doing on the client at the
 time, and exactly what the results were.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870870"></a>Debug levels</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941006"></a>Debug levels</h2></div></div><div></div></div><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 gives more
 detail, but may use too much disk space.
 </p><p>
-To set the debug level use the <a class="indexterm" name="id2870891"></a><i class="parameter"><tt>log level</tt></i> in your 
+To set the debug level use the <a class="indexterm" name="id2941026"></a><i class="parameter"><tt>log level</tt></i> in 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 add the following lines to your main <tt class="filename">smb.conf</tt> file:
@@ -15184,22 +15184,22 @@ then create a file
 <tt class="filename">/usr/local/samba/lib/smb.conf.<i class="replaceable"><tt>machine</tt></i></tt> where
 <i class="replaceable"><tt>machine</tt></i> is the name of the client you wish to debug. In that file
 put any <tt class="filename">smb.conf</tt> commands you want, for example 
-<a class="indexterm" name="id2870982"></a><i class="parameter"><tt>log level</tt></i> may be useful. This also allows you to 
+<a class="indexterm" name="id2941118"></a><i class="parameter"><tt>log level</tt></i> may be useful. This also allows you to 
 experiment with different security systems, protocol levels etc on just 
 one machine.
 </p><p>
-The <tt class="filename">smb.conf</tt> entry <a class="indexterm" name="id2871009"></a><i class="parameter"><tt>log level</tt></i> 
-is synonymous with the parameter <a class="indexterm" name="id2871023"></a><i class="parameter"><tt>debuglevel</tt></i> that has
+The <tt class="filename">smb.conf</tt> entry <a class="indexterm" name="id2941145"></a><i class="parameter"><tt>log level</tt></i> 
+is synonymous with the parameter <a class="indexterm" name="id2941160"></a><i class="parameter"><tt>debuglevel</tt></i> 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 <a class="indexterm" name="id2871049"></a><i class="parameter"><tt>log level</tt></i> value is increased you will record 
+As the <a class="indexterm" name="id2941186"></a><i class="parameter"><tt>log level</tt></i> 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 
 <tt class="constant">3</tt>. Nearly 
 all bugs can be tracked at a setting of <tt class="constant">10</tt>, but be 
 prepared for a VERY large volume of log data.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871078"></a>Internal errors</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941215"></a>Internal errors</h2></div></div><div></div></div><p>
 If you get a <span class="errorname">INTERNAL ERROR</span> 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
@@ -15212,12 +15212,12 @@ 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><a class="indexterm" name="id2871114"></a><p>
+</p><a class="indexterm" name="id2941250"></a><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><a class="indexterm" name="id2871136"></a><a class="indexterm" name="id2871145"></a><pre class="screen">
+</p><a class="indexterm" name="id2941273"></a><a class="indexterm" name="id2941281"></a><pre class="screen">
 <tt class="prompt">$ </tt><b class="userinput"><tt>gdb smbd core</tt></b>
 </pre><p>
 adding appropriate paths to smbd and core so gdb can find them. If you
@@ -15232,7 +15232,7 @@ disassemble the routine that called it) and try to work out exactly
 where the problem is by looking at the surrounding code. Even if you
 don't know assembly, including this info in the bug report can be
 useful. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871212"></a>Attaching to a running process</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941348"></a>Attaching to a running process</h2></div></div><div></div></div><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
@@ -15242,19 +15242,19 @@ to the running process using
 Then use <b class="command">c</b> 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871258"></a>Patches</h2></div></div><div></div></div><a class="indexterm" name="id2871266"></a><a class="indexterm" name="id2871274"></a><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941395"></a>Patches</h2></div></div><div></div></div><a class="indexterm" name="id2941403"></a><a class="indexterm" name="id2941411"></a><p>
 The best sort of bug report is one that includes a fix! If you send us
 patches please use <b class="userinput"><tt>diff -u</tt></b> format if your version of 
 diff supports it, otherwise use <b class="userinput"><tt>diff -c4</tt></b>. Make sure 
 you do the diff against a clean version of the source and let me know 
 exactly what version you used. 
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>36. <a href="#compiling">How to compile Samba</a></dt><dd><dl><dt><a href="#id2871417">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2871434">Introduction</a></dt><dt><a href="#id2871464">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2871712">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2871776">Verifying Samba's PGP signature</a></dt><dt><a href="#id2871926">Building the Binaries</a></dt><dd><dl><dt><a href="#id2872104">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2872271">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2872378">Starting from inetd.conf</a></dt><dt><a href="#id2872625">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2872789">HPUX</a></dt><dt><a href="#id2872876">SCO UNIX</a></dt><dt><a href="#id2872906">DNIX</a></dt><dt><a href="#id2943012">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943056">AIX</a></dt><dd><dl><dt><a href="#id2943063">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943089">Solaris</a></dt><dd><dl><dt><a href="#id2943096">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2943249">Macintosh clients?</a></dt><dt><a href="#id2943327">OS2 Client</a></dt><dd><dl><dt><a href="#id2943334">Configuring OS/2 Warp Connect or 
-			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943403">Configuring OS/2 Warp 3 (not Connect), 
-			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943455">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943555">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943563">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943653">Delete .pwl files after password change</a></dt><dt><a href="#id2943683">Configuring WfW password handling</a></dt><dt><a href="#id2943736">Case handling of passwords</a></dt><dt><a href="#id2943774">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943791">Speed improvement</a></dt></dl></dd><dt><a href="#id2943837">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2943911">Speed improvement</a></dt></dl></dd><dt><a href="#id2943935">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944122">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2944254">Comparisons</a></dt><dt><a href="#id2944298">Socket options</a></dt><dt><a href="#id2944388">Read size</a></dt><dt><a href="#id2944438">Max xmit</a></dt><dt><a href="#id2944498">Log level</a></dt><dt><a href="#id2944528">Read raw</a></dt><dt><a href="#id2944612">Write raw</a></dt><dt><a href="#id2944675">Slow Logins</a></dt><dt><a href="#id2944704">Client tuning</a></dt><dt><a href="#id2944729">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944774">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2944876">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2944943">Websites</a></dt><dt><a href="#id2945351">Related updates from Microsoft</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�36.�How to compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2871417">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2871434">Introduction</a></dt><dt><a href="#id2871464">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2871712">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2871776">Verifying Samba's PGP signature</a></dt><dt><a href="#id2871926">Building the Binaries</a></dt><dd><dl><dt><a href="#id2872104">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2872271">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2872378">Starting from inetd.conf</a></dt><dt><a href="#id2872625">Alternative: starting it as a daemon</a></dt></dl></dd></dl></div><p>
+</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>36. <a href="#compiling">How to compile Samba</a></dt><dd><dl><dt><a href="#id2941554">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2941570">Introduction</a></dt><dt><a href="#id2941600">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2941849">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2941913">Verifying Samba's PGP signature</a></dt><dt><a href="#id2942063">Building the Binaries</a></dt><dd><dl><dt><a href="#id2942242">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2942409">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2942516">Starting from inetd.conf</a></dt><dt><a href="#id2942763">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2942927">HPUX</a></dt><dt><a href="#id2943015">SCO UNIX</a></dt><dt><a href="#id2943044">DNIX</a></dt><dt><a href="#id2943217">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943261">AIX</a></dt><dd><dl><dt><a href="#id2943268">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943294">Solaris</a></dt><dd><dl><dt><a href="#id2943299">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2943452">Macintosh clients?</a></dt><dt><a href="#id2943531">OS2 Client</a></dt><dd><dl><dt><a href="#id2943538">Configuring OS/2 Warp Connect or 
+			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943607">Configuring OS/2 Warp 3 (not Connect), 
+			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943660">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943760">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943768">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943858">Delete .pwl files after password change</a></dt><dt><a href="#id2943888">Configuring WfW password handling</a></dt><dt><a href="#id2943941">Case handling of passwords</a></dt><dt><a href="#id2943979">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943996">Speed improvement</a></dt></dl></dd><dt><a href="#id2944042">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2944116">Speed improvement</a></dt></dl></dd><dt><a href="#id2944140">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944326">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2944458">Comparisons</a></dt><dt><a href="#id2944501">Socket options</a></dt><dt><a href="#id2944592">Read size</a></dt><dt><a href="#id2944641">Max xmit</a></dt><dt><a href="#id2944701">Log level</a></dt><dt><a href="#id2944732">Read raw</a></dt><dt><a href="#id2944816">Write raw</a></dt><dt><a href="#id2944879">Slow Logins</a></dt><dt><a href="#id2944908">Client tuning</a></dt><dt><a href="#id2944932">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944965">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2945070">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2945137">Websites</a></dt><dt><a href="#id2945545">Related updates from Microsoft</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter�36.�How to compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2941554">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2941570">Introduction</a></dt><dt><a href="#id2941600">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2941849">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2941913">Verifying Samba's PGP signature</a></dt><dt><a href="#id2942063">Building the Binaries</a></dt><dd><dl><dt><a href="#id2942242">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2942409">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2942516">Starting from inetd.conf</a></dt><dt><a href="#id2942763">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><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871417"></a>Access Samba source code via CVS</h2></div></div><div></div></div><a class="indexterm" name="id2871426"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871434"></a>Introduction</h3></div></div><div></div></div><p>
+</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941554"></a>Access Samba source code via CVS</h2></div></div><div></div></div><a class="indexterm" name="id2941562"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941570"></a>Introduction</h3></div></div><div></div></div><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
@@ -15263,12 +15263,12 @@ 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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871464"></a>CVS Access to samba.org</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941600"></a>CVS Access to samba.org</h3></div></div><div></div></div><p>
 The machine samba.org runs a publicly accessible CVS 
 repository for access to the source code of several packages, 
 including samba, rsync, distcc, ccache and jitterbug. There are two main ways
 of accessing the CVS server on this host.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871480"></a>Access via CVSweb</h4></div></div><div></div></div><a class="indexterm" name="id2871488"></a><p>
+</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2941616"></a>Access via CVSweb</h4></div></div><div></div></div><a class="indexterm" name="id2941625"></a><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 
@@ -15276,7 +15276,7 @@ history and commit logs of individual files. You can also ask for a diff
 listing between any two versions on the repository.
 </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" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871521"></a>Access via cvs</h4></div></div><div></div></div><p>
+</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2941658"></a>Access via cvs</h4></div></div><div></div></div><p>
 You can also access the source code via a 
 normal cvs client.  This gives you much more control over what you can 
 do with the repository and allows you to checkout whole source trees 
@@ -15326,7 +15326,7 @@ on this system just substitute the correct package name
 	the following command from within the samba directory: 
 	</p><p>
 	<b class="userinput"><tt>cvs update -d -P</tt></b>
-	</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871712"></a>Accessing the samba sources via rsync and ftp</h2></div></div><div></div></div><a class="indexterm" name="id2871720"></a><a class="indexterm" name="id2871729"></a><p>
+	</p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941849"></a>Accessing the samba sources via rsync and ftp</h2></div></div><div></div></div><a class="indexterm" name="id2941857"></a><a class="indexterm" name="id2941865"></a><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 
 	<a href="rsync://pserver.samba.org/ftp/unpacked/" target="_top">rsync://pserver.samba.org/ftp/unpacked/</a>. I recommend using rsync rather than ftp.
@@ -15335,7 +15335,7 @@ on this system just substitute the correct package name
 	The disadvantage of the unpacked trees is that they do not support automatic
 	merging of local changes like CVS does.  rsync access is most convenient 
 	for an initial install.                       
-	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871776"></a>Verifying Samba's PGP signature</h2></div></div><div></div></div><p>
+	</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941913"></a>Verifying Samba's PGP signature</h2></div></div><div></div></div><p>
 In these days of insecurity, it's strongly recommended that you verify the PGP
 signature for any source file before installing it. Even if you're not 
 downloading from a mirror site, verifying PGP signatures should be a
@@ -15346,7 +15346,7 @@ With that said, go ahead and download the following files:
 <tt class="prompt">$ </tt><b class="userinput"><tt>wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc</tt></b>
 <tt class="prompt">$ </tt><b class="userinput"><tt>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</tt></b>
 </pre><p>
-<a class="indexterm" name="id2871837"></a>
+<a class="indexterm" name="id2941973"></a>
 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="screen">
@@ -15365,13 +15365,13 @@ example of what you would not want to see would be:
 <tt class="computeroutput">
      gpg: BAD signature from "Samba Distribution Verification Key"
  </tt>
- </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871926"></a>Building the Binaries</h2></div></div><div></div></div><a class="indexterm" name="id2871933"></a><p>
+ </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942063"></a>Building the Binaries</h2></div></div><div></div></div><a class="indexterm" name="id2942071"></a><p>
 		To do this, first run the program <b class="userinput"><tt>./configure
 	</tt></b> 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><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>./configure --help
 </tt></b></pre><p>first to see what special options you can enable.
-	Then executing</p><a class="indexterm" name="id2871979"></a><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make</tt></b></pre><p>will create the binaries. Once it's successfully 
+	Then executing</p><a class="indexterm" name="id2942117"></a><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make</tt></b></pre><p>will create the binaries. Once it's successfully 
 	compiled you can use </p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make install</tt></b></pre><p>to install the binaries and manual pages. You can 
 	separately install the binaries and/or man pages using</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make installbin
 </tt></b></pre><p>and</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make installman
@@ -15379,7 +15379,7 @@ example of what you would not want to see would be:
 	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><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>make revert
-</tt></b></pre><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872104"></a>Compiling samba with Active Directory support</h3></div></div><div></div></div><p>In order to compile samba with ADS support, you need to have installed
+</tt></b></pre><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942242"></a>Compiling samba with Active Directory support</h3></div></div><div></div></div><p>In order to compile samba with ADS support, you need to have installed
 	on your system:</p><div class="itemizedlist"><ul type="disc"><li><p>the MIT kerberos development libraries
 	    (either install from the sources or use a package). The
 	    Heimdal libraries will not work.</p></li><li><p>the OpenLDAP development libraries.</p></li></ul></div><p>If your kerberos libraries are in a non-standard location then
@@ -15391,12 +15391,12 @@ example of what you would not want to see would be:
 #define HAVE_LDAP 1
 </pre><p>If it doesn't then configure did not find your krb5 libraries or
 	your ldap libraries. Look in <tt class="filename">config.log</tt> to figure
-	out why and fix it.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872186"></a>Installing the required packages for Debian</h4></div></div><div></div></div><p>On Debian you need to install the following packages:</p><p>
+	out why and fix it.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2942323"></a>Installing the required packages for Debian</h4></div></div><div></div></div><p>On Debian you need to install the following packages:</p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p>
-	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872217"></a>Installing the required packages for RedHat</h4></div></div><div></div></div><p>On RedHat this means you should have at least: </p><p>
+	</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2942355"></a>Installing the required packages for RedHat</h4></div></div><div></div></div><p>On RedHat this means you should have at least: </p><p>
 		</p><div class="itemizedlist"><ul type="disc"><li><p>krb5-workstation (for kinit)</p></li><li><p>krb5-libs (for linking with)</p></li><li><p>krb5-devel (because you are compiling from source)</p></li></ul></div><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 class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872271"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><a class="indexterm" name="id2872291"></a><p>You must choose to start <span class="application">smbd</span> and <span class="application">nmbd</span> either
+	to get them off CD2.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942409"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><a class="indexterm" name="id2942429"></a><p>You must choose to start <span class="application">smbd</span> and <span class="application">nmbd</span> 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
@@ -15409,7 +15409,7 @@ example of what you would not want to see would be:
 	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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872378"></a>Starting from inetd.conf</h3></div></div><div></div></div><a class="indexterm" name="id2872386"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if 
+	request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942516"></a>Starting from inetd.conf</h3></div></div><div></div></div><a class="indexterm" name="id2942524"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if 
 		you use NIS, NIS+ or LDAP to distribute services maps.</p></div><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><pre class="programlisting">netbios-ssn     139/tcp</pre><p>similarly for 137/udp you should have an entry like:</p><pre class="programlisting">netbios-ns	137/udp</pre><p>Next edit your <tt class="filename">/etc/inetd.conf</tt> 
@@ -15418,13 +15418,13 @@ example of what you would not want to see would be:
 		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
 		</pre><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><a class="indexterm" name="id2872476"></a><p>Some distributions use xinetd instead of inetd. Consult the 
+		for a guide. </p><a class="indexterm" name="id2942614"></a><p>Some distributions use xinetd instead of inetd. Consult the 
 		xinetd manual for configuration information.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><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></div><a class="indexterm" name="id2872519"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On many systems you may need to use the 
-		<a class="indexterm" name="id2872531"></a><i class="parameter"><tt>interfaces</tt></i> option in <tt class="filename">smb.conf</tt> to specify the IP
+		</p></div><a class="indexterm" name="id2942657"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On many systems you may need to use the 
+		<a class="indexterm" name="id2942669"></a><i class="parameter"><tt>interfaces</tt></i> 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
@@ -15437,7 +15437,7 @@ example of what you would not want to see would be:
 		from <b class="command">inetd</b>.</p></div><p>Restart <span class="application">inetd</span>, perhaps just send 
 			it a HUP. </p><pre class="screen">
 			<tt class="prompt">root# </tt><b class="userinput"><tt>killall -HUP inetd</tt></b>
-		</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872625"></a>Alternative: starting it as a daemon</h3></div></div><div></div></div><a class="indexterm" name="id2872633"></a><p>To start the server as a daemon you should create 
+		</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942763"></a>Alternative: starting it as a daemon</h3></div></div><div></div></div><a class="indexterm" name="id2942771"></a><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><pre class="programlisting">
 		#!/bin/sh
@@ -15449,9 +15449,9 @@ example of what you would not want to see would be:
 		</p><p>To kill it send a kill signal to the processes 
 			<span class="application">nmbd</span> and <span class="application">smbd</span>.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><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></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter�37.�Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2872789">HPUX</a></dt><dt><a href="#id2872876">SCO UNIX</a></dt><dt><a href="#id2872906">DNIX</a></dt><dt><a href="#id2943012">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943056">AIX</a></dt><dd><dl><dt><a href="#id2943063">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943089">Solaris</a></dt><dd><dl><dt><a href="#id2943096">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></div><p>Samba works on a wide range of platforms but the interface all the 
+		script to make Samba fit into that system.</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter�37.�Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2942927">HPUX</a></dt><dt><a href="#id2943015">SCO UNIX</a></dt><dt><a href="#id2943044">DNIX</a></dt><dt><a href="#id2943217">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2943261">AIX</a></dt><dd><dl><dt><a href="#id2943268">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2943294">Solaris</a></dt><dd><dl><dt><a href="#id2943299">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></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 
-platform-specific information about compiling and using samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872789"></a>HPUX</h2></div></div><div></div></div><p>
+platform-specific information about compiling and using samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2942927"></a>HPUX</h2></div></div><div></div></div><p>
 HP's implementation of supplementary groups is, er, non-standard (for
 hysterical reasons).  There are two group files, <tt class="filename">/etc/group</tt> and
 <tt class="filename">/etc/logingroup</tt>; the system maps UIDs to numbers using the former, but
@@ -15471,7 +15471,7 @@ allowed range.
 On HPUX you must use gcc or the HP ANSI compiler. The free compiler
 that comes with HP-UX is not ANSI compliant and cannot compile
 Samba.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872876"></a>SCO UNIX</h2></div></div><div></div></div><p> 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943015"></a>SCO UNIX</h2></div></div><div></div></div><p> 
 If you run an old version of SCO UNIX then you may need to get important 
 TCP/IP patches for Samba to work correctly. Without the patch, you may 
 encounter corrupt data transfers using samba.
@@ -15479,7 +15479,7 @@ encounter corrupt data transfers using samba.
 The patch you need is UOD385 Connection Drivers SLS. It is available from
 SCO (<a href="ftp://ftp.sco.com/" target="_top">ftp.sco.com</a>, directory SLS,
 files uod385a.Z and uod385a.ltr.Z).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872906"></a>DNIX</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943044"></a>DNIX</h2></div></div><div></div></div><p>
 DNIX has a problem with seteuid() and setegid(). These routines are
 needed for Samba to work correctly, but they were left out of the DNIX
 C library for some reason.
@@ -15538,7 +15538,7 @@ LIBSM = setegid.o seteuid.o -ln
 You should then remove the line:
 </p><pre class="programlisting">
 #define NO_EID
-</pre><p>from the DNIX section of <tt class="filename">includes.h</tt></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943012"></a>RedHat Linux Rembrandt-II</h2></div></div><div></div></div><p>
+</pre><p>from the DNIX section of <tt class="filename">includes.h</tt></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943217"></a>RedHat Linux Rembrandt-II</h2></div></div><div></div></div><p>
 By default RedHat Rembrandt-II during installation adds an
 entry to <tt class="filename">/etc/hosts</tt> as follows:
 </p><pre class="programlisting">
@@ -15552,10 +15552,10 @@ is the master browse list holder and who is the master browser.
 </p><p>
 Corrective Action:	Delete the entry after the word loopback
 	in the line starting 127.0.0.1
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943056"></a>AIX</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943063"></a>Sequential Read Ahead</h3></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943261"></a>AIX</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943268"></a>Sequential Read Ahead</h3></div></div><div></div></div><p>
 Disabling Sequential Read Ahead using <b class="userinput"><tt>vmtune -r 0</tt></b> improves 
 Samba performance significantly.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943089"></a>Solaris</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943096"></a>Locking improvements</h3></div></div><div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl 
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943294"></a>Solaris</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943299"></a>Locking improvements</h3></div></div><div></div></div><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 would try a lock, then fail,
@@ -15576,9 +15576,9 @@ and rebuild samba.
 Nsswitch on Solaris 9 refuses to use the winbind nss module.  This behavior
 is fixed by Sun in patch 113476-05 which as of March 2003 is not in any
 roll-up packages.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter�38.�Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><span class="contrib">OS/2</span><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2943249">Macintosh clients?</a></dt><dt><a href="#id2943327">OS2 Client</a></dt><dd><dl><dt><a href="#id2943334">Configuring OS/2 Warp Connect or 
-			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943403">Configuring OS/2 Warp 3 (not Connect), 
-			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943455">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943555">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943563">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943653">Delete .pwl files after password change</a></dt><dt><a href="#id2943683">Configuring WfW password handling</a></dt><dt><a href="#id2943736">Case handling of passwords</a></dt><dt><a href="#id2943774">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943791">Speed improvement</a></dt></dl></dd><dt><a href="#id2943837">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2943911">Speed improvement</a></dt></dl></dd><dt><a href="#id2943935">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944122">Windows NT 3.1</a></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943249"></a>Macintosh clients?</h2></div></div><div></div></div><p>
+</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter�38.�Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><span class="contrib">OS/2</span><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2943452">Macintosh clients?</a></dt><dt><a href="#id2943531">OS2 Client</a></dt><dd><dl><dt><a href="#id2943538">Configuring OS/2 Warp Connect or 
+			OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2943607">Configuring OS/2 Warp 3 (not Connect), 
+			OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2943660">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2943760">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2943768">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2943858">Delete .pwl files after password change</a></dt><dt><a href="#id2943888">Configuring WfW password handling</a></dt><dt><a href="#id2943941">Case handling of passwords</a></dt><dt><a href="#id2943979">Use TCP/IP as default protocol</a></dt><dt><a href="#id2943996">Speed improvement</a></dt></dl></dd><dt><a href="#id2944042">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2944116">Speed improvement</a></dt></dl></dd><dt><a href="#id2944140">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2944326">Windows NT 3.1</a></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943452"></a>Macintosh clients?</h2></div></div><div></div></div><p>
 	Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> now has a CIFS Client / Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a>
 </p><p>
 They test it against Windows 95, Windows NT and samba for
@@ -15598,7 +15598,7 @@ What Samba offers MS
 Windows users, these packages offer to Macs.  For more info on these
 packages, Samba, and Linux (and other UNIX-based systems) see
 <a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html</a>
-</p><p>Newer versions of the Macintosh (Mac OS X) include Samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943327"></a>OS2 Client</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943334"></a>Configuring OS/2 Warp Connect or 
+</p><p>Newer versions of the Macintosh (Mac OS X) include Samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943531"></a>OS2 Client</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943538"></a>Configuring OS/2 Warp Connect or 
 			OS/2 Warp 4 as a client for Samba</h3></div></div><div></div></div><p>Basically, you need three components:</p><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client ('IBM Peer')</p></li><li><p>TCP/IP ('Internet support') </p></li><li><p>The "NetBIOS over TCP/IP" driver ('TCPBEUI')</p></li></ul></div><p>Installing the first two together with the base operating 
 		system on a blank system is explained in the Warp manual. If Warp 
 		has already been installed, but you now want to install the 
@@ -15614,7 +15614,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 		to the "Names List", or specify a  WINS server ('NetBIOS 
 		Nameserver' in IBM and RFC terminology). For Warp Connect you 
 		may need to download an update for 'IBM Peer' to bring it on 
-		the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943403"></a>Configuring OS/2 Warp 3 (not Connect), 
+		the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943607"></a>Configuring OS/2 Warp 3 (not Connect), 
 			OS/2 1.2, 1.3 or 2.x for Samba</h3></div></div><div></div></div><p>You can use the free Microsoft LAN Manager 2.2c Client 
 		for OS/2 from 
 		<a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top">
@@ -15630,12 +15630,12 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 		or NS2000 driver from 
 		<a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top">
  		ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead.
-		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943455"></a>Printer driver download for for OS/2 clients?</h3></div></div><div></div></div><p>First, create a share called <i class="parameter"><tt>[PRINTDRV]</tt></i> that is 
+		</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943660"></a>Printer driver download for for OS/2 clients?</h3></div></div><div></div></div><p>First, create a share called <i class="parameter"><tt>[PRINTDRV]</tt></i> that is 
 		world-readable.  Copy your OS/2 driver files there.  Note 
 		that the .EA_ files must still be separate, so you will need 
 		to use the original install files, and not copy an installed 
 		driver from an OS/2 system.</p><p>Install the NT driver first for that printer.  Then, 
-			add to your <tt class="filename">smb.conf</tt> a parameter, <a class="indexterm" name="id2943489"></a><i class="parameter"><tt>os2 driver map</tt></i> = filename.  Then, in the file 
+			add to your <tt class="filename">smb.conf</tt> a parameter, <a class="indexterm" name="id2943694"></a><i class="parameter"><tt>os2 driver map</tt></i> = filename.  Then, in the file 
 		specified by <i class="replaceable"><tt>filename</tt></i>, map the 
 		name of the NT driver name to the OS/2 driver name as 
 		follows:</p><p><i class="parameter"><tt><i class="replaceable"><tt>nt driver name</tt></i> = <i class="replaceable"><tt>os2 driver name</tt></i>.<i class="replaceable"><tt>device name</tt></i></tt></i>, e.g.:</p><p><i class="parameter"><tt>
@@ -15645,7 +15645,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 		you the driver is not available.  On the second attempt, it 
 		will work.  This is fixed simply by adding the device name
   		 to the mapping, after which it will work on the first attempt.
-		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943555"></a>Windows for Workgroups</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943563"></a>Latest TCP/IP stack from Microsoft</h3></div></div><div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
+		</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943760"></a>Windows for Workgroups</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943768"></a>Latest TCP/IP stack from Microsoft</h3></div></div><div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows
 for Workgroups. 
 </p><p>The early TCP/IP stacks had lots of bugs.</p><p> 
 Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
@@ -15660,7 +15660,7 @@ fixed.  New files include <tt class="filename">WINSOCK.DLL</tt>,
 <tt class="filename">TRACERT.EXE</tt>, 
 <tt class="filename">NETSTAT.EXE</tt>, and 
 <tt class="filename">NBTSTAT.EXE</tt>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943653"></a>Delete .pwl files after password change</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943858"></a>Delete .pwl files after password change</h3></div></div><div></div></div><p>
 WfWg does a lousy job with passwords. I find that if I change my
 password on either the unix box or the PC the safest thing to do is to
 delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.
@@ -15669,19 +15669,19 @@ If you don't do this you may find that WfWg remembers and uses the old
 password, even if you told it a new one.
 </p><p> 
 Often WfWg will totally ignore a password you give it in a dialog box.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943683"></a>Configuring WfW password handling</h3></div></div><div></div></div><p>
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943888"></a>Configuring WfW password handling</h3></div></div><div></div></div><p>
 There is a program call admincfg.exe
 on the last disk (disk 8) of the WFW 3.11 disk set.  To install it
 type <b class="userinput"><tt>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</tt></b>.
 Then add an icon
 for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> Menu. 
 This program allows you to control how WFW handles passwords.  ie disable Password Caching etc
-for use with <a class="indexterm" name="id2943721"></a><i class="parameter"><tt>security</tt></i> = user
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943736"></a>Case handling of passwords</h3></div></div><div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <tt class="filename">smb.conf</tt> information on <a class="indexterm" name="id2943756"></a><i class="parameter"><tt>password level</tt></i> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943774"></a>Use TCP/IP as default protocol</h3></div></div><div></div></div><p>To support print queue reporting you may find
+for use with <a class="indexterm" name="id2943925"></a><i class="parameter"><tt>security</tt></i> = user
+</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943941"></a>Case handling of passwords</h3></div></div><div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <tt class="filename">smb.conf</tt> information on <a class="indexterm" name="id2943961"></a><i class="parameter"><tt>password level</tt></i> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943979"></a>Use TCP/IP as default protocol</h3></div></div><div></div></div><p>To support print queue reporting you may find
 that you have to use TCP/IP as the default protocol under
 WfWg. For some reason if you leave NetBEUI as the default
 it may break the print queue reporting on some systems.
-It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943791"></a>Speed improvement</h3></div></div><div></div></div><p>
+It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943996"></a>Speed improvement</h3></div></div><div></div></div><p>
 	Note that some people have found that setting <i class="parameter"><tt>DefaultRcvWindow</tt></i> in
 the <i class="parameter"><tt>[MSTCP]</tt></i> section of the 
 <tt class="filename">SYSTEM.INI</tt> file under WfWg to 3072 gives a
@@ -15692,7 +15692,7 @@ performance with a large value (16384 or larger). Other people have
 reported that anything over 3072 slows things down enormously. One
 person even reported a speed drop of a factor of 30 when he went from
 3072 to 8192. I don't know why.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943837"></a>Windows '95/'98</h2></div></div><div></div></div><p>
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944042"></a>Windows '95/'98</h2></div></div><div></div></div><p>
 When using Windows 95 OEM SR2 the following updates are recommended where Samba
 is being used. Please NOTE that the above change will affect you once these
 updates  have been installed.
@@ -15706,11 +15706,11 @@ install the <b class="command">OLEUPD.EXE</b> fix. This
 fix may stop your machine from hanging for an extended period when exiting
 Outlook and you may also notice a significant speedup when accessing network
 neighborhood services.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943911"></a>Speed improvement</h3></div></div><div></div></div><p>
+</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944116"></a>Speed improvement</h3></div></div><div></div></div><p>
 Configure the win95 TCPIP registry settings to give better
 performance. I use a program called <b class="command">MTUSPEED.exe</b> which I got off the
 net. There are various other utilities of this type freely available.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943935"></a>Windows 2000 Service Pack 2</h2></div></div><div></div></div><p> 
+</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944140"></a>Windows 2000 Service Pack 2</h2></div></div><div></div></div><p> 
 There are several annoyances with Windows 2000 SP2. One of which
 only appears when using a Samba server to host user profiles
 to Windows 2000 SP2 clients in a Windows domain.  This assumes
@@ -15719,7 +15719,7 @@ likely occur if it is not.
 </p><p> 
 In order to serve profiles successfully to Windows 2000 SP2 
 clients (when not operating as a PDC), Samba must have 
-<a class="indexterm" name="id2943956"></a><i class="parameter"><tt>nt acl support</tt></i> = no
+<a class="indexterm" name="id2944161"></a><i class="parameter"><tt>nt acl support</tt></i> = no
 added to the file share which houses the roaming profiles.
 If this is not done, then the Windows 2000 SP2 client will
 complain about not being able to access the profile (Access 
@@ -15727,11 +15727,11 @@ Denied) and create multiple copies of it on disk (DOMAIN.user.001,
 DOMAIN.user.002, etc...).  See the 
 <tt class="filename">smb.conf</tt> man page
 for more details on this option.  Also note that the 
-<a class="indexterm" name="id2943984"></a><i class="parameter"><tt>nt acl support</tt></i> parameter was formally a global parameter in
+<a class="indexterm" name="id2944189"></a><i class="parameter"><tt>nt acl support</tt></i> parameter was formally a global parameter in
 releases prior to Samba 2.2.2.
 </p><p> 
 The following is a minimal profile share:
-</p><div class="example"><a name="id2944007"></a><p class="title"><b>Example�38.1.�Minimal profile share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[profile]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export/profile</tt></i></td></tr><tr><td><i class="parameter"><tt>create mask = 0600</tt></i></td></tr><tr><td><i class="parameter"><tt>directory mask = 0700</tt></i></td></tr><tr><td><i class="parameter"><tt>nt acl support = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr></table></div><p>
+</p><div class="example"><a name="id2944212"></a><p class="title"><b>Example�38.1.�Minimal profile share</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[profile]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export/profile</tt></i></td></tr><tr><td><i class="parameter"><tt>create mask = 0600</tt></i></td></tr><tr><td><i class="parameter"><tt>directory mask = 0700</tt></i></td></tr><tr><td><i class="parameter"><tt>nt acl support = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr></table></div><p>
 The reason for this bug is that the Win2k SP2 client copies
 the security descriptor for the profile which contains
 the Samba server's SID, and not the domain SID.  The client
@@ -15739,15 +15739,15 @@ compares the SID for SAMBA\user and realizes it is
 different that the one assigned to DOMAIN\user.  Hence the reason
 for the <span class="errorname">access denied</span> message.
 </p><p>
-By disabling the <a class="indexterm" name="id2944087"></a><i class="parameter"><tt>nt acl support</tt></i> parameter, Samba will send
+By disabling the <a class="indexterm" name="id2944292"></a><i class="parameter"><tt>nt acl support</tt></i> 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><span class="emphasis"><em>DOMAIN\user 	"Full Control"</em></span>&gt;</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This bug does not occur when using winbind to
-create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944122"></a>Windows NT 3.1</h2></div></div><div></div></div><p>If you have problems communicating across routers with Windows 
+create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944326"></a>Windows NT 3.1</h2></div></div><div></div></div><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;Q103765" target="_top">this Microsoft Knowledge Base article</a>.
 
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter�39.�Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2944254">Comparisons</a></dt><dt><a href="#id2944298">Socket options</a></dt><dt><a href="#id2944388">Read size</a></dt><dt><a href="#id2944438">Max xmit</a></dt><dt><a href="#id2944498">Log level</a></dt><dt><a href="#id2944528">Read raw</a></dt><dt><a href="#id2944612">Write raw</a></dt><dt><a href="#id2944675">Slow Logins</a></dt><dt><a href="#id2944704">Client tuning</a></dt><dt><a href="#id2944729">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944774">Corrupt tdb Files</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944254"></a>Comparisons</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter�39.�Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2944458">Comparisons</a></dt><dt><a href="#id2944501">Socket options</a></dt><dt><a href="#id2944592">Read size</a></dt><dt><a href="#id2944641">Max xmit</a></dt><dt><a href="#id2944701">Log level</a></dt><dt><a href="#id2944732">Read raw</a></dt><dt><a href="#id2944816">Write raw</a></dt><dt><a href="#id2944879">Slow Logins</a></dt><dt><a href="#id2944908">Client tuning</a></dt><dt><a href="#id2944932">Samba performance problem due changing kernel</a></dt><dt><a href="#id2944965">Corrupt tdb Files</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944458"></a>Comparisons</h2></div></div><div></div></div><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
@@ -15769,14 +15769,14 @@ suspect the biggest factor is not Samba vs some other system but the
 hardware and drivers used on the various systems. Given similar
 hardware Samba should certainly be competitive in speed with other
 systems.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944298"></a>Socket options</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944501"></a>Socket options</h2></div></div><div></div></div><p>
 There are a number of socket options that can greatly affect the
 performance of a TCP based server like Samba.
 </p><p>
 The socket options that Samba uses are settable both on the command
 line with the <tt class="option">-O</tt> option, or in the <tt class="filename">smb.conf</tt> file.
 </p><p>
-The <a class="indexterm" name="id2944331"></a><i class="parameter"><tt>socket options</tt></i> section of the <tt class="filename">smb.conf</tt> manual page describes how
+The <a class="indexterm" name="id2944535"></a><i class="parameter"><tt>socket options</tt></i> section of the <tt class="filename">smb.conf</tt> manual page describes how
 to set these and gives recommendations.
 </p><p>
 Getting the socket options right can make a big difference to your
@@ -15785,11 +15785,11 @@ much. The correct settings are very dependent on your local network.
 </p><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 <a class="indexterm" name="id2944368"></a><i class="parameter"><tt>socket options</tt></i> = TCP_NODELAY doubles the read 
+adding <a class="indexterm" name="id2944572"></a><i class="parameter"><tt>socket options</tt></i> = 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="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944388"></a>Read size</h2></div></div><div></div></div><p>
-The option <a class="indexterm" name="id2944398"></a><i class="parameter"><tt>read size</tt></i> affects the overlap of disk
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944592"></a>Read size</h2></div></div><div></div></div><p>
+The option <a class="indexterm" name="id2944601"></a><i class="parameter"><tt>read size</tt></i> 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
@@ -15805,10 +15805,10 @@ The default value is 16384, but very little experimentation has been
 done yet to determine the optimal value, and it is likely that the best
 value will vary greatly between systems anyway. A value over 65536 is
 pointless and will cause you to allocate memory unnecessarily.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944438"></a>Max xmit</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944641"></a>Max xmit</h2></div></div><div></div></div><p>
 	At startup the client and server negotiate a <i class="parameter"><tt>maximum transmit</tt></i> size,
 which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the <a class="indexterm" name="id2944459"></a><i class="parameter"><tt>max xmit</tt></i> option
+maximum size that Samba will negotiate using the <a class="indexterm" name="id2944662"></a><i class="parameter"><tt>max xmit</tt></i> option
 in <tt class="filename">smb.conf</tt>. Note that this is the maximum size of SMB requests that 
 Samba will accept, but not the maximum size that the *client* will accept.
 The client maximum receive size is sent to Samba by the client and Samba
@@ -15819,41 +15819,41 @@ clients may perform better with a smaller transmit unit. Trying values
 of less than 2048 is likely to cause severe problems.
 </p><p>
 In most cases the default is the best option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944498"></a>Log level</h2></div></div><div></div></div><p>
-If you set the log level (also known as <a class="indexterm" name="id2944508"></a><i class="parameter"><tt>debug level</tt></i>) higher than 2
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944701"></a>Log level</h2></div></div><div></div></div><p>
+If you set the log level (also known as <a class="indexterm" name="id2944711"></a><i class="parameter"><tt>debug level</tt></i>) 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944528"></a>Read raw</h2></div></div><div></div></div><p>
-The <a class="indexterm" name="id2944538"></a><i class="parameter"><tt>read raw</tt></i> operation is designed to be an optimised, low-latency
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944732"></a>Read raw</h2></div></div><div></div></div><p>
+The <a class="indexterm" name="id2944742"></a><i class="parameter"><tt>read raw</tt></i> 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 <a class="indexterm" name="id2944554"></a><i class="parameter"><tt>read raw</tt></i> optional, with it
+however. and Samba makes support for <a class="indexterm" name="id2944758"></a><i class="parameter"><tt>read raw</tt></i> optional, with it
 being enabled by default.
 </p><p>
-In some cases clients don't handle <a class="indexterm" name="id2944572"></a><i class="parameter"><tt>read raw</tt></i> very well and actually
+In some cases clients don't handle <a class="indexterm" name="id2944776"></a><i class="parameter"><tt>read raw</tt></i> 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 <a class="indexterm" name="id2944594"></a><i class="parameter"><tt>read raw</tt></i> = no and see what happens on your
+So you might like to try <a class="indexterm" name="id2944797"></a><i class="parameter"><tt>read raw</tt></i> = 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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944612"></a>Write raw</h2></div></div><div></div></div><p>
-The <a class="indexterm" name="id2944622"></a><i class="parameter"><tt>write raw</tt></i> operation is designed to be an optimised, low-latency
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944816"></a>Write raw</h2></div></div><div></div></div><p>
+The <a class="indexterm" name="id2944826"></a><i class="parameter"><tt>write raw</tt></i> 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 <a class="indexterm" name="id2944639"></a><i class="parameter"><tt>write raw</tt></i> optional, with it
+however. and Samba makes support for <a class="indexterm" name="id2944843"></a><i class="parameter"><tt>write raw</tt></i> optional, with it
 being enabled by default.
 </p><p>
-Some machines may find <a class="indexterm" name="id2944657"></a><i class="parameter"><tt>write raw</tt></i> slower than normal write, in which
+Some machines may find <a class="indexterm" name="id2944861"></a><i class="parameter"><tt>write raw</tt></i> slower than normal write, in which
 case you may wish to change this option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944675"></a>Slow Logins</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944879"></a>Slow Logins</h2></div></div><div></div></div><p>
 Slow logins are almost always due to the password checking time. Using
-the lowest practical <a class="indexterm" name="id2944687"></a><i class="parameter"><tt>password level</tt></i> will improve things. 
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944704"></a>Client tuning</h2></div></div><div></div></div><p>
+the lowest practical <a class="indexterm" name="id2944890"></a><i class="parameter"><tt>password level</tt></i> will improve things. 
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944908"></a>Client tuning</h2></div></div><div></div></div><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. Check the sections on the various clients in 
 <a href="#Other-Clients" title="Chapter�38.�Samba and other CIFS clients">Samba and Other Clients</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944729"></a>Samba performance problem due changing kernel</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944932"></a>Samba performance problem due changing kernel</h2></div></div><div></div></div><p>
 Hi everyone. I am running Gentoo on my server and samba 2.2.8a. Recently
 I changed kernel version from linux-2.4.19-gentoo-r10 to
 linux-2.4.20-wolk4.0s. And now I have performance issue with samba. Ok
@@ -15868,7 +15868,7 @@ Grab mii-tool and check the duplex settings on the NIC.
 My guess is that it is a link layer issue, not an application
 layer problem.  Also run ifconfig and verify that the framing
 error, collisions, etc... look normal for ethernet.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944774"></a>Corrupt tdb Files</h2></div></div><div></div></div><p>
+</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944965"></a>Corrupt tdb Files</h2></div></div><div></div></div><p>
 Well today it happened, Our first major problem using samba.
 Our samba PDC server has been hosting 3 TB of data to our 500+ users
 [Windows NT/XP]  for the last 3 years using samba, no problem.
@@ -15886,10 +15886,10 @@ Q2) What I also would like to mention is that the service latency seems
 a lot lower then before the locks cleanup, any ideas on keeping it top notch?
 </p><p>
 A2) Yes! Same answer as for Q1!
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter�40.�DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2944876">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944876"></a>Note</h2></div></div><div></div></div><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter�40.�DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2945070">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2945070"></a>Note</h2></div></div><div></div></div><p>
 This chapter did not make it into this release.
 It is planned for the published release of this document.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Further-Resources"></a>Chapter�41.�Further Resources</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 1, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2944943">Websites</a></dt><dt><a href="#id2945351">Related updates from Microsoft</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944943"></a>Websites</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Further-Resources"></a>Chapter�41.�Further Resources</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email">&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">May 1, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2945137">Websites</a></dt><dt><a href="#id2945545">Related updates from Microsoft</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2945137"></a>Websites</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
 	<a href="http://hr.uoregon.edu/davidrl/cifs.txt" target="_top">
 	<span class="emphasis"><em>CIFS: Common Insecurities Fail Scrutiny</em></span> by "Hobbit"</a>
 	</p></li><li><p>
@@ -15981,7 +15981,7 @@ It is planned for the published release of this document.
 				<span class="emphasis"><em>W2K Samba deploy HOWTO</em></span>
 				by Arnaud Loonstra
 	</a>
-	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2945351"></a>Related updates from Microsoft</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+	</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2945545"></a>Related updates from Microsoft</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
 	<a href="http://support.microsoft.com/support/kb/articles/q92/5/88.asp" target="_top">
 		<span class="emphasis"><em>Enhanced Encryption for Windows 95 Password Cache</em></span> 
 	</a>
@@ -15993,42 +15993,42 @@ It is planned for the published release of this document.
 	<a href="http://support.microsoft.com/support/kb/articles/q136/4/18.asp" target="_top">
 		<span class="emphasis"><em>Windows for Workgroups Sharing Updates</em></span>
 	</a>
-	</p></li></ul></div></div></div></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2945421"></a>Index</h2></div></div><div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>"Domain Admins" group, <a href="#id2887722">Discussion</a></dt><dt>"Domain Users" group, <a href="#id2888294">Adding Domain Users to the Power Users group</a></dt><dt>"Printers" folder, <a href="#id2914749">Caveats to be considered</a>, <a href="#id2915946">Installing the PostScript Driver on a Client</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt>"raw" printing, <a href="#id2908431">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</a></dt><dt>/etc/host.conf, <a href="#id2934762">/etc/host.conf</a></dt><dt>/etc/hosts, <a href="#id2934577">/etc/hosts</a></dt><dt>/etc/nsswitch.conf, <a href="#id2934813">/etc/nsswitch.conf</a></dt><dt>8.3</dt><dd><dl><dt>file names, <a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>ACLs, <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dt>Active Directory, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>add group script, <a href="#id2888199">Adding Groups Fails</a></dt><dt>add machine script, <a href="#id2873520">The machine trust account not accessible</a>, <a href="#id2877258">Adding Machine to Domain Fails</a></dt><dt>add printer command, <a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt>add printer wizard, <a href="#id2908739">Three familiar Methods for driver upload plus a new one</a></dt><dt>add user script, <a href="#id2883502">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>addprinter command, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>admin users, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2892503">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt>Administrator, <a href="#id2887722">Discussion</a></dt><dt>ADS (see Active Directory)</dt><dt>ads server, <a href="#id2876674">Setup your smb.conf</a></dt><dt>application/cups.vnd-postscript, <a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/octet-stream, <a href="#id2908552">Explicitly enable "raw" printing for
-application/octet-stream!</a>, <a href="#id2910165">MIME type Conversion Rules</a>, <a href="#id2911697">"application/octet-stream" printing</a></dt><dt>application/pdf, <a href="#id2909959">MIME types and CUPS Filters</a></dt><dt>application/postscript, <a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/vnd.cups-raster, <a href="#id2911929">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt>application/vnd.cups-raw, <a href="#id2908552">Explicitly enable "raw" printing for
-application/octet-stream!</a></dt><dt>auth methods, <a href="#id2887258">auth methods does not work</a>, <a href="#id2937791">Passdb Backends and Authentication</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>bind interfaces only, <a href="#id2940846">The tests</a></dt><dt>brlock.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>browse list, <a href="#id2878408">What is Browsing?</a>, <a href="#id2881481">Technical Overview of browsing</a></dt><dt>browseable, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a>, <a href="#id2901686">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>case sensitive, <a href="#id2890173">Miscellaneous Controls</a>, <a href="#id2928828">Windows 9x / Me Profile Setup</a></dt><dt>chpass, <a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt>comment, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a>, <a href="#id2901686">Parameters in the [print$] Section</a></dt><dt>configure, <a href="#id2871926">Building the Binaries</a></dt><dt>connections.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>core files, <a href="#id2871078">Internal errors</a></dt><dt>create mask, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>csc policy, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>CUPS</dt><dd><dl><dt>Page Accounting, <a href="#id2920055">Page Accounting with CUPS</a></dt><dt>quotas, <a href="#id2920098">Setting up Quotas</a></dt></dl></dd><dt>CUPS-PPD, <a href="#id2919108">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>cupsaddsmb, <a href="#id2908739">Three familiar Methods for driver upload plus a new one</a>, <a href="#id2913913">cupsaddsmb: the unknown Utility</a>, <a href="#id2914749">Caveats to be considered</a>, <a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2915344">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2915567">Understanding cupsaddsmb</a>, <a href="#id2915798">cupsaddsmb with a Samba PDC</a>, <a href="#id2915877">cupsaddsmb Flowchart</a></dt><dt>cupsomatic, <a href="#id2909654">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="#id2909782">The CUPS Filtering Architecture</a>, <a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a>, <a href="#id2919108">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>CVS, <a href="#id2871417">Access Samba source code via CVS</a></dt><dd><dl><dt>web, <a href="#id2871480">Access via CVSweb</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a href="#id2872625">Alternative: starting it as a daemon</a></dt><dt>DDK, <a href="#id2913833">PostScript Drivers with no major problems -- even in Kernel
-Mode</a>, <a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>debug, <a href="#id2871078">Internal errors</a></dt><dt>debug level, <a href="#id2942341">Debugging with Samba itself</a>, <a href="#id2944498">Log level</a></dt><dt>debuglevel, <a href="#id2870870">Debug levels</a></dt><dt>default case, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>delete printer command, <a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt>deleteprinter command, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>DHCP, <a href="#id2934457">Background Information</a></dt><dt>diff, <a href="#id2871258">Patches</a></dt><dt>directory mask, <a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt>directory security mask, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>disable spoolss, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>display charset, <a href="#id2936097">Samba and charsets</a></dt><dt>DNS, <a href="#id2878972">TCP/IP - without NetBIOS</a>, <a href="#id2935528">DNS Lookup</a></dt><dd><dl><dt>Active Directory, <a href="#id2879137">DNS and Active Directory</a></dt><dt>Dynamic, <a href="#id2934457">Background Information</a></dt></dl></dd><dt>dns proxy, <a href="#id2878408">What is Browsing?</a></dt><dt>domain admin group, <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dt>domain logons, <a href="#id2870592">Preparing for Domain Control</a></dt><dt>domain master, <a href="#id2869000">Domain Network Logon Service</a>, <a href="#id2874464">Example Configuration</a>, <a href="#id2878408">What is Browsing?</a>, <a href="#id2880217">Making Samba the domain master</a></dt><dt>dont descend, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>dos charset, <a href="#id2936097">Samba and charsets</a>, <a href="#id2936254">Japanese charsets</a>, <a href="#id2936398">CP850.so can't be found</a></dt><dt>dos filemode, <a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt>dos filetime resolution, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>dos filetimes, <a href="#id2890173">Miscellaneous Controls</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>EMF, <a href="#id2909034">Windows Drivers, GDI and EMF</a>, <a href="#id2912965">From Windows Clients to an NT Print Server</a>, <a href="#id2913090">Driver Execution on the Server</a></dt><dt>encrypt passwords, <a href="#id2876053">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2884279">smbpasswd - Encrypted Password Database</a>, <a href="#id2933539">smb.conf PAM Configuration</a>, <a href="#id2940846">The tests</a></dt><dt>enhanced browsing, <a href="#id2878408">What is Browsing?</a></dt><dt>enumports command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2906300">Samba and Printer Ports</a></dt><dt>EPM (see ESP meta packager)</dt><dt>ESC/P, <a href="#id2913090">Driver Execution on the Server</a></dt><dt>ESP</dt><dd><dl><dt>Ghostscript, <a href="#id2909782">The CUPS Filtering Architecture</a>, <a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a></dt><dt>meta packager, <a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>Print Pro, <a href="#id2912731">Sources of CUPS drivers / PPDs</a>, <a href="#id2914689">ESP Print Pro Package of "PostScript Driver for
-WinNT/2k/XP"</a></dt></dl></dd><dt>Extended Attributes, <a href="#AccessControls">File, Directory and Share Access Controls</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fake oplocks, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>File System, <a href="#id2888688">File System Access Controls</a></dt><dt>foomatic, <a href="#id2909654">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="#id2909782">The CUPS Filtering Architecture</a>, <a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a>, <a href="#id2918890">foomatic-rip and Foomatic explained</a>, <a href="#id2919032">Foomatic's strange Name</a></dt><dt>foomatic-rip, <a href="#id2912192">Difference between cupsomatic/foomatic-rip and
-native CUPS printing</a>, <a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a>, <a href="#id2918890">foomatic-rip and Foomatic explained</a>, <a href="#id2919272">The Grand Unification
-achieved...</a></dt><dt>force create mode, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>force directory mode, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>force directory security mode, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>force group, <a href="#id2889373">User and Group Based Controls</a></dt><dt>force security mode, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>force user, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2892503">I have set force user but Samba still makes root the owner of all the files I touch!</a>, <a href="#id2893471">Beware of Force User</a></dt><dt>ftp, <a href="#id2871712">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gdb, <a href="#id2871078">Internal errors</a></dt><dt>GDI, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2909034">Windows Drivers, GDI and EMF</a>, <a href="#id2912965">From Windows Clients to an NT Print Server</a>, <a href="#id2913090">Driver Execution on the Server</a></dt><dt>GhostScript, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2909441">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dd><dl><dt>(see also PostScript)</dt></dl></dd><dt>Ghostscript</dt><dd><dl><dt>ESP (see ESP GhostScript)</dt></dl></dd><dt>GID, <a href="#id2887487">Features and Benefits</a></dt><dt>GPG, <a href="#id2871776">Verifying Samba's PGP signature</a></dt><dt>groupadd, <a href="#id2887487">Features and Benefits</a></dt><dt>groupdel, <a href="#id2887487">Features and Benefits</a></dt><dt>groups</dt><dd><dl><dt>domain, <a href="#id2887722">Discussion</a></dt><dt>mapping, <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dt>nested, <a href="#id2888268">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd><dt>guest account, <a href="#id2881662">Problem resolution</a>, <a href="#id2882497">My client reports "This server is not configured to list shared resources"</a>, <a href="#id2899274">The [printers] Section</a></dt><dt>guest ok, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a>, <a href="#id2901686">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hide dot files, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>hide files, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>hide unreadable, <a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt>hide unwriteable files, <a href="#id2889794">File and Directory Permissions Based Controls</a></dt><dt>host msdfs, <a href="#id2896731">Features and Benefits</a></dt><dt>hosts allow, <a href="#id2895003">Using host based protection</a>, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2899717">Any [my_printer_name] Section</a></dt><dt>hosts deny, <a href="#id2895003">Using host based protection</a>, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2899717">Any [my_printer_name] Section</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>idmap gid, <a href="#id2887487">Features and Benefits</a>, <a href="#id2934194">Winbind is not resolving users and groups</a></dt><dt>idmap uid, <a href="#id2887487">Features and Benefits</a>, <a href="#id2934194">Winbind is not resolving users and groups</a></dt><dt>ifconfig, <a href="#id2872378">Starting from inetd.conf</a></dt><dt>imprints, <a href="#id2908739">Three familiar Methods for driver upload plus a new one</a></dt><dt>inetd, <a href="#id2940846">The tests</a>, <a href="#id2872271">Starting the smbd and nmbd</a>, <a href="#id2872378">Starting from inetd.conf</a></dt><dt>Interdomain Trusts, <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt>completing, <a href="#id2896007">Completing an NT4 Domain Trust</a></dt><dt>creating, <a href="#id2895908">Native MS Windows NT4 Trusts Configuration</a></dt><dt>Facilities, <a href="#id2896054">Inter-Domain Trust Facilities</a></dt></dl></dd><dt>interfaces, <a href="#id2880412">Multiple interfaces</a>, <a href="#id2940846">The tests</a>, <a href="#id2872378">Starting from inetd.conf</a></dt><dt>invalid users, <a href="#id2889373">User and Group Based Controls</a></dt><dt>IPP, <a href="#id2915567">Understanding cupsaddsmb</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KDC, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>Kerberos, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>kinit, <a href="#id2876803">Setup your /etc/krb5.conf</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>ldap admin dn, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap delete dn, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap filter, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap machine suffix, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap passwd sync, <a href="#id2885030">Configuring Samba</a>, <a href="#id2886130">Password synchronisation</a></dt><dt>ldap ssl, <a href="#id2885030">Configuring Samba</a>, <a href="#id2885464">Security and sambaSamAccount</a></dt><dt>ldap suffix, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap trust ids, <a href="#id2885030">Configuring Samba</a></dt><dt>ldap user suffix, <a href="#id2885030">Configuring Samba</a></dt><dt>libnss_wins.so, <a href="#id2934813">/etc/nsswitch.conf</a></dt><dt>Links</dt><dd><dl><dt>hard, <a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>soft, <a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>Linuxprinting.org, <a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a></dt><dt>lm announce, <a href="#id2878408">What is Browsing?</a></dt><dt>lm interval, <a href="#id2878408">What is Browsing?</a></dt><dt>LMB (see Local Master Browser)</dt><dt>LMHOSTS, <a href="#id2935248">The LMHOSTS file</a></dt><dt>load printers, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898105">A little Experiment to warn you</a>, <a href="#id2898782">The [global] Section</a></dt><dt>local master, <a href="#id2878408">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt>Local Master Browser, <a href="#id2880448">Use of the Remote Announce parameter</a></dt><dt>locking, <a href="#id2892860">Discussion</a></dt><dt>locking.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>log files</dt><dd><dl><dt>monitoring, <a href="#id2940619">Assumptions</a></dt></dl></dd><dt>log level, <a href="#id2877258">Adding Machine to Domain Fails</a>, <a href="#id2923166">extd_audit</a>, <a href="#id2870870">Debug levels</a></dt><dt>logon drive, <a href="#id2929364">Windows NT4 Workstation</a></dt><dt>logon home, <a href="#id2885623">LDAP special attributes for sambaSamAccounts</a>, <a href="#id2928450">Windows 9x / Me User Profiles</a>, <a href="#id2928582">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="#id2929364">Windows NT4 Workstation</a>, <a href="#id2930060">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon path, <a href="#id2885623">LDAP special attributes for sambaSamAccounts</a>, <a href="#id2928582">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="#id2928828">Windows 9x / Me Profile Setup</a>, <a href="#id2929364">Windows NT4 Workstation</a>, <a href="#id2930060">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon script, <a href="#id2885623">LDAP special attributes for sambaSamAccounts</a></dt><dt>lpadmin, <a href="#id2918753">CUPS Print Drivers from Linuxprinting.org</a>, <a href="#id2920098">Setting up Quotas</a></dt><dt>lppause command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2920874">Pre-conditions</a></dt><dt>lpq cache time, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a></dt><dt>lpq command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2920874">Pre-conditions</a></dt><dt>lpresume command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2920874">Pre-conditions</a></dt><dt>lprm command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2920874">Pre-conditions</a></dt><dt>lpstat, <a href="#id2918021">Troubleshooting revisited</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>MAC Addresses, <a href="#id2934577">/etc/hosts</a></dt><dt>machine trust accounts, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt>creating, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>make, <a href="#id2871926">Building the Binaries</a></dt><dt>mangling method, <a href="#id2936254">Japanese charsets</a></dt><dt>map to guest, <a href="#id2901686">Parameters in the [print$] Section</a>, <a href="#id2905621">Adding new Printers with the Windows NT APW</a>, <a href="#id2921688">Can't reconnect to Samba under new account
-			from Win2K/XP</a>, <a href="#id2921914">Avoid being connected to the Samba server as the
-		"wrong" user</a></dt><dt>max print jobs, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>max xmit, <a href="#id2944438">Max xmit</a></dt><dt>messages.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>MIME, <a href="#id2909959">MIME types and CUPS Filters</a>, <a href="#id2910165">MIME type Conversion Rules</a>, <a href="#id2910315">Filter Requirements</a>, <a href="#id2911697">"application/octet-stream" printing</a></dt><dt>min print space, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>msdfs root, <a href="#id2896731">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>name resolve order, <a href="#id2878408">What is Browsing?</a></dt><dt>nbtstat, <a href="#id2935185">The NetBIOS Name Cache</a></dt><dt>NetBIOS, <a href="#id2878319">Features and Benefits</a>, <a href="#id2878972">TCP/IP - without NetBIOS</a>, <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a>, <a href="#id2934918">Name resolution as used within MS Windows networking</a></dt><dt>NetBIOS-less, <a href="#id2878972">TCP/IP - without NetBIOS</a></dt><dt>nmblookup, <a href="#id2935185">The NetBIOS Name Cache</a></dt><dt>nt acl support, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891057">Viewing file ownership</a>, <a href="#id2891188">Viewing File or Directory Permissions</a>, <a href="#id2891423">Modifying file or directory permissions</a>, <a href="#id2943935">Windows 2000 Service Pack 2</a></dt><dt>ntdrivers.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>ntforms.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTFS, <a href="#id2888688">File System Access Controls</a></dt><dt>ntprinters.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>obey pam restrictions, <a href="#id2933539">smb.conf PAM Configuration</a></dt><dt>only user, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2895500">Why can users access home directories of other users?</a></dt><dt>oplock break wait time, <a href="#id2893563">Advanced Samba Opportunistic Locking Parameters</a>, <a href="#id2893897">Disabling Kernel OpLocks</a></dt><dt>oplock contention limit, <a href="#id2893563">Advanced Samba Opportunistic Locking Parameters</a></dt><dt>os level, <a href="#id2878408">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a>, <a href="#id2879819">Setting up DOMAIN Browsing</a>, <a href="#browse-force-master">Forcing Samba to be the master</a>, <a href="#id2880217">Making Samba the domain master</a></dt><dt>os2 driver map, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2943455">Printer driver download for for OS/2 clients?</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>page_log, <a href="#id2920282">The page_log File Syntax</a></dt><dt>passdb backend, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="#passdb">Account Information Databases</a>, <a href="#id2883109">Technical Information</a>, <a href="#id2883959">The pdbedit Command</a>, <a href="#id2885030">Configuring Samba</a>, <a href="#id2886336">Configuring</a>, <a href="#id2887102">Users can not logon</a>, <a href="#id2887258">auth methods does not work</a>, <a href="#id2937791">Passdb Backends and Authentication</a></dt><dt>password level, <a href="#id2869450">Password checking</a>, <a href="#id2940846">The tests</a>, <a href="#id2943736">Case handling of passwords</a>, <a href="#id2944675">Slow Logins</a></dt><dt>password server, <a href="#id2852521">Server Security (User Level Security)</a>, <a href="#id2873169">Security Mode and Master Browsers</a>, <a href="#id2876053">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2940846">The tests</a></dt><dt>patch, <a href="#id2871258">Patches</a></dt><dt>path, <a href="#id2859124">"The network name cannot be found"</a>, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a>, <a href="#id2900032">Print Commands</a>, <a href="#id2901502">Creating the [print$] Share</a>, <a href="#id2901686">Parameters in the [print$] Section</a>, <a href="#id2901973">Subdirectory Structure in [print$]</a>, <a href="#id2913432">Samba receiving Jobfiles and passing them to CUPS</a>, <a href="#id2920734">Auto-Deletion or Preservation of CUPS Spool Files</a>, <a href="#id2922506">Permissions on
+	</p></li></ul></div></div></div></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2945614"></a>Index</h2></div></div><div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>"Domain Admins" group, <a href="#id2885202">Discussion</a></dt><dt>"Domain Users" group, <a href="#id2885768">Adding Domain Users to the Power Users group</a></dt><dt>"Printers" folder, <a href="#id2912362">Caveats to be considered</a>, <a href="#id2913497">Installing the PostScript Driver on a Client</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt>"raw" printing, <a href="#id2905999">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</a></dt><dt>/etc/host.conf, <a href="#id2932499">/etc/host.conf</a></dt><dt>/etc/hosts, <a href="#id2932315">/etc/hosts</a></dt><dt>/etc/nsswitch.conf, <a href="#id2932551">/etc/nsswitch.conf</a></dt><dt>8.3</dt><dd><dl><dt>file names, <a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>ACLs, <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dt>Active Directory, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>add group script, <a href="#id2885674">Adding Groups Fails</a></dt><dt>add machine script, <a href="#id2871029">The machine trust account not accessible</a>, <a href="#id2874764">Adding Machine to Domain Fails</a></dt><dt>add printer command, <a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt>add printer wizard, <a href="#id2906306">Three familiar Methods for driver upload plus a new one</a></dt><dt>add user script, <a href="#id2880966">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>addprinter command, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>admin users, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2889969">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt>Administrator, <a href="#id2885202">Discussion</a></dt><dt>ADS (see Active Directory)</dt><dt>ads server, <a href="#id2874178">Setup your smb.conf</a></dt><dt>application/cups.vnd-postscript, <a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/octet-stream, <a href="#id2906119">Explicitly enable "raw" printing for
+application/octet-stream!</a>, <a href="#id2907752">MIME type Conversion Rules</a>, <a href="#id2909312">"application/octet-stream" printing</a></dt><dt>application/pdf, <a href="#id2907545">MIME types and CUPS Filters</a></dt><dt>application/postscript, <a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/vnd.cups-raster, <a href="#id2909544">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt>application/vnd.cups-raw, <a href="#id2906119">Explicitly enable "raw" printing for
+application/octet-stream!</a></dt><dt>auth methods, <a href="#id2884738">auth methods does not work</a>, <a href="#id2935529">Passdb Backends and Authentication</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>bind interfaces only, <a href="#id2938586">The tests</a></dt><dt>brlock.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>browse list, <a href="#id2875904">What is Browsing?</a>, <a href="#id2878986">Technical Overview of browsing</a></dt><dt>browseable, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a>, <a href="#id2899189">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>case sensitive, <a href="#id2887639">Miscellaneous Controls</a>, <a href="#id2926538">Windows 9x / Me Profile Setup</a></dt><dt>chpass, <a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt>comment, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a>, <a href="#id2899189">Parameters in the [print$] Section</a></dt><dt>configure, <a href="#id2942063">Building the Binaries</a></dt><dt>connections.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>core files, <a href="#id2941215">Internal errors</a></dt><dt>create mask, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>csc policy, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>CUPS</dt><dd><dl><dt>Page Accounting, <a href="#id2917602">Page Accounting with CUPS</a></dt><dt>quotas, <a href="#id2917645">Setting up Quotas</a></dt></dl></dd><dt>CUPS-PPD, <a href="#id2916653">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>cupsaddsmb, <a href="#id2906306">Three familiar Methods for driver upload plus a new one</a>, <a href="#id2911524">cupsaddsmb: the unknown Utility</a>, <a href="#id2912362">Caveats to be considered</a>, <a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2912958">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2913117">Understanding cupsaddsmb</a>, <a href="#id2913349">cupsaddsmb with a Samba PDC</a>, <a href="#id2913427">cupsaddsmb Flowchart</a></dt><dt>cupsomatic, <a href="#id2907241">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="#id2907370">The CUPS Filtering Architecture</a>, <a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a>, <a href="#id2916653">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>CVS, <a href="#id2941554">Access Samba source code via CVS</a></dt><dd><dl><dt>web, <a href="#id2941616">Access via CVSweb</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a href="#id2942763">Alternative: starting it as a daemon</a></dt><dt>DDK, <a href="#id2911445">PostScript Drivers with no major problems -- even in Kernel
+Mode</a>, <a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>debug, <a href="#id2941215">Internal errors</a></dt><dt>debug level, <a href="#id2940082">Debugging with Samba itself</a>, <a href="#id2944701">Log level</a></dt><dt>debuglevel, <a href="#id2941006">Debug levels</a></dt><dt>default case, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>delete printer command, <a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt>deleteprinter command, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>DHCP, <a href="#id2932188">Background Information</a></dt><dt>diff, <a href="#id2941395">Patches</a></dt><dt>directory mask, <a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt>directory security mask, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>disable spoolss, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>display charset, <a href="#id2933835">Samba and charsets</a></dt><dt>DNS, <a href="#id2876469">TCP/IP - without NetBIOS</a>, <a href="#id2933266">DNS Lookup</a></dt><dd><dl><dt>Active Directory, <a href="#id2876635">DNS and Active Directory</a></dt><dt>Dynamic, <a href="#id2932188">Background Information</a></dt></dl></dd><dt>dns proxy, <a href="#id2875904">What is Browsing?</a></dt><dt>domain admin group, <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dt>domain logons, <a href="#id2869309">Preparing for Domain Control</a></dt><dt>domain master, <a href="#id2870253">Domain Network Logon Service</a>, <a href="#id2871968">Example Configuration</a>, <a href="#id2875904">What is Browsing?</a>, <a href="#id2877716">Making Samba the domain master</a></dt><dt>dont descend, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>dos charset, <a href="#id2933835">Samba and charsets</a>, <a href="#id2933992">Japanese charsets</a>, <a href="#id2934137">CP850.so can't be found</a></dt><dt>dos filemode, <a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt>dos filetime resolution, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>dos filetimes, <a href="#id2887639">Miscellaneous Controls</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>EMF, <a href="#id2906600">Windows Drivers, GDI and EMF</a>, <a href="#id2910577">From Windows Clients to an NT Print Server</a>, <a href="#id2910701">Driver Execution on the Server</a></dt><dt>encrypt passwords, <a href="#id2873558">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2881758">smbpasswd - Encrypted Password Database</a>, <a href="#id2931283">smb.conf PAM Configuration</a>, <a href="#id2938586">The tests</a></dt><dt>enhanced browsing, <a href="#id2875904">What is Browsing?</a></dt><dt>enumports command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2903854">Samba and Printer Ports</a></dt><dt>EPM (see ESP meta packager)</dt><dt>ESC/P, <a href="#id2910701">Driver Execution on the Server</a></dt><dt>ESP</dt><dd><dl><dt>Ghostscript, <a href="#id2907370">The CUPS Filtering Architecture</a>, <a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a></dt><dt>meta packager, <a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>Print Pro, <a href="#id2910331">Sources of CUPS drivers / PPDs</a>, <a href="#id2912301">ESP Print Pro Package of "PostScript Driver for
+WinNT/2k/XP"</a></dt></dl></dd><dt>Extended Attributes, <a href="#AccessControls">File, Directory and Share Access Controls</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fake oplocks, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>File System, <a href="#id2886154">File System Access Controls</a></dt><dt>foomatic, <a href="#id2907241">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="#id2907370">The CUPS Filtering Architecture</a>, <a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a>, <a href="#id2916436">foomatic-rip and Foomatic explained</a>, <a href="#id2916577">Foomatic's strange Name</a></dt><dt>foomatic-rip, <a href="#id2909807">Difference between cupsomatic/foomatic-rip and
+native CUPS printing</a>, <a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a>, <a href="#id2916436">foomatic-rip and Foomatic explained</a>, <a href="#id2916817">The Grand Unification
+achieved...</a></dt><dt>force create mode, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>force directory mode, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>force directory security mode, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>force group, <a href="#id2886837">User and Group Based Controls</a></dt><dt>force security mode, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>force user, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2889969">I have set force user but Samba still makes root the owner of all the files I touch!</a>, <a href="#id2890942">Beware of Force User</a></dt><dt>ftp, <a href="#id2941849">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gdb, <a href="#id2941215">Internal errors</a></dt><dt>GDI, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2906600">Windows Drivers, GDI and EMF</a>, <a href="#id2910577">From Windows Clients to an NT Print Server</a>, <a href="#id2910701">Driver Execution on the Server</a></dt><dt>GhostScript, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2907029">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dd><dl><dt>(see also PostScript)</dt></dl></dd><dt>Ghostscript</dt><dd><dl><dt>ESP (see ESP GhostScript)</dt></dl></dd><dt>GID, <a href="#id2884967">Features and Benefits</a></dt><dt>GPG, <a href="#id2941913">Verifying Samba's PGP signature</a></dt><dt>groupadd, <a href="#id2884967">Features and Benefits</a></dt><dt>groupdel, <a href="#id2884967">Features and Benefits</a></dt><dt>groups</dt><dd><dl><dt>domain, <a href="#id2885202">Discussion</a></dt><dt>mapping, <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dt>nested, <a href="#id2885742">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd><dt>guest account, <a href="#id2879168">Problem resolution</a>, <a href="#id2879979">My client reports "This server is not configured to list shared resources"</a>, <a href="#id2896767">The [printers] Section</a></dt><dt>guest ok, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a>, <a href="#id2899189">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hide dot files, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>hide files, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>hide unreadable, <a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt>hide unwriteable files, <a href="#id2887260">File and Directory Permissions Based Controls</a></dt><dt>host msdfs, <a href="#id2894231">Features and Benefits</a></dt><dt>hosts allow, <a href="#id2892490">Using host based protection</a>, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2897210">Any [my_printer_name] Section</a></dt><dt>hosts deny, <a href="#id2892490">Using host based protection</a>, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2897210">Any [my_printer_name] Section</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>idmap gid, <a href="#id2884967">Features and Benefits</a>, <a href="#id2931926">Winbind is not resolving users and groups</a></dt><dt>idmap uid, <a href="#id2884967">Features and Benefits</a>, <a href="#id2931926">Winbind is not resolving users and groups</a></dt><dt>ifconfig, <a href="#id2942516">Starting from inetd.conf</a></dt><dt>imprints, <a href="#id2906306">Three familiar Methods for driver upload plus a new one</a></dt><dt>inetd, <a href="#id2938586">The tests</a>, <a href="#id2942409">Starting the smbd and nmbd</a>, <a href="#id2942516">Starting from inetd.conf</a></dt><dt>Interdomain Trusts, <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt>completing, <a href="#id2893500">Completing an NT4 Domain Trust</a></dt><dt>creating, <a href="#id2893400">Native MS Windows NT4 Trusts Configuration</a></dt><dt>Facilities, <a href="#id2893547">Inter-Domain Trust Facilities</a></dt></dl></dd><dt>interfaces, <a href="#id2877911">Multiple interfaces</a>, <a href="#id2938586">The tests</a>, <a href="#id2942516">Starting from inetd.conf</a></dt><dt>invalid users, <a href="#id2886837">User and Group Based Controls</a></dt><dt>IPP, <a href="#id2913117">Understanding cupsaddsmb</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KDC, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>Kerberos, <a href="#ads-member">Samba ADS Domain Membership</a></dt><dt>kinit, <a href="#id2874307">Setup your /etc/krb5.conf</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>ldap admin dn, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap delete dn, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap filter, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap machine suffix, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap passwd sync, <a href="#id2882509">Configuring Samba</a>, <a href="#id2883609">Password synchronisation</a></dt><dt>ldap ssl, <a href="#id2882509">Configuring Samba</a>, <a href="#id2882943">Security and sambaSamAccount</a></dt><dt>ldap suffix, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap trust ids, <a href="#id2882509">Configuring Samba</a></dt><dt>ldap user suffix, <a href="#id2882509">Configuring Samba</a></dt><dt>libnss_wins.so, <a href="#id2932551">/etc/nsswitch.conf</a></dt><dt>Links</dt><dd><dl><dt>hard, <a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>soft, <a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>Linuxprinting.org, <a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a></dt><dt>lm announce, <a href="#id2875904">What is Browsing?</a></dt><dt>lm interval, <a href="#id2875904">What is Browsing?</a></dt><dt>LMB (see Local Master Browser)</dt><dt>LMHOSTS, <a href="#id2932985">The LMHOSTS file</a></dt><dt>load printers, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2895606">A little Experiment to warn you</a>, <a href="#id2896282">The [global] Section</a></dt><dt>local master, <a href="#id2875904">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt>Local Master Browser, <a href="#id2877946">Use of the Remote Announce parameter</a></dt><dt>locking, <a href="#id2890336">Discussion</a></dt><dt>locking.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>log files</dt><dd><dl><dt>monitoring, <a href="#id2938359">Assumptions</a></dt></dl></dd><dt>log level, <a href="#id2874764">Adding Machine to Domain Fails</a>, <a href="#id2920835">extd_audit</a>, <a href="#id2941006">Debug levels</a></dt><dt>logon drive, <a href="#id2927080">Windows NT4 Workstation</a></dt><dt>logon home, <a href="#id2883102">LDAP special attributes for sambaSamAccounts</a>, <a href="#id2926161">Windows 9x / Me User Profiles</a>, <a href="#id2926293">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="#id2927080">Windows NT4 Workstation</a>, <a href="#id2927776">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon path, <a href="#id2883102">LDAP special attributes for sambaSamAccounts</a>, <a href="#id2926293">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="#id2926538">Windows 9x / Me Profile Setup</a>, <a href="#id2927080">Windows NT4 Workstation</a>, <a href="#id2927776">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon script, <a href="#id2883102">LDAP special attributes for sambaSamAccounts</a></dt><dt>lpadmin, <a href="#id2916297">CUPS Print Drivers from Linuxprinting.org</a>, <a href="#id2917645">Setting up Quotas</a></dt><dt>lppause command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2918407">Pre-conditions</a></dt><dt>lpq cache time, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a></dt><dt>lpq command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2918407">Pre-conditions</a></dt><dt>lpresume command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2918407">Pre-conditions</a></dt><dt>lprm command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2918407">Pre-conditions</a></dt><dt>lpstat, <a href="#id2915566">Troubleshooting revisited</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>MAC Addresses, <a href="#id2932315">/etc/hosts</a></dt><dt>machine trust accounts, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt>creating, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>make, <a href="#id2942063">Building the Binaries</a></dt><dt>mangling method, <a href="#id2933992">Japanese charsets</a></dt><dt>map to guest, <a href="#id2899189">Parameters in the [print$] Section</a>, <a href="#id2903177">Adding new Printers with the Windows NT APW</a>, <a href="#id2919497">Can't reconnect to Samba under new account
+			from Win2K/XP</a>, <a href="#id2919582">Avoid being connected to the Samba server as the
+		"wrong" user</a></dt><dt>max print jobs, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>max xmit, <a href="#id2944641">Max xmit</a></dt><dt>messages.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>MIME, <a href="#id2907545">MIME types and CUPS Filters</a>, <a href="#id2907752">MIME type Conversion Rules</a>, <a href="#id2907903">Filter Requirements</a>, <a href="#id2909312">"application/octet-stream" printing</a></dt><dt>min print space, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>msdfs root, <a href="#id2894231">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>name resolve order, <a href="#id2875904">What is Browsing?</a></dt><dt>nbtstat, <a href="#id2932922">The NetBIOS Name Cache</a></dt><dt>NetBIOS, <a href="#id2875816">Features and Benefits</a>, <a href="#id2876469">TCP/IP - without NetBIOS</a>, <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a>, <a href="#id2932655">Name resolution as used within MS Windows networking</a></dt><dt>NetBIOS-less, <a href="#id2876469">TCP/IP - without NetBIOS</a></dt><dt>nmblookup, <a href="#id2932922">The NetBIOS Name Cache</a></dt><dt>nt acl support, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2888523">Viewing file ownership</a>, <a href="#id2888655">Viewing File or Directory Permissions</a>, <a href="#id2888889">Modifying file or directory permissions</a>, <a href="#id2944140">Windows 2000 Service Pack 2</a></dt><dt>ntdrivers.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>ntforms.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTFS, <a href="#id2886154">File System Access Controls</a></dt><dt>ntprinters.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>obey pam restrictions, <a href="#id2931283">smb.conf PAM Configuration</a></dt><dt>only user, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2892992">Why can users access home directories of other users?</a></dt><dt>oplock break wait time, <a href="#id2891044">Advanced Samba Opportunistic Locking Parameters</a>, <a href="#id2891378">Disabling Kernel OpLocks</a></dt><dt>oplock contention limit, <a href="#id2891044">Advanced Samba Opportunistic Locking Parameters</a></dt><dt>os level, <a href="#id2875904">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a>, <a href="#id2877309">Setting up DOMAIN Browsing</a>, <a href="#browse-force-master">Forcing Samba to be the master</a>, <a href="#id2877716">Making Samba the domain master</a></dt><dt>os2 driver map, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2943660">Printer driver download for for OS/2 clients?</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>page_log, <a href="#id2917829">The page_log File Syntax</a></dt><dt>passdb backend, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="#passdb">Account Information Databases</a>, <a href="#id2880590">Technical Information</a>, <a href="#id2881423">The pdbedit Command</a>, <a href="#id2882509">Configuring Samba</a>, <a href="#id2883816">Configuring</a>, <a href="#id2884582">Users can not logon</a>, <a href="#id2884738">auth methods does not work</a>, <a href="#id2935529">Passdb Backends and Authentication</a></dt><dt>password level, <a href="#id2868158">Password checking</a>, <a href="#id2938586">The tests</a>, <a href="#id2943941">Case handling of passwords</a>, <a href="#id2944879">Slow Logins</a></dt><dt>password server, <a href="#id2867877">Server Security (User Level Security)</a>, <a href="#id2870678">Security Mode and Master Browsers</a>, <a href="#id2873558">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2938586">The tests</a></dt><dt>patch, <a href="#id2941395">Patches</a></dt><dt>path, <a href="#id2866630">"The network name cannot be found"</a>, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a>, <a href="#id2897534">Print Commands</a>, <a href="#id2899004">Creating the [print$] Share</a>, <a href="#id2899189">Parameters in the [print$] Section</a>, <a href="#id2899475">Subdirectory Structure in [print$]</a>, <a href="#id2911043">Samba receiving Jobfiles and passing them to CUPS</a>, <a href="#id2918267">Auto-Deletion or Preservation of CUPS Spool Files</a>, <a href="#id2920175">Permissions on
 /var/spool/samba/ get reset after each
-reboot</a>, <a href="#id2940846">The tests</a></dt><dt>PCL, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a>, <a href="#id2913090">Driver Execution on the Server</a>, <a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a></dt><dt>PDF, <a href="#id2909034">Windows Drivers, GDI and EMF</a>, <a href="#id2909567">PostScript Printer Description (PPD) Specification</a></dt><dt>pdf, <a href="#id2910165">MIME type Conversion Rules</a></dt><dt>PDL, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PJL, <a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a>, <a href="#id2915016">Benefits of using "CUPS PostScript Driver for
-Windows NT/2k/XP" instead of Adobe Driver</a>, <a href="#id2920202">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>point and print, <a href="#id2908485">Driver Installation Methods on Windows Clients</a>, <a href="#id2908739">Three familiar Methods for driver upload plus a new one</a>, <a href="#id2911412">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2915946">Installing the PostScript Driver on a Client</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt>PostScript, <a href="#id2908865">Using CUPS/Samba in an advanced Way -- intelligent printing
-with PostScript Driver Download</a>, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a>, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2910493">Prefilters</a>, <a href="#id2913090">Driver Execution on the Server</a>, <a href="#id2913513">Network PostScript RIP: CUPS Filters on Server -- clients use
-PostScript Driver with CUPS-PPDs</a>, <a href="#id2913789">CUPS: a "Magical Stone"?</a>, <a href="#id2914233">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dd><dl><dt>(see also Ghostscript)</dt><dt>RIP, <a href="#post-and-ghost">PostScript and Ghostscript</a></dt></dl></dd><dt>PPD, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2909567">PostScript Printer Description (PPD) Specification</a>, <a href="#id2911929">PostScript Printer Descriptions (PPDs) for non-PS Printers</a>, <a href="#id2913594">PPDs for non-PS Printers on UNIX</a>, <a href="#id2913643">PPDs for non-PS Printers on Windows</a>, <a href="#id2913789">CUPS: a "Magical Stone"?</a>, <a href="#id2915946">Installing the PostScript Driver on a Client</a></dt><dd><dl><dt>CUPS (see CUPS-PPD)</dt></dl></dd><dt>preferred master, <a href="#id2878408">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a>, <a href="#browse-force-master">Forcing Samba to be the master</a>, <a href="#id2880217">Making Samba the domain master</a>, <a href="#id2940846">The tests</a></dt><dt>preserve case, <a href="#id2928828">Windows 9x / Me Profile Setup</a></dt><dt>print command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a>, <a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2900758">Setting up your own Print Commands</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2920874">Pre-conditions</a>, <a href="#id2921030">Manual Configuration</a></dt><dt>print ok , <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>printable, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a></dt><dt>printcap, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2907507">Basic Configuration of CUPS support</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2908016">More complex smb.conf Settings for
-CUPS</a>, <a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2920874">Pre-conditions</a></dt><dt>printcap name, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a></dt><dt>printer, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>printer admin, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a>, <a href="#id2901686">Parameters in the [print$] Section</a>, <a href="#id2902234">Setting Drivers for existing Printers with a Client GUI</a>, <a href="#id2904269">IMPORTANT! Setting Device Modes on new Printers</a>, <a href="#id2904670">Always make first Client Connection as root or "printer admin"</a>, <a href="#id2904870">Setting Default Print Options for the Client Drivers</a>, <a href="#id2905621">Adding new Printers with the Windows NT APW</a>, <a href="#id2908016">More complex smb.conf Settings for
-CUPS</a>, <a href="#id2916790">What is required for adddriver and setdriver to succeed</a>, <a href="#id2922126">Print options for all	users can't be set on Win2K/XP</a></dt><dt>printer name, <a href="#id2897387">Parameters Recommended for Use</a></dt><dt>printing, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a>, <a href="#id2900090">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2900758">Setting up your own Print Commands</a>, <a href="#id2907507">Basic Configuration of CUPS support</a>, <a href="#id2907600">Linking of smbd with libcups.so</a>, <a href="#id2908016">More complex smb.conf Settings for
-CUPS</a>, <a href="#id2913221">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2920874">Pre-conditions</a>, <a href="#id2921030">Manual Configuration</a></dt><dt>printing.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>PrintPro (see ESP Print Pro)</dt><dt>public, <a href="#id2899274">The [printers] Section</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>queue resume command, <a href="#id2907600">Linking of smbd with libcups.so</a></dt><dt>queuepause command, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2907600">Linking of smbd with libcups.so</a></dt><dt>queueresume command, <a href="#id2897387">Parameters Recommended for Use</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>read list, <a href="#id2889373">User and Group Based Controls</a></dt><dt>read only, <a href="#id2890173">Miscellaneous Controls</a>, <a href="#id2899274">The [printers] Section</a>, <a href="#id2901686">Parameters in the [print$] Section</a></dt><dt>read raw, <a href="#id2944528">Read raw</a></dt><dt>read size, <a href="#id2944388">Read size</a></dt><dt>remote announce, <a href="#id2878736">NetBIOS over TCP/IP</a>, <a href="#id2879284">How Browsing Functions</a>, <a href="#id2880448">Use of the Remote Announce parameter</a>, <a href="#id2881541">Browsing support in Samba</a></dt><dt>remote browse sync, <a href="#id2878736">NetBIOS over TCP/IP</a>, <a href="#id2879284">How Browsing Functions</a>, <a href="#id2880607">Use of the Remote Browse Sync parameter</a></dt><dt>root preexec, <a href="#id2938611">Logon Scripts</a></dt><dt>rpcclient</dt><dd><dl><dt>adddriver, <a href="#id2915344">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2915567">Understanding cupsaddsmb</a>, <a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a>, <a href="#id2916536">Understanding the rpcclient man page</a>, <a href="#id2916790">What is required for adddriver and setdriver to succeed</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt>enumdrivers, <a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt>enumports, <a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a></dt><dt>enumprinters, <a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a>, <a href="#id2916790">What is required for adddriver and setdriver to succeed</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a>, <a href="#id2918021">Troubleshooting revisited</a></dt><dt>getdriver, <a href="#id2916644">Producing an Example by querying a Windows Box</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt><dt>getprinter, <a href="#id2916644">Producing an Example by querying a Windows Box</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a>, <a href="#id2918021">Troubleshooting revisited</a></dt><dt>setdriver, <a href="#id2914749">Caveats to be considered</a>, <a href="#id2915344">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2915567">Understanding cupsaddsmb</a>, <a href="#id2916229">Installing PostScript Driver Files manually (using
-rpcclient)</a>, <a href="#id2916790">What is required for adddriver and setdriver to succeed</a>, <a href="#id2917000">Manual Driver Installation in 15 Steps</a></dt></dl></dd><dt>rsync, <a href="#id2871712">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>secrets.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>security, <a href="#id2867803">Samba Security Modes</a>, <a href="#id2852162">Domain Security Mode (User Level Security)</a>, <a href="#id2852521">Server Security (User Level Security)</a>, <a href="#id2869671">What makes Samba a SERVER?</a>, <a href="#id2869710">What makes Samba a Domain Controller?</a>, <a href="#id2869747">What makes Samba a Domain Member?</a>, <a href="#id2869786">Constantly Losing Connections to Password Server</a>, <a href="#id2870592">Preparing for Domain Control</a>, <a href="#id2873169">Security Mode and Master Browsers</a>, <a href="#id2876053">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2876489">Why is this better than security = server?</a>, <a href="#id2876674">Setup your smb.conf</a>, <a href="#id2915223">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2921558">"cupsaddsmb" keeps asking for root password in
-			neverending loop</a>, <a href="#id2937791">Passdb Backends and Authentication</a>, <a href="#id2940846">The tests</a>, <a href="#id2943683">Configuring WfW password handling</a></dt><dt>security mask, <a href="#id2889794">File and Directory Permissions Based Controls</a>, <a href="#id2891583">Interaction with the standard Samba create mask 
-		parameters</a></dt><dt>Server Manager, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt>sessionid.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>share_info.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>short preserve case, <a href="#id2890173">Miscellaneous Controls</a>, <a href="#id2928828">Windows 9x / Me Profile Setup</a></dt><dt>Short-Cuts, <a href="#id2888724">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>show add printer wizard, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a>, <a href="#id2905621">Adding new Printers with the Windows NT APW</a></dt><dt>SID, <a href="#id2887487">Features and Benefits</a></dt><dt>Single Sign On, <a href="#id2914749">Caveats to be considered</a></dt><dt>smbclient, <a href="#ads-test-smbclient">Testing with smbclient</a>, <a href="#id2940846">The tests</a></dt><dt>socket options, <a href="#id2944298">Socket options</a></dt><dt>spooling</dt><dd><dl><dt>central, <a href="#id2908382">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt>peer-to-peer, <a href="#id2908382">Central spooling vs. "Peer-to-Peer" printing</a></dt></dl></dd><dt>spooling-only, <a href="#id2908431">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
-with Vendor Drivers on Windows Clients</a></dt><dt>strict locking, <a href="#id2892860">Discussion</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>TDB, <a href="#id2918173">The printing *.tdb Files</a>, <a href="#id2918418">Trivial DataBase Files</a></dt><dd><dl><dt>backing up (see tdbbackup)</dt></dl></dd><dt>tdbbackup, <a href="#id2918617">Using tdbbackup</a></dt><dt>template homedir, <a href="#id2925859">Linux/FreeBSD-specific PAM configuration</a></dt><dt>testparm, <a href="#id2940846">The tests</a></dt><dt>text/plain, <a href="#id2910165">MIME type Conversion Rules</a></dt><dt>total print jobs, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UDP, <a href="#id2878736">NetBIOS over TCP/IP</a></dt><dt>UID, <a href="#id2887487">Features and Benefits</a></dt><dt>unexpected.tdb, <a href="#id2918173">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>unix charset, <a href="#id2936097">Samba and charsets</a>, <a href="#id2936254">Japanese charsets</a></dt><dt>use client driver, <a href="#id2897387">Parameters Recommended for Use</a>, <a href="#id2898782">The [global] Section</a></dt><dt>user, <a href="#id2868060">Share Level Security</a>, <a href="#id2940846">The tests</a></dt><dt>User Manager, <a href="#samba-trusted-domain">Samba as the Trusted Domain</a>, <a href="#id2896417">Samba as the Trusting Domain</a></dt><dt>useradd, <a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt><dt>username, <a href="#id2889373">User and Group Based Controls</a></dt><dt>username level, <a href="#id2869450">Password checking</a></dt><dt>username map, <a href="#id2875855">Windows 200x XP Professional</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2940846">The tests</a></dt><dt>veto files, <a href="#id2890173">Miscellaneous Controls</a></dt><dt>vfs objects, <a href="#id2922889">Discussion</a></dt><dt>vipw, <a href="#id2875264">Manual Creation of Machine Trust Accounts</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>winbind separator, <a href="#id2925188">Start up the winbindd daemon and test it!</a></dt><dt>WINS, <a href="#id2878408">What is Browsing?</a>, <a href="#id2878736">NetBIOS over TCP/IP</a>, <a href="#id2935560">WINS Lookup</a></dt><dt>wins hook, <a href="#id2878408">What is Browsing?</a></dt><dt>wins proxy, <a href="#id2878408">What is Browsing?</a></dt><dt>wins server, <a href="#id2878408">What is Browsing?</a>, <a href="#id2880684">WINS - The Windows Internetworking Name Server</a>, <a href="#id2880872">Setting up a WINS server</a></dt><dt>wins support, <a href="#id2878408">What is Browsing?</a>, <a href="#id2880684">WINS - The Windows Internetworking Name Server</a>, <a href="#id2880872">Setting up a WINS server</a></dt><dt>workgroup, <a href="#id2873169">Security Mode and Master Browsers</a>, <a href="#id2876053">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2881541">Browsing support in Samba</a></dt><dt>write list, <a href="#id2889373">User and Group Based Controls</a>, <a href="#id2901686">Parameters in the [print$] Section</a></dt><dt>write raw, <a href="#id2944612">Write raw</a></dt><dt>writeable, <a href="#id2899274">The [printers] Section</a>, <a href="#id2899717">Any [my_printer_name] Section</a></dt><dt>WYSIWYG, <a href="#id2909034">Windows Drivers, GDI and EMF</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X Window System, <a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a></dt><dt>xinetd, <a href="#id2872378">Starting from inetd.conf</a> (see inetd)</dt><dt>Xprint, <a href="#id2909175">UNIX Printfile Conversion and GUI Basics</a></dt></dl></div></div></div></div></body></html>
+reboot</a>, <a href="#id2938586">The tests</a></dt><dt>PCL, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a>, <a href="#id2910701">Driver Execution on the Server</a>, <a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a></dt><dt>PDF, <a href="#id2906600">Windows Drivers, GDI and EMF</a>, <a href="#id2907154">PostScript Printer Description (PPD) Specification</a></dt><dt>pdf, <a href="#id2907752">MIME type Conversion Rules</a></dt><dt>PDL, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PJL, <a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a>, <a href="#id2912629">Benefits of using "CUPS PostScript Driver for
+Windows NT/2k/XP" instead of Adobe Driver</a>, <a href="#id2917748">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>point and print, <a href="#id2906051">Driver Installation Methods on Windows Clients</a>, <a href="#id2906306">Three familiar Methods for driver upload plus a new one</a>, <a href="#id2909039">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2913497">Installing the PostScript Driver on a Client</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt>PostScript, <a href="#id2906432">Using CUPS/Samba in an advanced Way -- intelligent printing
+with PostScript Driver Download</a>, <a href="#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a>, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2908080">Prefilters</a>, <a href="#id2910701">Driver Execution on the Server</a>, <a href="#id2911125">Network PostScript RIP: CUPS Filters on Server -- clients use
+PostScript Driver with CUPS-PPDs</a>, <a href="#id2911400">CUPS: a "Magical Stone"?</a>, <a href="#id2911845">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dd><dl><dt>(see also Ghostscript)</dt><dt>RIP, <a href="#post-and-ghost">PostScript and Ghostscript</a></dt></dl></dd><dt>PPD, <a href="#post-and-ghost">PostScript and Ghostscript</a>, <a href="#id2907154">PostScript Printer Description (PPD) Specification</a>, <a href="#id2909544">PostScript Printer Descriptions (PPDs) for non-PS Printers</a>, <a href="#id2911206">PPDs for non-PS Printers on UNIX</a>, <a href="#id2911255">PPDs for non-PS Printers on Windows</a>, <a href="#id2911400">CUPS: a "Magical Stone"?</a>, <a href="#id2913497">Installing the PostScript Driver on a Client</a></dt><dd><dl><dt>CUPS (see CUPS-PPD)</dt></dl></dd><dt>preferred master, <a href="#id2875904">What is Browsing?</a>, <a href="#DMB">Setting up WORKGROUP Browsing</a>, <a href="#browse-force-master">Forcing Samba to be the master</a>, <a href="#id2877716">Making Samba the domain master</a>, <a href="#id2938586">The tests</a></dt><dt>preserve case, <a href="#id2926538">Windows 9x / Me Profile Setup</a></dt><dt>print command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a>, <a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2898261">Setting up your own Print Commands</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2918407">Pre-conditions</a>, <a href="#id2918564">Manual Configuration</a></dt><dt>print ok , <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>printable, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a></dt><dt>printcap, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2905074">Basic Configuration of CUPS support</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2905584">More complex smb.conf Settings for
+CUPS</a>, <a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2918407">Pre-conditions</a></dt><dt>printcap name, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a></dt><dt>printer, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>printer admin, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a>, <a href="#id2899189">Parameters in the [print$] Section</a>, <a href="#id2899736">Setting Drivers for existing Printers with a Client GUI</a>, <a href="#id2901839">IMPORTANT! Setting Device Modes on new Printers</a>, <a href="#id2902231">Always make first Client Connection as root or "printer admin"</a>, <a href="#id2902431">Setting Default Print Options for the Client Drivers</a>, <a href="#id2903177">Adding new Printers with the Windows NT APW</a>, <a href="#id2905584">More complex smb.conf Settings for
+CUPS</a>, <a href="#id2914333">What is required for adddriver and setdriver to succeed</a>, <a href="#id2919794">Print options for all	users can't be set on Win2K/XP</a></dt><dt>printer name, <a href="#id2894888">Parameters Recommended for Use</a></dt><dt>printing, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a>, <a href="#id2897592">Default Print Commands for various UNIX Print Subsystems</a>, <a href="#id2898261">Setting up your own Print Commands</a>, <a href="#id2905074">Basic Configuration of CUPS support</a>, <a href="#id2905167">Linking of smbd with libcups.so</a>, <a href="#id2905584">More complex smb.conf Settings for
+CUPS</a>, <a href="#id2910833">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="#id2918407">Pre-conditions</a>, <a href="#id2918564">Manual Configuration</a></dt><dt>printing.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>PrintPro (see ESP Print Pro)</dt><dt>public, <a href="#id2896767">The [printers] Section</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>queue resume command, <a href="#id2905167">Linking of smbd with libcups.so</a></dt><dt>queuepause command, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2905167">Linking of smbd with libcups.so</a></dt><dt>queueresume command, <a href="#id2894888">Parameters Recommended for Use</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>read list, <a href="#id2886837">User and Group Based Controls</a></dt><dt>read only, <a href="#id2887639">Miscellaneous Controls</a>, <a href="#id2896767">The [printers] Section</a>, <a href="#id2899189">Parameters in the [print$] Section</a></dt><dt>read raw, <a href="#id2944732">Read raw</a></dt><dt>read size, <a href="#id2944592">Read size</a></dt><dt>remote announce, <a href="#id2876233">NetBIOS over TCP/IP</a>, <a href="#id2876781">How Browsing Functions</a>, <a href="#id2877946">Use of the Remote Announce parameter</a>, <a href="#id2879046">Browsing support in Samba</a></dt><dt>remote browse sync, <a href="#id2876233">NetBIOS over TCP/IP</a>, <a href="#id2876781">How Browsing Functions</a>, <a href="#id2878104">Use of the Remote Browse Sync parameter</a></dt><dt>root preexec, <a href="#id2936350">Logon Scripts</a></dt><dt>rpcclient</dt><dd><dl><dt>adddriver, <a href="#id2912958">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2913117">Understanding cupsaddsmb</a>, <a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a>, <a href="#id2914086">Understanding the rpcclient man page</a>, <a href="#id2914333">What is required for adddriver and setdriver to succeed</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt>enumdrivers, <a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt>enumports, <a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a></dt><dt>enumprinters, <a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a>, <a href="#id2914333">What is required for adddriver and setdriver to succeed</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a>, <a href="#id2915566">Troubleshooting revisited</a></dt><dt>getdriver, <a href="#id2914186">Producing an Example by querying a Windows Box</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt><dt>getprinter, <a href="#id2914186">Producing an Example by querying a Windows Box</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a>, <a href="#id2915566">Troubleshooting revisited</a></dt><dt>setdriver, <a href="#id2912362">Caveats to be considered</a>, <a href="#id2912958">Run "cupsaddsmb" with verbose Output</a>, <a href="#id2913117">Understanding cupsaddsmb</a>, <a href="#id2913780">Installing PostScript Driver Files manually (using
+rpcclient)</a>, <a href="#id2914333">What is required for adddriver and setdriver to succeed</a>, <a href="#id2914542">Manual Driver Installation in 15 Steps</a></dt></dl></dd><dt>rsync, <a href="#id2941849">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>secrets.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>security, <a href="#id2867124">Samba Security Modes</a>, <a href="#id2867518">Domain Security Mode (User Level Security)</a>, <a href="#id2867877">Server Security (User Level Security)</a>, <a href="#id2868387">What makes Samba a SERVER?</a>, <a href="#id2868427">What makes Samba a Domain Controller?</a>, <a href="#id2868463">What makes Samba a Domain Member?</a>, <a href="#id2868503">Constantly Losing Connections to Password Server</a>, <a href="#id2869309">Preparing for Domain Control</a>, <a href="#id2870678">Security Mode and Master Browsers</a>, <a href="#id2873558">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2873995">Why is this better than security = server?</a>, <a href="#id2874178">Setup your smb.conf</a>, <a href="#id2912835">Run "cupsaddsmb" (quiet Mode)</a>, <a href="#id2919061">"cupsaddsmb" keeps asking for root password in
+			neverending loop</a>, <a href="#id2935529">Passdb Backends and Authentication</a>, <a href="#id2938586">The tests</a>, <a href="#id2943888">Configuring WfW password handling</a></dt><dt>security mask, <a href="#id2887260">File and Directory Permissions Based Controls</a>, <a href="#id2889049">Interaction with the standard Samba create mask 
+		parameters</a></dt><dt>Server Manager, <a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt>sessionid.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>share_info.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>short preserve case, <a href="#id2887639">Miscellaneous Controls</a>, <a href="#id2926538">Windows 9x / Me Profile Setup</a></dt><dt>Short-Cuts, <a href="#id2886190">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>show add printer wizard, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a>, <a href="#id2903177">Adding new Printers with the Windows NT APW</a></dt><dt>SID, <a href="#id2884967">Features and Benefits</a></dt><dt>Single Sign On, <a href="#id2912362">Caveats to be considered</a></dt><dt>smbclient, <a href="#ads-test-smbclient">Testing with smbclient</a>, <a href="#id2938586">The tests</a></dt><dt>socket options, <a href="#id2944501">Socket options</a></dt><dt>spooling</dt><dd><dl><dt>central, <a href="#id2905949">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt>peer-to-peer, <a href="#id2905949">Central spooling vs. "Peer-to-Peer" printing</a></dt></dl></dd><dt>spooling-only, <a href="#id2905999">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
+with Vendor Drivers on Windows Clients</a></dt><dt>strict locking, <a href="#id2890336">Discussion</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>TDB, <a href="#id2915718">The printing *.tdb Files</a>, <a href="#id2915962">Trivial DataBase Files</a></dt><dd><dl><dt>backing up (see tdbbackup)</dt></dl></dd><dt>tdbbackup, <a href="#id2916162">Using tdbbackup</a></dt><dt>template homedir, <a href="#id2923568">Linux/FreeBSD-specific PAM configuration</a></dt><dt>testparm, <a href="#id2938586">The tests</a></dt><dt>text/plain, <a href="#id2907752">MIME type Conversion Rules</a></dt><dt>total print jobs, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UDP, <a href="#id2876233">NetBIOS over TCP/IP</a></dt><dt>UID, <a href="#id2884967">Features and Benefits</a></dt><dt>unexpected.tdb, <a href="#id2915718">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>unix charset, <a href="#id2933835">Samba and charsets</a>, <a href="#id2933992">Japanese charsets</a></dt><dt>use client driver, <a href="#id2894888">Parameters Recommended for Use</a>, <a href="#id2896282">The [global] Section</a></dt><dt>user, <a href="#id2867382">Share Level Security</a>, <a href="#id2938586">The tests</a></dt><dt>User Manager, <a href="#samba-trusted-domain">Samba as the Trusted Domain</a>, <a href="#id2893918">Samba as the Trusting Domain</a></dt><dt>useradd, <a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt><dt>username, <a href="#id2886837">User and Group Based Controls</a></dt><dt>username level, <a href="#id2868158">Password checking</a></dt><dt>username map, <a href="#id2873360">Windows 200x XP Professional</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2938586">The tests</a></dt><dt>veto files, <a href="#id2887639">Miscellaneous Controls</a></dt><dt>vfs objects, <a href="#id2920556">Discussion</a></dt><dt>vipw, <a href="#id2872769">Manual Creation of Machine Trust Accounts</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>winbind separator, <a href="#id2922889">Start up the winbindd daemon and test it!</a></dt><dt>WINS, <a href="#id2875904">What is Browsing?</a>, <a href="#id2876233">NetBIOS over TCP/IP</a>, <a href="#id2933298">WINS Lookup</a></dt><dt>wins hook, <a href="#id2875904">What is Browsing?</a></dt><dt>wins proxy, <a href="#id2875904">What is Browsing?</a></dt><dt>wins server, <a href="#id2875904">What is Browsing?</a>, <a href="#id2878182">WINS - The Windows Internetworking Name Server</a>, <a href="#id2878371">Setting up a WINS server</a></dt><dt>wins support, <a href="#id2875904">What is Browsing?</a>, <a href="#id2878182">WINS - The Windows Internetworking Name Server</a>, <a href="#id2878371">Setting up a WINS server</a></dt><dt>workgroup, <a href="#id2870678">Security Mode and Master Browsers</a>, <a href="#id2873558">Joining an NT4 type Domain with Samba-3</a>, <a href="#id2879046">Browsing support in Samba</a></dt><dt>write list, <a href="#id2886837">User and Group Based Controls</a>, <a href="#id2899189">Parameters in the [print$] Section</a></dt><dt>write raw, <a href="#id2944816">Write raw</a></dt><dt>writeable, <a href="#id2896767">The [printers] Section</a>, <a href="#id2897210">Any [my_printer_name] Section</a></dt><dt>WYSIWYG, <a href="#id2906600">Windows Drivers, GDI and EMF</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X Window System, <a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a></dt><dt>xinetd, <a href="#id2942516">Starting from inetd.conf</a> (see inetd)</dt><dt>Xprint, <a href="#id2906741">UNIX Printfile Conversion and GUI Basics</a></dt></dl></div></div></div></div></body></html>
diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html
index cacc1090f6..a98700e42f 100644
--- a/docs/htmldocs/net.8.html
+++ b/docs/htmldocs/net.8.html
@@ -24,7 +24,7 @@
 		Defaults to trying 445 first, then 139.
 		</p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
 the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a class="indexterm" name="id2796721"></a><i class="parameter"><tt>netbios name</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. 
+to setting the <a class="indexterm" name="id2796900"></a><a href="#"><i class="parameter"><tt>netbios name</tt></i></a> parameter in the <tt class="filename">smb.conf</tt> file. 
 However, a command
 line setting will take precedence over settings in
 <tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the 
@@ -53,11 +53,18 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796870"></a><i class="parameter"><tt>log level</tt></i> parameter
-in the <tt class="filename">smb.conf</tt> file.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><div class="refsect2" lang="en"><h3>TIME</h3><p>The <b class="command">NET TIME</b> command allows you to view the time on a remote server
+override the <a class="indexterm" name="id2797170"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
+in the <tt class="filename">smb.conf</tt> file.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><div class="refsect2" lang="en"><h3>CHANGESECRETPW</h3><p>This command allows the Samba machine account password to be set from an external application
+to a machine account password that has already been stored in Active Directory. DO NOT USE this command
+unless you know exactly what you are doing. The use of this command requires that the force flag (-f)
+be used also. There will be NO command prompt. Whatever information is piped into stdin, either by
+typing at the command line or otherwise, will be stored as the literal machine password. Do NOT use
+this without care and attention as it will overwrite a legitimate machine password without warning.
+YOU HAVE BEEN WARNED.
+</p></div><div class="refsect2" lang="en"><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><div class="refsect3" lang="en"><h4>TIME</h4><p>Without any options, the <b class="command">NET TIME</b> command 
 displays the time on the remote server.
-</p></div><div class="refsect3" lang="en"><h4>TIME SYSTEM</h4><p> Displays the time on the remote server in a format ready for <b class="command">/bin/date</b></p></div><div class="refsect3" lang="en"><h4>TIME SET</h4><p>Tries to set the date and time of the local server to that on 
+</p></div><div class="refsect3" lang="en"><h4>TIME SYSTEM</h4><p>Displays the time on the remote server in a format ready for <b class="command">/bin/date</b></p></div><div class="refsect3" lang="en"><h4>TIME SET</h4><p>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></div><div class="refsect3" lang="en"><h4>TIME ZONE</h4><p>Displays the timezone in hours from GMT on the remote computer.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]</h3><p>
 Join a domain.  If the account already exists on the server, and 
 [TYPE] is MEMBER, the machine will attempt to join automatically. 
@@ -102,8 +109,8 @@ can be controlled using 'NET CACHE'.</p><p>All the timeout parameters support th
 List all current items in the cache.
 </p></div><div class="refsect3" lang="en"><h4>CACHE FLUSH</h4><p>Remove all the current items from the cache.</p></div></div><div class="refsect2" lang="en"><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" lang="en"><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" lang="en"><h3>GROUPMAP</h3><p>Manage the mappings between Windows group SIDs and UNIX groups.
-Parameters take the for &quot;parameter=value&quot;.  Common options include:</p><div class="itemizedlist"><ul type="disc"><li><p>unixgroup - Name of the UNIX group</p></li><li><p>ntgroup - Name of the Windows NT group (must be
-  resolvable to a SID</p></li><li><p>rid - Unsigned 32-bit integer</p></li><li><p>sid - Full SID in the form of &quot;S-1-...&quot;</p></li><li><p>type - Type of the group; either 'domain', 'local',
+Parameters take the for "parameter=value".  Common options include:</p><div class="itemizedlist"><ul type="disc"><li><p>unixgroup - Name of the UNIX group</p></li><li><p>ntgroup - Name of the Windows NT group (must be
+  resolvable to a SID</p></li><li><p>rid - Unsigned 32-bit integer</p></li><li><p>sid - Full SID in the form of "S-1-..."</p></li><li><p>type - Type of the group; either 'domain', 'local',
   or 'builtin'</p></li><li><p>comment - Freeform text description of the group</p></li></ul></div><div class="refsect3" lang="en"><h4>GROUPMAP ADD</h4><p>Add a new group mapping entry</p><p>net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]</p></div><div class="refsect3" lang="en"><h4>GROUPMAP DELETE</h4><p>Delete a group mapping entry</p><p>net groupmap delete {ntgroup=string|sid=SID}</p></div><div class="refsect3" lang="en"><h4>GROUPMAP MODIFY</h4><p>Update en existing group entry</p><p>net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}</p></div><div class="refsect3" lang="en"><h4>GROUPMAP LIST</h4><p>List existing group mapping entries</p><p>net groupmap list [verbose] [ntgroup=string] [sid=SID]</p></div></div><div class="refsect2" lang="en"><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" lang="en"><h3>RPC INFO</h3><p>Print information about the domain of the remote server,
@@ -129,7 +136,7 @@ local server. Can only be run an a BDC.
 </p></div><div class="refsect2" lang="en"><h3>GETSID</h3><p>Fetch domain SID and store it in the local <tt class="filename">secrets.tdb</tt>. </p></div><div class="refsect2" lang="en"><h3>ADS LEAVE</h3><p>Make the remote host leave the domain it is part of. </p></div><div class="refsect2" lang="en"><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" lang="en"><h3>ADS PRINTER</h3><div class="refsect3" lang="en"><h4>ADS PRINTER INFO [<i class="replaceable"><tt>PRINTER</tt></i>] [<i class="replaceable"><tt>SERVER</tt></i>]</h4><p>
-Lookup info for <i class="replaceable"><tt>PRINTER</tt></i> on <i class="replaceable"><tt>SERVER</tt></i>. The printer name defaults to &quot;*&quot;, the 
+Lookup info for <i class="replaceable"><tt>PRINTER</tt></i> on <i class="replaceable"><tt>SERVER</tt></i>. The printer name defaults to "*", the 
 server name defaults to the local host.</p></div><div class="refsect3" lang="en"><h4>ADS PRINTER PUBLISH <i class="replaceable"><tt>PRINTER</tt></i></h4><p>Publish specified printer using ADS.</p></div><div class="refsect3" lang="en"><h4>ADS PRINTER REMOVE <i class="replaceable"><tt>PRINTER</tt></i></h4><p>Remove specified printer from ADS directory.</p></div></div><div class="refsect2" lang="en"><h3>ADS SEARCH <i class="replaceable"><tt>EXPRESSION</tt></i> <i class="replaceable"><tt>ATTRIBUTES...</tt></i></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: <b class="userinput"><tt>net ads search '(objectCategory=group)' sAMAccountName</tt></b>
diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html
index ad1c7990c0..f3e514fa77 100644
--- a/docs/htmldocs/nmbd.8.html
+++ b/docs/htmldocs/nmbd.8.html
@@ -4,12 +4,12 @@
 	those produced by SMB/CIFS clients such as Windows 95/98/ME, 
 	Windows NT, Windows 2000, Windows XP and LanManager clients. It also
 	participates in the browsing protocols which make up the 
-	Windows &quot;Network Neighborhood&quot; view.</p><p>SMB/CIFS clients, when they start up, may wish to 
+	Windows "Network Neighborhood" view.</p><p>SMB/CIFS clients, when they start up, may wish to 
 	locate an SMB/CIFS server. That is, they wish to know what 
 	IP number a specified host is using.</p><p>Amongst other services, <b class="command">nmbd</b> will 
 	listen for such requests, and if its own NetBIOS name is 
 	specified it will respond with the IP number of the host it 
-	is running on.  Its &quot;own NetBIOS name&quot; is by
+	is running on.  Its "own NetBIOS name" is by
 	default the primary DNS name of the host it is running on, 
 	but this can be overridden with the <span class="emphasis"><em>-n</em></span> 
 	option (see OPTIONS below). Thus <b class="command">nmbd</b> will 
@@ -42,7 +42,7 @@
 		</p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
 		<b class="command">nmbd</b> to log to standard output rather
 		than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
-		server to run &quot;interactively&quot;, not as a daemon, even if the
+		server to run "interactively", not as a daemon, even if the
 		server is executed on the command line of a shell. Setting this
 		parameter negates the implicit daemon mode when run from the
 		command line. <b class="command">nmbd</b> also logs to standard
@@ -51,7 +51,7 @@
 </p></dd><dt><span class="term">-H &lt;filename&gt;</span></dt><dd><p>NetBIOS lmhosts file.  The lmhosts 
 		file is a list of NetBIOS names to IP addresses that 
 		is loaded by the nmbd server and used via the name 
-		resolution mechanism <a class="indexterm" name="id2796904"></a><i class="parameter"><tt>name resolve order</tt></i> described in <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> to resolve any 
+		resolution mechanism <a class="indexterm" name="id2797065"></a><a href="#"><i class="parameter"><tt>name resolve order</tt></i></a> described in <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> to resolve any 
 		NetBIOS name queries needed by the server. Note 
 		that the contents of this file are <span class="emphasis"><em>NOT</em></span> 
 		used by <b class="command">nmbd</b> to answer any name queries. 
@@ -80,9 +80,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2797084"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2797372"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-p &lt;UDP port number&gt;</span></dt><dd><p>UDP port number is a positive integer value.
 		This option changes the default UDP port number (normally 137)
@@ -104,13 +104,13 @@ never removed by the client.
 		configuration file. Other common places that systems
 		install this file are <tt class="filename">/usr/samba/lib/smb.conf</tt>
 		and <tt class="filename">/etc/samba/smb.conf</tt>.</p><p>When run as a WINS server (see the
-			<a class="indexterm" name="id2797295"></a><i class="parameter"><tt>wins support</tt></i>
+			<a class="indexterm" name="id2797588"></a><a href="#"><i class="parameter"><tt>wins support</tt></i></a>
 		parameter in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> man page),
 		<b class="command">nmbd</b>
 		will store the WINS database in the file <tt class="filename">wins.dat</tt>
 		in the <tt class="filename">var/locks</tt> directory configured under
 		wherever Samba was configured to install itself.</p><p>If <b class="command">nmbd</b> is acting as a <span class="emphasis"><em>
-				browse master</em></span> (see the <a class="indexterm" name="id2797358"></a><i class="parameter"><tt>local master</tt></i>
+				browse master</em></span> (see the <a class="indexterm" name="id2797657"></a><a href="#"><i class="parameter"><tt>local master</tt></i></a>
 		parameter in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> man page, <b class="command">nmbd</b>
 		will store the browsing database in the file <tt class="filename">browse.dat
 		</tt> in the <tt class="filename">var/locks</tt> directory
diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html
index 21e84c9c71..10131752b3 100644
--- a/docs/htmldocs/nmblookup.1.html
+++ b/docs/htmldocs/nmblookup.1.html
@@ -6,9 +6,9 @@
 	are done over UDP.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-M</span></dt><dd><p>Searches for a master browser by looking 
 		up the  NetBIOS name <i class="replaceable"><tt>name</tt></i> with a 
 		type of <tt class="constant">0x1d</tt>. If <i class="replaceable"><tt>
-		name</tt></i> is &quot;-&quot; then it does a lookup on the special name 
+		name</tt></i> is "-" then it does a lookup on the special name 
 		<tt class="constant">__MSBROWSE__</tt>. Please note that in order to 
-		use the name &quot;-&quot;, you need to make sure &quot;-&quot; isn't parsed as an 
+		use the name "-", you need to make sure "-" isn't parsed as an 
 		argument, e.g. use : 
 		<b class="userinput"><tt>nmblookup -M -- -</tt></b>.</p></dd><dt><span class="term">-R</span></dt><dd><p>Set the recursion desired bit in the packet 
 		to do a recursive lookup. This is used when sending a name 
@@ -28,7 +28,7 @@
 		</p></dd><dt><span class="term">-A</span></dt><dd><p>Interpret <i class="replaceable"><tt>name</tt></i> as 
 		an IP Address and do a node status query on this address.</p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
 the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a class="indexterm" name="id2796756"></a><i class="parameter"><tt>netbios name</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. 
+to setting the <a class="indexterm" name="id2799960"></a><a href="#"><i class="parameter"><tt>netbios name</tt></i></a> parameter in the <tt class="filename">smb.conf</tt> file. 
 However, a command
 line setting will take precedence over settings in
 <tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-i &lt;scope&gt;</span></dt><dd><p>This specifies a NetBIOS scope that
@@ -73,9 +73,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2797037"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2800366"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-T</span></dt><dd><p>This causes any IP addresses found in the 
 		lookup to be looked up via a reverse DNS lookup into a 
diff --git a/docs/htmldocs/ntlm_auth.1.html b/docs/htmldocs/ntlm_auth.1.html
index e048efae7b..27dfee1a0f 100644
--- a/docs/htmldocs/ntlm_auth.1.html
+++ b/docs/htmldocs/ntlm_auth.1.html
@@ -31,9 +31,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796746"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2799954"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba 
diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html
index f38aeccc18..39a901923f 100644
--- a/docs/htmldocs/pdbedit.8.html
+++ b/docs/htmldocs/pdbedit.8.html
@@ -31,7 +31,7 @@ Home Directory: \\BERSERKER\samba
 HomeDir Drive:  
 Logon Script:   
 Profile Path:   \\BERSERKER\profile
-</pre></dd><dt><span class="term">-w</span></dt><dd><p>This option sets the &quot;smbpasswd&quot; listing format.
+</pre></dd><dt><span class="term">-w</span></dt><dd><p>This option sets the "smbpasswd" listing format.
 		It will make pdbedit list the users in the database, printing
 		out the account fields in a format compatible with the
 		<tt class="filename">smbpasswd</tt> file format. (see the
@@ -44,18 +44,18 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX
 		operations and <span class="emphasis"><em>optional</em></span> in list
 		operations.</p></dd><dt><span class="term">-f fullname</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's full
-		name. </p><p>Example: <b class="command">-f &quot;Simo Sorce&quot;</b></p></dd><dt><span class="term">-h homedir</span></dt><dd><p>This option can be used while adding or
+		name. </p><p>Example: <b class="command">-f "Simo Sorce"</b></p></dd><dt><span class="term">-h homedir</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's home
-		directory network path.</p><p>Example: <b class="command">-h &quot;\\\\BERSERKER\\sorce&quot;</b>
+		directory network path.</p><p>Example: <b class="command">-h "\\\\BERSERKER\\sorce"</b>
 		</p></dd><dt><span class="term">-D drive</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the windows drive
-		letter to be used to map the home directory.</p><p>Example: <b class="command">-d &quot;H:&quot;</b>
+		letter to be used to map the home directory.</p><p>Example: <b class="command">-d "H:"</b>
 		</p></dd><dt><span class="term">-S script</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's logon
-		script path.</p><p>Example: <b class="command">-s &quot;\\\\BERSERKER\\netlogon\\sorce.bat&quot;</b>
+		script path.</p><p>Example: <b class="command">-s "\\\\BERSERKER\\netlogon\\sorce.bat"</b>
 		</p></dd><dt><span class="term">-p profile</span></dt><dd><p>This option can be used while adding or
 		modifing a user account. It will specify the user's profile
-		directory.</p><p>Example: <b class="command">-p &quot;\\\\BERSERKER\\netlogon&quot;</b>
+		directory.</p><p>Example: <b class="command">-p "\\\\BERSERKER\\netlogon"</b>
 		</p></dd><dt><span class="term">-G SID|rid</span></dt><dd><p>
 		This option can be used while adding or modifying a user account. It 
 		will specify the users' new primary group SID (Security Identifier) or 
@@ -65,7 +65,7 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX
 		rid. </p><p>Example: <b class="command">-U S-1-5-21-2447931902-1787058256-3961074038-5004</b></p></dd><dt><span class="term">-c account-control</span></dt><dd><p>This option can be used while adding or modifying a user
 		account. It will specify the users' account control property. Possible
 		flags that can be set are: N, D, H, L, X.				
-		</p><p>Example: <b class="command">-c &quot;[X          ]&quot;</b></p></dd><dt><span class="term">-a</span></dt><dd><p>This option is used to add a user into the
+		</p><p>Example: <b class="command">-c "[X          ]"</b></p></dd><dt><span class="term">-a</span></dt><dd><p>This option is used to add a user into the
 		database. This command needs a user name specified with
 		the -u switch. When adding a new user, pdbedit will also
 		ask for the password to be used.</p><p>Example: <b class="command">pdbedit -a -u sorce</b>
@@ -94,12 +94,12 @@ retype new password
 		applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
 		another and will ease backing up.</p></dd><dt><span class="term">-b passdb-backend</span></dt><dd><p>Use a different default passdb backend. </p><p>Example: <b class="command">pdbedit -b xml:/root/pdb-backup.xml -l</b></p></dd><dt><span class="term">-P account-policy</span></dt><dd><p>Display an account policy</p><p>Valid policies are: minimum password age, reset count minutes, disconnect time,
 		user must logon to change password, password history, lockout duration, min password length,
-		maximum password age and bad lockout attempt.</p><p>Example: <b class="command">pdbedit -P &quot;bad lockout attempt&quot;</b></p><pre class="programlisting">
+		maximum password age and bad lockout attempt.</p><p>Example: <b class="command">pdbedit -P "bad lockout attempt"</b></p><pre class="programlisting">
 account policy value for bad lockout attempt is 0
 </pre></dd><dt><span class="term">-C account-policy-value</span></dt><dd><p>Sets an account policy to a specified value. 
 		This option may only be used in conjunction
 		with the <i class="parameter"><tt>-P</tt></i> option.
-		</p><p>Example: <b class="command">pdbedit -P &quot;bad lockout attempt&quot; -C 3</b></p><pre class="programlisting">
+		</p><p>Example: <b class="command">pdbedit -P "bad lockout attempt" -C 3</b></p><pre class="programlisting">
 account policy value for bad lockout attempt was 0
 account policy value for bad lockout attempt is now 3
 </pre></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
@@ -123,9 +123,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2797533"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2800732"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>This command may be used only by root.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of 
 	the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities 
diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html
index 73caf547a2..e1ff391cbc 100644
--- a/docs/htmldocs/rpcclient.1.html
+++ b/docs/htmldocs/rpcclient.1.html
@@ -5,9 +5,9 @@
 	have now written scripts around it to manage Windows NT clients from 
 	their UNIX workstation. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">server</span></dt><dd><p>NetBIOS name of Server to which to connect. 
 		The server can be  any SMB/CIFS server.  The name is 
-		resolved using the <a class="indexterm" name="id2852375"></a><i class="parameter"><tt>name resolve order</tt></i> line from <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></dd><dt><span class="term">-c|--command='command string'</span></dt><dd><p>execute semicolon separated commands (listed 
+		resolved using the <a class="indexterm" name="id2799808"></a><a href="#"><i class="parameter"><tt>name resolve order</tt></i></a> line from <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>.</p></dd><dt><span class="term">-c|--command='command string'</span></dt><dd><p>execute semicolon separated commands (listed 
 		below)) </p></dd><dt><span class="term">-I IP-address</span></dt><dd><p><i class="replaceable"><tt>IP address</tt></i> is the address of the server to connect to. 
-		It should be specified in standard &quot;a.b.c.d&quot; notation. </p><p>Normally the client would attempt to locate a named 
+		It should be specified in standard "a.b.c.d" notation. </p><p>Normally the client would attempt to locate a named 
 		SMB/CIFS server by looking it up via the NetBIOS name resolution 
 		mechanism described above in the <i class="parameter"><tt>name resolve order</tt></i> 
 		parameter above. Using this parameter will force the client
@@ -35,9 +35,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796778"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2800110"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-N</span></dt><dd><p>If specified, this parameter suppresses the normal
 password prompt from the client to the user. This is useful when
@@ -70,7 +70,7 @@ via the <b class="command">ps</b> command.  To be safe always allow
 <b class="command">rpcclient</b> to prompt for a password and type
 it in directly. </p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
 the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a class="indexterm" name="id2796983"></a><i class="parameter"><tt>netbios name</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. 
+to setting the <a class="indexterm" name="id2800321"></a><a href="#"><i class="parameter"><tt>netbios name</tt></i></a> parameter in the <tt class="filename">smb.conf</tt> file. 
 However, a command
 line setting will take precedence over settings in
 <tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-i &lt;scope&gt;</span></dt><dd><p>This specifies a NetBIOS scope that
@@ -108,10 +108,10 @@ Help File Name:\
 Language Monitor Name:\
 Default Data Type:\
 Comma Separated list of Files
-</pre><p>Any empty fields should be enter as the string &quot;NULL&quot;. </p><p>Samba does not need to support the concept of Print Monitors
+</pre><p>Any empty fields should be enter as the string "NULL". </p><p>Samba does not need to support the concept of Print Monitors
 		since these only apply to local printers whose driver can make
 		use of a bi-directional link for communication.  This field should 
-		be &quot;NULL&quot;.   On a remote NT print server, the Print Monitor for a 
+		be "NULL".   On a remote NT print server, the Print Monitor for a 
 		driver must already be installed prior to adding the driver or 
 		else the RPC will fail. </p></dd><dt><span class="term">addprinter &lt;printername&gt; 
 		&lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</span></dt><dd><p>
@@ -155,9 +155,9 @@ Comma Separated list of Files
 		Execute a GetPrinterDriverDirectory()
 		RPC to retrieve the SMB share name and subdirectory for 
 		storing printer driver files for a given architecture.  Possible 
-		values for <i class="parameter"><tt>arch</tt></i> are &quot;Windows 4.0&quot; 
-		(for Windows 95/98), &quot;Windows NT x86&quot;, &quot;Windows NT PowerPC&quot;, &quot;Windows
-		Alpha_AXP&quot;, and &quot;Windows NT R4000&quot;. </p></dd><dt><span class="term">getprinter &lt;printername&gt;</span></dt><dd><p>Retrieve the current printer information.  This command 
+		values for <i class="parameter"><tt>arch</tt></i> are "Windows 4.0" 
+		(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
+		Alpha_AXP", and "Windows NT R4000". </p></dd><dt><span class="term">getprinter &lt;printername&gt;</span></dt><dd><p>Retrieve the current printer information.  This command 
 		corresponds to the GetPrinter() MS Platform SDK function. 
 		</p></dd><dt><span class="term">getprintprocdir</span></dt><dd><p>Get
 		print processor
diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html
index 926d8fcbb4..b6eb609bb0 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -21,7 +21,7 @@
 	values, but is preserved in string values. Some items such as 
 	create modes are numeric.</p></div><div class="refsect1" lang="en"><h2>SECTION DESCRIPTIONS</h2><p>Each section in the configuration file (except for the
 	[global] section) describes a shared resource (known
-	as a &quot;share&quot;). The section name is the name of the 
+	as a "share"). The section name is the name of the 
 	shared resource and the parameters within the section define 
 	the shares attributes.</p><p>There are three special sections, [global],
 	[homes] and [printers], which are
@@ -38,14 +38,14 @@
 	privileges in this case.</p><p>Sections other than guest services will require a password 
 	to access them. The client provides the username. As older clients 
 	only provide passwords and not usernames, you may specify a list 
-	of usernames to check against the password using the &quot;user =&quot; 
+	of usernames to check against the password using the "user =" 
 	option in the share definition. For modern clients such as 
 	Windows 95/98/ME/NT/2000, this should not be necessary.</p><p>Note that the access rights granted by the server are 
 	masked by the access rights granted to the specified or guest 
 	UNIX user by the host system. The server does not grant more
 	access than the host system grants.</p><p>The following sample section defines a file space share. 
 	The user has write access to the path <tt class="filename">/home/bar</tt>. 
-	The share is accessed via the share name &quot;foo&quot;:</p><pre class="screen">
+	The share is accessed via the share name "foo":</p><pre class="screen">
 <tt class="computeroutput">
 [foo]
 	path = /home/bar
@@ -83,7 +83,7 @@
 		for your PCs than for UNIX access.</p><p>This is a fast and simple way to give a large number 
 		of clients access to their home directories with a minimum 
 		of fuss.</p><p>A similar process occurs if the requested section 
-		name is &quot;homes&quot;, except that the share name is not 
+		name is "homes", except that the share name is not 
 		changed to that of the requesting user. This method of using
 		the [homes] section works well if different users share 
 		a client PC.</p><p>The [homes] section can specify all the parameters 
@@ -147,8 +147,8 @@ alias|alias|alias|alias...
 		components (if there are more than one) are separated by vertical 
 		bar symbols ('|').</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On SYSV systems which use lpstat to determine what 
 		printers are defined on the system you may be able to use
-		&quot;printcap name = lpstat&quot; to automatically obtain a list 
-		of printers. See the &quot;printcap name&quot; option 
+		"printcap name = lpstat" to automatically obtain a list 
+		of printers. See the "printcap name" option 
 		for more details.</p></div></div></div><div class="refsect1" lang="en"><h2>PARAMETERS</h2><p>parameters define the specific attributes of sections.</p><p>Some parameters are specific to the [global] section
 	(e.g., <span class="emphasis"><em>security</em></span>).  Some parameters are usable 
 	in all sections (e.g., <span class="emphasis"><em>create mode</em></span>). All others 
@@ -164,16 +164,16 @@ alias|alias|alias|alias...
 	not create best bedfellows, but at least you can find them! Where
 	there are synonyms, the preferred synonym is described, others refer 
 	to the preferred synonym.</p></div><div class="refsect1" lang="en"><h2>VARIABLE SUBSTITUTIONS</h2><p>Many of the strings that are settable in the config file 
-	can take substitutions. For example the option &quot;path =
-	/tmp/%u&quot; would be interpreted as &quot;path = 
-	/tmp/john&quot; if the user connected with the username john.</p><p>These substitutions are mostly noted in the descriptions below, 
+	can take substitutions. For example the option "path =
+	/tmp/%u" would be interpreted as "path = 
+	/tmp/john" if the user connected with the username john.</p><p>These substitutions are mostly noted in the descriptions below, 
 	but there are some general substitutions which apply whenever they 
 	might be relevant. These are:</p><div class="variablelist"><dl><dt><span class="term">%U</span></dt><dd><p>session user name (the user name that the client 
 		wanted, not necessarily the same as the one they got).</p></dd><dt><span class="term">%G</span></dt><dd><p>primary group name of %U.</p></dd><dt><span class="term">%h</span></dt><dd><p>the Internet hostname that Samba is running 
 		on.</p></dd><dt><span class="term">%m</span></dt><dd><p>the NetBIOS name of the client machine 
 		(very useful).</p></dd><dt><span class="term">%L</span></dt><dd><p>the NetBIOS name of the server. This allows you 
 		to change your config based on what the client calls you. Your 
-		server can have a &quot;dual personality&quot;.</p><p>Note that this parameter is not available when Samba listens
+		server can have a "dual personality".</p><p>Note that this parameter is not available when Samba listens
                 on port 445, as clients no longer send this information </p></dd><dt><span class="term">%M</span></dt><dd><p>the Internet name of the client machine.
 		</p></dd><dt><span class="term">%R</span></dt><dd><p>the selected protocol level after 
 		protocol negotiation. It can be one of CORE, COREPLUS, 
@@ -182,7 +182,7 @@ alias|alias|alias|alias...
 		machine. Only some are recognized, and those may not be 
 		100% reliable. It currently recognizes Samba, WfWg, Win95,
 		WinNT and Win2k. Anything else will be known as 
-		&quot;UNKNOWN&quot;. If it gets it wrong then sending a level 
+		"UNKNOWN". If it gets it wrong then sending a level 
 		3 log to <a href="mailto:samba@samba.org" target="_top">samba@samba.org
 		</a> should allow it to be fixed.</p></dd><dt><span class="term">%I</span></dt><dd><p>The IP address of the client machine.</p></dd><dt><span class="term">%T</span></dt><dd><p>the current date and time.</p></dd><dt><span class="term">%D</span></dt><dd><p>Name of the domain or workgroup of the current user.</p></dd><dt><span class="term">%$(<i class="replaceable"><tt>envvar</tt></i>)</span></dt><dd><p>The value of the environment variable
 		<i class="replaceable"><tt>envar</tt></i>.</p></dd></dl></div><p>The following substitutes apply only to some configuration options(only those 
@@ -193,33 +193,33 @@ alias|alias|alias|alias...
 		not compiled Samba with the <span class="emphasis"><em>--with-automount</em></span> 
 		option then this value will be the same as %L.</p></dd><dt><span class="term">%p</span></dt><dd><p>the path of the service's home directory, 
 		obtained from your NIS auto.map entry. The NIS auto.map entry 
-		is split up as &quot;%N:%p&quot;.</p></dd></dl></div><p>There are some quite creative things that can be done 
-	with these substitutions and other smb.conf options.</p></div><div class="refsect1" lang="en"><a name="NAMEMANGLINGSECT"></a><h2>NAME MANGLING</h2><p>Samba supports &quot;name mangling&quot; so that DOS and 
+		is split up as "%N:%p".</p></dd></dl></div><p>There are some quite creative things that can be done 
+	with these substitutions and other smb.conf options.</p></div><div class="refsect1" lang="en"><a name="NAMEMANGLINGSECT"></a><h2>NAME MANGLING</h2><p>Samba supports "name mangling" so that DOS and 
 	Windows clients can use files that don't conform to the 8.3 format. 
 	It can also be set to adjust the case of 8.3 format filenames.</p><p>There are several options that control the way mangling is 
 	performed, and they are grouped here rather than listed separately. 
 	For the defaults look at the output of the testparm program. </p><p>All of these options can be set separately for each service 
 	(or globally, of course). </p><p>The options are: </p><div class="variablelist"><dl><dt><span class="term">mangle case = yes/no</span></dt><dd><p> controls if names that have characters that 
-		aren't of the &quot;default&quot; case are mangled. For example, 
-		if this is yes then a name like &quot;Mail&quot; would be mangled. 
+		aren't of the "default" case are mangled. For example, 
+		if this is yes then a name like "Mail" would be mangled. 
 		Default <span class="emphasis"><em>no</em></span>.</p></dd><dt><span class="term">case sensitive = yes/no</span></dt><dd><p>controls whether filenames are case sensitive. If 
 		they aren't then Samba must do a filename search and match on passed 
 		names. Default <span class="emphasis"><em>no</em></span>.</p></dd><dt><span class="term">default case = upper/lower</span></dt><dd><p>controls what the default case is for new 
 		filenames. Default <span class="emphasis"><em>lower</em></span>.</p></dd><dt><span class="term">preserve case = yes/no</span></dt><dd><p>controls if new files are created with the 
 		case that the client passes, or if they are forced to be the 
-		&quot;default&quot; case. Default <span class="emphasis"><em>yes</em></span>.
+		"default" case. Default <span class="emphasis"><em>yes</em></span>.
 		</p></dd><dt><span class="term">short preserve case = yes/no</span></dt><dd><p>controls if new files which conform to 8.3 syntax,
 		that is all in upper case and of suitable length, are created 
-		upper case, or if they are forced to be the &quot;default&quot; 
-		case. This option can be use with &quot;preserve case = yes&quot; 
+		upper case, or if they are forced to be the "default" 
+		case. This option can be use with "preserve case = yes" 
 		to permit long filenames to retain their case, while short names 
 		are lowercased. Default <span class="emphasis"><em>yes</em></span>.</p></dd></dl></div><p>By default, Samba 3.0 has the same semantics as a Windows 
 	NT server, in that it is case insensitive but case preserving.</p></div><div class="refsect1" lang="en"><a name="VALIDATIONSECT"></a><h2>NOTE ABOUT USERNAME/PASSWORD VALIDATION</h2><p>There are a number of ways in which a user can connect 
 	to a service. The server uses the following steps in determining 
 	if it will allow a connection to a specified service. If all the 
 	steps fail, then the connection request is rejected.  However, if one of the 
-	steps succeeds, then the following steps are not checked.</p><p>If the service is marked &quot;guest only = yes&quot; and the
-	server is running with share-level security (&quot;security = share&quot;)
+	steps succeeds, then the following steps are not checked.</p><p>If the service is marked "guest only = yes" and the
+	server is running with share-level security ("security = share")
 	then steps 1 to 5 are skipped.</p><div class="orderedlist"><ol type="1"><li><p>If the client has passed a username/password 
 		pair and that username/password pair is validated by the UNIX 
 		system's password programs then the connection is made as that 
@@ -232,23 +232,28 @@ alias|alias|alias|alias...
 		they match then the connection is allowed as the corresponding 
 		user.</p></li><li><p>If the client has previously validated a
 		username/password pair with the server and the client has passed 
-		the validation token then that username is used. </p></li><li><p>If a &quot;user = &quot; field is given in the
+		the validation token then that username is used. </p></li><li><p>If a "user = " field is given in the
 		<tt class="filename">smb.conf</tt> file for the service and the client 
 		has supplied a password, and that password matches (according to 
 		the UNIX system's password checking) with one of the usernames 
-		from the &quot;user =&quot; field then the connection is made as 
-		the username in the &quot;user =&quot; line. If one 
-		of the username in the &quot;user =&quot; list begins with a
+		from the "user =" field then the connection is made as 
+		the username in the "user =" line. If one 
+		of the username in the "user =" list begins with a
 		'@' then that name expands to a list of names in 
 		the group of the same name.</p></li><li><p>If the service is a guest service then a 
-		connection is made as the username given in the &quot;guest 
-		account =&quot; for the service, irrespective of the 
+		connection is made as the username given in the "guest 
+		account =" for the service, irrespective of the 
 		supplied password.</p></li></ol></div></div><div class="refsect1" lang="en"><h2>COMPLETE LIST OF GLOBAL PARAMETERS</h2><p>Here is a list of all global parameters. See the section of 
-	each parameter for details.  Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ABORTSHUTDOWNSCRIPT"><i class="parameter"><tt>abort shutdown script</tt></i></a></p></li><li><p><a href="#ADDGROUPSCRIPT"><i class="parameter"><tt>add group script</tt></i></a></p></li><li><p><a href="#ADDMACHINESCRIPT"><i class="parameter"><tt>add machine script</tt></i></a></p></li><li><p><a href="#ADDPRINTERCOMMAND"><i class="parameter"><tt>addprinter command</tt></i></a></p></li><li><p><a href="#ADDSHARECOMMAND"><i class="parameter"><tt>add share command</tt></i></a></p></li><li><p><a href="#ADDUSERSCRIPT"><i class="parameter"><tt>add user script</tt></i></a></p></li><li><p><a href="#ADDUSERTOGROUPSCRIPT"><i class="parameter"><tt>add user to group script</tt></i></a></p></li><li><p><a href="#ALGORITHMICRIDBASE"><i class="parameter"><tt>algorithmic rid base</tt></i></a></p></li><li><p><a href="#ALLOWTRUSTEDDOMAINS"><i class="parameter"><tt>allow trusted domains</tt></i></a></p></li><li><p><a href="#ANNOUNCEAS"><i class="parameter"><tt>announce as</tt></i></a></p></li><li><p><a href="#ANNOUNCEVERSION"><i class="parameter"><tt>announce version</tt></i></a></p></li><li><p><a href="#AUTHMETHODS"><i class="parameter"><tt>auth methods</tt></i></a></p></li><li><p><a href="#AUTOSERVICES"><i class="parameter"><tt>auto services</tt></i></a></p></li><li><p><a href="#BINDINTERFACESONLY"><i class="parameter"><tt>bind interfaces only</tt></i></a></p></li><li><p><a href="#BROWSELIST"><i class="parameter"><tt>browse list</tt></i></a></p></li><li><p><a href="#CHANGENOTIFYTIMEOUT"><i class="parameter"><tt>change notify timeout</tt></i></a></p></li><li><p><a href="#CHANGESHARECOMMAND"><i class="parameter"><tt>change share command</tt></i></a></p></li><li><p><a href="#CLIENTLANMANAUTH"><i class="parameter"><tt>client lanman auth</tt></i></a></p></li><li><p><a href="#CLIENTNTLMV2AUTH"><i class="parameter"><tt>client ntlmv2 auth</tt></i></a></p></li><li><p><a href="#CLIENTUSESPNEGO"><i class="parameter"><tt>client use spnego</tt></i></a></p></li><li><p><a href="#CONFIGFILE"><i class="parameter"><tt>config file</tt></i></a></p></li><li><p><a href="#DEADTIME"><i class="parameter"><tt>deadtime</tt></i></a></p></li><li><p><a href="#DEBUGHIRESTIMESTAMP"><i class="parameter"><tt>debug hires timestamp</tt></i></a></p></li><li><p><a href="#DEBUGLEVEL"><i class="parameter"><tt>debuglevel</tt></i></a></p></li><li><p><a href="#DEBUGPID"><i class="parameter"><tt>debug pid</tt></i></a></p></li><li><p><a href="#DEBUGTIMESTAMP"><i class="parameter"><tt>debug timestamp</tt></i></a></p></li><li><p><a href="#DEBUGUID"><i class="parameter"><tt>debug uid</tt></i></a></p></li><li><p><a href="#DEFAULTSERVICE"><i class="parameter"><tt>default service</tt></i></a></p></li><li><p><a href="#DEFAULT"><i class="parameter"><tt>default</tt></i></a></p></li><li><p><a href="#DELETEGROUPSCRIPT"><i class="parameter"><tt>delete group script</tt></i></a></p></li><li><p><a href="#DELETEPRINTERCOMMAND"><i class="parameter"><tt>deleteprinter command</tt></i></a></p></li><li><p><a href="#DELETESHARECOMMAND"><i class="parameter"><tt>delete share command</tt></i></a></p></li><li><p><a href="#DELETEUSERFROMGROUPSCRIPT"><i class="parameter"><tt>delete user from group script</tt></i></a></p></li><li><p><a href="#DELETEUSERSCRIPT"><i class="parameter"><tt>delete user script</tt></i></a></p></li><li><p><a href="#DFREECOMMAND"><i class="parameter"><tt>dfree command</tt></i></a></p></li><li><p><a href="#DISABLENETBIOS"><i class="parameter"><tt>disable netbios</tt></i></a></p></li><li><p><a href="#DISABLESPOOLSS"><i class="parameter"><tt>disable spoolss</tt></i></a></p></li><li><p><a href="#DISPLAYCHARSET"><i class="parameter"><tt>display charset</tt></i></a></p></li><li><p><a href="#DNSPROXY"><i class="parameter"><tt>dns proxy</tt></i></a></p></li><li><p><a href="#DOMAINLOGONS"><i class="parameter"><tt>domain logons</tt></i></a></p></li><li><p><a href="#DOMAINMASTER"><i class="parameter"><tt>domain master</tt></i></a></p></li><li><p><a href="#DOSCHARSET"><i class="parameter"><tt>dos charset</tt></i></a></p></li><li><p><a href="#ENABLERIDALGORITHM"><i class="parameter"><tt>enable rid algorithm</tt></i></a></p></li><li><p><a href="#ENCRYPTPASSWORDS"><i class="parameter"><tt>encrypt passwords</tt></i></a></p></li><li><p><a href="#ENHANCEDBROWSING"><i class="parameter"><tt>enhanced browsing</tt></i></a></p></li><li><p><a href="#ENUMPORTSCOMMAND"><i class="parameter"><tt>enumports command</tt></i></a></p></li><li><p><a href="#GETQUOTACOMMAND"><i class="parameter"><tt>get quota command</tt></i></a></p></li><li><p><a href="#GETWDCACHE"><i class="parameter"><tt>getwd cache</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i class="parameter"><tt>guest account</tt></i></a></p></li><li><p><a href="#HIDELOCALUSERS"><i class="parameter"><tt>hide local users</tt></i></a></p></li><li><p><a href="#HOMEDIRMAP"><i class="parameter"><tt>homedir map</tt></i></a></p></li><li><p><a href="#HOSTMSDFS"><i class="parameter"><tt>host msdfs</tt></i></a></p></li><li><p><a href="#HOSTNAMELOOKUPS"><i class="parameter"><tt>hostname lookups</tt></i></a></p></li><li><p><a href="#HOSTSEQUIV"><i class="parameter"><tt>hosts equiv</tt></i></a></p></li><li><p><a href="#IDMAPBACKEND"><i class="parameter"><tt>idmap backend</tt></i></a></p></li><li><p><a href="#IDMAPGID"><i class="parameter"><tt>idmap gid</tt></i></a></p></li><li><p><a href="#IDMAPUID"><i class="parameter"><tt>idmap uid</tt></i></a></p></li><li><p><a href="#INCLUDE"><i class="parameter"><tt>include</tt></i></a></p></li><li><p><a href="#INTERFACES"><i class="parameter"><tt>interfaces</tt></i></a></p></li><li><p><a href="#KEEPALIVE"><i class="parameter"><tt>keepalive</tt></i></a></p></li><li><p><a href="#KERNELOPLOCKS"><i class="parameter"><tt>kernel oplocks</tt></i></a></p></li><li><p><a href="#LANMANAUTH"><i class="parameter"><tt>lanman auth</tt></i></a></p></li><li><p><a href="#LARGEREADWRITE"><i class="parameter"><tt>large readwrite</tt></i></a></p></li><li><p><a href="#LDAPADMINDN"><i class="parameter"><tt>ldap admin dn</tt></i></a></p></li><li><p><a href="#LDAPDELETEDN"><i class="parameter"><tt>ldap delete dn</tt></i></a></p></li><li><p><a href="#LDAPFILTER"><i class="parameter"><tt>ldap filter</tt></i></a></p></li><li><p><a href="#LDAPMACHINESUFFIX"><i class="parameter"><tt>ldap machine suffix</tt></i></a></p></li><li><p><a href="#LDAPPASSWDSYNC"><i class="parameter"><tt>ldap passwd sync</tt></i></a></p></li><li><p><a href="#LDAPPORT"><i class="parameter"><tt>ldap port</tt></i></a></p></li><li><p><a href="#LDAPSERVER"><i class="parameter"><tt>ldap server</tt></i></a></p></li><li><p><a href="#LDAPSSL"><i class="parameter"><tt>ldap ssl</tt></i></a></p></li><li><p><a href="#LDAPSUFFIX"><i class="parameter"><tt>ldap suffix</tt></i></a></p></li><li><p><a href="#LDAPTRUSTIDS"><i class="parameter"><tt>ldap trust ids</tt></i></a></p></li><li><p><a href="#LDAPUSERSUFFIX"><i class="parameter"><tt>ldap user suffix</tt></i></a></p></li><li><p><a href="#LMANNOUNCE"><i class="parameter"><tt>lm announce</tt></i></a></p></li><li><p><a href="#LMINTERVAL"><i class="parameter"><tt>lm interval</tt></i></a></p></li><li><p><a href="#LOADPRINTERS"><i class="parameter"><tt>load printers</tt></i></a></p></li><li><p><a href="#LOCALMASTER"><i class="parameter"><tt>local master</tt></i></a></p></li><li><p><a href="#LOCKDIRECTORY"><i class="parameter"><tt>lock directory</tt></i></a></p></li><li><p><a href="#LOCKDIR"><i class="parameter"><tt>lock dir</tt></i></a></p></li><li><p><a href="#LOCKSPINCOUNT"><i class="parameter"><tt>lock spin count</tt></i></a></p></li><li><p><a href="#LOCKSPINTIME"><i class="parameter"><tt>lock spin time</tt></i></a></p></li><li><p><a href="#LOGFILE"><i class="parameter"><tt>log file</tt></i></a></p></li><li><p><a href="#LOGLEVEL"><i class="parameter"><tt>log level</tt></i></a></p></li><li><p><a href="#LOGONDRIVE"><i class="parameter"><tt>logon drive</tt></i></a></p></li><li><p><a href="#LOGONHOME"><i class="parameter"><tt>logon home</tt></i></a></p></li><li><p><a href="#LOGONPATH"><i class="parameter"><tt>logon path</tt></i></a></p></li><li><p><a href="#LOGONSCRIPT"><i class="parameter"><tt>logon script</tt></i></a></p></li><li><p><a href="#LPQCACHETIME"><i class="parameter"><tt>lpq cache time</tt></i></a></p></li><li><p><a href="#MACHINEPASSWORDTIMEOUT"><i class="parameter"><tt>machine password timeout</tt></i></a></p></li><li><p><a href="#MANGLEDSTACK"><i class="parameter"><tt>mangled stack</tt></i></a></p></li><li><p><a href="#MANGLEPREFIX"><i class="parameter"><tt>mangle prefix</tt></i></a></p></li><li><p><a href="#MANGLINGMETHOD"><i class="parameter"><tt>mangling method</tt></i></a></p></li><li><p><a href="#MAPTOGUEST"><i class="parameter"><tt>map to guest</tt></i></a></p></li><li><p><a href="#MAXDISKSIZE"><i class="parameter"><tt>max disk size</tt></i></a></p></li><li><p><a href="#MAXLOGSIZE"><i class="parameter"><tt>max log size</tt></i></a></p></li><li><p><a href="#MAXMUX"><i class="parameter"><tt>max mux</tt></i></a></p></li><li><p><a href="#MAXOPENFILES"><i class="parameter"><tt>max open files</tt></i></a></p></li><li><p><a href="#MAXPROTOCOL"><i class="parameter"><tt>max protocol</tt></i></a></p></li><li><p><a href="#MAXSMBDPROCESSES"><i class="parameter"><tt>max smbd processes</tt></i></a></p></li><li><p><a href="#MAXTTL"><i class="parameter"><tt>max ttl</tt></i></a></p></li><li><p><a href="#MAXWINSTTL"><i class="parameter"><tt>max wins ttl</tt></i></a></p></li><li><p><a href="#MAXXMIT"><i class="parameter"><tt>max xmit</tt></i></a></p></li><li><p><a href="#MESSAGECOMMAND"><i class="parameter"><tt>message command</tt></i></a></p></li><li><p><a href="#MINPASSWDLENGTH"><i class="parameter"><tt>min passwd length</tt></i></a></p></li><li><p><a href="#MINPASSWORDLENGTH"><i class="parameter"><tt>min password length</tt></i></a></p></li><li><p><a href="#MINPROTOCOL"><i class="parameter"><tt>min protocol</tt></i></a></p></li><li><p><a href="#MINWINSTTL"><i class="parameter"><tt>min wins ttl</tt></i></a></p></li><li><p><a href="#NAMECACHETIMEOUT"><i class="parameter"><tt>name cache timeout</tt></i></a></p></li><li><p><a href="#NAMERESOLVEORDER"><i class="parameter"><tt>name resolve order</tt></i></a></p></li><li><p><a href="#NETBIOSALIASES"><i class="parameter"><tt>netbios aliases</tt></i></a></p></li><li><p><a href="#NETBIOSNAME"><i class="parameter"><tt>netbios name</tt></i></a></p></li><li><p><a href="#NETBIOSSCOPE"><i class="parameter"><tt>netbios scope</tt></i></a></p></li><li><p><a href="#NISHOMEDIR"><i class="parameter"><tt>nis homedir</tt></i></a></p></li><li><p><a href="#NTLMAUTH"><i class="parameter"><tt>ntlm auth</tt></i></a></p></li><li><p><a href="#NTPIPESUPPORT"><i class="parameter"><tt>nt pipe support</tt></i></a></p></li><li><p><a href="#NTSTATUSSUPPORT"><i class="parameter"><tt>nt status support</tt></i></a></p></li><li><p><a href="#NULLPASSWORDS"><i class="parameter"><tt>null passwords</tt></i></a></p></li><li><p><a href="#OBEYPAMRESTRICTIONS"><i class="parameter"><tt>obey pam restrictions</tt></i></a></p></li><li><p><a href="#OPLOCKBREAKWAITTIME"><i class="parameter"><tt>oplock break wait time</tt></i></a></p></li><li><p><a href="#OS2DRIVERMAP"><i class="parameter"><tt>os2 driver map</tt></i></a></p></li><li><p><a href="#OSLEVEL"><i class="parameter"><tt>os level</tt></i></a></p></li><li><p><a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i></a></p></li><li><p><a href="#PANICACTION"><i class="parameter"><tt>panic action</tt></i></a></p></li><li><p><a href="#PARANOIDSERVERSECURITY"><i class="parameter"><tt>paranoid server security</tt></i></a></p></li><li><p><a href="#PASSDBBACKEND"><i class="parameter"><tt>passdb backend</tt></i></a></p></li><li><p><a href="#PASSWDCHATDEBUG"><i class="parameter"><tt>passwd chat debug</tt></i></a></p></li><li><p><a href="#PASSWDCHAT"><i class="parameter"><tt>passwd chat</tt></i></a></p></li><li><p><a href="#PASSWDPROGRAM"><i class="parameter"><tt>passwd program</tt></i></a></p></li><li><p><a href="#PASSWORDLEVEL"><i class="parameter"><tt>password level</tt></i></a></p></li><li><p><a href="#PASSWORDSERVER"><i class="parameter"><tt>password server</tt></i></a></p></li><li><p><a href="#PIDDIRECTORY"><i class="parameter"><tt>pid directory</tt></i></a></p></li><li><p><a href="#PREFEREDMASTER"><i class="parameter"><tt>prefered master</tt></i></a></p></li><li><p><a href="#PREFERREDMASTER"><i class="parameter"><tt>preferred master</tt></i></a></p></li><li><p><a href="#PRELOADMODULES"><i class="parameter"><tt>preload modules</tt></i></a></p></li><li><p><a href="#PRELOAD"><i class="parameter"><tt>preload</tt></i></a></p></li><li><p><a href="#PRINTCAP"><i class="parameter"><tt>printcap</tt></i></a></p></li><li><p><a href="#PRIVATEDIR"><i class="parameter"><tt>private dir</tt></i></a></p></li><li><p><a href="#PROTOCOL"><i class="parameter"><tt>protocol</tt></i></a></p></li><li><p><a href="#READBMPX"><i class="parameter"><tt>read bmpx</tt></i></a></p></li><li><p><a href="#READRAW"><i class="parameter"><tt>read raw</tt></i></a></p></li><li><p><a href="#READSIZE"><i class="parameter"><tt>read size</tt></i></a></p></li><li><p><a href="#REALM"><i class="parameter"><tt>realm</tt></i></a></p></li><li><p><a href="#REMOTEANNOUNCE"><i class="parameter"><tt>remote announce</tt></i></a></p></li><li><p><a href="#REMOTEBROWSESYNC"><i class="parameter"><tt>remote browse sync</tt></i></a></p></li><li><p><a href="#RESTRICTANONYMOUS"><i class="parameter"><tt>restrict anonymous</tt></i></a></p></li><li><p><a href="#ROOTDIRECTORY"><i class="parameter"><tt>root directory</tt></i></a></p></li><li><p><a href="#ROOTDIR"><i class="parameter"><tt>root dir</tt></i></a></p></li><li><p><a href="#ROOT"><i class="parameter"><tt>root</tt></i></a></p></li><li><p><a href="#SECURITY"><i class="parameter"><tt>security</tt></i></a></p></li><li><p><a href="#SERVERSCHANNEL"><i class="parameter"><tt>server schannel</tt></i></a></p></li><li><p><a href="#SERVERSTRING"><i class="parameter"><tt>server string</tt></i></a></p></li><li><p><a href="#SETPRIMARYGROUPSCRIPT"><i class="parameter"><tt>set primary group script</tt></i></a></p></li><li><p><a href="#SETQUOTACOMMAND"><i class="parameter"><tt>set quota command</tt></i></a></p></li><li><p><a href="#SHOWADDPRINTERWIZARD"><i class="parameter"><tt>show add printer wizard</tt></i></a></p></li><li><p><a href="#SHUTDOWNSCRIPT"><i class="parameter"><tt>shutdown script</tt></i></a></p></li><li><p><a href="#SMBPASSWDFILE"><i class="parameter"><tt>smb passwd file</tt></i></a></p></li><li><p><a href="#SMBPORTS"><i class="parameter"><tt>smb ports</tt></i></a></p></li><li><p><a href="#SOCKETADDRESS"><i class="parameter"><tt>socket address</tt></i></a></p></li><li><p><a href="#SOCKETOPTIONS"><i class="parameter"><tt>socket options</tt></i></a></p></li><li><p><a href="#SOURCEENVIRONMENT"><i class="parameter"><tt>source environment</tt></i></a></p></li><li><p><a href="#STATCACHE"><i class="parameter"><tt>stat cache</tt></i></a></p></li><li><p><a href="#STRIPDOT"><i class="parameter"><tt>strip dot</tt></i></a></p></li><li><p><a href="#SYSLOGONLY"><i class="parameter"><tt>syslog only</tt></i></a></p></li><li><p><a href="#SYSLOG"><i class="parameter"><tt>syslog</tt></i></a></p></li><li><p><a href="#TEMPLATEHOMEDIR"><i class="parameter"><tt>template homedir</tt></i></a></p></li><li><p><a href="#TEMPLATEPRIMARYGROUP"><i class="parameter"><tt>template primary group</tt></i></a></p></li><li><p><a href="#TEMPLATESHELL"><i class="parameter"><tt>template shell</tt></i></a></p></li><li><p><a href="#TIMEOFFSET"><i class="parameter"><tt>time offset</tt></i></a></p></li><li><p><a href="#TIMESERVER"><i class="parameter"><tt>time server</tt></i></a></p></li><li><p><a href="#TIMESTAMPLOGS"><i class="parameter"><tt>timestamp logs</tt></i></a></p></li><li><p><a href="#UNICODE"><i class="parameter"><tt>unicode</tt></i></a></p></li><li><p><a href="#UNIXCHARSET"><i class="parameter"><tt>unix charset</tt></i></a></p></li><li><p><a href="#UNIXEXTENSIONS"><i class="parameter"><tt>unix extensions</tt></i></a></p></li><li><p><a href="#UNIXPASSWORDSYNC"><i class="parameter"><tt>unix password sync</tt></i></a></p></li><li><p><a href="#UPDATEENCRYPTED"><i class="parameter"><tt>update encrypted</tt></i></a></p></li><li><p><a href="#USEMMAP"><i class="parameter"><tt>use mmap</tt></i></a></p></li><li><p><a href="#USERNAMELEVEL"><i class="parameter"><tt>username level</tt></i></a></p></li><li><p><a href="#USERNAMEMAP"><i class="parameter"><tt>username map</tt></i></a></p></li><li><p><a href="#USESPNEGO"><i class="parameter"><tt>use spnego</tt></i></a></p></li><li><p><a href="#UTMPDIRECTORY"><i class="parameter"><tt>utmp directory</tt></i></a></p></li><li><p><a href="#UTMP"><i class="parameter"><tt>utmp</tt></i></a></p></li><li><p><a href="#WINBINDCACHETIME"><i class="parameter"><tt>winbind cache time</tt></i></a></p></li><li><p><a href="#WINBINDENABLELOCALACCOUNTS"><i class="parameter"><tt>winbind enable local accounts</tt></i></a></p></li><li><p><a href="#WINBINDENUMGROUPS"><i class="parameter"><tt>winbind enum groups</tt></i></a></p></li><li><p><a href="#WINBINDENUMUSERS"><i class="parameter"><tt>winbind enum users</tt></i></a></p></li><li><p><a href="#WINBINDGID"><i class="parameter"><tt>winbind gid</tt></i></a></p></li><li><p><a href="#WINBINDSEPARATOR"><i class="parameter"><tt>winbind separator</tt></i></a></p></li><li><p><a href="#WINBINDTRUSTEDDOMAINSONLY"><i class="parameter"><tt>winbind trusted domains only</tt></i></a></p></li><li><p><a href="#WINBINDUID"><i class="parameter"><tt>winbind uid</tt></i></a></p></li><li><p><a href="#WINBINDUSEDEFAULTDOMAIN"><i class="parameter"><tt>winbind use default domain</tt></i></a></p></li><li><p><a href="#WINSHOOK"><i class="parameter"><tt>wins hook</tt></i></a></p></li><li><p><a href="#WINSPARTNERS"><i class="parameter"><tt>wins partners</tt></i></a></p></li><li><p><a href="#WINSPROXY"><i class="parameter"><tt>wins proxy</tt></i></a></p></li><li><p><a href="#WINSSERVER"><i class="parameter"><tt>wins server</tt></i></a></p></li><li><p><a href="#WINSSUPPORT"><i class="parameter"><tt>wins support</tt></i></a></p></li><li><p><a href="#WORKGROUP"><i class="parameter"><tt>workgroup</tt></i></a></p></li><li><p><a href="#WRITERAW"><i class="parameter"><tt>write raw</tt></i></a></p></li><li><p><a href="#WTMPDIRECTORY"><i class="parameter"><tt>wtmp directory</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>COMPLETE LIST OF SERVICE PARAMETERS</h2><p>Here is a list of all service parameters. See the section on 
-	each parameter for details. Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ADMINUSERS"><i class="parameter"><tt>admin users</tt></i></a></p></li><li><p><a href="#ALLOWHOSTS"><i class="parameter"><tt>allow hosts</tt></i></a></p></li><li><p><a href="#AVAILABLE"><i class="parameter"><tt>available</tt></i></a></p></li><li><p><a href="#BLOCKINGLOCKS"><i class="parameter"><tt>blocking locks</tt></i></a></p></li><li><p><a href="#BLOCKSIZE"><i class="parameter"><tt>block size</tt></i></a></p></li><li><p><a href="#BROWSABLE"><i class="parameter"><tt>browsable</tt></i></a></p></li><li><p><a href="#BROWSEABLE"><i class="parameter"><tt>browseable</tt></i></a></p></li><li><p><a href="#CASESENSITIVE"><i class="parameter"><tt>case sensitive</tt></i></a></p></li><li><p><a href="#CASESIGNAMES"><i class="parameter"><tt>casesignames</tt></i></a></p></li><li><p><a href="#COMMENT"><i class="parameter"><tt>comment</tt></i></a></p></li><li><p><a href="#COPY"><i class="parameter"><tt>copy</tt></i></a></p></li><li><p><a href="#CREATEMASK"><i class="parameter"><tt>create mask</tt></i></a></p></li><li><p><a href="#CREATEMODE"><i class="parameter"><tt>create mode</tt></i></a></p></li><li><p><a href="#CSCPOLICY"><i class="parameter"><tt>csc policy</tt></i></a></p></li><li><p><a href="#DEFAULTCASE"><i class="parameter"><tt>default case</tt></i></a></p></li><li><p><a href="#DEFAULTDEVMODE"><i class="parameter"><tt>default devmode</tt></i></a></p></li><li><p><a href="#DELETEREADONLY"><i class="parameter"><tt>delete readonly</tt></i></a></p></li><li><p><a href="#DELETEVETOFILES"><i class="parameter"><tt>delete veto files</tt></i></a></p></li><li><p><a href="#DENYHOSTS"><i class="parameter"><tt>deny hosts</tt></i></a></p></li><li><p><a href="#DIRECTORYMASK"><i class="parameter"><tt>directory mask</tt></i></a></p></li><li><p><a href="#DIRECTORYMODE"><i class="parameter"><tt>directory mode</tt></i></a></p></li><li><p><a href="#DIRECTORYSECURITYMASK"><i class="parameter"><tt>directory security mask</tt></i></a></p></li><li><p><a href="#DIRECTORY"><i class="parameter"><tt>directory</tt></i></a></p></li><li><p><a href="#DONTDESCEND"><i class="parameter"><tt>dont descend</tt></i></a></p></li><li><p><a href="#DOSFILEMODE"><i class="parameter"><tt>dos filemode</tt></i></a></p></li><li><p><a href="#DOSFILETIMERESOLUTION"><i class="parameter"><tt>dos filetime resolution</tt></i></a></p></li><li><p><a href="#DOSFILETIMES"><i class="parameter"><tt>dos filetimes</tt></i></a></p></li><li><p><a href="#EXEC"><i class="parameter"><tt>exec</tt></i></a></p></li><li><p><a href="#FAKEDIRECTORYCREATETIMES"><i class="parameter"><tt>fake directory create times</tt></i></a></p></li><li><p><a href="#FAKEOPLOCKS"><i class="parameter"><tt>fake oplocks</tt></i></a></p></li><li><p><a href="#FOLLOWSYMLINKS"><i class="parameter"><tt>follow symlinks</tt></i></a></p></li><li><p><a href="#FORCECREATEMODE"><i class="parameter"><tt>force create mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYMODE"><i class="parameter"><tt>force directory mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYSECURITYMODE"><i class="parameter"><tt>force directory security mode</tt></i></a></p></li><li><p><a href="#FORCEGROUP"><i class="parameter"><tt>force group</tt></i></a></p></li><li><p><a href="#FORCESECURITYMODE"><i class="parameter"><tt>force security mode</tt></i></a></p></li><li><p><a href="#FORCEUSER"><i class="parameter"><tt>force user</tt></i></a></p></li><li><p><a href="#FSTYPE"><i class="parameter"><tt>fstype</tt></i></a></p></li><li><p><a href="#GROUP"><i class="parameter"><tt>group</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i class="parameter"><tt>guest account</tt></i></a></p></li><li><p><a href="#GUESTOK"><i class="parameter"><tt>guest ok</tt></i></a></p></li><li><p><a href="#GUESTONLY"><i class="parameter"><tt>guest only</tt></i></a></p></li><li><p><a href="#HIDEDOTFILES"><i class="parameter"><tt>hide dot files</tt></i></a></p></li><li><p><a href="#HIDEFILES"><i class="parameter"><tt>hide files</tt></i></a></p></li><li><p><a href="#HIDESPECIALFILES"><i class="parameter"><tt>hide special files</tt></i></a></p></li><li><p><a href="#HIDEUNREADABLE"><i class="parameter"><tt>hide unreadable</tt></i></a></p></li><li><p><a href="#HIDEUNWRITEABLEFILES"><i class="parameter"><tt>hide unwriteable files</tt></i></a></p></li><li><p><a href="#HOSTSALLOW"><i class="parameter"><tt>hosts allow</tt></i></a></p></li><li><p><a href="#HOSTSDENY"><i class="parameter"><tt>hosts deny</tt></i></a></p></li><li><p><a href="#INHERITACLS"><i class="parameter"><tt>inherit acls</tt></i></a></p></li><li><p><a href="#INHERITPERMISSIONS"><i class="parameter"><tt>inherit permissions</tt></i></a></p></li><li><p><a href="#INVALIDUSERS"><i class="parameter"><tt>invalid users</tt></i></a></p></li><li><p><a href="#LEVEL2OPLOCKS"><i class="parameter"><tt>level2 oplocks</tt></i></a></p></li><li><p><a href="#LOCKING"><i class="parameter"><tt>locking</tt></i></a></p></li><li><p><a href="#LPPAUSECOMMAND"><i class="parameter"><tt>lppause command</tt></i></a></p></li><li><p><a href="#LPQCOMMAND"><i class="parameter"><tt>lpq command</tt></i></a></p></li><li><p><a href="#LPRESUMECOMMAND"><i class="parameter"><tt>lpresume command</tt></i></a></p></li><li><p><a href="#LPRMCOMMAND"><i class="parameter"><tt>lprm command</tt></i></a></p></li><li><p><a href="#MAGICOUTPUT"><i class="parameter"><tt>magic output</tt></i></a></p></li><li><p><a href="#MAGICSCRIPT"><i class="parameter"><tt>magic script</tt></i></a></p></li><li><p><a href="#MANGLECASE"><i class="parameter"><tt>mangle case</tt></i></a></p></li><li><p><a href="#MANGLEDMAP"><i class="parameter"><tt>mangled map</tt></i></a></p></li><li><p><a href="#MANGLEDNAMES"><i class="parameter"><tt>mangled names</tt></i></a></p></li><li><p><a href="#MANGLINGCHAR"><i class="parameter"><tt>mangling char</tt></i></a></p></li><li><p><a href="#MAPACLINHERIT"><i class="parameter"><tt>map acl inherit</tt></i></a></p></li><li><p><a href="#MAPARCHIVE"><i class="parameter"><tt>map archive</tt></i></a></p></li><li><p><a href="#MAPHIDDEN"><i class="parameter"><tt>map hidden</tt></i></a></p></li><li><p><a href="#MAPSYSTEM"><i class="parameter"><tt>map system</tt></i></a></p></li><li><p><a href="#MAXCONNECTIONS"><i class="parameter"><tt>max connections</tt></i></a></p></li><li><p><a href="#MAXPRINTJOBS"><i class="parameter"><tt>max print jobs</tt></i></a></p></li><li><p><a href="#MAXREPORTEDPRINTJOBS"><i class="parameter"><tt>max reported print jobs</tt></i></a></p></li><li><p><a href="#MINPRINTSPACE"><i class="parameter"><tt>min print space</tt></i></a></p></li><li><p><a href="#MSDFSPROXY"><i class="parameter"><tt>msdfs proxy</tt></i></a></p></li><li><p><a href="#MSDFSROOT"><i class="parameter"><tt>msdfs root</tt></i></a></p></li><li><p><a href="#NTACLSUPPORT"><i class="parameter"><tt>nt acl support</tt></i></a></p></li><li><p><a href="#ONLYGUEST"><i class="parameter"><tt>only guest</tt></i></a></p></li><li><p><a href="#ONLYUSER"><i class="parameter"><tt>only user</tt></i></a></p></li><li><p><a href="#OPLOCKCONTENTIONLIMIT"><i class="parameter"><tt>oplock contention limit</tt></i></a></p></li><li><p><a href="#OPLOCKS"><i class="parameter"><tt>oplocks</tt></i></a></p></li><li><p><a href="#PATH"><i class="parameter"><tt>path</tt></i></a></p></li><li><p><a href="#POSIXLOCKING"><i class="parameter"><tt>posix locking</tt></i></a></p></li><li><p><a href="#POSTEXEC"><i class="parameter"><tt>postexec</tt></i></a></p></li><li><p><a href="#PREEXECCLOSE"><i class="parameter"><tt>preexec close</tt></i></a></p></li><li><p><a href="#PREEXEC"><i class="parameter"><tt>preexec</tt></i></a></p></li><li><p><a href="#PRESERVECASE"><i class="parameter"><tt>preserve case</tt></i></a></p></li><li><p><a href="#PRINTABLE"><i class="parameter"><tt>printable</tt></i></a></p></li><li><p><a href="#PRINTCAPNAME"><i class="parameter"><tt>printcap name</tt></i></a></p></li><li><p><a href="#PRINTCOMMAND"><i class="parameter"><tt>print command</tt></i></a></p></li><li><p><a href="#PRINTERADMIN"><i class="parameter"><tt>printer admin</tt></i></a></p></li><li><p><a href="#PRINTERNAME"><i class="parameter"><tt>printer name</tt></i></a></p></li><li><p><a href="#PRINTER"><i class="parameter"><tt>printer</tt></i></a></p></li><li><p><a href="#PRINTING"><i class="parameter"><tt>printing</tt></i></a></p></li><li><p><a href="#PRINTOK"><i class="parameter"><tt>print ok</tt></i></a></p></li><li><p><a href="#PROFILEACLS"><i class="parameter"><tt>profile acls</tt></i></a></p></li><li><p><a href="#PUBLIC"><i class="parameter"><tt>public</tt></i></a></p></li><li><p><a href="#QUEUEPAUSECOMMAND"><i class="parameter"><tt>queuepause command</tt></i></a></p></li><li><p><a href="#QUEUERESUMECOMMAND"><i class="parameter"><tt>queueresume command</tt></i></a></p></li><li><p><a href="#READLIST"><i class="parameter"><tt>read list</tt></i></a></p></li><li><p><a href="#READONLY"><i class="parameter"><tt>read only</tt></i></a></p></li><li><p><a href="#ROOTPOSTEXEC"><i class="parameter"><tt>root postexec</tt></i></a></p></li><li><p><a href="#ROOTPREEXECCLOSE"><i class="parameter"><tt>root preexec close</tt></i></a></p></li><li><p><a href="#ROOTPREEXEC"><i class="parameter"><tt>root preexec</tt></i></a></p></li><li><p><a href="#SECURITYMASK"><i class="parameter"><tt>security mask</tt></i></a></p></li><li><p><a href="#SETDIRECTORY"><i class="parameter"><tt>set directory</tt></i></a></p></li><li><p><a href="#SHAREMODES"><i class="parameter"><tt>share modes</tt></i></a></p></li><li><p><a href="#SHORTPRESERVECASE"><i class="parameter"><tt>short preserve case</tt></i></a></p></li><li><p><a href="#STRICTALLOCATE"><i class="parameter"><tt>strict allocate</tt></i></a></p></li><li><p><a href="#STRICTLOCKING"><i class="parameter"><tt>strict locking</tt></i></a></p></li><li><p><a href="#STRICTSYNC"><i class="parameter"><tt>strict sync</tt></i></a></p></li><li><p><a href="#SYNCALWAYS"><i class="parameter"><tt>sync always</tt></i></a></p></li><li><p><a href="#USECLIENTDRIVER"><i class="parameter"><tt>use client driver</tt></i></a></p></li><li><p><a href="#USERNAME"><i class="parameter"><tt>username</tt></i></a></p></li><li><p><a href="#USERS"><i class="parameter"><tt>users</tt></i></a></p></li><li><p><a href="#USER"><i class="parameter"><tt>user</tt></i></a></p></li><li><p><a href="#USESENDFILE"><i class="parameter"><tt>use sendfile</tt></i></a></p></li><li><p><a href="#VALIDUSERS"><i class="parameter"><tt>valid users</tt></i></a></p></li><li><p><a href="#-VALID"><i class="parameter"><tt>-valid</tt></i></a></p></li><li><p><a href="#VETOFILES"><i class="parameter"><tt>veto files</tt></i></a></p></li><li><p><a href="#VETOOPLOCKFILES"><i class="parameter"><tt>veto oplock files</tt></i></a></p></li><li><p><a href="#VFSOBJECTS"><i class="parameter"><tt>vfs objects</tt></i></a></p></li><li><p><a href="#VFSOBJECT"><i class="parameter"><tt>vfs object</tt></i></a></p></li><li><p><a href="#VOLUME"><i class="parameter"><tt>volume</tt></i></a></p></li><li><p><a href="#WIDELINKS"><i class="parameter"><tt>wide links</tt></i></a></p></li><li><p><a href="#WRITABLE"><i class="parameter"><tt>writable</tt></i></a></p></li><li><p><a href="#WRITEABLE"><i class="parameter"><tt>writeable</tt></i></a></p></li><li><p><a href="#WRITECACHESIZE"><i class="parameter"><tt>write cache size</tt></i></a></p></li><li><p><a href="#WRITELIST"><i class="parameter"><tt>write list</tt></i></a></p></li><li><p><a href="#WRITEOK"><i class="parameter"><tt>write ok</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXPLANATION OF EACH PARAMETER</h2><div class="variablelist"><dl><dt><span class="term"><a name="ABORTSHUTDOWNSCRIPT"></a>abort shutdown script (G)</span></dt><dd><p><span class="emphasis"><em>This parameter only exists in the HEAD cvs branch</em></span>
+	each parameter for details.  Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ABORTSHUTDOWNSCRIPT"><i class="parameter"><tt>abort shutdown script</tt></i></a></p></li><li><p><a href="#ADDGROUPSCRIPT"><i class="parameter"><tt>add group script</tt></i></a></p></li><li><p><a href="#ADDMACHINESCRIPT"><i class="parameter"><tt>add machine script</tt></i></a></p></li><li><p><a href="#ADDPRINTERCOMMAND"><i class="parameter"><tt>addprinter command</tt></i></a></p></li><li><p><a href="#ADDSHARECOMMAND"><i class="parameter"><tt>add share command</tt></i></a></p></li><li><p><a href="#ADDUSERSCRIPT"><i class="parameter"><tt>add user script</tt></i></a></p></li><li><p><a href="#ADDUSERTOGROUPSCRIPT"><i class="parameter"><tt>add user to group script</tt></i></a></p></li><li><p><a href="#ALGORITHMICRIDBASE"><i class="parameter"><tt>algorithmic rid base</tt></i></a></p></li><li><p><a href="#ALLOWTRUSTEDDOMAINS"><i class="parameter"><tt>allow trusted domains</tt></i></a></p></li><li><p><a href="#ANNOUNCEAS"><i class="parameter"><tt>announce as</tt></i></a></p></li><li><p><a href="#ANNOUNCEVERSION"><i class="parameter"><tt>announce version</tt></i></a></p></li><li><p><a href="#AUTHMETHODS"><i class="parameter"><tt>auth methods</tt></i></a></p></li><li><p><a href="#AUTOSERVICES"><i class="parameter"><tt>auto services</tt></i></a></p></li><li><p><a href="#BINDINTERFACESONLY"><i class="parameter"><tt>bind interfaces only</tt></i></a></p></li><li><p><a href="#BROWSELIST"><i class="parameter"><tt>browse list</tt></i></a></p></li><li><p><a href="#CHANGENOTIFYTIMEOUT"><i class="parameter"><tt>change notify timeout</tt></i></a></p></li><li><p><a href="#CHANGESHARECOMMAND"><i class="parameter"><tt>change share command</tt></i></a></p></li><li><p><a href="#CLIENTLANMANAUTH"><i class="parameter"><tt>client lanman auth</tt></i></a></p></li><li><p><a href="#CLIENTNTLMV2AUTH"><i class="parameter"><tt>client ntlmv2 auth</tt></i></a></p></li><li><p><a href="#CLIENTPLAINTEXTAUTH"><i class="parameter"><tt>client plaintext auth</tt></i></a></p></li><li><p><a href="#CLIENTSCHANNEL"><i class="parameter"><tt>client schannel</tt></i></a></p></li><li><p><a href="#CLIENTSIGNING"><i class="parameter"><tt>client signing</tt></i></a></p></li><li><p><a href="#CLIENTUSESPNEGO"><i class="parameter"><tt>client use spnego</tt></i></a></p></li><li><p><a href="#CONFIGFILE"><i class="parameter"><tt>config file</tt></i></a></p></li><li><p><a href="#DEADTIME"><i class="parameter"><tt>deadtime</tt></i></a></p></li><li><p><a href="#DEBUGHIRESTIMESTAMP"><i class="parameter"><tt>debug hires timestamp</tt></i></a></p></li><li><p><a href="#DEBUGLEVEL"><i class="parameter"><tt>debuglevel</tt></i></a></p></li><li><p><a href="#DEBUGPID"><i class="parameter"><tt>debug pid</tt></i></a></p></li><li><p><a href="#DEBUGTIMESTAMP"><i class="parameter"><tt>debug timestamp</tt></i></a></p></li><li><p><a href="#DEBUGUID"><i class="parameter"><tt>debug uid</tt></i></a></p></li><li><p><a href="#DEFAULT"><i class="parameter"><tt>default</tt></i></a></p></li><li><p><a href="#DEFAULTSERVICE"><i class="parameter"><tt>default service</tt></i></a></p></li><li><p><a href="#DELETEGROUPSCRIPT"><i class="parameter"><tt>delete group script</tt></i></a></p></li><li><p><a href="#DELETEPRINTERCOMMAND"><i class="parameter"><tt>deleteprinter command</tt></i></a></p></li><li><p><a href="#DELETESHARECOMMAND"><i class="parameter"><tt>delete share command</tt></i></a></p></li><li><p><a href="#DELETEUSERFROMGROUPSCRIPT"><i class="parameter"><tt>delete user from group script</tt></i></a></p></li><li><p><a href="#DELETEUSERSCRIPT"><i class="parameter"><tt>delete user script</tt></i></a></p></li><li><p><a href="#DFREECOMMAND"><i class="parameter"><tt>dfree command</tt></i></a></p></li><li><p><a href="#DISABLENETBIOS"><i class="parameter"><tt>disable netbios</tt></i></a></p></li><li><p><a href="#DISABLESPOOLSS"><i class="parameter"><tt>disable spoolss</tt></i></a></p></li><li><p><a href="#DISPLAYCHARSET"><i class="parameter"><tt>display charset</tt></i></a></p></li><li><p><a href="#DNSPROXY"><i class="parameter"><tt>dns proxy</tt></i></a></p></li><li><p><a href="#DOMAINLOGONS"><i class="parameter"><tt>domain logons</tt></i></a></p></li><li><p><a href="#DOMAINMASTER"><i class="parameter"><tt>domain master</tt></i></a></p></li><li><p><a href="#DOSCHARSET"><i class="parameter"><tt>dos charset</tt></i></a></p></li><li><p><a href="#ENABLERIDALGORITHM"><i class="parameter"><tt>enable rid algorithm</tt></i></a></p></li><li><p><a href="#ENCRYPTPASSWORDS"><i class="parameter"><tt>encrypt passwords</tt></i></a></p></li><li><p><a href="#ENHANCEDBROWSING"><i class="parameter"><tt>enhanced browsing</tt></i></a></p></li><li><p><a href="#ENUMPORTSCOMMAND"><i class="parameter"><tt>enumports command</tt></i></a></p></li><li><p><a href="#GETQUOTACOMMAND"><i class="parameter"><tt>get quota command</tt></i></a></p></li><li><p><a href="#GETWDCACHE"><i class="parameter"><tt>getwd cache</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i class="parameter"><tt>guest account</tt></i></a></p></li><li><p><a href="#HIDELOCALUSERS"><i class="parameter"><tt>hide local users</tt></i></a></p></li><li><p><a href="#HOMEDIRMAP"><i class="parameter"><tt>homedir map</tt></i></a></p></li><li><p><a href="#HOSTMSDFS"><i class="parameter"><tt>host msdfs</tt></i></a></p></li><li><p><a href="#HOSTNAMELOOKUPS"><i class="parameter"><tt>hostname lookups</tt></i></a></p></li><li><p><a href="#HOSTSEQUIV"><i class="parameter"><tt>hosts equiv</tt></i></a></p></li><li><p><a href="#IDMAPBACKEND"><i class="parameter"><tt>idmap backend</tt></i></a></p></li><li><p><a href="#IDMAPGID"><i class="parameter"><tt>idmap gid</tt></i></a></p></li><li><p><a href="#IDMAPUID"><i class="parameter"><tt>idmap uid</tt></i></a></p></li><li><p><a href="#INCLUDE"><i class="parameter"><tt>include</tt></i></a></p></li><li><p><a href="#INTERFACES"><i class="parameter"><tt>interfaces</tt></i></a></p></li><li><p><a href="#KEEPALIVE"><i class="parameter"><tt>keepalive</tt></i></a></p></li><li><p><a href="#KERNELCHANGENOTIFY"><i class="parameter"><tt>kernel change notify</tt></i></a></p></li><li><p><a href="#KERNELOPLOCKS"><i class="parameter"><tt>kernel oplocks</tt></i></a></p></li><li><p><a href="#LANMANAUTH"><i class="parameter"><tt>lanman auth</tt></i></a></p></li><li><p><a href="#LARGEREADWRITE"><i class="parameter"><tt>large readwrite</tt></i></a></p></li><li><p><a href="#LDAPADMINDN"><i class="parameter"><tt>ldap admin dn</tt></i></a></p></li><li><p><a href="#LDAPDELETEDN"><i class="parameter"><tt>ldap delete dn</tt></i></a></p></li><li><p><a href="#LDAPFILTER"><i class="parameter"><tt>ldap filter</tt></i></a></p></li><li><p><a href="#LDAPGROUPSUFFIX"><i class="parameter"><tt>ldap group suffix</tt></i></a></p></li><li><p><a href="#LDAPIDMAPSUFFIX"><i class="parameter"><tt>ldap idmap suffix</tt></i></a></p></li><li><p><a href="#LDAPMACHINESUFFIX"><i class="parameter"><tt>ldap machine suffix</tt></i></a></p></li><li><p><a href="#LDAPPASSWDSYNC"><i class="parameter"><tt>ldap passwd sync</tt></i></a></p></li><li><p><a href="#LDAPPORT"><i class="parameter"><tt>ldap port</tt></i></a></p></li><li><p><a href="#LDAPSERVER"><i class="parameter"><tt>ldap server</tt></i></a></p></li><li><p><a href="#LDAPSSL"><i class="parameter"><tt>ldap ssl</tt></i></a></p></li><li><p><a href="#LDAPSUFFIX"><i class="parameter"><tt>ldap suffix</tt></i></a></p></li><li><p><a href="#LDAPUSERSUFFIX"><i class="parameter"><tt>ldap user suffix</tt></i></a></p></li><li><p><a href="#LMANNOUNCE"><i class="parameter"><tt>lm announce</tt></i></a></p></li><li><p><a href="#LMINTERVAL"><i class="parameter"><tt>lm interval</tt></i></a></p></li><li><p><a href="#LOADPRINTERS"><i class="parameter"><tt>load printers</tt></i></a></p></li><li><p><a href="#LOCALMASTER"><i class="parameter"><tt>local master</tt></i></a></p></li><li><p><a href="#LOCKDIR"><i class="parameter"><tt>lock dir</tt></i></a></p></li><li><p><a href="#LOCKDIRECTORY"><i class="parameter"><tt>lock directory</tt></i></a></p></li><li><p><a href="#LOCKSPINCOUNT"><i class="parameter"><tt>lock spin count</tt></i></a></p></li><li><p><a href="#LOCKSPINTIME"><i class="parameter"><tt>lock spin time</tt></i></a></p></li><li><p><a href="#LOGFILE"><i class="parameter"><tt>log file</tt></i></a></p></li><li><p><a href="#LOGLEVEL"><i class="parameter"><tt>log level</tt></i></a></p></li><li><p><a href="#LOGONDRIVE"><i class="parameter"><tt>logon drive</tt></i></a></p></li><li><p><a href="#LOGONHOME"><i class="parameter"><tt>logon home</tt></i></a></p></li><li><p><a href="#LOGONPATH"><i class="parameter"><tt>logon path</tt></i></a></p></li><li><p><a href="#LOGONSCRIPT"><i class="parameter"><tt>logon script</tt></i></a></p></li><li><p><a href="#LPQCACHETIME"><i class="parameter"><tt>lpq cache time</tt></i></a></p></li><li><p><a href="#MACHINEPASSWORDTIMEOUT"><i class="parameter"><tt>machine password timeout</tt></i></a></p></li><li><p><a href="#MANGLEDSTACK"><i class="parameter"><tt>mangled stack</tt></i></a></p></li><li><p><a href="#MANGLEPREFIX"><i class="parameter"><tt>mangle prefix</tt></i></a></p></li><li><p><a href="#MANGLINGMETHOD"><i class="parameter"><tt>mangling method</tt></i></a></p></li><li><p><a href="#MAPTOGUEST"><i class="parameter"><tt>map to guest</tt></i></a></p></li><li><p><a href="#MAXDISKSIZE"><i class="parameter"><tt>max disk size</tt></i></a></p></li><li><p><a href="#MAXLOGSIZE"><i class="parameter"><tt>max log size</tt></i></a></p></li><li><p><a href="#MAXMUX"><i class="parameter"><tt>max mux</tt></i></a></p></li><li><p><a href="#MAXOPENFILES"><i class="parameter"><tt>max open files</tt></i></a></p></li><li><p><a href="#MAXPROTOCOL"><i class="parameter"><tt>max protocol</tt></i></a></p></li><li><p><a href="#MAXSMBDPROCESSES"><i class="parameter"><tt>max smbd processes</tt></i></a></p></li><li><p><a href="#MAXTTL"><i class="parameter"><tt>max ttl</tt></i></a></p></li><li><p><a href="#MAXWINSTTL"><i class="parameter"><tt>max wins ttl</tt></i></a></p></li><li><p><a href="#MAXXMIT"><i class="parameter"><tt>max xmit</tt></i></a></p></li><li><p><a href="#MESSAGECOMMAND"><i class="parameter"><tt>message command</tt></i></a></p></li><li><p><a href="#MINPASSWDLENGTH"><i class="parameter"><tt>min passwd length</tt></i></a></p></li><li><p><a href="#MINPASSWORDLENGTH"><i class="parameter"><tt>min password length</tt></i></a></p></li><li><p><a href="#MINPROTOCOL"><i class="parameter"><tt>min protocol</tt></i></a></p></li><li><p><a href="#MINWINSTTL"><i class="parameter"><tt>min wins ttl</tt></i></a></p></li><li><p><a href="#NAMECACHETIMEOUT"><i class="parameter"><tt>name cache timeout</tt></i></a></p></li><li><p><a href="#NAMERESOLVEORDER"><i class="parameter"><tt>name resolve order</tt></i></a></p></li><li><p><a href="#NETBIOSALIASES"><i class="parameter"><tt>netbios aliases</tt></i></a></p></li><li><p><a href="#NETBIOSNAME"><i class="parameter"><tt>netbios name</tt></i></a></p></li><li><p><a href="#NETBIOSSCOPE"><i class="parameter"><tt>netbios scope</tt></i></a></p></li><li><p><a href="#NISHOMEDIR"><i class="parameter"><tt>nis homedir</tt></i></a></p></li><li><p><a href="#NTLMAUTH"><i class="parameter"><tt>ntlm auth</tt></i></a></p></li><li><p><a href="#NTPIPESUPPORT"><i class="parameter"><tt>nt pipe support</tt></i></a></p></li><li><p><a href="#NTSTATUSSUPPORT"><i class="parameter"><tt>nt status support</tt></i></a></p></li><li><p><a href="#NULLPASSWORDS"><i class="parameter"><tt>null passwords</tt></i></a></p></li><li><p><a href="#OBEYPAMRESTRICTIONS"><i class="parameter"><tt>obey pam restrictions</tt></i></a></p></li><li><p><a href="#OPLOCKBREAKWAITTIME"><i class="parameter"><tt>oplock break wait time</tt></i></a></p></li><li><p><a href="#OS2DRIVERMAP"><i class="parameter"><tt>os2 driver map</tt></i></a></p></li><li><p><a href="#OSLEVEL"><i class="parameter"><tt>os level</tt></i></a></p></li><li><p><a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i></a></p></li><li><p><a href="#PANICACTION"><i class="parameter"><tt>panic action</tt></i></a></p></li><li><p><a href="#PARANOIDSERVERSECURITY"><i class="parameter"><tt>paranoid server security</tt></i></a></p></li><li><p><a href="#PASSDBBACKEND"><i class="parameter"><tt>passdb backend</tt></i></a></p></li><li><p><a href="#PASSWDCHAT"><i class="parameter"><tt>passwd chat</tt></i></a></p></li><li><p><a href="#PASSWDCHATDEBUG"><i class="parameter"><tt>passwd chat debug</tt></i></a></p></li><li><p><a href="#PASSWDPROGRAM"><i class="parameter"><tt>passwd program</tt></i></a></p></li><li><p><a href="#PASSWORDLEVEL"><i class="parameter"><tt>password level</tt></i></a></p></li><li><p><a href="#PASSWORDSERVER"><i class="parameter"><tt>password server</tt></i></a></p></li><li><p><a href="#PIDDIRECTORY"><i class="parameter"><tt>pid directory</tt></i></a></p></li><li><p><a href="#PREFEREDMASTER"><i class="parameter"><tt>prefered master</tt></i></a></p></li><li><p><a href="#PREFERREDMASTER"><i class="parameter"><tt>preferred master</tt></i></a></p></li><li><p><a href="#PRELOAD"><i class="parameter"><tt>preload</tt></i></a></p></li><li><p><a href="#PRELOADMODULES"><i class="parameter"><tt>preload modules</tt></i></a></p></li><li><p><a href="#PRINTCAP"><i class="parameter"><tt>printcap</tt></i></a></p></li><li><p><a href="#PRIVATEDIR"><i class="parameter"><tt>private dir</tt></i></a></p></li><li><p><a href="#PROTOCOL"><i class="parameter"><tt>protocol</tt></i></a></p></li><li><p><a href="#READBMPX"><i class="parameter"><tt>read bmpx</tt></i></a></p></li><li><p><a href="#READRAW"><i class="parameter"><tt>read raw</tt></i></a></p></li><li><p><a href="#READSIZE"><i class="parameter"><tt>read size</tt></i></a></p></li><li><p><a href="#REALM"><i class="parameter"><tt>realm</tt></i></a></p></li><li><p><a href="#REMOTEANNOUNCE"><i class="parameter"><tt>remote announce</tt></i></a></p></li><li><p><a href="#REMOTEBROWSESYNC"><i class="parameter"><tt>remote browse sync</tt></i></a></p></li><li><p><a href="#RESTRICTANONYMOUS"><i class="parameter"><tt>restrict anonymous</tt></i></a></p></li><li><p><a href="#ROOT"><i class="parameter"><tt>root</tt></i></a></p></li><li><p><a href="#ROOTDIR"><i class="parameter"><tt>root dir</tt></i></a></p></li><li><p><a href="#ROOTDIRECTORY"><i class="parameter"><tt>root directory</tt></i></a></p></li><li><p><a href="#SECURITY"><i class="parameter"><tt>security</tt></i></a></p></li><li><p><a href="#SERVERSCHANNEL"><i class="parameter"><tt>server schannel</tt></i></a></p></li><li><p><a href="#SERVERSIGNING"><i class="parameter"><tt>server signing</tt></i></a></p></li><li><p><a href="#SERVERSTRING"><i class="parameter"><tt>server string</tt></i></a></p></li><li><p><a href="#SETPRIMARYGROUPSCRIPT"><i class="parameter"><tt>set primary group script</tt></i></a></p></li><li><p><a href="#SETQUOTACOMMAND"><i class="parameter"><tt>set quota command</tt></i></a></p></li><li><p><a href="#SHOWADDPRINTERWIZARD"><i class="parameter"><tt>show add printer wizard</tt></i></a></p></li><li><p><a href="#SHUTDOWNSCRIPT"><i class="parameter"><tt>shutdown script</tt></i></a></p></li><li><p><a href="#SMBPASSWDFILE"><i class="parameter"><tt>smb passwd file</tt></i></a></p></li><li><p><a href="#SMBPORTS"><i class="parameter"><tt>smb ports</tt></i></a></p></li><li><p><a href="#SOCKETADDRESS"><i class="parameter"><tt>socket address</tt></i></a></p></li><li><p><a href="#SOCKETOPTIONS"><i class="parameter"><tt>socket options</tt></i></a></p></li><li><p><a href="#SOURCEENVIRONMENT"><i class="parameter"><tt>source environment</tt></i></a></p></li><li><p><a href="#STATCACHE"><i class="parameter"><tt>stat cache</tt></i></a></p></li><li><p><a href="#STRIPDOT"><i class="parameter"><tt>strip dot</tt></i></a></p></li><li><p><a href="#SYSLOG"><i class="parameter"><tt>syslog</tt></i></a></p></li><li><p><a href="#SYSLOGONLY"><i class="parameter"><tt>syslog only</tt></i></a></p></li><li><p><a href="#TEMPLATEHOMEDIR"><i class="parameter"><tt>template homedir</tt></i></a></p></li><li><p><a href="#TEMPLATEPRIMARYGROUP"><i class="parameter"><tt>template primary group</tt></i></a></p></li><li><p><a href="#TEMPLATESHELL"><i class="parameter"><tt>template shell</tt></i></a></p></li><li><p><a href="#TIMEOFFSET"><i class="parameter"><tt>time offset</tt></i></a></p></li><li><p><a href="#TIMESERVER"><i class="parameter"><tt>time server</tt></i></a></p></li><li><p><a href="#TIMESTAMPLOGS"><i class="parameter"><tt>timestamp logs</tt></i></a></p></li><li><p><a href="#UNICODE"><i class="parameter"><tt>unicode</tt></i></a></p></li><li><p><a href="#UNIXCHARSET"><i class="parameter"><tt>unix charset</tt></i></a></p></li><li><p><a href="#UNIXEXTENSIONS"><i class="parameter"><tt>unix extensions</tt></i></a></p></li><li><p><a href="#UNIXPASSWORDSYNC"><i class="parameter"><tt>unix password sync</tt></i></a></p></li><li><p><a href="#UPDATEENCRYPTED"><i class="parameter"><tt>update encrypted</tt></i></a></p></li><li><p><a href="#USEMMAP"><i class="parameter"><tt>use mmap</tt></i></a></p></li><li><p><a href="#USERNAMELEVEL"><i class="parameter"><tt>username level</tt></i></a></p></li><li><p><a href="#USERNAMEMAP"><i class="parameter"><tt>username map</tt></i></a></p></li><li><p><a href="#USESPNEGO"><i class="parameter"><tt>use spnego</tt></i></a></p></li><li><p><a href="#UTMP"><i class="parameter"><tt>utmp</tt></i></a></p></li><li><p><a href="#UTMPDIRECTORY"><i class="parameter"><tt>utmp directory</tt></i></a></p></li><li><p><a href="#WINBINDCACHETIME"><i class="parameter"><tt>winbind cache time</tt></i></a></p></li><li><p><a href="#WINBINDENABLELOCALACCOUNTS"><i class="parameter"><tt>winbind enable local accounts</tt></i></a></p></li><li><p><a href="#WINBINDENUMGROUPS"><i class="parameter"><tt>winbind enum groups</tt></i></a></p></li><li><p><a href="#WINBINDENUMUSERS"><i class="parameter"><tt>winbind enum users</tt></i></a></p></li><li><p><a href="#WINBINDGID"><i class="parameter"><tt>winbind gid</tt></i></a></p></li><li><p><a href="#WINBINDSEPARATOR"><i class="parameter"><tt>winbind separator</tt></i></a></p></li><li><p><a href="#WINBINDTRUSTEDDOMAINSONLY"><i class="parameter"><tt>winbind trusted domains only</tt></i></a></p></li><li><p><a href="#WINBINDUID"><i class="parameter"><tt>winbind uid</tt></i></a></p></li><li><p><a href="#WINBINDUSEDEFAULTDOMAIN"><i class="parameter"><tt>winbind use default domain</tt></i></a></p></li><li><p><a href="#WINSHOOK"><i class="parameter"><tt>wins hook</tt></i></a></p></li><li><p><a href="#WINSPARTNERS"><i class="parameter"><tt>wins partners</tt></i></a></p></li><li><p><a href="#WINSPROXY"><i class="parameter"><tt>wins proxy</tt></i></a></p></li><li><p><a href="#WINSSERVER"><i class="parameter"><tt>wins server</tt></i></a></p></li><li><p><a href="#WINSSUPPORT"><i class="parameter"><tt>wins support</tt></i></a></p></li><li><p><a href="#WORKGROUP"><i class="parameter"><tt>workgroup</tt></i></a></p></li><li><p><a href="#WRITERAW"><i class="parameter"><tt>write raw</tt></i></a></p></li><li><p><a href="#WTMPDIRECTORY"><i class="parameter"><tt>wtmp directory</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>COMPLETE LIST OF SERVICE PARAMETERS</h2><p>Here is a list of all service parameters. See the section on 
+	each parameter for details. Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ACLCOMPATIBILITY"><i class="parameter"><tt>acl compatibility</tt></i></a></p></li><li><p><a href="#ADMINUSERS"><i class="parameter"><tt>admin users</tt></i></a></p></li><li><p><a href="#ALLOWHOSTS"><i class="parameter"><tt>allow hosts</tt></i></a></p></li><li><p><a href="#AVAILABLE"><i class="parameter"><tt>available</tt></i></a></p></li><li><p><a href="#BLOCKINGLOCKS"><i class="parameter"><tt>blocking locks</tt></i></a></p></li><li><p><a href="#BLOCKSIZE"><i class="parameter"><tt>block size</tt></i></a></p></li><li><p><a href="#BROWSABLE"><i class="parameter"><tt>browsable</tt></i></a></p></li><li><p><a href="#BROWSEABLE"><i class="parameter"><tt>browseable</tt></i></a></p></li><li><p><a href="#CASESENSITIVE"><i class="parameter"><tt>case sensitive</tt></i></a></p></li><li><p><a href="#CASESIGNAMES"><i class="parameter"><tt>casesignames</tt></i></a></p></li><li><p><a href="#COMMENT"><i class="parameter"><tt>comment</tt></i></a></p></li><li><p><a href="#COPY"><i class="parameter"><tt>copy</tt></i></a></p></li><li><p><a href="#CREATEMASK"><i class="parameter"><tt>create mask</tt></i></a></p></li><li><p><a href="#CREATEMODE"><i class="parameter"><tt>create mode</tt></i></a></p></li><li><p><a href="#CSCPOLICY"><i class="parameter"><tt>csc policy</tt></i></a></p></li><li><p><a href="#DEFAULTCASE"><i class="parameter"><tt>default case</tt></i></a></p></li><li><p><a href="#DEFAULTDEVMODE"><i class="parameter"><tt>default devmode</tt></i></a></p></li><li><p><a href="#DELETEREADONLY"><i class="parameter"><tt>delete readonly</tt></i></a></p></li><li><p><a href="#DELETEVETOFILES"><i class="parameter"><tt>delete veto files</tt></i></a></p></li><li><p><a href="#DENYHOSTS"><i class="parameter"><tt>deny hosts</tt></i></a></p></li><li><p><a href="#DIRECTORY"><i class="parameter"><tt>directory</tt></i></a></p></li><li><p><a href="#DIRECTORYMASK"><i class="parameter"><tt>directory mask</tt></i></a></p></li><li><p><a href="#DIRECTORYMODE"><i class="parameter"><tt>directory mode</tt></i></a></p></li><li><p><a href="#DIRECTORYSECURITYMASK"><i class="parameter"><tt>directory security mask</tt></i></a></p></li><li><p><a href="#DONTDESCEND"><i class="parameter"><tt>dont descend</tt></i></a></p></li><li><p><a href="#DOSFILEMODE"><i class="parameter"><tt>dos filemode</tt></i></a></p></li><li><p><a href="#DOSFILETIMERESOLUTION"><i class="parameter"><tt>dos filetime resolution</tt></i></a></p></li><li><p><a href="#DOSFILETIMES"><i class="parameter"><tt>dos filetimes</tt></i></a></p></li><li><p><a href="#EXEC"><i class="parameter"><tt>exec</tt></i></a></p></li><li><p><a href="#FAKEDIRECTORYCREATETIMES"><i class="parameter"><tt>fake directory create times</tt></i></a></p></li><li><p><a href="#FAKEOPLOCKS"><i class="parameter"><tt>fake oplocks</tt></i></a></p></li><li><p><a href="#FOLLOWSYMLINKS"><i class="parameter"><tt>follow symlinks</tt></i></a></p></li><li><p><a href="#FORCECREATEMODE"><i class="parameter"><tt>force create mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYMODE"><i class="parameter"><tt>force directory mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYSECURITYMODE"><i class="parameter"><tt>force directory security mode</tt></i></a></p></li><li><p><a href="#FORCEGROUP"><i class="parameter"><tt>force group</tt></i></a></p></li><li><p><a href="#FORCESECURITYMODE"><i class="parameter"><tt>force security mode</tt></i></a></p></li><li><p><a href="#FORCEUSER"><i class="parameter"><tt>force user</tt></i></a></p></li><li><p><a href="#FSTYPE"><i class="parameter"><tt>fstype</tt></i></a></p></li><li><p><a href="#GROUP"><i class="parameter"><tt>group</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i class="parameter"><tt>guest account</tt></i></a></p></li><li><p><a href="#GUESTOK"><i class="parameter"><tt>guest ok</tt></i></a></p></li><li><p><a href="#GUESTONLY"><i class="parameter"><tt>guest only</tt></i></a></p></li><li><p><a href="#HIDEDOTFILES"><i class="parameter"><tt>hide dot files</tt></i></a></p></li><li><p><a href="#HIDEFILES"><i class="parameter"><tt>hide files</tt></i></a></p></li><li><p><a href="#HIDESPECIALFILES"><i class="parameter"><tt>hide special files</tt></i></a></p></li><li><p><a href="#HIDEUNREADABLE"><i class="parameter"><tt>hide unreadable</tt></i></a></p></li><li><p><a href="#HIDEUNWRITEABLEFILES"><i class="parameter"><tt>hide unwriteable files</tt></i></a></p></li><li><p><a href="#HOSTSALLOW"><i class="parameter"><tt>hosts allow</tt></i></a></p></li><li><p><a href="#HOSTSDENY"><i class="parameter"><tt>hosts deny</tt></i></a></p></li><li><p><a href="#INHERITACLS"><i class="parameter"><tt>inherit acls</tt></i></a></p></li><li><p><a href="#INHERITPERMISSIONS"><i class="parameter"><tt>inherit permissions</tt></i></a></p></li><li><p><a href="#INVALIDUSERS"><i class="parameter"><tt>invalid users</tt></i></a></p></li><li><p><a href="#LEVEL2OPLOCKS"><i class="parameter"><tt>level2 oplocks</tt></i></a></p></li><li><p><a href="#LOCKING"><i class="parameter"><tt>locking</tt></i></a></p></li><li><p><a href="#LPPAUSECOMMAND"><i class="parameter"><tt>lppause command</tt></i></a></p></li><li><p><a href="#LPQCOMMAND"><i class="parameter"><tt>lpq command</tt></i></a></p></li><li><p><a href="#LPRESUMECOMMAND"><i class="parameter"><tt>lpresume command</tt></i></a></p></li><li><p><a href="#LPRMCOMMAND"><i class="parameter"><tt>lprm command</tt></i></a></p></li><li><p><a href="#MAGICOUTPUT"><i class="parameter"><tt>magic output</tt></i></a></p></li><li><p><a href="#MAGICSCRIPT"><i class="parameter"><tt>magic script</tt></i></a></p></li><li><p><a href="#MANGLECASE"><i class="parameter"><tt>mangle case</tt></i></a></p></li><li><p><a href="#MANGLEDMAP"><i class="parameter"><tt>mangled map</tt></i></a></p></li><li><p><a href="#MANGLEDNAMES"><i class="parameter"><tt>mangled names</tt></i></a></p></li><li><p><a href="#MANGLINGCHAR"><i class="parameter"><tt>mangling char</tt></i></a></p></li><li><p><a href="#MAPACLINHERIT"><i class="parameter"><tt>map acl inherit</tt></i></a></p></li><li><p><a href="#MAPARCHIVE"><i class="parameter"><tt>map archive</tt></i></a></p></li><li><p><a href="#MAPHIDDEN"><i class="parameter"><tt>map hidden</tt></i></a></p></li><li><p><a href="#MAPSYSTEM"><i class="parameter"><tt>map system</tt></i></a></p></li><li><p><a href="#MAXCONNECTIONS"><i class="parameter"><tt>max connections</tt></i></a></p></li><li><p><a href="#MAXPRINTJOBS"><i class="parameter"><tt>max print jobs</tt></i></a></p></li><li><p><a href="#MAXREPORTEDPRINTJOBS"><i class="parameter"><tt>max reported print jobs</tt></i></a></p></li><li><p><a href="#MINPRINTSPACE"><i class="parameter"><tt>min print space</tt></i></a></p></li><li><p><a href="#MSDFSPROXY"><i class="parameter"><tt>msdfs proxy</tt></i></a></p></li><li><p><a href="#MSDFSROOT"><i class="parameter"><tt>msdfs root</tt></i></a></p></li><li><p><a href="#NTACLSUPPORT"><i class="parameter"><tt>nt acl support</tt></i></a></p></li><li><p><a href="#ONLYGUEST"><i class="parameter"><tt>only guest</tt></i></a></p></li><li><p><a href="#ONLYUSER"><i class="parameter"><tt>only user</tt></i></a></p></li><li><p><a href="#OPLOCKCONTENTIONLIMIT"><i class="parameter"><tt>oplock contention limit</tt></i></a></p></li><li><p><a href="#OPLOCKS"><i class="parameter"><tt>oplocks</tt></i></a></p></li><li><p><a href="#PATH"><i class="parameter"><tt>path</tt></i></a></p></li><li><p><a href="#POSIXLOCKING"><i class="parameter"><tt>posix locking</tt></i></a></p></li><li><p><a href="#POSTEXEC"><i class="parameter"><tt>postexec</tt></i></a></p></li><li><p><a href="#PREEXEC"><i class="parameter"><tt>preexec</tt></i></a></p></li><li><p><a href="#PREEXECCLOSE"><i class="parameter"><tt>preexec close</tt></i></a></p></li><li><p><a href="#PRESERVECASE"><i class="parameter"><tt>preserve case</tt></i></a></p></li><li><p><a href="#PRINTABLE"><i class="parameter"><tt>printable</tt></i></a></p></li><li><p><a href="#PRINTCAPNAME"><i class="parameter"><tt>printcap name</tt></i></a></p></li><li><p><a href="#PRINTCOMMAND"><i class="parameter"><tt>print command</tt></i></a></p></li><li><p><a href="#PRINTER"><i class="parameter"><tt>printer</tt></i></a></p></li><li><p><a href="#PRINTERADMIN"><i class="parameter"><tt>printer admin</tt></i></a></p></li><li><p><a href="#PRINTERNAME"><i class="parameter"><tt>printer name</tt></i></a></p></li><li><p><a href="#PRINTING"><i class="parameter"><tt>printing</tt></i></a></p></li><li><p><a href="#PRINTOK"><i class="parameter"><tt>print ok</tt></i></a></p></li><li><p><a href="#PROFILEACLS"><i class="parameter"><tt>profile acls</tt></i></a></p></li><li><p><a href="#PUBLIC"><i class="parameter"><tt>public</tt></i></a></p></li><li><p><a href="#QUEUEPAUSECOMMAND"><i class="parameter"><tt>queuepause command</tt></i></a></p></li><li><p><a href="#QUEUERESUMECOMMAND"><i class="parameter"><tt>queueresume command</tt></i></a></p></li><li><p><a href="#READLIST"><i class="parameter"><tt>read list</tt></i></a></p></li><li><p><a href="#READONLY"><i class="parameter"><tt>read only</tt></i></a></p></li><li><p><a href="#ROOTPOSTEXEC"><i class="parameter"><tt>root postexec</tt></i></a></p></li><li><p><a href="#ROOTPREEXEC"><i class="parameter"><tt>root preexec</tt></i></a></p></li><li><p><a href="#ROOTPREEXECCLOSE"><i class="parameter"><tt>root preexec close</tt></i></a></p></li><li><p><a href="#SECURITYMASK"><i class="parameter"><tt>security mask</tt></i></a></p></li><li><p><a href="#SETDIRECTORY"><i class="parameter"><tt>set directory</tt></i></a></p></li><li><p><a href="#SHAREMODES"><i class="parameter"><tt>share modes</tt></i></a></p></li><li><p><a href="#SHORTPRESERVECASE"><i class="parameter"><tt>short preserve case</tt></i></a></p></li><li><p><a href="#STRICTALLOCATE"><i class="parameter"><tt>strict allocate</tt></i></a></p></li><li><p><a href="#STRICTLOCKING"><i class="parameter"><tt>strict locking</tt></i></a></p></li><li><p><a href="#STRICTSYNC"><i class="parameter"><tt>strict sync</tt></i></a></p></li><li><p><a href="#SYNCALWAYS"><i class="parameter"><tt>sync always</tt></i></a></p></li><li><p><a href="#USECLIENTDRIVER"><i class="parameter"><tt>use client driver</tt></i></a></p></li><li><p><a href="#USER"><i class="parameter"><tt>user</tt></i></a></p></li><li><p><a href="#USERNAME"><i class="parameter"><tt>username</tt></i></a></p></li><li><p><a href="#USERS"><i class="parameter"><tt>users</tt></i></a></p></li><li><p><a href="#USESENDFILE"><i class="parameter"><tt>use sendfile</tt></i></a></p></li><li><p><a href="#-VALID"><i class="parameter"><tt>-valid</tt></i></a></p></li><li><p><a href="#VALIDUSERS"><i class="parameter"><tt>valid users</tt></i></a></p></li><li><p><a href="#VETOFILES"><i class="parameter"><tt>veto files</tt></i></a></p></li><li><p><a href="#VETOOPLOCKFILES"><i class="parameter"><tt>veto oplock files</tt></i></a></p></li><li><p><a href="#VFSOBJECT"><i class="parameter"><tt>vfs object</tt></i></a></p></li><li><p><a href="#VFSOBJECTS"><i class="parameter"><tt>vfs objects</tt></i></a></p></li><li><p><a href="#VOLUME"><i class="parameter"><tt>volume</tt></i></a></p></li><li><p><a href="#WIDELINKS"><i class="parameter"><tt>wide links</tt></i></a></p></li><li><p><a href="#WRITABLE"><i class="parameter"><tt>writable</tt></i></a></p></li><li><p><a href="#WRITEABLE"><i class="parameter"><tt>writeable</tt></i></a></p></li><li><p><a href="#WRITECACHESIZE"><i class="parameter"><tt>write cache size</tt></i></a></p></li><li><p><a href="#WRITELIST"><i class="parameter"><tt>write list</tt></i></a></p></li><li><p><a href="#WRITEOK"><i class="parameter"><tt>write ok</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXPLANATION OF EACH PARAMETER</h2><div class="variablelist"><dl><dt><span class="term"><a name="ABORTSHUTDOWNSCRIPT"></a>abort shutdown script (G)</span></dt><dd><p><span class="emphasis"><em>This parameter only exists in the HEAD cvs branch</em></span>
 	This a full path name to a script called by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> that
 	should stop a shutdown procedure issued by the <a href="#SHUTDOWNSCRIPT">
-	<i class="parameter"><tt>shutdown script</tt></i></a>.</p><p>This command will be run as user.</p><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b class="command">abort shutdown script = /sbin/shutdown -c</b></p></dd><dt><span class="term"><a name="ADDGROUPSCRIPT"></a>add group script (G)</span></dt><dd><p>This is the full pathname to a script that will be run
+	<i class="parameter"><tt>shutdown script</tt></i></a>.</p><p>This command will be run as user.</p><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b class="command">abort shutdown script = /sbin/shutdown -c</b></p></dd><dt><span class="term"><a name="ACLCOMPATIBILITY"></a>acl compatibility (S)</span></dt><dd><p>This parameter specifies what OS ACL semantics should 
+	be compatible with. Possible values are <span class="emphasis"><em>winnt</em></span> for Windows NT 4, 
+	<span class="emphasis"><em>win2k</em></span> for Windows 2000 and above and <span class="emphasis"><em>auto</em></span>.
+	If you specify <span class="emphasis"><em>auto</em></span>, the value for this parameter 
+	will be based upon the version of the client. There should 
+	be no reason to change this parameter from the default.</p><p>Default: <b class="command">acl compatibility = Auto</b></p><p>Example: <b class="command">acl compatibility = win2k</b></p></dd><dt><span class="term"><a name="ADDGROUPSCRIPT"></a>add group script (G)</span></dt><dd><p>This is the full pathname to a script that will be run
 	<span class="emphasis"><em>AS ROOT</em></span> by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>
 	when a new group is requested. It will expand any <i class="parameter"><tt>%g</tt></i> to the group name passed. This
 	script is only useful for installations using the Windows NT
@@ -264,7 +269,7 @@ alias|alias|alias|alias...
 	machines -c Machine -d /dev/null -s /bin/false %u</b></p></dd><dt><span class="term"><a name="ADDPRINTERCOMMAND"></a>addprinter command (G)</span></dt><dd><p>With the introduction of MS-RPC based printing
     support for Windows NT/2000 clients in Samba 2.2, The MS Add
     Printer Wizard (APW) icon is now also available in the 
-    &quot;Printers...&quot; folder displayed a share listing.  The APW
+    "Printers..." folder displayed a share listing.  The APW
     allows for printers to be add remotely to a Samba or Windows 
     NT/2000 print server.</p><p>For a Samba host this means that the printer must be 
     physically added to the underlying printing system.  The <i class="parameter"><tt>add 
@@ -275,15 +280,15 @@ alias|alias|alias|alias...
     shared by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>.</p><p>The <i class="parameter"><tt>addprinter command</tt></i> is
     automatically invoked with the following parameter (in 
     order):</p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>printer name</tt></i></p></li><li><p><i class="parameter"><tt>share name</tt></i></p></li><li><p><i class="parameter"><tt>port name</tt></i></p></li><li><p><i class="parameter"><tt>driver name</tt></i></p></li><li><p><i class="parameter"><tt>location</tt></i></p></li><li><p><i class="parameter"><tt>Windows 9x driver location</tt></i></p></li></ul></div><p>All parameters are filled in from the PRINTER_INFO_2 structure sent 
-    by the Windows NT/2000 client with one exception.  The &quot;Windows 9x
-    driver location&quot; parameter is included for backwards compatibility
+    by the Windows NT/2000 client with one exception.  The "Windows 9x
+    driver location" parameter is included for backwards compatibility
     only.  The remaining fields in the structure are generated from answers
     to the APW questions.</p><p>Once the <i class="parameter"><tt>addprinter command</tt></i> has 
     been executed, <b class="command">smbd</b> will reparse the <tt class="filename">
     smb.conf</tt> to determine if the share defined by the APW
     exists.  If the sharename is still invalid, then <b class="command">smbd
     </b> will return an ACCESS_DENIED error to the client.</p><p>
-    The &quot;add printer command&quot; program can output a single line of text,
+    The "add printer command" program can output a single line of text,
     which Samba will set as the port the new printer is connected to. 
     If this line isn't output, Samba won't reload its printer shares.
     </p><p>See also <a href="#DELETEPRINTERCOMMAND"><i class="parameter"><tt>
@@ -378,8 +383,8 @@ alias|alias|alias|alias...
     Samba server even if they do not have an account in DOMA.  This 
     can make implementing a security boundary difficult.</p><p>Default: <b class="command">allow trusted domains = yes</b></p></dd><dt><span class="term"><a name="ANNOUNCEAS"></a>announce as (G)</span></dt><dd><p>This specifies what type of server <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> will announce itself as, to a network neighborhood browse 
     list. By default this is set to Windows NT. The valid options 
-    are : &quot;NT Server&quot; (which can also be written as &quot;NT&quot;), 
-    &quot;NT Workstation&quot;, &quot;Win95&quot; or &quot;WfW&quot; meaning Windows NT Server, 
+    are : "NT Server" (which can also be written as "NT"), 
+    "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, 
     Windows NT Workstation, Windows 95 and Windows for Workgroups 
     respectively. Do not change this parameter unless you have a 
     specific need to stop Samba appearing as an NT server as this 
@@ -402,7 +407,7 @@ alias|alias|alias|alias...
     method of authentication for remote domain users; deprecated in favour of winbind method), 
     <tt class="constant">trustdomain</tt> (authenticate trusted users by contacting the 
     remote DC directly from smbd; deprecated in favour of winbind method).</p><p>Default: <b class="command">auth methods = &lt;empty string&gt;</b></p><p>Example: <b class="command">auth methods = guest sam winbind</b></p></dd><dt><span class="term"><a name="AUTOSERVICES"></a>auto services (G)</span></dt><dd><p>This is a synonym for the <a href="#PRELOAD">
-	<i class="parameter"><tt>preload</tt></i></a>.</p></dd><dt><span class="term"><a name="AVAILABLE"></a>available (S)</span></dt><dd><p>This parameter lets you &quot;turn off&quot; a service. If 
+	<i class="parameter"><tt>preload</tt></i></a>.</p></dd><dt><span class="term"><a name="AVAILABLE"></a>available (S)</span></dt><dd><p>This parameter lets you "turn off" a service. If 
 	<i class="parameter"><tt>available = no</tt></i>, then <span class="emphasis"><em>ALL</em></span> 
 	attempts to connect to the service will fail. Such failures are 
 	logged.</p><p>Default: <b class="command">available = yes</b></p></dd><dt><span class="term"><a name="BINDINTERFACESONLY"></a>bind interfaces only (G)</span></dt><dd><p>This global parameter allows the Samba admin 
@@ -410,7 +415,7 @@ alias|alias|alias|alias...
         affects file service <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and name service <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> in a slightly different ways.</p><p>For name service it causes <b class="command">nmbd</b> to bind 
 	to ports 137 and 138 on the interfaces listed in 
         the <a href="#INTERFACES">interfaces</a> parameter. <b class="command">nmbd</b> also 
-        binds to the &quot;all addresses&quot; interface (0.0.0.0) 
+        binds to the "all addresses" interface (0.0.0.0) 
 	on ports 137 and 138 for the purposes of reading broadcast messages. 
 	If this option is not set then <b class="command">nmbd</b> will service 
 	name requests on all of these sockets. If <i class="parameter"><tt>bind interfaces
@@ -447,7 +452,7 @@ alias|alias|alias|alias...
 	<span class="emphasis"><em>127.0.0.1</em></span> to determine if they are running.  
 	Not adding <span class="emphasis"><em>127.0.0.1</em></span>  will cause <b class="command">
 	smbd</b> and <b class="command">nmbd</b> to always show
-	&quot;not running&quot; even if they really are.  This can prevent <b class="command">
+	"not running" even if they really are.  This can prevent <b class="command">
 	swat</b> from starting/stopping/restarting <b class="command">smbd</b>
 	and <b class="command">nmbd</b>.</p><p>Default: <b class="command">bind interfaces only = no</b></p></dd><dt><span class="term"><a name="BLOCKINGLOCKS"></a>blocking locks (S)</span></dt><dd><p>This parameter controls the behavior 
 	of <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when given a request by a client 
@@ -474,7 +479,7 @@ alias|alias|alias|alias...
 	a client doing a <b class="command">NetServerEnum</b> call. Normally 
 	set to <tt class="constant">yes</tt>. You should never need to change 
 	this.</p><p>Default: <b class="command">browse list = yes</b></p></dd><dt><span class="term"><a name="CASESENSITIVE"></a>case sensitive (S)</span></dt><dd><p>See the discussion in the section <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a>.</p><p>Default: <b class="command">case sensitive = no</b></p></dd><dt><span class="term"><a name="CASESIGNAMES"></a>casesignames (S)</span></dt><dd><p>Synonym for <a href="#CASESENSITIVE">case sensitive</a>.</p></dd><dt><span class="term"><a name="CHANGENOTIFYTIMEOUT"></a>change notify timeout (G)</span></dt><dd><p>This SMB allows a client to tell a server to 
-    &quot;watch&quot; a particular directory for any changes and only reply to
+    "watch" a particular directory for any changes and only reply to
     the SMB request when a change has occurred. Such constant scanning of
     a directory is expensive under UNIX, hence an <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> daemon only performs such a scan 
     on each requested directory once every <i class="parameter"><tt>change notify 
@@ -499,7 +504,7 @@ alias|alias|alias|alias...
 			with the new share.
 			</p></li></ul></div><p>
 	This parameter is only used modify existing file shares definitions.  To modify 
-	printer shares, use the &quot;Printers...&quot; folder as seen when browsing the Samba host.
+	printer shares, use the "Printers..." folder as seen when browsing the Samba host.
 	</p><p>
 	See also <a href="#ADDSHARECOMMAND"><i class="parameter"><tt>add share
 	command</tt></i></a>, <a href="#DELETESHARECOMMAND"><i class="parameter"><tt>delete 
@@ -522,7 +527,21 @@ alias|alias|alias|alias...
     NTLMv2.  </p><p>If disabled, an NTLM response (and possibly a LANMAN response)
     will be sent by the client, depending on the value of <b class="command">client lanman auth</b>.  </p><p>Note that some sites (particularly
     those following 'best practice' security polices) only allow NTLMv2
-    responses, and not the weaker LM or NTLM.</p><p>Default : <b class="command">client ntlmv2 auth = no</b></p></dd><dt><span class="term"><a name="CLIENTUSESPNEGO"></a>client use spnego (G)</span></dt><dd><p> This variable controls controls whether samba clients will try 
+    responses, and not the weaker LM or NTLM.</p><p>Default : <b class="command">client ntlmv2 auth = no</b></p></dd><dt><span class="term"><a name="CLIENTPLAINTEXTAUTH"></a>client plaintext auth (G)</span></dt><dd><p>Specifies whether a client should send a plaintext 
+	password if the server does not support encrypted passwords.</p><p>Default: <b class="command">client plaintext auth = yes</b></p></dd><dt><span class="term"><a name="CLIENTSCHANNEL"></a>client schannel (G)</span></dt><dd><p>This controls whether the client offers or even
+    demands the use of the netlogon schannel.
+    <i class="parameter"><tt>client schannel = no</tt></i> does not
+    offer the schannel, <i class="parameter"><tt>server schannel =
+    auto</tt></i> offers the schannel but does not
+    enforce it, and <i class="parameter"><tt>server schannel =
+    yes</tt></i> denies access if the server is not
+    able to speak netlogon schannel. </p><p>Default: <b class="command">client schannel = auto</b></p><p>Example: <b class="command">client schannel = yes</b></p></dd><dt><span class="term"><a name="CLIENTSIGNING"></a>client signing (G)</span></dt><dd><p>This controls whether the client offers or requires
+    the server it talks to to use SMB signing. Possible values 
+    are <span class="emphasis"><em>auto</em></span>, <span class="emphasis"><em>mandatory</em></span> 
+    and <span class="emphasis"><em>disabled</em></span>. 
+    </p><p>When set to auto, SMB signing is offered, but not enforced. 
+    When set to mandatory, SMB signing is required and if set 
+    to disabled, SMB signing is not offered either.</p><p>Default: <b class="command">client signing = auto</b></p></dd><dt><span class="term"><a name="CLIENTUSESPNEGO"></a>client use spnego (G)</span></dt><dd><p> This variable controls controls whether samba clients will try 
     to use Simple and Protected NEGOciation (as specified by rfc2478) with 
     WindowsXP and Windows2000 servers to agree upon an authentication mechanism. 
 	SPNEGO client support for SMB Signing is currently broken, so 
@@ -541,7 +560,7 @@ alias|alias|alias|alias...
 	the new config file.</p><p>This option takes the usual substitutions, which can 
 	be very useful.</p><p>If the config file doesn't exist then it won't be loaded 
 	(allowing you to special case the config files of just a few 
-	clients).</p><p>Example: <b class="command">config file = /usr/local/samba/lib/smb.conf.%m</b></p></dd><dt><span class="term"><a name="COPY"></a>copy (S)</span></dt><dd><p>This parameter allows you to &quot;clone&quot; service 
+	clients).</p><p>Example: <b class="command">config file = /usr/local/samba/lib/smb.conf.%m</b></p></dd><dt><span class="term"><a name="COPY"></a>copy (S)</span></dt><dd><p>This parameter allows you to "clone" service 
 	entries. The specified service is simply duplicated under the 
 	current service's name. Any parameters specified in the current 
 	section will override those in the section being copied.</p><p>This feature lets you set up a 'template' service and 
@@ -603,7 +622,8 @@ alias|alias|alias|alias...
     current euid, egid, uid and gid to the timestamp message headers 
     in the log file if turned on.</p><p>Note that the parameter <a href="#DEBUGTIMESTAMP"><i class="parameter"><tt>
     debug timestamp</tt></i></a> must be on for this to have an 
-    effect.</p><p>Default: <b class="command">debug uid = no</b></p></dd><dt><span class="term"><a name="DEFAULTCASE"></a>default case (S)</span></dt><dd><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">
+    effect.</p><p>Default: <b class="command">debug uid = no</b></p></dd><dt><span class="term"><a name="DEFAULT"></a>default (G)</span></dt><dd><p>A synonym for <a href="#DEFAULTSERVICE"><i class="parameter"><tt>
+				default service</tt></i></a>.</p></dd><dt><span class="term"><a name="DEFAULTCASE"></a>default case (S)</span></dt><dd><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">
 	NAME MANGLING</a>. Also note the <a href="#SHORTPRESERVECASE">
 	<i class="parameter"><tt>short preserve case</tt></i></a> parameter.</p><p>Default: <b class="command">default case = lower</b></p></dd><dt><span class="term"><a name="DEFAULTDEVMODE"></a>default devmode (S)</span></dt><dd><p>This parameter is only applicable to <a href="#PRINTOK">printable</a> services.
     When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
@@ -636,16 +656,15 @@ alias|alias|alias|alias...
 	<i class="parameter"><tt>read-only</tt></i></a> service.</p><p>Also note that the apparent service name will be changed 
 	to equal that of the requested service, this is very useful as it 
 	allows you to use macros like <i class="parameter"><tt>%S</tt></i> to make 
-	a wildcard service.</p><p>Note also that any &quot;_&quot; characters in the name of the service 
-	used in the default service will get mapped to a &quot;/&quot;. This allows for
+	a wildcard service.</p><p>Note also that any "_" characters in the name of the service 
+	used in the default service will get mapped to a "/". This allows for
 	interesting things.</p><p>Example:</p><pre class="programlisting">
 [global]
 	default service = pub
         
 [pub]
 	path = /%S
-</pre></dd><dt><span class="term"><a name="DEFAULT"></a>default (G)</span></dt><dd><p>A synonym for <a href="#DEFAULTSERVICE"><i class="parameter"><tt>
-				default service</tt></i></a>.</p></dd><dt><span class="term"><a name="DELETEGROUPSCRIPT"></a>delete group script (G)</span></dt><dd><p>This is the full pathname to a script that will 
+</pre></dd><dt><span class="term"><a name="DELETEGROUPSCRIPT"></a>delete group script (G)</span></dt><dd><p>This is the full pathname to a script that will 
 	be run <span class="emphasis"><em>AS ROOT</em></span> <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> when a group is requested to be deleted. 
 	It will expand any <i class="parameter"><tt>%g</tt></i> to the group name passed.  
 	This script is only useful for installations using the Windows NT domain administration tools.
@@ -659,7 +678,7 @@ alias|alias|alias|alias...
     from the print system and from <tt class="filename">smb.conf</tt>.
     </p><p>The <i class="parameter"><tt>deleteprinter command</tt></i> is 
     automatically called with only one parameter: <i class="parameter"><tt>
-    &quot;printer name&quot;</tt></i>.</p><p>Once the <i class="parameter"><tt>deleteprinter command</tt></i> has 
+    "printer name"</tt></i>.</p><p>Once the <i class="parameter"><tt>deleteprinter command</tt></i> has 
     been executed, <b class="command">smbd</b> will reparse the <tt class="filename">
     smb.conf</tt> to associated printer no longer exists.  
     If the sharename is still valid, then <b class="command">smbd
@@ -721,8 +740,8 @@ alias|alias|alias|alias...
 	should only be used on systems where a problem occurs with the
 	internal disk space calculations. This has been known to happen
 	with Ultrix, but may occur with other operating systems. The
-	symptom that was seen was an error of &quot;Abort Retry
-	Ignore&quot; at the end of each directory listing.</p><p>This setting allows the replacement of the internal routines to
+	symptom that was seen was an error of "Abort Retry
+	Ignore" at the end of each directory listing.</p><p>This setting allows the replacement of the internal routines to
 	calculate the total disk space and amount available with an external
 	routine. The example below gives a possible script that might fulfill
 	this function.</p><p>The external program will be passed a single parameter indicating 
@@ -736,11 +755,11 @@ alias|alias|alias|alias...
 	determining the disk capacity and remaining space will be used.
 	</em></span></p><p>Example: <b class="command">dfree command = /usr/local/samba/bin/dfree</b></p><p>Where the script dfree (which must be made executable) could be:</p><pre class="programlisting"> 
 #!/bin/sh
-df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
+df $1 | tail -1 | awk '{print $2" "$4}'
 </pre><p>or perhaps (on Sys V based systems):</p><pre class="programlisting"> 
 #!/bin/sh
-/usr/bin/df -k $1 | tail -1 | awk '{print $3&quot; &quot;$5}'
-</pre><p>Note that you may have to replace the command names with full path names on some systems.</p></dd><dt><span class="term"><a name="DIRECTORYMASK"></a>directory mask (S)</span></dt><dd><p>This parameter is the octal modes which are 
+/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+</pre><p>Note that you may have to replace the command names with full path names on some systems.</p></dd><dt><span class="term"><a name="DIRECTORY"></a>directory (S)</span></dt><dd><p>Synonym for <a href="#PATH"><i class="parameter"><tt>path</tt></i></a>.</p></dd><dt><span class="term"><a name="DIRECTORYMASK"></a>directory mask (S)</span></dt><dd><p>This parameter is the octal modes which are 
     used when converting DOS modes to UNIX modes when creating UNIX 
     directories.</p><p>When a directory is created, the necessary permissions are 
     calculated according to the mapping from DOS modes to UNIX permissions, 
@@ -774,13 +793,13 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     meaning a user is allowed to modify all the user/group/world
     permissions on a directory.</p><p><span class="emphasis"><em>Note</em></span> that users who can access the 
     Samba server through other means can easily bypass this restriction, 
-    so it is primarily useful for standalone &quot;appliance&quot; systems.  
+    so it is primarily useful for standalone "appliance" systems.  
     Administrators of most normal systems will probably want to leave
     it as the default of <tt class="constant">0777</tt>.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE"><i class="parameter"><tt>
     force directory security mode</tt></i></a>, <a href="#SECURITYMASK">
     <i class="parameter"><tt>security mask</tt></i></a>, 
     <a href="#FORCESECURITYMODE"><i class="parameter"><tt>force security mode
-    </tt></i></a> parameters.</p><p>Default: <b class="command">directory security mask = 0777</b></p><p>Example: <b class="command">directory security mask = 0700</b></p></dd><dt><span class="term"><a name="DIRECTORY"></a>directory (S)</span></dt><dd><p>Synonym for <a href="#PATH"><i class="parameter"><tt>path</tt></i></a>.</p></dd><dt><span class="term"><a name="DISABLENETBIOS"></a>disable netbios (G)</span></dt><dd><p>Enabling this parameter will disable netbios support
+    </tt></i></a> parameters.</p><p>Default: <b class="command">directory security mask = 0777</b></p><p>Example: <b class="command">directory security mask = 0700</b></p></dd><dt><span class="term"><a name="DISABLENETBIOS"></a>disable netbios (G)</span></dt><dd><p>Enabling this parameter will disable netbios support
     in Samba. Netbios is the only available form of browsing in 
     all windows versions except for 2000 and XP. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Note that clients that only support netbios won't be able to 
     see your samba server when netbios support is disabled.
@@ -838,7 +857,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	of interest to clients or are infinitely deep (recursive). This 
 	parameter allows you to specify a comma-delimited list of directories 
 	that the server should always show as empty.</p><p>Note that Samba can be very fussy about the exact format 
-	of the &quot;dont descend&quot; entries. For example you may need <tt class="filename">
+	of the "dont descend" entries. For example you may need <tt class="filename">
 	./proc</tt> instead of just <tt class="filename">/proc</tt>. 
 	Experimentation is the best policy :-)  </p><p>Default: <span class="emphasis"><em>none (i.e., all directories are OK 
 	to descend)</em></span></p><p>Example: <b class="command">dont descend = /proc,/dev</b></p></dd><dt><span class="term"><a name="DOSCHARSET"></a>dos charset (G)</span></dt><dd><p>DOS SMB clients assume the server has 
@@ -886,7 +905,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     will be negotiated with the client. Note that Windows NT 4.0 SP3 and 
     above and also Windows 98 will by default expect encrypted passwords 
     unless a registry entry is changed. To use encrypted passwords in 
-	Samba see the chapter &quot;User Database&quot; in the Samba HOWTO Collection. </p><p>In order for encrypted passwords to work correctly
+	Samba see the chapter "User Database" in the Samba HOWTO Collection. </p><p>In order for encrypted passwords to work correctly
     <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> must either 
     have access to a local <a href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a> file (see the <a href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a> program for information on how to set up 
     and maintain this file), or set the <a href="#SECURITY">security = [server|domain|ads]</a> parameter which 
@@ -902,16 +921,16 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	workgroups not disappearing from browse lists. Due to the restrictions
 	of the browse protocols these enhancements can cause a empty workgroup
 	to stay around forever which can be annoying.</p><p>In general you should leave this option enabled as it makes
-	cross-subnet browse propagation much more reliable.</p><p>Default: <b class="command">enhanced browsing = yes</b></p></dd><dt><span class="term"><a name="ENUMPORTSCOMMAND"></a>enumports command (G)</span></dt><dd><p>The concept of a &quot;port&quot; is fairly foreign
+	cross-subnet browse propagation much more reliable.</p><p>Default: <b class="command">enhanced browsing = yes</b></p></dd><dt><span class="term"><a name="ENUMPORTSCOMMAND"></a>enumports command (G)</span></dt><dd><p>The concept of a "port" is fairly foreign
     to UNIX hosts.  Under Windows NT/2000 print servers, a port
     is associated with a port monitor and generally takes the form of
     a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
     (i.e. LPD Port Monitor, etc...).  By default, Samba has only one
-    port defined--<tt class="constant">&quot;Samba Printer Port&quot;</tt>.  Under 
+    port defined--<tt class="constant">"Samba Printer Port"</tt>.  Under 
     Windows NT/2000, all printers must have a valid port name.  
     If you wish to have a list of ports displayed (<b class="command">smbd
     </b> does not use a port name for anything) other than 
-    the default <tt class="constant">&quot;Samba Printer Port&quot;</tt>, you 
+    the default <tt class="constant">"Samba Printer Port"</tt>, you 
     can define <i class="parameter"><tt>enumports command</tt></i> to point to
     a program which should generate a list of ports, one per line,
     to standard output.  This listing will then be used in response
@@ -993,7 +1012,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     allows a user to modify all the user/group/world permissions on a 
     directory without restrictions.</p><p><span class="emphasis"><em>Note</em></span> that users who can access the 
     Samba server through other means can easily bypass this restriction, 
-    so it is primarily useful for standalone &quot;appliance&quot; systems.  
+    so it is primarily useful for standalone "appliance" systems.  
     Administrators of most normal systems will probably want to leave
     it set as 0000.</p><p>See also the <a href="#DIRECTORYSECURITYMASK"><i class="parameter"><tt>
     directory security mask</tt></i></a>, <a href="#SECURITYMASK">
@@ -1030,7 +1049,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     and allows a user to modify all the user/group/world permissions on a file,
     with no restrictions.</p><p><span class="emphasis"><em>Note</em></span> that users who can access 
     the Samba server through other means can easily bypass this restriction, 
-    so it is primarily useful for standalone &quot;appliance&quot; systems.  
+    so it is primarily useful for standalone "appliance" systems.  
     Administrators of most normal systems will probably want to leave
     this set to 0000.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE"><i class="parameter"><tt>
     force directory security mode</tt></i></a>,
@@ -1042,7 +1061,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     as using it incorrectly can cause security problems.</p><p>This user name only gets used once a connection is established. 
     Thus clients still need to connect as a valid user and supply a 
     valid password. Once connected, all file operations will be performed 
-    as the &quot;forced user&quot;, no matter what username the client connected 
+    as the "forced user", no matter what username the client connected 
     as.  This can be very useful.</p><p>In Samba 2.0.5 and above this parameter also causes the 
     primary group of the forced user to be used as the primary group 
     for all file activity. Prior to 2.0.5 the primary group was left 
@@ -1068,17 +1087,17 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     guest ok</tt></i></a> (see below). Whatever privileges this 
     user has will be available to any client connecting to the guest service. 
     Typically this user will exist in the password file, but will not
-    have a valid login. The user account &quot;ftp&quot; is often a good choice 
+    have a valid login. The user account "ftp" is often a good choice 
     for this parameter. If a username is specified in a given service, 
     the specified username overrides this one.
-    </p><p>One some systems the default guest account &quot;nobody&quot; may not 
+    </p><p>One some systems the default guest account "nobody" may not 
     be able to print. Use another account in this case. You should test 
     this by trying to log in as your guest user (perhaps by using the 
     <b class="command">su -</b> command) and trying to print using the 
     system print command such as <b class="command">lpr(1)</b> or <b class="command">
     lp(1)</b>.</p><p>This parameter does not accept % macros, because
     many parts of the system require this value to be
-    constant for correct operation.</p><p>Default: <span class="emphasis"><em>specified at compile time, usually &quot;nobody&quot;</em></span></p><p>Example: <b class="command">guest account = ftp</b></p></dd><dt><span class="term"><a name="GUESTOK"></a>guest ok (S)</span></dt><dd><p>If this parameter is <tt class="constant">yes</tt> for 
+    constant for correct operation.</p><p>Default: <span class="emphasis"><em>specified at compile time, usually "nobody"</em></span></p><p>Example: <b class="command">guest account = ftp</b></p></dd><dt><span class="term"><a name="GUESTOK"></a>guest ok (S)</span></dt><dd><p>If this parameter is <tt class="constant">yes</tt> for 
     a service, then no password is required to connect to the service. 
     Privileges will be those of the <a href="#GUESTACCOUNT"><i class="parameter"><tt>
     guest account</tt></i></a>.</p><p>This paramater nullifies the benifits of setting
@@ -1153,7 +1172,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     <i class="parameter"><tt>hosts deny</tt></i></a> option.</p><p>You can also specify hosts by network/netmask pairs and 
     by netgroup names if your system supports netgroups. The 
     <span class="emphasis"><em>EXCEPT</em></span> keyword can also be used to limit a 
-    wildcard list. The following examples may provide some help:</p><p>Example 1: allow all IPs in 150.203.*.*; except one</p><p><b class="command">hosts allow = 150.203. EXCEPT 150.203.6.66</b></p><p>Example 2: allow hosts that match the given network/netmask</p><p><b class="command">hosts allow = 150.203.15.0/255.255.255.0</b></p><p>Example 3: allow a couple of hosts</p><p><b class="command">hosts allow = lapland, arvidsjaur</b></p><p>Example 4: allow only hosts in NIS netgroup &quot;foonet&quot;, but 
+    wildcard list. The following examples may provide some help:</p><p>Example 1: allow all IPs in 150.203.*.*; except one</p><p><b class="command">hosts allow = 150.203. EXCEPT 150.203.6.66</b></p><p>Example 2: allow hosts that match the given network/netmask</p><p><b class="command">hosts allow = 150.203.15.0/255.255.255.0</b></p><p>Example 3: allow a couple of hosts</p><p><b class="command">hosts allow = lapland, arvidsjaur</b></p><p>Example 4: allow only hosts in NIS netgroup "foonet", but 
     deny access from one particular host</p><p><b class="command">hosts allow = @foonet</b></p><p><b class="command">hosts deny = pirate</b></p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Note that access still requires suitable user-level passwords.</p></div><p>See <a href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a> for a way of testing your host access 
     to see if it does what you expect.</p><p>Default: <span class="emphasis"><em>none (i.e., all hosts permitted access)</em></span></p><p>Example: <b class="command">allow hosts = 150.203.5. myhost.mynet.edu.au</b></p></dd><dt><span class="term"><a name="HOSTSDENY"></a>hosts deny (S)</span></dt><dd><p>The opposite of <i class="parameter"><tt>hosts allow</tt></i> 
     - hosts listed here are <span class="emphasis"><em>NOT</em></span> permitted access to 
@@ -1179,7 +1198,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	LDAP backend. This way all domain members and controllers will have the same UID and GID
 	to SID mappings. This avoids the risk of UID / GID inconsistencies across UNIX / Linux
 	systems that are sharing information over protocols other than SMB/CIFS (ie: NFS).
-	</p><p>Default: <b class="command">idmap backend = &lt;empty string&gt;</b></p><p>Example: <b class="command">idmap backend = ldapsam://ldapslave.example.com</b></p></dd><dt><span class="term"><a name="IDMAPGID"></a>idmap gid (G)</span></dt><dd><p>The idmap gid parameter specifies the range of group ids that are allocated for
+	</p><p>Default: <b class="command">idmap backend = &lt;empty string&gt;</b></p><p>Example: <b class="command">idmap backend = ldap:ldap://ldapslave.example.com</b></p></dd><dt><span class="term"><a name="IDMAPGID"></a>idmap gid (G)</span></dt><dd><p>The idmap gid parameter specifies the range of group ids that are allocated for
 	the purpose of mapping UNX groups to NT group SIDs. This range of group ids should have no 
 	existing local or NIS groups within it as strange conflicts can occur otherwise.</p><p>The availability of an idmap gid range is essential for correct operation of
 	all group mapping.</p><p>Default: <b class="command">idmap gid = &lt;empty string&gt;</b></p><p>Example: <b class="command">idmap gid = 10000-20000</b></p></dd><dt><span class="term"><a name="IDMAPUID"></a>idmap uid (G)</span></dt><dd><p>The idmap uid parameter specifies the range of user ids that are allocated for use
@@ -1222,11 +1241,11 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	interfaces except 127.0.0.1 that are broadcast capable.</p><p>The option takes a list of interface strings. Each string 
 	can be in any of the following forms:</p><div class="itemizedlist"><ul type="disc"><li><p>a network interface name (such as eth0). 
 		This may include shell-like wildcards so eth* will match 
-		any interface starting with the substring &quot;eth&quot;</p></li><li><p>an IP address. In this case the netmask is 
+		any interface starting with the substring "eth"</p></li><li><p>an IP address. In this case the netmask is 
 		determined from the list of interfaces obtained from the 
-		kernel</p></li><li><p>an IP/mask pair. </p></li><li><p>a broadcast/mask pair.</p></li></ul></div><p>The &quot;mask&quot; parameters can either be a bit length (such 
+		kernel</p></li><li><p>an IP/mask pair. </p></li><li><p>a broadcast/mask pair.</p></li></ul></div><p>The "mask" parameters can either be a bit length (such 
 	as 24 for a C class network) or a full netmask in dotted 
-	decimal form.</p><p>The &quot;IP&quot; parameters above can either be a full dotted 
+	decimal form.</p><p>The "IP" parameters above can either be a full dotted 
 	decimal IP address or a hostname which will be looked up via 
 	the OS's normal hostname resolution mechanisms.</p><p>For example, the following line:</p><p><b class="command">interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</b></p><p>would configure three network interfaces corresponding 
 	to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. 
@@ -1255,7 +1274,12 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     a client is still present and responding.</p><p>Keepalives should, in general, not be needed if the socket 
     being used has the SO_KEEPALIVE attribute set on it (see <a href="#SOCKETOPTIONS">
     <i class="parameter"><tt>socket options</tt></i></a>). 
-    Basically you should only use this option if you strike difficulties.</p><p>Default: <b class="command">keepalive = 300</b></p><p>Example: <b class="command">keepalive = 600</b></p></dd><dt><span class="term"><a name="KERNELOPLOCKS"></a>kernel oplocks (G)</span></dt><dd><p>For UNIXes that support kernel based <a href="#OPLOCKS">
+    Basically you should only use this option if you strike difficulties.</p><p>Default: <b class="command">keepalive = 300</b></p><p>Example: <b class="command">keepalive = 600</b></p></dd><dt><span class="term"><a name="KERNELCHANGENOTIFY"></a>kernel change notify (G)</span></dt><dd><p>This parameter specifies whether Samba should ask the 
+	kernel for change notifications in directories so that
+	SMB clients can refresh whenever the data on the server changes.
+	</p><p>This parameter is only usd when your kernel supports 
+	change notification to user programs, using the F_NOTIFY fcntl.
+	</p><p>Default: <span class="emphasis"><em>Yes</em></span></p></dd><dt><span class="term"><a name="KERNELOPLOCKS"></a>kernel oplocks (G)</span></dt><dd><p>For UNIXes that support kernel based <a href="#OPLOCKS">
 	<i class="parameter"><tt>oplocks</tt></i></a>
 	(currently only IRIX and the Linux 2.4 kernel), this parameter 
 	allows the use of them to be turned on or off.</p><p>Kernel oplocks support allows Samba <i class="parameter"><tt>oplocks
@@ -1300,7 +1324,12 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	The default is to match the login name with the <tt class="constant">uid</tt> 
 	attribute for all entries matching the <tt class="constant">sambaAccount</tt>		
 	objectclass.  Note that this filter should only return one entry.
-	</p><p>Default: <b class="command">ldap filter = (&amp;(uid=%u)(objectclass=sambaAccount))</b></p></dd><dt><span class="term"><a name="LDAPMACHINESUFFIX"></a>ldap machine suffix (G)</span></dt><dd><p>It specifies where machines should be added to the ldap tree.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPPASSWDSYNC"></a>ldap passwd sync (G)</span></dt><dd><p>This option is used to define whether
+	</p><p>Default: <b class="command">ldap filter = (&amp;(uid=%u)(objectclass=sambaAccount))</b></p></dd><dt><span class="term"><a name="LDAPGROUPSUFFIX"></a>ldap group suffix (G)</span></dt><dd><p>This parameters specifies the suffix that is 
+	used for groups when these are added to the LDAP directory.
+	If this parameter is unset, the value of <i class="parameter"><tt>ldap suffix</tt></i> will be used instead.</p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <span class="emphasis"><em>dc=samba,ou=Groups</em></span></p></dd><dt><span class="term"><a name="LDAPIDMAPSUFFIX"></a>ldap idmap suffix (G)</span></dt><dd><p>This parameters specifies the suffix that is 
+	used when storing idmap mappings. If this parameter 
+	is unset, the value of <i class="parameter"><tt>ldap suffix</tt></i>
+	will be used instead.</p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <span class="emphasis"><em>dc=samba,ou=Idmap</em></span></p></dd><dt><span class="term"><a name="LDAPMACHINESUFFIX"></a>ldap machine suffix (G)</span></dt><dd><p>It specifies where machines should be added to the ldap tree.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPPASSWDSYNC"></a>ldap passwd sync (G)</span></dt><dd><p>This option is used to define whether
 	or not Samba should sync the LDAP password with the NT
 	and LM hashes for normal accounts (NOT for
 	workstation, server or domain trusts) on a password
@@ -1332,16 +1361,8 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	tree. Can be overriden by <b class="command">ldap user
 	suffix</b> and <b class="command">ldap machine
 	suffix</b>. It also used as the base dn for all ldap
-	searches. </p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPTRUSTIDS"></a>ldap trust ids (G)</span></dt><dd><p>Normally, Samba validates each entry in the LDAP server
-	against getpwnam(). This allows LDAP to be used for Samba with
-	the unix system using NIS (for example) and also ensures that
-	Samba does not present accounts that do not otherwise exist. 
-	</p><p>This option is used to disable this functionality, and 	
-	instead to rely on the presence of the appropriate  attributes
-	in LDAP directly, which can result in a  significant performance
-	boost in some situations.  Setting this option to yes effectivly
-	assumes that the local machine is running <b class="command">nss_ldap</b> against the same LDAP
-	server.</p><p>Default: <b class="command">ldap trust ids = No</b></p></dd><dt><span class="term"><a name="LDAPUSERSUFFIX"></a>ldap user suffix (G)</span></dt><dd><p>It specifies where users are added to the tree.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LEVEL2OPLOCKS"></a>level2 oplocks (S)</span></dt><dd><p>This parameter controls whether Samba supports
+	searches. </p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPUSERSUFFIX"></a>ldap user suffix (G)</span></dt><dd><p>This parameter specifies where users are added to the tree. 
+	If this parameter is not specified, the value from <b class="command">ldap suffix</b>.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LEVEL2OPLOCKS"></a>level2 oplocks (S)</span></dt><dd><p>This parameter controls whether Samba supports
 	level2 (read-only) oplocks on a share.</p><p>Level2, or read-only oplocks allow Windows NT clients 
 	that have an oplock on a file to downgrade from a read-write oplock 
 	to a read-only oplock once a second client opens the file (instead 
@@ -1352,7 +1373,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	for many accesses of files that are not commonly written (such as 
 	application .EXE files).</p><p>Once one of the clients which have a read-only oplock 
 	writes to the file all clients are notified (no reply is needed 
-	or waited for) and told to break their oplocks to &quot;none&quot; and 
+	or waited for) and told to break their oplocks to "none" and 
 	delete any read-ahead caches.</p><p>It is recommended that this parameter be turned on to
 	speed access to shared executables.</p><p>For more discussions on level2 oplocks see the CIFS spec.</p><p>Currently, if <a href="#KERNELOPLOCKS"><i class="parameter"><tt>kernel 
 	oplocks</tt></i></a> are supported then level2 oplocks are 
@@ -1390,12 +1411,12 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	<tt class="constant">yes</tt> doesn't mean that Samba will <span class="emphasis"><em>become</em></span> the 
 	local master browser on a subnet, just that <b class="command">nmbd</b> 
 	will <span class="emphasis"><em>participate</em></span> in elections for local master browser.</p><p>Setting this value to <tt class="constant">no</tt> will cause <b class="command">nmbd</b> <span class="emphasis"><em>never</em></span> to become a local 
-	master browser.</p><p>Default: <b class="command">local master = yes</b></p></dd><dt><span class="term"><a name="LOCKDIRECTORY"></a>lock directory (G)</span></dt><dd><p>This option specifies the directory where lock 
+	master browser.</p><p>Default: <b class="command">local master = yes</b></p></dd><dt><span class="term"><a name="LOCKDIR"></a>lock dir (G)</span></dt><dd><p>Synonym for <a href="#LOCKDIRECTORY"><i class="parameter"><tt>
+	lock directory</tt></i></a>.
+</p></dd><dt><span class="term"><a name="LOCKDIRECTORY"></a>lock directory (G)</span></dt><dd><p>This option specifies the directory where lock 
 	files will be placed.  The lock files are used to implement the 
 	<a href="#MAXCONNECTIONS"><i class="parameter"><tt>max connections</tt></i>
-	</a> option.</p><p>Default: <b class="command">lock directory = ${prefix}/var/locks</b></p><p>Example: <b class="command">lock directory = /var/run/samba/locks</b></p></dd><dt><span class="term"><a name="LOCKDIR"></a>lock dir (G)</span></dt><dd><p>Synonym for <a href="#LOCKDIRECTORY"><i class="parameter"><tt>
-	lock directory</tt></i></a>.
-</p></dd><dt><span class="term"><a name="LOCKING"></a>locking (S)</span></dt><dd><p>This controls whether or not locking will be 
+	</a> option.</p><p>Default: <b class="command">lock directory = ${prefix}/var/locks</b></p><p>Example: <b class="command">lock directory = /var/run/samba/locks</b></p></dd><dt><span class="term"><a name="LOCKING"></a>locking (S)</span></dt><dd><p>This controls whether or not locking will be 
 	performed by the server in response to lock requests from the 
 	client.</p><p>If <b class="command">locking = no</b>, all lock and unlock 
 	requests will appear to succeed and all lock queries will report 
@@ -1444,14 +1465,14 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	<i class="parameter"><tt>logon home</tt></i>.  This broke <b class="command">net use /home</b> but allowed profiles outside the home directory.  
 	The current implementation is correct, and can be used for profiles if you use 
 	the above trick.</p><p>This option is only useful if Samba is set up as a logon 
-	server.</p><p>Default: <b class="command">logon home = &quot;\\%N\%U&quot;</b></p><p>Example: <b class="command">logon home = &quot;\\remote_smb_server\%U&quot;</b></p></dd><dt><span class="term"><a name="LOGONPATH"></a>logon path (G)</span></dt><dd><p>This parameter specifies the home directory 
+	server.</p><p>Default: <b class="command">logon home = "\\%N\%U"</b></p><p>Example: <b class="command">logon home = "\\remote_smb_server\%U"</b></p></dd><dt><span class="term"><a name="LOGONPATH"></a>logon path (G)</span></dt><dd><p>This parameter specifies the home directory 
 	where roaming profiles (NTuser.dat etc files for Windows NT) are 
 	stored.  Contrary to previous versions of these manual pages, it has 
 	nothing to do with Win 9X roaming profiles.  To find out how to 
 	handle roaming profiles for Win 9X system, see the <a href="#LOGONHOME">
 	<i class="parameter"><tt>logon home</tt></i></a> parameter.</p><p>This option takes the standard substitutions, allowing you 
 	to have separate logon scripts for each user or machine.  It also 
-	specifies the directory from which the &quot;Application Data&quot;, 
+	specifies the directory from which the "Application Data", 
 	(<tt class="filename">desktop</tt>, <tt class="filename">start menu</tt>,
 	<tt class="filename">network neighborhood</tt>, <tt class="filename">programs</tt> 
 	and other folders, and their contents, are loaded and displayed on 
@@ -1589,12 +1610,12 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	you would use:</p><p><b class="command">mangled map = (*.html *.htm)</b></p><p>One very useful case is to remove the annoying <tt class="filename">;1
 	</tt> off the ends of filenames on some CDROMs (only visible 
 	under some UNIXes). To do this use a map of (*;1 *;).</p><p>Default: <span class="emphasis"><em>no mangled map</em></span></p><p>Example: <b class="command">mangled map = (*;1 *;)</b></p></dd><dt><span class="term"><a name="MANGLEDNAMES"></a>mangled names (S)</span></dt><dd><p>This controls whether non-DOS names under UNIX 
-	should be mapped to DOS-compatible names (&quot;mangled&quot;) and made visible, 
+	should be mapped to DOS-compatible names ("mangled") and made visible, 
 	or whether non-DOS names should simply be ignored.</p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a> for 
 	details on how to control the mangling process.</p><p>If mangling is used then the mangling algorithm is as follows:</p><div class="itemizedlist"><ul type="disc"><li><p>The first (up to) five alphanumeric characters 
 			before the rightmost dot of the filename are preserved, forced 
 			to upper case, and appear as the first (up to) five characters 
-			of the mangled name.</p></li><li><p>A tilde &quot;~&quot; is appended to the first part of the mangled
+			of the mangled name.</p></li><li><p>A tilde "~" is appended to the first part of the mangled
 			name, followed by a two-character unique sequence, based on the
 			original root name (i.e., the original filename minus its final
 			extension). The final extension is included in the hash calculation
@@ -1606,9 +1627,9 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 			extension of the mangled name. The final extension is defined as that 
 			part of the original filename after the rightmost dot. If there are no 
 			dots in the filename, the mangled name will have no extension (except 
-			in the case of &quot;hidden files&quot; - see below).</p></li><li><p>Files whose UNIX name begins with a dot will be 
+			in the case of "hidden files" - see below).</p></li><li><p>Files whose UNIX name begins with a dot will be 
 			presented as DOS hidden files. The mangled name will be created as 
-			for other filenames, but with the leading dot removed and &quot;___&quot; as 
+			for other filenames, but with the leading dot removed and "___" as 
 			its extension regardless of actual original extension (that's three 
 			underscores).</p></li></ul></div><p>The two-digit hash value consists of upper case alphanumeric characters.</p><p>This algorithm can cause name collisions only if files 
 	in a directory share the same first five alphanumeric characters. 
@@ -1634,9 +1655,9 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	the <span class="emphasis"><em>magic</em></span> character in <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">name mangling</a>. The 
 	default is a '~' but this may interfere with some software. Use this option to set 
 	it to whatever you prefer. This is effective only when mangling method is hash.</p><p>Default: <b class="command">mangling char = ~</b></p><p>Example: <b class="command">mangling char = ^</b></p></dd><dt><span class="term"><a name="MANGLINGMETHOD"></a>mangling method (G)</span></dt><dd><p> controls the algorithm used for the generating
-	the mangled names. Can take two different values, &quot;hash&quot; and
-	&quot;hash2&quot;. &quot;hash&quot; is  the default and is the algorithm that has been
-	used in Samba for many years. &quot;hash2&quot; is a newer and considered
+	the mangled names. Can take two different values, "hash" and
+	"hash2". "hash" is  the default and is the algorithm that has been
+	used in Samba for many years. "hash2" is a newer and considered
 	a better algorithm (generates less collisions) in the names.
 	However, many Win32 applications store the mangled names and so
 	changing to the new algorithm must not be done
@@ -1677,18 +1698,18 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	    with an invalid password are treated as a guest login and mapped 
 	    into the <a href="#GUESTACCOUNT">guest account</a>. Note that 
 	    this can cause problems as it means that any user incorrectly typing 
-	    their password will be silently logged on as &quot;guest&quot; - and 
+	    their password will be silently logged on as "guest" - and 
 	    will not know the reason they cannot access files they think
 	    they should - there will have been no message given to them
 	    that they got their password wrong. Helpdesk services will
 	    <span class="emphasis"><em>hate</em></span> you if you set the <i class="parameter"><tt>map to 
-	    guest</tt></i> parameter this way :-).</p></li></ul></div><p>Note that this parameter is needed to set up &quot;Guest&quot; 
+	    guest</tt></i> parameter this way :-).</p></li></ul></div><p>Note that this parameter is needed to set up "Guest" 
     share services when using <i class="parameter"><tt>security</tt></i> modes other than 
     share. This is because in these modes the name of the resource being
     requested is <span class="emphasis"><em>not</em></span> sent to the server until after 
     the server has successfully authenticated the client so the server 
     cannot make authentication decisions at the correct time (connection 
-    to the share) for &quot;Guest&quot; shares.</p><p>For people familiar with the older Samba releases, this 
+    to the share) for "Guest" shares.</p><p>For people familiar with the older Samba releases, this 
     parameter maps to the old compile-time setting of the <tt class="constant">
     GUEST_SESSSETUP</tt> value in local.h.</p><p>Default: <b class="command">map to guest = Never</b></p><p>Example: <b class="command">map to guest = Bad User</b></p></dd><dt><span class="term"><a name="MAXCONNECTIONS"></a>max connections (S)</span></dt><dd><p>This option allows the number of simultaneous connections to a service to be limited.
     If <i class="parameter"><tt>max connections</tt></i> is greater than 0 then connections
@@ -1718,7 +1739,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     by the UNIX per-process file descriptor limit rather than 
     this parameter so you should never need to touch this parameter.</p><p>Default: <b class="command">max open files = 10000</b></p></dd><dt><span class="term"><a name="MAXPRINTJOBS"></a>max print jobs (S)</span></dt><dd><p>This parameter limits the maximum number of 
     jobs allowable in a Samba printer queue at any given moment.
-    If this number is exceeded, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will remote &quot;Out of Space&quot; to the client.
+    If this number is exceeded, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will remote "Out of Space" to the client.
     See all <a href="#"><i class="parameter"><tt>total
     print jobs</tt></i></a>.
     </p><p>Default: <b class="command">max print jobs = 1000</b></p><p>Example: <b class="command">max print jobs = 5000</b></p></dd><dt><span class="term"><a name="MAXPROTOCOL"></a>max protocol (G)</span></dt><dd><p>The value of the parameter (a string) is the highest 
@@ -1825,8 +1846,8 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     suite to determine what naming services to use and in what order 
     to resolve host names to IP addresses. Its main purpose to is to
     control how netbios name resolution is performed.  The option takes a space 
-    separated string of name resolution options.</p><p>The options are: &quot;lmhosts&quot;, &quot;host&quot;,
-    &quot;wins&quot; and &quot;bcast&quot;. They cause names to be
+    separated string of name resolution options.</p><p>The options are: "lmhosts", "host",
+    "wins" and "bcast". They cause names to be
     resolved as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="constant">lmhosts</tt> : Lookup an IP 
 	    address in the Samba lmhosts file. If the line in lmhosts has 
 	    no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html" target="_top">lmhosts(5)</a> for details) then
@@ -1975,7 +1996,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     <a href="#PASSWDCHAT"><i class="parameter"><tt>passwd chat</tt></i></a>
     parameter for most setups.</p><p>Default: <b class="command">pam password change = no</b></p></dd><dt><span class="term"><a name="PANICACTION"></a>panic action (G)</span></dt><dd><p>This is a Samba developer option that allows a 
 	system command to be called when either <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> or <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>	crashes. This is usually used to 
-	draw attention to the fact that a problem occurred.</p><p>Default: <b class="command">panic action = &lt;empty string&gt;</b></p><p>Example: <b class="command">panic action = &quot;/bin/sleep 90000&quot;</b></p></dd><dt><span class="term"><a name="PARANOIDSERVERSECURITY"></a>paranoid server security (G)</span></dt><dd><p>Some version of NT 4.x allow non-guest 
+	draw attention to the fact that a problem occurred.</p><p>Default: <b class="command">panic action = &lt;empty string&gt;</b></p><p>Example: <b class="command">panic action = "/bin/sleep 90000"</b></p></dd><dt><span class="term"><a name="PARANOIDSERVERSECURITY"></a>paranoid server security (G)</span></dt><dd><p>Some version of NT 4.x allow non-guest 
     users with a bad passowrd. When this option is enabled, samba will not 
     use a broken NT 4.x server as password server, but instead complain
     to the logs and exit.  
@@ -2007,21 +2028,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 		argument. Read the Samba HOWTO Collection for configuration
 		details.
 		</p></li></ul></div><p>
-    </p><p>Default: <b class="command">passdb backend = smbpasswd</b></p><p>Example: <b class="command">passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd</b></p><p>Example: <b class="command">passdb backend = ldapsam:ldaps://ldap.example.com</b></p><p>Example: <b class="command">passdb backend = mysql:my_plugin_args tdbsam</b></p></dd><dt><span class="term"><a name="PASSWDCHATDEBUG"></a>passwd chat debug (G)</span></dt><dd><p>This boolean specifies if the passwd chat script 
-    parameter is run in <span class="emphasis"><em>debug</em></span> mode. In this mode the 
-    strings passed to and received from the passwd chat are printed 
-    in the <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> log with a 
-    <a href="#DEBUGLEVEL"><i class="parameter"><tt>debug level</tt></i></a> 
-    of 100. This is a dangerous option as it will allow plaintext passwords 
-    to be seen in the <b class="command">smbd</b> log. It is available to help 
-    Samba admins debug their <i class="parameter"><tt>passwd chat</tt></i> scripts 
-    when calling the <i class="parameter"><tt>passwd program</tt></i> and should 
-    be turned off after this has been done. This option has no effect if the 
-    <a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i></a>
-    paramter is set. This parameter is off by default.</p><p>See also <a href="#PASSWDCHAT"><i class="parameter"><tt>passwd chat</tt></i>
-    </a>, <a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i>
-    </a>, <a href="#PASSWDPROGRAM"><i class="parameter"><tt>passwd program</tt></i>
-    </a>.</p><p>Default: <b class="command">passwd chat debug = no</b></p></dd><dt><span class="term"><a name="PASSWDCHAT"></a>passwd chat (G)</span></dt><dd><p>This string controls the <span class="emphasis"><em>&quot;chat&quot;</em></span> 
+    </p><p>Default: <b class="command">passdb backend = smbpasswd</b></p><p>Example: <b class="command">passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd</b></p><p>Example: <b class="command">passdb backend = ldapsam:ldaps://ldap.example.com</b></p><p>Example: <b class="command">passdb backend = mysql:my_plugin_args tdbsam</b></p></dd><dt><span class="term"><a name="PASSWDCHAT"></a>passwd chat (G)</span></dt><dd><p>This string controls the <span class="emphasis"><em>"chat"</em></span> 
     conversation that takes places between <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and the local password changing
     program to change the user's password. The string describes a 
     sequence of response-receive pairs that <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> uses to determine what to send to the 
@@ -2043,7 +2050,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     give line-feed, carriage-return, tab and space.  The chat sequence string can also contain 
     a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces 
     in them into a single string.</p><p>If the send string in any part of the chat sequence  is a full
-    stop &quot;.&quot;,  then no string is sent. Similarly,  if the
+    stop ".",  then no string is sent. Similarly,  if the
     expect string is a full stop then no string is expected.</p><p>If the <a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam
     password change</tt></i></a> parameter is set to <tt class="constant">yes</tt>, the chat pairs
     may be matched in any order, and success is determined by the PAM result, 
@@ -2053,9 +2060,23 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     passwd program</tt></i></a> ,<a href="#PASSWDCHATDEBUG">
     <i class="parameter"><tt>passwd chat debug</tt></i></a> and <a href="#PAMPASSWORDCHANGE">
     <i class="parameter"><tt>pam password change</tt></i></a>.</p><p>Default: <b class="command">passwd chat = *new*password* %n\\n 
-    *new*password* %n\\n *changed*</b></p><p>Example: <b class="command">passwd chat = &quot;*Enter OLD password*&quot; %o\\n 
-    &quot;*Enter NEW password*&quot; %n\\n &quot;*Reenter NEW password*&quot; %n\\n 
-    &quot;*Password changed*&quot;</b></p></dd><dt><span class="term"><a name="PASSWDPROGRAM"></a>passwd program (G)</span></dt><dd><p>The name of a program that can be used to set 
+    *new*password* %n\\n *changed*</b></p><p>Example: <b class="command">passwd chat = "*Enter OLD password*" %o\\n 
+    "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n 
+    "*Password changed*"</b></p></dd><dt><span class="term"><a name="PASSWDCHATDEBUG"></a>passwd chat debug (G)</span></dt><dd><p>This boolean specifies if the passwd chat script 
+    parameter is run in <span class="emphasis"><em>debug</em></span> mode. In this mode the 
+    strings passed to and received from the passwd chat are printed 
+    in the <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> log with a 
+    <a href="#DEBUGLEVEL"><i class="parameter"><tt>debug level</tt></i></a> 
+    of 100. This is a dangerous option as it will allow plaintext passwords 
+    to be seen in the <b class="command">smbd</b> log. It is available to help 
+    Samba admins debug their <i class="parameter"><tt>passwd chat</tt></i> scripts 
+    when calling the <i class="parameter"><tt>passwd program</tt></i> and should 
+    be turned off after this has been done. This option has no effect if the 
+    <a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i></a>
+    paramter is set. This parameter is off by default.</p><p>See also <a href="#PASSWDCHAT"><i class="parameter"><tt>passwd chat</tt></i>
+    </a>, <a href="#PAMPASSWORDCHANGE"><i class="parameter"><tt>pam password change</tt></i>
+    </a>, <a href="#PASSWDPROGRAM"><i class="parameter"><tt>passwd program</tt></i>
+    </a>.</p><p>Default: <b class="command">passwd chat debug = no</b></p></dd><dt><span class="term"><a name="PASSWDPROGRAM"></a>passwd program (G)</span></dt><dd><p>The name of a program that can be used to set 
     UNIX user passwords.  Any occurrences of <i class="parameter"><tt>%u</tt></i> 
     will be replaced with the user name. The user name is checked for 
     existence before calling the password changing program.</p><p>Also note that many passwd programs insist in <span class="emphasis"><em>reasonable
@@ -2081,10 +2102,10 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     family of operating systems.  These clients upper case clear
     text passwords even when NT LM 0.12 selected by the protocol
     negotiation request/response.</p><p>This parameter defines the maximum number of characters 
-    that may be upper case in passwords.</p><p>For example, say the password given was &quot;FRED&quot;. If <i class="parameter"><tt>
+    that may be upper case in passwords.</p><p>For example, say the password given was "FRED". If <i class="parameter"><tt>
     password level</tt></i> is set to 1, the following combinations 
-    would be tried if &quot;FRED&quot; failed:</p><p>&quot;Fred&quot;, &quot;fred&quot;, &quot;fRed&quot;, &quot;frEd&quot;,&quot;freD&quot;</p><p>If <i class="parameter"><tt>password level</tt></i> was set to 2, 
-    the following combinations would also be tried: </p><p>&quot;FRed&quot;, &quot;FrEd&quot;, &quot;FreD&quot;, &quot;fREd&quot;, &quot;fReD&quot;, &quot;frED&quot;, ..</p><p>And so on.</p><p>The higher value this parameter is set to the more likely 
+    would be tried if "FRED" failed:</p><p>"Fred", "fred", "fRed", "frEd","freD"</p><p>If <i class="parameter"><tt>password level</tt></i> was set to 2, 
+    the following combinations would also be tried: </p><p>"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</p><p>And so on.</p><p>The higher value this parameter is set to the more likely 
     it is that a mixed case password will be matched against a single 
     case password. However, you should be aware that use of this 
     parameter reduces security and increases the time taken to 
@@ -2104,7 +2125,7 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     parameter <a href="#NAMERESOLVEORDER"><i class="parameter"><tt>name 
     resolve order</tt></i></a> and so may resolved
     by any method and order described in that parameter.</p><p>The password server must be a machine capable of using 
-    the &quot;LM1.2X002&quot; or the &quot;NT LM 0.12&quot; protocol, and it must be in 
+    the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in 
     user level security mode.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Using a password server  means your UNIX box (running
     Samba) is only as secure as your  password server. <span class="emphasis"><em>DO NOT
     CHOOSE A PASSWORD SERVER THAT  YOU DON'T COMPLETELY TRUST</em></span>.
@@ -2169,13 +2190,13 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	whenever the service is disconnected. It takes the usual 
 	substitutions. The command may be run as the root on some 
 	systems.</p><p>An interesting example may be to unmount server 
-	resources:</p><p><b class="command">postexec = /etc/umount /cdrom</b></p><p>See also <a href="#PREEXEC"><i class="parameter"><tt>preexec</tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b class="command">postexec = echo \&quot;%u disconnected from %S from %m (%I)\&quot; &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREEXECCLOSE"></a>preexec close (S)</span></dt><dd><p>This boolean option controls whether a non-zero 
-	return code from <a href="#PREEXEC"><i class="parameter"><tt>preexec
-	</tt></i></a> should close the service being connected to.</p><p>Default: <b class="command">preexec close = no</b></p></dd><dt><span class="term"><a name="PREEXEC"></a>preexec (S)</span></dt><dd><p>This option specifies a command to be run whenever 
+	resources:</p><p><b class="command">postexec = /etc/umount /cdrom</b></p><p>See also <a href="#PREEXEC"><i class="parameter"><tt>preexec</tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b class="command">postexec = echo \"%u disconnected from %S from %m (%I)\" &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREEXEC"></a>preexec (S)</span></dt><dd><p>This option specifies a command to be run whenever 
 	the service is connected to. It takes the usual substitutions.</p><p>An interesting example is to send the users a welcome 
 	message every time they log in. Maybe a message of the day? Here 
-	is an example:</p><p><b class="command">preexec = csh -c 'echo \&quot;Welcome to %S!\&quot; | /usr/local/samba/bin/smbclient -M %m -I %I' &amp; </b></p><p>Of course, this could get annoying after a while :-)</p><p>See also <a href="#PREEXECCLOSE"><i class="parameter"><tt>preexec close</tt></i></a> and <a href="#POSTEXEC"><i class="parameter"><tt>postexec
-	</tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b class="command">preexec = echo \&quot;%u connected to %S from %m (%I)\&quot; &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREFEREDMASTER"></a>prefered master (G)</span></dt><dd><p>Synonym for <a href="#PREFERREDMASTER"><i class="parameter"><tt>
+	is an example:</p><p><b class="command">preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &amp; </b></p><p>Of course, this could get annoying after a while :-)</p><p>See also <a href="#PREEXECCLOSE"><i class="parameter"><tt>preexec close</tt></i></a> and <a href="#POSTEXEC"><i class="parameter"><tt>postexec
+	</tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b class="command">preexec = echo \"%u connected to %S from %m (%I)\" &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREEXECCLOSE"></a>preexec close (S)</span></dt><dd><p>This boolean option controls whether a non-zero 
+	return code from <a href="#PREEXEC"><i class="parameter"><tt>preexec
+	</tt></i></a> should close the service being connected to.</p><p>Default: <b class="command">preexec close = no</b></p></dd><dt><span class="term"><a name="PREFEREDMASTER"></a>prefered master (G)</span></dt><dd><p>Synonym for <a href="#PREFERREDMASTER"><i class="parameter"><tt>
 	preferred master</tt></i></a> for people who cannot spell :-).</p></dd><dt><span class="term"><a name="PREFERREDMASTER"></a>preferred master (G)</span></dt><dd><p>This boolean parameter controls if
 	<a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> is a preferred master
 	browser  for its workgroup.</p><p>If this is set to <tt class="constant">yes</tt>, on startup, <b class="command">nmbd</b> 
@@ -2188,15 +2209,14 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
 	preferred  master browsers on the same subnet, they will each
 	periodically  and continuously attempt to become the local
 	master browser. This will result in unnecessary broadcast
-	traffic and reduced browsing capabilities.</p><p>See also <a href="#OSLEVEL"><i class="parameter"><tt>os level</tt></i></a>.</p><p>Default: <b class="command">preferred master = auto</b></p></dd><dt><span class="term"><a name="PRELOADMODULES"></a>preload modules (G)</span></dt><dd><p>This is a list of paths to modules that should
-	be loaded into smbd before a client connects. This improves
-	the speed of smbd when reacting to new connections somewhat. </p><p>It is recommended to only use this option on heavy-performance
-	servers.</p><p>Default: <b class="command">preload modules = </b></p><p>Example: <b class="command">preload modules = /usr/lib/samba/passdb/mysql.so+++ </b></p></dd><dt><span class="term"><a name="PRELOAD"></a>preload (G)</span></dt><dd><p>This is a list of services that you want to be 
+	traffic and reduced browsing capabilities.</p><p>See also <a href="#OSLEVEL"><i class="parameter"><tt>os level</tt></i></a>.</p><p>Default: <b class="command">preferred master = auto</b></p></dd><dt><span class="term"><a name="PRELOAD"></a>preload (G)</span></dt><dd><p>This is a list of services that you want to be 
 	automatically added to the browse lists. This is most useful 
 	for homes and printers services that would otherwise not be 
 	visible.</p><p>Note that if you just want all printers in your 
 	printcap file loaded then the <a href="#LOADPRINTERS">
-	<i class="parameter"><tt>load printers</tt></i></a> option is easier.</p><p>Default: <span class="emphasis"><em>no preloaded services</em></span></p><p>Example: <b class="command">preload = fred lp colorlp</b></p></dd><dt><span class="term"><a name="PRESERVECASE"></a>preserve case (S)</span></dt><dd><p> This controls if new filenames are created
+	<i class="parameter"><tt>load printers</tt></i></a> option is easier.</p><p>Default: <span class="emphasis"><em>no preloaded services</em></span></p><p>Example: <b class="command">preload = fred lp colorlp</b></p></dd><dt><span class="term"><a name="PRELOADMODULES"></a>preload modules (G)</span></dt><dd><p>This is a list of paths to modules that should
+	be loaded into smbd before a client connects. This improves
+	the speed of smbd when reacting to new connections somewhat. </p><p>Default: <b class="command">preload modules = </b></p><p>Example: <b class="command">preload modules = /usr/lib/samba/passdb/mysql.so+++ </b></p></dd><dt><span class="term"><a name="PRESERVECASE"></a>preserve case (S)</span></dt><dd><p> This controls if new filenames are created
 	with the case that the client passes, or if they are forced to 
 	be the <a href="#DEFAULTCASE"><i class="parameter"><tt>default case
 	</tt></i></a>.</p><p>Default: <b class="command">preserve case = yes</b></p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a> for a fuller discussion.</p></dd><dt><span class="term"><a name="PRINTABLE"></a>printable (S)</span></dt><dd><p>If this parameter is <tt class="constant">yes</tt>, then 
@@ -2205,14 +2225,15 @@ df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
     to the service path (user privileges permitting) via the spooling 
     of print data. The <a href="#READONLY"><i class="parameter"><tt>read only
     </tt></i></a> parameter controls only non-printing access to 
-    the resource.</p><p>Default: <b class="command">printable = no</b></p></dd><dt><span class="term"><a name="PRINTCAPNAME"></a>printcap name (S)</span></dt><dd><p>This parameter may be used to override the 
+    the resource.</p><p>Default: <b class="command">printable = no</b></p></dd><dt><span class="term"><a name="PRINTCAP"></a>printcap (G)</span></dt><dd><p>Synonym for <a href="#PRINTCAPNAME"><i class="parameter"><tt>
+    printcap name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTCAPNAME"></a>printcap name (S)</span></dt><dd><p>This parameter may be used to override the 
     compiled-in default printcap name used by the server (usually <tt class="filename">
     /etc/printcap</tt>). See the discussion of the <a href="#PRINTERSSECT" title="The [printers] section">[printers]</a> section above for reasons 
     why you might want to do this.</p><p>To use the CUPS printing interface set <b class="command">printcap name = cups
     </b>. This should be supplemented by an addtional setting 
     <a href="#PRINTING">printing = cups</a> in the [global] 
     section.  <b class="command">printcap name = cups</b> will use the  
-    &quot;dummy&quot; printcap created by CUPS, as specified in your CUPS
+    "dummy" printcap created by CUPS, as specified in your CUPS
     configuration file.
     </p><p>On System V systems that use <b class="command">lpstat</b> to 
     list available printers you can use <b class="command">printcap name = lpstat
@@ -2232,8 +2253,7 @@ print5|My Printer 5
     that it's a comment.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Under AIX the default printcap 
     name is <tt class="filename">/etc/qconfig</tt>. Samba will assume the 
     file is in AIX <tt class="filename">qconfig</tt> format if the string
-    <tt class="filename">qconfig</tt> appears in the printcap filename.</p></div><p>Default: <b class="command">printcap name = /etc/printcap</b></p><p>Example: <b class="command">printcap name = /etc/myprintcap</b></p></dd><dt><span class="term"><a name="PRINTCAP"></a>printcap (G)</span></dt><dd><p>Synonym for <a href="#PRINTCAPNAME"><i class="parameter"><tt>
-    printcap name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTCOMMAND"></a>print command (S)</span></dt><dd><p>After a print job has finished spooling to 
+    <tt class="filename">qconfig</tt> appears in the printcap filename.</p></div><p>Default: <b class="command">printcap name = /etc/printcap</b></p><p>Example: <b class="command">printcap name = /etc/myprintcap</b></p></dd><dt><span class="term"><a name="PRINTCOMMAND"></a>print command (S)</span></dt><dd><p>After a print job has finished spooling to 
     a service, this command will be used via a <b class="command">system()</b> 
     call to process the spool file. Typically the command specified will 
     submit the spool file to the host's printing subsystem, but there 
@@ -2274,15 +2294,15 @@ print5|My Printer 5
     uses <b class="command">lp -c -d%p -oraw; rm %s</b>.   
     With <b class="command">printing = cups</b>,
     and if SAMBA is compiled against libcups, any manually 
-    set print command will be ignored.</p><p>Example: <b class="command">print command = /usr/local/samba/bin/myprintscript %p %s</b></p></dd><dt><span class="term"><a name="PRINTERADMIN"></a>printer admin (S)</span></dt><dd><p>This is a list of users that can do anything to 
+    set print command will be ignored.</p><p>Example: <b class="command">print command = /usr/local/samba/bin/myprintscript %p %s</b></p></dd><dt><span class="term"><a name="PRINTER"></a>printer (S)</span></dt><dd><p>Synonym for <a href="#PRINTERNAME"><i class="parameter"><tt>
+    printer name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTERADMIN"></a>printer admin (S)</span></dt><dd><p>This is a list of users that can do anything to 
     printers via the remote administration interfaces offered by MS-RPC 
     (usually using a NT workstation). Note that the root user always 
     has admin rights.</p><p>Default: <b class="command">printer admin = &lt;empty string&gt;</b></p><p>Example: <b class="command">printer admin = admin, @staff</b></p></dd><dt><span class="term"><a name="PRINTERNAME"></a>printer name (S)</span></dt><dd><p>This parameter specifies the name of the printer 
     to which print jobs spooled through a printable service will be sent.</p><p>If specified in the [global] section, the printer
     name given will be used for any printable service that does 
     not have its own printer name specified.</p><p>Default: <span class="emphasis"><em>none (but may be <tt class="constant">lp</tt> 
-    on many systems)</em></span></p><p>Example: <b class="command">printer name = laserwriter</b></p></dd><dt><span class="term"><a name="PRINTER"></a>printer (S)</span></dt><dd><p>Synonym for <a href="#PRINTERNAME"><i class="parameter"><tt>
-    printer name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTING"></a>printing (S)</span></dt><dd><p>This parameters controls how printer status  information is
+    on many systems)</em></span></p><p>Example: <b class="command">printer name = laserwriter</b></p></dd><dt><span class="term"><a name="PRINTING"></a>printing (S)</span></dt><dd><p>This parameters controls how printer status  information is
     interpreted on your system. It also affects the  default values for
     the <i class="parameter"><tt>print command</tt></i>,  <i class="parameter"><tt>lpq command</tt></i>, <i class="parameter"><tt>lppause command </tt></i>, <i class="parameter"><tt>lpresume command</tt></i>, and  <i class="parameter"><tt>lprm command</tt></i> if specified in the 
     [global] section.</p><p>Currently nine printing styles are supported. They are
@@ -2310,11 +2330,11 @@ print5|My Printer 5
 	returned Windows ACL. Firstly it changes the owner and group owner
 	of all reported files and directories to be BUILTIN\\Administrators,
 	BUILTIN\\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly
-	it adds an ACE entry of &quot;Full Control&quot; to the SID BUILTIN\\Users to
+	it adds an ACE entry of "Full Control" to the SID BUILTIN\\Users to
 	every returned ACL. This will allow any Windows 2000 or XP workstation
 	user to access the profile.</p><p>Note that if you have multiple users logging
 	on to a workstation then in order to prevent them from being able to access
-	each others profiles you must remove the &quot;Bypass traverse checking&quot; advanced
+	each others profiles you must remove the "Bypass traverse checking" advanced
 	user right. This will prevent access to other users profile directories as
 	the top level profile directory (named after the user) is created by the
 	workstation profile code and has an ACL restricting entry to the directory
@@ -2344,8 +2364,8 @@ print5|My Printer 5
     path in the command as the PATH may not be available to the 
     server.</p><p>Default: <span class="emphasis"><em>depends on the setting of <a href="#PRINTING">
     <i class="parameter"><tt>printing</tt></i></a></em></span></p><p>Example: <b class="command">queuepause command = enable %p</b></p></dd><dt><span class="term"><a name="READBMPX"></a>read bmpx (G)</span></dt><dd><p>This boolean parameter controls whether
-    <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will support the &quot;Read
-    Block Multiplex&quot; SMB. This is now rarely used and defaults to 
+    <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> will support the "Read
+    Block Multiplex" SMB. This is now rarely used and defaults to 
     <tt class="constant">no</tt>. You should never need to set this 
     parameter.</p><p>Default: <b class="command">read bmpx = no</b></p></dd><dt><span class="term"><a name="READLIST"></a>read list (S)</span></dt><dd><p>This is a list of users that are given read-only 
     access to a service. If the connecting user is in this list then 
@@ -2429,17 +2449,21 @@ print5|My Printer 5
     The security advantage of using restrict anonymous = 2 is removed
     by setting <a href="#GUESTOK"><i class="parameter"><tt>guest
 	ok</tt></i> = yes</a> on any share.
-	</p></div><p>Default: <b class="command">restrict anonymous = 0</b></p></dd><dt><span class="term"><a name="ROOTDIRECTORY"></a>root directory (G)</span></dt><dd><p>The server will <b class="command">chroot()</b> (i.e. 
+	</p></div><p>Default: <b class="command">restrict anonymous = 0</b></p></dd><dt><span class="term"><a name="ROOT"></a>root (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
+    <i class="parameter"><tt>root directory"</tt></i></a>.
+    </p></dd><dt><span class="term"><a name="ROOTDIR"></a>root dir (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
+    <i class="parameter"><tt>root directory"</tt></i></a>.
+    </p></dd><dt><span class="term"><a name="ROOTDIRECTORY"></a>root directory (G)</span></dt><dd><p>The server will <b class="command">chroot()</b> (i.e. 
     Change its root directory) to this directory on startup. This is 
     not strictly necessary for secure operation. Even without it the 
     server will deny access to files not in one of the service entries. 
     It may also check for, and deny access to, soft links to other 
-    parts of the filesystem, or attempts to use &quot;..&quot; in file names 
+    parts of the filesystem, or attempts to use ".." in file names 
     to access other directories (depending on the setting of the <a href="#WIDELINKS">
     <i class="parameter"><tt>wide links</tt></i></a> 
     parameter).
     </p><p>Adding a <i class="parameter"><tt>root directory</tt></i> entry other 
-    than &quot;/&quot; adds an extra level of security, but at a price. It 
+    than "/" adds an extra level of security, but at a price. It 
     absolutely ensures that no access is given to files not in the 
     sub-tree specified in the <i class="parameter"><tt>root directory</tt></i> 
     option, <span class="emphasis"><em>including</em></span> some files needed for 
@@ -2449,42 +2473,21 @@ print5|My Printer 5
     you will need to mirror <tt class="filename">/etc/passwd</tt> (or a 
     subset of it), and any binaries or configuration files needed for 
     printing (if required). The set of files that must be mirrored is
-    operating system dependent.</p><p>Default: <b class="command">root directory = /</b></p><p>Example: <b class="command">root directory = /homes/smb</b></p></dd><dt><span class="term"><a name="ROOTDIR"></a>root dir (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
-    <i class="parameter"><tt>root directory&quot;</tt></i></a>.
-    </p></dd><dt><span class="term"><a name="ROOTPOSTEXEC"></a>root postexec (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>postexec</tt></i>
+    operating system dependent.</p><p>Default: <b class="command">root directory = /</b></p><p>Example: <b class="command">root directory = /homes/smb</b></p></dd><dt><span class="term"><a name="ROOTPOSTEXEC"></a>root postexec (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>postexec</tt></i>
 	parameter except that the command is run as root. This 
 	is useful for unmounting filesystems 
 	(such as CDROMs) after a connection is closed.</p><p>See also <a href="#POSTEXEC"><i class="parameter"><tt>
-	postexec</tt></i></a>.</p><p>Default: <b class="command">root postexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOTPREEXECCLOSE"></a>root preexec close (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>preexec close
-	</tt></i> parameter except that the command is run as root.</p><p>See also <a href="#PREEXEC"><i class="parameter"><tt>
-	preexec</tt></i></a> and <a href="#PREEXECCLOSE">
-	<i class="parameter"><tt>preexec close</tt></i></a>.</p><p>Default: <b class="command">root preexec close = no</b></p></dd><dt><span class="term"><a name="ROOTPREEXEC"></a>root preexec (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>preexec</tt></i>
+	postexec</tt></i></a>.</p><p>Default: <b class="command">root postexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOTPREEXEC"></a>root preexec (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>preexec</tt></i>
 	parameter except that the command is run as root. This 
 	is useful for mounting filesystems (such as CDROMs) when a 
 	connection is opened.</p><p>See also <a href="#PREEXEC"><i class="parameter"><tt>
 	preexec</tt></i></a> and <a href="#PREEXECCLOSE">
-	<i class="parameter"><tt>preexec close</tt></i></a>.</p><p>Default: <b class="command">root preexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOT"></a>root (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
-    <i class="parameter"><tt>root directory&quot;</tt></i></a>.
-    </p></dd><dt><span class="term"><a name="SECURITYMASK"></a>security mask (S)</span></dt><dd><p>This parameter controls what UNIX permission 
-    bits can be modified when a Windows NT client is manipulating 
-    the UNIX permission on a file using the native NT security 
-    dialog box.</p><p>This parameter is applied as a mask (AND'ed with) to 
-    the changed permission bits, thus preventing any bits not in 
-    this mask from being modified. Essentially, zero bits in this 
-    mask may be treated as a set of bits the user is not allowed 
-    to change.</p><p>If not set explicitly this parameter is 0777, allowing
-    a user to modify all the user/group/world permissions on a file.
-    </p><p><span class="emphasis"><em>Note</em></span> that users who can access the 
-    Samba server through other means can easily bypass this 
-    restriction, so it is primarily useful for standalone 
-    &quot;appliance&quot; systems.  Administrators of most normal systems will 
-    probably want to leave it set to <tt class="constant">0777</tt>.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE">
-    <i class="parameter"><tt>force directory security mode</tt></i></a>, 
-    <a href="#DIRECTORYSECURITYMASK"><i class="parameter"><tt>directory 
-    security mask</tt></i></a>, <a href="#FORCESECURITYMODE">
-    <i class="parameter"><tt>force security mode</tt></i></a> parameters.</p><p>Default: <b class="command">security mask = 0777</b></p><p>Example: <b class="command">security mask = 0770</b></p></dd><dt><span class="term"><a name="SECURITY"></a>security (G)</span></dt><dd><p>This option affects how clients respond to 
+	<i class="parameter"><tt>preexec close</tt></i></a>.</p><p>Default: <b class="command">root preexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOTPREEXECCLOSE"></a>root preexec close (S)</span></dt><dd><p>This is the same as the <i class="parameter"><tt>preexec close
+	</tt></i> parameter except that the command is run as root.</p><p>See also <a href="#PREEXEC"><i class="parameter"><tt>
+	preexec</tt></i></a> and <a href="#PREEXECCLOSE">
+	<i class="parameter"><tt>preexec close</tt></i></a>.</p><p>Default: <b class="command">root preexec close = no</b></p></dd><dt><span class="term"><a name="SECURITY"></a>security (G)</span></dt><dd><p>This option affects how clients respond to 
     Samba and is one of the most important settings in the <tt class="filename">
-    smb.conf</tt> file.</p><p>The option sets the &quot;security mode bit&quot; in replies to 
+    smb.conf</tt> file.</p><p>The option sets the "security mode bit" in replies to 
     protocol negotiations with <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> to turn share level security on or off. Clients decide 
     based on this bit whether (and how) to transfer user and password 
     information to the server.</p><p>The default is <b class="command">security = user</b>, as this is
@@ -2495,8 +2498,8 @@ print5|My Printer 5
     <b class="command">security = share</b> mainly because that was
     the only option at one stage.</p><p>There is a bug in WfWg that has relevance to this 
     setting. When in user or server level security a WfWg client 
-    will totally ignore the password you type in the &quot;connect 
-    drive&quot; dialog box. This makes it very difficult (if not impossible) 
+    will totally ignore the password you type in the "connect 
+    drive" dialog box. This makes it very difficult (if not impossible) 
     to connect to a Samba service as anyone except the user that 
     you are logged into WfWg as.</p><p>If your PCs use usernames that are the same as their 
     usernames on the UNIX machine then you will want to use 
@@ -2550,7 +2553,7 @@ print5|My Printer 5
     in share-level security as to which UNIX username will eventually
     be used in granting access.</p><p>See also the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">
     NOTE ABOUT USERNAME/PASSWORD VALIDATION</a>.</p><p><a name="SECURITYEQUALSUSER"></a><span class="emphasis"><em>SECURITY = USER</em></span></p><p>This is the default security setting in Samba 3.0. 
-    With user-level security a client must first &quot;log-on&quot; with a 
+    With user-level security a client must first "log-on" with a 
     valid username and password (which can be mapped using the <a href="#USERNAMEMAP">
     <i class="parameter"><tt>username map</tt></i></a> 
     parameter). Encrypted passwords (see the <a href="#ENCRYPTPASSWORDS">
@@ -2628,7 +2631,24 @@ print5|My Printer 5
 		Controller. </p><p>Read the chapter about Domain Membership in the HOWTO for details.</p><p>See also the <a href="#"><i class="parameter"><tt>ads server
 	</tt></i></a> parameter, the <a href="#REALM"><i class="parameter"><tt>realm
 	</tt></i></a> paramter and the <a href="#ENCRYPTPASSWORDS">
-    <i class="parameter"><tt>encrypted passwords</tt></i></a> parameter.</p><p>Default: <b class="command">security = USER</b></p><p>Example: <b class="command">security = DOMAIN</b></p></dd><dt><span class="term"><a name="SERVERSCHANNEL"></a>server schannel (G)</span></dt><dd><p>This controls whether the server offers or even
+    <i class="parameter"><tt>encrypted passwords</tt></i></a> parameter.</p><p>Default: <b class="command">security = USER</b></p><p>Example: <b class="command">security = DOMAIN</b></p></dd><dt><span class="term"><a name="SECURITYMASK"></a>security mask (S)</span></dt><dd><p>This parameter controls what UNIX permission 
+    bits can be modified when a Windows NT client is manipulating 
+    the UNIX permission on a file using the native NT security 
+    dialog box.</p><p>This parameter is applied as a mask (AND'ed with) to 
+    the changed permission bits, thus preventing any bits not in 
+    this mask from being modified. Essentially, zero bits in this 
+    mask may be treated as a set of bits the user is not allowed 
+    to change.</p><p>If not set explicitly this parameter is 0777, allowing
+    a user to modify all the user/group/world permissions on a file.
+    </p><p><span class="emphasis"><em>Note</em></span> that users who can access the 
+    Samba server through other means can easily bypass this 
+    restriction, so it is primarily useful for standalone 
+    "appliance" systems.  Administrators of most normal systems will 
+    probably want to leave it set to <tt class="constant">0777</tt>.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE">
+    <i class="parameter"><tt>force directory security mode</tt></i></a>, 
+    <a href="#DIRECTORYSECURITYMASK"><i class="parameter"><tt>directory 
+    security mask</tt></i></a>, <a href="#FORCESECURITYMODE">
+    <i class="parameter"><tt>force security mode</tt></i></a> parameters.</p><p>Default: <b class="command">security mask = 0777</b></p><p>Example: <b class="command">security mask = 0770</b></p></dd><dt><span class="term"><a name="SERVERSCHANNEL"></a>server schannel (G)</span></dt><dd><p>This controls whether the server offers or even
     demands the use of the netlogon schannel.
     <i class="parameter"><tt>server schannel = no</tt></i> does not
     offer the schannel, <i class="parameter"><tt>server schannel =
@@ -2639,7 +2659,13 @@ print5|My Printer 5
     for Windows NT4 before SP4.</p><p>Please note that with this set to
     <i class="parameter"><tt>no</tt></i> you will have to apply the
     WindowsXP requireSignOrSeal-Registry patch found in
-    the docs/Registry subdirectory.</p><p>Default: <b class="command">server schannel = auto</b></p><p>Example: <b class="command">server schannel = yes</b></p></dd><dt><span class="term"><a name="SERVERSTRING"></a>server string (G)</span></dt><dd><p>This controls what string will show up in the printer comment box in print 
+    the docs/Registry subdirectory.</p><p>Default: <b class="command">server schannel = auto</b></p><p>Example: <b class="command">server schannel = yes</b></p></dd><dt><span class="term"><a name="SERVERSIGNING"></a>server signing (G)</span></dt><dd><p>This controls whether the server offers or requires
+    the client it talks to to use SMB signing. Possible values 
+    are <span class="emphasis"><em>auto</em></span>, <span class="emphasis"><em>mandatory</em></span> 
+    and <span class="emphasis"><em>disabled</em></span>. 
+    </p><p>When set to auto, SMB signing is offered, but not enforced. 
+    When set to mandatory, SMB signing is required and if set 
+    to disabled, SMB signing is not offered either.</p><p>Default: <b class="command">client signing = False</b></p></dd><dt><span class="term"><a name="SERVERSTRING"></a>server string (G)</span></dt><dd><p>This controls what string will show up in the printer comment box in print 
         manager and next to the IPC connection in <b class="command">net view</b>. It 
         can be any string that you wish to show to your users.</p><p>It also sets what will appear in browse lists next 
 	to the machine name.</p><p>A <i class="parameter"><tt>%v</tt></i> will be replaced with the Samba 
@@ -2681,7 +2707,7 @@ print5|My Printer 5
 	</tt></i></a>. This  option can be use with <a href="#PRESERVECASE"><b class="command">preserve case = yes</b>
 	</a> to permit long filenames to retain their case, while short 
 	names are lowered. </p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a>.</p><p>Default: <b class="command">short preserve case = yes</b></p></dd><dt><span class="term"><a name="SHOWADDPRINTERWIZARD"></a>show add printer wizard (G)</span></dt><dd><p>With the introduction of MS-RPC based printing support
-    for Windows NT/2000 client in Samba 2.2, a &quot;Printers...&quot; folder will 
+    for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will 
     appear on Samba hosts in the share listing.  Normally this folder will 
     contain an icon for the MS Add Printer Wizard (APW).  However, it is 
     possible to disable this feature regardless of the level of privilege 
@@ -2712,8 +2738,8 @@ print5|My Printer 5
 #!/bin/bash
 		
 $time=0
-let &quot;time/60&quot;
-let &quot;time++&quot;
+let "time/60"
+let "time++"
 
 /sbin/shutdown $3 $4 +$time $1 &amp;
 </pre><p>
@@ -2734,7 +2760,7 @@ Shutdown does not return so we need to launch it in background.
     suggest you read the appropriate documentation for your  operating
     system first (perhaps <b class="command">man
     setsockopt</b> will help).</p><p>You may find that on some systems Samba will say 
-    &quot;Unknown socket option&quot; when you supply an option. This means you 
+    "Unknown socket option" when you supply an option. This means you 
     either incorrectly  typed it or you need to add an include file 
     to includes.h for your OS.  If the latter is the case please 
     send the patch to <a href="mailto:samba-technical@samba.org" target="_top">
@@ -2749,7 +2775,7 @@ Shutdown does not return so we need to launch it in background.
     might be:</p><p><b class="command">socket options = IPTOS_LOWDELAY</b></p><p>If you have a local network then you could try:</p><p><b class="command">socket options = IPTOS_LOWDELAY TCP_NODELAY</b></p><p>If you are on a wide area network then perhaps try 
     setting IPTOS_THROUGHPUT. </p><p>Note that several of the options may cause your Samba 
     server to fail completely. Use these options with caution!</p><p>Default: <b class="command">socket options = TCP_NODELAY</b></p><p>Example: <b class="command">socket options = IPTOS_LOWDELAY</b></p></dd><dt><span class="term"><a name="SOURCEENVIRONMENT"></a>source environment (G)</span></dt><dd><p>This parameter causes Samba to set environment 
-	variables as per the content of the file named.</p><p>If the value of this parameter starts with a &quot;|&quot; character 
+	variables as per the content of the file named.</p><p>If the value of this parameter starts with a "|" character 
 	then Samba will treat that value as a pipe command to open and 
 	will set the environment variables from the output of the pipe.</p><p>The contents of the file or the output of the pipe should 
 	be formatted as the output of the standard Unix <b class="command">env(1)</b> command. This is of the form:</p><p>Example environment entry:</p><p><b class="command">SAMBA_NETBIOS_NAME = myhostname</b></p><p>Default: <span class="emphasis"><em>No default value</em></span></p><p>Examples: <b class="command">source environment = |/etc/smb.conf.sh</b></p><p>Example: <b class="command">source environment = 
@@ -2796,9 +2822,7 @@ Shutdown does not return so we need to launch it in background.
     the <i class="parameter"><tt>strict sync</tt></i> parameter must be set to
     <tt class="constant">yes</tt> in order for this parameter to have 
     any affect.</p><p>See also the <a href="#STRICTSYNC"><i class="parameter"><tt>strict 
-    sync</tt></i></a> parameter.</p><p>Default: <b class="command">sync always = no</b></p></dd><dt><span class="term"><a name="SYSLOGONLY"></a>syslog only (G)</span></dt><dd><p>If this parameter is set then Samba debug 
-    messages are logged into the system syslog only, and not to 
-    the debug log files.</p><p>Default: <b class="command">syslog only = no</b></p></dd><dt><span class="term"><a name="SYSLOG"></a>syslog (G)</span></dt><dd><p>This parameter maps how Samba debug messages 
+    sync</tt></i></a> parameter.</p><p>Default: <b class="command">sync always = no</b></p></dd><dt><span class="term"><a name="SYSLOG"></a>syslog (G)</span></dt><dd><p>This parameter maps how Samba debug messages 
     are logged onto the system syslog logging levels. Samba debug 
     level zero maps onto syslog <tt class="constant">LOG_ERR</tt>, debug 
     level one maps onto <tt class="constant">LOG_WARNING</tt>, debug level 
@@ -2806,7 +2830,9 @@ Shutdown does not return so we need to launch it in background.
     maps onto LOG_INFO. All higher levels are mapped to <tt class="constant">
     LOG_DEBUG</tt>.</p><p>This parameter sets the threshold for sending messages 
     to syslog.  Only messages with debug level less than this value 
-    will be sent to syslog.</p><p>Default: <b class="command">syslog = 1</b></p></dd><dt><span class="term"><a name="TEMPLATEHOMEDIR"></a>template homedir (G)</span></dt><dd><p>When filling out the user information for a Windows NT 
+    will be sent to syslog.</p><p>Default: <b class="command">syslog = 1</b></p></dd><dt><span class="term"><a name="SYSLOGONLY"></a>syslog only (G)</span></dt><dd><p>If this parameter is set then Samba debug 
+    messages are logged into the system syslog only, and not to 
+    the debug log files.</p><p>Default: <b class="command">syslog only = no</b></p></dd><dt><span class="term"><a name="TEMPLATEHOMEDIR"></a>template homedir (G)</span></dt><dd><p>When filling out the user information for a Windows NT 
 	user, the <a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon  uses this
 	parameter to fill in the home directory for that user. If the
 	string <i class="parameter"><tt>%D</tt></i> is present it
@@ -2833,7 +2859,7 @@ Shutdown does not return so we need to launch it in background.
     These extensions enable Samba to better serve UNIX CIFS clients
     by supporting features such as symbolic links, hard links, etc...
     These extensions require a similarly enabled client, and are of
-    no current use to Windows clients.</p><p>Default: <b class="command">unix extensions = no</b></p></dd><dt><span class="term"><a name="UNIXPASSWORDSYNC"></a>unix password sync (G)</span></dt><dd><p>This boolean parameter controls whether Samba 
+    no current use to Windows clients.</p><p>Default: <b class="command">unix extensions = yes</b></p></dd><dt><span class="term"><a name="UNIXPASSWORDSYNC"></a>unix password sync (G)</span></dt><dd><p>This boolean parameter controls whether Samba 
     attempts to synchronize the UNIX password with the SMB password 
     when the encrypted SMB password in the smbpasswd file is changed. 
     If this is set to <tt class="constant">yes</tt> the program specified in the <i class="parameter"><tt>passwd
@@ -2877,7 +2903,7 @@ Shutdown does not return so we need to launch it in background.
     logged on user. If the user possesses local administator rights but
     not root privilegde on the Samba host (often the case), the
     OpenPrinterEx() call will fail.  The result is that the client will
-    now display an &quot;Access Denied; Unable to connect&quot; message
+    now display an "Access Denied; Unable to connect" message
     in the printer queue window (even though jobs may successfully be
     printed).  </p><p>If this parameter is enabled for a printer, then any attempt
     to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
@@ -2891,7 +2917,42 @@ Shutdown does not return so we need to launch it in background.
     default on HPUX. On all other systems this parameter should be left alone. This
     parameter is provided to help the Samba developers track down problems with
     the tdb internal code.
-    </p><p>Default: <b class="command">use mmap = yes</b></p></dd><dt><span class="term"><a name="USERNAMELEVEL"></a>username level (G)</span></dt><dd><p>This option helps Samba to try and 'guess' at 
+    </p><p>Default: <b class="command">use mmap = yes</b></p></dd><dt><span class="term"><a name="USER"></a>user (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i class="parameter"><tt>username</tt></i></a>.</p></dd><dt><span class="term"><a name="USERNAME"></a>username (S)</span></dt><dd><p>Multiple users may be specified in a comma-delimited 
+    list, in which case the supplied password will be tested against 
+    each username in turn (left to right).</p><p>The <i class="parameter"><tt>username</tt></i> line is needed only when 
+    the PC is unable to supply its own username. This is the case 
+    for the COREPLUS protocol or where your users have different WfWg 
+    usernames to UNIX usernames. In both these cases you may also be 
+    better using the \\server\share%user syntax instead.</p><p>The <i class="parameter"><tt>username</tt></i> line is not a great 
+    solution in many cases as it means Samba will try to validate 
+    the supplied password against each of the usernames in the 
+    <i class="parameter"><tt>username</tt></i> line in turn. This is slow and 
+    a bad idea for lots of users in case of duplicate passwords. 
+    You may get timeouts or security breaches using this parameter 
+    unwisely.</p><p>Samba relies on the underlying UNIX security. This 
+    parameter does not restrict who can login, it just offers hints 
+    to the Samba server as to what usernames might correspond to the 
+    supplied password. Users can login as whoever they please and 
+    they will be able to do no more damage than if they started a 
+    telnet session. The daemon runs as the user that they log in as, 
+    so they cannot do anything that user cannot do.</p><p>To restrict a service to a particular set of users you 
+    can use the <a href="#VALIDUSERS"><i class="parameter"><tt>valid users
+    </tt></i></a> parameter.</p><p>If any of the usernames begin with a '@' then the name 
+    will be looked up first in the NIS netgroups list (if Samba 
+    is compiled with netgroup support), followed by a lookup in 
+    the UNIX groups database and will expand to a list of all users 
+    in the group of that name.</p><p>If any of the usernames begin with a '+' then the name 
+    will be looked up only in the UNIX groups database and will 
+    expand to a list of all users in the group of that name.</p><p>If any of the usernames begin with a '&amp;' then the name 
+    will be looked up only in the NIS netgroups database (if Samba 
+    is compiled with netgroup support) and will expand to a list 
+    of all users in the netgroup group of that name.</p><p>Note that searching though a groups database can take 
+    quite some time, and some clients may time out during the 
+    search.</p><p>See the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">NOTE ABOUT 
+    USERNAME/PASSWORD VALIDATION</a> for more information on how 
+    this parameter determines access to the services.</p><p>Default: <b class="command">The guest account if a guest service, 
+    else &lt;empty string&gt;.</b></p><p>Examples:<b class="command">username = fred, mary, jack, jane, 
+    @users, @pcgroup</b></p></dd><dt><span class="term"><a name="USERNAMELEVEL"></a>username level (G)</span></dt><dd><p>This option helps Samba to try and 'guess' at 
     the real UNIX username, as many DOS clients send an all-uppercase 
     username. By default Samba tries all lowercase, followed by the 
     username with the first letter capitalized, and fails if the 
@@ -2926,8 +2987,8 @@ Shutdown does not return so we need to launch it in background.
     to the UNIX name <tt class="constant">sys</tt> you would use:</p><p><b class="command">sys = @system</b></p><p>You can have as many mappings as you like in a username map file.</p><p>If your system supports the NIS NETGROUP option then
     the netgroup database is checked before the <tt class="filename">/etc/group
     </tt> database for matching groups.</p><p>You can map Windows usernames that have spaces in them
-     by using double quotes around the name. For example:</p><p><b class="command">tridge = &quot;Andrew Tridgell&quot;</b></p><p>would map the windows username &quot;Andrew Tridgell&quot; to the
-    unix username &quot;tridge&quot;.</p><p>The following example would map mary and fred to the
+     by using double quotes around the name. For example:</p><p><b class="command">tridge = "Andrew Tridgell"</b></p><p>would map the windows username "Andrew Tridgell" to the
+    unix username "tridge".</p><p>The following example would map mary and fred to the
     unix user sys, and map the rest to guest. Note the use of the
     '!' to tell Samba to stop processing if it gets a match on
     that line.</p><pre class="programlisting">
@@ -2945,43 +3006,8 @@ guest = *
     modification.</p><p>Also note that no reverse mapping is done. The main effect
     this has is with printing. Users who have been mapped may have
     trouble deleting print jobs as PrintManager under WfWg will think
-    they don't own the print job.</p><p>Default: <span class="emphasis"><em>no username map</em></span></p><p>Example: <b class="command">username map = /usr/local/samba/lib/users.map</b></p></dd><dt><span class="term"><a name="USERNAME"></a>username (S)</span></dt><dd><p>Multiple users may be specified in a comma-delimited 
-    list, in which case the supplied password will be tested against 
-    each username in turn (left to right).</p><p>The <i class="parameter"><tt>username</tt></i> line is needed only when 
-    the PC is unable to supply its own username. This is the case 
-    for the COREPLUS protocol or where your users have different WfWg 
-    usernames to UNIX usernames. In both these cases you may also be 
-    better using the \\server\share%user syntax instead.</p><p>The <i class="parameter"><tt>username</tt></i> line is not a great 
-    solution in many cases as it means Samba will try to validate 
-    the supplied password against each of the usernames in the 
-    <i class="parameter"><tt>username</tt></i> line in turn. This is slow and 
-    a bad idea for lots of users in case of duplicate passwords. 
-    You may get timeouts or security breaches using this parameter 
-    unwisely.</p><p>Samba relies on the underlying UNIX security. This 
-    parameter does not restrict who can login, it just offers hints 
-    to the Samba server as to what usernames might correspond to the 
-    supplied password. Users can login as whoever they please and 
-    they will be able to do no more damage than if they started a 
-    telnet session. The daemon runs as the user that they log in as, 
-    so they cannot do anything that user cannot do.</p><p>To restrict a service to a particular set of users you 
-    can use the <a href="#VALIDUSERS"><i class="parameter"><tt>valid users
-    </tt></i></a> parameter.</p><p>If any of the usernames begin with a '@' then the name 
-    will be looked up first in the NIS netgroups list (if Samba 
-    is compiled with netgroup support), followed by a lookup in 
-    the UNIX groups database and will expand to a list of all users 
-    in the group of that name.</p><p>If any of the usernames begin with a '+' then the name 
-    will be looked up only in the UNIX groups database and will 
-    expand to a list of all users in the group of that name.</p><p>If any of the usernames begin with a '&amp;' then the name 
-    will be looked up only in the NIS netgroups database (if Samba 
-    is compiled with netgroup support) and will expand to a list 
-    of all users in the netgroup group of that name.</p><p>Note that searching though a groups database can take 
-    quite some time, and some clients may time out during the 
-    search.</p><p>See the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">NOTE ABOUT 
-    USERNAME/PASSWORD VALIDATION</a> for more information on how 
-    this parameter determines access to the services.</p><p>Default: <b class="command">The guest account if a guest service, 
-    else &lt;empty string&gt;.</b></p><p>Examples:<b class="command">username = fred, mary, jack, jane, 
-    @users, @pcgroup</b></p></dd><dt><span class="term"><a name="USERS"></a>users (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i class="parameter"><tt>
-    username</tt></i></a>.</p></dd><dt><span class="term"><a name="USER"></a>user (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i class="parameter"><tt>username</tt></i></a>.</p></dd><dt><span class="term"><a name="USESENDFILE"></a>use sendfile (S)</span></dt><dd><p>If this parameter is <tt class="constant">yes</tt>, and Samba
+    they don't own the print job.</p><p>Default: <span class="emphasis"><em>no username map</em></span></p><p>Example: <b class="command">username map = /usr/local/samba/lib/users.map</b></p></dd><dt><span class="term"><a name="USERS"></a>users (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i class="parameter"><tt>
+    username</tt></i></a>.</p></dd><dt><span class="term"><a name="USESENDFILE"></a>use sendfile (S)</span></dt><dd><p>If this parameter is <tt class="constant">yes</tt>, and Samba
     was built with the --with-sendfile-support option, and the underlying operating
     system supports sendfile system call, then some SMB read calls (mainly ReadAndX
     and ReadRaw) will use the more efficient sendfile system call for files that
@@ -2992,15 +3018,7 @@ guest = *
     WindowsXP and Windows2000 clients to agree upon an authentication mechanism. 
     Unless further issues are discovered with our SPNEGO
     implementation, there is no reason this should ever be
-    disabled.</p><p>Default:  <span class="emphasis"><em>use spnego = yes</em></span></p></dd><dt><span class="term"><a name="UTMPDIRECTORY"></a>utmp directory (G)</span></dt><dd><p>This parameter is only available if Samba has 
-	been configured and compiled with the option <b class="command">
-	--with-utmp</b>. It specifies a directory pathname that is
-	used to store the utmp or utmpx files (depending on the UNIX system) that
-	record user connections to a Samba server. See also the <a href="#UTMP">
-	<i class="parameter"><tt>utmp</tt></i></a> parameter. By default this is 
-	not set, meaning the system will use whatever utmp file the 
-	native system is set to use (usually 
-	<tt class="filename">/var/run/utmp</tt> on Linux).</p><p>Default: <span class="emphasis"><em>no utmp directory</em></span></p><p>Example: <b class="command">utmp directory = /var/run/utmp</b></p></dd><dt><span class="term"><a name="UTMP"></a>utmp (G)</span></dt><dd><p>This boolean parameter is only available if
+    disabled.</p><p>Default:  <span class="emphasis"><em>use spnego = yes</em></span></p></dd><dt><span class="term"><a name="UTMP"></a>utmp (G)</span></dt><dd><p>This boolean parameter is only available if
 	Samba has been configured and compiled  with the option <b class="command">
 	--with-utmp</b>. If set to <tt class="constant">yes</tt> then Samba will attempt
 	to add utmp or utmpx records (depending on the UNIX system) whenever a
@@ -3010,7 +3028,22 @@ guest = *
 	incoming user.  Enabling this option creates an n^2
 	algorithm to find this number.  This may impede
 	performance on large installations. </p><p>See also the <a href="#UTMPDIRECTORY"><i class="parameter"><tt>
-	utmp directory</tt></i></a> parameter.</p><p>Default: <b class="command">utmp = no</b></p></dd><dt><span class="term"><a name="VALIDUSERS"></a>valid users (S)</span></dt><dd><p>This is a list of users that should be allowed 
+	utmp directory</tt></i></a> parameter.</p><p>Default: <b class="command">utmp = no</b></p></dd><dt><span class="term"><a name="UTMPDIRECTORY"></a>utmp directory (G)</span></dt><dd><p>This parameter is only available if Samba has 
+	been configured and compiled with the option <b class="command">
+	--with-utmp</b>. It specifies a directory pathname that is
+	used to store the utmp or utmpx files (depending on the UNIX system) that
+	record user connections to a Samba server. See also the <a href="#UTMP">
+	<i class="parameter"><tt>utmp</tt></i></a> parameter. By default this is 
+	not set, meaning the system will use whatever utmp file the 
+	native system is set to use (usually 
+	<tt class="filename">/var/run/utmp</tt> on Linux).</p><p>Default: <span class="emphasis"><em>no utmp directory</em></span></p><p>Example: <b class="command">utmp directory = /var/run/utmp</b></p></dd><dt><span class="term"><a name="-VALID"></a>-valid (S)</span></dt><dd><p> This parameter indicates whether a share is 
+	valid and thus can be used. When this parameter is set to false, 
+	the share will be in no way visible nor accessible.
+	</p><p>
+	This option should not be 
+	used by regular users but might be of help to developers. 
+	Samba uses this option internally to mark shares as deleted.
+	</p><p>Default: <span class="emphasis"><em>True</em></span></p></dd><dt><span class="term"><a name="VALIDUSERS"></a>valid users (S)</span></dt><dd><p>This is a list of users that should be allowed 
     to login to this service. Names starting with '@', '+' and  '&amp;'
     are interpreted using the same rules as described in the 
     <i class="parameter"><tt>invalid users</tt></i> parameter.</p><p>If this is empty (the default) then any user can login. 
@@ -3018,14 +3051,7 @@ guest = *
     users</tt></i> list then access is denied for that user.</p><p>The current servicename is substituted for <i class="parameter"><tt>%S
     </tt></i>. This is useful in the [homes] section.</p><p>See also <a href="#INVALIDUSERS"><i class="parameter"><tt>invalid users
     </tt></i></a></p><p>Default: <span class="emphasis"><em>No valid users list (anyone can login)
-    </em></span></p><p>Example: <b class="command">valid users = greg, @pcusers</b></p></dd><dt><span class="term"><a name="-VALID"></a>-valid (S)</span></dt><dd><p> This parameter indicates whether a share is 
-	valid and thus can be used. When this parameter is set to false, 
-	the share will be in no way visible nor accessible.
-	</p><p>
-	This option should not be 
-	used by regular users but might be of help to developers. 
-	Samba uses this option internally to mark shares as deleted.
-	</p><p>Default: <span class="emphasis"><em>True</em></span></p></dd><dt><span class="term"><a name="VETOFILES"></a>veto files (S)</span></dt><dd><p>This is a list of files and directories that 
+    </em></span></p><p>Example: <b class="command">valid users = greg, @pcusers</b></p></dd><dt><span class="term"><a name="VETOFILES"></a>veto files (S)</span></dt><dd><p>This is a list of files and directories that 
 	are neither visible nor accessible.  Each entry in the list must 
 	be separated by a '/', which allows spaces to be included 
 	in the entry. '*' and '?' can be used to specify multiple files 
@@ -3065,14 +3091,14 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
 	client contention for files ending in <tt class="filename">.SEM</tt>. 
 	To cause Samba not to grant oplocks on these files you would use 
 	the line (either in the [global] section or in the section for 
-	the particular NetBench share :</p><p>Example: <b class="command">veto oplock files = /*.SEM/</b></p></dd><dt><span class="term"><a name="VFSOBJECTS"></a>vfs objects (S)</span></dt><dd><p>This parameter specifies the backend names which 
-	are used for Samba VFS I/O operations.  By default, normal 
-	disk I/O operations are used but these can be overloaded 
-	with one or more VFS objects. </p><p>Default: <span class="emphasis"><em>no value</em></span></p><p>Example: <b class="command">vfs objects = extd_audit recycle</b></p></dd><dt><span class="term"><a name="VFSOBJECT"></a>vfs object (S)</span></dt><dd><p>Synonym for
+	the particular NetBench share :</p><p>Example: <b class="command">veto oplock files = /*.SEM/</b></p></dd><dt><span class="term"><a name="VFSOBJECT"></a>vfs object (S)</span></dt><dd><p>Synonym for
 	<a href="#VFSOBJECTS">
 	<i class="parameter"><tt>vfs objects</tt></i>
 	</a>.
-	</p></dd><dt><span class="term"><a name="VOLUME"></a>volume (S)</span></dt><dd><p> This allows you to override the volume label 
+	</p></dd><dt><span class="term"><a name="VFSOBJECTS"></a>vfs objects (S)</span></dt><dd><p>This parameter specifies the backend names which 
+	are used for Samba VFS I/O operations.  By default, normal 
+	disk I/O operations are used but these can be overloaded 
+	with one or more VFS objects. </p><p>Default: <span class="emphasis"><em>no value</em></span></p><p>Example: <b class="command">vfs objects = extd_audit recycle</b></p></dd><dt><span class="term"><a name="VOLUME"></a>volume (S)</span></dt><dd><p> This allows you to override the volume label 
 	returned for a share. Useful for CDROMs with installation programs 
 	that insist on a particular volume label.</p><p>Default: <span class="emphasis"><em>the name of the share</em></span></p></dd><dt><span class="term"><a name="WIDELINKS"></a>wide links (S)</span></dt><dd><p>This parameter controls whether or not links 
 	in the UNIX file system may be followed by the server. Links 
@@ -3083,7 +3109,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
 	that Samba has to  do in order to perform the link checks.</p><p>Default: <b class="command">wide links = yes</b></p></dd><dt><span class="term"><a name="WINBINDCACHETIME"></a>winbind cache time (G)</span></dt><dd><p>This parameter specifies the number of 
 	seconds the <a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon will cache 
 	user and group information before querying a Windows NT server 
-	again.</p><p>Default: <b class="command">winbind cache type = 15</b></p></dd><dt><span class="term"><a name="WINBINDENABLELOCALACCOUNTS"></a>winbind enable local accounts (G)</span></dt><dd><p>This parameter controls whether or not winbindd 
+	again.</p><p>Default: <b class="command">winbind cache type = 300</b></p></dd><dt><span class="term"><a name="WINBINDENABLELOCALACCOUNTS"></a>winbind enable local accounts (G)</span></dt><dd><p>This parameter controls whether or not winbindd 
 	will act as a stand in replacement for the various account
 	management hooks in smb.conf (e.g. 'add user script').
 	If enabled, winbindd will support the creation of local 
@@ -3138,11 +3164,11 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
 	dynamic update of external name resolution databases such as 
 	dynamic DNS.</p><p>The wins hook parameter specifies the name of a script 
 	or executable that will be called as follows:</p><p><b class="command">wins_hook operation name nametype ttl IP_list</b></p><div class="itemizedlist"><ul type="disc"><li><p>The first argument is the operation and is
-			one  of &quot;add&quot;, &quot;delete&quot;, or
-			&quot;refresh&quot;. In most cases the operation
+			one  of "add", "delete", or
+			"refresh". In most cases the operation
 			can  be ignored as the rest of the parameters
 			provide sufficient  information. Note that
-			&quot;refresh&quot; may sometimes be called when
+			"refresh" may sometimes be called when
 			the  name has not previously been added, in that
 			case it should be treated  as an add.</p></li><li><p>The second argument is the NetBIOS name. If the 
 			name is not a legal name then the wins hook is not called. 
diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html
index 44585bc1f7..1c3cc5a2d3 100644
--- a/docs/htmldocs/smbcacls.1.html
+++ b/docs/htmldocs/smbcacls.1.html
@@ -10,10 +10,10 @@
 		only the ones specified on the command line.  All other ACLs are 
 		erased. Note that the ACL specified must contain at least a revision,
 		type, owner and group for the call to succeed. </p></dd><dt><span class="term">-U username</span></dt><dd><p>Specifies a username used to connect to the 
-		specified service.  The username may be of the form &quot;username&quot; in 
+		specified service.  The username may be of the form "username" in 
 		which case the user is prompted to enter in a password and the 
 		workgroup specified in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file is 
-		used, or &quot;username%password&quot;  or &quot;DOMAIN\username%password&quot; and the 
+		used, or "username%password"  or "DOMAIN\username%password" and the 
 		password and workgroup names are used as provided. </p></dd><dt><span class="term">-C name</span></dt><dd><p>The owner of a file or directory can be changed 
 		to the name given using the <i class="parameter"><tt>-C</tt></i> option.  
 		The name can be a sid in the form S-1-x-y-z or a name resolved 
@@ -48,9 +48,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796911"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2800108"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by 
 	either commas or newlines.  An ACL entry is one of the following: </p><pre class="programlisting"> 
diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html
index 233dee51d7..64968b5de7 100644
--- a/docs/htmldocs/smbmount.8.html
+++ b/docs/htmldocs/smbmount.8.html
@@ -1,14 +1,14 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmount.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbmount &#8212; mount an smbfs filesystem</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbmount</tt>  {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b class="command">smbmount</b> mounts a Linux SMB filesystem. It 
 	is usually invoked as <b class="command">mount.smbfs</b> by
 	the <a href="mount.8.html"><span class="citerefentry"><span class="refentrytitle">mount</span>(8)</span></a> command when using the 
-	&quot;-t smbfs&quot; option. This command only works in Linux, and the kernel must
+	"-t smbfs" option. This command only works in Linux, and the kernel must
 	support the smbfs filesystem. </p><p>Options to <b class="command">smbmount</b> are specified as a comma-separated
 	list of key=value pairs. It is possible to send options other
 	than those listed here, assuming that smbfs supports them. If
 	you get mount failures, check your kernel log for errors on
 	unknown options.</p><p><b class="command">smbmount</b> is a daemon. After mounting it keeps running until
 	the mounted smbfs is umounted. It will log things that happen
-	when in daemon mode using the &quot;machine name&quot; smbmount, so
+	when in daemon mode using the "machine name" smbmount, so
 	typically this output will end up in <tt class="filename">log.smbmount</tt>. The <b class="command">
 	smbmount</b> process may also be called mount.smbfs.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> <b class="command">smbmount</b> 
 	calls <a href="smbmnt.8.html"><span class="citerefentry"><span class="refentrytitle">smbmnt</span>(8)</span></a> to do the actual mount. You 
@@ -16,8 +16,8 @@
 	that it can be found. </p></div></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">username=&lt;arg&gt;</span></dt><dd><p>specifies the username to connect as. If
 		this is not given, then the environment variable <tt class="envar">
 		USER</tt> is used. This option can also take the
-		form &quot;user%password&quot; or &quot;user/workgroup&quot; or
-		&quot;user/workgroup%password&quot; to allow the password and workgroup
+		form "user%password" or "user/workgroup" or
+		"user/workgroup%password" to allow the password and workgroup
 		to be specified as part of the username.</p></dd><dt><span class="term">password=&lt;arg&gt;</span></dt><dd><p>specifies the SMB password. If this
 		option is not given then the environment variable
 		<tt class="envar">PASSWD</tt> is used. If it can find
diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html
index 700f986f30..feb899f946 100644
--- a/docs/htmldocs/smbpasswd.5.html
+++ b/docs/htmldocs/smbpasswd.5.html
@@ -19,8 +19,8 @@
 		Note that this password hash is regarded as weak as it is
 		vulnerable to dictionary attacks and if two users choose the 
 		same password this entry will be identical (i.e. the password 
-		is not &quot;salted&quot; as the UNIX password is). If the user has a 
-		null password this field will contain the characters &quot;NO PASSWORD&quot; 
+		is not "salted" as the UNIX password is). If the user has a 
+		null password this field will contain the characters "NO PASSWORD" 
 		as the start of the hex string. If the hex string is equal to 
 		32 'X' characters then the user's account is marked as 
 		<tt class="constant">disabled</tt> and the user will not be able to 
@@ -43,7 +43,7 @@
 		password and uses a much higher quality hashing algorithm. 
 		However, it is still the case that if two users choose the same 
 		password this entry will be identical (i.e. the password is 
-		not &quot;salted&quot; as the UNIX password is). </p><p><span class="emphasis"><em>WARNING !!</em></span>. Note that, due to 
+		not "salted" as the UNIX password is). </p><p><span class="emphasis"><em>WARNING !!</em></span>. Note that, due to 
 		the challenge-response nature of the SMB/CIFS authentication
 		protocol, anyone with a knowledge of this password hash will 
 		be able to impersonate the user on the network. For this
@@ -59,7 +59,7 @@
 		13 characters in length (including the '[' and ']' characters).
 		The contents of this field may be any of the following characters:
 		</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>U</em></span> - This means 
-			this is a &quot;User&quot; account, i.e. an ordinary user. Only User 
+			this is a "User" account, i.e. an ordinary user. Only User 
 			and Workstation Trust accounts are currently supported 
 			in the smbpasswd file. </p></li><li><p><span class="emphasis"><em>N</em></span> - This means the
 			account has no password (the passwords in the fields LANMAN 
@@ -68,12 +68,12 @@
 			null passwords</tt></i> parameter is set in the 
 			<a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> config file. </p></li><li><p><span class="emphasis"><em>D</em></span> - This means the account 
 			is disabled and no SMB/CIFS logins  will be allowed for this user. </p></li><li><p><span class="emphasis"><em>W</em></span> - This means this account 
-			is a &quot;Workstation Trust&quot; account. This kind of account is used 
+			is a "Workstation Trust" account. This kind of account is used 
 			in the Samba PDC code stream to allow Windows NT Workstations 
 			and Servers to join a Domain hosted by a Samba PDC. </p></li></ul></div><p>Other flags may be added as the code is extended in future.
 		The rest of this field space is filled in with spaces. </p></dd><dt><span class="term">Last Change Time</span></dt><dd><p>This field consists of the time the account was 
 		last modified. It consists of the characters 'LCT-' (standing for 
-		&quot;Last Change Time&quot;) followed by a numeric encoding of the UNIX time 
+		"Last Change Time") followed by a numeric encoding of the UNIX time 
 		in seconds since the epoch (1970) that the last change was made. 
 		</p></dd></dl></div><p>All other colon separated fields are ignored at this time.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of 
 	the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a>, <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>, and
diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html
index 73feaecf14..7c98e4b080 100644
--- a/docs/htmldocs/smbpasswd.8.html
+++ b/docs/htmldocs/smbpasswd.8.html
@@ -16,7 +16,7 @@
 	for their new password twice, to ensure that the new password
 	was typed correctly. No passwords will be echoed on the screen 
 	whilst being typed. If you have a blank SMB password (specified by 
-	the string &quot;NO PASSWORD&quot; in the smbpasswd file) then just press 
+	the string "NO PASSWORD" in the smbpasswd file) then just press 
 	the &lt;Enter&gt; key when asked for your old password. </p><p>smbpasswd can also be used by a normal user to change their
 	SMB password on remote machines, such as Windows NT Primary Domain 
 	Controllers.   See the (<i class="parameter"><tt>-r</tt></i>) and <i class="parameter"><tt>-U</tt></i> options 
@@ -64,10 +64,10 @@
 		HUGE amounts of log data, most of which is extremely cryptic. 
 		</p></dd><dt><span class="term">-n</span></dt><dd><p>This option specifies that the username following 
 		should have their password set to null (i.e. a blank password) in 
-		the local smbpasswd file. This is done by writing the string &quot;NO 
-		PASSWORD&quot; as the first part of the first password stored in the 
+		the local smbpasswd file. This is done by writing the string "NO 
+		PASSWORD" as the first part of the first password stored in the 
 		smbpasswd file. </p><p>Note that to allow users to logon to a Samba server once 
-		the password has been set to &quot;NO PASSWORD&quot; in the smbpasswd
+		the password has been set to "NO PASSWORD" in the smbpasswd
 		file the administrator must set the following parameter in the [global]
 		section of the <tt class="filename">smb.conf</tt> file : </p><p><b class="command">null passwords = yes</b></p><p>This option is only available when running smbpasswd as 
 		root.</p></dd><dt><span class="term">-r remote machine name</span></dt><dd><p>This option allows a user to specify what machine 
@@ -89,7 +89,7 @@
 		a real password database so it is not possible to change passwords 
 		specifying a Win95/98  machine as remote machine target. </p></dd><dt><span class="term">-R name resolve order</span></dt><dd><p>This option allows the user of smbpasswd to determine
 		what name resolution services to use when looking up the NetBIOS
-		name of the host being connected to. </p><p>The options are :&quot;lmhosts&quot;, &quot;host&quot;, &quot;wins&quot; and &quot;bcast&quot;. They
+		name of the host being connected to. </p><p>The options are :"lmhosts", "host", "wins" and "bcast". They
 		 cause names to be resolved as follows: </p><div class="itemizedlist"><ul type="disc"><li><p><tt class="constant">lmhosts</tt>: Lookup an IP 
             address in the Samba lmhosts file. If the line in lmhosts has 
             no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html"><span class="citerefentry"><span class="refentrytitle">lmhosts</span>(5)</span></a> for details) then
@@ -127,7 +127,7 @@
 		has been configured to use the experimental
 		<b class="command">--with-ldapsam</b> option. The <i class="parameter"><tt>-w</tt></i> 
 		switch is used to specify the password to be used with the 
-		<a class="indexterm" name="id2797339"></a><i class="parameter"><tt>ldap admin dn</tt></i>.  Note that the password is stored in
+		<a class="indexterm" name="id2800537"></a><a href="#"><i class="parameter"><tt>ldap admin dn</tt></i></a>.  Note that the password is stored in
 		the <tt class="filename">secrets.tdb</tt> and is keyed off 
 		of the admin's DN.  This means that if the value of <i class="parameter"><tt>ldap
 		admin dn</tt></i> ever changes, the password will need to be 
@@ -147,7 +147,7 @@
 	smbd</b> running on the local machine by specifying either <i class="parameter"><tt>allow
 	hosts</tt></i> or <i class="parameter"><tt>deny hosts</tt></i> entry in 
 	the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file and neglecting to 
-	allow &quot;localhost&quot; access to the smbd. </p><p>In addition, the smbpasswd command is only useful if Samba
+	allow "localhost" access to the smbd. </p><p>In addition, the smbpasswd command is only useful if Samba
 	has been set up to use encrypted passwords. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a>, <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities 
 	were created by Andrew Tridgell. Samba is now developed
 	by the Samba Team as an Open Source project similar 
diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html
index 9cce85da75..d1360d849d 100644
--- a/docs/htmldocs/smbsh.1.html
+++ b/docs/htmldocs/smbsh.1.html
@@ -33,7 +33,7 @@ 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>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2802215"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2796897"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-R &lt;name resolve order&gt;</span></dt><dd><p>This option is used to determine what naming 
 services and in what order to resolve 
 host names to IP addresses. The option takes a space-separated 
@@ -66,9 +66,9 @@ resolution methods as it depends on the target host
 being on a locally connected subnet.
 </p></li></ul></div><p>If this parameter is not set then the name resolve order 
 defined in the <tt class="filename">smb.conf</tt> file parameter  
-(<a class="indexterm" name="id2796281"></a><i class="parameter"><tt>name resolve order</tt></i>) will be used.
+(<a class="indexterm" name="id2797172"></a><a href="#"><i class="parameter"><tt>name resolve order</tt></i></a>) will be used.
 </p><p>The default order is lmhosts, host, wins, bcast. Without 
-this parameter or any entry in the <a class="indexterm" name="id2796300"></a><i class="parameter"><tt>name resolve order</tt></i> parameter of the <tt class="filename">smb.conf</tt> file, the name 
+this parameter or any entry in the <a class="indexterm" name="id2797198"></a><a href="#"><i class="parameter"><tt>name resolve order</tt></i></a> parameter of the <tt class="filename">smb.conf</tt> file, the name 
 resolution methods will be attempted in this order. </p></dd><dt><span class="term">-L libdir</span></dt><dd><p>This parameter specifies the location of the 
 		shared libraries used by <b class="command">smbsh</b>. The default
 		value is specified at compile time.
diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html
index 30058d1860..95aabf1bc3 100644
--- a/docs/htmldocs/smbtar.1.html
+++ b/docs/htmldocs/smbtar.1.html
@@ -2,7 +2,7 @@
 	directly to UNIX tape drives</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbtar</tt>  [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a> suite.</p><p><b class="command">smbtar</b> is a very small shell script on top 
 	of <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> which dumps SMB shares directly to tape.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s server</span></dt><dd><p>The SMB/CIFS server that the share resides 
 		upon.</p></dd><dt><span class="term">-x service</span></dt><dd><p>The share name on the server to connect to. 
-		The default is &quot;backup&quot;.</p></dd><dt><span class="term">-X</span></dt><dd><p>Exclude mode. Exclude filenames... from tar 
+		The default is "backup".</p></dd><dt><span class="term">-X</span></dt><dd><p>Exclude mode. Exclude filenames... from tar 
 		create or restore. </p></dd><dt><span class="term">-d directory</span></dt><dd><p>Change to initial <i class="parameter"><tt>directory
 		</tt></i> before restoring / backing up files. </p></dd><dt><span class="term">-v</span></dt><dd><p>Verbose mode.</p></dd><dt><span class="term">-p password</span></dt><dd><p>The password to use to access a share. 
 		Default: none </p></dd><dt><span class="term">-u user</span></dt><dd><p>The user id to connect as. Default: 
diff --git a/docs/htmldocs/smbtree.1.html b/docs/htmldocs/smbtree.1.html
index 26120161d5..cc683838dd 100644
--- a/docs/htmldocs/smbtree.1.html
+++ b/docs/htmldocs/smbtree.1.html
@@ -1,6 +1,6 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtree</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtree.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbtree &#8212; A text based smb network browser
 	</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbtree</tt>  [-b] [-D] [-S]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html"><span class="citerefentry"><span class="refentrytitle">Samba</span>(7)</span></a> suite.</p><p><b class="command">smbtree</b> is a smb browser program 
-	in text mode. It is similar to the &quot;Network Neighborhood&quot; found 
+	in text mode. It is similar to the "Network Neighborhood" found 
 	on Windows computers. It prints a tree with all 
 	the known domains, the servers in those domains and 
 	the shares on the servers.
@@ -31,9 +31,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796642"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2799845"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-N</span></dt><dd><p>If specified, this parameter suppresses the normal
 password prompt from the client to the user. This is useful when
diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html
index 33e595e0c3..a7f2eaaf5b 100644
--- a/docs/htmldocs/swat.8.html
+++ b/docs/htmldocs/swat.8.html
@@ -33,9 +33,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796724"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2796899"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
 </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>INSTALLATION</h2><p>Swat is included as binary package with most distributions. The 
@@ -60,7 +60,7 @@ never removed by the client.
 		and <tt class="filename">/etc/inetd.conf</tt> you need to send a 
 		HUP signal to inetd. To do this use <b class="command">kill -1 PID
 		</b> where PID is the process ID of the inetd daemon. </p></div></div><div class="refsect1" lang="en"><h2>LAUNCHING</h2><p>To launch SWAT just run your favorite web browser and 
-	point it at &quot;http://localhost:901/&quot;.</p><p>Note that you can attach to SWAT from any IP connected 
+	point it at "http://localhost:901/".</p><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 class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt class="filename">/etc/inetd.conf</tt></span></dt><dd><p>This file must contain suitable startup 
diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html
index 561b3deb45..2cfbfad283 100644
--- a/docs/htmldocs/vfstest.1.html
+++ b/docs/htmldocs/vfstest.1.html
@@ -28,9 +28,9 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796651"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2799859"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt class="constant">&quot;.client&quot;</tt> will be appended. The log file is
+<tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
 </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><p><span class="emphasis"><em>VFS COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><b class="command">load &lt;module.so&gt;</b> - Load specified VFS module </p></li><li><p><b class="command">populate &lt;char&gt; &lt;size&gt;</b> - Populate a data buffer with the specified data
 		</p></li><li><p><b class="command">showdata [&lt;offset&gt; &lt;len&gt;]</b> - Show data currently in data buffer
diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html
index 656a482b91..7b2d6e0261 100644
--- a/docs/htmldocs/winbindd.8.html
+++ b/docs/htmldocs/winbindd.8.html
@@ -69,7 +69,7 @@ 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>Note that specifying this parameter here will 
-override the <a class="indexterm" name="id2796344"></a><i class="parameter"><tt>log level</tt></i> parameter
+override the <a class="indexterm" name="id2800127"></a><a href="#"><i class="parameter"><tt>log level</tt></i></a> parameter
 in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
 <tt class="constant">".client"</tt> will be appended. The log file is
 never removed by the client.
@@ -108,15 +108,15 @@ never removed by the client.
 	and group rids. </p></div><div class="refsect1" lang="en"><h2>CONFIGURATION</h2><p>Configuration of the <b class="command">winbindd</b> daemon 
 	is done through configuration parameters in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.  All parameters should be specified in the 
 	[global] section of smb.conf. </p><div class="itemizedlist"><ul type="disc"><li><p>
-		<a class="indexterm" name="id2798898"></a><i class="parameter"><tt>winbind separator</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2798916"></a><i class="parameter"><tt>idmap uid</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2798934"></a><i class="parameter"><tt>idmap gid</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2798952"></a><i class="parameter"><tt>winbind cache time</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2798970"></a><i class="parameter"><tt>winbind enum users</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2798988"></a><i class="parameter"><tt>winbind enum groups</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2799006"></a><i class="parameter"><tt>template homedir</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2799025"></a><i class="parameter"><tt>template shell</tt></i></p></li><li><p>
-		<a class="indexterm" name="id2799043"></a><i class="parameter"><tt>winbind use default domain</tt></i></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXAMPLE SETUP</h2><p>To setup winbindd for user and group lookups plus 
+		<a class="indexterm" name="id2800484"></a><a href="#"><i class="parameter"><tt>winbind separator</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800509"></a><a href="#"><i class="parameter"><tt>idmap uid</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800532"></a><a href="#"><i class="parameter"><tt>idmap gid</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800556"></a><a href="#"><i class="parameter"><tt>winbind cache time</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800581"></a><a href="#"><i class="parameter"><tt>winbind enum users</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800606"></a><a href="#"><i class="parameter"><tt>winbind enum groups</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800630"></a><a href="#"><i class="parameter"><tt>template homedir</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800655"></a><a href="#"><i class="parameter"><tt>template shell</tt></i></a></p></li><li><p>
+		<a class="indexterm" name="id2800679"></a><a href="#"><i class="parameter"><tt>winbind use default domain</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXAMPLE SETUP</h2><p>To setup winbindd for user and group lookups plus 
 	authentication from a domain controller use something like the 
 	following setup. This was tested on a RedHat 6.2 Linux box. </p><p>In <tt class="filename">/etc/nsswitch.conf</tt> put the 
 	following:
diff --git a/docs/manpages/net.8 b/docs/manpages/net.8
index 3f3f9340be..70a6090792 100644
--- a/docs/manpages/net.8
+++ b/docs/manpages/net.8
@@ -109,6 +109,11 @@ Note that specifying this parameter here will override the \fIlog level\fR param
 
 .SH "COMMANDS"
 
+.SS "CHANGESECRETPW"
+
+.PP
+This command allows the Samba machine account password to be set from an external application to a machine account password that has already been stored in Active Directory\&. DO NOT USE this command unless you know exactly what you are doing\&. The use of this command requires that the force flag (-f) be used also\&. There will be NO command prompt\&. Whatever information is piped into stdin, either by typing at the command line or otherwise, will be stored as the literal machine password\&. Do NOT use this without care and attention as it will overwrite a legitimate machine password without warning\&. YOU HAVE BEEN WARNED\&.
+
 .SS "TIME"
 
 .PP
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index 6379e942ec..55fdc8be44 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -508,6 +508,18 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
+\fIclient plaintext auth\fR
+
+.TP
+\(bu
+\fIclient schannel\fR
+
+.TP
+\(bu
+\fIclient signing\fR
+
+.TP
+\(bu
 \fIclient use spnego\fR
 
 .TP
@@ -540,11 +552,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIdefault service\fR
+\fIdefault\fR
 
 .TP
 \(bu
-\fIdefault\fR
+\fIdefault service\fR
 
 .TP
 \(bu
@@ -672,6 +684,10 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
+\fIkernel change notify\fR
+
+.TP
+\(bu
 \fIkernel oplocks\fR
 
 .TP
@@ -696,6 +712,14 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
+\fIldap group suffix\fR
+
+.TP
+\(bu
+\fIldap idmap suffix\fR
+
+.TP
+\(bu
 \fIldap machine suffix\fR
 
 .TP
@@ -720,10 +744,6 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIldap trust ids\fR
-
-.TP
-\(bu
 \fIldap user suffix\fR
 
 .TP
@@ -744,11 +764,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIlock directory\fR
+\fIlock dir\fR
 
 .TP
 \(bu
-\fIlock dir\fR
+\fIlock directory\fR
 
 .TP
 \(bu
@@ -936,11 +956,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIpasswd chat debug\fR
+\fIpasswd chat\fR
 
 .TP
 \(bu
-\fIpasswd chat\fR
+\fIpasswd chat debug\fR
 
 .TP
 \(bu
@@ -968,11 +988,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIpreload modules\fR
+\fIpreload\fR
 
 .TP
 \(bu
-\fIpreload\fR
+\fIpreload modules\fR
 
 .TP
 \(bu
@@ -1016,7 +1036,7 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIroot directory\fR
+\fIroot\fR
 
 .TP
 \(bu
@@ -1024,7 +1044,7 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIroot\fR
+\fIroot directory\fR
 
 .TP
 \(bu
@@ -1036,6 +1056,10 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
+\fIserver signing\fR
+
+.TP
+\(bu
 \fIserver string\fR
 
 .TP
@@ -1084,11 +1108,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIsyslog only\fR
+\fIsyslog\fR
 
 .TP
 \(bu
-\fIsyslog\fR
+\fIsyslog only\fR
 
 .TP
 \(bu
@@ -1152,11 +1176,11 @@ Here is a list of all global parameters\&. See the section of each parameter for
 
 .TP
 \(bu
-\fIutmp directory\fR
+\fIutmp\fR
 
 .TP
 \(bu
-\fIutmp\fR
+\fIutmp directory\fR
 
 .TP
 \(bu
@@ -1235,6 +1259,10 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP 3
 \(bu
+\fIacl compatibility\fR
+
+.TP
+\(bu
 \fIadmin users\fR
 
 .TP
@@ -1311,19 +1339,19 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIdirectory mask\fR
+\fIdirectory\fR
 
 .TP
 \(bu
-\fIdirectory mode\fR
+\fIdirectory mask\fR
 
 .TP
 \(bu
-\fIdirectory security mask\fR
+\fIdirectory mode\fR
 
 .TP
 \(bu
-\fIdirectory\fR
+\fIdirectory security mask\fR
 
 .TP
 \(bu
@@ -1563,11 +1591,11 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIpreexec close\fR
+\fIpreexec\fR
 
 .TP
 \(bu
-\fIpreexec\fR
+\fIpreexec close\fR
 
 .TP
 \(bu
@@ -1587,15 +1615,15 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIprinter admin\fR
+\fIprinter\fR
 
 .TP
 \(bu
-\fIprinter name\fR
+\fIprinter admin\fR
 
 .TP
 \(bu
-\fIprinter\fR
+\fIprinter name\fR
 
 .TP
 \(bu
@@ -1635,11 +1663,11 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIroot preexec close\fR
+\fIroot preexec\fR
 
 .TP
 \(bu
-\fIroot preexec\fR
+\fIroot preexec close\fR
 
 .TP
 \(bu
@@ -1679,15 +1707,15 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIusername\fR
+\fIuser\fR
 
 .TP
 \(bu
-\fIusers\fR
+\fIusername\fR
 
 .TP
 \(bu
-\fIuser\fR
+\fIusers\fR
 
 .TP
 \(bu
@@ -1695,11 +1723,11 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIvalid users\fR
+\fI-valid\fR
 
 .TP
 \(bu
-\fI-valid\fR
+\fIvalid users\fR
 
 .TP
 \(bu
@@ -1711,11 +1739,11 @@ Here is a list of all service parameters\&. See the section on each parameter fo
 
 .TP
 \(bu
-\fIvfs objects\fR
+\fIvfs object\fR
 
 .TP
 \(bu
-\fIvfs object\fR
+\fIvfs objects\fR
 
 .TP
 \(bu
@@ -1764,6 +1792,17 @@ Example: \fBabort shutdown script = /sbin/shutdown -c\fR
 
 
 .TP
+acl compatibility (S)
+This parameter specifies what OS ACL semantics should be compatible with\&. Possible values are \fBwinnt\fR for Windows NT 4, \fBwin2k\fR for Windows 2000 and above and \fBauto\fR\&. If you specify \fBauto\fR, the value for this parameter will be based upon the version of the client\&. There should be no reason to change this parameter from the default\&.
+
+
+Default: \fBacl compatibility = Auto\fR
+
+
+Example: \fBacl compatibility = win2k\fR
+
+
+.TP
 add group script (G)
 This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd\fR(8) when a new group is requested\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&. The script is free to create a group with an arbitrary name to circumvent unix group name restrictions\&. In that case the script must print the numeric gid of the created group on stdout\&.
 
@@ -2146,6 +2185,36 @@ Default : \fBclient ntlmv2 auth = no\fR
 
 
 .TP
+client plaintext auth (G)
+Specifies whether a client should send a plaintext password if the server does not support encrypted passwords\&.
+
+
+Default: \fBclient plaintext auth = yes\fR
+
+
+.TP
+client schannel (G)
+This controls whether the client offers or even demands the use of the netlogon schannel\&. \fIclient schannel = no\fR does not offer the schannel, \fIserver schannel = auto\fR offers the schannel but does not enforce it, and \fIserver schannel = yes\fR denies access if the server is not able to speak netlogon schannel\&.
+
+
+Default: \fBclient schannel = auto\fR
+
+
+Example: \fBclient schannel = yes\fR
+
+
+.TP
+client signing (G)
+This controls whether the client offers or requires the server it talks to to use SMB signing\&. Possible values are \fBauto\fR, \fBmandatory\fR and \fBdisabled\fR\&.
+
+
+When set to auto, SMB signing is offered, but not enforced\&. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either\&.
+
+
+Default: \fBclient signing = auto\fR
+
+
+.TP
 client use spnego (G)
 This variable controls controls whether samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 servers to agree upon an authentication mechanism\&. SPNEGO client support for SMB Signing is currently broken, so you might want to turn this option off when operating with Windows 2003 domain controllers in particular\&.
 
@@ -2319,6 +2388,11 @@ Default: \fBdebug uid = no\fR
 
 
 .TP
+default (G)
+A synonym for \fI default service\fR\&.
+
+
+.TP
 default case (S)
 See the section on NAME MANGLING\&. Also note the \fIshort preserve case\fR parameter\&.
 
@@ -2374,11 +2448,6 @@ Example:
 
 
 .TP
-default (G)
-A synonym for \fI default service\fR\&.
-
-
-.TP
 delete group script (G)
 This is the full pathname to a script that will be run \fBAS ROOT\fR \fBsmbd\fR(8) when a group is requested to be deleted\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&.
 
@@ -2535,6 +2604,11 @@ Note that you may have to replace the command names with full path names on some
 
 
 .TP
+directory (S)
+Synonym for \fIpath\fR\&.
+
+
+.TP
 directory mask (S)
 This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&.
 
@@ -2595,11 +2669,6 @@ Example: \fBdirectory security mask = 0700\fR
 
 
 .TP
-directory (S)
-Synonym for \fIpath\fR\&.
-
-
-.TP
 disable netbios (G)
 Enabling this parameter will disable netbios support in Samba\&. Netbios is the only available form of browsing in all windows versions except for 2000 and XP\&.
 
@@ -3270,7 +3339,7 @@ The purpose of the idmap backend parameter is to allow idmap to NOT use the loca
 Default: \fBidmap backend = <empty string>\fR
 
 
-Example: \fBidmap backend = ldapsam://ldapslave.example.com\fR
+Example: \fBidmap backend = ldap:ldap://ldapslave.example.com\fR
 
 
 .TP
@@ -3418,6 +3487,17 @@ Example: \fBkeepalive = 600\fR
 
 
 .TP
+kernel change notify (G)
+This parameter specifies whether Samba should ask the kernel for change notifications in directories so that SMB clients can refresh whenever the data on the server changes\&.
+
+
+This parameter is only usd when your kernel supports change notification to user programs, using the F_NOTIFY fcntl\&.
+
+
+Default: \fBYes\fR
+
+
+.TP
 kernel oplocks (G)
 For UNIXes that support kernel based \fIoplocks\fR (currently only IRIX and the Linux 2\&.4 kernel), this parameter allows the use of them to be turned on or off\&.
 
@@ -3481,6 +3561,28 @@ Default: \fBldap filter = (&(uid=%u)(objectclass=sambaAccount))\fR
 
 
 .TP
+ldap group suffix (G)
+This parameters specifies the suffix that is used for groups when these are added to the LDAP directory\&. If this parameter is unset, the value of \fIldap suffix\fR will be used instead\&.
+
+
+Default: \fBnone\fR
+
+
+Example: \fBdc=samba,ou=Groups\fR
+
+
+.TP
+ldap idmap suffix (G)
+This parameters specifies the suffix that is used when storing idmap mappings\&. If this parameter is unset, the value of \fIldap suffix\fR will be used instead\&.
+
+
+Default: \fBnone\fR
+
+
+Example: \fBdc=samba,ou=Idmap\fR
+
+
+.TP
 ldap machine suffix (G)
 It specifies where machines should be added to the ldap tree\&.
 
@@ -3559,19 +3661,8 @@ Default: \fBnone\fR
 
 
 .TP
-ldap trust ids (G)
-Normally, Samba validates each entry in the LDAP server against getpwnam()\&. This allows LDAP to be used for Samba with the unix system using NIS (for example) and also ensures that Samba does not present accounts that do not otherwise exist\&.
-
-
-This option is used to disable this functionality, and instead to rely on the presence of the appropriate attributes in LDAP directly, which can result in a significant performance boost in some situations\&. Setting this option to yes effectivly assumes that the local machine is running \fBnss_ldap\fR against the same LDAP server\&.
-
-
-Default: \fBldap trust ids = No\fR
-
-
-.TP
 ldap user suffix (G)
-It specifies where users are added to the tree\&.
+This parameter specifies where users are added to the tree\&. If this parameter is not specified, the value from \fBldap suffix\fR\&.
 
 
 Default: \fBnone\fR
@@ -3651,6 +3742,11 @@ Default: \fBlocal master = yes\fR
 
 
 .TP
+lock dir (G)
+Synonym for \fI lock directory\fR\&.
+
+
+.TP
 lock directory (G)
 This option specifies the directory where lock files will be placed\&. The lock files are used to implement the \fImax connections\fR option\&.
 
@@ -3662,11 +3758,6 @@ Example: \fBlock directory = /var/run/samba/locks\fR
 
 
 .TP
-lock dir (G)
-Synonym for \fI lock directory\fR\&.
-
-
-.TP
 locking (S)
 This controls whether or not locking will be performed by the server in response to lock requests from the client\&.
 
@@ -4797,17 +4888,6 @@ Example: \fBpassdb backend = mysql:my_plugin_args tdbsam\fR
 
 
 .TP
-passwd chat debug (G)
-This boolean specifies if the passwd chat script parameter is run in \fBdebug\fR mode\&. In this mode the strings passed to and received from the passwd chat are printed in the \fBsmbd\fR(8) log with a \fIdebug level\fR of 100\&. This is a dangerous option as it will allow plaintext passwords to be seen in the \fBsmbd\fR log\&. It is available to help Samba admins debug their \fIpasswd chat\fR scripts when calling the \fIpasswd program\fR and should be turned off after this has been done\&. This option has no effect if the \fIpam password change\fR paramter is set\&. This parameter is off by default\&.
-
-
-See also \fIpasswd chat\fR , \fIpam password change\fR , \fIpasswd program\fR \&.
-
-
-Default: \fBpasswd chat debug = no\fR
-
-
-.TP
 passwd chat (G)
 This string controls the \fB"chat"\fR conversation that takes places between \fBsmbd\fR(8) and the local password changing program to change the user's password\&. The string describes a sequence of response-receive pairs that \fBsmbd\fR(8) uses to determine what to send to the \fIpasswd program\fR and what to expect back\&. If the expected output is not received then the password is not changed\&.
 
@@ -4837,6 +4917,17 @@ Example: \fBpasswd chat = "*Enter OLD password*" %o\\n "*Enter NEW password*" %n
 
 
 .TP
+passwd chat debug (G)
+This boolean specifies if the passwd chat script parameter is run in \fBdebug\fR mode\&. In this mode the strings passed to and received from the passwd chat are printed in the \fBsmbd\fR(8) log with a \fIdebug level\fR of 100\&. This is a dangerous option as it will allow plaintext passwords to be seen in the \fBsmbd\fR log\&. It is available to help Samba admins debug their \fIpasswd chat\fR scripts when calling the \fIpasswd program\fR and should be turned off after this has been done\&. This option has no effect if the \fIpam password change\fR paramter is set\&. This parameter is off by default\&.
+
+
+See also \fIpasswd chat\fR , \fIpam password change\fR , \fIpasswd program\fR \&.
+
+
+Default: \fBpasswd chat debug = no\fR
+
+
+.TP
 passwd program (G)
 The name of a program that can be used to set UNIX user passwords\&. Any occurrences of \fI%u\fR will be replaced with the user name\&. The user name is checked for existence before calling the password changing program\&.
 
@@ -5007,14 +5098,6 @@ Example: \fBpostexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log
 
 
 .TP
-preexec close (S)
-This boolean option controls whether a non-zero return code from \fIpreexec \fR should close the service being connected to\&.
-
-
-Default: \fBpreexec close = no\fR
-
-
-.TP
 preexec (S)
 This option specifies a command to be run whenever the service is connected to\&. It takes the usual substitutions\&.
 
@@ -5038,6 +5121,14 @@ Example: \fBpreexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log\fR
 
 
 .TP
+preexec close (S)
+This boolean option controls whether a non-zero return code from \fIpreexec \fR should close the service being connected to\&.
+
+
+Default: \fBpreexec close = no\fR
+
+
+.TP
 prefered master (G)
 Synonym for \fI preferred master\fR for people who cannot spell :-)\&.
 
@@ -5060,31 +5151,28 @@ Default: \fBpreferred master = auto\fR
 
 
 .TP
-preload modules (G)
-This is a list of paths to modules that should be loaded into smbd before a client connects\&. This improves the speed of smbd when reacting to new connections somewhat\&.
+preload (G)
+This is a list of services that you want to be automatically added to the browse lists\&. This is most useful for homes and printers services that would otherwise not be visible\&.
 
 
-It is recommended to only use this option on heavy-performance servers\&.
+Note that if you just want all printers in your printcap file loaded then the \fIload printers\fR option is easier\&.
 
 
-Default: \fBpreload modules = \fR
+Default: \fBno preloaded services\fR
 
 
-Example: \fBpreload modules = /usr/lib/samba/passdb/mysql.so+++ \fR
+Example: \fBpreload = fred lp colorlp\fR
 
 
 .TP
-preload (G)
-This is a list of services that you want to be automatically added to the browse lists\&. This is most useful for homes and printers services that would otherwise not be visible\&.
-
-
-Note that if you just want all printers in your printcap file loaded then the \fIload printers\fR option is easier\&.
+preload modules (G)
+This is a list of paths to modules that should be loaded into smbd before a client connects\&. This improves the speed of smbd when reacting to new connections somewhat\&.
 
 
-Default: \fBno preloaded services\fR
+Default: \fBpreload modules = \fR
 
 
-Example: \fBpreload = fred lp colorlp\fR
+Example: \fBpreload modules = /usr/lib/samba/passdb/mysql.so+++ \fR
 
 
 .TP
@@ -5110,6 +5198,11 @@ Default: \fBprintable = no\fR
 
 
 .TP
+printcap (G)
+Synonym for \fI printcap name\fR\&.
+
+
+.TP
 printcap name (S)
 This parameter may be used to override the compiled-in default printcap name used by the server (usually \fI /etc/printcap\fR)\&. See the discussion of the [printers] section above for reasons why you might want to do this\&.
 
@@ -5145,11 +5238,6 @@ Example: \fBprintcap name = /etc/myprintcap\fR
 
 
 .TP
-printcap (G)
-Synonym for \fI printcap name\fR\&.
-
-
-.TP
 print command (S)
 After a print job has finished spooling to a service, this command will be used via a \fBsystem()\fR call to process the spool file\&. Typically the command specified will submit the spool file to the host's printing subsystem, but there is no requirement that this be the case\&. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\&.
 
@@ -5218,6 +5306,11 @@ Example: \fBprint command = /usr/local/samba/bin/myprintscript %p %s\fR
 
 
 .TP
+printer (S)
+Synonym for \fI printer name\fR\&.
+
+
+.TP
 printer admin (S)
 This is a list of users that can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation)\&. Note that the root user always has admin rights\&.
 
@@ -5243,11 +5336,6 @@ Example: \fBprinter name = laserwriter\fR
 
 
 .TP
-printer (S)
-Synonym for \fI printer name\fR\&.
-
-
-.TP
 printing (S)
 This parameters controls how printer status information is interpreted on your system\&. It also affects the default values for the \fIprint command\fR, \fIlpq command\fR, \fIlppause command \fR, \fIlpresume command\fR, and \fIlprm command\fR if specified in the [global] section\&.
 
@@ -5491,6 +5579,16 @@ Default: \fBrestrict anonymous = 0\fR
 
 
 .TP
+root (G)
+Synonym for \fIroot directory"\fR\&.
+
+
+.TP
+root dir (G)
+Synonym for \fIroot directory"\fR\&.
+
+
+.TP
 root directory (G)
 The server will \fBchroot()\fR (i\&.e\&. Change its root directory) to this directory on startup\&. This is not strictly necessary for secure operation\&. Even without it the server will deny access to files not in one of the service entries\&. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use "\&.\&." in file names to access other directories (depending on the setting of the \fIwide links\fR parameter)\&.
 
@@ -5505,11 +5603,6 @@ Example: \fBroot directory = /homes/smb\fR
 
 
 .TP
-root dir (G)
-Synonym for \fIroot directory"\fR\&.
-
-
-.TP
 root postexec (S)
 This is the same as the \fIpostexec\fR parameter except that the command is run as root\&. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed\&.
 
@@ -5521,17 +5614,6 @@ Default: \fBroot postexec = <empty string>\fR
 
 
 .TP
-root preexec close (S)
-This is the same as the \fIpreexec close \fR parameter except that the command is run as root\&.
-
-
-See also \fI preexec\fR and \fIpreexec close\fR\&.
-
-
-Default: \fBroot preexec close = no\fR
-
-
-.TP
 root preexec (S)
 This is the same as the \fIpreexec\fR parameter except that the command is run as root\&. This is useful for mounting filesystems (such as CDROMs) when a connection is opened\&.
 
@@ -5543,31 +5625,14 @@ Default: \fBroot preexec = <empty string>\fR
 
 
 .TP
-root (G)
-Synonym for \fIroot directory"\fR\&.
-
-
-.TP
-security mask (S)
-This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&.
-
-
-This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&.
-
-
-If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file\&.
-
-
-\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set to \fB0777\fR\&.
-
-
-See also the \fIforce directory security mode\fR, \fIdirectory security mask\fR, \fIforce security mode\fR parameters\&.
+root preexec close (S)
+This is the same as the \fIpreexec close \fR parameter except that the command is run as root\&.
 
 
-Default: \fBsecurity mask = 0777\fR
+See also \fI preexec\fR and \fIpreexec close\fR\&.
 
 
-Example: \fBsecurity mask = 0770\fR
+Default: \fBroot preexec close = no\fR
 
 
 .TP
@@ -5715,6 +5780,29 @@ Example: \fBsecurity = DOMAIN\fR
 
 
 .TP
+security mask (S)
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&.
+
+
+This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&.
+
+
+If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file\&.
+
+
+\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set to \fB0777\fR\&.
+
+
+See also the \fIforce directory security mode\fR, \fIdirectory security mask\fR, \fIforce security mode\fR parameters\&.
+
+
+Default: \fBsecurity mask = 0777\fR
+
+
+Example: \fBsecurity mask = 0770\fR
+
+
+.TP
 server schannel (G)
 This controls whether the server offers or even demands the use of the netlogon schannel\&. \fIserver schannel = no\fR does not offer the schannel, \fIserver schannel = auto\fR offers the schannel but does not enforce it, and \fIserver schannel = yes\fR denies access if the client is not able to speak netlogon schannel\&. This is only the case for Windows NT4 before SP4\&.
 
@@ -5729,6 +5817,17 @@ Example: \fBserver schannel = yes\fR
 
 
 .TP
+server signing (G)
+This controls whether the server offers or requires the client it talks to to use SMB signing\&. Possible values are \fBauto\fR, \fBmandatory\fR and \fBdisabled\fR\&.
+
+
+When set to auto, SMB signing is offered, but not enforced\&. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either\&.
+
+
+Default: \fBclient signing = False\fR
+
+
+.TP
 server string (G)
 This controls what string will show up in the printer comment box in print manager and next to the IPC connection in \fBnet view\fR\&. It can be any string that you wish to show to your users\&.
 
@@ -6093,14 +6192,6 @@ Default: \fBsync always = no\fR
 
 
 .TP
-syslog only (G)
-If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files\&.
-
-
-Default: \fBsyslog only = no\fR
-
-
-.TP
 syslog (G)
 This parameter maps how Samba debug messages are logged onto the system syslog logging levels\&. Samba debug level zero maps onto syslog \fBLOG_ERR\fR, debug level one maps onto \fBLOG_WARNING\fR, debug level two maps onto \fBLOG_NOTICE\fR, debug level three maps onto LOG_INFO\&. All higher levels are mapped to \fB LOG_DEBUG\fR\&.
 
@@ -6112,6 +6203,14 @@ Default: \fBsyslog = 1\fR
 
 
 .TP
+syslog only (G)
+If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files\&.
+
+
+Default: \fBsyslog only = no\fR
+
+
+.TP
 template homedir (G)
 When filling out the user information for a Windows NT user, the \fBwinbindd\fR(8) daemon uses this parameter to fill in the home directory for that user\&. If the string \fI%D\fR is present it is substituted with the user's Windows NT domain name\&. If the string \fI%U\fR is present it is substituted with the user's Windows NT user name\&.
 
@@ -6183,7 +6282,7 @@ unix extensions (G)
 This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP\&. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc\&.\&.\&. These extensions require a similarly enabled client, and are of no current use to Windows clients\&.
 
 
-Default: \fBunix extensions = no\fR
+Default: \fBunix extensions = yes\fR
 
 
 .TP
@@ -6237,6 +6336,49 @@ Default: \fBuse mmap = yes\fR
 
 
 .TP
+user (S)
+Synonym for \fIusername\fR\&.
+
+
+.TP
+username (S)
+Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\&.
+
+
+The \fIusername\fR line is needed only when the PC is unable to supply its own username\&. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\&. In both these cases you may also be better using the \\\\server\\share%user syntax instead\&.
+
+
+The \fIusername\fR line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the \fIusername\fR line in turn\&. This is slow and a bad idea for lots of users in case of duplicate passwords\&. You may get timeouts or security breaches using this parameter unwisely\&.
+
+
+Samba relies on the underlying UNIX security\&. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password\&. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session\&. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do\&.
+
+
+To restrict a service to a particular set of users you can use the \fIvalid users \fR parameter\&.
+
+
+If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&.
+
+
+If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&.
+
+
+If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\&.
+
+
+Note that searching though a groups database can take quite some time, and some clients may time out during the search\&.
+
+
+See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how this parameter determines access to the services\&.
+
+
+Default: \fBThe guest account if a guest service, else <empty string>.\fR
+
+
+Examples:\fBusername = fred, mary, jack, jane, @users, @pcgroup\fR
+
+
+.TP
 username level (G)
 This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username\&. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine\&.
 
@@ -6317,54 +6459,11 @@ Example: \fBusername map = /usr/local/samba/lib/users.map\fR
 
 
 .TP
-username (S)
-Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\&.
-
-
-The \fIusername\fR line is needed only when the PC is unable to supply its own username\&. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\&. In both these cases you may also be better using the \\\\server\\share%user syntax instead\&.
-
-
-The \fIusername\fR line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the \fIusername\fR line in turn\&. This is slow and a bad idea for lots of users in case of duplicate passwords\&. You may get timeouts or security breaches using this parameter unwisely\&.
-
-
-Samba relies on the underlying UNIX security\&. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password\&. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session\&. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do\&.
-
-
-To restrict a service to a particular set of users you can use the \fIvalid users \fR parameter\&.
-
-
-If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&.
-
-
-If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&.
-
-
-If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\&.
-
-
-Note that searching though a groups database can take quite some time, and some clients may time out during the search\&.
-
-
-See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how this parameter determines access to the services\&.
-
-
-Default: \fBThe guest account if a guest service, else <empty string>.\fR
-
-
-Examples:\fBusername = fred, mary, jack, jane, @users, @pcgroup\fR
-
-
-.TP
 users (S)
 Synonym for \fI username\fR\&.
 
 
 .TP
-user (S)
-Synonym for \fIusername\fR\&.
-
-
-.TP
 use sendfile (S)
 If this parameter is \fByes\fR, and Samba was built with the --with-sendfile-support option, and the underlying operating system supports sendfile system call, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\&. This may make more efficient use of the system CPU's and cause Samba to be faster\&. This is off by default as it's effects are unknown as yet\&.
 
@@ -6381,6 +6480,20 @@ Default: \fBuse spnego = yes\fR
 
 
 .TP
+utmp (G)
+This boolean parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. If set to \fByes\fR then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server\&. Sites may use this to record the user connecting to a Samba share\&.
+
+
+Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user\&. Enabling this option creates an n^2 algorithm to find this number\&. This may impede performance on large installations\&.
+
+
+See also the \fI utmp directory\fR parameter\&.
+
+
+Default: \fButmp = no\fR
+
+
+.TP
 utmp directory (G)
 This parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server\&. See also the \fIutmp\fR parameter\&. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually \fI/var/run/utmp\fR on Linux)\&.
 
@@ -6392,17 +6505,14 @@ Example: \fButmp directory = /var/run/utmp\fR
 
 
 .TP
-utmp (G)
-This boolean parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. If set to \fByes\fR then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server\&. Sites may use this to record the user connecting to a Samba share\&.
-
-
-Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user\&. Enabling this option creates an n^2 algorithm to find this number\&. This may impede performance on large installations\&.
+-valid (S)
+This parameter indicates whether a share is valid and thus can be used\&. When this parameter is set to false, the share will be in no way visible nor accessible\&.
 
 
-See also the \fI utmp directory\fR parameter\&.
+This option should not be used by regular users but might be of help to developers\&. Samba uses this option internally to mark shares as deleted\&.
 
 
-Default: \fButmp = no\fR
+Default: \fBTrue\fR
 
 
 .TP
@@ -6426,17 +6536,6 @@ Example: \fBvalid users = greg, @pcusers\fR
 
 
 .TP
--valid (S)
-This parameter indicates whether a share is valid and thus can be used\&. When this parameter is set to false, the share will be in no way visible nor accessible\&.
-
-
-This option should not be used by regular users but might be of help to developers\&. Samba uses this option internally to mark shares as deleted\&.
-
-
-Default: \fBTrue\fR
-
-
-.TP
 veto files (S)
 This is a list of files and directories that are neither visible nor accessible\&. Each entry in the list must be separated by a '/', which allows spaces to be included in the entry\&. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards\&.
 
@@ -6488,6 +6587,11 @@ Example: \fBveto oplock files = /*.SEM/\fR
 
 
 .TP
+vfs object (S)
+Synonym for \fIvfs objects\fR \&.
+
+
+.TP
 vfs objects (S)
 This parameter specifies the backend names which are used for Samba VFS I/O operations\&. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects\&.
 
@@ -6499,11 +6603,6 @@ Example: \fBvfs objects = extd_audit recycle\fR
 
 
 .TP
-vfs object (S)
-Synonym for \fIvfs objects\fR \&.
-
-
-.TP
 volume (S)
 This allows you to override the volume label returned for a share\&. Useful for CDROMs with installation programs that insist on a particular volume label\&.
 
@@ -6527,7 +6626,7 @@ winbind cache time (G)
 This parameter specifies the number of seconds the \fBwinbindd\fR(8) daemon will cache user and group information before querying a Windows NT server again\&.
 
 
-Default: \fBwinbind cache type = 15\fR
+Default: \fBwinbind cache type = 300\fR
 
 
 .TP
diff --git a/docs/manpages/smbsh.1 b/docs/manpages/smbsh.1
index 0788237aca..3b9e507246 100644
--- a/docs/manpages/smbsh.1
+++ b/docs/manpages/smbsh.1
@@ -19,7 +19,7 @@
 ..
 .TH "SMBSH" 1 "" "" ""
 .SH NAME
-smbsh \- Allows access to Windows NT filesystem using UNIX commands
+smbsh \- Allows access to remote SMB shares using UNIX commands
 .SH "SYNOPSIS"
 
 .nf
author	John Terpstra <jht@samba.org>	2003-08-29 01:15:53 +0000
committer	John Terpstra <jht@samba.org>	2003-08-29 01:15:53 +0000
commit	04cfbc7854bb793481e9050264a1f0cac1c6198a (patch)
tree	22d0e5d6d77baa1742fe0c9cb7b92ff6ef9f3efc /docs
parent	cc87f00bddb8e13111fcc4ebea4776df7022ae2d (diff)
download	samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.tar.gz samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.tar.bz2 samba-04cfbc7854bb793481e9050264a1f0cac1c6198a.zip