diff options
| author | Jelmer Vernooij <jelmer@samba.org> | 2003-08-15 18:26:34 +0000 |
|---|---|---|
| committer | Jelmer Vernooij <jelmer@samba.org> | 2003-08-15 18:26:34 +0000 |
| commit | d069dacb6e17866dd5d3862e1837a9cae008644f (patch) | |
| tree | c1b660005d31583819c7f43f79168a3332150a85 /docs | |
| parent | cedd66b6e67f4c463eaa072f0e6d87ee1f55718e (diff) | |
| download | samba-d069dacb6e17866dd5d3862e1837a9cae008644f.tar.gz samba-d069dacb6e17866dd5d3862e1837a9cae008644f.tar.bz2 samba-d069dacb6e17866dd5d3862e1837a9cae008644f.zip | |
Regenerate docs
(This used to be commit dc33e94161e4fc1ca6bf66a321c708c89bb276e3)
Diffstat (limited to 'docs')
54 files changed, 9249 insertions, 4441 deletions
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 64c78025ed..c16b48441b 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -34,7 +34,7 @@ Print Queue TDB's ChangeID and Client Caching of Printer Information </a></dt><dt><a href="#id2877045"> 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="#id2879089">About</a></dt><dt><a href="#id2879107">General Overview</a></dt></dl></dd><dt>17. <a href="#vfs">VFS Modules</a></dt><dd><dl><dt><a href="#id2879316">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2879324">The general interface</a></dt><dt><a href="#id2879439">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2879511">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2879518">Initialization and registration</a></dt><dt><a href="#id2879711">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879954">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879961">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2880504">Some Notes</a></dt><dd><dl><dt><a href="#id2880511">Implement TRANSPARENT functions</a></dt><dt><a href="#id2880536">Implement OPAQUE functions</a></dt></dl></dd></dl></dd><dt>18. <a href="#Packaging">Notes to packagers</a></dt><dd><dl><dt><a href="#id2880603">Versioning</a></dt><dt><a href="#id2880638">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 <<a href="mailto:David.Chappell@mail.trincoll.edu" target="_top">David.Chappell@mail.trincoll.edu</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></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 <<a href="mailto:lkcl@switchboard.net" target="_top">lkcl@switchboard.net</a>></p></li><li><p>Paul Ashton <<a href="mailto:paul@argo.demon.co.uk" target="_top">paul@argo.demon.co.uk</a>></p></li><li><p>Duncan Stansfield <<a href="mailto:duncans@sco.com" target="_top">duncans@sco.com</a>></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 <<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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 <<a href="mailto:aliguor@us.ibm.com" target="_top">aliguor@us.ibm.com</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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 <<a href="mailto:ab@samba.org" target="_top">ab@samba.org</a>></p></li><li><p>Stefan Metzmacher <<a href="mailto:metze@metzemix.de" target="_top">metze@metzemix.de</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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="#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 <<a href="mailto:David.Chappell@mail.trincoll.edu" target="_top">David.Chappell@mail.trincoll.edu</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></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 <<a href="mailto:lkcl@switchboard.net" target="_top">lkcl@switchboard.net</a>></p></li><li><p>Paul Ashton <<a href="mailto:paul@argo.demon.co.uk" target="_top">paul@argo.demon.co.uk</a>></p></li><li><p>Duncan Stansfield <<a href="mailto:duncans@sco.com" target="_top">duncans@sco.com</a>></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 <<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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 <<a href="mailto:aliguor@us.ibm.com" target="_top">aliguor@us.ibm.com</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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 <<a href="mailto:ab@samba.org" target="_top">ab@samba.org</a>></p></li><li><p>Stefan Metzmacher <<a href="mailto:metze@metzemix.de" target="_top">metze@metzemix.de</a>></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 <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></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> 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 @@ -1998,22 +1998,24 @@ On the bottom of configure.in, SMB_MODULE() should be called for each module and SMB_SUBSYSTEM() for each subsystem. </p><p>Syntax:</p><pre class="programlisting"> SMB_MODULE(<i class="replaceable"><tt>subsystem</tt></i>_<i class="replaceable"><tt>backend</tt></i>, <i class="replaceable"><tt>object files</tt></i>, <i class="replaceable"><tt>plugin name</tt></i>, <i class="replaceable"><tt>subsystem name</tt></i>, <i class="replaceable"><tt>static_action</tt></i>, <i class="replaceable"><tt>shared_action</tt></i>) -SMB_SUBSYSTEM(<i class="replaceable"><tt>subsystem</tt></i>) -</pre><p>Also, make sure to add the correct directives to -<tt class="filename">Makefile.in</tt>. <i class="replaceable"><tt>@SUBSYSTEM_STATIC@</tt></i> -will be replaced with a list of objects files of the modules that need to -be linked in statically. <i class="replaceable"><tt>@SUBSYSTEM_MODULES@</tt></i> will +SMB_SUBSYSTEM(<i class="replaceable"><tt>subsystem</tt></i>,<i class="replaceable"><tt>depfile</tt></i>) +</pre><p>The depfile for a certain subsystem is the file that calls the +initialisation functions for the statically built in modules.</p><p> +<i class="replaceable"><tt>@SUBSYSTEM_MODULES@</tt></i> in Makefile.in will be replaced with the names of the plugins to build. </p><p>You must make sure all .c files that contain defines that can be changed by ./configure are rebuilded in the 'modules_clean' make target. Practically, this means all c files that contain <b class="command">static_init_subsystem;</b> calls need to be rebuilded. -</p></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"><<a href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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="#id2879089">About</a></dt><dt><a href="#id2879107">General Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879089"></a>About</h2></div></div><div></div></div><p> +</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"><<a href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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> 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="id2879107"></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="id2879116"></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_<pipename>.so</tt> to handle the call if it doesn't know how to handle the call internally. For instance, LSA calls @@ -2030,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"><<a href="mailto:ab@samba.org">ab@samba.org</a>></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"><<a href="mailto:metze@metzemix.de">metze@metzemix.de</a>></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="#id2879316">The Samba (Posix) VFS layer</a></dt><dd><dl><dt><a href="#id2879324">The general interface</a></dt><dt><a href="#id2879439">Possible VFS operation layers</a></dt></dl></dd><dt><a href="#id2879511">The Interaction between the Samba VFS subsystem and the modules</a></dt><dd><dl><dt><a href="#id2879518">Initialization and registration</a></dt><dt><a href="#id2879711">How the Modules handle per connection data</a></dt></dl></dd><dt><a href="#id2879954">Upgrading to the New VFS Interface</a></dt><dd><dl><dt><a href="#id2879961">Upgrading from 2.2.* and 3.0aplha modules</a></dt></dl></dd><dt><a href="#id2880504">Some Notes</a></dt><dd><dl><dt><a href="#id2880511">Implement TRANSPARENT functions</a></dt><dt><a href="#id2880536">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="id2879316"></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="id2879324"></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"><<a href="mailto:ab@samba.org">ab@samba.org</a>></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"><<a href="mailto:metze@metzemix.de">metze@metzemix.de</a>></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> 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>.) @@ -2126,7 +2128,7 @@ DO NOT ACCESS conn->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="id2879439"></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="id2879448"></a>Possible VFS operation layers</h3></div></div><div></div></div><p> These values are used by the VFS subsystem when building the conn->vfs and conn->vfs_opaque structs for a connection with multiple VFS modules. Internally, Samba differentiates only opaque and transparent layers at this process. @@ -2155,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="id2879511"></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="id2879518"></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="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> 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,7 +2197,7 @@ NTSTATUS init_module(void) { 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="id2879711"></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="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. </p><pre class="programlisting"> typedef struct vfs_handle_struct { struct vfs_handle_struct *next, *prev; @@ -2296,7 +2298,7 @@ you can set this function pointer to NULL.</p></dd></dl></div><p>Some useful MAC (handle)->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="id2879954"></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="id2879961"></a>Upgrading from 2.2.* and 3.0aplha modules</h3></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p> +</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 "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); -> example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user); @@ -2559,7 +2561,7 @@ for your module. </p></li><li><p> Compiling & 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="id2880504"></a>Some Notes</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880511"></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="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> Avoid writing functions like this: </p><pre class="programlisting"> @@ -2570,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="id2880536"></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="id2880533"></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) @@ -2590,12 +2592,12 @@ static int example_rename(vfs_handle_struct *handle, connection_struct *conn, 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="#id2880603">Versioning</a></dt><dt><a href="#id2880638">Modules</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880603"></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="#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 <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="id2880638"></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="id2880635"></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/SambaHA.html b/docs/htmldocs/SambaHA.html new file mode 100644 index 0000000000..39ab6b91d8 --- /dev/null +++ b/docs/htmldocs/SambaHA.html @@ -0,0 +1,4 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 29. High Availability Options</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="Backup.html" title="Chapter 28. Samba Backup Techniques"><link rel="next" href="migration.html" title="Part IV. Migration and Updating"></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 29. High Availability Options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Backup.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="migration.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="SambaHA.html#id2953955">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2953955"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Backup.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 28. Samba Backup Techniques </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Part IV. Migration and Updating</td></tr></table></div></body></html> diff --git a/docs/htmldocs/StandAloneServer.html b/docs/htmldocs/StandAloneServer.html new file mode 100644 index 0000000000..f85fdfe3fc --- /dev/null +++ b/docs/htmldocs/StandAloneServer.html @@ -0,0 +1,112 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 8. Stand-Alone Servers</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="domain-member.html" title="Chapter 7. Domain Membership"><link rel="next" href="ClientConfig.html" title="Chapter 9. MS Windows Network Configuration Guide"></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 8. Stand-Alone Servers</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="domain-member.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="ClientConfig.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="StandAloneServer.html#id2893079">Features and Benefits</a></dt><dt><a href="StandAloneServer.html#id2893117">Background</a></dt><dt><a href="StandAloneServer.html#id2893191">Example Configuration</a></dt><dd><dl><dt><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="StandAloneServer.html#id2893714">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="id2893079"></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. +</p><p> +If all that is needed is a server for read-only files, or for +printers alone, it may not make sense to affect a complex installation. +For example: A drafting office needs to store old drawings and reference +standards. No-one can write files to the server as it is legislatively +important that all documents remain unaltered. A share mode read-only stand-alone +server is an ideal solution. +</p><p> +Another situation that warrants simplicity is an office that has many printers +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="id2893117"></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 +local user database. In more technical terms, it means that resources +on the machine will be made available in either SHARE mode or in +USER mode. +</p><p> +No special action is needed other than to create user accounts. Stand-alone +servers do NOT provide network logon services. This means that machines that +use this server do NOT perform a domain logon to it. Whatever logon facility +the workstations are subject to is independent of this machine. It is however +necessary to accommodate any network user so that the logon name they use will +be translated (mapped) locally on the stand-alone server to a locally known +user name. There are several ways this can be done. +</p><p> +Samba tends to blur the distinction a little in respect of what is +a stand-alone server. This is because the authentication database may be +local or on a remote server, even if from the Samba protocol perspective +the Samba server is NOT a member of a domain security context. +</p><p> +Through the use of PAM (Pluggable Authentication Modules) and nsswitch +(the name service switcher, which maintains the unix user database) the source of authentication may reside on +another server. We would be inclined to call this the authentication server. +This means that the Samba server may use the local UNIX/Linux system password database +(<tt class="filename">/etc/passwd</tt> or <tt class="filename">/etc/shadow</tt>), may use a +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="id2893191"></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. +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="RefDocServer"></a>Reference Documentation Server</h3></div></div><div></div></div><p> +Configuration of a read-only data server that EVERYONE can access is very simple. +Here is the smb.conf file that will do this. Assume that all the reference documents +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="id2893237"></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 +unprivileged account names to be used. Given that there is a WINS server on this network +we do use it. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="SimplePrintServer"></a>Central Print Serving</h3></div></div><div></div></div><p> +Configuration of a simple print server is very simple if you have all the right tools +on your system. +</p><div class="orderedlist"><p class="title"><b> Assumptions:</b></p><ol type="1"><li><p> + The print server must require no administration + </p></li><li><p> + The print spooling and processing system on our print server will be CUPS. + (Please refer to <a href="CUPS-printing.html" title="Chapter 19. CUPS Printing Support in Samba 3.0">the chapter about CUPS</a> for more information). + </p></li><li><p> + All printers that the print server will service will be network + printers. They will be correctly configured, by the administrator, + in the CUPS environment. + </p></li><li><p> + All workstations will be installed using postscript drivers. The printer + of choice is the Apple Color LaserWriter. + </p></li></ol></div><p> +In this example our print server will spool all incoming print jobs to +<tt class="filename">/var/spool/samba</tt> until the job is ready to be submitted by +Samba to the CUPS print processor. Since all incoming connections will be as +the anonymous (guest) user, two things will be required: +</p><div class="itemizedlist"><p class="title"><b>Enabling Anonymous Printing</b></p><ul type="disc"><li><p> + The UNIX/Linux system must have a <b class="command">guest</b> account. + The default for this is usually the account <b class="command">nobody</b>. + To find the correct name to use for your version of Samba do the + following: +</p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>testparm -s -v | grep "guest account"</tt></b> +</pre><p> + Then make sure that this account exists in your system password + database (<tt class="filename">/etc/passwd</tt>). + </p></li><li><p> + The directory into which Samba will spool the file must have write + access for the guest account. The following commands will ensure that + this directory is available for use: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>mkdir /var/spool/samba</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>chown nobody.nobody /var/spool/samba</tt></b> +<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="id2893557"></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="id2893714"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="domain-member.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ClientConfig.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 7. Domain Membership </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 9. MS Windows Network Configuration Guide</td></tr></table></div></body></html> diff --git a/docs/htmldocs/VFS.html b/docs/htmldocs/VFS.html new file mode 100644 index 0000000000..ffa767e6c9 --- /dev/null +++ b/docs/htmldocs/VFS.html @@ -0,0 +1,102 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 20. Stackable VFS modules</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="CUPS-printing.html" title="Chapter 19. CUPS Printing Support in Samba 3.0"><link rel="next" href="winbind.html" title="Chapter 21. Winbind: Use of Domain Accounts"></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 20. Stackable VFS modules</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="winbind.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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="VFS.html#id2940177">Features and Benefits</a></dt><dt><a href="VFS.html#id2940195">Discussion</a></dt><dt><a href="VFS.html#id2940424">Included modules</a></dt><dd><dl><dt><a href="VFS.html#id2940432">audit</a></dt><dt><a href="VFS.html#id2940474">extd_audit</a></dt><dt><a href="VFS.html#id2940604">fake_perms</a></dt><dt><a href="VFS.html#id2940622">recycle</a></dt><dt><a href="VFS.html#id2940798">netatalk</a></dt></dl></dd><dt><a href="VFS.html#id2940843">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="VFS.html#id2940865">DatabaseFS</a></dt><dt><a href="VFS.html#id2940920">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="id2940177"></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="id2940195"></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="id2940216"></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="id2940233"></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> +Samba will attempt to load modules from the <span class="emphasis"><em>lib</em></span> +directory in the root directory of the samba installation (usually +<tt class="filename">/usr/lib/samba/vfs</tt> or <tt class="filename">/usr/local/samba/lib/vfs +</tt>). +</p><p> +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="id2940333"></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="id2940424"></a>Included modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940432"></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="id2940474"></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="id2940498"></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="id2940521"></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="id2940604"></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="id2940622"></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 + effect as the "Recycle Bin" on Windows computers. + </p><p>Supported options: + </p><div class="variablelist"><dl><dt><span class="term">recycle:repository</span></dt><dd><p>Relative path of the directory where deleted files should be moved to</p></dd><dt><span class="term">recycle:keeptree</span></dt><dd><p>Specifies whether the directory structure should + be kept or if the files in the directory that is being + deleted should be kept seperately in the recycle bin. + </p></dd><dt><span class="term">recycle:versions</span></dt><dd><p>If this option is set, two files + with the same name that are deleted will both + be kept in the recycle bin. Newer deleted versions + of a file will be called "Copy #x of <i class="replaceable"><tt>filename</tt></i>".</p></dd><dt><span class="term">recycle:touch</span></dt><dd><p>Specifies whether a file's access + date should be touched when the file is moved to + the recycle bin.</p></dd><dt><span class="term">recycle:maxsize</span></dt><dd><p>Files that are larger than the number + of bytes specified by this parameter will + not be put into the recycle bin.</p></dd><dt><span class="term">recycle:exclude</span></dt><dd><p>List of files that should not + be put into the recycle bin when deleted, but deleted + in the regular way.</p></dd><dt><span class="term">recycle:exclude_dir</span></dt><dd><p>Contains a list of directories. When files from + 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="id2940798"></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="id2940843"></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 +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="id2940865"></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 + filesystem. It presents information from a database as a filesystem in + a modular and generic way to allow different databases to be used + (originally designed for organizing MP3s under directories such as + "Artists," "Song Keywords," etc... I have since applied it to a student + roster database very easily). The directory structure is stored in the + database itself and the module makes no assumptions about the database + structure beyond the table it requires to run. + </p><p> + Any feedback would be appreciated: comments, suggestions, patches, + etc... If nothing else, hopefully it might prove useful for someone + else who wishes to create a virtual filesystem. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940920"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="winbind.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 19. CUPS Printing Support in Samba 3.0 </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 21. Winbind: Use of Domain Accounts</td></tr></table></div></body></html> diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html new file mode 100644 index 0000000000..49eb2117ca --- /dev/null +++ b/docs/htmldocs/bugreport.html @@ -0,0 +1,115 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 35. Reporting Bugs</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="problems.html" title="Chapter 34. Analysing and solving samba problems"><link rel="next" href="Appendixes.html" title="Part VI. Appendixes"></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 35. Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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="bugreport.html#id2960613">Introduction</a></dt><dt><a href="bugreport.html#id2960681">General info</a></dt><dt><a href="bugreport.html#id2960718">Debug levels</a></dt><dt><a href="bugreport.html#id2960926">Internal errors</a></dt><dt><a href="bugreport.html#id2961060">Attaching to a running process</a></dt><dt><a href="bugreport.html#id2961107">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960613"></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 +may be changing the bug reporting mechanism at some time. +</p><p> +Please also do as much as you can yourself to help track down the +bug. Samba is maintained by a dedicated group of people who volunteer +their time, skills and efforts. We receive far more mail about it than +we can possibly answer, so you have a much higher chance of an answer +and a fix if you send us a "developer friendly" bug report that lets +us fix it fast. +</p><p> +Do not assume that if you post the bug to the comp.protocols.smb +newsgroup or the mailing list that we will read it. If you suspect that your +problem is not a bug but a configuration problem then it is better to send +it to the Samba mailing list, as there are (at last count) 5000 other users on +that list that may be able to help you. +</p><p> +You may also like to look though the recent mailing list archives, +which are conveniently accessible on the Samba web pages +at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960681"></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 +file for correct syntax. +</p><p> +Have you run through the <a href="diagnosis.html" title="Chapter 33. The Samba checklist">diagnosis</a>? +This is very important. +</p><p> +If you include part of a log file with your bug report then be sure to +annotate it with exactly what you were doing on the client at the +time, and exactly what the results were. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960718"></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="id2960739"></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: +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>log level = 10</tt></i></td></tr><tr><td><i class="parameter"><tt>log file = /usr/local/samba/lib/log.%m</tt></i></td></tr><tr><td><i class="parameter"><tt>include = /usr/local/samba/lib/smb.conf.%m</tt></i></td></tr></table><p> +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="id2960830"></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="id2960857"></a><i class="parameter"><tt>log level</tt></i> +is synonymous with the parameter <a class="indexterm" name="id2960872"></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="id2960897"></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="id2960926"></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 +you have faulty hardware or system software). +</p><p> +If the message came from smbd then it will probably be accompanied by +a message which details the last SMB message received by smbd. This +info is often very useful in tracking down the problem so please +include it in your bug report. +</p><p> +You should also detail how to reproduce the problem, if +possible. Please make this reasonably detailed. +</p><a class="indexterm" name="id2960962"></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="id2960984"></a><a class="indexterm" name="id2960993"></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 +don't have gdb then try <b class="userinput"><tt>dbx</tt></b>. Then within the debugger +use the command <b class="command">where</b> to give a stack trace of where the +problem occurred. Include this in your report. +</p><p> +If you know any assembly language then do a +<b class="command">disass</b> of the routine +where the problem occurred (if its in a library routine then +disassemble the routine that called it) and try to work out exactly +where the problem is by looking at the surrounding code. Even if you +don't know assembly, 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="id2961060"></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 +to the running process using +<b class="userinput"><tt>gdb smbd <i class="replaceable"><tt>PID</tt></i></tt></b> where you get +<i class="replaceable"><tt>PID</tt></i> from <span class="application">smbstatus</span>. +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="id2961107"></a>Patches</h2></div></div><div></div></div><a class="indexterm" name="id2961114"></a><a class="indexterm" name="id2961123"></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 class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 34. Analysing and solving samba problems </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Part VI. Appendixes</td></tr></table></div></body></html> diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html new file mode 100644 index 0000000000..95cdb0f581 --- /dev/null +++ b/docs/htmldocs/compiling.html @@ -0,0 +1,200 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 36. How to compile Samba</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="Part VI. Appendixes"><link rel="previous" href="Appendixes.html" title="Part VI. Appendixes"><link rel="next" href="Portability.html" title="Chapter 37. Portability"></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 36. How to compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendixes.html">Prev</a> </td><th width="60%" align="center">Part VI. Appendixes</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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="compiling.html#id2961265">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="compiling.html#id2961282">Introduction</a></dt><dt><a href="compiling.html#id2961320">CVS Access to samba.org</a></dt></dl></dd><dt><a href="compiling.html#id2961581">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="compiling.html#id2961644">Verifying Samba's PGP signature</a></dt><dt><a href="compiling.html#id2961798">Building the Binaries</a></dt><dd><dl><dt><a href="compiling.html#id2961978">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="compiling.html#id2962144">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="compiling.html#id2962252">Starting from inetd.conf</a></dt><dt><a href="compiling.html#id2962499">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="id2961265"></a>Access Samba source code via CVS</h2></div></div><div></div></div><a class="indexterm" name="id2961274"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961282"></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 +be accessed via anonymous CVS using the instructions +detailed in this chapter. +</p><p> +This chapter is a modified version of the instructions found at +<a href="http://samba.org/samba/cvs.html" target="_top">http://samba.org/samba/cvs.html</a> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961320"></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="id2961335"></a>Access via CVSweb</h4></div></div><div></div></div><a class="indexterm" name="id2961344"></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 +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="id2961383"></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 +and keep them up to date via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser. +</p><p> +To download the latest cvs source code, point your +browser at the URL : +<a href="http://www.cyclic.com/" target="_top">http://www.cyclic.com/</a>. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from the Cyclic website. +</p><p> +To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name +</p><div class="procedure"><p class="title"><b>Procedure 36.1. Retrieving samba using CVS</b></p><ol type="1"><li><p> + Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + </p></li><li><p> + Run the command + </p><p> + <b class="userinput"><tt>cvs -d :pserver:cvs@samba.org:/cvsroot login</tt></b> + </p></li><li><p> + When it asks you for a password type <b class="userinput"><tt>cvs</tt></b>. + </p></li><li><p> + Run the command + </p><p> + <b class="userinput"><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</tt></b> + </p><p> + This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + </p><p> + CVS branches other then HEAD can be obtained by using the + <tt class="option">-r</tt> and defining a tag name. A list of branch tag names + can be found on the "Development" page of the samba web site. A common + request is to obtain the latest 3.0 release code. This could be done by + using the following command: + </p><p> + <b class="userinput"><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_3_0 samba</tt></b> + </p></li><li><p> + Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + </p><p> + <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="id2961581"></a>Accessing the samba sources via rsync and ftp</h2></div></div><div></div></div><a class="indexterm" name="id2961589"></a><a class="indexterm" name="id2961597"></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. + See <a href="http://rsync.samba.org/" target="_top">the rsync homepage</a> for more info on rsync. + </p><p> + The disadvantage of the unpacked trees is that they do not support automatic + merging of local changes like CVS does. rsync access is most convenient + for an initial install. + </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2961644"></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 +standard reflex. +</p><p> +With that said, go ahead and download the following files: +</p><pre class="screen"> +<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="id2961705"></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"> +<tt class="prompt">$ </tt><b class="userinput"><tt>gpg --import samba-pubkey.asc</tt></b> +</pre><p> +And verify the Samba source code integrity with: +</p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>gzip -d samba-2.2.8a.tar.gz</tt></b> +<tt class="prompt">$ </tt><b class="userinput"><tt>gpg --verify samba-2.2.8a.tar.asc</tt></b> +</pre><p> +If you receive a message like, "Good signature from Samba Distribution +Verification Key..." +then all is well. The warnings about trust relationships can be ignored. An +example of what you would not want to see would be: +</p><p> +<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="id2961798"></a>Building the Binaries</h2></div></div><div></div></div><a class="indexterm" name="id2961805"></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="id2961851"></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 + </tt></b></pre><p>Note that if you are upgrading for a previous version + of Samba you might like to know that the old versions of + the binaries will be renamed with a ".old" extension. You + can go back to the previous version with</p><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="id2961978"></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 + remember to add the configure option + <tt class="option">--with-krb5=<i class="replaceable"><tt>DIR</tt></i></tt>.</p><p>After you run configure make sure that + <tt class="filename">include/config.h</tt> it generates contains lines like + this:</p><pre class="programlisting"> +#define HAVE_KRB5 1 +#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="id2962059"></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="id2962091"></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="id2962144"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><a class="indexterm" name="id2962165"></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 + by <span class="application">inetd</span> or <span class="application">xinetd</span>, + or you can start them as + daemons either from the command line or in <tt class="filename"> + /etc/rc.local</tt>. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start + Samba. In many cases you must be root.</p><p>The main advantage of starting <span class="application">smbd</span> + and <span class="application">nmbd</span> using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962252"></a>Starting from inetd.conf</h3></div></div><div></div></div><a class="indexterm" name="id2962260"></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> + and add two lines something like this:</p><pre class="programlisting"> + netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd + netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd + </pre><p>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="id2962350"></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="id2962393"></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="id2962405"></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 + net. <span class="application">nmbd</span> tries to determine it at run + time, but fails on some unixes. + </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Many unixes only accept around 5 + parameters on the command line in <tt class="filename">inetd.conf</tt>. + This means you shouldn't use spaces between the options and + arguments, or you should use a script, and start the script + from <b class="command">inetd</b>.</p></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="id2962499"></a>Alternative: starting it as a daemon</h3></div></div><div></div></div><a class="indexterm" name="id2962507"></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 + /usr/local/samba/bin/smbd -D + /usr/local/samba/bin/nmbd -D + </pre><p>then make it executable with <b class="command">chmod + +x startsmb</b></p><p>You can then run <b class="command">startsmb</b> by + hand or execute it from <tt class="filename">/etc/rc.local</tt> + </p><p>To kill it send a kill signal to the processes + <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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Appendixes.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Appendixes.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part VI. Appendixes </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 37. Portability</td></tr></table></div></body></html> diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html new file mode 100644 index 0000000000..ea84661d30 --- /dev/null +++ b/docs/htmldocs/diagnosis.html @@ -0,0 +1,287 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 33. The Samba checklist</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="next" href="problems.html" title="Chapter 34. Analysing and solving samba 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 33. The Samba checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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="diagnosis.html#id2957982">Introduction</a></dt><dt><a href="diagnosis.html#id2958022">Assumptions</a></dt><dt><a href="diagnosis.html#id2958249">The tests</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957982"></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 +then it is probably working fine. +</p><p> +You should do ALL the tests, in the order shown. We have tried to +carefully choose them so later tests only use capabilities verified in +the earlier tests. However, do not stop at the first error as there +have been some instances when continuing with the tests has helped +to solve a problem. +</p><p> +If you send one of the samba mailing lists an email saying "it doesn't work" +and you have not followed this test procedure then you should not be surprised +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="id2958022"></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> +The procedure is similar for other types of clients. +</p><p> +It is also assumed you know the name of an available share in your +<tt class="filename">smb.conf</tt>. I will assume this share is called <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="id2958071"></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. +</p></div><p> +Please pay attention to the error messages you receive. If any error message +reports that your server is being unfriendly you should first check that your +IP name resolution is correctly set up. eg: Make sure your <tt class="filename">/etc/resolv.conf</tt> +file points to name servers that really do exist. +</p><p> +Also, if you do not have DNS server access for name resolution please check +that the settings for your <tt 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="id2958171"></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). +Relevant log files can be found (for default installations) in +<tt class="filename">/usr/local/samba/var</tt>. Also, connection logs from +machines can be found here or possibly in <tt class="filename">/var/log/samba</tt> +depending on how or if you specified logging in your <tt class="filename">smb.conf</tt> file. +</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="id2958249"></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="id2958265"></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. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Your <tt class="filename">smb.conf</tt> file may be located in: <tt class="filename">/etc/samba</tt> +Or in: <tt class="filename">/usr/local/samba/lib</tt> +</p></div></li><li><p> +Run the command <b class="userinput"><tt>ping BIGSERVER</tt></b> from the PC and +<b class="userinput"><tt>ping ACLIENT</tt></b> from +the unix box. If you don't get a valid response then your TCP/IP +software is not correctly installed. +</p><p> +Note that you will need to start a "dos prompt" window on the PC to +run ping. +</p><p> +If you get a message saying <span class="errorname">host not found</span> or similar then your DNS +software or <tt class="filename">/etc/hosts</tt> file is not correctly setup. +It is possible to +run samba without DNS entries for the server and client, but I assume +you do have correct entries for the remainder of these tests. +</p><p> +Another reason why ping might fail is if your host is running firewall +software. You will need to relax the rules to let in the workstation +in question, perhaps by allowing access from another subnet (on Linux +this is done via the <span class="application">ipfwadm</span> program.) +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Modern Linux distributions install ipchains/iptables by default. +This is a common problem that is often overlooked. +</p></div></li><li><p> +Run the command <b class="userinput"><tt>smbclient -L BIGSERVER</tt></b> on the unix box. You +should get a list of available shares back. +</p><p> +If you get a error message containing the string "Bad password" then +you probably have either an incorrect <b class="command">hosts allow</b>, +<b class="command">hosts deny</b> or <b class="command">valid users</b> line in your +<tt class="filename">smb.conf</tt>, or your guest account is not +valid. Check what your guest account is using <span class="application">testparm</span> and +temporarily remove any <b class="command">hosts allow</b>, <b class="command">hosts deny</b>, <b class="command">valid users</b> or <b class="command">invalid users</b> lines. +</p><p> +If you get a <span class="errorname">connection refused</span> response then the smbd server may +not be running. If you installed it in inetd.conf then you probably edited +that file incorrectly. If you installed it as a daemon then check that +it is running, and check that the netbios-ssn port is in a LISTEN +state using <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="id2958530"></a> +<a class="indexterm" name="id2958538"></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 +this network super daemon. +</p></div><p> +If you get a <span class="errorname">session request failed</span> then the server refused the +connection. If it says "Your server software is being unfriendly" then +its probably because you have invalid command line parameters to <span class="application">smbd</span>, +or a similar fatal problem with the initial startup of <span class="application">smbd</span>. Also +check your config file (<tt class="filename">smb.conf</tt>) for syntax errors with <span class="application">testparm</span> +and that the various directories where samba keeps its log and lock +files exist. +</p><p> +There are a number of reasons for which smbd may refuse or decline +a session request. The most common of these involve one or more of +the following <tt class="filename">smb.conf</tt> file entries: +</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</tt></i></td></tr><tr><td><i class="parameter"><tt>bind interfaces only = Yes</tt></i></td></tr></table><p> +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="id2958698"></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="id2958724"></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="id2958744"></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 +something like Digital's Pathworks. Check your <tt class="filename">inetd.conf</tt> file before trying +to start <span class="application">smbd</span> as a daemon, it can avoid a lot of frustration! +</p><p> +And yet another possible cause for failure of this test is when the subnet mask +and / or broadcast address settings are incorrect. Please check that the +network interface IP Address / Broadcast Address / Subnet Mask settings are +correct and that Samba has correctly noted these in the <tt class="filename">log.nmbd</tt> file. +</p></li><li><p> +Run the command <b class="userinput"><tt>nmblookup -B BIGSERVER __SAMBA__</tt></b>. You should get the +IP address of your Samba server back. +</p><p> +If you don't then nmbd is incorrectly installed. Check your <tt class="filename">inetd.conf</tt> +if you run it from there, or that the daemon is running and listening +to udp port 137. +</p><p> +One common problem is that many inetd implementations can't take many +parameters on the command line. If this is the case then create a +one-line script that contains the right parameters and run that from +inetd. +</p></li><li><p>run the command <b class="userinput"><tt>nmblookup -B ACLIENT '*'</tt></b></p><p> +You should get the PCs IP address back. If you don't then the client +software on the PC isn't installed correctly, or isn't started, or you +got the name of the PC wrong. +</p><p> +If ACLIENT doesn't resolve via DNS then use the IP address of the +client in the above test. +</p></li><li><p> +Run the command <b class="userinput"><tt>nmblookup -d 2 '*'</tt></b> +</p><p> +This time we are trying the same as the previous test but are trying +it via a broadcast to the default broadcast address. A number of +NetBIOS / TCP/IP hosts on the network should respond, although Samba may +not catch all of the responses in the short time it listens. You +should see <span class="errorname">got a positive name query response</span> +messages from several hosts. +</p><p> +If this doesn't give a similar result to the previous test then +nmblookup isn't correctly getting your broadcast address through its +automatic mechanism. In this case you should experiment with the +<a class="indexterm" name="id2958915"></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 +use the <tt class="option">-B</tt> option to set the broadcast address to that of the PCs +subnet. +</p><p> +This test will probably fail if your subnet mask and broadcast address are +not correct. (Refer to TEST 3 notes above). +</p></li><li><a class="indexterm" name="id2958962"></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 +another account then add the <tt class="option">-U <i class="replaceable"><tt>accountname</tt></i></tt> option to the end of +the command line. eg: +<b class="userinput"><tt>smbclient //bigserver/tmp -Ujohndoe</tt></b> +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +It is possible to specify the password along with the username +as follows: +<b class="userinput"><tt>smbclient //bigserver/tmp -Ujohndoe%secret</tt></b> +</p></div><p> +Once you enter the password you should get the <tt class="prompt">smb></tt> prompt. If you +don't then look at the error message. If it says <span class="errorname">invalid network +name</span> then the service <span class="emphasis"><em>"tmp"</em></span> is not correctly setup in your <tt class="filename">smb.conf</tt>. +</p><p> +If it says <span class="errorname">bad password</span> then the likely causes are: +</p><div class="orderedlist"><ol type="1"><li><p> + 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="id2959084"></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="id2959107"></a><i class="parameter"><tt>password level</tt></i> option at a high enough level + </p></li><li><p> + the <a class="indexterm" name="id2959129"></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> +Once connected you should be able to use the commands +<b class="command">dir</b> <b class="command">get</b> <b class="command">put</b> etc. +Type <b class="command">help <i class="replaceable"><tt>command</tt></i></b> for instructions. You should +especially check that the amount of free disk space shown is correct +when you type <b class="command">dir</b>. +</p></li><li><p> +On the PC, type the command <b class="userinput"><tt>net view \\BIGSERVER</tt></b>. You will +need to do this from within a "dos prompt" window. You should get back a +list of available shares on the server. +</p><p> +If you get a <span class="errorname">network name not found</span> or similar error then netbios +name resolution is not working. This is usually caused by a problem in +nmbd. To overcome it you could do one of the following (you only need +to choose one of them): +</p><div class="orderedlist"><ol type="1"><li><p> + fixup the <span class="application">nmbd</span> installation +</p></li><li><p> + add the IP address of BIGSERVER to the <b class="command">wins server</b> box in the + advanced TCP/IP setup on the PC. +</p></li><li><p> + enable windows name resolution via DNS in the advanced section of + the TCP/IP setup +</p></li><li><p> + add BIGSERVER to your lmhosts file on the PC. +</p></li></ol></div><p> +If you get a <span class="errorname">invalid network name</span> or <span class="errorname">bad password error</span> then the +same fixes apply as they did for the <b class="userinput"><tt>smbclient -L</tt></b> test above. In +particular, make sure your <b class="command">hosts allow</b> line is correct (see the man +pages) +</p><p> +Also, do not overlook that fact that when the workstation requests the +connection to the samba server it will attempt to connect using the +name with which you logged onto your Windows machine. You need to make +sure that an account exists on your Samba server with that exact same +name and password. +</p><p> +If you get <span class="errorname">specified computer is not receiving requests</span> or similar +it probably means that the host is not contactable via tcp services. +Check to see if the host is running tcp wrappers, and if so add an entry in +the <tt class="filename">hosts.allow</tt> file for your client (or subnet, etc.) +</p></li><li><p> +Run the command <b class="userinput"><tt>net use x: \\BIGSERVER\TMP</tt></b>. You should +be prompted for a password then you should get a <tt class="computeroutput">command completed +successfully</tt> message. If not then your PC software is incorrectly +installed or your smb.conf is incorrect. make sure your <b class="command">hosts allow</b> +and other config lines in <tt class="filename">smb.conf</tt> are correct. +</p><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="id2959420"></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="id2959460"></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 +<i class="replaceable"><tt>testgroup</tt></i> is the name of the workgroup that your Samba server and +Windows PCs belong to. You should get back the IP address of the +master browser for that workgroup. +</p><p> +If you don't then the election process has failed. Wait a minute to +see if it is just being slow then try again. If it still fails after +that then look at the browsing options you have set in <tt class="filename">smb.conf</tt>. Make +sure you have <a class="indexterm" name="id2959524"></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 +appear in the browse list of your local workgroup (or the one you +specified in <tt class="filename">smb.conf</tt>). You should be able to double click on the name +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it +is refusing to browse a server that has no encrypted password +capability and is in user level security mode. In this case either set +<a class="indexterm" name="id2959575"></a><i class="parameter"><tt>security</tt></i> = server AND +<a class="indexterm" name="id2959589"></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="id2959610"></a><i class="parameter"><tt>encrypt passwords</tt></i> is +set to "yes". +</p></li></ol></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="problems.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part V. Troubleshooting </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 34. Analysing and solving samba problems</td></tr></table></div></body></html> diff --git a/docs/htmldocs/domain-member.html b/docs/htmldocs/domain-member.html new file mode 100644 index 0000000000..313c6e0fc7 --- /dev/null +++ b/docs/htmldocs/domain-member.html @@ -0,0 +1,534 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 7. Domain Membership</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="samba-bdc.html" title="Chapter 6. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 8. Stand-Alone Servers"></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 7. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:jra@samba.org">jra@samba.org</a>></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="domain-member.html#id2890490">Features and Benefits</a></dt><dt><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="domain-member.html#id2891126">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="domain-member.html#id2891341">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="domain-member.html#id2891414">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="domain-member.html#id2892061">Why is this better than security = server?</a></dt></dl></dd><dt><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="domain-member.html#id2892246">Setup your smb.conf</a></dt><dt><a href="domain-member.html#id2892373">Setup your /etc/krb5.conf</a></dt><dt><a href="domain-member.html#ads-create-machine-account">Create the computer account</a></dt><dt><a href="domain-member.html#ads-test-server">Test your server setup</a></dt><dt><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="domain-member.html#id2892751">Notes</a></dt></dl></dd><dt><a href="domain-member.html#id2892773">Common Errors</a></dt><dd><dl><dt><a href="domain-member.html#id2892816">Can Not Add Machine Back to Domain</a></dt><dt><a href="domain-member.html#id2892848">Adding Machine to Domain Fails</a></dt><dt><a href="domain-member.html#id2892992">I can't join a Windows 2003 PDC</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, +otherwise it would not be capable of offering a viable option for many users. +</p><p> +This chapter covers background information pertaining to domain membership, +Samba configuration for it, and MS Windows client procedures for joining a +domain. Why is this necessary? Because both are areas in which there exists +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="id2890490"></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 +chapter describes the process that must be followed to make a workstation +(or another server - be it an <span class="application">MS Windows NT4 / 200x</span> +server) or a Samba server a member of an MS Windows Domain security context. +</p><p> +Samba-3 can join an MS Windows NT4 style domain as a native member server, an +MS Windows Active Directory Domain as a native member server, or a Samba Domain +Control network. +</p><p> +Domain membership has many advantages: +</p><div class="itemizedlist"><ul type="disc"><li><p> + MS Windows workstation users get the benefit of SSO + </p></li><li><p> + Domain user access rights and file ownership / access controls can be set + from the single Domain SAM (Security Account Manager) database + (works with Domain member servers as well as with MS Windows workstations + that are domain members) + </p></li><li><p> + Only <span class="application">MS Windows NT4 / 200x / XP Professional</span> + workstations that are Domain members + can use network logon facilities + </p></li><li><p> + Domain Member workstations can be better controlled through the use of + Policy files (<tt class="filename">NTConfig.POL</tt>) and Desktop Profiles. + </p></li><li><p> + Through the use of logon scripts, users can be given transparent access to network + applications that run off application servers + </p></li><li><p> + Network administrators gain better application and user access management + abilities because there is no need to maintain user accounts on any network + 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="id2890621"></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, +this is known as a "Computer Account." +</p><p> +The password of a machine trust account acts as the shared secret for +secure communication with the Domain Controller. This is a security +feature to prevent an unauthorized machine with the same NetBIOS name +from joining the domain and gaining access to domain user/group +accounts. Windows NT, 200x, XP Professional clients use machine trust +accounts, but Windows 9x / Me / XP Home clients do not. Hence, a +Windows 9x / Me / XP Home client is never a true member of a domain +because it does not possess a machine trust account, and thus has no +shared secret with the domain controller. +</p><p> +A Windows NT4 PDC stores each machine trust account in the Windows Registry. +The introduction of MS Windows 2000 saw the introduction of Active Directory, +the new repository for machine trust accounts. +</p><p> +A Samba PDC, however, stores each machine trust account in two parts, +as follows: + +</p><div class="itemizedlist"><ul type="disc"><li><p> + A Domain Security Account (stored in the + <a class="indexterm" name="id2890675"></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> + The older format of this data is the <tt class="filename">smbpasswd</tt> database + which contains the UNIX login ID, the UNIX user identifier (UID), and the + LanMan and NT encrypted passwords. There is also some other information in + this file that we do not need to concern ourselves with here. + </p><p> + The two newer database types are called <span class="emphasis"><em>ldapsam</em></span>, + <span class="emphasis"><em>tdbsam</em></span>. Both store considerably more data than the + older <tt class="filename">smbpasswd</tt> file did. The extra information + enables new user account controls to be used. + </p></li><li><p> + A corresponding UNIX account, typically stored in + <tt class="filename">/etc/passwd</tt>. Work is in progress to allow a + 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="id2890757"></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="id2890790"></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 + logged on as the administrator account. + </p></li><li><p> + "On-the-fly" creation. The Samba machine trust account is automatically + 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="id2890821"></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="id2890851"></a> +<a class="indexterm" name="id2890859"></a> + + +</p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/sbin/useradd -g 100 -d /dev/null -c <i class="replaceable"><tt>"machine nickname"</tt></i> \ + -s /bin/false <i class="replaceable"><tt>machine_name</tt></i>$ </tt></b> + +<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="id2890921"></a> +On *BSD systems, this can be done using the <b class="command">chpass</b> utility: +</p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>chpass -a \ + "<i class="replaceable"><tt>machine_name</tt></i>$:*:101:100::0:0:Workstation <i class="replaceable"><tt>machine_name</tt></i>:/dev/null:/sbin/nologin"</tt></b> +</pre><p> +</p><p> +The <tt class="filename">/etc/passwd</tt> entry will list the machine name +with a "$" appended, won't have a password, will have a null shell and no +home directory. For example a machine named 'doppy' would have an +<tt class="filename">/etc/passwd</tt> entry like this: +</p><pre class="programlisting"> +doppy$:x:505:100:<i class="replaceable"><tt>machine_nickname</tt></i>:/dev/null:/bin/false +</pre><p> +Above, <i class="replaceable"><tt>machine_nickname</tt></i> can be any +descriptive name for the client, i.e., BasementComputer. +<i class="replaceable"><tt>machine_name</tt></i> absolutely must be the NetBIOS +name of the client to be joined to the domain. The "$" must be +appended to the NetBIOS name of the client or Samba will not recognize +this as a machine trust account. +</p><p> +Now that the corresponding UNIX account has been created, the next step is to create +the Samba account for the client containing the well-known initial +machine trust account password. This can be done using the +<b class="command">smbpasswd</b> command +as shown here: +</p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -a -m <i class="replaceable"><tt>machine_name</tt></i></tt></b> +</pre><p> +</p><p> +where <i class="replaceable"><tt>machine_name</tt></i> is the machine's NetBIOS +name. The RID of the new machine account is generated from the UID of +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="id2891100"></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="id2891126"></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>. +When executed in the target directory this will unpack <b class="command">SrvMge.exe</b> +and <b class="command">UsrMgr.exe</b> (both are domain management tools for MS Windows NT4 workstation). +</p><p> +If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product + you should download the <b class="command">Nexus.exe</b> package from the Microsoft web site. +When executed from the target directory this will unpack the same tools but for use on +this platform. +</p><p> +Further information about these tools may be obtained from the following locations: +<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;173673</a> +<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;172540</a> +</p><p> +Launch the <b class="command">srvmgr.exe</b> (Server Manager for Domains) and follow these steps: +</p><div class="procedure"><p class="title"><b>Procedure 7.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p> + From the menu select <span class="guimenu">Computer</span> + </p></li><li><p> + Click on <span class="guimenuitem">Select Domain</span> + </p></li><li><p> + Click on the name of the domain you wish to administer in the + <span class="guilabel">Select Domain</span> panel and then click + <span class="guibutton">OK</span>. + </p></li><li><p> + Again from the menu select <span class="guimenu">Computer</span> + </p></li><li><p> + Select <span class="guimenuitem">Add to Domain</span> + </p></li><li><p> + In the dialog box, click on the radio button to + <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="id2891341"></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. +</p><p>Since each Samba machine trust account requires a corresponding UNIX account, a method +for automatically creating the UNIX account is usually supplied; this requires configuration of the +add machine script option in +<tt class="filename">smb.conf</tt>. This method is not required, however; corresponding UNIX +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># <...remainder of parameters...></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="id2891414"></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="id2891426"></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 + Samba server) must be entered here; the operation will fail if an ordinary user + account is given. + </p><p> + Note: For security reasons the password for this administrative account should be set + to a password that is other than that used for the root user in the + <tt class="filename">/etc/passwd</tt>. + </p><p> + 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="id2891478"></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="id2891503"></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>. + In this case, the existing machine trust account is used to join the machine + to the domain. + </p><p> + If the machine trust account is to be created + on-the-fly, on the Identification Changes menu enter the domain + name, and check the box <span class="guilabel">Create a Computer Account in the + 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="id2891543"></a>Samba</h4></div></div><div></div></div><p>Joining a Samba client to a domain is documented in + <a href="domain-member.html#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 +of a domain security context. This means by definition that all user +authentication will be done from a centrally defined authentication regime. +The authentication regime may come from an NT3/4 style (old domain technology) +server, or it may be provided from an Active Directory server (ADS) running on +MS Windows 2000 or later. +</p><p> +<span class="emphasis"><em> +Of course it should be clear that the authentication back end itself could be +from any distributed directory architecture server that is supported by Samba. +This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory +Server, etc. +</em></span> +</p><p> +Please refer to <a href="samba-pdc.html" title="Chapter 5. Domain Control">the chapter on setting up a PDC</a> +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="id2891624"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><p> + </p><div class="table"><a name="id2891635"></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="id2891708"></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="id2891752"></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> +</p><p> +as this is the name of the domain we are joining. +</p><p> +You must also have the parameter +<a class="indexterm" name="id2891802"></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="id2891826"></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> +</p><p> +These are the primary and backup domain controllers Samba +will attempt to contact in order to authenticate users. Samba will +try to contact each of these servers in order, so you may want to +rearrange this list in order to spread out the authentication load +among domain controllers. +</p><p> +Alternatively, if you want smbd to automatically determine +the list of Domain controllers to use for authentication, you may +set this line to be: +</p><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password server = *</tt></i></td></tr></table><p> +</p><p> +This method allows Samba to use exactly the same mechanism that NT does. This +method either broadcasts or uses a WINS database in order to +find domain controllers to authenticate against. +</p><p> +In order to actually join the domain, you must run this command: +</p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>net rpc join -S DOMPDC -U<i class="replaceable"><tt>Administrator%password</tt></i></tt></b> +</pre><p> +</p><p> +If the <tt class="option">-S DOMPDC</tt> argument is not given then +the domain name will be obtained from <tt class="filename">smb.conf</tt>. +</p><p> +As we are joining the domain DOM and the PDC for that domain +(the only machine that has write access to the domain SAM database) +is DOMPDC, we use it for the <tt class="option">-S</tt> option. +The <i class="replaceable"><tt>Administrator%password</tt></i> is +the login name and password for an account which has the necessary +privilege to add machines to the domain. If this is successful +you will see the message: +</p><p> +<tt class="computeroutput">Joined domain DOM.</tt> +or <tt class="computeroutput">Joined 'SERV1' to realm 'MYREALM'</tt> +</p><p> +in your terminal window. See the +<b class="command">net</b> man page for more details. +</p><p> +This process joins the server to the domain without having to create the machine +trust account on the PDC beforehand. +</p><p> +This command goes through the machine account password +change protocol, then writes the new (random) machine account +password for this Samba server into a file in the same directory +in which an smbpasswd file would be stored - normally: +</p><p> +<tt class="filename">/usr/local/samba/private/secrets.tdb</tt> +</p><p> +This file is created and owned by root and is not +readable by any other user. It is the key to the domain-level +security for your system, and should be treated as carefully +as a shadow password file. +</p><p> +Finally, restart your Samba daemons and get ready for +clients to begin using domain security! The way you can restart your +samba daemons depends on your distribution, but in most cases running +</p><pre class="screen"> + <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="id2892061"></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 +</tt> attaches to your domain security Samba server, there needs +to be a local UNIX user fred to represent that user in the UNIX +filesystem. This is very similar to the older Samba security mode +security = server, +where Samba would pass through the authentication request to a Windows +NT server in the same way as a Windows 95 or Windows 98 server would. +</p><p> + Please refer to <a href="winbind.html" title="Chapter 21. Winbind: Use of Domain Accounts">the chapter on winbind</a> for information on a system +to automatically assign UNIX uids and gids to Windows NT Domain users and groups. +</p><p> +The advantage to domain-level security is that the +authentication in domain-level security is passed down the authenticated +RPC channel in exactly the same way that an NT server would do it. This +means Samba servers now participate in domain trust relationships in +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="id2892116"></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="id2892135"></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. +</p><p> +And finally, acting in the same manner as an NT server +authenticating to a PDC means that as part of the authentication +reply, the Samba server gets the user identification information such +as the user SID, the list of NT groups the user belongs to, etc. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +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="id2892203"></a><a class="indexterm" name="id2892211"></a><a class="indexterm" name="id2892223"></a><a class="indexterm" name="id2892231"></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="id2892246"></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="id2892305"></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="id2892352"></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="id2892373"></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] + default_realm = YOUR.KERBEROS.REALM + + [realms] + YOUR.KERBEROS.REALM = { + kdc = your.kerberos.server + } +</pre><a class="indexterm" name="id2892409"></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. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +The realm must be uppercase or you will get <span class="errorname">Cannot find KDC for +requested realm while getting initial credentials</span> error (Kerberos +is case-sensitive!). +</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Time between the two servers must be synchronized. You will get a +<span class="errorname">kinit(v5): Clock skew too great while getting initial credentials</span> +if the time difference is more than five minutes. +</p></div><p> +You also must ensure that you can do a reverse DNS lookup on the IP +address of your KDC. Also, the name that this reverse lookup maps to +must either be the NetBIOS name of the KDC (ie. the hostname with no +domain attached) or it can alternatively be the NetBIOS name +followed by the realm. +</p><p> +The easiest way to ensure you get this right is to add a +<tt class="filename">/etc/hosts</tt> entry mapping the IP address of your KDC to +its NetBIOS name. If you don't get this right then you will get a +<span class="errorname">local error</span> when you try to join the realm. +</p><p> +If all you want is Kerberos support in <span class="application">smbclient</span> then you can skip +straight to <a href="domain-member.html#ads-test-smbclient" title="Testing with smbclient">Test with <span class="application">smbclient</span></a> now. +<a href="domain-member.html#ads-create-machine-account" title="Create the computer account">Creating a computer account</a> +and <a href="domain-member.html#ads-test-server" title="Test your server setup">testing your servers</a> +is only needed if you want Kerberos support for <span class="application">smbd</span> and <span class="application">winbindd</span>. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-create-machine-account"></a>Create the computer account</h3></div></div><div></div></div><p> +As a user that has write permission on the Samba private directory +(usually root) run: +</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="id2892592"></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 + <i class="replaceable"><tt>USERNAME</tt></i>@<i class="replaceable"><tt>REALM</tt></i></tt></b>. + <i class="replaceable"><tt>USERNAME</tt></i> must be a user who has rights to add a machine + to the domain. </p></dd></dl></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-server"></a>Test your server setup</h3></div></div><div></div></div><p> +If the join was successful, you will see a new computer account with the +NetBIOS name of your Samba server in Active Directory (in the "Computers" +folder under Users and Computers. +</p><p> +On a Windows 2000 client try <b class="userinput"><tt>net use * \\server\share</tt></b>. You should +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="id2892719"></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="id2892751"></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="id2892773"></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 “<span class="quote">little</span>” things that can go wrong. +It is particularly interesting how often subscribers on the samba mailing list have concluded +after repeated failed attempts to add a machine account that it is necessary to "re-install" +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="id2892816"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p> +“<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 +exists on the network - I know it doesn't. Why is this failing?</span>” +</p><p> +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="id2892848"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p> + “<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>” +</p><p> +You should check that there is an <a class="indexterm" name="id2892875"></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="id2892900"></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> +Possible causes include: +</p><div class="itemizedlist"><ul type="disc"><li><p> + The script does not actually exist, or could not be located in the path specified. + </p><p> + <span class="emphasis"><em>Corrective Action:</em></span> Fix it. Make sure that when run manually + that the script will add both the UNIX system account _and_ the Samba SAM account. + </p></li><li><p> + The machine could not be added to the UNIX system accounts file <tt class="filename">/etc/passwd</tt> + </p><p> + <span class="emphasis"><em>Corrective Action:</em></span> Check that the machine name is a legal UNIX + system account name. ie: If the UNIX utility <b class="command">useradd</b> is called + 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 class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892992"></a>I can't join a Windows 2003 PDC</h3></div></div><div></div></div><p>Windows 2003 requires SMB signing. Client side SMB signing has + only been implemented partially in Samba 3.0. Set <a class="indexterm" name="id2893004"></a><i class="parameter"><tt>client use spnego</tt></i> = no when communicating + with a windows 2003 server. </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Backup Domain Control </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 8. Stand-Alone Servers</td></tr></table></div></body></html> diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html new file mode 100644 index 0000000000..39d317e8cf --- /dev/null +++ b/docs/htmldocs/groupmapping.html @@ -0,0 +1,196 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 12. Mapping MS Windows and UNIX Groups</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="passdb.html" title="Chapter 11. Account Information Databases"><link rel="next" href="AccessControls.html" title="Chapter 13. File, Directory and Share Access Controls"></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 12. Mapping MS Windows and UNIX Groups</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="AccessControls.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt><a href="groupmapping.html#id2903416">Discussion</a></dt><dd><dl><dt><a href="groupmapping.html#id2903652">Example Configuration</a></dt></dl></dd><dt><a href="groupmapping.html#id2903718">Configuration Scripts</a></dt><dd><dl><dt><a href="groupmapping.html#id2903732">Sample smb.conf add group script</a></dt><dt><a href="groupmapping.html#id2903817">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="groupmapping.html#id2903900">Common Errors</a></dt><dd><dl><dt><a href="groupmapping.html#id2903915">Adding Groups Fails</a></dt><dt><a href="groupmapping.html#id2903984">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="groupmapping.html#id2904010">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></div><a class="indexterm" name="id2903109"></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="id2903150"></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="id2903181"></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="id2903197"></a><a class="indexterm" name="id2903205"></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="id2903232"></a><i class="parameter"><tt>idmap uid</tt></i>/<a class="indexterm" name="id2903245"></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="id2903314"></a><a class="indexterm" name="id2903322"></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 + to any limits imposed by these tools. If the tool does NOT allow upper case characters + 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="id2903374"></a><a class="indexterm" name="id2903382"></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) + back to the calling Samba interface. This will provide a dynamic work-around solution. + </p><p> + 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="id2903416"></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="id2903445"></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'. + </p><p> + When an MS Windows NT4 / W200x is made a domain member, the "Domain Admins" group of the + PDC is added to the local 'Administrators' group of the workstation. Every member of the + 'Domain Administrators' group inherits the rights of the local 'Administrators' group when + logging on the workstation. + </p><p> + The following steps describe how to make Samba PDC users members of the 'Domain Admins' group? + </p><div class="orderedlist"><ol type="1"><li><p> + create a unix group (usually in <tt class="filename">/etc/group</tt>), let's call it domadm + </p></li><li><p>add to this group the users that must be Administrators. For example + if you want joe, john and mary, your entry in <tt class="filename">/etc/group</tt> will + look like: + </p><pre class="programlisting"> + domadm:x:502:joe,john,mary + </pre><p> + </p></li><li><p> + Map this domadm group to the "Domain Admins" group by running the command: + </p><p> +</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="id2903569"></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="id2903594"></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, + you would flag that group as a domain group by running the following on the Samba PDC: + </p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</tt></b> +</pre><p> + </p><p> + Be aware that the RID parameter is a unsigned 32 bit integer that should + normally start at 1000. However, this rid must not overlap with any RID assigned + 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="id2903652"></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> +</p><pre class="screen"> +<tt class="prompt">root# </tt> <b class="userinput"><tt>net groupmap list</tt></b> +System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin +Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin +Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser +Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> 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="id2903718"></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="id2903732"></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="id2903754"></a><p class="title"><b>Example 12.1. smbgrpadd.sh</b></p><pre class="programlisting"> + +#!/bin/bash + +# Add the group using normal system groupadd tool. +groupadd smbtmpgrp00 + +thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3` + +# Now change the name to what we want for the MS Windows networking end +cp /etc/group /etc/group.bak +cat /etc/group.bak | sed s/smbtmpgrp00/$1/g > /etc/group + +# Now return the GID as would normally happen. +echo $thegid +exit 0 +</pre></div><p> +</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="id2903817"></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> +</p><pre class="programlisting"> +#!/bin/bash + +net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin +net groupmap modify ntgroup="Domain Users" unixgroup=users +net groupmap modify ntgroup="Domain Guests" unixgroup=nobody +net groupmap modify ntgroup="Administrators" unixgroup=root +net groupmap modify ntgroup="Users" unixgroup=users +net groupmap modify ntgroup="Guests" unixgroup=nobody +net groupmap modify ntgroup="System Operators" unixgroup=sys +net groupmap modify ntgroup="Account Operators" unixgroup=root +net groupmap modify ntgroup="Backup Operators" unixgroup=bin +net groupmap modify ntgroup="Print Operators" unixgroup=lp +net groupmap modify ntgroup="Replicators" unixgroup=daemon +net groupmap modify ntgroup="Power Users" unixgroup=sys + +groupadd Orks +groupadd Elves +groupadd Gnomes + +net groupmap add ntgroup="Orks" unixgroup=Orks type=d +net groupmap add ntgroup="Elves" unixgroup=Elves type=d +net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d +</pre><p> +</p><p> + 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="id2903900"></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="id2903915"></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="id2903935"></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 + that has either an upper case character and/or a space character in it. + </p><p> + There are three possible work-arounds. Firstly, use only group names that comply + with the limitations of the UNIX/Linux <b class="command">groupadd</b> system tool. + The second involves use of the script mentioned earlier in this chapter, and the + 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="id2903984"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><a class="indexterm" name="id2903992"></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="id2904010"></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>“<span class="quote"> + What must I do to add Domain Users to the Power Users group? + </span>”</p><p> + The Power Users group is a group that is local to each Windows + 200x / XP Professional workstation. You can not add the Domain Users group to the Power Users + 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="id2904048"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="passdb.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="AccessControls.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 11. Account Information Databases </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 13. File, Directory and Share Access Controls</td></tr></table></div></body></html> diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html new file mode 100644 index 0000000000..73971d2a72 --- /dev/null +++ b/docs/htmldocs/integrate-ms-networks.html @@ -0,0 +1,415 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 26. Integrating MS Windows networks with Samba</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="pam.html" title="Chapter 25. PAM based Distributed Authentication"><link rel="next" href="unicode.html" title="Chapter 27. Unicode/Charsets"></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 26. Integrating MS Windows networks with Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pam.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="unicode.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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="integrate-ms-networks.html#id2951812">Features and Benefits</a></dt><dt><a href="integrate-ms-networks.html#id2951838">Background Information</a></dt><dt><a href="integrate-ms-networks.html#id2951903">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2951960">/etc/hosts</a></dt><dt><a href="integrate-ms-networks.html#id2952110">/etc/resolv.conf</a></dt><dt><a href="integrate-ms-networks.html#id2952153">/etc/host.conf</a></dt><dt><a href="integrate-ms-networks.html#id2952204">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2952319">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2952629">The NetBIOS Name Cache</a></dt><dt><a href="integrate-ms-networks.html#id2952692">The LMHOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2952854">HOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2952886">DNS Lookup</a></dt><dt><a href="integrate-ms-networks.html#id2952918">WINS Lookup</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2953036">Common Errors</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2953052">Pinging works only in one way</a></dt><dt><a href="integrate-ms-networks.html#id2953086">Very Slow Network Connections</a></dt><dt><a href="integrate-ms-networks.html#id2953137">Samba server name change problem</a></dt></dl></dd></dl></div><a class="indexterm" name="id2951782"></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 +NetBIOS over TCP/IP then this section may help you to resolve networking problems. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS + over Logical Link Control (LLC). On modern networks it is highly advised + to NOT run NetBEUI at all. Note also that there is NO such thing as + NetBEUI over TCP/IP - the existence of such a protocol is a complete + and utter mis-apprehension. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2951812"></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 +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="id2951838"></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 +TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be +used and UDP port 137 and TCP port 139 will not. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then +the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet +Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic). +</p></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="id2951878"></a> +Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). +<a class="indexterm" name="id2951891"></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="id2951903"></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="id2951960"></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"> +127.0.0.1 localhost localhost.localdomain +192.168.1.1 bigbox.caldera.com bigbox alias4box +</pre><p> +The purpose of <tt class="filename">/etc/hosts</tt> is to provide a +name resolution mechanism so that uses do not need to remember +IP addresses. +</p><p> +Network packets that are sent over the physical network transport +layer communicate not via IP addresses but rather using the Media +Access Control address, or MAC address. IP addresses are currently +32 bits in length and are typically presented as four (4) decimal +numbers that are separated by a dot (or period). eg: 168.192.1.1. +</p><a class="indexterm" name="id2952009"></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 +</p><p> +Every network interface must have an MAC address. Associated with +a MAC address there may be one or more IP addresses. There is NO +relationship between an IP address and a MAC address, all such assignments +are arbitrary or discretionary in nature. At the most basic level all +network communications takes place using MAC addressing. Since MAC +addresses must be globally unique, and generally remains fixed for +any particular interface, the assignment of an IP address makes sense +from a network management perspective. More than one IP address can +be assigned per MAC address. One address must be the primary IP address, +this is the address that will be returned in the ARP reply. +</p><p> +When a user or a process wants to communicate with another machine +the protocol implementation ensures that the "machine name" or "host +name" is resolved to an IP address in a manner that is controlled +by the TCP/IP configuration control files. The file +<tt class="filename">/etc/hosts</tt> is one such file. +</p><p> +When the IP address of the destination interface has been +determined a protocol called ARP/RARP is used to identify +the MAC address of the target interface. ARP stands for Address +Resolution Protocol, and is a broadcast oriented method that +uses UDP (User Datagram Protocol) to send a request to all +interfaces on the local network segment using the all 1's MAC +address. Network interfaces are programmed to respond to two +MAC addresses only; their own unique address and the address +ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will +contain the MAC address and the primary IP address for each +interface. +</p><a class="indexterm" name="id2952082"></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 +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="id2952110"></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 + </p></li><li><p>The name(s) of any domains that should be + automatically searched when trying to resolve unqualified + host names to their IP address + </p></li><li><p>The name or IP address of available Domain + Name Servers that may be asked to perform name to address + translation lookups + </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952153"></a><tt class="filename">/etc/host.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2952165"></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 +which name resolution may proceed. The typical structure is: +</p><pre class="programlisting"> +order hosts,bind +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="id2952204"></a><tt class="filename">/etc/nsswitch.conf</tt></h3></div></div><div></div></div><a class="indexterm" name="id2952216"></a><p> +This file controls the actual name resolution targets. The +file typically has resolver object specifications as follows: +</p><pre class="programlisting"> +# /etc/nsswitch.conf +# +# Name Service Switch configuration file. +# + +passwd: compat +# Alternative entries for password authentication are: +# passwd: compat files nis ldap winbind +shadow: compat +group: compat + +hosts: files nis dns +# Alternative entries for host name resolution are: +# hosts: files dns nis nis+ hesiod db compat ldap wins +networks: nis files dns + +ethers: nis files +protocols: nis files +rpc: nis files +services: nis files +</pre><p> +Of course, each of these mechanisms requires that the appropriate +facilities and/or services are correctly configured. +</p><p> +It should be noted that unless a network request/message must be +sent, TCP/IP networks are silent. All TCP/IP communications assumes a +principal of speaking only when necessary. +</p><a class="indexterm" name="id2952270"></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 +Addresses. To gain this functionality Samba needs to be compiled +with appropriate arguments to the make command (i.e.: <b class="userinput"><tt>make +nsswitch/libnss_wins.so</tt></b>). The resulting library should +then be installed in the <tt class="filename">/lib</tt> directory and +the "wins" parameter needs to be added to the "hosts:" line in +the <tt class="filename">/etc/nsswitch.conf</tt> file. At this point it +will be possible to ping any MS Windows machine by 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="id2952319"></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", +or "SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a +simple name with which the machine is associated. All NetBIOS names +are exactly 16 characters in length. The 16th character is reserved. +It is used to store a one byte value that indicates service level +information for the NetBIOS name that is registered. A NetBIOS machine +name is therefore registered for each service type that is provided by +the client/server. +</p><p> +The following are typical NetBIOS name/service type registrations: +</p><div class="table"><a name="id2952372"></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<00></td><td align="justify">Server Service is running on MACHINENAME</td></tr><tr><td align="left">MACHINENAME<03></td><td align="justify">Generic Machine Name (NetBIOS name)</td></tr><tr><td align="left">MACHINENAME<20></td><td align="justify">LanMan Server service is running on MACHINENAME</td></tr><tr><td align="left">WORKGROUP<1b></td><td align="justify">Domain Master Browser</td></tr></tbody></table></div><div class="table"><a name="id2952442"></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<03></td><td align="justify">Generic Name registered by all members of WORKGROUP</td></tr><tr><td align="left">WORKGROUP<1c></td><td align="justify">Domain Controllers / Netlogon Servers</td></tr><tr><td align="left">WORKGROUP<1d></td><td align="justify">Local Master Browsers</td></tr><tr><td align="left">WORKGROUP<1e></td><td align="justify">Internet Name Resolvers</td></tr></tbody></table></div><p> +<a class="indexterm" name="id2952514"></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="id2952529"></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 +be needed. An example of this is what happens when an MS Windows client +wants to locate a domain logon server. It finds this service and the IP +address of a server that provides it by performing a lookup (via a +NetBIOS broadcast) for enumeration of all machines that have +registered the name type *<1c>. A logon request is then sent to each +IP address that is returned in the enumerated list of IP addresses. +Whichever machine first replies then ends up providing the logon services. +</p><p> +The name "workgroup" or "domain" really can be confusing since these +have the added significance of indicating what is the security +architecture of the MS Windows network. The term "workgroup" indicates +that the primary nature of the network environment is that of a +peer-to-peer design. In a WORKGROUP all machines are responsible for +their own security, and generally such security is limited to use of +just a password (known as SHARE MODE security). In most situations +with peer-to-peer networking the users who control their own machines +will simply opt to have no security at all. It is possible to have +USER MODE security in a WORKGROUP environment, thus requiring use +of a user name and a matching password. +</p><p> +MS Windows networking is thus predetermined to use machine names +for all local and remote machine message passing. The protocol used is +called Server Message Block (SMB) and this is implemented using +the NetBIOS protocol (Network Basic Input Output System). NetBIOS can +be encapsulated using LLC (Logical Link Control) protocol - in which case +the resulting protocol is called NetBEUI (Network Basic Extended User +Interface). NetBIOS can also be run over IPX (Internetworking Packet +Exchange) protocol as used by Novell NetWare, and it can be run +over TCP/IP protocols - in which case the resulting protocol is called +NBT or NetBT, the NetBIOS over TCP/IP. +</p><p> +MS Windows machines use a complex array of name resolution mechanisms. +Since we are primarily concerned with TCP/IP this demonstration is +limited to this area. +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952629"></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 +past 10-15 minutes. It is more efficient to obtain an IP address +for a machine from the local cache than it is to go through all the +configured name resolution mechanisms. +</p><p> +If a machine whose name is in the local name cache has been shut +down before the name had been expired and flushed from the cache, then +an attempt to exchange a message with that machine will be subject +to time-out delays. i.e.: Its name is in the cache, so a name resolution +lookup will succeed, but the machine can not respond. This can be +frustrating for users - but it is a characteristic of the protocol. +</p><a class="indexterm" name="id2952661"></a><a class="indexterm" name="id2952669"></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="id2952692"></a>The LMHOSTS file</h3></div></div><div></div></div><a class="indexterm" name="id2952700"></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 +<tt class="filename">LMHOSTS</tt> file performs NetBIOS name +to IP address mapping. +</p><p> +It typically looks like: +</p><pre class="programlisting"> +# Copyright (c) 1998 Microsoft Corp. +# +# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS +# over TCP/IP) stack for Windows98 +# +# This file contains the mappings of IP addresses to NT computernames +# (NetBIOS) names. Each entry should be kept on an individual line. +# The IP address should be placed in the first column followed by the +# corresponding computername. The address and the computername +# should be separated by at least one space or tab. The "#" character +# is generally used to denote the start of a comment (see the exceptions +# below). +# +# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts +# files and offers the following extensions: +# +# #PRE +# #DOM:<domain> +# #INCLUDE <filename> +# #BEGIN_ALTERNATE +# #END_ALTERNATE +# \0xnn (non-printing character support) +# +# Following any entry in the file with the characters "#PRE" will cause +# the entry to be preloaded into the name cache. By default, entries are +# not preloaded, but are parsed only after dynamic name resolution fails. +# +# Following an entry with the "#DOM:<domain>" tag will associate the +# entry with the domain specified by <domain>. This affects how the +# browser and logon services behave in TCP/IP environments. To preload +# the host name associated with #DOM entry, it is necessary to also add a +# #PRE to the line. The <domain> is always preloaded although it will not +# be shown when the name cache is viewed. +# +# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) +# software to seek the specified <filename> and parse it as if it were +# local. <filename> is generally a UNC-based name, allowing a +# centralized lmhosts file to be maintained on a server. +# It is ALWAYS necessary to provide a mapping for the IP address of the +# server prior to the #INCLUDE. This mapping must use the #PRE directive. +# In addition the share "public" in the example below must be in the +# LanManServer list of "NullSessionShares" in order for client machines to +# be able to read the lmhosts file successfully. This key is under +# \machine\system\currentcontrolset\services\lanmanserver\ +# parameters\nullsessionshares +# in the registry. Simply add "public" to the list found there. +# +# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE +# statements to be grouped together. Any single successful include +# will cause the group to succeed. +# +# Finally, non-printing characters can be embedded in mappings by +# first surrounding the NetBIOS name in quotations, then using the +# \0xnn notation to specify a hex value for a non-printing character. +# +# The following example illustrates all of these extensions: +# +# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC +# 102.54.94.102 "appname \0x14" #special app server +# 102.54.94.123 popular #PRE #source server +# 102.54.94.117 localsrv #PRE #needed for the include +# +# #BEGIN_ALTERNATE +# #INCLUDE \\localsrv\public\lmhosts +# #INCLUDE \\rhino\public\lmhosts +# #END_ALTERNATE +# +# In the above example, the "appname" server contains a special +# character in its name, the "popular" and "localsrv" server names are +# preloaded, and the "rhino" server name is specified so it can be used +# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" +# system is unavailable. +# +# Note that the whole file is parsed including comments on each lookup, +# so keeping the number of comments to a minimum will improve performance. +# Therefore it is not advisable to simply add lmhosts file entries onto the +# end of this file. +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952854"></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="id2952886"></a>DNS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2952894"></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 +Node Type parameter is configured. A Node Type of 0 means that +NetBIOS broadcast (over UDP broadcast) is used if the name +that is the subject of a name lookup is not found in the NetBIOS name +cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to +Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the +WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast +lookup is used. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952918"></a>WINS Lookup</h3></div></div><div></div></div><a class="indexterm" name="id2952927"></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 +if the TCP/IP setup has been given at least one WINS Server IP Address. +</p><p> +To configure Samba to be a WINS server the following parameter needs +to be added to the <tt class="filename">smb.conf</tt> file: +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>wins support = Yes</tt></i></td></tr></table><p> +To configure Samba to use a WINS server the following parameters are +needed in the <tt class="filename">smb.conf</tt> file: +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>wins support = No</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = xxx.xxx.xxx.xxx</tt></i></td></tr></table><p> +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.html" 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="id2953036"></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="id2953052"></a>Pinging works only in one way</h3></div></div><div></div></div><p> + “<span class="quote">I can ping my samba server from Windows, but I can + not ping my Windows machine from the samba server.</span>” + </p><p> + The Windows machine was at IP Address 192.168.1.2 with netmask 255.255.255.0, the + Samba server (Linux) was at IP Address 192.168.1.130 with netmask 255.255.255.128. + The machines were on a local network with no external connections. + </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="id2953086"></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="id2953137"></a>Samba server name change problem</h3></div></div><div></div></div><p> + “<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>” + </p><p> + From this description three (3) things are rather obvious: + </p><div class="itemizedlist"><ul type="disc"><li><p>WINS is NOT in use, only broadcast based name resolution is used</p></li><li><p>The samba server was renamed and restarted within the last 10-15 minutes</p></li><li><p>The old samba server name is still in the NetBIOS name cache on the MS Windows NT4 Workstation</p></li></ul></div><p> + To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine, + open a cmd shell, then: + </p><p> +</p><pre class="screen"> +<tt class="prompt">C:\> </tt><b class="userinput"><tt>nbtstat -n</tt></b> + + NetBIOS Local Name Table + + Name Type Status +------------------------------------------------ +FRODO <03> UNIQUE Registered +ADMINSTRATOR <03> UNIQUE Registered +FRODO <00> UNIQUE Registered +SARDON <00> GROUP Registered +FRODO <20> UNIQUE Registered +FRODO <1F> UNIQUE Registered + + +<tt class="prompt">C:\> </tt>nbtstat -c + + NetBIOS Remote Cache Name Table + + Name Type Host Address Life [sec] +-------------------------------------------------------------- +GANDALF <20> UNIQUE 192.168.1.1 240 + +<tt class="prompt">C:\> </tt> +</pre><p> + </p><p> + In the above example, GANDALF is the Samba server and FRODO is the MS Windows NT4 Workstation. + 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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="pam.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="unicode.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 25. PAM based Distributed Authentication </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 27. Unicode/Charsets</td></tr></table></div></body></html> diff --git a/docs/htmldocs/ix01.html b/docs/htmldocs/ix01.html new file mode 100644 index 0000000000..6e09e98de4 --- /dev/null +++ b/docs/htmldocs/ix01.html @@ -0,0 +1,39 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="samba-doc.html" title="SAMBA Project Documentation"><link rel="previous" href="Further-Resources.html" title="Chapter 41. Further Resources"></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">Index</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Further-Resources.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2965347"></a>Index</h2></div></div><div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>"Domain Admins" group, <a href="groupmapping.html#id2903416">Discussion</a></dt><dt>"Domain Users" group, <a href="groupmapping.html#id2904010">Adding Domain Users to the Power Users group</a></dt><dt>"Printers" folder, <a href="CUPS-printing.html#id2931562">Caveats to be considered</a>, <a href="CUPS-printing.html#id2932789">Installing the PostScript Driver on a Client</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt>"raw" printing, <a href="CUPS-printing.html#id2924825">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt>/etc/host.conf, <a href="integrate-ms-networks.html#id2952153">/etc/host.conf</a></dt><dt>/etc/hosts, <a href="integrate-ms-networks.html#id2951960">/etc/hosts</a></dt><dt>/etc/nsswitch.conf, <a href="integrate-ms-networks.html#id2952204">/etc/nsswitch.conf</a></dt><dt>8.3</dt><dd><dl><dt>file names, <a href="AccessControls.html#id2904431">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.html">File, Directory and Share Access Controls</a></dt><dt>Active Directory, <a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></dt><dt>add group script, <a href="groupmapping.html#id2903915">Adding Groups Fails</a></dt><dt>add machine script, <a href="samba-pdc.html#id2889059">The machine trust account not accessible</a>, <a href="domain-member.html#id2892848">Adding Machine to Domain Fails</a></dt><dt>add printer command, <a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a></dt><dt>add printer wizard, <a href="CUPS-printing.html#id2925177">Three familiar Methods for driver upload plus a new one</a></dt><dt>add user script, <a href="passdb.html#id2899165">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt>addprinter command, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>admin users, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="AccessControls.html#id2908232">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt>Administrator, <a href="groupmapping.html#id2903416">Discussion</a></dt><dt>ADS (see Active Directory)</dt><dt>ads server, <a href="domain-member.html#id2892246">Setup your smb.conf</a></dt><dt>application/cups.vnd-postscript, <a href="CUPS-printing.html#id2931837">Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/octet-stream, <a href="CUPS-printing.html#id2924971">Explicitly enable "raw" printing for +application/octet-stream!</a>, <a href="CUPS-printing.html#id2926707">MIME type Conversion Rules</a>, <a href="CUPS-printing.html#id2928335">"application/octet-stream" printing</a></dt><dt>application/pdf, <a href="CUPS-printing.html#id2926501">MIME types and CUPS Filters</a></dt><dt>application/postscript, <a href="CUPS-printing.html#id2931837">Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt>application/vnd.cups-raster, <a href="CUPS-printing.html#id2928581">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt>application/vnd.cups-raw, <a href="CUPS-printing.html#id2924971">Explicitly enable "raw" printing for +application/octet-stream!</a></dt><dt>auth methods, <a href="passdb.html#id2902952">auth methods does not work</a>, <a href="upgrading-to-3.0.html#id2955156">Passdb Backends and Authentication</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>bind interfaces only, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>brlock.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>browse list, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#id2897133">Technical Overview of browsing</a></dt><dt>browseable, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>case sensitive, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a>, <a href="ProfileMgmt.html#id2946186">Windows 9x / Me Profile Setup</a></dt><dt>chpass, <a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt><dt>client use spnego, <a href="domain-member.html#id2892992">I can't join a Windows 2003 PDC</a></dt><dt>comment, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt><dt>configure, <a href="compiling.html#id2961798">Building the Binaries</a></dt><dt>connections.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>core files, <a href="bugreport.html#id2960926">Internal errors</a></dt><dt>create mask, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>csc policy, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>CUPS</dt><dd><dl><dt>Page Accounting, <a href="CUPS-printing.html#id2937141">Page Accounting with CUPS</a></dt><dt>quotas, <a href="CUPS-printing.html#id2937193">Setting up Quotas</a></dt></dl></dd><dt>CUPS-PPD, <a href="CUPS-printing.html#id2936123">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>cupsaddsmb, <a href="CUPS-printing.html#id2925177">Three familiar Methods for driver upload plus a new one</a>, <a href="CUPS-printing.html#id2930710">cupsaddsmb: the unknown Utility</a>, <a href="CUPS-printing.html#id2931562">Caveats to be considered</a>, <a href="CUPS-printing.html#id2932052">Run "cupsaddsmb" (quiet Mode)</a>, <a href="CUPS-printing.html#id2932180">Run "cupsaddsmb" with verbose Output</a>, <a href="CUPS-printing.html#id2932401">Understanding cupsaddsmb</a>, <a href="CUPS-printing.html#id2932633">cupsaddsmb with a Samba PDC</a>, <a href="CUPS-printing.html#id2932714">cupsaddsmb Flowchart</a></dt><dt>cupsomatic, <a href="CUPS-printing.html#id2926179">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="CUPS-printing.html#id2926306">The CUPS Filtering Architecture</a>, <a href="CUPS-printing.html#id2928022">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="CUPS-printing.html#id2928848">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a>, <a href="CUPS-printing.html#id2936123">cupsomatic, pdqomatic, lpdomatic, directomatic</a></dt><dt>CVS, <a href="compiling.html#id2961265">Access Samba source code via CVS</a></dt><dd><dl><dt>web, <a href="compiling.html#id2961335">Access via CVSweb</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>daemon, <a href="compiling.html#id2962499">Alternative: starting it as a daemon</a></dt><dt>DDK, <a href="CUPS-printing.html#id2930614">PostScript Drivers with no major problems -- even in Kernel +Mode</a>, <a href="CUPS-printing.html#id2931030">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>debug, <a href="bugreport.html#id2960926">Internal errors</a></dt><dt>debug level, <a href="problems.html#id2959768">Debugging with Samba itself</a>, <a href="speed.html#id2964453">Log level</a></dt><dt>debuglevel, <a href="bugreport.html#id2960718">Debug levels</a></dt><dt>default case, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>delete printer command, <a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a></dt><dt>deleteprinter command, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>DHCP, <a href="integrate-ms-networks.html#id2951838">Background Information</a></dt><dt>diff, <a href="bugreport.html#id2961107">Patches</a></dt><dt>directory mask, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a></dt><dt>directory security mask, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>disable spoolss, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>display charset, <a href="unicode.html#id2953454">Samba and charsets</a></dt><dt>DNS, <a href="NetworkBrowsing.html#id2894584">TCP/IP - without NetBIOS</a>, <a href="integrate-ms-networks.html#id2952886">DNS Lookup</a></dt><dd><dl><dt>Active Directory, <a href="NetworkBrowsing.html#id2894750">DNS and Active Directory</a></dt><dt>Dynamic, <a href="integrate-ms-networks.html#id2951838">Background Information</a></dt></dl></dd><dt>dns proxy, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>domain admin group, <a href="groupmapping.html">Mapping MS Windows and UNIX Groups</a></dt><dt>domain logons, <a href="samba-pdc.html#id2887335">Preparing for Domain Control</a></dt><dt>domain master, <a href="samba-pdc.html#id2888272">Domain Network Logon Service</a>, <a href="samba-bdc.html#id2890011">Example Configuration</a>, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#id2895844">Making Samba the domain master</a></dt><dt>dont descend, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>dos charset, <a href="unicode.html#id2953454">Samba and charsets</a>, <a href="unicode.html#id2953612">Japanese charsets</a>, <a href="unicode.html#id2953758">CP850.so can't be found</a></dt><dt>dos filemode, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a></dt><dt>dos filetime resolution, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>dos filetimes, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>EMF, <a href="CUPS-printing.html#id2925497">Windows Drivers, GDI and EMF</a>, <a href="CUPS-printing.html#id2929677">From Windows Clients to an NT Print Server</a>, <a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a></dt><dt>encrypt passwords, <a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a>, <a href="passdb.html#id2899942">smbpasswd - Encrypted Password Database</a>, <a href="pam.html#id2950929">smb.conf PAM Configuration</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>enhanced browsing, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>enumports command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2922594">Samba and Printer Ports</a></dt><dt>EPM (see ESP meta packager)</dt><dt>ESC/P, <a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a></dt><dt>ESP</dt><dd><dl><dt>Ghostscript, <a href="CUPS-printing.html#id2926306">The CUPS Filtering Architecture</a>, <a href="CUPS-printing.html#id2928848">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a></dt><dt>meta packager, <a href="CUPS-printing.html#id2931030">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt>Print Pro, <a href="CUPS-printing.html#id2929420">Sources of CUPS drivers / PPDs</a>, <a href="CUPS-printing.html#id2931493">ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"</a></dt></dl></dd><dt>Extended Attributes, <a href="AccessControls.html">File, Directory and Share Access Controls</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>fake oplocks, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>File System, <a href="AccessControls.html#id2904395">File System Access Controls</a></dt><dt>foomatic, <a href="CUPS-printing.html#id2926179">CUPS can use all Windows-formatted Vendor PPDs</a>, <a href="CUPS-printing.html#id2926306">The CUPS Filtering Architecture</a>, <a href="CUPS-printing.html#id2928022">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="CUPS-printing.html#id2928848">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a>, <a href="CUPS-printing.html#id2935871">foomatic-rip and Foomatic explained</a>, <a href="CUPS-printing.html#id2936022">Foomatic's strange Name</a></dt><dt>foomatic-rip, <a href="CUPS-printing.html#id2928848">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a>, <a href="CUPS-printing.html#id2935716">CUPS Print Drivers from Linuxprinting.org</a>, <a href="CUPS-printing.html#id2935871">foomatic-rip and Foomatic explained</a>, <a href="CUPS-printing.html#id2936304">The Grand Unification +achieved...</a></dt><dt>force create mode, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>force directory mode, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>force directory security mode, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>force group, <a href="AccessControls.html#id2905070">User and Group Based Controls</a></dt><dt>force security mode, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>force user, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="AccessControls.html#id2908232">I have set force user but Samba still makes root the owner of all the files I touch!</a>, <a href="locking.html#id2909231">Beware of Force User</a></dt><dt>ftp, <a href="compiling.html#id2961581">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gdb, <a href="bugreport.html#id2960926">Internal errors</a></dt><dt>GDI, <a href="CUPS-printing.html#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="CUPS-printing.html#id2925497">Windows Drivers, GDI and EMF</a>, <a href="CUPS-printing.html#id2929677">From Windows Clients to an NT Print Server</a>, <a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a></dt><dt>GhostScript, <a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a href="CUPS-printing.html#id2925951">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="groupmapping.html#id2903181">Features and Benefits</a></dt><dt>GPG, <a href="compiling.html#id2961644">Verifying Samba's PGP signature</a></dt><dt>groupadd, <a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt>groupdel, <a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt>groups</dt><dd><dl><dt>domain, <a href="groupmapping.html#id2903416">Discussion</a></dt><dt>mapping, <a href="groupmapping.html">Mapping MS Windows and UNIX Groups</a></dt><dt>nested, <a href="groupmapping.html#id2903984">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd><dt>guest account, <a href="NetworkBrowsing.html#id2897308">Problem resolution</a>, <a href="NetworkBrowsing.html#id2898121">My client reports "This server is not configured to list shared resources"</a>, <a href="printing.html#id2915245">The [printers] Section</a></dt><dt>guest ok, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hide dot files, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>hide files, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>hide unreadable, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a></dt><dt>hide unwriteable files, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a></dt><dt>host msdfs, <a href="msdfs.html#id2912546">Features and Benefits</a></dt><dt>hosts allow, <a href="securing-samba.html#id2910816">Using host based protection</a>, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt><dt>hosts deny, <a href="securing-samba.html#id2910816">Using host based protection</a>, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt>idmap gid, <a href="groupmapping.html#id2903181">Features and Benefits</a>, <a href="pam.html#id2951576">Winbind is not resolving users and groups</a></dt><dt>idmap uid, <a href="groupmapping.html#id2903181">Features and Benefits</a>, <a href="pam.html#id2951576">Winbind is not resolving users and groups</a></dt><dt>ifconfig, <a href="compiling.html#id2962252">Starting from inetd.conf</a></dt><dt>imprints, <a href="CUPS-printing.html#id2925177">Three familiar Methods for driver upload plus a new one</a></dt><dt>inetd, <a href="diagnosis.html#id2958249">The tests</a>, <a href="compiling.html#id2962144">Starting the smbd and nmbd</a>, <a href="compiling.html#id2962252">Starting from inetd.conf</a></dt><dt>Interdomain Trusts, <a href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dd><dl><dt>completing, <a href="InterdomainTrusts.html#id2911822">Completing an NT4 Domain Trust</a></dt><dt>creating, <a href="InterdomainTrusts.html#id2911721">Native MS Windows NT4 Trusts Configuration</a></dt><dt>Facilities, <a href="InterdomainTrusts.html#id2911868">Inter-Domain Trust Facilities</a></dt></dl></dd><dt>interfaces, <a href="NetworkBrowsing.html#id2896045">Multiple interfaces</a>, <a href="diagnosis.html#id2958249">The tests</a>, <a href="compiling.html#id2962252">Starting from inetd.conf</a></dt><dt>invalid users, <a href="AccessControls.html#id2905070">User and Group Based Controls</a></dt><dt>IPP, <a href="CUPS-printing.html#id2932401">Understanding cupsaddsmb</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>KDC, <a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></dt><dt>Kerberos, <a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></dt><dt>kinit, <a href="domain-member.html#id2892373">Setup your /etc/krb5.conf</a></dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>ldap admin dn, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap delete dn, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap filter, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap machine suffix, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap passwd sync, <a href="passdb.html#id2900704">Configuring Samba</a>, <a href="passdb.html#id2901824">Password synchronisation</a></dt><dt>ldap ssl, <a href="passdb.html#id2900704">Configuring Samba</a>, <a href="passdb.html#id2901140">Security and sambaSamAccount</a></dt><dt>ldap suffix, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap trust ids, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>ldap user suffix, <a href="passdb.html#id2900704">Configuring Samba</a></dt><dt>libnss_wins.so, <a href="integrate-ms-networks.html#id2952204">/etc/nsswitch.conf</a></dt><dt>Links</dt><dd><dl><dt>hard, <a href="AccessControls.html#id2904431">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>soft, <a href="AccessControls.html#id2904431">MS Windows NTFS Comparison with UNIX File Systems</a></dt></dl></dd><dt>Linuxprinting.org, <a href="CUPS-printing.html#id2935716">CUPS Print Drivers from Linuxprinting.org</a></dt><dt>lm announce, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>lm interval, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>LMB (see Local Master Browser)</dt><dt>LMHOSTS, <a href="integrate-ms-networks.html#id2952692">The LMHOSTS file</a></dt><dt>load printers, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914010">A little Experiment to warn you</a>, <a href="printing.html#id2914714">The [global] Section</a></dt><dt>local master, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#DMB">Setting up WORKGROUP Browsing</a></dt><dt>Local Master Browser, <a href="NetworkBrowsing.html#id2896081">Use of the Remote Announce parameter</a></dt><dt>locking, <a href="locking.html#id2908589">Discussion</a></dt><dt>locking.tdb, <a href="CUPS-printing.html#id2935118">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="diagnosis.html#id2958022">Assumptions</a></dt></dl></dd><dt>log level, <a href="domain-member.html#id2892848">Adding Machine to Domain Fails</a>, <a href="VFS.html#id2940474">extd_audit</a>, <a href="bugreport.html#id2960718">Debug levels</a></dt><dt>logon drive, <a href="ProfileMgmt.html#id2946726">Windows NT4 Workstation</a></dt><dt>logon home, <a href="passdb.html#id2901300">LDAP special attributes for sambaSamAccounts</a>, <a href="ProfileMgmt.html#id2945807">Windows 9x / Me User Profiles</a>, <a href="ProfileMgmt.html#id2945938">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="ProfileMgmt.html#id2946726">Windows NT4 Workstation</a>, <a href="ProfileMgmt.html#id2947427">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon path, <a href="passdb.html#id2901300">LDAP special attributes for sambaSamAccounts</a>, <a href="ProfileMgmt.html#id2945938">Mixed Windows 9x / Me and Windows NT4/200x User Profiles</a>, <a href="ProfileMgmt.html#id2946186">Windows 9x / Me Profile Setup</a>, <a href="ProfileMgmt.html#id2946726">Windows NT4 Workstation</a>, <a href="ProfileMgmt.html#id2947427">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt>logon script, <a href="passdb.html#id2901300">LDAP special attributes for sambaSamAccounts</a></dt><dt>lpadmin, <a href="CUPS-printing.html#id2935716">CUPS Print Drivers from Linuxprinting.org</a>, <a href="CUPS-printing.html#id2937193">Setting up Quotas</a></dt><dt>lppause command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2929956">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt>lpq cache time, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a></dt><dt>lpq command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt>lpresume command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt>lprm command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt>lpstat, <a href="CUPS-printing.html#id2934958">Troubleshooting revisited</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>MAC Addresses, <a href="integrate-ms-networks.html#id2951960">/etc/hosts</a></dt><dt>machine trust accounts, <a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt>creating, <a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt></dl></dd><dt>make, <a href="compiling.html#id2961798">Building the Binaries</a></dt><dt>mangling method, <a href="unicode.html#id2953612">Japanese charsets</a></dt><dt>map to guest, <a href="printing.html#id2917756">Parameters in the [print$] Section</a>, <a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a>, <a href="CUPS-printing.html#id2938921">Can't reconnect to Samba under new account + from Win2K/XP</a>, <a href="CUPS-printing.html#id2939149">Avoid being connected to the Samba server as the + "wrong" user</a></dt><dt>max print jobs, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>max xmit, <a href="speed.html#id2964393">Max xmit</a></dt><dt>messages.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>MIME, <a href="CUPS-printing.html#id2926501">MIME types and CUPS Filters</a>, <a href="CUPS-printing.html#id2926707">MIME type Conversion Rules</a>, <a href="CUPS-printing.html#id2926862">Filter Requirements</a>, <a href="CUPS-printing.html#id2928335">"application/octet-stream" printing</a></dt><dt>min print space, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>msdfs root, <a href="msdfs.html#id2912546">Features and Benefits</a></dt></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>name resolve order, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>nbtstat, <a href="integrate-ms-networks.html#id2952629">The NetBIOS Name Cache</a></dt><dt>NetBIOS, <a href="NetworkBrowsing.html#id2893931">Features and Benefits</a>, <a href="NetworkBrowsing.html#id2894584">TCP/IP - without NetBIOS</a>, <a href="integrate-ms-networks.html">Integrating MS Windows networks with Samba</a>, <a href="integrate-ms-networks.html#id2952319">Name resolution as used within MS Windows networking</a></dt><dt>NetBIOS-less, <a href="NetworkBrowsing.html#id2894584">TCP/IP - without NetBIOS</a></dt><dt>nmblookup, <a href="integrate-ms-networks.html#id2952629">The NetBIOS Name Cache</a></dt><dt>nt acl support, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2906755">Viewing file ownership</a>, <a href="AccessControls.html#id2906887">Viewing File or Directory Permissions</a>, <a href="AccessControls.html#id2907132">Modifying file or directory permissions</a>, <a href="Other-Clients.html#id2963891">Windows 2000 Service Pack 2</a></dt><dt>ntdrivers.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>ntforms.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>NTFS, <a href="AccessControls.html#id2904395">File System Access Controls</a></dt><dt>ntprinters.tdb, <a href="CUPS-printing.html#id2935118">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="pam.html#id2950929">smb.conf PAM Configuration</a></dt><dt>only user, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="securing-samba.html#id2911314">Why can users access home directories of other users?</a></dt><dt>oplock break wait time, <a href="locking.html#id2909323">Advanced Samba Opportunistic Locking Parameters</a>, <a href="locking.html#id2909679">Disabling Kernel OpLocks</a></dt><dt>oplock contention limit, <a href="locking.html#id2909323">Advanced Samba Opportunistic Locking Parameters</a></dt><dt>os level, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#DMB">Setting up WORKGROUP Browsing</a>, <a href="NetworkBrowsing.html#id2895446">Setting up DOMAIN Browsing</a>, <a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to be the master</a>, <a href="NetworkBrowsing.html#id2895844">Making Samba the domain master</a></dt><dt>os2 driver map, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="Other-Clients.html#id2963411">Printer driver download for for OS/2 clients?</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>page_log, <a href="CUPS-printing.html#id2937398">The page_log File Syntax</a></dt><dt>passdb backend, <a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="passdb.html">Account Information Databases</a>, <a href="passdb.html#id2898749">Technical Information</a>, <a href="passdb.html#id2899622">The pdbedit Command</a>, <a href="passdb.html#id2900704">Configuring Samba</a>, <a href="passdb.html#id2902030">Configuring</a>, <a href="passdb.html#id2902796">Users can not logon</a>, <a href="passdb.html#id2902952">auth methods does not work</a>, <a href="upgrading-to-3.0.html#id2955156">Passdb Backends and Authentication</a></dt><dt>password level, <a href="ServerType.html#id2886191">Password checking</a>, <a href="diagnosis.html#id2958249">The tests</a>, <a href="Other-Clients.html#id2963692">Case handling of passwords</a>, <a href="speed.html#id2964630">Slow Logins</a></dt><dt>password server, <a href="ServerType.html#id2885909">Server Security (User Level Security)</a>, <a href="samba-pdc.html#id2888704">Security Mode and Master Browsers</a>, <a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>patch, <a href="bugreport.html#id2961107">Patches</a></dt><dt>path, <a href="install.html#id2884661">"The network name cannot be found"</a>, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a>, <a href="printing.html#id2916027">Print Commands</a>, <a href="printing.html#id2917566">Creating the [print$] Share</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a>, <a href="printing.html#id2918066">Subdirectory Structure in [print$]</a>, <a href="CUPS-printing.html#id2930169">Samba receiving Jobfiles and passing them to CUPS</a>, <a href="CUPS-printing.html#id2937912">Auto-Deletion or Preservation of CUPS Spool Files</a>, <a href="CUPS-printing.html#id2939796">Permissions on +/var/spool/samba/ get reset after each +reboot</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>PCL, <a href="CUPS-printing.html#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="CUPS-printing.html#id2925650">UNIX Printfile Conversion and GUI Basics</a>, <a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a>, <a href="CUPS-printing.html#id2930255">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a></dt><dt>PDF, <a href="CUPS-printing.html#id2925497">Windows Drivers, GDI and EMF</a>, <a href="CUPS-printing.html#id2926092">PostScript Printer Description (PPD) Specification</a></dt><dt>pdf, <a href="CUPS-printing.html#id2926707">MIME type Conversion Rules</a></dt><dt>PDL, <a href="CUPS-printing.html#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt>PJL, <a href="CUPS-printing.html#id2930255">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a>, <a href="CUPS-printing.html#id2931837">Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver</a>, <a href="CUPS-printing.html#id2937303">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt>point and print, <a href="CUPS-printing.html#id2924894">Driver Installation Methods on Windows Clients</a>, <a href="CUPS-printing.html#id2925177">Three familiar Methods for driver upload plus a new one</a>, <a href="CUPS-printing.html#id2928022">cupsomatic/Foomatic -- how do they fit into the Picture?</a>, <a href="CUPS-printing.html#id2932052">Run "cupsaddsmb" (quiet Mode)</a>, <a href="CUPS-printing.html#id2932789">Installing the PostScript Driver on a Client</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt>PostScript, <a href="CUPS-printing.html#id2925317">Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download</a>, <a href="CUPS-printing.html#gdipost">GDI on Windows -- PostScript on UNIX</a>, <a href="CUPS-printing.html#id2925650">UNIX Printfile Conversion and GUI Basics</a>, <a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a href="CUPS-printing.html#id2927043">Prefilters</a>, <a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a>, <a href="CUPS-printing.html#id2930255">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a>, <a href="CUPS-printing.html#id2930560">CUPS: a "Magical Stone"?</a>, <a href="CUPS-printing.html#id2931030">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dd><dl><dt>(see also Ghostscript)</dt><dt>RIP, <a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt></dl></dd><dt>PPD, <a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a>, <a href="CUPS-printing.html#id2926092">PostScript Printer Description (PPD) Specification</a>, <a href="CUPS-printing.html#id2928581">PostScript Printer Descriptions (PPDs) for non-PS Printers</a>, <a href="CUPS-printing.html#id2930344">PPDs for non-PS Printers on UNIX</a>, <a href="CUPS-printing.html#id2930400">PPDs for non-PS Printers on Windows</a>, <a href="CUPS-printing.html#id2930560">CUPS: a "Magical Stone"?</a>, <a href="CUPS-printing.html#id2932789">Installing the PostScript Driver on a Client</a></dt><dd><dl><dt>CUPS (see CUPS-PPD)</dt></dl></dd><dt>preferred master, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#DMB">Setting up WORKGROUP Browsing</a>, <a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to be the master</a>, <a href="NetworkBrowsing.html#id2895844">Making Samba the domain master</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>preserve case, <a href="ProfileMgmt.html#id2946186">Windows 9x / Me Profile Setup</a></dt><dt>print command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a>, <a href="printing.html#id2916108">Default Print Commands for various UNIX Print Subsystems</a>, <a href="printing.html#id2916791">Setting up your own Print Commands</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2929956">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a>, <a href="CUPS-printing.html#id2938226">Manual Configuration</a></dt><dt>print ok , <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>printable, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt><dt>printcap, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2916108">Default Print Commands for various UNIX Print Subsystems</a>, <a href="CUPS-printing.html#id2923880">Basic Configuration of CUPS support</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2924395">More complex smb.conf Settings for +CUPS</a>, <a href="CUPS-printing.html#id2929956">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt>printcap name, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a></dt><dt>printer, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>printer admin, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a>, <a href="printing.html#id2918333">Setting Drivers for existing Printers with a Client GUI</a>, <a href="printing.html#id2920462">IMPORTANT! Setting Device Modes on new Printers</a>, <a href="printing.html#id2920857">Always make first Client Connection as root or "printer admin"</a>, <a href="printing.html#id2921063">Setting Default Print Options for the Client Drivers</a>, <a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a>, <a href="CUPS-printing.html#id2924395">More complex smb.conf Settings for +CUPS</a>, <a href="CUPS-printing.html#id2933674">What is required for adddriver and setdriver to succeed</a>, <a href="CUPS-printing.html#id2939398">Print options for all users can't be set on Win2K/XP</a></dt><dt>printer name, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt><dt>printing, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a>, <a href="printing.html#id2916108">Default Print Commands for various UNIX Print Subsystems</a>, <a href="printing.html#id2916791">Setting up your own Print Commands</a>, <a href="CUPS-printing.html#id2923880">Basic Configuration of CUPS support</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a>, <a href="CUPS-printing.html#id2924395">More complex smb.conf Settings for +CUPS</a>, <a href="CUPS-printing.html#id2929956">From Windows Clients to a CUPS/Samba Print Server</a>, <a href="CUPS-printing.html#id2938069">Pre-conditions</a>, <a href="CUPS-printing.html#id2938226">Manual Configuration</a></dt><dt>printing.tdb, <a href="CUPS-printing.html#id2935118">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="printing.html#id2915245">The [printers] Section</a></dt></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt>queue resume command, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a></dt><dt>queuepause command, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a></dt><dt>queueresume command, <a href="printing.html#id2913251">Parameters Recommended for Use</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>read list, <a href="AccessControls.html#id2905070">User and Group Based Controls</a></dt><dt>read only, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a>, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt><dt>read raw, <a href="speed.html#id2964483">Read raw</a></dt><dt>read size, <a href="speed.html#id2964343">Read size</a></dt><dt>remote announce, <a href="NetworkBrowsing.html#id2894349">NetBIOS over TCP/IP</a>, <a href="NetworkBrowsing.html#id2894896">How Browsing Functions</a>, <a href="NetworkBrowsing.html#id2896081">Use of the Remote Announce parameter</a>, <a href="NetworkBrowsing.html#id2897187">Browsing support in Samba</a></dt><dt>remote browse sync, <a href="NetworkBrowsing.html#id2894349">NetBIOS over TCP/IP</a>, <a href="NetworkBrowsing.html#id2894896">How Browsing Functions</a>, <a href="NetworkBrowsing.html#id2896240">Use of the Remote Browse Sync parameter</a></dt><dt>root preexec, <a href="NT4Migration.html#id2955990">Logon Scripts</a></dt><dt>rpcclient</dt><dd><dl><dt>adddriver, <a href="CUPS-printing.html#id2932180">Run "cupsaddsmb" with verbose Output</a>, <a href="CUPS-printing.html#id2932401">Understanding cupsaddsmb</a>, <a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a>, <a href="CUPS-printing.html#id2933403">Understanding the rpcclient man page</a>, <a href="CUPS-printing.html#id2933674">What is required for adddriver and setdriver to succeed</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt>enumdrivers, <a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt>enumports, <a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a></dt><dt>enumprinters, <a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a>, <a href="CUPS-printing.html#id2933674">What is required for adddriver and setdriver to succeed</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a>, <a href="CUPS-printing.html#id2934958">Troubleshooting revisited</a></dt><dt>getdriver, <a href="CUPS-printing.html#id2933506">Producing an Example by querying a Windows Box</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt>getprinter, <a href="CUPS-printing.html#id2933506">Producing an Example by querying a Windows Box</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a>, <a href="CUPS-printing.html#id2934958">Troubleshooting revisited</a></dt><dt>setdriver, <a href="CUPS-printing.html#id2931562">Caveats to be considered</a>, <a href="CUPS-printing.html#id2932180">Run "cupsaddsmb" with verbose Output</a>, <a href="CUPS-printing.html#id2932401">Understanding cupsaddsmb</a>, <a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a>, <a href="CUPS-printing.html#id2933674">What is required for adddriver and setdriver to succeed</a>, <a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt></dl></dd><dt>rsync, <a href="compiling.html#id2961581">Accessing the samba sources via rsync and ftp</a></dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>secrets.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>security, <a href="ServerType.html#id2885157">Samba Security Modes</a>, <a href="ServerType.html#id2885551">Domain Security Mode (User Level Security)</a>, <a href="ServerType.html#id2885909">Server Security (User Level Security)</a>, <a href="ServerType.html#id2886414">What makes Samba a SERVER?</a>, <a href="ServerType.html#id2886453">What makes Samba a Domain Controller?</a>, <a href="ServerType.html#id2886490">What makes Samba a Domain Member?</a>, <a href="ServerType.html#id2886529">Constantly Losing Connections to Password Server</a>, <a href="samba-pdc.html#id2887335">Preparing for Domain Control</a>, <a href="samba-pdc.html#id2888704">Security Mode and Master Browsers</a>, <a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a>, <a href="domain-member.html#id2892061">Why is this better than security = server?</a>, <a href="domain-member.html#id2892246">Setup your smb.conf</a>, <a href="CUPS-printing.html#id2932052">Run "cupsaddsmb" (quiet Mode)</a>, <a href="CUPS-printing.html#id2938787">"cupsaddsmb" keeps asking for root password in + neverending loop</a>, <a href="upgrading-to-3.0.html#id2955156">Passdb Backends and Authentication</a>, <a href="diagnosis.html#id2958249">The tests</a>, <a href="Other-Clients.html#id2963639">Configuring WfW password handling</a></dt><dt>security mask, <a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a>, <a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt>Server Manager, <a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a>, <a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt><dt>sessionid.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>share_info.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>short preserve case, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a>, <a href="ProfileMgmt.html#id2946186">Windows 9x / Me Profile Setup</a></dt><dt>Short-Cuts, <a href="AccessControls.html#id2904431">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt>show add printer wizard, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a>, <a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a></dt><dt>SID, <a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt>Single Sign On, <a href="CUPS-printing.html#id2931562">Caveats to be considered</a></dt><dt>smbclient, <a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>socket options, <a href="speed.html#id2964253">Socket options</a></dt><dt>spooling</dt><dd><dl><dt>central, <a href="CUPS-printing.html#id2924770">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt>peer-to-peer, <a href="CUPS-printing.html#id2924770">Central spooling vs. "Peer-to-Peer" printing</a></dt></dl></dd><dt>spooling-only, <a href="CUPS-printing.html#id2924825">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt>strict locking, <a href="locking.html#id2908589">Discussion</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>TDB, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a>, <a href="CUPS-printing.html#id2935364">Trivial DataBase Files</a></dt><dd><dl><dt>backing up (see tdbbackup)</dt></dl></dd><dt>tdbbackup, <a href="CUPS-printing.html#id2935579">Using tdbbackup</a></dt><dt>template homedir, <a href="winbind.html#id2943196">Linux/FreeBSD-specific PAM configuration</a></dt><dt>testparm, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>text/plain, <a href="CUPS-printing.html#id2926707">MIME type Conversion Rules</a></dt><dt>total print jobs, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>UDP, <a href="NetworkBrowsing.html#id2894349">NetBIOS over TCP/IP</a></dt><dt>UID, <a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt>unexpected.tdb, <a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt>(see also TDB)</dt></dl></dd><dt>unix charset, <a href="unicode.html#id2953454">Samba and charsets</a>, <a href="unicode.html#id2953612">Japanese charsets</a></dt><dt>use client driver, <a href="printing.html#id2913251">Parameters Recommended for Use</a>, <a href="printing.html#id2914714">The [global] Section</a></dt><dt>user, <a href="ServerType.html#id2885414">Share Level Security</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>User Manager, <a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a>, <a href="InterdomainTrusts.html#id2912232">Samba as the Trusting Domain</a></dt><dt>useradd, <a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt><dt>username, <a href="AccessControls.html#id2905070">User and Group Based Controls</a></dt><dt>username level, <a href="ServerType.html#id2886191">Password checking</a></dt><dt>username map, <a href="domain-member.html#id2891426">Windows 200x XP Professional</a></dt></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>valid users, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="diagnosis.html#id2958249">The tests</a></dt><dt>veto files, <a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt><dt>vfs objects, <a href="VFS.html#id2940195">Discussion</a></dt><dt>vipw, <a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>winbind separator, <a href="winbind.html#id2942516">Start up the winbindd daemon and test it!</a></dt><dt>WINS, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#id2894349">NetBIOS over TCP/IP</a>, <a href="integrate-ms-networks.html#id2952918">WINS Lookup</a></dt><dt>wins hook, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>wins proxy, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt>wins server, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#id2896317">WINS - The Windows Internetworking Name Server</a>, <a href="NetworkBrowsing.html#id2896504">Setting up a WINS server</a></dt><dt>wins support, <a href="NetworkBrowsing.html#id2894019">What is Browsing?</a>, <a href="NetworkBrowsing.html#id2896317">WINS - The Windows Internetworking Name Server</a>, <a href="NetworkBrowsing.html#id2896504">Setting up a WINS server</a></dt><dt>workgroup, <a href="samba-pdc.html#id2888704">Security Mode and Master Browsers</a>, <a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a>, <a href="NetworkBrowsing.html#id2897187">Browsing support in Samba</a></dt><dt>write list, <a href="AccessControls.html#id2905070">User and Group Based Controls</a>, <a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt><dt>write raw, <a href="speed.html#id2964567">Write raw</a></dt><dt>writeable, <a href="printing.html#id2915245">The [printers] Section</a>, <a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt><dt>WYSIWYG, <a href="CUPS-printing.html#id2925497">Windows Drivers, GDI and EMF</a></dt></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X Window System, <a href="CUPS-printing.html#id2925650">UNIX Printfile Conversion and GUI Basics</a></dt><dt>xinetd, <a href="compiling.html#id2962252">Starting from inetd.conf</a> (see inetd)</dt><dt>Xprint, <a href="CUPS-printing.html#id2925650">UNIX Printfile Conversion and GUI Basics</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Further-Resources.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-doc.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 41. Further Resources </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html> diff --git a/docs/htmldocs/locking.html b/docs/htmldocs/locking.html new file mode 100644 index 0000000000..07228df19d --- /dev/null +++ b/docs/htmldocs/locking.html @@ -0,0 +1,637 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 14. File and Record Locking</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="AccessControls.html" title="Chapter 13. File, Directory and Share Access Controls"><link rel="next" href="securing-samba.html" title="Chapter 15. Securing Samba"></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 14. File and Record Locking</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="securing-samba.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jra@samba.org">jra@samba.org</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="locking.html#id2908532">Features and Benefits</a></dt><dt><a href="locking.html#id2908589">Discussion</a></dt><dd><dl><dt><a href="locking.html#id2908732">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="locking.html#id2909449">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="locking.html#id2909569">Example Configuration</a></dt></dl></dd><dt><a href="locking.html#id2909983">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="locking.html#id2910208">Workstation Service Entries</a></dt><dt><a href="locking.html#id2910237">Server Service Entries</a></dt></dl></dd><dt><a href="locking.html#id2910317">Persistent Data Corruption</a></dt><dt><a href="locking.html#id2910345">Common Errors</a></dt><dd><dl><dt><a href="locking.html#id2910419">locking.tdb error messages</a></dt><dt><a href="locking.html#id2910456">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="locking.html#id2910479">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="locking.html#id2910511">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="id2908532"></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> +The term <span class="emphasis"><em>locking</em></span> has exceptionally broad meaning and covers +a range of functions that are all categorized under this one term. +</p><p> +Opportunistic locking is a desirable feature when it can enhance the +perceived performance of applications on a networked client. However, the +opportunistic locking protocol is not robust, and therefore can +encounter problems when invoked beyond a simplistic configuration, or +on extended, slow, or faulty networks. In these cases, operating +system management of opportunistic locking and/or recovering from +repetitive errors can offset the perceived performance advantage that +it is intended to provide. +</p><p> +The MS Windows network administrator needs to be aware that file and record +locking semantics (behaviour) can be controlled either in Samba or by way of registry +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="id2908589"></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> +that are specified when a file is open. +</p><p> +Record locking semantics under UNIX are very different from record locking under +Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix +system call to implement proper record locking between different Samba clients. +This can not be fully correct due to several reasons. The simplest is the fact +that a Windows client is allowed to lock a byte range up to 2^32 or 2^64, +depending on the client OS. The unix locking only supports byte ranges up to 2^31. +So it is not possible to correctly satisfy a lock request above 2^31. There are +many more differences, too many to be listed here. +</p><p> +Samba 2.2 and above implements record locking completely independent of the +underlying unix system. If a byte range lock that the client requests happens +to fall into the range 0-2^31, Samba hands this request down to the UNIX system. +All other locks can not be seen by unix anyway. +</p><p> +Strictly an SMB server should check for locks before every read and write call on +a file. Unfortunately with the way fcntl() works this can be slow and may over-stress +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="id2908656"></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="id2908676"></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. +</p><p> +The second class of locking is the <span class="emphasis"><em>deny modes</em></span>. These +are set by an application when it opens a file to determine what types of +access should be allowed simultaneously with its open. A client may ask for +<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="id2908732"></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 +residing on a server. Performance is enhanced by caching the file +locally on the client which allows: +</p><div class="variablelist"><dl><dt><span class="term">Read-ahead:</span></dt><dd><p> + The client reads the local copy of the file, eliminating network latency + </p></dd><dt><span class="term">Write caching:</span></dt><dd><p> + The client writes to the local copy of the file, eliminating network latency + </p></dd><dt><span class="term">Lock caching:</span></dt><dd><p> + The client caches application locks locally, eliminating network latency + </p></dd></dl></div><p> +The performance enhancement of oplocks is due to the opportunity of +exclusive access to the file - even if it is opened with deny-none - +because Windows monitors the file's status for concurrent access from +other processes. +</p><div class="variablelist"><p class="title"><b>Windows defines 4 kinds of Oplocks:</b></p><dl><dt><span class="term">Level1 Oplock:</span></dt><dd><p> + The redirector sees that the file was opened with deny + none (allowing concurrent access), verifies that no + other process is accessing the file, checks that + oplocks are enabled, then grants deny-all/read-write/exclusive + access to the file. The client now performs + operations on the cached local file. + </p><p> + If a second process attempts to open the file, the open + is deferred while the redirector "breaks" the original + oplock. The oplock break signals the caching client to + write the local file back to the server, flush the + local locks, and discard read-ahead data. The break is + then complete, the deferred open is granted, and the + multiple processes can enjoy concurrent file access as + dictated by mandatory or byte-range locking options. + However, if the original opening process opened the + file with a share mode other than deny-none, then the + second process is granted limited or no access, despite + the oplock break. + </p></dd><dt><span class="term">Level2 Oplock:</span></dt><dd><p> + Performs like a level1 oplock, except caching is only + operative for reads. All other operations are performed + on the server disk copy of the file. + </p></dd><dt><span class="term">Filter Oplock:</span></dt><dd><p> + Does not allow write or delete file access + </p></dd><dt><span class="term">Batch Oplock:</span></dt><dd><p> + Manipulates file openings and closings - allows caching + of file attributes + </p></dd></dl></div><p> +An important detail is that oplocks are invoked by the file system, not +an application API. Therefore, an application can close an oplocked +file, but the file system does not relinquish the oplock. When the +oplock break is issued, the file system then simply closes the file in +preparation for the subsequent open by the second process. +</p><p> +<span class="emphasis"><em>Opportunistic Locking</em></span> is actually an improper name for this feature. +The true benefit of this feature is client-side data caching, and +oplocks is merely a notification mechanism for writing data back to the +networked storage disk. The limitation of opportunistic locking is the +reliability of the mechanism to process an oplock break (notification) +between the server and the caching client. If this exchange is faulty +(usually due to timing out for any number of reasons) then the +client-side caching benefit is negated. +</p><p> +The actual decision that a user or administrator should consider is +whether it is sensible to share amongst multiple users data that will +be cached locally on a client. In many cases the answer is no. +Deciding when to cache or not cache data is the real question, and thus +"opportunistic locking" should be treated as a toggle for client-side +caching. Turn it "ON" when client-side caching is desirable and +reliable. Turn it "OFF" when client-side caching is redundant, +unreliable, or counter-productive. +</p><p> +Opportunistic locking is by default set to "on" by Samba on all +configured shares, so careful attention should be given to each case to +determine if the potential benefit is worth the potential for delays. +The following recommendations will help to characterize the environment +where opportunistic locking may be effectively configured. +</p><p> +Windows Opportunistic Locking is a lightweight performance-enhancing +feature. It is not a robust and reliable protocol. Every +implementation of Opportunistic Locking should be evaluated as a +tradeoff between perceived performance and reliability. Reliability +decreases as each successive rule above is not enforced. Consider a +share with oplocks enabled, over a wide area network, to a client on a +South Pacific atoll, on a high-availability server, serving a +mission-critical multi-user corporate database, during a tropical +storm. This configuration will likely encounter problems with oplocks. +</p><p> +Oplocks can be beneficial to perceived client performance when treated +as a configuration toggle for client-side data caching. If the data +caching is likely to be interrupted, then oplock usage should be +reviewed. Samba enables opportunistic locking by default on all +shares. Careful attention should be given to the client usage of +shared data on the server, the server network reliability, and the +opportunistic locking configuration of each share. +n 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 +failover replacement will be available immediately to provide +continuous data availability. +</p><p> +Windows client failover behavior is more at risk of application +interruption than other platforms because it is dependant upon an +established TCP transport connection. If the connection is interrupted +- as in a file server failover - a new session must be established. +It is rare for Windows client applications to be coded to recover +correctly from a transport connection loss, therefore most applications +will experience some sort of interruption - at worst, abort and +require restarting. +</p><p> +If a client session has been caching writes and reads locally due to +opportunistic locking, it is likely that the data will be lost when the +application restarts, or recovers from the TCP interrupt. When the TCP +connection drops, the client state is lost. When the file server +recovers, an oplock break is not sent to the client. In this case, the +work from the prior session is lost. Observing this scenario with +oplocks disabled, and the client was writing data to the file server +real-time, then the failover will provide the data on disk as it +existed at the time of the disconnect. +</p><p> +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="id2909061"></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 +client caching of data, any operation that interrupts the caching +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="id2909086"></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 +share that has oplocks enabled, the management impact of sending and +receiving oplock breaks, and the resulting latency while other clients +wait for the caching client to flush data, offset the performance gains +of the caching user. +</p><p> +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="id2909115"></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 +that has a file cached. Local UNIX or NFS file access can therefore +write to a file that has been cached by a Windows client, which +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="id2909141"></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. +This is most likely to occur when the network is extremely slow, +congested, or distributed (as in a WAN). However, network latency also +has a very high impact on the reliability of the oplock break +mechanism, and thus increases the likelihood of encountering oplock +problems that more than offset the potential perceived performance +gain. Of course, if an oplock break never has to be sent, then this is +the most advantageous scenario to utilize opportunistic locking. +</p><p> +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="id2909174"></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 +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="id2909204"></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 +environments for critical data security and access. The typical PDM +environment is usually associated with sophisticated client design +applications that will load data locally as demanded. In addition, the +PDM application will usually monitor the data-state of each client. +In this case, client-side data caching is best left to the local +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="id2909231"></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="id2909250"></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 +to the client, even if the user has not explicitly loaded a file. In +cases where the network is slow or unreliable, an oplock break can +become lost without the user even accessing a file. This can cause +apparent performance degradation as the client continually reconnects +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="id2909286"></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="id2909323"></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="id2909340"></a><i class="parameter"><tt>oplock break wait time</tt></i>, +<a class="indexterm" name="id2909355"></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="id2909382"></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 +failover replacement will be available immediately to provide +continuous data availability. +</p><p> +Windows client failover behavior is more at risk of application +interruption than other platforms because it is dependant upon an +established TCP transport connection. If the connection is interrupted +- as in a file server failover - a new session must be established. +It is rare for Windows client applications to be coded to recover +correctly from a transport connection loss, therefore most applications +will experience some sort of interruption - at worst, abort and +require restarting. +</p><p> +If a client session has been caching writes and reads locally due to +opportunistic locking, it is likely that the data will be lost when the +application restarts, or recovers from the TCP interrupt. When the TCP +connection drops, the client state is lost. When the file server +recovers, an oplock break is not sent to the client. In this case, the +work from the prior session is lost. Observing this scenario with +oplocks disabled, and the client was writing data to the file server +real-time, then the failover will provide the data on disk as it +existed at the time of the disconnect. +</p><p> +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="id2909449"></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. +Opportunistic Locking is actually part of the Windows client file +caching mechanism. It is not a particularly robust or reliable feature +when implemented on the variety of customized networks that exist in +enterprise computing. +</p><p> +Like Windows, Samba implements Opportunistic Locking as a server-side +component of the client caching mechanism. Because of the lightweight +nature of the Windows feature design, effective configuration of +Opportunistic Locking requires a good understanding of its limitations, +and then applying that understanding when configuring data access for +each particular customized network and client usage state. +</p><p> +Opportunistic locking essentially means that the client is allowed to download and cache +a file on their hard drive while making changes; if a second client wants to access the +file, the first client receives a break and must synchronise the file back to the server. +This can give significant performance gains in some cases; some programs insist on +synchronising the contents of the entire file back to the server for a single change. +</p><p> +Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. +</p><p> +Level2 Oplocks provides opportunistic locking for a file that will be treated as +<span class="emphasis"><em>read only</em></span>. Typically this is used on files that are read-only or +on files that the client has no initial intention to write to at time of opening the file. +</p><p> +Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with +Samba's oplocked files, although this has provided better integration of MS Windows network +file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are +oplock aware at this time. +</p><p> +Unless your system supports kernel oplocks, you should disable oplocks if you are +accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should +always be disabled if you are sharing a database file (e.g., Microsoft Access) between +multiple clients, as any break the first client receives will affect synchronisation of +the entire file (not just the single record), which will result in a noticeable performance +impairment and, more likely, problems accessing the database in the first place. Notably, +Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt, +disable oplocks and tune your system from that point. +</p><p> +If client-side caching is desirable and reliable on your network, you will benefit from +turning on oplocks. If your network is slow and/or unreliable, or you are sharing your +files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people +will be accessing the same files frequently, you probably will not benefit from the overhead +of your client sending oplock breaks and will instead want to disable oplocks for the share. +</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="id2909569"></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="id2909582"></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> +</p><p> +The default oplock type is Level1. Level2 Oplocks are enabled on a per-share basis +in the <tt class="filename">smb.conf</tt> file. +</p><p> +Alternately, you could disable oplocks on a per-file basis within the share: +</p><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/</tt></i></td></tr></table><p> +</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="id2909679"></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 +cached. This parameter addresses sharing files between UNIX and +Windows with Oplocks enabled on the Samba server: the UNIX process +can open the file that is Oplocked (cached) by the Windows client and +the smbd process will not send an oplock break, which exposes the file +to the risk of data corruption. If the UNIX kernel has the ability to +send an oplock break, then the kernel oplocks parameter enables Samba +to send the oplock break. Kernel oplocks are enabled on a per-server +basis in the <tt class="filename">smb.conf</tt> file. +</p><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>kernel oplocks = yes</tt></i></td></tr></table><p> +The default is "no". +</p><p> +Veto OpLocks is an <tt class="filename">smb.conf</tt> parameter that identifies specific files for +which Oplocks are disabled. When a Windows client opens a file that +has been configured for veto oplocks, the client will not be granted +the oplock, and all operations will be executed on the original file on +disk instead of a client-cached file copy. By explicitly identifying +files that are shared with UNIX processes, and disabling oplocks for +those files, the server-wide Oplock configuration can be enabled to +allow Windows clients to utilize the performance benefit of file +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="id2909772"></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="id2909826"></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 +configured globally in the <tt class="filename">smb.conf</tt> file: +</p><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>oplock break wait time = 0 (default)</tt></i></td></tr></table><p> +</p><p> +<span class="emphasis"><em>Oplock break contention limit</em></span> is an <tt class="filename">smb.conf</tt> parameter that limits the +response of the Samba server to grant an oplock if the configured +number of contending clients reaches the limit specified by the +parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU +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="id2909930"></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="id2909983"></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 +operating system known as <span class="emphasis"><em>Opportunistic Locking</em></span>. When a workstation +attempts to access shared data files located on another Windows 2000/XP computer, +the Windows 2000/XP operating system will attempt to increase performance by locking the +files and caching information locally. When this occurs, the application is unable to +properly function, which results in an <span class="errorname">Access Denied</span> + error message being displayed during network operations. +</p><p> +All Windows operating systems in the NT family that act as database servers for data files +(meaning that data files are stored there and accessed by other Windows PCs) may need to +have opportunistic locking disabled in order to minimize the risk of data file corruption. +This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP. +</p><p> +If you are using a Windows NT family workstation in place of a server, you must also +disable opportunistic locking (oplocks) on that workstation. For example, if you use a +PC with the Windows NT Workstation operating system instead of Windows NT Server, and you +have data files located on it that are accessed from other Windows PCs, you may need to +disable oplocks on that system. +</p><p> +The major difference is the location in the Windows registry where the values for disabling +oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location +may be used. +</p><p> +You can verify (or change or add, if necessary) this Registry value using the Windows +Registry Editor. When you change this registry value, you will have to reboot the PC +to ensure that the new setting goes into effect. +</p><p> +The location of the client registry entry for opportunistic locking has changed in +Windows 2000 from the earlier location in Microsoft Windows NT. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks +in earlier versions of Windows. +</p></div><p> +You can also deny the granting of opportunistic locks by changing the following registry entries: +</p><p> +</p><pre class="programlisting"> + HKEY_LOCAL_MACHINE\System\ + CurrentControlSet\Services\MRXSmb\Parameters\ + + OplocksDisabled REG_DWORD 0 or 1 + Default: 0 (not disabled) +</pre><p> +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +The OplocksDisabled registry value configures Windows clients to either request or not +request opportunistic locks on a remote file. To disable oplocks, the value of + OplocksDisabled must be set to 1. +</p></div><p> +</p><pre class="programlisting"> + HKEY_LOCAL_MACHINE\System\ + CurrentControlSet\Services\LanmanServer\Parameters + + EnableOplocks REG_DWORD 0 or 1 + Default: 1 (Enabled by Default) + + EnableOpLockForceClose REG_DWORD 0 or 1 + Default: 0 (Disabled by Default) +</pre><p> +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +The EnableOplocks value configures Windows-based servers (including Workstations sharing +files) to allow or deny opportunistic locks on local files. +</p></div><p> +To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1. +</p><p> +An illustration of how level II oplocks work: +</p><div class="itemizedlist"><ul type="disc"><li><p> + Station 1 opens the file, requesting oplock. + </p></li><li><p> + Since no other station has the file open, the server grants station 1 exclusive oplock. + </p></li><li><p> + Station 2 opens the file, requesting oplock. + </p></li><li><p> + Since station 1 has not yet written to the file, the server asks station 1 to Break + to Level II Oplock. + </p></li><li><p> + Station 1 complies by flushing locally buffered lock information to the server. + </p></li><li><p> + Station 1 informs the server that it has Broken to Level II Oplock (alternatively, + station 1 could have closed the file). + </p></li><li><p> + The server responds to station 2's open request, granting it level II oplock. + Other stations can likewise open the file and obtain level II oplock. + </p></li><li><p> + Station 2 (or any station that has the file open) sends a write request SMB. + The server returns the write response. + </p></li><li><p> + The server asks all stations that have the file open to Break to None, meaning no + 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="id2910208"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting"> + \HKEY_LOCAL_MACHINE\System\ + CurrentControlSet\Services\LanmanWorkstation\Parameters + + UseOpportunisticLocking REG_DWORD 0 or 1 + Default: 1 (true) +</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="id2910237"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting"> + \HKEY_LOCAL_MACHINE\System\ + CurrentControlSet\Services\LanmanServer\Parameters + + EnableOplocks REG_DWORD 0 or 1 + Default: 1 (true) +</pre><p> +Specifies whether the server allows clients to use oplocks on files. Oplocks are a +significant performance enhancement, but have the potential to cause lost cached +data on some networks, particularly wide-area networks. +</p><pre class="programlisting"> + MinLinkThroughput REG_DWORD 0 to infinite bytes per second + Default: 0 +</pre><p> +Specifies the minimum link throughput allowed by the server before it disables +raw and opportunistic locks for this connection. +</p><pre class="programlisting"> + MaxLinkDelay REG_DWORD 0 to 100,000 seconds + Default: 60 +</pre><p> +Specifies the maximum time allowed for a link delay. If delays exceed this number, +the server disables raw I/O and opportunistic locking for this connection. +</p><pre class="programlisting"> + OplockBreakWait REG_DWORD 10 to 180 seconds + Default: 35 +</pre><p> +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="id2910317"></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> +We have credible reports from developers that faulty network hardware, such as a single +faulty network card, can cause symptoms similar to read caching and data corruption. +If you see persistent data corruption even after repeated reindexing, you may have to +rebuild the data files in question. This involves creating a new data file with the +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="id2910345"></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. +</p><p> +Over the past few years there have been a number of complaints on the samba mailing lists +that have claimed that samba caused data corruption. Three causes have been identified +so far: +</p><div class="itemizedlist"><ul type="disc"><li><p> + Incorrect configuration of opportunistic locking (incompatible with the application + being used. This is a VERY common problem even where MS Windows NT4 or MS Windows 200x + based servers were in use. It is imperative that the software application vendors' + instructions for configuration of file locking should be followed. If in doubt, + disable oplocks on both the server and the client. Disabling of all forms of file + caching on the MS Windows client may be necessary also. + </p></li><li><p> + Defective network cards, cables, or HUBs / Switched. This is generally a more + prevalent factor with low cost networking hardware, though occasionally there + have been problems with incompatibilities in more up market hardware also. + </p></li><li><p> + There have been some random reports of samba log files being written over data + files. This has been reported by very few sites (about 5 in the past 3 years) + and all attempts to reproduce the problem have failed. The Samba-Team has been + unable to catch this happening and thus has NOT been able to isolate any particular + cause. Considering the millions of systems that use samba, for the sites that have + been affected by this as well as for the Samba-Team this is a frustrating and + a vexing challenge. If you see this type of thing happening please create a bug + 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="id2910419"></a>locking.tdb error messages</h3></div></div><div></div></div><p> + “<span class="quote"> + We are seeing lots of errors in the samba logs like: +</span>” +</p><pre class="programlisting"> +tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic + 0x4d6f4b61 at offset=36116 +</pre><p> +“<span class="quote"> + What do these mean? + </span>” + </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="id2910456"></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="id2910479"></a>Long delays deleting files over network with XP SP1</h3></div></div><div></div></div><p>“<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied</span>”</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="id2910511"></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. +</p><p> +Section of the Microsoft MSDN Library on opportunistic locking: +</p><p> +Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development > +Windows Base Services > Files and I/O > SDK Documentation > File Storage > File Systems +> About File Systems > Opportunistic Locks, Microsoft Corporation. +<a href="http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp" target="_top">http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp</a> +</p><p> +Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", +Microsoft Corporation, April 1999, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992</a>. +</p><p> +Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", +Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264</a>. +</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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="AccessControls.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="securing-samba.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 13. File, Directory and Share Access Controls </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 15. Securing Samba</td></tr></table></div></body></html> diff --git a/docs/htmldocs/migration.html b/docs/htmldocs/migration.html new file mode 100644 index 0000000000..36b6edb0b1 --- /dev/null +++ b/docs/htmldocs/migration.html @@ -0,0 +1 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part IV. Migration and Updating</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="samba-doc.html" title="SAMBA Project Documentation"><link rel="previous" href="SambaHA.html" title="Chapter 29. High Availability Options"><link rel="next" href="upgrading-to-3.0.html" title="Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0"></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">Part IV. Migration and Updating</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SambaHA.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr></table><hr></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.html">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2954094">New Features in Samba-3</a></dt><dt><a href="upgrading-to-3.0.html#id2954229">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2954244">Removed Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2954370">New Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2954767">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="upgrading-to-3.0.html#id2954842">New Functionality</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2954849">Databases</a></dt><dt><a href="upgrading-to-3.0.html#id2955083">Changes in Behavior</a></dt><dt><a href="upgrading-to-3.0.html#id2955133">Charsets</a></dt><dt><a href="upgrading-to-3.0.html#id2955156">Passdb Backends and Authentication</a></dt><dt><a href="upgrading-to-3.0.html#id2955274">Charsets</a></dt><dt><a href="upgrading-to-3.0.html#id2955299">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="NT4Migration.html">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="NT4Migration.html#id2955644">Planning and Getting Started</a></dt><dd><dl><dt><a href="NT4Migration.html#id2955669">Objectives</a></dt><dt><a href="NT4Migration.html#id2956108">Steps In Migration Process</a></dt></dl></dd><dt><a href="NT4Migration.html#id2956323">Migration Options</a></dt><dd><dl><dt><a href="NT4Migration.html#id2956414">Planning for Success</a></dt><dt><a href="NT4Migration.html#id2956670">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="SWAT.html">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="SWAT.html#id2957030">Features and Benefits</a></dt><dd><dl><dt><a href="SWAT.html#id2957079">Enabling SWAT for use</a></dt><dt><a href="SWAT.html#id2957316">Securing SWAT through SSL</a></dt><dt><a href="SWAT.html#id2957428">The SWAT Home Page</a></dt><dt><a href="SWAT.html#id2957493">Global Settings</a></dt><dt><a href="SWAT.html#id2957601">Share Settings</a></dt><dt><a href="SWAT.html#id2957665">Printers Settings</a></dt><dt><a href="SWAT.html#id2957730">The SWAT Wizard</a></dt><dt><a href="SWAT.html#id2957777">The Status Page</a></dt><dt><a href="SWAT.html#id2957829">The View Page</a></dt><dt><a href="SWAT.html#id2957853">The Password Change Page</a></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SambaHA.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-doc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrading-to-3.0.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 29. High Availability Options </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</td></tr></table></div></body></html> diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html new file mode 100644 index 0000000000..9fdf906ed0 --- /dev/null +++ b/docs/htmldocs/msdfs.html @@ -0,0 +1,51 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 17. Hosting a Microsoft Distributed File System tree on Samba</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="InterdomainTrusts.html" title="Chapter 16. Interdomain Trust Relationships"><link rel="next" href="printing.html" title="Chapter 18. Classical Printing Support"></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 17. Hosting a Microsoft Distributed File System tree on Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="printing.html">Next</a></td></tr></table><hr></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 & Veritas Software<br></span><div class="address"><p><br> + <tt class="email"><<a href="mailto:samba@samba.org">samba@samba.org</a>></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="msdfs.html#id2912546">Features and Benefits</a></dt><dt><a href="msdfs.html#id2912820">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912546"></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 + storage expansion, load balancing etc. + </p><p> + For information about DFS, refer to the +<a href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top">Microsoft documentation</a>. + </p><p> + This document explains how to host a DFS tree on a UNIX machine (for DFS-aware + clients to browse) using Samba. + </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="id2912593"></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="id2912615"></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->msdfs:storage1\share1</tt> in the share directory acts + as the DFS junction. When DFS-aware clients attempt to access the junction link, + they are redirected to the storage location (in this case, \\storage1\share1). + </p><p> + 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="id2912656"></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> +<tt class="prompt">root# </tt><b class="userinput"><tt>chmod 755 /export/dfsroot</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>ln -s msdfs:storageA\\shareA linka</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b> +</pre><p>You should set up the permissions and ownership of + the directory acting as the DFS root such that only designated + users can create, delete or modify the msdfs links. Also note + that symlink names should be all lowercase. This limitation exists + to have Samba avoid trying all the case combinations to get at + the link name. Finally set up the symbolic links to point to the + network shares you want, and start Samba.</p><p>Users on DFS-aware clients can now browse the DFS tree + on the Samba server at \\samba\dfs. Accessing + links linka or linkb (which appear as directories to the client) + takes users directly to the appropriate shares on the network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912820"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 16. Interdomain Trust Relationships </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 18. Classical Printing Support</td></tr></table></div></body></html> diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 4db6d92a8a..cacc1090f6 100644 --- a/docs/htmldocs/net.8.html +++ b/docs/htmldocs/net.8.html @@ -1,943 +1,144 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="net.8"> - -<refmeta> - <refentrytitle>net</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>net</refname> - <refpurpose>Tool for administration of Samba and remote +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>net</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="net.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>net — Tool for administration of Samba and remote CIFS servers. - </refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">net</command> - <arg rep="norepeat" choice="req"><ads|rap|rpc></arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-w workgroup</arg> - <arg rep="norepeat" choice="opt">-W myworkgroup</arg> - <arg rep="norepeat" choice="opt">-U user</arg> - <arg rep="norepeat" choice="opt">-I ip-address</arg> - <arg rep="norepeat" choice="opt">-p port</arg> - <arg rep="norepeat" choice="opt">-n myname</arg> - <arg rep="norepeat" choice="opt">-s conffile</arg> - <arg rep="norepeat" choice="opt">-S server</arg> - <arg rep="norepeat" choice="opt">-l</arg> - <arg rep="norepeat" choice="opt">-P</arg> - <arg rep="norepeat" choice="opt">-D debuglevel</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para>The samba net utility is meant to work just like the net utility + </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">net</tt> {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]</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>The samba net utility is meant to work just like the net utility available for windows and DOS. The first argument should be used to specify the protocol to use when executing a certain command. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000. If this argument is omitted, net will try to determine it automatically. Not all commands are available on all protocols. - </para> - -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - <varlistentry> - <term>-w target-workgroup</term> - <listitem><para> + </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-w target-workgroup</span></dt><dd><p> Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-W workgroup</term> - <listitem><para> + </p></dd><dt><span class="term">-W workgroup</span></dt><dd><p> Sets client workgroup or domain - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-U user</term> - <listitem><para> + </p></dd><dt><span class="term">-U user</span></dt><dd><p> User name to use - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-I ip-address</term> - <listitem><para> + </p></dd><dt><span class="term">-I ip-address</span></dt><dd><p> IP address of target server to use. You have to specify either this option or a target workgroup or a target server. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-p port</term> - <listitem><para> + </p></dd><dt><span class="term">-p port</span></dt><dd><p> Port on the target server to connect to (usually 139 or 445). Defaults to trying 445 first, then 139. - </para></listitem> - </varlistentry> - - -<varlistentry> -<term>-n <primary NetBIOS name></term> -<listitem><para>This option allows you to override + </p></dd><dt><span class="term">-n <primary NetBIOS name></span></dt><dd><p>This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the <indexterm><primary>netbios name</primary></indexterm><parameter moreinfo="none">netbios name</parameter> parameter in the <filename moreinfo="none">smb.conf</filename> file. +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. However, a command line setting will take precedence over settings in -<filename moreinfo="none">smb.conf</filename>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the +<tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - - <varlistentry> - <term>-S server</term> - <listitem><para> +compile time.</p></dd><dt><span class="term">-S server</span></dt><dd><p> Name of target server. You should specify either this option or a target workgroup or a target IP address. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-l</term> - <listitem><para> + </p></dd><dt><span class="term">-l</span></dt><dd><p> When listing data, give more information on each item. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-P</term> - <listitem><para> + </p></dd><dt><span class="term">-P</span></dt><dd><p> Make queries to the external server using the machine account of the local server. - </para></listitem> - </varlistentry> - - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer + </p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - </variablelist> -</refsect1> - -<refsect1> -<title>COMMANDS</title> - -<refsect2> - <title>TIME</title> - - <para>The <command moreinfo="none">NET TIME</command> 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.</para> - -<refsect3> -<title>TIME</title> - -<para>Without any options, the <command moreinfo="none">NET TIME</command> command +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 + 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. -</para> - -</refsect3> - -<refsect3> -<title>TIME SYSTEM</title> - -<para> Displays the time on the remote server in a format ready for <command moreinfo="none">/bin/date</command></para> - -</refsect3> - -<refsect3> -<title>TIME SET</title> -<para>Tries to set the date and time of the local server to that on -the remote server using <command moreinfo="none">/bin/date</command>. </para> - -</refsect3> - -<refsect3> -<title>TIME ZONE</title> - -<para>Displays the timezone in hours from GMT on the remote computer.</para> - -</refsect3> -</refsect2> - -<refsect2> -<title>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]</title> - -<para> +</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. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may -be created.</para> - -<para> +be created.</p><p> [TYPE] may be PDC, BDC or MEMBER to specify the type of server joining the domain. -</para> -</refsect2> - -<refsect2> -<title>[RPC] OLDJOIN [options]</title> - -<para>Join a domain. Use the OLDJOIN option to join the domain +</p></div><div class="refsect2" lang="en"><h3>[RPC] OLDJOIN [options]</h3><p>Join a domain. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust -account in server manager first.</para> -</refsect2> - -<refsect2> -<title>[RPC|ADS] USER</title> - -<refsect3> -<title>[RPC|ADS] USER DELETE <replaceable>target</replaceable></title> - -<para>Delete specified user</para> - -</refsect3> - -<refsect3> -<title>[RPC|ADS] USER LIST</title> - -<para>List all users</para> - -</refsect3> - -<refsect3> -<title>[RPC|ADS] USER INFO <replaceable>target</replaceable></title> - -<para>List the domain groups of a the specified user.</para> - -</refsect3> - -<refsect3> -<title>[RPC|ADS] USER ADD <replaceable>name</replaceable> [password] [-F user flags] [-C comment]</title> - -<para>Add specified user.</para> -</refsect3> -</refsect2> - -<refsect2> -<title>[RPC|ADS] GROUP</title> - -<refsect3> -<title>[RPC|ADS] GROUP [misc options] [targets]</title> -<para>List user groups.</para> -</refsect3> - -<refsect3> -<title>[RPC|ADS] GROUP DELETE <replaceable>name</replaceable> [misc. options]</title> - -<para>Delete specified group.</para> - -</refsect3> - -<refsect3> -<title>[RPC|ADS] GROUP ADD <replaceable>name</replaceable> [-C comment]</title> - -<para>Create specified group.</para> - -</refsect3> -</refsect2> - -<refsect2> -<title>[RAP|RPC] SHARE</title> - -<refsect3> -<title>[RAP|RPC] SHARE [misc. options] [targets]</title> - -<para>Enumerates all exported resources (network shares) on target server.</para> - -</refsect3> - -<refsect3> -<title>[RAP|RPC] SHARE ADD <replaceable>name=serverpath</replaceable> [-C comment] [-M maxusers] [targets]</title> - -<para>Adds a share from a server (makes the export active). Maxusers +account in server manager first.</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] USER</h3><div class="refsect3" lang="en"><h4>[RPC|ADS] USER DELETE <i class="replaceable"><tt>target</tt></i></h4><p>Delete specified user</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER LIST</h4><p>List all users</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER INFO <i class="replaceable"><tt>target</tt></i></h4><p>List the domain groups of a the specified user.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER ADD <i class="replaceable"><tt>name</tt></i> [password] [-F user flags] [-C comment]</h4><p>Add specified user.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|ADS] GROUP</h3><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP [misc options] [targets]</h4><p>List user groups.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP DELETE <i class="replaceable"><tt>name</tt></i> [misc. options]</h4><p>Delete specified group.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP ADD <i class="replaceable"><tt>name</tt></i> [-C comment]</h4><p>Create specified group.</p></div></div><div class="refsect2" lang="en"><h3>[RAP|RPC] SHARE</h3><div class="refsect3" lang="en"><h4>[RAP|RPC] SHARE [misc. options] [targets]</h4><p>Enumerates all exported resources (network shares) on target server.</p></div><div class="refsect3" lang="en"><h4>[RAP|RPC] SHARE ADD <i class="replaceable"><tt>name=serverpath</tt></i> [-C comment] [-M maxusers] [targets]</h4><p>Adds a share from a server (makes the export active). Maxusers specifies the number of users that can be connected to the -share simultaneously.</para> - -</refsect3> - -<refsect3> -<title>SHARE DELETE <replaceable>sharenam</replaceable></title> - -<para>Delete specified share.</para> -</refsect3> -</refsect2> - -<refsect2> -<title>[RPC|RAP] FILE</title> - -<refsect3> -<title>[RPC|RAP] FILE</title> - -<para>List all open files on remote server.</para> - -</refsect3> - -<refsect3> -<title>[RPC|RAP] FILE CLOSE <replaceable>fileid</replaceable></title> - -<para>Close file with specified <replaceable>fileid</replaceable> on -remote server.</para> - -</refsect3> - -<refsect3> -<title>[RPC|RAP] FILE INFO <replaceable>fileid</replaceable></title> - -<para> -Print information on specified <replaceable>fileid</replaceable>. +share simultaneously.</p></div><div class="refsect3" lang="en"><h4>SHARE DELETE <i class="replaceable"><tt>sharenam</tt></i></h4><p>Delete specified share.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|RAP] FILE</h3><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE</h4><p>List all open files on remote server.</p></div><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE CLOSE <i class="replaceable"><tt>fileid</tt></i></h4><p>Close file with specified <i class="replaceable"><tt>fileid</tt></i> on +remote server.</p></div><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE INFO <i class="replaceable"><tt>fileid</tt></i></h4><p> +Print information on specified <i class="replaceable"><tt>fileid</tt></i>. Currently listed are: file-id, username, locks, path, permissions. -</para> - -</refsect3> - -<refsect3> -<title>[RAP|RPC] FILE USER</title> - -<note><para>Currently NOT implemented.</para></note> - -</refsect3> - -</refsect2> - -<refsect2> -<title>SESSION</title> - -<refsect3> -<title>RAP SESSION</title> - -<para>Without any other options, SESSION enumerates all active SMB/CIFS -sessions on the target server.</para> - -</refsect3> - -<refsect3> -<title>RAP SESSION DELETE|CLOSE <replaceable>CLIENT_NAME</replaceable></title> - -<para>Close the specified sessions.</para> - -</refsect3> - -<refsect3> -<title>RAP SESSION INFO <replaceable>CLIENT_NAME</replaceable></title> - -<para>Give a list with all the open files in specified session.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>RAP SERVER <replaceable>DOMAIN</replaceable></title> - -<para>List all servers in specified domain or workgroup. Defaults -to local domain.</para> - -</refsect2> - -<refsect2> -<title>RAP DOMAIN</title> - -<para>Lists all domains and workgroups visible on the -current network.</para> - -</refsect2> - -<refsect2> -<title>RAP PRINTQ</title> - -<refsect3> -<title>RAP PRINTQ LIST <replaceable>QUEUE_NAME</replaceable></title> - -<para>Lists the specified print queue and print jobs on the server. -If the <replaceable>QUEUE_NAME</replaceable> is omitted, all -queues are listed.</para> - -</refsect3> - -<refsect3> -<title>RAP PRINTQ DELETE <replaceable>JOBID</replaceable></title> - -<para>Delete job with specified id.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>RAP VALIDATE <replaceable>user</replaceable> [<replaceable>password</replaceable>]</title> - -<para> +</p></div><div class="refsect3" lang="en"><h4>[RAP|RPC] FILE USER</h4><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><h3>SESSION</h3><div class="refsect3" lang="en"><h4>RAP SESSION</h4><p>Without any other options, SESSION enumerates all active SMB/CIFS +sessions on the target server.</p></div><div class="refsect3" lang="en"><h4>RAP SESSION DELETE|CLOSE <i class="replaceable"><tt>CLIENT_NAME</tt></i></h4><p>Close the specified sessions.</p></div><div class="refsect3" lang="en"><h4>RAP SESSION INFO <i class="replaceable"><tt>CLIENT_NAME</tt></i></h4><p>Give a list with all the open files in specified session.</p></div></div><div class="refsect2" lang="en"><h3>RAP SERVER <i class="replaceable"><tt>DOMAIN</tt></i></h3><p>List all servers in specified domain or workgroup. Defaults +to local domain.</p></div><div class="refsect2" lang="en"><h3>RAP DOMAIN</h3><p>Lists all domains and workgroups visible on the +current network.</p></div><div class="refsect2" lang="en"><h3>RAP PRINTQ</h3><div class="refsect3" lang="en"><h4>RAP PRINTQ LIST <i class="replaceable"><tt>QUEUE_NAME</tt></i></h4><p>Lists the specified print queue and print jobs on the server. +If the <i class="replaceable"><tt>QUEUE_NAME</tt></i> is omitted, all +queues are listed.</p></div><div class="refsect3" lang="en"><h4>RAP PRINTQ DELETE <i class="replaceable"><tt>JOBID</tt></i></h4><p>Delete job with specified id.</p></div></div><div class="refsect2" lang="en"><h3>RAP VALIDATE <i class="replaceable"><tt>user</tt></i> [<i class="replaceable"><tt>password</tt></i>]</h3><p> Validate whether the specified user can log in to the remote server. If the password is not specified on the commandline, it will be prompted. -</para> - -<note><para>Currently NOT implemented.</para></note> - -</refsect2> - -<refsect2> -<title>RAP GROUPMEMBER</title> - -<refsect3> -<title>RAP GROUPMEMBER LIST <replaceable>GROUP</replaceable></title> - -<para>List all members of the specified group.</para> - -</refsect3> - -<refsect3> -<title>RAP GROUPMEMBER DELETE <replaceable>GROUP</replaceable> <replaceable>USER</replaceable></title> - -<para>Delete member from group.</para> - -</refsect3> - -<refsect3> -<title>RAP GROUPMEMBER ADD <replaceable>GROUP</replaceable> <replaceable>USER</replaceable></title> - -<para>Add member to group.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>RAP ADMIN <replaceable>command</replaceable></title> - -<para>Execute the specified <replaceable>command</replaceable> on +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><h3>RAP GROUPMEMBER</h3><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER LIST <i class="replaceable"><tt>GROUP</tt></i></h4><p>List all members of the specified group.</p></div><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER DELETE <i class="replaceable"><tt>GROUP</tt></i> <i class="replaceable"><tt>USER</tt></i></h4><p>Delete member from group.</p></div><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER ADD <i class="replaceable"><tt>GROUP</tt></i> <i class="replaceable"><tt>USER</tt></i></h4><p>Add member to group.</p></div></div><div class="refsect2" lang="en"><h3>RAP ADMIN <i class="replaceable"><tt>command</tt></i></h3><p>Execute the specified <i class="replaceable"><tt>command</tt></i> on the remote server. Only works with OS/2 servers. -</para> - -<note><para>Currently NOT implemented.</para></note> - -</refsect2> - -<refsect2> -<title>RAP SERVICE</title> - -<refsect3> -<title>RAP SERVICE START <replaceable>NAME</replaceable> [arguments...]</title> - -<para>Start the specified service on the remote server. Not implemented yet.</para> - -<note><para>Currently NOT implemented.</para></note> - -</refsect3> - -<refsect3> -<title>RAP SERVICE STOP</title> - -<para>Stop the specified service on the remote server.</para> - -<note><para>Currently NOT implemented.</para></note> - -</refsect3> - -</refsect2> - -<refsect2> -<title>RAP PASSWORD <replaceable>USER</replaceable> <replaceable>OLDPASS</replaceable> <replaceable>NEWPASS</replaceable></title> - -<para> -Change password of <replaceable>USER</replaceable> from <replaceable>OLDPASS</replaceable> to <replaceable>NEWPASS</replaceable>. -</para> - -</refsect2> - -<refsect2> -<title>LOOKUP</title> - -<refsect3> -<title>LOOKUP HOST <replaceable>HOSTNAME</replaceable> [<replaceable>TYPE</replaceable>]</title> - -<para> +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><h3>RAP SERVICE</h3><div class="refsect3" lang="en"><h4>RAP SERVICE START <i class="replaceable"><tt>NAME</tt></i> [arguments...]</h4><p>Start the specified service on the remote server. Not implemented yet.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><h4>RAP SERVICE STOP</h4><p>Stop the specified service on the remote server.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><h3>RAP PASSWORD <i class="replaceable"><tt>USER</tt></i> <i class="replaceable"><tt>OLDPASS</tt></i> <i class="replaceable"><tt>NEWPASS</tt></i></h3><p> +Change password of <i class="replaceable"><tt>USER</tt></i> from <i class="replaceable"><tt>OLDPASS</tt></i> to <i class="replaceable"><tt>NEWPASS</tt></i>. +</p></div><div class="refsect2" lang="en"><h3>LOOKUP</h3><div class="refsect3" lang="en"><h4>LOOKUP HOST <i class="replaceable"><tt>HOSTNAME</tt></i> [<i class="replaceable"><tt>TYPE</tt></i>]</h4><p> Lookup the IP address of the given host with the specified type (netbios suffix). The type defaults to 0x20 (workstation). -</para> - -</refsect3> +</p></div><div class="refsect3" lang="en"><h4>LOOKUP LDAP [<i class="replaceable"><tt>DOMAIN</tt></i></h4><p>Give IP address of LDAP server of specified <i class="replaceable"><tt>DOMAIN</tt></i>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><h4>LOOKUP KDC [<i class="replaceable"><tt>REALM</tt></i>]</h4><p>Give IP address of KDC for the specified <i class="replaceable"><tt>REALM</tt></i>. +Defaults to local realm.</p></div><div class="refsect3" lang="en"><h4>LOOKUP DC [<i class="replaceable"><tt>DOMAIN</tt></i>]</h4><p>Give IP's of Domain Controllers for specified <i class="replaceable"><tt> +DOMAIN</tt></i>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><h4>LOOKUP MASTER <i class="replaceable"><tt>DOMAIN</tt></i></h4><p>Give IP of master browser for specified <i class="replaceable"><tt>DOMAIN</tt></i> +or workgroup. Defaults to local domain.</p></div></div><div class="refsect2" lang="en"><h3>CACHE</h3><p>Samba uses a general caching interface called 'gencache'. It +can be controlled using 'NET CACHE'.</p><p>All the timeout parameters support the suffixes: -<refsect3> -<title>LOOKUP LDAP [<replaceable>DOMAIN</replaceable></title> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>s - Seconds</td></tr><tr><td>m - Minutes</td></tr><tr><td>h - Hours</td></tr><tr><td>d - Days</td></tr><tr><td>w - Weeks</td></tr></table><p> -<para>Give IP address of LDAP server of specified <replaceable>DOMAIN</replaceable>. Defaults to local domain.</para> - -</refsect3> - -<refsect3> -<title>LOOKUP KDC [<replaceable>REALM</replaceable>]</title> - -<para>Give IP address of KDC for the specified <replaceable>REALM</replaceable>. -Defaults to local realm.</para> - -</refsect3> - -<refsect3> -<title>LOOKUP DC [<replaceable>DOMAIN</replaceable>]</title> - -<para>Give IP's of Domain Controllers for specified <replaceable> -DOMAIN</replaceable>. Defaults to local domain.</para> - -</refsect3> - -<refsect3> -<title>LOOKUP MASTER <replaceable>DOMAIN</replaceable></title> - -<para>Give IP of master browser for specified <replaceable>DOMAIN</replaceable> -or workgroup. Defaults to local domain.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>CACHE</title> - -<para>Samba uses a general caching interface called 'gencache'. It -can be controlled using 'NET CACHE'.</para> - -<para>All the timeout parameters support the suffixes: - -<simplelist type="vert"> -<member>s - Seconds</member> -<member>m - Minutes</member> -<member>h - Hours</member> -<member>d - Days</member> -<member>w - Weeks</member> -</simplelist> - -</para> - -<refsect3> -<title>CACHE ADD <replaceable>key</replaceable> <replaceable>data</replaceable> <replaceable>time-out</replaceable></title> - -<para>Add specified key+data to the cache with the given timeout.</para> - -</refsect3> - -<refsect3> -<title>CACHE DEL <replaceable>key</replaceable></title> - -<para>Delete key from the cache.</para> - -</refsect3> - -<refsect3> -<title>CACHE SET <replaceable>key</replaceable> <replaceable>data</replaceable> <replaceable>time-out</replaceable></title> - -<para>Update data of existing cache entry.</para> - -</refsect3> - -<refsect3> -<title>CACHE SEARCH <replaceable>PATTERN</replaceable></title> - -<para>Search for the specified pattern in the cache data.</para> - -</refsect3> - -<refsect3> -<title>CACHE LIST</title> - -<para> +</p><div class="refsect3" lang="en"><h4>CACHE ADD <i class="replaceable"><tt>key</tt></i> <i class="replaceable"><tt>data</tt></i> <i class="replaceable"><tt>time-out</tt></i></h4><p>Add specified key+data to the cache with the given timeout.</p></div><div class="refsect3" lang="en"><h4>CACHE DEL <i class="replaceable"><tt>key</tt></i></h4><p>Delete key from the cache.</p></div><div class="refsect3" lang="en"><h4>CACHE SET <i class="replaceable"><tt>key</tt></i> <i class="replaceable"><tt>data</tt></i> <i class="replaceable"><tt>time-out</tt></i></h4><p>Update data of existing cache entry.</p></div><div class="refsect3" lang="en"><h4>CACHE SEARCH <i class="replaceable"><tt>PATTERN</tt></i></h4><p>Search for the specified pattern in the cache data.</p></div><div class="refsect3" lang="en"><h4>CACHE LIST</h4><p> List all current items in the cache. -</para> - -</refsect3> - -<refsect3> -<title>CACHE FLUSH</title> - -<para>Remove all the current items from the cache.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>GETLOCALSID [DOMAIN]</title> - -<para>Print the SID of the specified domain, or if the parameter is -omitted, the SID of the domain the local server is in.</para> - -</refsect2> - -<refsect2> -<title>SETLOCALSID S-1-5-21-x-y-z</title> - -<para>Sets domain sid for the local server to the specified SID.</para> - -</refsect2> - -<refsect2> -<title>GROUPMAP</title> - -<para>Manage the mappings between Windows group SIDs and UNIX groups. -Parameters take the for "parameter=value". Common options include:</para> - -<itemizedlist> -<listitem><para>unixgroup - Name of the UNIX group</para></listitem> -<listitem><para>ntgroup - Name of the Windows NT group (must be - resolvable to a SID</para></listitem> -<listitem><para>rid - Unsigned 32-bit integer</para></listitem> -<listitem><para>sid - Full SID in the form of "S-1-..."</para></listitem> -<listitem><para>type - Type of the group; either 'domain', 'local', - or 'builtin'</para></listitem> -<listitem><para>comment - Freeform text description of the group</para></listitem> -</itemizedlist> - -<refsect3> -<title>GROUPMAP ADD</title> - -<para>Add a new group mapping entry</para> - -<para>net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]</para> - -</refsect3> - -<refsect3> -<title>GROUPMAP DELETE</title> - -<para>Delete a group mapping entry</para> - -<para>net groupmap delete {ntgroup=string|sid=SID}</para> - -</refsect3> - -<refsect3> -<title>GROUPMAP MODIFY</title> - -<para>Update en existing group entry</para> - -<para>net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}</para> -</refsect3> - -<refsect3> -<title>GROUPMAP LIST</title> - -<para>List existing group mapping entries</para> - -<para>net groupmap list [verbose] [ntgroup=string] [sid=SID]</para> - -</refsect3> -</refsect2> - - - -<refsect2> -<title>MAXRID</title> - -<para>Prints out the highest RID currently in use on the local +</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 "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'). -</para> - -</refsect2> - -<refsect2> -<title>RPC INFO</title> - -<para>Print information about the domain of the remote server, +</p></div><div class="refsect2" lang="en"><h3>RPC INFO</h3><p>Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups. -</para> - -</refsect2> - -<refsect2> -<title>[RPC|ADS] TESTJOIN</title> - -<para>Check whether participation in a domain is still valid.</para> - -</refsect2> - -<refsect2> -<title>[RPC|ADS] CHANGETRUSTPW</title> - -<para>Force change of domain trust password.</para> - -</refsect2> - -<refsect2> -<title>RPC TRUSTDOM</title> - -<refsect3> -<title>RPC TRUSTDOM ADD <replaceable>DOMAIN</replaceable></title> - -<para>Add a interdomain trust account for -<replaceable>DOMAIN</replaceable> to the remote server. -</para> - -</refsect3> - -<refsect3> -<title>RPC TRUSTDOM DEL <replaceable>DOMAIM</replaceable></title> - -<para>Remove interdomain trust account for -<replaceable>DOMAIN</replaceable> from the remote server. -</para> - -<note><para>Currently NOT implemented.</para></note> - -</refsect3> - -<refsect3> -<title>RPC TRUSTDOM ESTABLISH <replaceable>DOMAIN</replaceable></title> - -<para> +</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] TESTJOIN</h3><p>Check whether participation in a domain is still valid.</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] CHANGETRUSTPW</h3><p>Force change of domain trust password.</p></div><div class="refsect2" lang="en"><h3>RPC TRUSTDOM</h3><div class="refsect3" lang="en"><h4>RPC TRUSTDOM ADD <i class="replaceable"><tt>DOMAIN</tt></i></h4><p>Add a interdomain trust account for +<i class="replaceable"><tt>DOMAIN</tt></i> to the remote server. +</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM DEL <i class="replaceable"><tt>DOMAIM</tt></i></h4><p>Remove interdomain trust account for +<i class="replaceable"><tt>DOMAIN</tt></i> from the remote server. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM ESTABLISH <i class="replaceable"><tt>DOMAIN</tt></i></h4><p> Establish a trust relationship to a trusting domain. Interdomain account must already be created on the remote PDC. -</para> - -</refsect3> - -<refsect3> -<title>RPC TRUSTDOM REVOKE <replaceable>DOMAIN</replaceable></title> -<para>Abandon relationship to trusted domain</para> - -</refsect3> - -<refsect3> -<title>RPC TRUSTDOM LIST</title> - -<para>List all current interdomain trust relationships.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>RPC ABORTSHUTDOWN</title> - -<para>Abort the shutdown of a remote server.</para> - -</refsect2> - -<refsect2> -<title>SHUTDOWN [-t timeout] [-r] [-f] [-C message]</title> - -<para>Shut down the remote server.</para> - -<variablelist> -<varlistentry> -<term>-r</term> -<listitem><para> +</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM REVOKE <i class="replaceable"><tt>DOMAIN</tt></i></h4><p>Abandon relationship to trusted domain</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM LIST</h4><p>List all current interdomain trust relationships.</p></div></div><div class="refsect2" lang="en"><h3>RPC ABORTSHUTDOWN</h3><p>Abort the shutdown of a remote server.</p></div><div class="refsect2" lang="en"><h3>SHUTDOWN [-t timeout] [-r] [-f] [-C message]</h3><p>Shut down the remote server.</p><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p> Reboot after shutdown. -</para></listitem> -</varlistentry> - -<varlistentry> -<term>-f</term> -<listitem><para> +</p></dd><dt><span class="term">-f</span></dt><dd><p> Force shutting down all applications. -</para></listitem> -</varlistentry> - -<varlistentry> -<term>-t timeout</term> -<listitem><para> +</p></dd><dt><span class="term">-t timeout</span></dt><dd><p> Timeout before system will be shut down. An interactive user of the system can use this time to cancel the shutdown. -</para></listitem> -</varlistentry>'> - -<varlistentry> -<term>-C message</term> -<listitem><para>Display the specified message on the screen to -announce the shutdown.</para></listitem> -</varlistentry> -</variablelist> - -</refsect2> - -<refsect2> -<title>SAMDUMP</title> - -<para>Print out sam database of remote server. You need -to run this on either a BDC. <!-- -Is that correct? - Jelmer --></para> -</refsect2> - -<refsect2> -<title>VAMPIRE</title> - -<para>Export users, aliases and groups from remote server to +</p></dd><dt><span class="term">-C message</span></dt><dd><p>Display the specified message on the screen to +announce the shutdown.</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SAMDUMP</h3><p>Print out sam database of remote server. You need +to run this on either a BDC. </p></div><div class="refsect2" lang="en"><h3>VAMPIRE</h3><p>Export users, aliases and groups from remote server to local server. Can only be run an a BDC. -</para> - -</refsect2> - -<refsect2> -<title>GETSID</title> - -<para>Fetch domain SID and store it in the local <filename moreinfo="none">secrets.tdb</filename>. </para> - -</refsect2> - -<refsect2> -<title>ADS LEAVE</title> - -<para>Make the remote host leave the domain it is part of. </para> - -</refsect2> - -<refsect2> -<title>ADS STATUS</title> - -<para>Print out status of machine account of the local machine in ADS. +</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 <command moreinfo="none">NET ADS TESTJOIN</command>.</para> - -</refsect2> - -<refsect2> -<title>ADS PRINTER</title> - -<refsect3> -<title>ADS PRINTER INFO [<replaceable>PRINTER</replaceable>] [<replaceable>SERVER</replaceable>]</title> - -<para> -Lookup info for <replaceable>PRINTER</replaceable> on <replaceable>SERVER</replaceable>. The printer name defaults to "*", the -server name defaults to the local host.</para> - -</refsect3> - -<refsect3> -<title>ADS PRINTER PUBLISH <replaceable>PRINTER</replaceable></title> - -<para>Publish specified printer using ADS.</para> - -</refsect3> - -<refsect3> -<title>ADS PRINTER REMOVE <replaceable>PRINTER</replaceable></title> - -<para>Remove specified printer from ADS directory.</para> - -</refsect3> - -</refsect2> - -<refsect2> -<title>ADS SEARCH <replaceable>EXPRESSION</replaceable> <replaceable>ATTRIBUTES...</replaceable></title> - -<para>Perform a raw LDAP search on a ADS server and dump the results. The +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 "*", 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.</para> - -<para>Example: <userinput moreinfo="none">net ads search '(objectCategory=group)' sAMAccountName</userinput> -</para> - -</refsect2> - -<refsect2> -<title>ADS DN <replaceable>DN</replaceable> <replaceable>(attributes)</replaceable></title> - -<para> +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> +</p></div><div class="refsect2" lang="en"><h3>ADS DN <i class="replaceable"><tt>DN</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 DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result. -</para> - -<para>Example: <userinput moreinfo="none">net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</userinput></para> - -</refsect2> - -<refsect2> -<title>WORKGROUP</title> - -<para>Print out workgroup name for specified kerberos realm.</para> - -</refsect2> - - -<refsect2> -<title>HELP [COMMAND]</title> - -<para>Gives usage information for the specified command.</para> - -</refsect2> - -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is complete for version 3.0 of the Samba - suite.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities +</p><p>Example: <b class="userinput"><tt>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</tt></b></p></div><div class="refsect2" lang="en"><h3>WORKGROUP</h3><p>Print out workgroup name for specified kerberos realm.</p></div><div class="refsect2" lang="en"><h3>HELP [COMMAND]</h3><p>Gives usage information for the specified command.</p></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is complete for version 3.0 of the Samba + suite.</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 - to the way the Linux kernel is developed.</para> - - <para>The net manpage was written by Jelmer Vernooij.</para> - -</refsect1> - -</refentry> + to the way the Linux kernel is developed.</p><p>The net manpage was written by Jelmer Vernooij.</p></div></div></body></html> diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 815534dad9..ad1c7990c0 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -1,354 +1,147 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="nmbd.8"> - -<refmeta> - <refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>nmbd</refname> - <refpurpose>NetBIOS name server to provide NetBIOS - over IP naming services to clients</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">nmbd</command> - <arg rep="norepeat" choice="opt">-D</arg> - <arg rep="norepeat" choice="opt">-F</arg> - <arg rep="norepeat" choice="opt">-S</arg> - <arg rep="norepeat" choice="opt">-a</arg> - <arg rep="norepeat" choice="opt">-i</arg> - <arg rep="norepeat" choice="opt">-o</arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-V</arg> - <arg rep="norepeat" choice="opt">-d <debug level></arg> - <arg rep="norepeat" choice="opt">-H <lmhosts file></arg> - <arg rep="norepeat" choice="opt">-l <log directory></arg> - <arg rep="norepeat" choice="opt">-n <primary netbios name></arg> - <arg rep="norepeat" choice="opt">-p <port number></arg> - <arg rep="norepeat" choice="opt">-s <configuration file></arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - <para>This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">nmbd</command> is a server that understands +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmbd</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="nmbd.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>nmbd — NetBIOS name server to provide NetBIOS + over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">nmbd</tt> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program 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">nmbd</b> is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients. It also participates in the browsing protocols which make up the - Windows "Network Neighborhood" view.</para> - - <para>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.</para> - - <para>Amongst other services, <command moreinfo="none">nmbd</command> will + 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 "own NetBIOS name" is by default the primary DNS name of the host it is running on, - but this can be overridden with the <emphasis>-n</emphasis> - option (see OPTIONS below). Thus <command moreinfo="none">nmbd</command> will + 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 reply to broadcast queries for its own name(s). Additional - names for <command moreinfo="none">nmbd</command> to respond on can be set - via parameters in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> configuration file.</para> - - <para><command moreinfo="none">nmbd</command> can also be used as a WINS + names for <b class="command">nmbd</b> to respond on can be set + via parameters in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> configuration file.</p><p><b class="command">nmbd</b> can also be used as a WINS (Windows Internet Name Server) server. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and - replying to queries from clients for these names.</para> - - <para>In addition, <command moreinfo="none">nmbd</command> can act as a WINS + replying to queries from clients for these names.</p><p>In addition, <b class="command">nmbd</b> can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS - server.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-D</term> - <listitem><para>If specified, this parameter causes - <command moreinfo="none">nmbd</command> to operate as a daemon. That is, + server.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes + <b class="command">nmbd</b> to operate as a daemon. That is, it detaches itself and runs in the background, fielding - requests on the appropriate port. By default, <command moreinfo="none">nmbd</command> + requests on the appropriate port. By default, <b class="command">nmbd</b> will operate as a daemon if launched from a command shell. - nmbd can also be operated from the <command moreinfo="none">inetd</command> + nmbd can also be operated from the <b class="command">inetd</b> meta-daemon, although this is not recommended. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-F</term> - <listitem><para>If specified, this parameter causes - the main <command moreinfo="none">nmbd</command> process to not daemonize, + </p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes + the main <b class="command">nmbd</b> process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running - <command moreinfo="none">nmbd</command> under process supervisors such - as <command moreinfo="none">supervise</command> and <command moreinfo="none">svscan</command> - from Daniel J. Bernstein's <command moreinfo="none">daemontools</command> + <b class="command">nmbd</b> under process supervisors such + as <b class="command">supervise</b> and <b class="command">svscan</b> + from Daniel J. Bernstein's <b class="command">daemontools</b> package, or the AIX process monitor. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-S</term> - <listitem><para>If specified, this parameter causes - <command moreinfo="none">nmbd</command> to log to standard output rather - than a file.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-i</term> - <listitem><para>If this parameter is specified it causes the + </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 "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. <command moreinfo="none">nmbd</command> also logs to standard - output, as if the <constant>-S</constant> parameter had been - given. </para></listitem> - </varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - <varlistentry> - <term>-H <filename></term> - <listitem><para>NetBIOS lmhosts file. The lmhosts + command line. <b class="command">nmbd</b> also logs to standard + output, as if the <tt class="constant">-S</tt> parameter had been + given. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-H <filename></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 <indexterm><primary>name resolve order</primary></indexterm><parameter moreinfo="none">name resolve order</parameter> described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> to resolve any + 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 NetBIOS name queries needed by the server. Note - that the contents of this file are <emphasis>NOT</emphasis> - used by <command moreinfo="none">nmbd</command> to answer any name queries. + 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. Adding a line to this file affects name NetBIOS resolution - from this host <emphasis>ONLY</emphasis>.</para> - - <para>The default path to this file is compiled into + from this host <span class="emphasis"><em>ONLY</em></span>.</p><p>The default path to this file is compiled into Samba as part of the build process. Common defaults - are <filename moreinfo="none">/usr/local/samba/lib/lmhosts</filename>, - <filename moreinfo="none">/usr/samba/lib/lmhosts</filename> or - <filename moreinfo="none">/etc/samba/lmhosts</filename>. See the <citerefentry><refentrytitle>lmhosts</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page for details on the contents of this file.</para></listitem> - </varlistentry> - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + are <tt class="filename">/usr/local/samba/lib/lmhosts</tt>, + <tt class="filename">/usr/samba/lib/lmhosts</tt> or + <tt class="filename">/etc/samba/lmhosts</tt>. See the <a href="lmhosts.5.html"><span class="citerefentry"><span class="refentrytitle">lmhosts</span>(5)</span></a> man page for details on the contents of this file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +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 +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. -</para></listitem> -</varlistentry> - - - <varlistentry> - <term>-p <UDP port number></term> - <listitem><para>UDP port number is a positive integer value. +</p></dd><dt><span class="term">-p <UDP port number></span></dt><dd><p>UDP port number is a positive integer value. This option changes the default UDP port number (normally 137) - that <command moreinfo="none">nmbd</command> responds to name queries on. Don't + that <b class="command">nmbd</b> responds to name queries on. Don't use this option unless you are an expert, in which case you - won't need help!</para></listitem> - </varlistentry> - - </variablelist> -</refsect1> - -<refsect1> - <title>FILES</title> - - <variablelist> - <varlistentry> - <term><filename moreinfo="none">/etc/inetd.conf</filename></term> - <listitem><para>If the server is to be run by the - <command moreinfo="none">inetd</command> meta-daemon, this file + won't need help!</p></dd></dl></div></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>If the server is to be run by the + <b class="command">inetd</b> meta-daemon, this file must contain suitable startup information for the meta-daemon. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/etc/rc</filename></term> - <listitem><para>or whatever initialization script your - system uses).</para> - - <para>If running the server as a daemon at startup, + </p></dd><dt><span class="term"><tt class="filename">/etc/rc</tt></span></dt><dd><p>or whatever initialization script your + system uses).</p><p>If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server.</para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/etc/services</filename></term> - <listitem><para>If running the server via the - meta-daemon <command moreinfo="none">inetd</command>, this file + sequence for the server.</p></dd><dt><span class="term"><tt class="filename">/etc/services</tt></span></dt><dd><p>If running the server via the + meta-daemon <b class="command">inetd</b>, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of - the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> server + </p></dd><dt><span class="term"><tt class="filename">/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of + the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server configuration file. Other common places that systems - install this file are <filename moreinfo="none">/usr/samba/lib/smb.conf</filename> - and <filename moreinfo="none">/etc/samba/smb.conf</filename>.</para> - - <para>When run as a WINS server (see the - <indexterm><primary>wins support</primary></indexterm><parameter moreinfo="none">wins support</parameter> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page), - <command moreinfo="none">nmbd</command> - will store the WINS database in the file <filename moreinfo="none">wins.dat</filename> - in the <filename moreinfo="none">var/locks</filename> directory configured under - wherever Samba was configured to install itself.</para> - - <para>If <command moreinfo="none">nmbd</command> is acting as a <emphasis> - browse master</emphasis> (see the <indexterm><primary>local master</primary></indexterm><parameter moreinfo="none">local master</parameter> - parameter in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> man page, <command moreinfo="none">nmbd</command> - will store the browsing database in the file <filename moreinfo="none">browse.dat - </filename> in the <filename moreinfo="none">var/locks</filename> directory + 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> + 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> + 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 configured under wherever Samba was configured to install itself. - </para></listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>SIGNALS</title> - - <para>To shut down an <command moreinfo="none">nmbd</command> process it is recommended - that SIGKILL (-9) <emphasis>NOT</emphasis> be used, except as a last + </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>To shut down an <b class="command">nmbd</b> process it is recommended + that SIGKILL (-9) <span class="emphasis"><em>NOT</em></span> be used, except as a last resort, as this may leave the name database in an inconsistent state. - The correct way to terminate <command moreinfo="none">nmbd</command> is to send it - a SIGTERM (-15) signal and wait for it to die on its own.</para> - - <para><command moreinfo="none">nmbd</command> will accept SIGHUP, which will cause - it to dump out its namelists into the file <filename moreinfo="none">namelist.debug - </filename> in the <filename moreinfo="none">/usr/local/samba/var/locks</filename> - directory (or the <filename moreinfo="none">var/locks</filename> directory configured + The correct way to terminate <b class="command">nmbd</b> is to send it + a SIGTERM (-15) signal and wait for it to die on its own.</p><p><b class="command">nmbd</b> will accept SIGHUP, which will cause + it to dump out its namelists into the file <tt class="filename">namelist.debug + </tt> in the <tt class="filename">/usr/local/samba/var/locks</tt> + directory (or the <tt class="filename">var/locks</tt> directory configured under wherever Samba was configured to install itself). This will also - cause <command moreinfo="none">nmbd</command> to dump out its server database in - the <filename moreinfo="none">log.nmb</filename> file.</para> - - <para>The debug log level of nmbd may be raised or lowered - using <citerefentry><refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> (SIGUSR[1|2] signals + cause <b class="command">nmbd</b> to dump out its server database in + the <tt class="filename">log.nmb</tt> file.</p><p>The debug log level of nmbd may be raised or lowered + using <a href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a> (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running - at a normally low log level.</para> -</refsect1> - - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para> - <citerefentry><refentrytitle>inetd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, and the Internet - RFC's <filename moreinfo="none">rfc1001.txt</filename>, <filename moreinfo="none">rfc1002.txt</filename>. + at a normally low log level.</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="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the Internet + RFC's <tt class="filename">rfc1001.txt</tt>, <tt class="filename">rfc1002.txt</tt>. In addition the CIFS (formerly SMB) specification is available - as a link from the Web page <ulink url="http://samba.org/cifs/"> - http://samba.org/cifs/</ulink>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + as a link from the Web page <a href="http://samba.org/cifs/" target="_top"> + http://samba.org/cifs/</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 26320c93b2..21e84c9c71 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -1,322 +1,105 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="nmblookup"> - -<refmeta> - <refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>nmblookup</refname> - <refpurpose>NetBIOS over TCP/IP client used to lookup NetBIOS - names</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">nmblookup</command> - <arg rep="norepeat" choice="opt">-M</arg> - <arg rep="norepeat" choice="opt">-R</arg> - <arg rep="norepeat" choice="opt">-S</arg> - <arg rep="norepeat" choice="opt">-r</arg> - <arg rep="norepeat" choice="opt">-A</arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-B <broadcast address></arg> - <arg rep="norepeat" choice="opt">-U <unicast address></arg> - <arg rep="norepeat" choice="opt">-d <debug level></arg> - <arg rep="norepeat" choice="opt">-s <smb config file></arg> - <arg rep="norepeat" choice="opt">-i <NetBIOS scope></arg> - <arg rep="norepeat" choice="opt">-T</arg> - <arg rep="norepeat" choice="opt">-f</arg> - <arg rep="norepeat" choice="req">name</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">nmblookup</command> is used to query NetBIOS names +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmblookup</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="nmblookup"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>nmblookup — NetBIOS over TCP/IP client used to lookup NetBIOS + names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">nmblookup</tt> [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}</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">nmblookup</b> is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine. All queries - are done over UDP.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-M</term> - <listitem><para>Searches for a master browser by looking - up the NetBIOS name <replaceable>name</replaceable> with a - type of <constant>0x1d</constant>. If <replaceable> - name</replaceable> is "-" then it does a lookup on the special name - <constant>__MSBROWSE__</constant>. Please note that in order to + 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 "-" then it does a lookup on the special name + <tt class="constant">__MSBROWSE__</tt>. Please note that in order to use the name "-", you need to make sure "-" isn't parsed as an argument, e.g. use : - <userinput moreinfo="none">nmblookup -M -- -</userinput>.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-R</term> - <listitem><para>Set the recursion desired bit in the packet + <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 query to a machine running a WINS server and the user wishes to query the names in the WINS server. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead. See RFC1001, RFC1002 for details. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-S</term> - <listitem><para>Once the name query has returned an IP + </p></dd><dt><span class="term">-S</span></dt><dd><p>Once the name query has returned an IP address then do a node status query as well. A node status query returns the NetBIOS names registered by a host. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-r</term> - <listitem><para>Try and bind to UDP port 137 to send and receive UDP + </p></dd><dt><span class="term">-r</span></dt><dd><p>Try and bind to UDP port 137 to send and receive UDP datagrams. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and - in addition, if the <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon is running on this machine it also binds to this port. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-A</term> - <listitem><para>Interpret <replaceable>name</replaceable> as - an IP Address and do a node status query on this address.</para> - </listitem> - </varlistentry> - - - - - -<varlistentry> -<term>-n <primary NetBIOS name></term> -<listitem><para>This option allows you to override + in addition, if the <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> daemon is running on this machine it also binds to this port. + </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 <primary NetBIOS name></span></dt><dd><p>This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the <indexterm><primary>netbios name</primary></indexterm><parameter moreinfo="none">netbios name</parameter> parameter in the <filename moreinfo="none">smb.conf</filename> file. +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. However, a command line setting will take precedence over settings in -<filename moreinfo="none">smb.conf</filename>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-i <scope></term> -<listitem><para>This specifies a NetBIOS scope that -<command moreinfo="none">nmblookup</command> will use to communicate with when +<tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-i <scope></span></dt><dd><p>This specifies a NetBIOS scope that +<b class="command">nmblookup</b> will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -<emphasis>very</emphasis> rarely used, only set this parameter +<span class="emphasis"><em>very</em></span> rarely used, only set this parameter if you are the system administrator in charge of all the -NetBIOS systems you communicate with.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-W|--workgroup=domain</term> -<listitem><para>Set the SMB domain of the username. This +NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This overrides the default domain which is the domain defined in smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). </para></listitem> -</varlistentry> - -<varlistentry> -<term>-O socket options</term> -<listitem><para>TCP socket options to set on the client +SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client socket. See the socket options parameter in -the <filename moreinfo="none">smb.conf</filename> manual page for the list of valid -options. </para></listitem> -</varlistentry> - - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - <varlistentry> - <term>-B <broadcast address></term> - <listitem><para>Send the query to the given broadcast address. Without +the <tt class="filename">smb.conf</tt> manual page for the list of valid +options. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-B <broadcast address></span></dt><dd><p>Send the query to the given broadcast address. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as - either auto-detected or defined in the <ulink url="smb.conf.5.html#INTERFACES"><parameter moreinfo="none">interfaces</parameter> - </ulink> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. - </para></listitem> - </varlistentry> - - - - <varlistentry> - <term>-U <unicast address></term> - <listitem><para>Do a unicast query to the specified address or - host <replaceable>unicast address</replaceable>. This option - (along with the <parameter moreinfo="none">-R</parameter> option) is needed to - query a WINS server.</para></listitem> - </varlistentry> - - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + either auto-detected or defined in the <a href="smb.conf.5.html#INTERFACES" target="_top"><i class="parameter"><tt>interfaces</tt></i> + </a> parameter of the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. + </p></dd><dt><span class="term">-U <unicast address></span></dt><dd><p>Do a unicast query to the specified address or + host <i class="replaceable"><tt>unicast address</tt></i>. This option + (along with the <i class="parameter"><tt>-R</tt></i> option) is needed to + query a WINS server.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +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 +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. -</para></listitem> -</varlistentry> - - - <varlistentry> - <term>-T</term> - <listitem><para>This causes any IP addresses found in the +</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 - DNS name, and printed out before each</para> - - <para><emphasis>IP address .... NetBIOS name</emphasis></para> - - <para> pair that is the normal output.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-f</term> - <listitem><para> + DNS name, and printed out before each</p><p><span class="emphasis"><em>IP address .... NetBIOS name</em></span></p><p> pair that is the normal output.</p></dd><dt><span class="term">-f</span></dt><dd><p> Show which flags apply to the name that has been looked up. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>name</term> - <listitem><para>This is the NetBIOS name being queried. Depending + </p></dd><dt><span class="term">name</span></dt><dd><p>This is the NetBIOS name being queried. Depending upon the previous options this may be a NetBIOS name or IP address. If a NetBIOS name then the different name types may be specified by appending '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast - area.</para></listitem> - </varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>EXAMPLES</title> - - <para><command moreinfo="none">nmblookup</command> can be used to query - a WINS server (in the same way <command moreinfo="none">nslookup</command> is - used to query DNS servers). To query a WINS server, <command moreinfo="none">nmblookup</command> - must be called like this:</para> - - <para><command moreinfo="none">nmblookup -U server -R 'name'</command></para> - - <para>For example, running :</para> - - <para><command moreinfo="none">nmblookup -U samba.org -R 'IRIX#1B'</command></para> - - <para>would query the WINS server samba.org for the domain - master browser (1B name type) for the IRIX workgroup.</para> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, and <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + area.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p><b class="command">nmblookup</b> can be used to query + a WINS server (in the same way <b class="command">nslookup</b> is + used to query DNS servers). To query a WINS server, <b class="command">nmblookup</b> + must be called like this:</p><p><b class="command">nmblookup -U server -R 'name'</b></p><p>For example, running :</p><p><b class="command">nmblookup -U samba.org -R 'IRIX#1B'</b></p><p>would query the WINS server samba.org for the domain + master browser (1B name type) for the IRIX workgroup.</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="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, and <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/ntlm_auth.1.html b/docs/htmldocs/ntlm_auth.1.html index 3fe48ac02d..e048efae7b 100644 --- a/docs/htmldocs/ntlm_auth.1.html +++ b/docs/htmldocs/ntlm_auth.1.html @@ -31,7 +31,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="id2796757"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796746"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html new file mode 100644 index 0000000000..bd76a344f8 --- /dev/null +++ b/docs/htmldocs/optional.html @@ -0,0 +1,35 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part III. Advanced Configuration</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="samba-doc.html" title="SAMBA Project Documentation"><link rel="previous" href="ClientConfig.html" title="Chapter 9. MS Windows Network Configuration Guide"><link rel="next" href="NetworkBrowsing.html" title="Chapter 10. Samba / MS Windows Network Browsing Guide"></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">Part III. Advanced Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr></table><hr></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="id2893806"></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.html">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2893931">Features and Benefits</a></dt><dt><a href="NetworkBrowsing.html#id2894019">What is Browsing?</a></dt><dt><a href="NetworkBrowsing.html#id2894333">Discussion</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2894349">NetBIOS over TCP/IP</a></dt><dt><a href="NetworkBrowsing.html#id2894584">TCP/IP - without NetBIOS</a></dt><dt><a href="NetworkBrowsing.html#id2894750">DNS and Active Directory</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2894896">How Browsing Functions</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="NetworkBrowsing.html#id2895446">Setting up DOMAIN Browsing</a></dt><dt><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="NetworkBrowsing.html#id2895844">Making Samba the domain master</a></dt><dt><a href="NetworkBrowsing.html#id2896022">Note about broadcast addresses</a></dt><dt><a href="NetworkBrowsing.html#id2896045">Multiple interfaces</a></dt><dt><a href="NetworkBrowsing.html#id2896081">Use of the Remote Announce parameter</a></dt><dt><a href="NetworkBrowsing.html#id2896240">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2896317">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2896504">Setting up a WINS server</a></dt><dt><a href="NetworkBrowsing.html#id2896761">WINS Replication</a></dt><dt><a href="NetworkBrowsing.html#id2896787">Static WINS Entries</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2896875">Helpful Hints</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2896889">Windows Networking Protocols</a></dt><dt><a href="NetworkBrowsing.html#id2896967">Name Resolution Order</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2897133">Technical Overview of browsing</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2897187">Browsing support in Samba</a></dt><dt><a href="NetworkBrowsing.html#id2897308">Problem resolution</a></dt><dt><a href="NetworkBrowsing.html#id2897396">Browsing across subnets</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2898078">Common Errors</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2898092">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="NetworkBrowsing.html#id2898121">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="NetworkBrowsing.html#id2898166">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="passdb.html">Account Information Databases</a></dt><dd><dl><dt><a href="passdb.html#id2898446">Features and Benefits</a></dt><dd><dl><dt><a href="passdb.html#id2898460">Backwards Compatibility Backends</a></dt><dt><a href="passdb.html#id2898561">New Backends</a></dt></dl></dd><dt><a href="passdb.html#id2898749">Technical Information</a></dt><dd><dl><dt><a href="passdb.html#id2898874">Important Notes About Security</a></dt><dt><a href="passdb.html#id2899165">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="passdb.html#id2899351">The smbpasswd Command</a></dt><dt><a href="passdb.html#id2899622">The pdbedit Command</a></dt></dl></dd><dt><a href="passdb.html#id2899860">Password Backends</a></dt><dd><dl><dt><a href="passdb.html#id2899902">Plain Text</a></dt><dt><a href="passdb.html#id2899942">smbpasswd - Encrypted Password Database</a></dt><dt><a href="passdb.html#id2900055">tdbsam</a></dt><dt><a href="passdb.html#id2900089">ldapsam</a></dt><dt><a href="passdb.html#id2901940">MySQL</a></dt><dt><a href="passdb.html#XMLpassdb">XML</a></dt></dl></dd><dt><a href="passdb.html#id2902790">Common Errors</a></dt><dd><dl><dt><a href="passdb.html#id2902796">Users can not logon</a></dt><dt><a href="passdb.html#id2902841">Users being added to wrong backend database</a></dt><dt><a href="passdb.html#id2902952">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="groupmapping.html">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="groupmapping.html#id2903181">Features and Benefits</a></dt><dt><a href="groupmapping.html#id2903416">Discussion</a></dt><dd><dl><dt><a href="groupmapping.html#id2903652">Example Configuration</a></dt></dl></dd><dt><a href="groupmapping.html#id2903718">Configuration Scripts</a></dt><dd><dl><dt><a href="groupmapping.html#id2903732">Sample smb.conf add group script</a></dt><dt><a href="groupmapping.html#id2903817">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="groupmapping.html#id2903900">Common Errors</a></dt><dd><dl><dt><a href="groupmapping.html#id2903915">Adding Groups Fails</a></dt><dt><a href="groupmapping.html#id2903984">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="groupmapping.html#id2904010">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="AccessControls.html">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="AccessControls.html#id2904266">Features and Benefits</a></dt><dt><a href="AccessControls.html#id2904395">File System Access Controls</a></dt><dd><dl><dt><a href="AccessControls.html#id2904431">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="AccessControls.html#id2904735">Managing Directories</a></dt><dt><a href="AccessControls.html#id2904829">File and Directory Access Control</a></dt></dl></dd><dt><a href="AccessControls.html#id2905040">Share Definition Access Controls</a></dt><dd><dl><dt><a href="AccessControls.html#id2905070">User and Group Based Controls</a></dt><dt><a href="AccessControls.html#id2905491">File and Directory Permissions Based Controls</a></dt><dt><a href="AccessControls.html#id2905871">Miscellaneous Controls</a></dt></dl></dd><dt><a href="AccessControls.html#id2906251">Access Controls on Shares</a></dt><dd><dl><dt><a href="AccessControls.html#id2906323">Share Permissions Management</a></dt></dl></dd><dt><a href="AccessControls.html#id2906623">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="AccessControls.html#id2906631">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="AccessControls.html#id2906675">Viewing File Security on a Samba Share</a></dt><dt><a href="AccessControls.html#id2906755">Viewing file ownership</a></dt><dt><a href="AccessControls.html#id2906887">Viewing File or Directory Permissions</a></dt><dt><a href="AccessControls.html#id2907132">Modifying file or directory permissions</a></dt><dt><a href="AccessControls.html#id2907296">Interaction with the standard Samba create mask + parameters</a></dt><dt><a href="AccessControls.html#id2907693">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="AccessControls.html#id2907788">Common Errors</a></dt><dd><dl><dt><a href="AccessControls.html#id2907802">Users can not write to a public share</a></dt><dt><a href="AccessControls.html#id2908232">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="AccessControls.html#id2908284">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="locking.html">File and Record Locking</a></dt><dd><dl><dt><a href="locking.html#id2908532">Features and Benefits</a></dt><dt><a href="locking.html#id2908589">Discussion</a></dt><dd><dl><dt><a href="locking.html#id2908732">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="locking.html#id2909449">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="locking.html#id2909569">Example Configuration</a></dt></dl></dd><dt><a href="locking.html#id2909983">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="locking.html#id2910208">Workstation Service Entries</a></dt><dt><a href="locking.html#id2910237">Server Service Entries</a></dt></dl></dd><dt><a href="locking.html#id2910317">Persistent Data Corruption</a></dt><dt><a href="locking.html#id2910345">Common Errors</a></dt><dd><dl><dt><a href="locking.html#id2910419">locking.tdb error messages</a></dt><dt><a href="locking.html#id2910456">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="locking.html#id2910479">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="locking.html#id2910511">Additional Reading</a></dt></dl></dd><dt>15. <a href="securing-samba.html">Securing Samba</a></dt><dd><dl><dt><a href="securing-samba.html#id2910685">Introduction</a></dt><dt><a href="securing-samba.html#id2910722">Features and Benefits</a></dt><dt><a href="securing-samba.html#id2910796">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="securing-samba.html#id2910816">Using host based protection</a></dt><dt><a href="securing-samba.html#id2910915">User based protection</a></dt><dt><a href="securing-samba.html#id2910975">Using interface protection</a></dt><dt><a href="securing-samba.html#id2911042">Using a firewall</a></dt><dt><a href="securing-samba.html#id2911098">Using a IPC$ share deny</a></dt><dt><a href="securing-samba.html#id2911187">NTLMv2 Security</a></dt></dl></dd><dt><a href="securing-samba.html#id2911245">Upgrading Samba</a></dt><dt><a href="securing-samba.html#id2911271">Common Errors</a></dt><dd><dl><dt><a href="securing-samba.html#id2911289">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="securing-samba.html#id2911314">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#id2911605">Features and Benefits</a></dt><dt><a href="InterdomainTrusts.html#id2911633">Trust Relationship Background</a></dt><dt><a href="InterdomainTrusts.html#id2911721">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#id2911750">Creating an NT4 Domain Trust</a></dt><dt><a href="InterdomainTrusts.html#id2911822">Completing an NT4 Domain Trust</a></dt><dt><a href="InterdomainTrusts.html#id2911868">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="InterdomainTrusts.html#id2912046">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="InterdomainTrusts.html#id2912232">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="InterdomainTrusts.html#id2912370">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="InterdomainTrusts.html#id2912476">Common Errors</a></dt></dl></dd><dt>17. <a href="msdfs.html">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="msdfs.html#id2912546">Features and Benefits</a></dt><dt><a href="msdfs.html#id2912820">Common Errors</a></dt></dl></dd><dt>18. <a href="printing.html">Classical Printing Support</a></dt><dd><dl><dt><a href="printing.html#id2912941">Features and Benefits</a></dt><dt><a href="printing.html#id2913045">Technical Introduction</a></dt><dd><dl><dt><a href="printing.html#id2913083">What happens if you send a Job from a Client</a></dt><dt><a href="printing.html#id2913154">Printing Related Configuration Parameters</a></dt><dt><a href="printing.html#id2913251">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="printing.html#id2913718">A simple Configuration to Print</a></dt><dd><dl><dt><a href="printing.html#id2913883">Verification of "Settings in Use" with testparm</a></dt><dt><a href="printing.html#id2914010">A little Experiment to warn you</a></dt></dl></dd><dt><a href="printing.html#id2914370">Extended Sample Configuration to Print</a></dt><dt><a href="printing.html#id2914701">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="printing.html#id2914714">The [global] Section</a></dt><dt><a href="printing.html#id2915245">The [printers] Section</a></dt><dt><a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt><dt><a href="printing.html#id2916027">Print Commands</a></dt><dt><a href="printing.html#id2916108">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="printing.html#id2916791">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="printing.html#id2917131">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="printing.html#id2917292">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="printing.html#id2917453">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="printing.html#id2917566">Creating the [print$] Share</a></dt><dt><a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt><dt><a href="printing.html#id2918066">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="printing.html#id2918239">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="printing.html#id2918333">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="printing.html#id2918531">Setting Drivers for existing Printers with +rpcclient</a></dt></dl></dd><dt><a href="printing.html#id2920241">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="printing.html#id2920260">The first Client Driver Installation</a></dt><dt><a href="printing.html#id2920462">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="printing.html#id2920763">Further Client Driver Install Procedures</a></dt><dt><a href="printing.html#id2920857">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="printing.html#id2921029">Other Gotchas</a></dt><dd><dl><dt><a href="printing.html#id2921063">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="printing.html#id2921530">Supporting large Numbers of Printers</a></dt><dt><a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a></dt><dt><a href="printing.html#id2922136">Weird Error Message Cannot connect under a +different Name</a></dt><dt><a href="printing.html#id2922236">Be careful when assembling Driver Files</a></dt><dt><a href="printing.html#id2922594">Samba and Printer Ports</a></dt><dt><a href="printing.html#id2922687">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="printing.html#id2922712">The Imprints Toolset</a></dt><dd><dl><dt><a href="printing.html#id2922768">What is Imprints?</a></dt><dt><a href="printing.html#id2922810">Creating Printer Driver Packages</a></dt><dt><a href="printing.html#id2922828">The Imprints Server</a></dt><dt><a href="printing.html#id2922853">The Installation Client</a></dt></dl></dd><dt><a href="printing.html#id2923008">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="printing.html#id2923342">The addprinter command</a></dt><dt><a href="printing.html#id2923388">Migration of "Classical" printing to Samba</a></dt><dt><a href="printing.html#id2923561">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="printing.html#id2923575">Common Errors</a></dt><dd><dl><dt><a href="printing.html#id2923582">I give my root password but I don't get access</a></dt><dt><a href="printing.html#id2923615">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="CUPS-printing.html">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2923750">Introduction</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2923756">Features and Benefits</a></dt><dt><a href="CUPS-printing.html#id2923811">Overview</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2923880">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2923972">Linking of smbd with libcups.so</a></dt><dt><a href="CUPS-printing.html#id2924213">Simple smb.conf Settings for CUPS</a></dt><dt><a href="CUPS-printing.html#id2924395">More complex smb.conf Settings for +CUPS</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2924750">Advanced Configuration</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2924770">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="CUPS-printing.html#id2924825">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2924894">Driver Installation Methods on Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2924971">Explicitly enable "raw" printing for +application/octet-stream!</a></dt><dt><a href="CUPS-printing.html#id2925177">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2925317">Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download</a></dt><dd><dl><dt><a href="CUPS-printing.html#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="CUPS-printing.html#id2925497">Windows Drivers, GDI and EMF</a></dt><dt><a href="CUPS-printing.html#id2925650">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="CUPS-printing.html#id2925951">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="CUPS-printing.html#id2926092">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="CUPS-printing.html#id2926179">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="CUPS-printing.html#id2926285">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2926306">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2926501">MIME types and CUPS Filters</a></dt><dt><a href="CUPS-printing.html#id2926707">MIME type Conversion Rules</a></dt><dt><a href="CUPS-printing.html#id2926862">Filter Requirements</a></dt><dt><a href="CUPS-printing.html#id2927043">Prefilters</a></dt><dt><a href="CUPS-printing.html#id2927153">pstops</a></dt><dt><a href="CUPS-printing.html#id2927264">pstoraster</a></dt><dt><a href="CUPS-printing.html#id2927459">imagetops and imagetoraster</a></dt><dt><a href="CUPS-printing.html#id2927523">rasterto [printers specific]</a></dt><dt><a href="CUPS-printing.html#id2927675">CUPS Backends</a></dt><dt><a href="CUPS-printing.html#id2928022">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="CUPS-printing.html#id2928168">The Complete Picture</a></dt><dt><a href="CUPS-printing.html#id2928183">mime.convs</a></dt><dt><a href="CUPS-printing.html#id2928246">"Raw" printing</a></dt><dt><a href="CUPS-printing.html#id2928335">"application/octet-stream" printing</a></dt><dt><a href="CUPS-printing.html#id2928581">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="CUPS-printing.html#id2928848">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a></dt><dt><a href="CUPS-printing.html#id2929083">Examples for filtering Chains</a></dt><dt><a href="CUPS-printing.html#id2929420">Sources of CUPS drivers / PPDs</a></dt><dt><a href="CUPS-printing.html#id2929572">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2929667">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2929677">From Windows Clients to an NT Print Server</a></dt><dt><a href="CUPS-printing.html#id2929741">Driver Execution on the Client</a></dt><dt><a href="CUPS-printing.html#id2929818">Driver Execution on the Server</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2929936">Network Printing (Windows clients -- UNIX/Samba Print +Servers)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2929956">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="CUPS-printing.html#id2930169">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2930255">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2930344">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="CUPS-printing.html#id2930400">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2930476">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2930493">Printer Drivers running in "Kernel Mode" cause many +Problems</a></dt><dt><a href="CUPS-printing.html#id2930538">Workarounds impose Heavy Limitations</a></dt><dt><a href="CUPS-printing.html#id2930560">CUPS: a "Magical Stone"?</a></dt><dt><a href="CUPS-printing.html#id2930614">PostScript Drivers with no major problems -- even in Kernel +Mode</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2930637">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2930710">cupsaddsmb: the unknown Utility</a></dt><dt><a href="CUPS-printing.html#id2930811">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="CUPS-printing.html#id2931030">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="CUPS-printing.html#id2931268">Recognize the different Driver Files</a></dt><dt><a href="CUPS-printing.html#id2931460">Acquiring the Adobe Driver Files</a></dt><dt><a href="CUPS-printing.html#id2931493">ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"</a></dt><dt><a href="CUPS-printing.html#id2931562">Caveats to be considered</a></dt><dt><a href="CUPS-printing.html#id2931837">Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="CUPS-printing.html#id2932052">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="CUPS-printing.html#id2932180">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="CUPS-printing.html#id2932401">Understanding cupsaddsmb</a></dt><dt><a href="CUPS-printing.html#id2932551">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="CUPS-printing.html#id2932633">cupsaddsmb with a Samba PDC</a></dt><dt><a href="CUPS-printing.html#id2932714">cupsaddsmb Flowchart</a></dt><dt><a href="CUPS-printing.html#id2932789">Installing the PostScript Driver on a Client</a></dt><dt><a href="CUPS-printing.html#id2932953">Avoiding critical PostScript Driver Settings on the +Client</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2933086">Installing PostScript Driver Files manually (using +rpcclient)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2933288">A Check of the rpcclient man Page</a></dt><dt><a href="CUPS-printing.html#id2933403">Understanding the rpcclient man page</a></dt><dt><a href="CUPS-printing.html#id2933506">Producing an Example by querying a Windows Box</a></dt><dt><a href="CUPS-printing.html#id2933674">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="CUPS-printing.html#id2933889">Manual Driver Installation in 15 Steps</a></dt><dt><a href="CUPS-printing.html#id2934958">Troubleshooting revisited</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2935118">The printing *.tdb Files</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2935364">Trivial DataBase Files</a></dt><dt><a href="CUPS-printing.html#id2935456">Binary Format</a></dt><dt><a href="CUPS-printing.html#id2935520">Losing *.tdb Files</a></dt><dt><a href="CUPS-printing.html#id2935579">Using tdbbackup</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2935716">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2935871">foomatic-rip and Foomatic explained</a></dt><dt><a href="CUPS-printing.html#id2936640">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2937141">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2937193">Setting up Quotas</a></dt><dt><a href="CUPS-printing.html#id2937258">Correct and incorrect Accounting</a></dt><dt><a href="CUPS-printing.html#id2937303">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2937398">The page_log File Syntax</a></dt><dt><a href="CUPS-printing.html#id2937516">Possible Shortcomings</a></dt><dt><a href="CUPS-printing.html#id2937592">Future Developments</a></dt><dt><a href="CUPS-printing.html#id2937648">Other Accounting Tools</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2937662">Additional Material</a></dt><dt><a href="CUPS-printing.html#id2937912">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2937974">CUPS Configuration Settings explained</a></dt><dt><a href="CUPS-printing.html#id2938069">Pre-conditions</a></dt><dt><a href="CUPS-printing.html#id2938226">Manual Configuration</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2938284">In Case of Trouble.....</a></dt><dt><a href="CUPS-printing.html#id2938356">Printing from CUPS to Windows attached +Printers</a></dt><dt><a href="CUPS-printing.html#id2938656">More CUPS filtering Chains</a></dt><dt><a href="CUPS-printing.html#id2938758">Common Errors</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2938765">Win9x client can't install driver</a></dt><dt><a href="CUPS-printing.html#id2938787">"cupsaddsmb" keeps asking for root password in + neverending loop</a></dt><dt><a href="CUPS-printing.html#id2938835">"cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present</a></dt><dt><a href="CUPS-printing.html#id2938893">Client can't connect to Samba printer</a></dt><dt><a href="CUPS-printing.html#id2938921">Can't reconnect to Samba under new account + from Win2K/XP</a></dt><dt><a href="CUPS-printing.html#id2939149">Avoid being connected to the Samba server as the + "wrong" user</a></dt><dt><a href="CUPS-printing.html#id2939202">Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems</a></dt><dt><a href="CUPS-printing.html#id2939219">Can't use "cupsaddsmb" on Samba server which is + a PDC</a></dt><dt><a href="CUPS-printing.html#id2939249">Deleted Win2K printer driver is still shown</a></dt><dt><a href="CUPS-printing.html#id2939258">Win2K/XP "Local Security + Policies"</a></dt><dt><a href="CUPS-printing.html#id2939297">WinXP clients: "Administrator can not install + printers for all local users"</a></dt><dt><a href="CUPS-printing.html#id2939331">"Print Change Notify" functions on + NT-clients</a></dt><dt><a href="CUPS-printing.html#id2939354">WinXP-SP1</a></dt><dt><a href="CUPS-printing.html#id2939398">Print options for all users can't be set on Win2K/XP</a></dt><dt><a href="CUPS-printing.html#id2939689">Most common blunders in driver + settings on Windows clients</a></dt><dt><a href="CUPS-printing.html#id2939734">cupsaddsmb does not work + with newly installed printer</a></dt><dt><a href="CUPS-printing.html#id2939796">Permissions on +/var/spool/samba/ get reset after each +reboot</a></dt><dt><a href="CUPS-printing.html#id2939905">Printer named "lp" +intermittently swallows jobs and spits out completely different +ones</a></dt><dt><a href="CUPS-printing.html#id2939953">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2940008">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="VFS.html">Stackable VFS modules</a></dt><dd><dl><dt><a href="VFS.html#id2940177">Features and Benefits</a></dt><dt><a href="VFS.html#id2940195">Discussion</a></dt><dt><a href="VFS.html#id2940424">Included modules</a></dt><dd><dl><dt><a href="VFS.html#id2940432">audit</a></dt><dt><a href="VFS.html#id2940474">extd_audit</a></dt><dt><a href="VFS.html#id2940604">fake_perms</a></dt><dt><a href="VFS.html#id2940622">recycle</a></dt><dt><a href="VFS.html#id2940798">netatalk</a></dt></dl></dd><dt><a href="VFS.html#id2940843">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="VFS.html#id2940865">DatabaseFS</a></dt><dt><a href="VFS.html#id2940920">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="winbind.html">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="winbind.html#id2941150">Features and Benefits</a></dt><dt><a href="winbind.html#id2941246">Introduction</a></dt><dt><a href="winbind.html#id2941324">What Winbind Provides</a></dt><dd><dl><dt><a href="winbind.html#id2941400">Target Uses</a></dt></dl></dd><dt><a href="winbind.html#id2941431">How Winbind Works</a></dt><dd><dl><dt><a href="winbind.html#id2941460">Microsoft Remote Procedure Calls</a></dt><dt><a href="winbind.html#id2941493">Microsoft Active Directory Services</a></dt><dt><a href="winbind.html#id2941516">Name Service Switch</a></dt><dt><a href="winbind.html#id2941652">Pluggable Authentication Modules</a></dt><dt><a href="winbind.html#id2941724">User and Group ID Allocation</a></dt><dt><a href="winbind.html#id2941757">Result Caching</a></dt></dl></dd><dt><a href="winbind.html#id2941785">Installation and Configuration</a></dt><dd><dl><dt><a href="winbind.html#id2941792">Introduction</a></dt><dt><a href="winbind.html#id2941859">Requirements</a></dt><dt><a href="winbind.html#id2941953">Testing Things Out</a></dt></dl></dd><dt><a href="winbind.html#id2943561">Conclusion</a></dt><dt><a href="winbind.html#id2943580">Common Errors</a></dt><dd><dl><dt><a href="winbind.html#id2943633">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="AdvancedNetworkManagement.html">Advanced Network Management</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2943742">Features and Benefits</a></dt><dt><a href="AdvancedNetworkManagement.html#id2943772">Remote Server Administration</a></dt><dt><a href="AdvancedNetworkManagement.html#id2943871">Remote Desktop Management</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2943888">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="AdvancedNetworkManagement.html#id2944129">Network Logon Script Magic</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2944368">Adding printers without user intervention</a></dt></dl></dd><dt><a href="AdvancedNetworkManagement.html#id2944401">Common Errors</a></dt></dl></dd><dt>23. <a href="PolicyMgmt.html">System and Account Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2944479">Features and Benefits</a></dt><dt><a href="PolicyMgmt.html#id2944538">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2944652">Windows 9x/Me Policies</a></dt><dt><a href="PolicyMgmt.html#id2944748">Windows NT4 Style Policy Files</a></dt><dt><a href="PolicyMgmt.html#id2944880">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="PolicyMgmt.html#id2945132">Managing Account/User Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2945238">Samba Editreg Toolset</a></dt><dt><a href="PolicyMgmt.html#id2945277">Windows NT4/200x</a></dt><dt><a href="PolicyMgmt.html#id2945301">Samba PDC</a></dt></dl></dd><dt><a href="PolicyMgmt.html#id2945346">System Startup and Logon Processing Overview</a></dt><dt><a href="PolicyMgmt.html#id2945496">Common Errors</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2945511">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="ProfileMgmt.html">Desktop Profile Management</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2945611">Features and Benefits</a></dt><dt><a href="ProfileMgmt.html#id2945646">Roaming Profiles</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2945686">Samba Configuration for Profile Handling</a></dt><dt><a href="ProfileMgmt.html#id2946178">Windows Client Profile Configuration Information</a></dt><dt><a href="ProfileMgmt.html#id2947427">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="ProfileMgmt.html#id2947512">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2947770">Mandatory profiles</a></dt><dt><a href="ProfileMgmt.html#id2947828">Creating/Managing Group Profiles</a></dt><dt><a href="ProfileMgmt.html#id2947873">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2947893">MS Windows 9x/Me</a></dt><dt><a href="ProfileMgmt.html#id2948045">MS Windows NT4 Workstation</a></dt><dt><a href="ProfileMgmt.html#id2948600">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2949100">Common Errors</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2949130">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="ProfileMgmt.html#id2949201">Can NOT use Roaming Profiles</a></dt><dt><a href="ProfileMgmt.html#id2949414">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="pam.html">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="pam.html#id2949695">Features and Benefits</a></dt><dt><a href="pam.html#id2949942">Technical Discussion</a></dt><dd><dl><dt><a href="pam.html#id2949960">PAM Configuration Syntax</a></dt><dt><a href="pam.html#id2950624">Example System Configurations</a></dt><dt><a href="pam.html#id2950929">smb.conf PAM Configuration</a></dt><dt><a href="pam.html#id2951007">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="pam.html#id2951091">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="pam.html#id2951474">Common Errors</a></dt><dd><dl><dt><a href="pam.html#id2951487">pam_winbind problem</a></dt><dt><a href="pam.html#id2951576">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="integrate-ms-networks.html">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2951812">Features and Benefits</a></dt><dt><a href="integrate-ms-networks.html#id2951838">Background Information</a></dt><dt><a href="integrate-ms-networks.html#id2951903">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2951960">/etc/hosts</a></dt><dt><a href="integrate-ms-networks.html#id2952110">/etc/resolv.conf</a></dt><dt><a href="integrate-ms-networks.html#id2952153">/etc/host.conf</a></dt><dt><a href="integrate-ms-networks.html#id2952204">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2952319">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2952629">The NetBIOS Name Cache</a></dt><dt><a href="integrate-ms-networks.html#id2952692">The LMHOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2952854">HOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2952886">DNS Lookup</a></dt><dt><a href="integrate-ms-networks.html#id2952918">WINS Lookup</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2953036">Common Errors</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2953052">Pinging works only in one way</a></dt><dt><a href="integrate-ms-networks.html#id2953086">Very Slow Network Connections</a></dt><dt><a href="integrate-ms-networks.html#id2953137">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="unicode.html">Unicode/Charsets</a></dt><dd><dl><dt><a href="unicode.html#id2953342">Features and Benefits</a></dt><dt><a href="unicode.html#id2953385">What are charsets and unicode?</a></dt><dt><a href="unicode.html#id2953454">Samba and charsets</a></dt><dt><a href="unicode.html#id2953583">Conversion from old names</a></dt><dt><a href="unicode.html#id2953612">Japanese charsets</a></dt><dt><a href="unicode.html#id2953751">Common errors</a></dt><dd><dl><dt><a href="unicode.html#id2953758">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="Backup.html">Samba Backup Techniques</a></dt><dd><dl><dt><a href="Backup.html#id2953871">Note</a></dt><dt><a href="Backup.html#id2953885">Features and Benefits</a></dt></dl></dd><dt>29. <a href="SambaHA.html">High Availability Options</a></dt><dd><dl><dt><a href="SambaHA.html#id2953955">Note</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ClientConfig.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-doc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 9. MS Windows Network Configuration Guide </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 10. Samba / MS Windows Network Browsing Guide</td></tr></table></div></body></html> diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html new file mode 100644 index 0000000000..8edbdb26ca --- /dev/null +++ b/docs/htmldocs/pam.html @@ -0,0 +1,565 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 25. PAM based Distributed Authentication</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="ProfileMgmt.html" title="Chapter 24. Desktop Profile Management"><link rel="next" href="integrate-ms-networks.html" title="Chapter 26. Integrating MS Windows networks with Samba"></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 25. PAM based Distributed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>></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="pam.html#id2949695">Features and Benefits</a></dt><dt><a href="pam.html#id2949942">Technical Discussion</a></dt><dd><dl><dt><a href="pam.html#id2949960">PAM Configuration Syntax</a></dt><dt><a href="pam.html#id2950624">Example System Configurations</a></dt><dt><a href="pam.html#id2950929">smb.conf PAM Configuration</a></dt><dt><a href="pam.html#id2951007">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="pam.html#id2951091">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="pam.html#id2951474">Common Errors</a></dt><dd><dl><dt><a href="pam.html#id2951487">pam_winbind problem</a></dt><dt><a href="pam.html#id2951576">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 +based domain environment. It will also help you to configure PAM based local host access +controls that are appropriate to your Samba configuration. +</p><p> +In addition to knowing how to configure winbind into PAM, you will learn generic PAM management +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.html" 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="id2949695"></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 +to use an alternative to the system password database (<tt class="filename">/etc/passwd</tt>) +would require the provision of alternatives for all programs that provide security services. +Such a choice would involve provision of alternatives to such programs as: <b class="command">login</b>, +<b class="command">passwd</b>, <b class="command">chown</b>, etc. +</p><p> +PAM provides a mechanism that disconnects these security programs from the underlying +authentication/authorization infrastructure. PAM is configured either through one file +<tt class="filename">/etc/pam.conf</tt> (Solaris), or by editing individual files that are +located in <tt class="filename">/etc/pam.d</tt>. +</p><p> +On PAM enabled UNIX/Linux systems it is an easy matter to configure the system to use any +authentication backend, so long as the appropriate dynamically loadable library modules +are available for it. The backend may be local to the system, or may be centralised on a +remote server. +</p><p> +PAM support modules are available for: +</p><div class="variablelist"><dl><dt><span class="term"><tt class="filename">/etc/passwd</tt>:</span></dt><dd><p> + There are several PAM modules that interact with this standard UNIX user + database. The most common are called: pam_unix.so, pam_unix2.so, pam_pwdb.so + and pam_userdb.so. + </p></dd><dt><span class="term">Kerberos:</span></dt><dd><p> + The pam_krb5.so module allows the use of any Kerberos compliant server. + This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially + Microsoft Active Directory (if enabled). + </p></dd><dt><span class="term">LDAP:</span></dt><dd><p> + The pam_ldap.so module allows the use of any LDAP v2 or v3 compatible backend + server. Commonly used LDAP backend servers include: OpenLDAP v2.0 and v2.1, + Sun ONE iDentity server, Novell eDirectory server, Microsoft Active Directory. + </p></dd><dt><span class="term">NetWare Bindery:</span></dt><dd><p> + The pam_ncp_auth.so module allows authentication off any bindery enabled + NetWare Core Protocol based server. + </p></dd><dt><span class="term">SMB Password:</span></dt><dd><p> + This module, called pam_smbpass.so, will allow user authentication off + the passdb backend that is configured in the Samba <tt class="filename">smb.conf</tt> file. + </p></dd><dt><span class="term">SMB Server:</span></dt><dd><p> + The pam_smb_auth.so module is the original MS Windows networking authentication + tool. This module has been somewhat outdated by the Winbind module. + </p></dd><dt><span class="term">Winbind:</span></dt><dd><p> + The pam_winbind.so module allows Samba to obtain authentication from any + MS Windows Domain Controller. It can just as easily be used to authenticate + users for access to any PAM enabled application. + </p></dd><dt><span class="term">RADIUS:</span></dt><dd><p> + There is a PAM RADIUS (Remote Access Dial-In User Service) authentication + module. In most cases the administrator will need to locate the source code + for this tool and compile and install it themselves. RADIUS protocols are + used by many routers and terminal servers. + </p></dd></dl></div><p> +Of the above, Samba provides the pam_smbpasswd.so and the pam_winbind.so modules alone. +</p><p> +Once configured, these permit a remarkable level of flexibility in the location and use +of distributed samba domain controllers that can provide wide are network bandwidth +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="id2949942"></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="id2949960"></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. +The case-sensitivity of the arguments to any given module is defined for each module in turn. +</p><p> +In addition to the lines described below, there are two special characters provided for the convenience +of the system administrator: comments are preceded by a `#' and extend to the next end-of-line; also, +module specification lines may be extended with a `\' escaped newline. +</p><p> +If the PAM authentication module (loadable link library file) is located in the +default location then it is not necessary to specify the path. In the case of +Linux, the default location is <tt class="filename">/lib/security</tt>. If the module +is located outside the default then the path must be specified as: +</p><p> +</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="id2950018"></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> +</p><p> +A general configuration line of the /etc/pam.conf file has the following form: +</p><p> +</p><pre class="programlisting"> +service-name module-type control-flag module-path args +</pre><p> +</p><p> +Below, we explain the meaning of each of these tokens. The second (and more recently adopted) +way of configuring Linux-PAM is via the contents of the <tt class="filename">/etc/pam.d/</tt> directory. +Once we have explained the meaning of the above tokens, we will describe this method. +</p><div class="variablelist"><dl><dt><span class="term">service-name:</span></dt><dd><p> + The name of the service associated with this entry. Frequently the service name is the conventional + name of the given application. For example, `ftpd', `rlogind' and `su', etc. . + </p><p> + There is a special service-name, reserved for defining a default authentication mechanism. It has + the name `OTHER' and may be specified in either lower or upper case characters. Note, when there + is a module specified for a named service, the `OTHER' entries are ignored. + </p></dd><dt><span class="term">module-type:</span></dt><dd><p> + One of (currently) four types of module. The four types are as follows: + </p><div class="itemizedlist"><ul type="disc"><li><p> + <span class="emphasis"><em>auth:</em></span> this module type provides two aspects of authenticating the user. + Firstly, it establishes that the user is who they claim to be, by instructing the application + to prompt the user for a password or other means of identification. Secondly, the module can + grant group membership (independently of the <tt class="filename">/etc/groups</tt> file discussed + above) or other privileges through its credential granting properties. + </p></li><li><p> + <span class="emphasis"><em>account:</em></span> this module performs non-authentication based account management. + It is typically used to restrict/permit access to a service based on the time of day, currently + available system resources (maximum number of users) or perhaps the location of the applicant + user `root' login only on the console. + </p></li><li><p> + <span class="emphasis"><em>session:</em></span> primarily, this module is associated with doing things that need + to be done for the user before/after they can be given service. Such things include the logging + of information concerning the opening/closing of some data exchange with a user, mounting + directories, etc. + </p></li><li><p> + <span class="emphasis"><em>password:</em></span> this last module type is required for updating the authentication + token associated with the user. Typically, there is one module for each `challenge/response' + based authentication (auth) module-type. + </p></li></ul></div></dd><dt><span class="term">control-flag:</span></dt><dd><p> + The control-flag is used to indicate how the PAM library will react to the success or failure of the + module it is associated with. Since modules can be stacked (modules of the same type execute in series, + one after another), the control-flags determine the relative importance of each module. The application + is not made aware of the individual success or failure of modules listed in the + <tt class="filename">/etc/pam.conf</tt> file. Instead, it receives a summary success or fail response from + the Linux-PAM library. The order of execution of these modules is that of the entries in the + <tt class="filename">/etc/pam.conf</tt> file; earlier entries are executed before later ones. + As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes. + </p><p> + The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the + severity of concern associated with the success or failure of a specific module. There are four such + <span class="emphasis"><em>keywords: required, requisite, sufficient and optional</em></span>. + </p><p> + The Linux-PAM library interprets these keywords in the following manner: + </p><div class="itemizedlist"><ul type="disc"><li><p> + <span class="emphasis"><em>required:</em></span> this indicates that the success of the module is required for the + module-type facility to succeed. Failure of this module will not be apparent to the user until all + of the remaining modules (of the same module-type) have been executed. + </p></li><li><p> + <span class="emphasis"><em>requisite:</em></span> like required, however, in the case that such a module returns a + failure, control is directly returned to the application. The return value is that associated with + the first required or requisite module to fail. Note, this flag can be used to protect against the + possibility of a user getting the opportunity to enter a password over an unsafe medium. It is + conceivable that such behavior might inform an attacker of valid accounts on a system. This + possibility should be weighed against the not insignificant concerns of exposing a sensitive + password in a hostile environment. + </p></li><li><p> + <span class="emphasis"><em>sufficient:</em></span> the success of this module is deemed `sufficient' to satisfy + the Linux-PAM library that this module-type has succeeded in its purpose. In the event that no + previous required module has failed, no more `stacked' modules of this type are invoked. (Note, + in this case subsequent required modules are not invoked.). A failure of this module is not deemed + as fatal to satisfying the application that this module-type has succeeded. + </p></li><li><p> + <span class="emphasis"><em>optional:</em></span> as its name suggests, this control-flag marks the module as not + being critical to the success or failure of the user's application for service. In general, + Linux-PAM ignores such a module when determining if the module stack will succeed or fail. + However, in the absence of any definite successes or failures of previous or subsequent stacked + modules this module will determine the nature of the response to the application. One example of + this latter case, is when the other modules return something like PAM_IGNORE. + </p></li></ul></div><p> + The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control + over how the user is authenticated. This form of the control flag is delimited with square brackets and + consists of a series of value=action tokens: + </p><pre class="programlisting"> +[value1=action1 value2=action2 ...] +</pre><p> + Here, value1 is one of the following return values: success; open_err; symbol_err; service_err; + system_err; buf_err; perm_denied; auth_err; cred_insufficient; authinfo_unavail; user_unknown; maxtries; + new_authtok_reqd; acct_expired; session_err; cred_unavail; cred_expired; cred_err; no_module_data; conv_err; + authtok_err; authtok_recover_err; authtok_lock_busy; authtok_disable_aging; try_again; ignore; abort; + authtok_expired; module_unknown; bad_item; and default. The last of these (default) can be used to set + the action for those return values that are not explicitly defined. + </p><p> + The action1 can be a positive integer or one of the following tokens: ignore; ok; done; bad; die; and reset. + A positive integer, J, when specified as the action, can be used to indicate that the next J modules of the + current module-type will be skipped. In this way, the administrator can develop a moderately sophisticated + stack of modules with a number of different paths of execution. Which path is taken can be determined by the + reactions of individual modules. + </p><div class="itemizedlist"><ul type="disc"><li><p> + <span class="emphasis"><em>ignore:</em></span> when used with a stack of modules, the module's return status will not + contribute to the return code the application obtains. + </p></li><li><p> + <span class="emphasis"><em>bad:</em></span> this action indicates that the return code should be thought of as indicative + of the module failing. If this module is the first in the stack to fail, its status value will be used + for that of the whole stack. + </p></li><li><p> + <span class="emphasis"><em>die:</em></span> equivalent to bad with the side effect of terminating the module stack and + PAM immediately returning to the application. + </p></li><li><p> + <span class="emphasis"><em>ok:</em></span> this tells PAM that the administrator thinks this return code should + contribute directly to the return code of the full stack of modules. In other words, if the former + state of the stack would lead to a return of PAM_SUCCESS, the module's return code will override + this value. Note, if the former state of the stack holds some value that is indicative of a modules + failure, this 'ok' value will not be used to override that value. + </p></li><li><p> + <span class="emphasis"><em>done:</em></span> equivalent to ok with the side effect of terminating the module stack and + PAM immediately returning to the application. + </p></li><li><p> + <span class="emphasis"><em>reset:</em></span> clear all memory of the state of the module stack and start again with + the next stacked module. + </p></li></ul></div><p> + Each of the four keywords: required; requisite; sufficient; and optional, have an equivalent expression in + terms of the [...] syntax. They are as follows: + </p><p> + </p><div class="itemizedlist"><ul type="disc"><li><p> + required is equivalent to [success=ok new_authtok_reqd=ok ignore=ignore default=bad] + </p></li><li><p> + requisite is equivalent to [success=ok new_authtok_reqd=ok ignore=ignore default=die] + </p></li><li><p> + sufficient is equivalent to [success=done new_authtok_reqd=done default=ignore] + </p></li><li><p> + optional is equivalent to [success=ok new_authtok_reqd=ok default=ignore] + </p></li></ul></div><p> + </p><p> + Just to get a feel for the power of this new syntax, here is a taste of what you can do with it. With Linux-PAM-0.63, + the notion of client plug-in agents was introduced. This is something that makes it possible for PAM to support + machine-machine authentication using the transport protocol inherent to the client/server application. With the + <span class="emphasis"><em>[ ... value=action ... ]</em></span> control syntax, it is possible for an application to be configured + to support binary prompts with compliant clients, but to gracefully fall over into an alternative authentication + mode for older, legacy, applications. + </p></dd><dt><span class="term">module-path:</span></dt><dd><p> + The path-name of the dynamically loadable object file; the pluggable module itself. If the first character of the + module path is `/', it is assumed to be a complete path. If this is not the case, the given module path is appended + to the default module path: <tt class="filename">/lib/security</tt> (but see the notes above). + </p><p> + The args are a list of tokens that are passed to the module when it is invoked. Much like arguments to a typical + Linux shell command. Generally, valid arguments are optional and are specific to any given module. Invalid arguments + are ignored by a module, however, when encountering an invalid argument, the module is required to write an error + to syslog(3). For a list of generic options see the next section. + </p><p> + Note, if you wish to include spaces in an argument, you should surround that argument with square brackets. For example: + </p><pre class="programlisting"> +squid auth required pam_mysql.so user=passwd_query passwd=mada \ + db=eminence [query=select user_name from internet_service where \ + user_name='%u' and password=PASSWORD('%p') and \ + service='web_proxy'] +</pre><p> + Note, when using this convention, you can include `[' characters inside the string, and if you wish to include a `]' + character inside the string that will survive the argument parsing, you should use `\['. In other words: + </p><pre class="programlisting"> +[..[..\]..] --> ..[..].. +</pre><p> + 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="id2950624"></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="id2950655"></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 +# +auth required pam_securetty.so +auth required pam_nologin.so +# auth required pam_dialup.so +# auth optional pam_mail.so +auth required pam_pwdb.so shadow md5 +# account requisite pam_time.so +account required pam_pwdb.so +session required pam_pwdb.so +# session optional pam_lastlog.so +# password required pam_cracklib.so retry=3 +password required pam_pwdb.so shadow md5 +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2950683"></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"> +pam_access.so pam_ftp.so pam_limits.so +pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so +pam_cracklib.so pam_group.so pam_listfile.so +pam_nologin.so pam_rootok.so pam_tally.so +pam_deny.so pam_issue.so pam_mail.so +pam_permit.so pam_securetty.so pam_time.so +pam_dialup.so pam_lastlog.so pam_mkhomedir.so +pam_pwdb.so pam_shells.so pam_unix.so +pam_env.so pam_ldap.so pam_motd.so +pam_radius.so pam_smbpass.so pam_unix_acct.so +pam_wheel.so pam_unix_auth.so pam_unix_passwd.so +pam_userdb.so pam_warn.so pam_unix_session.so +</pre><p> +The following example for the login program replaces the use of +the <tt class="filename">pam_pwdb.so</tt> module which uses the system +password database (<tt class="filename">/etc/passwd</tt>, +<tt class="filename">/etc/shadow</tt>, <tt class="filename">/etc/group</tt>) with +the module <tt class="filename">pam_smbpass.so</tt> which uses the Samba +database which contains the Microsoft MD4 encrypted password +hashes. This database is stored in either +<tt class="filename">/usr/local/samba/private/smbpasswd</tt>, +<tt class="filename">/etc/samba/smbpasswd</tt>, or in +<tt class="filename">/etc/samba.d/smbpasswd</tt>, depending on the +Samba implementation for your UNIX/Linux system. The +<tt class="filename">pam_smbpass.so</tt> module is provided by +Samba version 2.2.1 or later. It can be compiled by specifying the +<tt class="option">--with-pam_smbpass</tt> options when running Samba's +<b class="command">configure</b> script. For more information +on the <tt class="filename">pam_smbpass</tt> module, see the documentation +in the <tt class="filename">source/pam_smbpass</tt> directory of the Samba +source distribution. +</p><pre class="programlisting"> +#%PAM-1.0 +# The PAM configuration file for the `login' service +# +auth required pam_smbpass.so nodelay +account required pam_smbpass.so nodelay +session required pam_smbpass.so nodelay +password required pam_smbpass.so nodelay +</pre><p> +The following is the PAM configuration file for a particular +Linux system. The default condition uses <tt class="filename">pam_pwdb.so</tt>. +</p><pre class="programlisting"> +#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth required pam_pwdb.so nullok nodelay shadow audit +account required pam_pwdb.so audit nodelay +session required pam_pwdb.so nodelay +password required pam_pwdb.so shadow md5 +</pre><p> +In the following example the decision has been made to use the +smbpasswd database even for basic samba authentication. Such a +decision could also be made for the passwd program and would +thus allow the smbpasswd passwords to be changed using the passwd +program. +</p><pre class="programlisting"> +#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth required pam_smbpass.so nodelay +account required pam_pwdb.so audit nodelay +session required pam_pwdb.so nodelay +password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf +</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>PAM allows stacking of authentication mechanisms. It is +also possible to pass information obtained within one PAM module through +to the next module in the PAM stack. Please refer to the documentation for +your particular system implementation for details regarding the specific +capabilities of PAM in this environment. Some Linux implementations also +provide the <tt class="filename">pam_stack.so</tt> module that allows all +authentication to be configured in a single central file. The +<tt class="filename">pam_stack.so</tt> method has some very devoted followers +on the basis that it allows for easier administration. As with all issues in +life though, every decision makes trade-offs, so you may want examine the +PAM documentation for further helpful information. +</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950929"></a>smb.conf PAM Configuration</h3></div></div><div></div></div><p> + There is an option in smb.conf called <a class="indexterm" name="id2950938"></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. +<tt class="option">--with-pam</tt>), this parameter will +control whether or not Samba should obey PAM's account +and session management directives. The default behavior +is to use PAM for clear text authentication only and to +ignore any account or session management. Note that Samba always +ignores PAM for authentication in the case of +<a class="indexterm" name="id2950969"></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="id2950990"></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="id2951007"></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 +as <tt class="filename">/etc/passwd</tt>. +</p><p> +Users and groups on a Windows NT server are assigned a relative id (rid) which is unique for +the domain when the user or group is created. To convert the Windows NT user or group into +a unix user or group, a mapping between rids and unix user and group ids is required. This +is one of the jobs that winbind performs. +</p><p> +As winbind users and groups are resolved from a server, user and group ids are allocated +from a specified range. This is done on a first come, first served basis, although all +existing users and groups will be mapped as soon as a client performs a user or group +enumeration command. The allocated unix ids are stored in a database file under the Samba +lock directory and will be remembered. +</p><p> +The astute administrator will realize from this that the combination of <tt class="filename">pam_smbpass.so</tt>, +<b class="command">winbindd</b>, and a distributed passdb backend, such as ldap, will allow the establishment of a +centrally managed, distributed user/password database that can also be used by all PAM (eg: Linux) aware +programs and applications. This arrangement can have particularly potent advantages compared with the use of +Microsoft Active Directory Service (ADS) in so far as reduction of wide area network authentication traffic. +</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> +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="id2951091"></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 +under some Unices, such as Solaris, HPUX and Linux, that provides a +generic interface to authentication mechanisms. +</p><p> +This module authenticates a local smbpasswd user database. If you require +support for authenticating against a remote SMB server, or if you're +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="id2951123"></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 + pam_pwdb module upon which pam_smbpass was originally based</p></li><li><p><a href="mailto:lkcl@switchboard.net" target="_top">Luke Leighton</a> for being receptive to the idea, + and for the occasional good-natured complaint about the project's status + that keep me working on it :)</p></li></ul></div><p>. +</p><p> +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="id2951339"></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 +application (such as ssh). +</p><pre class="programlisting"> +#%PAM-1.0 +# password-sync +# +auth requisite pam_nologin.so +auth required pam_unix.so +account required pam_unix.so +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="id2951372"></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: +password migration takes place when users ftp in, login using ssh, pop +their mail, etc. +</p><pre class="programlisting"> +#%PAM-1.0 +# password-migration +# +auth requisite pam_nologin.so +# pam_smbpass is called IF pam_unix succeeds. +auth requisite pam_unix.so +auth optional pam_smbpass.so migrate +account required pam_unix.so +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="id2951407"></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. +</p><pre class="programlisting"> +#%PAM-1.0 +# password-mature +# +auth requisite pam_nologin.so +auth required pam_unix.so +account required pam_unix.so +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="id2951440"></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. +</p><pre class="programlisting"> +#%PAM-1.0 +# kdc-pdc +# +auth requisite pam_nologin.so +auth requisite pam_krb5.so +auth optional pam_smbpass.so migrate +account required pam_krb5.so +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="id2951474"></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="id2951487"></a>pam_winbind problem</h3></div></div><div></div></div><p> + “<span class="quote"> + I have the following PAM configuration: + </span>” + </p><p> +</p><pre class="programlisting"> +auth required /lib/security/pam_securetty.so +auth sufficient /lib/security/pam_winbind.so +auth sufficient /lib/security/pam_unix.so use_first_pass nullok +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_nologin.so +account required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_winbind.so +password required /lib/security/pam_stack.so service=system-auth +</pre><p> + </p><p> + “<span class="quote"> + When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie". + I've tried with user "scienceu+pitie" also. +</span>” + </p><p> + The problem may lie with your inclusion of <i class="parameter"><tt>pam_stack.so + service=system-auth</tt></i>. That file often contains a lot of stuff that may + duplicate what you're already doing. Try commenting out the pam_stack lines + for auth and account and see if things work. If they do, look at + <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="id2951576"></a>Winbind is not resolving users and groups</h3></div></div><div></div></div><p> + “<span class="quote"> + My smb.conf file is correctly configured. I have specified + <a class="indexterm" name="id2951590"></a><i class="parameter"><tt>idmap uid</tt></i> = 12000, + and <a class="indexterm" name="id2951604"></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>” + </p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>wbinfo -u</tt></b> +MIDEARTH+maryo +MIDEARTH+jackb +MIDEARTH+ameds +... +MIDEARTH+root + +<tt class="prompt">root# </tt><b class="userinput"><tt>wbinfo -g</tt></b> +MIDEARTH+Domain Users +MIDEARTH+Domain Admins +MIDEARTH+Domain Guests +... +MIDEARTH+Accounts + +<tt class="prompt">root# </tt><b class="userinput"><tt>getent passwd</tt></b> +root:x:0:0:root:/root:/bin/bash +bin:x:1:1:bin:/bin:/bin/bash +... +maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false +</pre><p> + “<span class="quote"> + But the following command just fails: +</span>” +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>chown 'maryo' a_file</tt></b> +chown: `maryo': invalid user +</pre><p> +“<span class="quote"> +This is driving me nuts! What can be wrong? +</span>” + </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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 24. Desktop Profile Management </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 26. Integrating MS Windows networks with Samba</td></tr></table></div></body></html> diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html new file mode 100644 index 0000000000..4d5432fd70 --- /dev/null +++ b/docs/htmldocs/passdb.html @@ -0,0 +1,785 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="NetworkBrowsing.html" title="Chapter 10. Samba / MS Windows Network Browsing Guide"><link rel="next" href="groupmapping.html" title="Chapter 12. Mapping MS Windows and UNIX Groups"></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 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a href="mailto:jra@samba.org">jra@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></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="passdb.html#id2898446">Features and Benefits</a></dt><dd><dl><dt><a href="passdb.html#id2898460">Backwards Compatibility Backends</a></dt><dt><a href="passdb.html#id2898561">New Backends</a></dt></dl></dd><dt><a href="passdb.html#id2898749">Technical Information</a></dt><dd><dl><dt><a href="passdb.html#id2898874">Important Notes About Security</a></dt><dt><a href="passdb.html#id2899165">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="passdb.html#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="passdb.html#id2899351">The smbpasswd Command</a></dt><dt><a href="passdb.html#id2899622">The pdbedit Command</a></dt></dl></dd><dt><a href="passdb.html#id2899860">Password Backends</a></dt><dd><dl><dt><a href="passdb.html#id2899902">Plain Text</a></dt><dt><a href="passdb.html#id2899942">smbpasswd - Encrypted Password Database</a></dt><dt><a href="passdb.html#id2900055">tdbsam</a></dt><dt><a href="passdb.html#id2900089">ldapsam</a></dt><dt><a href="passdb.html#id2901940">MySQL</a></dt><dt><a href="passdb.html#XMLpassdb">XML</a></dt></dl></dd><dt><a href="passdb.html#id2902790">Common Errors</a></dt><dd><dl><dt><a href="passdb.html#id2902796">Users can not logon</a></dt><dt><a href="passdb.html#id2902841">Users being added to wrong backend database</a></dt><dt><a href="passdb.html#id2902952">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. +This chapter describes the new functionality and how to get the most out of it. +</p><p> +In the course of development of Samba-3, a number of requests were received to provide the +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="id2898413"></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 +deliver this functionality until a better method of recognising NT Group SIDs from NT User +SIDs could be found. This feature may thus return during the life cycle for the Samba-3 series. +</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="id2898446"></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="id2898460"></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 + Samba-2.2.x, and the protocol limitations imposed by MS Windows clients + apply likewise. + </p></dd><dt><span class="term">smbpasswd:</span></dt><dd><p> + This option allows continues use of the <tt class="filename">smbpasswd</tt> + file that maintains a plain ASCII (text) layout that includes the MS Windows + LanMan and NT encrypted passwords as well as a field that stores some + account information. This form of password backend does NOT store any of + the MS Windows NT/200x SAM (Security Account Manager) information needed to + provide the extended controls that are needed for more comprehensive + interoperation with MS Windows NT4 / 200x servers. + </p><p> + This backend should be used only for backwards compatibility with older + versions of Samba. It may be deprecated in future releases. + </p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility):</span></dt><dd><p> + There is a password backend option that allows continued operation with + a existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension. + 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="id2898561"></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 + backend is NOT suitable for multiple domain controller (ie: PDC + one + or more BDC) installations. + </p><p> + The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em> + smbpasswd</em></span> information PLUS the extended MS Windows NT / 200x + SAM information into a binary format TDB (trivial database) file. + The inclusion of the extended information makes it possible for Samba-3 + to implement the same account and system access controls that are possible + with MS Windows NT4 and MS Windows 200x based systems. + </p><p> + The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct + response to user requests to allow simple site operation without the overhead + of the complexities of running OpenLDAP. It is recommended to use this only + for sites that have fewer than 250 users. For larger sites or implementations + the use of OpenLDAP or of Active Directory integration is strongly recommended. + </p></dd><dt><span class="term">ldapsam:</span></dt><dd><p> + This provides a rich directory backend for distributed account installation. + </p><p> + Samba-3 has a new and extended LDAP implementation that requires configuration + of OpenLDAP with a new format samba schema. The new format schema file is + included in the <tt class="filename">examples/LDAP</tt> directory of the Samba distribution. + </p><p> + The new LDAP implementation significantly expands the control abilities that + were possible with prior versions of Samba. It is now possible to specify + "per user" profile settings, home directories, account access controls, and + much more. Corporate sites will see that the Samba-Team has listened to their + requests both for capability and to allow greater scalability. + </p></dd><dt><span class="term">mysqlsam (MySQL based backend):</span></dt><dd><p> + It is expected that the MySQL based SAM will be very popular in some corners. + This database backend will be on considerable interest to sites that want to + leverage existing MySQL technology. + </p></dd><dt><span class="term">xmlsam (XML based datafile):</span></dt><dd><p> + Allows the account and password data to be stored in an XML format + data file. This backend can not be used for normal operation, it can only + be used in conjunction with <b class="command">pdbedit</b>'s pdb2pdb + functionality. The DTD that is used might be subject to changes in the future. + </p><p> + 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="id2898749"></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> + Newer windows clients send encrypted passwords (so-called Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients will send only encrypted + passwords and refuse to send plain text passwords, unless their registry is tweaked. + </p><p> + These passwords can't be converted to unix style encrypted passwords. Because of that, + you can't use the standard unix user database, and you have to store the Lanman and NT + hashes somewhere else. + </p><p> + 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="id2898789"></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="id2898812"></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="id2898874"></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 + never sends the cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed values + are a "password equivalent". You cannot derive the user's password from them, but + they could potentially be used in a modified client to gain access to a server. + This would require considerable technical knowledge on behalf of the attacker but + is perfectly possible. You should thus treat the data stored in whatever passdb + backend you use (smbpasswd file, ldap, mysql) as though it contained the cleartext + passwords of all your users. Its contents must be kept secret, and the file should + be protected accordingly. + </p><p> + Ideally we would like a password scheme that involves neither plain text passwords + on the net nor on disk. Unfortunately this is not available as Samba is stuck with + having to be compatible with other SMB systems (WinNT, WfWg, Win95 etc). + </p><p> + Windows NT 4.0 Service pack 3 changed the default setting so that plaintext passwords + are disabled from being sent over the wire. This mandates either the use of encrypted + password support or edit the Windows NT registry to re-enable plaintext passwords. + </p><p> + The following versions of MS Windows do not support full domain security protocols, + although they may log onto a domain environment: + </p><div class="itemizedlist"><ul type="disc"><li><p>MS DOS Network client 3.0 with the basic network redirector installed</p></li><li><p>Windows 95 with the network redirector update installed</p></li><li><p>Windows 98 [se]</p></li><li><p>Windows Me</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + MS Windows XP Home does not have facilities to become a domain member and it can + not participate in domain logons. + </p></div><p> + The following versions of MS Windows fully support domain security protocols. + </p><div class="itemizedlist"><ul type="disc"><li><p>Windows NT 3.5x</p></li><li><p>Windows NT 4.0</p></li><li><p>Windows 2000 Professional</p></li><li><p>Windows 200x Server/Advanced Server</p></li><li><p>Windows XP Professional</p></li></ul></div><p> + All current release of Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling clear text authentication + does not disable the ability of the client to participate in encrypted authentication. + Instead, it allows the client to negotiate either plain text _or_ encrypted password + handling. + </p><p> + MS Windows clients will cache the encrypted password alone. Where plain text passwords + are re-enabled, through the appropriate registry change, the plain text password is NEVER + cached. This means that in the event that a network connections should become disconnected + (broken) only the cached (encrypted) password will be sent to the resource server to + affect a auto-reconnect. If the resource server does not support encrypted passwords the + auto-reconnect will fail. <span class="emphasis"><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="id2899068"></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 + that does not support encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. + </p></li><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="id2899128"></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="id2899165"></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="id2899188"></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> + The second way to affect Windows SID to UNIX UID mapping is via the + <span class="emphasis"><em>idmap uid, idmap gid</em></span> parameters in <tt class="filename">smb.conf</tt>. + Please refer to the man page for information about these parameters. + These parameters are essential when mapping users from a remote SAM server. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div><div></div></div><p> + Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs + on all servers in a distributed network. A distributed network is one where there exists + a PDC, one or more BDCs and/or one or more domain member servers. Why is this important? + This is important if files are being shared over more than one protocol (eg: NFS) and where + users are copying files across UNIX/Linux systems using tools such as <b class="command">rsync</b>. + </p><p> + The special facility is enabled using a parameter called <i class="parameter"><tt>idmap backend</tt></i>. + The default setting for this parameter is an empty string. Administrators should NOT set this + parameter except when an LDAP based passdb backend is in use. An example of use is: + </p><p> +</p><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. </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>idmap backend = ldapsam://ldap-server.quenya.org:636</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="acctmgmttools"></a>Account Management Tools</h2></div></div><div></div></div><p> +Samba provides two (2) tools for management of User and machine accounts. These tools are +called <b class="command">smbpasswd</b> and <b class="command">pdbedit</b>. A third tool is under +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="id2899351"></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. + </p><p> + <b class="command">smbpasswd</b> works in a client-server mode where it contacts the + local smbd to change the user's password on its behalf. This has enormous benefits + as follows: + </p><p> + <b class="command">smbpasswd</b> has the capability to change passwords on Windows NT + servers (this only works when the request is sent to the NT Primary Domain Controller + if changing an NT Domain user's password). + </p><p> + <b class="command">smbpasswd</b> can be used to: + </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>add</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>delete</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>enable</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>disable</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>set to NULL</em></span> user passwords</p></li><li><p><span class="emphasis"><em>manage interdomain trust accounts</em></span></p></li></ul></div><p> + To run smbpasswd as a normal user just type: + </p><p> +</p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>smbpasswd</tt></b> +<tt class="prompt">Old SMB password: </tt><b class="userinput"><tt><i class="replaceable"><tt>secret</tt></i></tt></b> +</pre><p> + For <i class="replaceable"><tt>secret</tt></i> type old value here - or hit return if + there was no old password +</p><pre class="screen"> +<tt class="prompt">New SMB Password: </tt><b class="userinput"><tt><i class="replaceable"><tt>new secret</tt></i></tt></b> +<tt class="prompt">Repeat New SMB Password: </tt><b class="userinput"><tt><i class="replaceable"><tt>new secret</tt></i></tt></b> +</pre><p> + </p><p> + If the old value does not match the current value stored for that user, or the two + new values do not match each other, then the password will not be changed. + </p><p> + When invoked by an ordinary user it will only allow change of their own + SMB password. + </p><p> + When run by root smbpasswd may take an optional argument, specifying + the user name whose SMB password you wish to change. When run as root, smbpasswd + does not prompt for or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords. + </p><p> + <b class="command">smbpasswd</b> is designed to work in the way familiar to UNIX + users who use the <b class="command">passwd</b> or <b class="command">yppasswd</b> commands. + While designed for administrative use, this tool provides essential user level + password change capabilities. + </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="id2899622"></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> + The <b class="command">pdbedit</b> tool is the only one that can manage the account + security and policy settings. It is capable of all operations that smbpasswd can + do as well as a super set of them. + </p><p> + One particularly important purpose of the <b class="command">pdbedit</b> is to allow + the migration of account information from one passdb backend to another. See the + <a href="passdb.html#XMLpassdb" title="XML">XML</a> password backend section of this chapter. + </p><p> + The following is an example of the user account information that is stored in + a tdbsam password backend. This listing was produced by running: + </p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>pdbedit -Lv met</tt></b> +UNIX username: met +NT username: +Account Flags: [UX ] +User SID: S-1-5-21-1449123459-1407424037-3116680435-2004 +Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201 +Full Name: Melissa E Terpstra +Home Directory: \\frodo\met\Win9Profile +HomeDir Drive: H: +Logon Script: scripts\logon.bat +Profile Path: \\frodo\Profiles\met +Domain: MIDEARTH +Account desc: +Workstations: melbelle +Munged dial: +Logon time: 0 +Logoff time: Mon, 18 Jan 2038 20:14:07 GMT +Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT +Password last set: Sat, 14 Dec 2002 14:37:03 GMT +Password can change: Sat, 14 Dec 2002 14:37:03 GMT +Password must change: Mon, 18 Jan 2038 20:14:07 GMT +</pre><p> + The <b class="command">pdbedit</b> tool allows migration of authentication (account) + databases from one backend to another. For example: To migrate accounts from an + 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="id2899790"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam, smbpasswd. + </p></li><li><p> + Execute: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>pdbedit -i smbpassed -e tdbsam</tt></b> +</pre><p> + </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="id2899860"></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. +</p><p> +It is possible to specify not only multiple different password backends, but even multiple +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="id2899902"></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="id2899942"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p> + Traditionally, when configuring <a class="indexterm" name="id2899952"></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 + in the thousands). + </p><div class="itemizedlist"><ul type="disc"><li><p> + The first is that all lookups must be performed sequentially. Given that + there are approximately two lookups per domain logon (one for a normal + session connection such as when mapping a network drive or printer), this + is a performance bottleneck for large sites. What is needed is an indexed approach + such as is used in databases. + </p></li><li><p> + The second problem is that administrators who desire to replicate a smbpasswd file + to more than one Samba server were left to use external tools such as + <b class="command">rsync(1)</b> and <b class="command">ssh(1)</b> and wrote custom, + in-house scripts. + </p></li><li><p> + And finally, the amount of information which is stored in an smbpasswd entry leaves + no room for additional attributes such as a home directory, password expiration time, + or even a Relative Identifier (RID). + </p></li></ul></div><p> + As a result of these deficiencies, a more robust means of storing user attributes + used by smbd was developed. The API which defines access to user accounts + is commonly referred to as the samdb interface (previously this was called the passdb + API, and is still so named in the Samba CVS trees). + </p><p> + 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="id2900055"></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> + As a general guide the Samba-Team does NOT recommend using the tdbsam backend for sites + 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="id2900089"></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 + an Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p> + The second item can be accomplished by using LDAP NSS and PAM modules. LGPL + versions of these libraries can be obtained from PADL Software + (<a href="http://www.padl.com/" target="_top">http://www.padl.com/</a>). More + information about the configuration of these packages may be found at "LDAP, + System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". + Refer to <a href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top"> + http://safari.oreilly.com/?XmlId=1-56592-491-6</a> for those who might wish to know + more about configuration and administration of an OpenLDAP server. + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + This section is outdated for Samba-3 schema. Samba-3 introduces a new schema + that has not been documented at the time of this publication. + </p></div><p> + This document describes how to use an LDAP directory for storing Samba user + account information traditionally stored in the smbpasswd(5) file. It is + assumed that the reader already has a basic understanding of LDAP concepts + and has a working directory server already installed. For more information + on LDAP architectures and Directories, please refer to the following sites. + </p><div class="itemizedlist"><ul type="disc"><li><p>OpenLDAP - <a href="http://www.openldap.org/" target="_top">http://www.openldap.org/</a></p></li><li><p>iPlanet Directory Server - + <a href="http://iplanet.netscape.com/directory" target="_top">http://iplanet.netscape.com/directory</a></p></li></ul></div><p> + Two additional Samba resources which may prove to be helpful are + </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="id2900244"></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.html" 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="id2900270"></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> +</p><pre class="programlisting"> +objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY + DESC 'Samba 3.0 Auxiliary SAM Account' + MUST ( uid $ sambaSID ) + MAY ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $ + sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $ + sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $ + displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $ + sambaProfilePath $ description $ sambaUserWorkstations $ + sambaPrimaryGroupSID $ sambaDomainName )) +</pre><p> +</p><p> + The <tt class="filename">samba.schema</tt> file has been formatted for OpenLDAP 2.0/2.1. + The OID's are owned by the Samba Team and as such is legal to be openly published. + If you translate the schema to be used with Netscape DS, please + submit the modified schema file as a patch to + <a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>. + </p><p> + Just as the smbpasswd file is meant to store information which supplements a + user's <tt class="filename">/etc/passwd</tt> entry, so is the sambaSamAccount object + meant to supplement the UNIX user account information. A sambaSamAccount is a + <tt class="constant">STRUCTURAL</tt> objectclass so it can be stored individually + in the directory. However, there are several fields (e.g. uid) which overlap + with the posixAccount objectclass outlined in RFC2307. This is by design. + </p><p> + In order to store all user account information (UNIX and Samba) in the directory, + it is necessary to use the sambaSamAccount and posixAccount objectclasses in + combination. However, smbd will still obtain the user's UNIX account + information via the standard C library calls (e.g. getpwnam(), et. al.). + This means that the Samba server must also have the LDAP NSS library installed + and functioning correctly. This division of information makes it possible to + store all Samba account information in LDAP, but still maintain UNIX account + information in NIS while the network is transitioning to a full LDAP infrastructure. + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2900380"></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> + in the samba source distribution. + </p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>cp samba.schema /etc/openldap/schema/</tt></b> +</pre><p> +</p><p> + Next, include the <tt class="filename">samba.schema</tt> file in <tt class="filename">slapd.conf</tt>. + The sambaSamAccount object contains two attributes which depend upon other schema + files. The 'uid' attribute is defined in <tt class="filename">cosine.schema</tt> and + the 'displayName' attribute is defined in the <tt class="filename">inetorgperson.schema</tt> + file. Both of these must be included before the <tt class="filename">samba.schema</tt> file. + </p><p> +</p><pre class="programlisting"> +## /etc/openldap/slapd.conf + +## schema files (core.schema is required by default) +include /etc/openldap/schema/core.schema + +## needed for sambaSamAccount +include /etc/openldap/schema/cosine.schema +include /etc/openldap/schema/inetorgperson.schema +include /etc/openldap/schema/samba.schema +include /etc/openldap/schema/nis.schema +.... +</pre><p> +</p><p> + It is recommended that you maintain some indices on some of the most useful attributes, + like in the following example, to speed up searches made on sambaSamAccount objectclasses + (and possibly posixAccount and posixGroup as well). + </p><p> +</p><pre class="programlisting"> +# Indices to maintain +## required by OpenLDAP +index objectclass eq + +index cn pres,sub,eq +index sn pres,sub,eq +## required to support pdb_getsampwnam +index uid pres,sub,eq +## required to support pdb_getsambapwrid() +index displayName pres,sub,eq + +## uncomment these if you are storing posixAccount and +## posixGroup entries in the directory as well +##index uidNumber eq +##index gidNumber eq +##index memberUid eq + +index sambaSID eq +index sambaPrimaryGroupSID eq +index sambaDomainName eq +index default sub +</pre><p> +</p><p> + Create the new index by executing: + </p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt>./sbin/slapindex -f slapd.conf +</pre><p> +</p><p> + Remember to restart slapd after making these changes: + </p><p> +</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="id2900576"></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.). + </p><p> +</p><pre class="programlisting"> +# Organization for Samba Base +dn: dc=quenya,dc=org +objectclass: dcObject +objectclass: organization +dc: quenya +o: Quenya Org Network +description: The Samba-3 Network LDAP Example + +# Organizational Role for Directory Management +dn: cn=Manager,dc=quenya,dc=org +objectclass: organizationalRole +cn: Manager +description: Directory Manager + +# Setting up container for users +dn: ou=People,dc=quenya,dc=org +objectclass: top +objectclass: organizationalUnit +ou: People + +# Setting up admin handle for People OU +dn: cn=admin,ou=People,dc=quenya,dc=org +cn: admin +objectclass: top +objectclass: organizationalRole +objectclass: simpleSecurityObject +userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz +</pre><p> +</p><p> + The userPassword shown above should be generated using <b class="command">slappasswd</b>. + </p><p> + The following command will then load the contents of the LDIF file into the LDAP + database. + </p><p> +</p><pre class="screen"> +<tt class="prompt">$ </tt><b class="userinput"><tt>slapadd -v -l initldap.dif</tt></b> +</pre><p> +</p><p> + Do not forget to secure your LDAP server with an adequate access control list, + as well as an admin password. + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + Before Samba can access the LDAP server you need to store the LDAP admin password + into the Samba-3 <tt class="filename">secrets.tdb</tt> database by: +</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="id2900704"></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="id2900721"></a><i class="parameter"><tt>passdb backend</tt></i> = ldapsam:url, + <a class="indexterm" name="id2900737"></a><i class="parameter"><tt>ldap ssl</tt></i>, + <a class="indexterm" name="id2900750"></a><i class="parameter"><tt>ldap admin dn</tt></i>, + <a class="indexterm" name="id2900764"></a><i class="parameter"><tt>ldap suffix</tt></i>, + <a class="indexterm" name="id2900777"></a><i class="parameter"><tt>ldap filter</tt></i>, + <a class="indexterm" name="id2900791"></a><i class="parameter"><tt>ldap machine suffix</tt></i>, + <a class="indexterm" name="id2900805"></a><i class="parameter"><tt>ldap user suffix</tt></i>, + <a class="indexterm" name="id2900819"></a><i class="parameter"><tt>ldap delete dn</tt></i>, + <a class="indexterm" name="id2900833"></a><i class="parameter"><tt>ldap passwd sync</tt></i>, + <a class="indexterm" name="id2900847"></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="id2900879"></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 = "(&(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="id2901104"></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> + Machines accounts are managed with the sambaSamAccount objectclass, just + like users accounts. However, it's up to you to store those accounts + in a different tree of your LDAP namespace: you should use + "ou=Groups,dc=quenya,dc=org" to store groups and + "ou=People,dc=quenya,dc=org" to store users. Just configure your + NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration + file). + </p><p> + In Samba release 3.0, the group management system is based on POSIX + groups. This means that Samba 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="id2901140"></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 + ntPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to + view the lmPassword or ntPassword attribute values.</p></li></ul></div><p> + These password hashes are clear text equivalents and can be used to impersonate + the user without deriving the original clear text strings. For more information + on the details of LM/NT password hashes, refer to the + <a href="passdb.html" 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="id2901200"></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="id2901222"></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="id2901244"></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 + the older method of securing communication between clients and servers. + </p><p> + The second security precaution is to prevent non-administrative users from + harvesting password hashes from the directory. This can be done using the + following ACL in <tt class="filename">slapd.conf</tt>: + </p><p> +</p><pre class="programlisting"> +## allow the "ldap admin dn" access, but deny everyone else +access to attrs=lmPassword,ntPassword + by dn="cn=Samba Admin,ou=people,dc=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="id2901300"></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="id2901317"></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. + </td></tr><tr><td align="left"><tt class="constant">sambaAcctFlags</tt></td><td align="justify">string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), + I(Domain trust account), H(Home dir required), S(Server trust account), + and D(disabled).</td></tr><tr><td align="left"><tt class="constant">sambaLogonTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaLogoffTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaKickoffTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaPwdCanChange</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaPwdMustChange</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaHomeDrive</tt></td><td align="justify">specifies the drive letter to which to map the + UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.</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="id2901492"></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="id2901527"></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. +Refer to the <b class="command">logon home</b> parameter in the <tt class="filename">smb.conf</tt> man page for more information. + </td></tr><tr><td align="left"><tt class="constant">sambaUserWorkstations</tt></td><td align="justify">character string value currently unused. + </td></tr><tr><td align="left"><tt class="constant">sambaSID</tt></td><td align="justify">The security identifier(SID) of the user. The windows equivalent of unix uid's.</td></tr><tr><td align="left"><tt class="constant">sambaPrimaryGroupSID</tt></td><td align="justify">the relative identifier (RID) of the primary group + of the user.</td></tr><tr><td align="left"><tt class="constant">sambaDomainName</tt></td><td align="justify">domain the user is part of.</td></tr></tbody></table></div><p> + </p><p> + The majority of these parameters are only used when Samba is acting as a PDC of + a domain (refer to the <a href="samba-pdc.html" title="Chapter 5. Domain Control">Samba as a primary domain controller</a> chapter for details on + how to configure Samba as a Primary Domain Controller). The following four attributes + are only stored with the sambaSamAccount entry if the values are non-default values: + </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="id2901683"></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="id2901708"></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="id2901732"></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="id2901758"></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"> + dn: uid=guest2, ou=people,dc=quenya,dc=org + sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 + sambaPwdMustChange: 2147483647 + sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513 + sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE + sambaPwdLastSet: 1010179124 + sambaLogonTime: 0 + objectClass: sambaSamAccount + uid: guest2 + sambaKickoffTime: 2147483647 + sambaAcctFlags: [UX ] + sambaLogoffTime: 2147483647 + sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006 + sambaPwdCanChange: 0 + </pre><p> + </p><p> + The following is an LDIF entry for using both the sambaSamAccount and + posixAccount objectclasses: + </p><p> + </p><pre class="programlisting"> + dn: uid=gcarter, ou=people,dc=quenya,dc=org + sambaLogonTime: 0 + displayName: Gerald Carter + sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE + sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201 + objectClass: posixAccount + objectClass: sambaSamAccount + sambaAcctFlags: [UX ] + userPassword: {crypt}BpM2ej8Rkzogo + uid: gcarter + uidNumber: 9000 + cn: Gerald Carter + loginShell: /bin/bash + logoffTime: 2147483647 + gidNumber: 100 + sambaKickoffTime: 2147483647 + sambaPwdLastSet: 1010179230 + sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004 + homeDirectory: /home/tashtego/gcarter + sambaPwdCanChange: 0 + sambaPwdMustChange: 2147483647 + sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 +</pre><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901824"></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="id2901842"></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="id2901925" href="#ftn.id2901925">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="id2901940"></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="id2901962"></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 : + +</p><pre class="screen"> +<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> < <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="id2902030"></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="id2902046"></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="id2902089"></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="id2902128"></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="id2902260"></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="id2902649"></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 + 'identifier:lanman pass column' and 'identifier:nt pass column' to + 'NULL' (without the quotes) and 'identifier:plain pass column' to the + name of the column containing the plaintext passwords. + </p><p> + If you use encrypted passwords, set the 'identifier:plain pass + column' to 'NULL' (without the quotes). This is the default. + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902679"></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 : + <b class="command">CONCAT(First_name,' ',Sur_name)</b> + </p><p> + Or, set 'identifier:workstations column' to : + <b class="command">NULL</b></p><p>See the MySQL documentation for more language constructs.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="XMLpassdb"></a>XML</h3></div></div><div></div></div><p>This module requires libxml2 to be installed.</p><p>The usage of pdb_xml is pretty straightforward. To export data, use: + </p><p> + <tt class="prompt">$ </tt> <b class="userinput"><tt>pdbedit -e xml:filename</tt></b> + </p><p> + (where filename is the name of the file to put the data in) + </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="id2902790"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902796"></a>Users can not logon</h3></div></div><div></div></div><p>“<span class="quote">I've installed samba, but now I can't log on with my unix account!</span>”</p><p>Make sure your user has been added to the current samba <a class="indexterm" name="id2902813"></a><i class="parameter"><tt>passdb backend</tt></i>. Read the section <a href="passdb.html#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="id2902841"></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: + </p><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>...</td></tr><tr><td><i class="parameter"><tt>passdb backend = smbpasswd, tdbsam</tt></i></td></tr><tr><td>...</td></tr></table><p> + </p><p> + Samba will add new accounts to the first entry in the <span class="emphasis"><em>passdb backend</em></span> + 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="id2902952"></a>auth methods does not work</h3></div></div><div></div></div><p> + If you explicitly set an <a class="indexterm" name="id2902963"></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="id2902979"></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="id2902998"></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.id2901925" href="#id2901925">3</a>] </sup>Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 10. Samba / MS Windows Network Browsing Guide </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 12. Mapping MS Windows and UNIX Groups</td></tr></table></div></body></html> diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index 57b69487c9..f38aeccc18 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -123,7 +123,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="id2797544"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2797533"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html new file mode 100644 index 0000000000..2b0abb56e6 --- /dev/null +++ b/docs/htmldocs/printing.html @@ -0,0 +1,2156 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 18. Classical Printing Support</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="msdfs.html" title="Chapter 17. Hosting a Microsoft Distributed File System tree on Samba"><link rel="next" href="CUPS-printing.html" title="Chapter 19. CUPS Printing Support in Samba 3.0"></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 18. Classical Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></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"><<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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="printing.html#id2912941">Features and Benefits</a></dt><dt><a href="printing.html#id2913045">Technical Introduction</a></dt><dd><dl><dt><a href="printing.html#id2913083">What happens if you send a Job from a Client</a></dt><dt><a href="printing.html#id2913154">Printing Related Configuration Parameters</a></dt><dt><a href="printing.html#id2913251">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="printing.html#id2913718">A simple Configuration to Print</a></dt><dd><dl><dt><a href="printing.html#id2913883">Verification of "Settings in Use" with testparm</a></dt><dt><a href="printing.html#id2914010">A little Experiment to warn you</a></dt></dl></dd><dt><a href="printing.html#id2914370">Extended Sample Configuration to Print</a></dt><dt><a href="printing.html#id2914701">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="printing.html#id2914714">The [global] Section</a></dt><dt><a href="printing.html#id2915245">The [printers] Section</a></dt><dt><a href="printing.html#id2915706">Any [my_printer_name] Section</a></dt><dt><a href="printing.html#id2916027">Print Commands</a></dt><dt><a href="printing.html#id2916108">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="printing.html#id2916791">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="printing.html#id2917131">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="printing.html#id2917292">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="printing.html#id2917453">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="printing.html#id2917566">Creating the [print$] Share</a></dt><dt><a href="printing.html#id2917756">Parameters in the [print$] Section</a></dt><dt><a href="printing.html#id2918066">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="printing.html#id2918239">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="printing.html#id2918333">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="printing.html#id2918531">Setting Drivers for existing Printers with +rpcclient</a></dt></dl></dd><dt><a href="printing.html#id2920241">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="printing.html#id2920260">The first Client Driver Installation</a></dt><dt><a href="printing.html#id2920462">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="printing.html#id2920763">Further Client Driver Install Procedures</a></dt><dt><a href="printing.html#id2920857">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="printing.html#id2921029">Other Gotchas</a></dt><dd><dl><dt><a href="printing.html#id2921063">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="printing.html#id2921530">Supporting large Numbers of Printers</a></dt><dt><a href="printing.html#id2921841">Adding new Printers with the Windows NT APW</a></dt><dt><a href="printing.html#id2922136">Weird Error Message Cannot connect under a +different Name</a></dt><dt><a href="printing.html#id2922236">Be careful when assembling Driver Files</a></dt><dt><a href="printing.html#id2922594">Samba and Printer Ports</a></dt><dt><a href="printing.html#id2922687">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="printing.html#id2922712">The Imprints Toolset</a></dt><dd><dl><dt><a href="printing.html#id2922768">What is Imprints?</a></dt><dt><a href="printing.html#id2922810">Creating Printer Driver Packages</a></dt><dt><a href="printing.html#id2922828">The Imprints Server</a></dt><dt><a href="printing.html#id2922853">The Installation Client</a></dt></dl></dd><dt><a href="printing.html#id2923008">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="printing.html#id2923342">The addprinter command</a></dt><dt><a href="printing.html#id2923388">Migration of "Classical" printing to Samba</a></dt><dt><a href="printing.html#id2923561">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="printing.html#id2923575">Common Errors</a></dt><dd><dl><dt><a href="printing.html#id2923582">I give my root password but I don't get access</a></dt><dt><a href="printing.html#id2923615">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="id2912941"></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. +</p><p> +A Samba print service may be run on a Standalone or a Domain +member server, side by side with file serving functions, or on a +dedicated print server. It can be made as tight or as loosely secured +as needs dictate. Configurations may be simple or complex. Available +authentication schemes are essentially the same as described for file +services in previous chapters. Overall, Samba's printing support is +now able to replace an NT or Windows 2000 print server full-square, +with additional benefits in many cases. Clients may download and +install drivers and printers through their familiar "Point'n'Print" +mechanism. Printer installations executed by "Logon Scripts" are no +problem. Administrators can upload and manage drivers to be used by +clients through the familiar "Add Printer Wizard". As an additional +benefit, driver and printer management may be run from the command line +or through scripts, making it more efficient in case of large numbers +of printers. If a central accounting of print jobs (tracking every +single page and supplying the raw data for all sorts of statistical +reports) is required, this is best supported by CUPS as the print +subsystem underneath the Samba hood. +</p><p> +This chapter deals with the foundations of Samba printing, as they +implemented by the more traditional UNIX (BSD- and System V-style) +printing systems. Many things apply to CUPS, the newer Common UNIX +Printing System, too; so if you use CUPS, you might be tempted to jump +to the next chapter -- but you will certainly miss a few things if you +do so. Better to read this chapter too. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Most of the given examples have been verified on Windows XP +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="id2913045"></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 +real printing system for further processing. Therefore it needs to +"talk" to two sides: to the Windows print clients and to the UNIX +printing system. Hence we must differentiate between the various +client OS types each of which behave differently, as well as the +various UNIX print subsystems, which themselves have different +features and are accessed differently. This part of the Samba HOWTO +Collection deals with the "traditional" way of UNIX printing first; +the next chapter covers in great detail the more modern +<span class="emphasis"><em>Common UNIX Printing System</em></span> +(CUPS). + +</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="id2913083"></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: +</p><div class="orderedlist"><ol type="1"><li><p>Windows opens a connection to the printer share</p></li><li><p>Samba must authenticate the user</p></li><li><p>Windows sends a copy of the printfile over the network +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="id2913154"></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 +acquire an overview about these. As with other parameters, there are +Global Level (tagged with a "<span class="emphasis"><em>G</em></span>" in the listings) and +Service Level ("<span class="emphasis"><em>S</em></span>") parameters. +</p><div class="variablelist"><dl><dt><span class="term">Service Level Parameters</span></dt><dd><p>These <span class="emphasis"><em>may</em></span> go into the +<i class="parameter"><tt>[global]</tt></i> section of <tt class="filename">smb.conf</tt>. +In this case they define the default +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="id2913251"></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="id2913280"></a><i class="parameter"><tt>addprinter command</tt></i>, +<a class="indexterm" name="id2913295"></a><i class="parameter"><tt>deleteprinter command</tt></i>, +<a class="indexterm" name="id2913310"></a><i class="parameter"><tt>disable spoolss</tt></i>, +<a class="indexterm" name="id2913324"></a><i class="parameter"><tt>enumports command</tt></i>, +<a class="indexterm" name="id2913338"></a><i class="parameter"><tt>load printers</tt></i>, +<a class="indexterm" name="id2913352"></a><i class="parameter"><tt>lpq cache time</tt></i>, +<a class="indexterm" name="id2913366"></a><i class="parameter"><tt>os2 driver map</tt></i>, +<a class="indexterm" name="id2913380"></a><i class="parameter"><tt>printcap name</tt></i>, <a class="indexterm" name="id2913394"></a><i class="parameter"><tt>printcap</tt></i>, +<a class="indexterm" name="id2913407"></a><i class="parameter"><tt>show add printer wizard</tt></i>, +<a class="indexterm" name="id2913422"></a><i class="parameter"><tt>total print jobs</tt></i>, +<a class="indexterm" name="id2913436"></a><i class="parameter"><tt>use client driver</tt></i>. +</p><p>Service level parameters: <a class="indexterm" name="id2913454"></a><i class="parameter"><tt>hosts allow</tt></i>, +<a class="indexterm" name="id2913468"></a><i class="parameter"><tt>hosts deny</tt></i>, +<a class="indexterm" name="id2913481"></a><i class="parameter"><tt>lppause command</tt></i>, +<a class="indexterm" name="id2913496"></a><i class="parameter"><tt>lpq command</tt></i>, +<a class="indexterm" name="id2913509"></a><i class="parameter"><tt>lpresume command</tt></i>, +<a class="indexterm" name="id2913523"></a><i class="parameter"><tt>lprm command</tt></i>, +<a class="indexterm" name="id2913537"></a><i class="parameter"><tt>max print jobs</tt></i>, +<a class="indexterm" name="id2913551"></a><i class="parameter"><tt>min print space</tt></i>, +<a class="indexterm" name="id2913565"></a><i class="parameter"><tt>print command</tt></i>, +<a class="indexterm" name="id2913579"></a><i class="parameter"><tt>printable</tt></i>, <a class="indexterm" name="id2913593"></a><i class="parameter"><tt>print ok </tt></i>, +<a class="indexterm" name="id2913606"></a><i class="parameter"><tt>printer name</tt></i>, <a class="indexterm" name="id2913621"></a><i class="parameter"><tt>printer</tt></i>, +<a class="indexterm" name="id2913634"></a><i class="parameter"><tt>printer admin</tt></i>, +<a class="indexterm" name="id2913648"></a><i class="parameter"><tt>printing</tt></i> = [cups|bsd|lprng...], +<a class="indexterm" name="id2913662"></a><i class="parameter"><tt>queuepause command</tt></i>, +<a class="indexterm" name="id2913676"></a><i class="parameter"><tt>queueresume command</tt></i>, +<a class="indexterm" name="id2913690"></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="id2913718"></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 +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="id2913746"></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 +the default value. The <b class="command">testparm</b> utility when run as root +is capable of reporting all setting, both default as well as <tt class="filename">smb.conf</tt> file +settings. <b class="command">Testparm</b> gives warnings for all mis-configured +settings. The complete output is easily 340 lines and more, so you may want +to pipe it through a pager program. +</p><p> +The syntax for the configuration file is easy to grasp. You should +know that is not very picky about its +syntax. It has been explained elsewhere in this document. A short +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="id2913883"></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", +"spool", "driver", "ports" and "[" in testparm's output and gives you +a nice overview about the running smbd's print configuration. (Note +that this command does not show individually created printer shares, +or the spooling paths in each case). Here is the output of my Samba +setup, with exactly the same settings in +as shown above: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v | egrep "(lp|print|spool|driver|ports|\[)"</tt></b> + Load smb config files from /etc/samba/smb.conf.simpleprinting + Processing section "[homes]" + Processing section "[printers]" + + [global] + smb ports = 445 139 + lpq cache time = 10 + total print jobs = 0 + load printers = Yes + printcap name = /etc/printcap + disable spoolss = No + enumports command = + addprinter command = + deleteprinter command = + show add printer wizard = Yes + os2 driver map = + printer admin = + min print space = 0 + max print jobs = 1000 + printable = No + printing = bsd + print command = lpr -r -P'%p' %s + lpq command = lpq -P'%p' + lprm command = lprm -P'%p' %j + lppause command = + lpresume command = + printer name = + use client driver = No + + [homes] + + [printers] + path = /var/spool/samba + printable = Yes + +</pre><p> +You can easily verify which settings were implicitly added by Samba's +default behaviour. <span class="emphasis"><em>Don't forget about this point: it may +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="id2914010"></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="id2914020"></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 + # load printers = Yes + # This setting is commented ooouuuuut!! + +<tt class="prompt">root# </tt>testparm -v /etc/samba/smb.conf | egrep "(load printers)" + load printers = Yes + +</pre><p> +Despite my imagination that the commenting out of this setting should +prevent Samba from publishing my printers, it still did! Oh Boy -- it +cost me quite some time to find out the reason. But I am not fooled +any more... at least not by this ;-) +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>grep -A1 "load printers" /etc/samba/smb.conf</tt></b> + load printers = No + # This setting is what I mean!! + # load printers = Yes + # This setting is commented ooouuuuut!! + +<tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v smb.conf.simpleprinting | egrep "(load printers)"</tt></b> + load printers = No + +</pre><p> +Only when setting the parameter explicitly to +"<a class="indexterm" name="id2914136"></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 +settings which might not reflect your intentions.</p></li></ul></div><p> +You can have a working Samba print configuration with this +minimal : +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>cat /etc/samba/smb.conf-minimal</tt></b> + [printers] + +</pre><p> +This example should show you that you can use testparm to test any +filename for fitness as a Samba configuration. Actually, we want to +encourage you <span class="emphasis"><em>not</em></span> to change your + on a working system (unless you know +exactly what you are doing)! Don't rely on an assumption that changes +will only take effect after you re-start smbd! This is not the +case. Samba re-reads its every 60 +seconds and on each new client connection. You might have to face +changes for your production clients that you didn't intend to apply at +this time! You will now note a few more interesting things. Let's now +ask <b class="command">testparm</b> what the Samba print configuration +would be, if you used this minimalistic file as your real +: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"</tt></b> + Processing section "[printers]" + WARNING: [printers] service MUST be printable! + No path in service printers - using /tmp + + lpq cache time = 10 + total print jobs = 0 + load printers = Yes + printcap name = /etc/printcap + disable spoolss = No + enumports command = + addprinter command = + deleteprinter command = + show add printer wizard = Yes + os2 driver map = + printer admin = + min print space = 0 + max print jobs = 1000 + printable = No + printing = bsd + print command = lpr -r -P%p %s + lpq command = lpq -P%p + printer name = + use client driver = No + [printers] + printable = Yes + +</pre><p> +testparm issued 2 warnings: +</p><div class="itemizedlist"><ul type="disc"><li><p>because we didn't specify the +<i class="parameter"><tt>[printers]</tt></i> section as printable, +and</p></li><li><p>because we didn't tell it which spool directory to +use.</p></li></ul></div><p> +However, this was not fatal, and samba will default to values that +will work here. Please, don't rely on this and don't use this +example! This was only meant to make you careful to design and specify +your setup to be what you really want it to be. The outcome on your +system may vary for some parameters, since you may have a Samba built +with a different compile-time configuration. +<span class="emphasis"><em>Warning:</em></span> don't put a comment sign <span class="emphasis"><em>at +the end</em></span> of a valid line. It +will cause the parameter to be ignored (just as if you had put the +comment sign at the front). At first I regarded this as a bug in my +Samba version(s). But the man page states: “<span class="quote">Internal whitespace +in a parameter value is retained verbatim.</span>” This means that a +line consisting of, for example, +</p><table class="simplelist" border="0" summary="Simple list"><tr><td># This defines LPRng as the printing system"</td></tr><tr><td><i class="parameter"><tt>printing = lprng</tt></i></td></tr></table><p> +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="id2914370"></a>Extended Sample Configuration to Print</h2></div></div><div></div></div><p> + In <a href="printing.html#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 +printing here, because we guess it is still the most commonly used +system on legacy Linux installations (new installs now predominantly +have CUPS, which is discussed entirely in the next chapter of this +document). Note, that this example explicitly names many parameters +which don't need to be specified because they are set by default. You +might be able to do with a leaner <tt class="filename">smb.conf</tt> file.</p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example 18.2. Extended 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><i class="parameter"><tt>show add printer wizard = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = /etc/printcap</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = @ntadmin, root</tt></i></td></tr><tr><td><i class="parameter"><tt>total print jobs = 100</tt></i></td></tr><tr><td><i class="parameter"><tt>lpq cache time = 20</tt></i></td></tr><tr><td><i class="parameter"><tt>use client driver = no</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>printable = yes</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>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no </tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[my_printer_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer with Restricted Access</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba_my_printer</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = kurt</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = 0.0.0.0</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr></table></div><p> +This <span class="emphasis"><em>also</em></span> is only an example configuration. You +may not find all the settings in your own + (as pre-configured by your OS +vendor). Many configuration parameters, if not explicitly set to a +specific value, are used and set by Samba implicitly to its own +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="id2914701"></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="id2914714"></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 +<i class="parameter"><tt>[print$]</tt></i>...) It contains all parameters which +apply to the server as a whole. It is the place for parameters which +have only a "global" meaning. It may also contain service level +parameters which then define default settings for all other +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="id2914781"></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="id2914801"></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="id2914838"></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="id2914868"></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 +separate shares for each printer. Each automatically created printer +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="id2914927"></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 +share listing (as shown in <span class="guiicon">Network Neighbourhood</span> or +by the <b class="command">net view</b> command). To disable it, you need to +explicitly set it to <tt class="constant">no</tt> (commenting it out +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="id2914996"></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 “<span class="quote">no more space +available on server</span>” 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="id2915035"></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="id2915072"></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="id2915102"></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="id2915124"></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="id2915141"></a><i class="parameter"><tt>printer admin</tt></i> parameter on the +share levels). +</p></dd><dt><span class="term"><a class="indexterm" name="id2915159"></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="id2915186"></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="id2915245"></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, +because Samba on startup then creates a printer share for every +printername it finds in the printcap file. You could regard this +section as a general convenience shortcut to share all printers with +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="id2915287"></a><i class="parameter"><tt>comment</tt></i> = All printers</span></dt><dd><p> the <a class="indexterm" name="id2915307"></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="id2915340"></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="id2915374"></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="id2915394"></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="id2915428"></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="id2915453"></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="id2915487"></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="id2915513"></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="id2915562"></a><i class="parameter"><tt>public</tt></i> = yes</span></dt><dd><p> this is a synonym for <a class="indexterm" name="id2915582"></a><i class="parameter"><tt>guest ok</tt></i> = yes. Since we have <a class="indexterm" name="id2915596"></a><i class="parameter"><tt>guest ok</tt></i> = yes, +it really doesn't need to be here! (This leads to the interesting +question: “<span class="quote">What, if I by accident have to contradictory settings +for the same share?</span>” The answer is: the last one encountered by +Samba wins. The "winner" is shown by testparm. Testparm doesn't +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="id2915632"></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="id2915669"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p> +synonym for <a class="indexterm" name="id2915689"></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="id2915706"></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="id2915717"></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 +printer the same name as an existing user or file share name: upon a +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="id2915747"></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="id2915772"></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="id2915799"></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="id2915832"></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="id2915866"></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="id2915889"></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="id2915913"></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="id2915935"></a><i class="parameter"><tt>hosts allow</tt></i> and <a class="indexterm" name="id2915949"></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="id2915970"></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="id2916003"></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="id2916027"></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="id2916055"></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 +case. For debugging purposes or some other reason you may want to do +something completely different than "print" the file. An example is a +command that just copies the print file to a temporary location for +further investigation when you need to debug printing. If you craft +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="id2916108"></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="id2916122"></a><i class="parameter"><tt>print command</tt></i>. The default print command varies +depending on the <a class="indexterm" name="id2916138"></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="id2916224"></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="id2916254"></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="id2916286"></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="id2916317"></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="id2916348"></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="id2916378"></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="id2916408"></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="id2916439"></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="id2916470"></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="id2916500"></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="id2916531"></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="id2916556"></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="id2916582"></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="id2916613"></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="id2916638"></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="id2916676"></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 +<b class="command">lp -c -d%p -oraw; rm %s</b> With <i class="parameter"><tt>printing = +cups</tt></i> , and if SAMBA is compiled against libcups, any +manually set print command will be ignored! +</p><p> +Having listed the above mappings here, you should note that there used +to be a <span class="emphasis"><em>bug</em></span> in recent 2.2.x versions which +prevented the mapping from taking effect. It lead to the +"bsd|aix|lprng|plp" settings taking effect for all other systems, for +the most important commands (the <b class="command">print</b> command, the +<b class="command">lpq</b> command and the <b class="command">lprm</b> +command). The <b class="command">lppause</b> command and the +<b class="command">lpresume</b> command remained empty. Of course, these +commands worked on bsd|aix|lprng|plp but they didn't work on +sysv|hpux|qnx systems. To work around this bug, you need to +explicitly set the commands. Use <b class="command">testparm -v</b> to +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="id2916791"></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="id2916802"></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 +be the case. The print subsystem will probably not remove the spool +file on its own. So whatever command you specify on your own you +should ensure that the spool file is deleted after it has been +processed. +</p><p> +There is no difficulty with using your own customized print commands +with the traditional printing systems. However, if you don't wish to +"roll your own", you should be well informed about the default +built-in commands that Samba uses for each printing subsystem (see the +table above). In all the commands listed in the last paragraphs you +see parameters of the form <span class="emphasis"><em>%X</em></span> These are +<span class="emphasis"><em>macros</em></span>, or shortcuts, used as place holders for +the names of real objects. At the time of running a command with such +a placeholder, Samba will insert the appropriate value +automatically. Print commands can handle all Samba macro +substitutions. In regard to printing, the following ones do have +special relevance: +</p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>%s, %f</tt></i> - the path to the spool +file name</p></li><li><p><i class="parameter"><tt>%p</tt></i> - the appropriate printer +name</p></li><li><p><i class="parameter"><tt>%J</tt></i> - the job name as +transmitted by the client.</p></li><li><p><i class="parameter"><tt>%c</tt></i> - the number of printed +pages of the spooled job (if known).</p></li><li><p><i class="parameter"><tt>%z</tt></i> - the size of the spooled +print job (in bytes)</p></li></ul></div><p> +The print command MUST contain at least one occurrence of +<i class="parameter"><tt>%s</tt></i> or <i class="parameter"><tt>%f</tt></i>. -- The +<i class="parameter"><tt>%p</tt></i> is optional. If no printer name is supplied, +the <i class="parameter"><tt>%p</tt></i> will be silently removed from the print +command. In this case the job is sent to the default printer. +</p><p> +If specified in the <i class="parameter"><tt>[global]</tt></i> section, the print +command given will be used for any printable service that does not +have its own print command specified. If there is neither a specified +print command for a printable service nor a global print command, +spool files will be created but not processed! And (most importantly): +print files will not be removed, so they will start filling your Samba +hard disk. +</p><p> +Note that printing may fail on some UNIXes from the "nobody" +account. If this happens, create an alternative guest account and +supply it with the privilege to print. Set up this guest account in +the <i class="parameter"><tt>[global]</tt></i> section with the <i class="parameter"><tt>guest +account</tt></i> parameter. +</p><p> +You can form quite complex print commands. You need to realize that +print commands are just passed to a UNIX shell. The shell is able to +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="id2917032"></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 >> /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="id2917081"></a><i class="parameter"><tt>print command</tt></i> parameter varies depending on the setting of +the <a class="indexterm" name="id2917098"></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="id2917131"></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 +they share printers. Beginning with the 2.2.0 release, Samba started +to support the native Windows NT printing mechanisms. These are +implemented via <span class="emphasis"><em>MS-RPC</em></span> (RPC = <span class="emphasis"><em>Remote +Procedure Calls</em></span> ). MS-RPCs use the +<span class="emphasis"><em>SPOOLSS</em></span> named pipe for all printing. +</p><p> +The additional functionality provided by the new SPOOLSS support includes: +</p><div class="itemizedlist"><ul type="disc"><li><p>Support for downloading printer driver files to Windows +95/98/NT/2000 clients upon demand (<span class="emphasis"><em>Point'n'Print</em></span>); +</p></li><li><p>Uploading of printer drivers via the Windows NT +<span class="emphasis"><em>Add Printer Wizard</em></span> (APW) or the +<a href="http://imprints.sourceforge.net/" target="_top">Imprints</a> tool set. +</p></li><li><p>Support for the native MS-RPC printing calls such as + StartDocPrinter, EnumJobs(), etc... (See the <a href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a> for more information on the Win32 printing API);</p></li><li><p>Support for NT <span class="emphasis"><em>Access Control +Lists</em></span> (ACL) on printer objects;</p></li><li><p>Improved support for printer queue manipulation +through the use of internal databases for spooled job information +(implemented by various <tt class="filename">*.tdb</tt> +files).</p></li></ul></div><p> +One other benefit of an update is this: Samba 3 is able to publish +all its printers in Active Directory (or LDAP)! +</p><p> +One slight difference is here: it is possible on a Windows NT print +server to have printers listed in the Printers folder which are +<span class="emphasis"><em>not</em></span> shared. Samba does not make this +distinction. By definition, the only printers of which Samba is aware +are those which are specified as shares in +. The reason is that Windows NT/200x/XP Professional +clients do not normally need to use the standard SMB printer share; +rather they can print directly to any printer on another Windows NT +host using MS-RPC. This of course assumes that the printing client has +the necessary privileges on the remote host serving the printer. The +default permissions assigned by Windows NT to a printer gives the +"Print" permissions to the 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="id2917292"></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 +answer to this is: No, it is not a +<span class="emphasis"><em>requirement</em></span>. Windows NT/2000 clients can, of +course, also run their APW to install drivers +<span class="emphasis"><em>locally</em></span> (which then connect to a Samba served +print queue). This is the same method as used by Windows 9x +clients. (However, a <span class="emphasis"><em>bug</em></span> existed in Samba 2.2.0 +which made Windows NT/2000 clients require that the Samba server +possess a valid driver for the printer. This was fixed in Samba +2.2.1). +</p><p> +But it is a new <span class="emphasis"><em>option</em></span> to install the printer +drivers into the <i class="parameter"><tt>[print$]</tt></i> share of the Samba +server, and a big convenience too. Then <span class="emphasis"><em>all</em></span> +clients (including 95/98/ME) get the driver installed when they first +connect to this printer share. The <span class="emphasis"><em>uploading</em></span> or +<span class="emphasis"><em>depositing</em></span> of the driver into this +<i class="parameter"><tt>[print$]</tt></i> share, and the following binding of +this driver to an existing Samba printer share can be achieved by +different means: +</p><div class="itemizedlist"><ul type="disc"><li><p>running the <span class="emphasis"><em>APW</em></span> on an +NT/200x/XP Professional client (this doesn't work from 95/98/ME +clients);</p></li><li><p>using the <span class="emphasis"><em>Imprints</em></span> +toolset;</p></li><li><p>using the <span class="emphasis"><em>smbclient</em></span> and +<span class="emphasis"><em>rpcclient</em></span> commandline tools;</p></li><li><p>using <span class="emphasis"><em>cupsaddsmb</em></span>(only works for +the CUPS printing system, not for LPR/LPD, LPRng +etc.).</p></li></ul></div><p> +Please take additional note of the following fact: <span class="emphasis"><em>Samba +does not use these uploaded drivers in any way to process spooled +files</em></span>. Drivers are utilized entirely by the clients, who +download and install them via the "Point'n'Print" mechanism supported +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="id2917453"></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 +named <span class="emphasis"><em>[printer$]</em></span>. This name was taken from the +same named service created by Windows 9x clients when a printer was +shared by them. Windows 9x printer servers always have a +<i class="parameter"><tt>[printer$]</tt></i> service which provides read-only +access (with no password required) in order to support printer driver +downloads. However, Samba's initial implementation allowed for a +parameter named <i class="parameter"><tt>printer driver location</tt></i> to be +used on a per share basis. This specified the location of the driver +files associated with that printer. Another parameter named +<i class="parameter"><tt>printer driver</tt></i> provided a means of defining the +printer driver name to be sent to the client. These parameters, +including the <i class="parameter"><tt>printer driver file</tt></i> parameter, +are now removed and can not be used in installations of samba-3. +Now the share name <i class="parameter"><tt>[print$]</tt></i> is used for the +location of downloadable printer drivers. It is taken from the +<i class="parameter"><tt>[print$]</tt></i> service created by Windows NT PCs when +a printer is shared by them. Windows NT print servers always have a +<i class="parameter"><tt>[print$]</tt></i> service which provides read-write +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="id2917566"></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 +hard coded in Samba's internals (because it is hard coded in the MS +Windows clients too). It cannot be renamed since Windows clients are +programmed to search for a service of exactly this name if they want +to retrieve printer driver files. +</p><p> +You should modify the server's file to +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="id2917613"></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="id2917739"></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="id2917756"></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="id2917784"></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="id2917819"></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="id2917844"></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="id2917889"></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 +will be guaranteed to have an account on the Samba host, then this is +a non-issue.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +The non-issue is this: if all your Windows NT users are guaranteed to +be authenticated by the Samba server (for example if Samba +authenticates via an NT domain server and the NT user has already been +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="id2917936"></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="id2917963"></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="id2917990"></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 +public's "read-only" access), which they need to update files on the +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="id2918045"></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="id2918066"></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="id2918085"></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 +*must* be exactly the names listed below (you may leave out the +subdirectories of architectures you don't want to support). +</p><p> +Therefore, create a directory tree below the +<i class="parameter"><tt>[print$]</tt></i> share for each architecture you wish +to support. +</p><pre class="programlisting"> +[print$]--+-- + |--W32X86 # serves drivers to "Windows NT x86" + |--WIN40 # serves drivers to "Windows 95/98" + |--W32ALPHA # serves drivers to "Windows NT Alpha_AXP" + |--W32MIPS # serves drivers to "Windows NT R4000" + |--W32PPC # serves drivers to "Windows NT PowerPC" +</pre><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Required permissions</h3><p> +In order to add a new driver to your Samba host, one of two conditions +must hold true: +</p><div class="itemizedlist"><ul type="disc"><li><p>The account used to connect to the Samba host must +have a UID of 0 (i.e. a root account)</p></li><li><p>The account used to connect to the Samba host must be +named in the <span class="emphasis"><em>printer admin</em></span>list.</p></li></ul></div><p> +Of course, the connected account must still possess access to add +files to the subdirectories beneath +<i class="parameter"><tt>[print$]</tt></i>. Remember that all file shares are set +to 'read only' by default. +</p></div><p> +Once you have created the required <i class="parameter"><tt>[print$]</tt></i> +service and associated subdirectories, go to a Windows NT 4.0/2k/XP +client workstation. Open <span class="guiicon">Network Neighbourhood</span> or +<span class="guiicon">My Network Places</span> and browse for the Samba host. +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="id2918239"></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 +<span class="emphasis"><em>driver files</em></span> need to be present in this share, +too! So far it is still an empty share. Unfortunately, it is not enough +to just copy the driver files over. They need to be <span class="emphasis"><em>set +up</em></span> too. And that is a bit tricky, to say the least. We +will now discuss two alternative ways to install the drivers into +<i class="parameter"><tt>[print$]</tt></i>: +</p><div class="itemizedlist"><ul type="disc"><li><p>using the Samba commandline utility +<b class="command">rpcclient</b> with its various subcommands (here: +<b class="command">adddriver</b> and <b class="command">setdriver</b>) from +any UNIX workstation;</p></li><li><p>running a GUI (<span class="emphasis"><em>Printer +Properties</em></span> and <span class="emphasis"><em>Add Printer Wizard</em></span>) +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="id2918333"></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 +this driver name is set to a NULL +string. This must be changed now. The local <span class="emphasis"><em>Add Printer +Wizard</em></span>, run from NT/2000/XP clients, will help us in this +task. +</p><p> +However, the job to set a valid driver for the printer is not a +straightforward one: You must attempt to view the printer properties +for the printer to which you want the driver assigned. Open the +Windows Explorer, open Network Neighbourhood, browse to the Samba +host, open Samba's <span class="guiicon">Printers</span> folder, right-click the printer icon and +select <span class="guimenu">Properties...</span>. You are now trying to view printer and driver +properties for a queue which has this default <tt class="constant">NULL</tt> driver +assigned. This will result in an error message (this is normal here): +</p><p><span class="errorname"> Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler properties +will be displayed. Do you want to install the driver +now?</span></p><p> +<span class="emphasis"><em>Important:</em></span>Don't click <span class="guibutton">Yes</span>! Instead, +<span class="emphasis"><em>click <span class="guibutton">No</span></em></span> in the error dialog. +Only now you will be presented with the printer properties window. From here, +the way to assign a driver to a printer is open to us. You have now the choice +either: +</p><div class="itemizedlist"><ul type="disc"><li><p>select a driver from the pop-up list of installed +drivers. <span class="emphasis"><em>Initially this list will be empty.</em></span> +Or</p></li><li><p>use the <span class="guibutton">New Driver...</span> button to +install a new printer driver (which will in fact start up the +APW).</p></li></ul></div><p> +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="id2918468"></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="id2918510"></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="id2918531"></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 +done from the UNIX command line. This involves four distinct steps: +</p><div class="orderedlist"><ol type="1"><li><p>gathering the info about the required driver files +and collecting the files together;</p></li><li><p>deposit the driver files into the +<i class="parameter"><tt>[print$]</tt></i> share's correct subdirectories +(possibly by using <b class="command">smbclient</b>);</p></li><li><p>running the <b class="command">rpcclient</b> +commandline utility once with the <b class="command">adddriver</b> +subcommand,</p></li><li><p>running <b class="command">rpcclient</b> a second +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="id2918640"></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 +may not be the possible, since the *.inf file might be +missing. Unfortunately, many vendors have now started to use their own +installation programs. These installations packages are often some +sort of Windows platform archive format, plus, the files may get +re-named during the installation process. This makes it extremely +difficult to identify the driver files you need. +</p><p> +Then you only have the second option: install the driver first on a +Windows client *locally* and investigate which file names and paths it +uses after they are installed. (Note, that you need to repeat this +procedure for every client platform you want to support. We are going +to show it here for the <span class="application">W32X86</span> platform only, a +name used by Microsoft for all WinNT/2k/XP clients...) +</p><p> +A good method to recognize the driver files this is to print the test +page from the driver's <span class="guilabel">Properties</span> Dialog +(<span class="guilabel">General</span> tab). Then look at the list of driver +files named on the printout. You'll need to recognize what Windows +(and Samba) are calling the <span class="guilabel">Driver File</span> , the +<span class="guilabel">Data File</span>, the <span class="guilabel">Config File</span>, +the <span class="guilabel">Help File</span> and (optionally) the +<span class="guilabel">Dependent Driver Files</span> (this may vary slightly +for Windows NT). You need to remember all names (or better take a +note) for the next steps. +</p><p> +Another method to quickly test the driver filenames and related paths +is provided by the <b class="command">rpcclient</b> utility. Run it with +<b class="command">enumdrivers</b> or with the +<b class="command">getdriver</b> subcommand, each in the +<span class="emphasis"><em>3</em></span> level. In the following example, +<span class="emphasis"><em>TURBO_XP</em></span> is the name of the Windows PC (in this +case it was a Windows XP Professional laptop, BTW). I had installed +the driver locally to TURBO_XP while <span class="emphasis"><em>kde-bitshop</em></span> is +the name of the Linux host from which I am working. We could run an +<span class="emphasis"><em>interactive</em></span> <b class="command">rpcclient</b> session; +then we'd get an <span class="emphasis"><em>rpcclient /></em></span> prompt and would +type the subcommands at this prompt. This is left as a good exercise +to the reader. For now we use <b class="command">rpcclient</b> with the +<tt class="option">-c</tt> parameter to execute a single subcommand +line and exit again. This is the method you would use if you want to +create scripts to automate the procedure for a large number of +printers and drivers. Note the different quotes used to overcome the +different spaces in between words: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'Danka%xxxx' -c \ + 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP</tt></b> +cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3 + +[Windows NT x86] +Printer Driver Info 3: + Version: [2] + Driver Name: [Heidelberg Digimaster 9110 (PS)] + Architecture: [Windows NT x86] + Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL] + Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd] + Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL] + Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP] + + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll] + Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF] + + Monitorname: [] + Defaultdatatype: [] +</pre><p> +You may notice, that this driver has quite a big number of +<span class="guilabel">Dependentfiles</span> (I know worse cases however). Also, +strangely, the <span class="guilabel">Driver File</span> is here tagged as +<span class="guilabel">Driver Path</span>.... oh, well. Here we don't have yet +support for the so-called <span class="application">WIN40</span> architecture +installed. This name is used by Microsoft for the Win95/98/ME platforms. +If we want to support these, we need to install the Win95/98/ME driver +files in addition to those for <span class="application">W32X86</span> +(i.e. the WinNT72000/XP clients) onto a Windows PC. This PC +can also host the Win9x drivers, even if itself runs on Windows NT, +2000 or XP. +</p><p> +Since the <i class="parameter"><tt>[print$]</tt></i> share is usually accessible +through the <span class="guiicon">Network Neighbourhood</span>, you can also use the UNC notation +from Windows Explorer to poke at it. The Win9x driver files will end +up in subdirectory "0" of the "WIN40" directory. The full path to +access them will be +<tt class="filename">\\WINDOWSHOST\print$\WIN40\0\</tt>. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> more recent drivers on Windows 2000 and Windows XP are +installed into the "3" subdirectory instead of the "2". The version 2 +of drivers, as used in Windows NT, were running in Kernel Mode. +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="id2919003"></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 +from the very PC and the same <i class="parameter"><tt>[print$]</tt></i> share +which we investigated in our last step to identify the files? We can +use <b class="command">smbclient</b> to do this. We will use the paths and +names which were leaked to us by <b class="command">getdriver</b>. The +listing is edited to include linebreaks for readability: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \ + -c 'cd W32X86/2;mget HD*_de.* \ + hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL'</tt></b> +added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 +Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) +Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] +<tt class="prompt">Get file Hddm91c1_de.ABD? </tt><b class="userinput"><tt>n</tt></b> +<tt class="prompt">Get file Hddm91c1_de.def? </tt><b class="userinput"><tt>y</tt></b> +getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def +<tt class="prompt">Get file Hddm91c1_de.DLL? </tt><b class="userinput"><tt>y</tt></b> +getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL +[...] + +</pre><p> +After this command is complete, the files are in our current local +directory. You probably have noticed that this time we passed several +commands to the <tt class="option">-c</tt> parameter, separated by semi-colons. This +effects that all commands are executed in sequence on the remote +Windows server before smbclient exits again. +</p><p> +Don't forget to repeat the procedure for the <span class="application">WIN40</span> +architecture should you need to support Win95/98/XP clients. Remember, the +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="id2919153"></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 +. You also have created subdirectories +for the different Windows client types you want to support. Supposing +your <i class="parameter"><tt>[print$]</tt></i> share maps to the UNIX path +<tt class="filename">/etc/samba/drivers/</tt>, your driver files should now +go here: +</p><div class="itemizedlist"><ul type="disc"><li><p>for all Windows NT, 2000 and XP clients into +<tt class="filename">/etc/samba/drivers/W32X86/</tt> <span class="emphasis"><em>but +*not*(yet) into the "2" subdir</em></span>!</p></li><li><p>for all Windows 95, 98 and ME clients into +<tt class="filename">/etc/samba/drivers/WIN40/</tt> -- <span class="emphasis"><em>but *not* +(yet) into the "0" subdir</em></span>!</p></li></ul></div><p> +We again use smbclient to transfer the driver files across the +network. We specify the same files and paths as were leaked to us by +running <b class="command">getdriver</b> against the original +<span class="emphasis"><em>Windows</em></span> install. However, now we are going to +store the files into a <span class="emphasis"><em>Samba/UNIX</em></span> print server's +<i class="parameter"><tt>[print$]</tt></i> share... +</p><pre class="screen"> + <tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \ + 'cd W32X86; put HDNIS01_de.DLL; \ + put Hddm91c1_de.ppd; put HDNIS01U_de.DLL; \ + put HDNIS01U_de.HLP; put Hddm91c1_de.DLL; \ + put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL; \ + put Hddm91c1_de.dat; put Hddm91c1_de.dat; \ + put Hddm91c1_de.def; put Hddm91c1_de.hre; \ + put Hddm91c1_de.vnd; put Hddm91c1_de.hlp; \ + put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll; \ + put HDNIS01_de.NTF'</tt></b> +added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 +Got a positive name query response from 10.160.51.162 ( 10.160.51.162 ) +Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] +putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL +putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd +putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL +putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP +putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL +putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI +putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL +putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat +putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat +putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def +putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre +putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd +putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp +putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP +putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll +putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF +</pre><p> +Phewww -- that was a lot of typing! Most drivers are a lot smaller -- +many only having 3 generic PostScript driver files plus 1 PPD. Note, +that while we did retrieve the files from the "2" subdirectory of the +"W32X86" directory from the Windows box, we <span class="emphasis"><em>don't</em></span> +put them (for now) in this same subdirectory of the Samba box! This +re-location will automatically be done by the +<b class="command">adddriver</b> command which we will run shortly (and +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="id2919348"></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): +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \ + -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'</tt></b> + added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 +Got a positive name query response from 10.160.51.162 ( 10.160.51.162 ) +Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] + +Current directory is \\SAMBA-CUPS\print$\W32X86\ +. D 0 Sun May 4 03:56:35 2003 +.. D 0 Thu Apr 10 23:47:40 2003 +2 D 0 Sun May 4 03:56:18 2003 +HDNIS01Aux.dll A 15356 Sun May 4 03:58:59 2003 +Hddm91c1KMMin.DLL A 46966 Sun May 4 03:58:59 2003 +HDNIS01_de.DLL A 434400 Sun May 4 03:58:59 2003 +HDNIS01_de.NTF A 790404 Sun May 4 03:56:35 2003 +Hddm91c1_de.DLL A 876544 Sun May 4 03:58:59 2003 +Hddm91c1_de.INI A 101 Sun May 4 03:58:59 2003 +Hddm91c1_de.dat A 5044 Sun May 4 03:58:59 2003 +Hddm91c1_de.def A 428 Sun May 4 03:58:59 2003 +Hddm91c1_de.hlp A 37699 Sun May 4 03:58:59 2003 +Hddm91c1_de.hre A 323584 Sun May 4 03:58:59 2003 +Hddm91c1_de.ppd A 26373 Sun May 4 03:58:59 2003 +Hddm91c1_de.vnd A 45056 Sun May 4 03:58:59 2003 +HDNIS01U_de.DLL A 165888 Sun May 4 03:58:59 2003 +HDNIS01U_de.HLP A 19770 Sun May 4 03:58:59 2003 +Hddm91c1_de_reg.HLP A 228417 Sun May 4 03:58:59 2003 + 40976 blocks of size 262144. 709 blocks available + +Current directory is \\SAMBA-CUPS\print$\W32X86\2\ +. D 0 Sun May 4 03:56:18 2003 +.. D 0 Sun May 4 03:56:35 2003 +ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003 +laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003 +ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003 +ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003 +PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003 + 40976 blocks of size 262144. 709 blocks available +</pre><p> +Notice that there are already driver files present in the +<tt class="filename">2</tt> subdir (probably from a previous +installation). Once the files for the new driver are there too, you +are still a few steps away from being able to use them on the +clients. The only thing you could do *now* is to retrieve them from a +client just like you retrieve ordinary files from a file share, by +opening print$ in Windows Explorer. But that wouldn't install them per +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="id2919464"></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 +is done by the <b class="command">adddriver</b> command. It will +prompt Samba to register the driver files into its internal TDB +database files. The following command and its output has been edited, +again, for readability: +</p><pre class="screen"> + <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \ +"dm9110:HDNIS01_de.DLL: \ +Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \ + NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ + Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ + Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ + HDNIS01Aux.dll,HDNIS01_de.NTF, \ + Hddm91c1_de_reg.HLP' SAMBA-CUPS</tt></b> + +cmd = adddriver "Windows NT x86" \ +"dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL: \ + HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ + Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ + Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ + HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP" + +Printer Driver dm9110 successfully installed. + +</pre><p> +After this step the driver should be recognized by Samba on the print +server. You need to be very careful when typing the command. Don't +exchange the order of the fields. Some changes would lead to a +<tt class="computeroutput">NT_STATUS_UNSUCCESSFUL</tt> error +message. These become obvious. Other changes might install the driver +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="id2919577"></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. +Another one is the fact, that our files have been moved by the +<b class="command">adddriver</b> command into the <tt class="filename">2</tt> +subdirectory. You can check this again with +<b class="command">smbclient</b>: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -Uroot%xx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'</tt></b> + added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0 + Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] + + Current directory is \\SAMBA-CUPS\print$\W32X86\ + . D 0 Sun May 4 04:32:48 2003 + .. D 0 Thu Apr 10 23:47:40 2003 + 2 D 0 Sun May 4 04:32:48 2003 + 40976 blocks of size 262144. 731 blocks available + + Current directory is \\SAMBA-CUPS\print$\W32X86\2\ + . D 0 Sun May 4 04:32:48 2003 + .. D 0 Sun May 4 04:32:48 2003 + DigiMaster.PPD A 148336 Thu Apr 24 01:07:00 2003 + ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003 + laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003 + ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003 + ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003 + PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003 + HDNIS01Aux.dll A 15356 Sun May 4 04:32:18 2003 + Hddm91c1KMMin.DLL A 46966 Sun May 4 04:32:18 2003 + HDNIS01_de.DLL A 434400 Sun May 4 04:32:18 2003 + HDNIS01_de.NTF A 790404 Sun May 4 04:32:18 2003 + Hddm91c1_de.DLL A 876544 Sun May 4 04:32:18 2003 + Hddm91c1_de.INI A 101 Sun May 4 04:32:18 2003 + Hddm91c1_de.dat A 5044 Sun May 4 04:32:18 2003 + Hddm91c1_de.def A 428 Sun May 4 04:32:18 2003 + Hddm91c1_de.hlp A 37699 Sun May 4 04:32:18 2003 + Hddm91c1_de.hre A 323584 Sun May 4 04:32:18 2003 + Hddm91c1_de.ppd A 26373 Sun May 4 04:32:18 2003 + Hddm91c1_de.vnd A 45056 Sun May 4 04:32:18 2003 + HDNIS01U_de.DLL A 165888 Sun May 4 04:32:18 2003 + HDNIS01U_de.HLP A 19770 Sun May 4 04:32:18 2003 + Hddm91c1_de_reg.HLP A 228417 Sun May 4 04:32:18 2003 + 40976 blocks of size 262144. 731 blocks available + +</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="id2919746"></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 +<span class="emphasis"><em>printer</em></span>. We may check the driver status of the +files by at least three methods: +</p><div class="itemizedlist"><ul type="disc"><li><p>from any Windows client browse Network Neighbourhood, +find the Samba host and open the Samba <span class="guiicon">Printers and +Faxes</span> folder. Select any printer icon, right-click and +select the printer <span class="guimenuitem">Properties</span>. Click on the +<span class="guilabel">Advanced</span> tab. Here is a field indicating the +driver for that printer. A drop down menu allows you to change that +driver (be careful to not do this unwittingly.). You can use this +list to view all drivers know to Samba. Your new one should be amongst +them. (Each type of client will only see his own architecture's +list. If you don't have every driver installed for each platform, the +list will differ if you look at it from Windows95/98/ME or +WindowsNT/2000/XP.)</p></li><li><p>from a Windows 2000 or XP client (not WinNT) browse +<span class="guiicon">Network Neighbourhood</span>, search for the Samba +server and open the server's <span class="guiicon">Printers</span> folder, +right-click the white background (with no printer highlighted). Select +<span class="guimenuitem">Server Properties</span>. On the +<span class="guilabel">Drivers</span> tab you will see the new driver listed +now. This view enables you to also inspect the list of files belonging +to that driver<span class="emphasis"><em> (this doesn't work on Windows NT, but only on +Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" +tab).</em></span>. An alternative, much quicker method for Windows +2000/XP to start this dialog is by typing into a DOS box (you must of +course adapt the name to your Samba server instead of <i class="replaceable"><tt>SAMBA-CUPS</tt></i>): +</p><p><b class="userinput"><tt> rundll32 printui.dll,PrintUIEntry /s /t2 /n\\<i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b></p></li><li><p>from a UNIX prompt run this command (or a variant +thereof), where <i class="replaceable"><tt>SAMBA-CUPS</tt></i> is the name of the Samba +host and "xxxx" represents the actual Samba password assigned to root: +</p><p><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'enumdrivers' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b></p><p> +You will see a listing of all drivers Samba knows about. Your new one +should be amongst them. But it is only listed under the <i class="parameter"><tt>[Windows NT +x86]</tt></i> heading, not under <i class="parameter"><tt>[Windows 4.0]</tt></i>, +since we didn't install that part. Or did *you*? -- You will see a listing of +all drivers Samba knows about. Your new one should be amongst them. In our +example it is named <span class="emphasis"><em>dm9110</em></span>. Note that the 3rd column +shows the other installed drivers twice, for each supported architecture one +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="id2919954"></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: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx \ + -c 'adddriver "Windows NT x86" \ + "myphantasydrivername:HDNIS01_de.DLL: \ + Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \ + NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ + Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ + Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ + HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS + </tt></b> + + cmd = adddriver "Windows NT x86" + "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\ + HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ + Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ + Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ + HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP" + + Printer Driver myphantasydrivername successfully installed. + +</pre><p> +You will also be able to bind that driver to any print queue (however, +you are responsible yourself that you associate drivers to queues +which make sense to the target printer). Note, that you can't run the +<b class="command">rpcclient</b> <b class="command">adddriver</b> command +repeatedly. Each run "consumes" the files you had put into the +<i class="parameter"><tt>[print$]</tt></i> share by moving them 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="id2920088"></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 +store this info in its "memory", the TDB files. The <b class="command">rpcclient +setdriver</b> command achieves exactly this: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'setdriver dm9110 myphantasydrivername' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b> + cmd = setdriver dm9110 myphantasydrivername + Successfully set dm9110 to driver myphantasydrivername. +</pre><p> +Ahhhhh -- no, I didn't want to do that. Repeat, this time with the +name I intended: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'setdriver dm9110 dm9110' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b> + cmd = setdriver dm9110 dm9110 + Successfully set dm9110 to driver dm9110. +</pre><p> +The syntax of the command is <b class="userinput"><tt>rpcclient +-U'root%<i class="replaceable"><tt>sambapassword</tt></i>' -c 'setdriver +"<i class="replaceable"><tt>printername</tt></i>" +"<i class="replaceable"><tt>drivername</tt></i>' +<i class="replaceable"><tt>SAMBA-Hostname</tt></i></tt></b> . -- +Now we have done *most* of the work. But not yet all.... +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +the <b class="command">setdriver</b> command will only succeed if the printer is +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="id2920241"></a>Client Driver Install Procedure</h2></div></div><div></div></div><p> +A famous philosopher said once: “<span class="quote">The Proof of the Pudding lies +in the Eating</span>”. 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="id2920260"></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 +attention. What follows is a description for the recommended first +procedure. You work now from a client workstation. First you should +guarantee that your connection is not unwittingly mapped to +<span class="emphasis"><em>bad user</em></span> "nobody". In a DOS box type: +</p><p><b class="userinput"><tt>net use \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\print$ /user:root</tt></b></p><p> +Replace root, if needed, by another valid +<i class="replaceable"><tt>printer admin</tt></i> user as given in the definition. +Should you already be connected as a different user, you'll get an error +message. There is no easy way to get rid of that connection, because +Windows doesn't seem to know a concept of "logging off" from a share +connection (don't confuse this with logging off from the local +workstation; that is a different matter). You can try to close +<span class="emphasis"><em>all</em></span> Windows file explorer and Internet Explorer +windows. As a last resort, you may have to reboot. Make sure there is +no automatic re-connection set up. It may be easier to go to a +different workstation and try from there. After you have made sure you +are connected as a printer admin user (you can check this with the +<b class="command">smbstatus</b> command on Samba) do this from the +Windows workstation: +</p><div class="itemizedlist"><ul type="disc"><li><p>Open <span class="guiicon">Network +Neighbourhood</span></p></li><li><p>Browse to Samba server</p></li><li><p>Open its <span class="guiicon">Printers and +Faxes</span> folder</p></li><li><p>Highlight and right-click the printer</p></li><li><p>Select <span class="guimenuitem">Connect...</span> (for WinNT4/2K +it is possibly <span class="guimenuitem">Install...</span>)</p></li></ul></div><p> +A new printer (named <i class="replaceable"><tt>printername</tt></i> on +samba-server) should now have appeared in your +<span class="emphasis"><em>local</em></span> Printer folder (check <span class="guimenu">Start</span> -- +<span class="guimenuitem">Settings</span> -- <span class="guimenuitem">Control Panel</span> +-- <span class="guiicon">Printers and Faxes</span>). +</p><p> +Most likely you are now tempted to try and print a test page. After +all, you now can open the printer properties and on the "General" tab, +there is a button offering to do just that. But chances are that you +get an error message saying <span class="errorname">Unable to print Test +Page</span>. The reason might be that there is not yet a +valid Device Mode set for the driver, or that the "Printer Driver +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="id2920462"></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 +the driver for the printer (defining things like paper size, +orientation and duplex settings), and</p></li><li><p>a complete set of +<span class="emphasis"><em>Printer Driver Data</em></span> generated by the +driver.</p></li></ul></div><p> +If either one of these is incomplete, the clients can produce less +than optimal output at best. In the worst cases, unreadable garbage or +nothing at all comes from the printer or they produce a harvest of +error messages when attempting to print. Samba stores the named values +and all printing related info in its internal TDB database files +<tt class="filename">(ntprinters.tdb</tt>, +<tt class="filename">ntdrivers.tdb</tt>, <tt class="filename">printing.tdb</tt> +and <tt class="filename">ntforms.tdb</tt>). +</p><p> +What do these two words stand for? Basically, the Device Mode and the +set of Printer Driver Data is a collection of settings for all print +queue properties, initialized in a sensible way. Device Modes and +Printer Driver Data should initially be set on the print server (that is +here: the Samba host) to healthy values so that the clients can start +to use them immediately. How do we set these initial healthy values? +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="id2920558"></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 +not a valid setting for clients to use). Fortunately, most drivers +generate themselves the Printer Driver Data that is needed, when they +are uploaded to the <i class="parameter"><tt>[print$]</tt></i> share with the +help of the APW or rpcclient. +</p><p> +The generation and setting of a first valid Device Mode however +requires some "tickling" from a client, to set it on the Samba +server. The easiest means of doing so is to simply change the page +orientation on the server's printer. This "executes" enough of the +printer driver program on the client for the desired effect to happen, +and feeds back the new Device Mode to our Samba server. You can use the +native Windows NT/2K/XP printer properties page from a Window client +for this: +</p><div class="itemizedlist"><ul type="disc"><li><p>Browse the <span class="guiicon">Network Neighbourhood</span></p></li><li><p>Find the Samba server</p></li><li><p>Open the Samba server's <span class="guiicon">Printers and + Faxes</span> folder</p></li><li><p>Highlight the shared printer in question</p></li><li><p>Right-click the printer (you may already be here, if you +followed the last section's description)</p></li><li><p>At the bottom of the context menu select +<span class="guimenu">Properties....</span> (if the menu still offers the +<span class="guimenuitem">Connect...</span> entry +further above, you need to click that one first to achieve the driver +installation as shown in the last section)</p></li><li><p>Go to the <span class="guilabel">Advanced</span> tab; click on +<span class="guibutton">Printing Defaults...</span></p></li><li><p>Change the "Portrait" page setting to "Landscape" (and +back)</p></li><li><p>(Oh, and make sure to <span class="emphasis"><em>apply</em></span> +changes between swapping the page orientation to cause the change to +actually take effect...).</p></li><li><p>While you're at it, you may optionally also want to +set the desired printing defaults here, which then apply to all future +client driver installations on the remaining from now +on.</p></li></ul></div><p> +This procedure has executed the printer driver program on the client +platform and fed back the correct Device Mode to Samba, which now +stored it in its TDB files. Once the driver is installed on the +client, you can follow the analogous steps by accessing the +<span class="emphasis"><em>local</em></span> <span class="guiicon">Printers</span> folder too if you are +a Samba printer admin user. From now on printing should work as expected. +</p><p> +Samba also includes a service level parameter name <i class="parameter"><tt>default +devmode</tt></i> for generating a default Device Mode for a +printer. Some drivers will function well with Samba's default set of +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="id2920763"></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 +this completes (should be not more than a few seconds, but could also take +a minute, depending on network conditions), you should find the new printer in +your client workstation local <span class="guiicon">Printers and +Faxes</span> folder. +</p><p> +You can also open your local <span class="guiicon">Printers and Faxes</span> folder by +using this command on Windows 2000 and Windows XP Professional workstations: +</p><p><b class="userinput"><tt>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder +</tt></b></p><p> +or this command on Windows NT 4.0 workstations: +</p><p><b class="userinput"><tt> +rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2 +</tt></b></p><p> +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="id2920857"></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="id2920879"></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 +further client installations are as you want them</p></li></ul></div><p> +Do this by changing the orientation to landscape, click +<span class="emphasis"><em>Apply</em></span>, and then change it back again. Then modify +the other settings (for example, you don't want the default media size +set to <span class="emphasis"><em>Letter</em></span>, when you are all using +<span class="emphasis"><em>A4</em></span>, right? You may want to set the printer for +<span class="emphasis"><em>duplex</em></span> as the default; etc.). +</p><p> +To connect as root to a Samba printer, try this command from a Windows +2K/XP DOS box command prompt: +</p><pre class="screen"> +<tt class="prompt">C:\> </tt><b class="userinput"><tt>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n + \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printername</tt></i>"</tt></b> +</pre><p> +</p><p> +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="id2921000"></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="id2921029"></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 +onto your first client machine now. But wait... let's make you +acquainted first with a few tips and tricks you may find useful. For +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 “<span class="quote">We need to set the paper +size for each job from Letter to A4 and it won't store it!</span>”) +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921063"></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 +fault. The confusing thing is this: in the multi-tabbed dialog that pops +up when you right-click the printer name and select +<span class="guimenuitem">Properties...</span>, you can arrive at two identically +looking dialogs, each claiming that they help you to set printer options, +in three different ways. Here is the definite answer to the "Samba +Default Driver Setting FAQ": +</p><p><b>“<span class="quote">I can't set and save default print options +for all users on Win2K/XP! Why not?</span>” </b> +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 +<span class="emphasis"><em>does</em></span> what you intend. +<span class="emphasis"><em>Important:</em></span> you need to be Administrator or Print +Administrator to do this for all users. Here is how I reproduce it in +on XP Professional: + +</p><div class="orderedlist"><ol type="A"><li><p>The first "wrong" way: + +</p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guiicon">Printers</span> +folder.</p></li><li><p>Right-click on the printer +(<span class="emphasis"><em>remoteprinter on cupshost</em></span>) and +select in context menu <span class="guimenu">Printing +Preferences...</span></p></li><li><p>Look at this dialog closely and remember what it looks +like.</p></li></ol></div><p> +</p></li><li><p>The second "wrong" way: + +</p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guimenu">Printers</span> +folder.</p></li><li><p>Right-click on the printer (<span class="emphasis"><em>remoteprinter on +cupshost</em></span>) and select in the context menu +<span class="guimenuitem">Properties</span></p></li><li><p>Click on the <span class="guilabel">General</span> +tab</p></li><li><p>Click on the button <span class="guibutton">Printing +Preferences...</span></p></li><li><p>A new dialog opens. Keep this dialog open and go back +to the parent dialog.</p></li></ol></div><p> +</p></li><li><p>The third, the "correct" way: (should you do +this from the beginning, just carry out steps 1. and 2. from second +"way" above) + +</p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="guilabel">Advanced</span> +tab. (Hmmm... if everything is "Grayed Out", then you are not logged +in as a user with enough privileges).</p></li><li><p>Click on the <span class="guibutton">Printing +Defaults...</span> button.</p></li><li><p>On any of the two new tabs, click on the +<span class="guilabel">Advanced...</span> button.</p></li><li><p>A new dialog opens. Compare this one to the other, +identical looking one from "B.5" or A.3".</p></li></ol></div><p> +</p></li></ol></div><p> + +Do you see any difference in the two settings dialogs? I don't +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="id2921360"></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> +or <span class="emphasis"><em>B.</em></span> above...). (This is new: Windows 2000 and +Windows XP allow <span class="emphasis"><em>per-user</em></span> default settings and +the ones the administrator gives them, before they set up their own). +The "parents" of the identically looking dialogs have a slight +difference in their window names: one is called +<tt class="computeroutput">Default Print Values for Printer Foo on Server +Bar"</tt> (which is the one you need) and the other is +called "<tt class="computeroutput">Print Settings for Printer Foo on Server +Bar</tt>". The last one is the one you arrive at when you +right-click on the printer and select <span class="guimenuitem">Print +Settings...</span>. This is the one what you were +taught to use back in the days of Windows NT! So it is only natural to +try the same way with Win2k or WinXP. You wouldn't dream +that there is now a different "clicking path" to arrive at an +identically looking, but functionally different dialog to set defaults +for all users! +</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>Try (on Win2000 and WinXP) to run this command (as a user +with the right privileges): +</p><p><b class="userinput"><tt> +rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printersharename</tt></i> +</tt></b></p><p> +to see the tab with the <span class="guilabel">Printing Defaults...</span> +button (the one you need). Also run this command: +</p><p><b class="userinput"><tt> +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> +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="id2921530"></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 +don't want to acquire RSS pains from such the printer installation +clicking orgy alone, you need to think about a non-interactive script. +</p><p> +If more than one printer is using the same driver, the +<b class="command">rpcclient setdriver</b> command can be used to set the +driver associated with an installed queue. If the driver is uploaded +to <i class="parameter"><tt>[print$]</tt></i> once and registered with the +printing TDBs, it can be used by multiple print queues. In this case +you just need to repeat the <b class="command">setprinter</b> subcommand +of <b class="command">rpcclient</b> for every queue (without the need to +conduct the <b class="command">adddriver</b> again and again). The +following is an example of how this could be accomplished: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumdrivers'</tt></b> + cmd = enumdrivers + + [Windows NT x86] + Printer Driver Info 1: + Driver Name: [infotec IS 2075 PCL 6] + + Printer Driver Info 1: + Driver Name: [DANKA InfoStream] + + Printer Driver Info 1: + Driver Name: [Heidelberg Digimaster 9110 (PS)] + + Printer Driver Info 1: + Driver Name: [dm9110] + + Printer Driver Info 1: + Driver Name: [myphantasydrivername] + + [....] +</pre><p> + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> + cmd = enumprinters + flags:[0x800000] + name:[\\SAMBA-CUPS\dm9110] + description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart] + comment:[110 ppm HiVolume DANKA Stuttgart] + [....] +</pre><p> + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c \ + 'setdriver <i class="replaceable"><tt>dm9110</tt></i> "<i class="replaceable"><tt>Heidelberg Digimaster 9110 (PS)</tt></i>"'</tt></b> + cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD) + Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS). +</pre><p> + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> + cmd = enumprinters + flags:[0x800000] + name:[\\SAMBA-CUPS\dm9110] + description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\ + 110ppm HiVolume DANKA Stuttgart] + comment:[110ppm HiVolume DANKA Stuttgart] + [....] +</pre><p> + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'setdriver <i class="replaceable"><tt>dm9110</tt></i> <i class="replaceable"><tt>myphantasydrivername</tt></i>'</tt></b> + cmd = setdriver dm9110 myphantasydrivername + Successfully set dm9110 to myphantasydrivername. +</pre><p> + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> + cmd = enumprinters + flags:[0x800000] + name:[\\SAMBA-CUPS\dm9110] + description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,\ + 110ppm HiVolume DANKA Stuttgart] + comment:[110ppm HiVolume DANKA Stuttgart] + [....] +</pre><p> +It may be not easy to recognize: but the first call to +<b class="command">enumprinters</b> showed the "dm9110" printer with an +empty string where the driver should have been listed (between the 2 +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="id2921841"></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 +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="id2921887"></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="id2921942"></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="id2922001"></a><i class="parameter"><tt>add printer command</tt></i>; +a corresponding <a class="indexterm" name="id2922017"></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="id2922045"></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>, +<tt class="filename">/etc/cups/printers.conf</tt> or other appropriate +files) and to if necessary. +</p><p> +When using the APW from a client, if the named printer share does not +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="id2922095"></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="id2922111"></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="id2922136"></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 +perhaps reboot. +</p><div class="itemizedlist"><ul type="disc"><li><p>The <b class="command">net use \\SAMBA-SERVER\sharename +/user:root</b> gives you an error message: <tt class="computeroutput">Multiple +connections to a server or a shared resource by the same user +utilizing the several user names are not allowed. Disconnect all +previous connections to the server, resp. the shared resource, and try +again.</tt></p></li><li><p>Every attempt to "connect a network drive" to +<tt class="filename">\\SAMBASERVER\\print$</tt> to z: is countered by the +pertinacious message. <tt class="computeroutput">This network folder is currently +connected under different credentials (username and password). +Disconnect first any existing connection to this network share in +order to connect again under a different username and +password</tt>.</p></li></ul></div><p> +So you close all connections. You try again. You get the same +message. You check from the Samba side, using +<b class="command">smbstatus</b>. Yes, there are some more +connections. You kill them all. The client still gives you the same +error message. You watch the smbd.log file on a very high debug level +and try re-connect. Same error message, but not a single line in the +log. You start to wonder if there was a connection attempt at all. You +run ethereal and tcpdump while you try to connect. Result: not a +single byte goes on the wire. Windows still gives the error +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="id2922236"></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 +<tt class="filename">[print$]/WIN/0/</tt>), driver version "2" (Kernel Mode +driver for WinNT, going into <tt class="filename">[print$]/W32X86/2/</tt> +<span class="emphasis"><em>may</em></span> be used on Win2K/XP too), and driver version +"3" (non-Kernel Mode driver going into +<tt class="filename">[print$]/W32X86/3/</tt> <span class="emphasis"><em>can not</em></span> +be used on WinNT). Very often these different driver versions contain +files carrying the same name; but still the files are very different! +Also, if you look at them from the Windows Explorer (they reside in +<tt class="filename">%WINDOWS%\system32\spool\drivers\W32X86\</tt>) you +will probably see names in capital letters, while an "enumdrivers" +command from Samba would show mixed or lower case letters. So it is +easy to confuse them. If you install them manually using +<b class="command">rpcclient</b> and subcommands, you may even succeed +without an error message. Only later, when you try install on a +client, you will encounter error messages like <tt class="computeroutput">This +server has no appropriate driver for the printer</tt>. +</p><p> +Here is an example. You are invited to look very closely at the +various files, compare their names and their spelling, and discover +the differences in the composition of the version-2 and -3 sets +Note: the version-0 set contained 40 (!) +<i class="parameter"><tt>Dependentfiles</tt></i>, so I left it out for space +reasons: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U 'Administrator%<i class="replaceable"><tt>secret</tt></i>' -c 'enumdrivers 3' 10.160.50.8 </tt></b> + + Printer Driver Info 3: + Version: [3] + Driver Name: [Canon iR8500 PS3] + Architecture: [Windows NT x86] + Driver Path: [\\10.160.50.8\print$\W32X86\3\cns3g.dll] + Datafile: [\\10.160.50.8\print$\W32X86\3\iR8500sg.xpd] + Configfile: [\\10.160.50.8\print$\W32X86\3\cns3gui.dll] + Helpfile: [\\10.160.50.8\print$\W32X86\3\cns3g.hlp] + + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aucplmNT.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\ucs32p.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\tnl32.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussdrv.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cnspdc.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussapi.dat] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3407.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\CnS3G.cnt] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBAPI.DLL] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBIPC.DLL] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcview.exe] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcdspl.exe] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcedit.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm.exe] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcspl.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cfine32.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcr407.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\Cpcqm407.hlp] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm407.cnt] + Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3ggr.dll] + + Monitorname: [] + Defaultdatatype: [] + + Printer Driver Info 3: + Version: [2] + Driver Name: [Canon iR5000-6000 PS3] + Architecture: [Windows NT x86] + Driver Path: [\\10.160.50.8\print$\W32X86\2\cns3g.dll] + Datafile: [\\10.160.50.8\print$\W32X86\2\IR5000sg.xpd] + Configfile: [\\10.160.50.8\print$\W32X86\2\cns3gui.dll] + Helpfile: [\\10.160.50.8\print$\W32X86\2\cns3g.hlp] + + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\AUCPLMNT.DLL] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussdrv.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cnspdc.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussapi.dat] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3407.dll] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\CnS3G.cnt] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBAPI.DLL] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBIPC.DLL] + Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3gum.dll] + + Monitorname: [CPCA Language Monitor2] + Defaultdatatype: [] + +</pre><p> +If we write the "version 2" files and the "version 3" files +into different text files and compare the result, we see this +picture: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>sdiff 2-files 3-files</tt></b> + + + cns3g.dll cns3g.dll + iR8500sg.xpd iR8500sg.xpd + cns3gui.dll cns3gui.dll + cns3g.hlp cns3g.hlp + AUCPLMNT.DLL | aucplmNT.dll + > ucs32p.dll + > tnl32.dll + aussdrv.dll aussdrv.dll + cnspdc.dll cnspdc.dll + aussapi.dat aussapi.dat + cns3407.dll cns3407.dll + CnS3G.cnt CnS3G.cnt + NBAPI.DLL NBAPI.DLL + NBIPC.DLL NBIPC.DLL + cns3gum.dll | cpcview.exe + > cpcdspl.exe + > cpcqm.exe + > cpcspl.dll + > cfine32.dll + > cpcr407.dll + > Cpcqm407.hlp + > cpcqm407.cnt + > cns3ggr.dll + +</pre><p> +Don't be fooled though! Driver files for each version with identical +names may be different in their content, as you can see from this size +comparison: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>for i in cns3g.hlp cns3gui.dll cns3g.dll; do \ + smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \ + -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i"; \ + done</tt></b> + + CNS3G.HLP A 122981 Thu May 30 02:31:00 2002 + CNS3G.HLP A 99948 Thu May 30 02:31:00 2002 + + CNS3GUI.DLL A 1805824 Thu May 30 02:31:00 2002 + CNS3GUI.DLL A 1785344 Thu May 30 02:31:00 2002 + + CNS3G.DLL A 1145088 Thu May 30 02:31:00 2002 + CNS3G.DLL A 15872 Thu May 30 02:31:00 2002 + +</pre><p> +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="id2922594"></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 +must also support the concept of ports associated with a printer. By +default, only one printer port, named "Samba Printer Port", exists on +a system. Samba does not really need such a "port" in order to print; +it rather is a requirement of Windows clients. They insist on being +told about an available port when they request this info, otherwise +they throw an error message at you. So Samba fakes the port +information to keep the Windows clients happy. +</p><p> +Note that Samba does not support the concept of "Printer Pooling" +internally either. Printer Pooling assigns a logical printer to +multiple ports as a form of load balancing or fail over. +</p><p> +If you require that multiple ports be defined for some reason or +another (“<span class="quote">My users and my Boss should not know that they are +working with Samba</span>”), possesses a +<a class="indexterm" name="id2922668"></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="id2922687"></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="id2922712"></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 +at <a href="http://imprints.sourceforge.net/" target="_top">http://imprints.sourceforge.net/</a> +as well as the documentation included with the imprints source +distribution. This section will only provide a brief introduction +to the features of Imprints. +</p><p><b>Attention! Maintainer required. </b> +Unfortunately, the Imprints toolset is no longer maintained. As of +December, 2000, the project is in need of a new maintainer. The most +important skill to have is decent perl coding and an interest in +MS-RPC based printing using Samba. If you wish to volunteer, please +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="id2922768"></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="id2922810"></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="id2922828"></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 +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="id2922853"></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. +</p><p> +The Imprints installation client comes in two forms. +</p><div class="itemizedlist"><ul type="disc"><li><p>a set of command line Perl scripts</p></li><li><p>a GTK+ based graphical interface to the command line Perl +scripts</p></li></ul></div><p> +The installation client (in both forms) provides a means of querying +the Imprints database server for a matching list of known printer +model names as well as a means to download and install the drivers on +remote Samba and Windows NT print servers. +</p><p> +The basic installation process is in four steps and perl code is +wrapped around smbclient and rpcclient +</p><div class="itemizedlist"><ul type="disc"><li><p> + foreach (supported architecture for a given driver) + </p><div class="orderedlist"><ol type="1"><li><p>rpcclient: Get the appropriate upload directory on the remote server</p></li><li><p>smbclient: Upload the driver files</p></li><li><p>rpcclient: Issues an AddPrinterDriver() MS-RPC</p></li></ol></div><p> + </p></li><li><p>rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer</p></li></ul></div><p> +One of the problems encountered when implementing the Imprints tool +set was the name space issues between various supported client +architectures. For example, Windows NT includes a driver named "Apple +LaserWriter II NTX v51.8" and Windows 95 calls its version of this +driver "Apple LaserWriter II NTX" +</p><p> +The problem is how to know what client drivers have been uploaded for +a printer. An astute reader will remember that the Windows NT Printer +Properties dialog only includes space for one printer driver name. A +quick look in the Windows NT 4.0 system registry at +</p><p><tt class="filename"> + HKLM\System\CurrentControlSet\Control\Print\Environment +</tt></p><p> +will reveal that Windows NT always uses the NT driver name. This is +ok as Windows NT always requires that at least the Windows NT version +of the printer driver is present. However, Samba does not have the +requirement internally. Therefore, how can you use the NT driver name +if is has not already been installed? +</p><p> +The way of sidestepping this limitation is to require that all +Imprints printer driver packages include both the Intel Windows NT and +95/98 printer drivers and that NT driver is installed first. +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2923008"></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> +). It also applies to Windows XP Professional clients. +</p><p> +The ideas sketched out below are inspired by this article. It +describes a commandline method which can be applied to install +network and local printers and their drivers. This is most useful +if integrated in Logon Scripts. You can see what options are +available by typing in a command prompt ("DOS box") this: +</p><p><b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /?</tt></b></p><p> +A window pops up which shows you all of the commandline switches +available. An extensive list of examples is also provided. This is +only for Win 2k/XP. It doesn't work on WinNT. WinNT has probably some +other tools in the respective Resource Kit. Here is a suggestion about +what a client logon script might contain, with a short explanation of +what the lines actually do (it works if 2k/XP Windows clients access +printers via Samba, but works for Windows-based print servers too): +</p><pre class="screen"> +<b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q</tt></b> +<b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"</tt></b> +<b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"</tt></b> +</pre><p> +Here is a list of the used commandline parameters: +</p><div class="variablelist"><dl><dt><span class="term">/dn</span></dt><dd><p>deletes a network printer</p></dd><dt><span class="term">/q</span></dt><dd><p>quiet modus</p></dd><dt><span class="term">/n</span></dt><dd><p>names a printer</p></dd><dt><span class="term">/in</span></dt><dd><p>adds a network printer connection</p></dd><dt><span class="term">/y</span></dt><dd><p>sets printer as default printer</p></dd></dl></div><div class="itemizedlist"><ul type="disc"><li><p>Line 1 deletes a possibly existing previous network +printer <span class="emphasis"><em>infotec2105-IPDS</em></span> (which had used native +Windows drivers with LPRng that were removed from the server which was +converted to CUPS). The <b class="command">/q</b> at the end eliminates +"Confirm" or error dialog boxes popping up. They should not be +presented to the user logging on.</p></li><li><p>Line 2 adds the new printer +<span class="emphasis"><em>infotec2105-PS</em></span> (which actually is same physical +device but is now run by the new CUPS printing system and associated +with the CUPS/Adobe PS drivers). The printer and its driver +<span class="emphasis"><em>must</em></span> have been added to Samba prior to the user +logging in (e.g. by a procedure as discussed earlier in this chapter, +or by running <b class="command">cupsaddsmb</b>). The driver is now +auto-downloaded to the client PC where the user is about to log +in.</p></li><li><p>Line 3 sets the default printer to this new network +printer (there might be several other printers installed with this +same method and some may be local as well -- so we decide for a +default printer). The default printer selection may of course be +different for different users.</p></li></ul></div><p> +Note that the second line only works if the printer +<span class="emphasis"><em>infotec2105-PS</em></span> has an already working print queue +on "sambacupsserver", and if the printer drivers have successfully been +uploaded (via <b class="command">APW</b> , +<b class="command">smbclient/rpcclient</b> or +<b class="command">cupsaddsmb</b>) into the +<i class="parameter"><tt>[print$]</tt></i> driver repository of Samba. Also, some +Samba versions prior to version 3.0 required a re-start of smbd after +the printer install and the driver upload, otherwise the script (or +any other client driver download) would fail. +</p><p> +Since there no easy way to test for the existence of an installed +network printer from the logon script, the suggestion is: don't bother +checking and just allow the deinstallation/reinstallation to occur +every time a user logs in; it's really quick anyway (1 to 2 seconds). +</p><p> +The additional benefits for this are: +</p><div class="itemizedlist"><ul type="disc"><li><p>It puts in place any printer default setup changes +automatically at every user logon.</p></li><li><p>It allows for "roaming" users' login into the domain from +different workstations.</p></li></ul></div><p> +Since network printers are installed per user this much simplifies the +process of keeping the installation up-to-date. The extra few seconds +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="id2923342"></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 +user to fill in several fields (such as printer name, driver to be +used, comment, port monitor, etc.). These parameters are passed on to +Samba by the APW. If the addprinter command is designed in a way that +it can create a new printer (through writing correct printcap entries +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="id2923388"></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 +followed previous advice to stop using deprecated parameters in your +setup. For migrations from an existing 2.0.x setup, or if you +continued "Win9x-style" printing in your Samba 2.2 installations, it +is more of an effort. Please read the appropriate release notes and +the HOWTO Collection for 2.2. You can follow several paths. Here are +possible scenarios for migration: +</p><div class="itemizedlist"><ul type="disc"><li><p>You need to study and apply the new Windows NT printer +and driver support. Previously used parameters <i class="parameter"><tt>printer +driver file</tt></i>, <i class="parameter"><tt>printer driver</tt></i> and +<i class="parameter"><tt>printer driver location</tt></i> are no longer +supported.</p></li><li><p>If you want to take advantage of WinNT printer driver +support you also need to migrate the Win9x/ME drivers to the new +setup.</p></li><li><p>An existing <tt class="filename">printers.def</tt> file + (the one specified in the now removed parameter <i class="parameter"><tt>printer driver file</tt></i>) will work no longer with samba 3. In +3.0, smbd attempts to locate a Win9x/ME driver files for the printer +in <i class="parameter"><tt>[print$]</tt></i> and additional settings in the TDB +and only there; if it fails it will <span class="emphasis"><em>not</em></span> (as 2.2.x +used to do) drop down to using a <tt class="filename">printers.def</tt> +(and all associated parameters). The make_printerdef tool is removed +and there is no backwards compatibility for this.</p></li><li><p>You need to install a Windows 9x driver into the +<i class="parameter"><tt>[print$]</tt></i> share for a printer on your Samba +host. The driver files will be stored in the "WIN40/0" subdirectory of +<i class="parameter"><tt>[print$]</tt></i>, and some other settings and info go +into the printing-related TDBs.</p></li><li><p>If you want to migrate an existing +<tt class="filename">printers.def</tt> file into the new setup, the current +only solution is to use the Windows NT APW to install the NT drivers +and the 9x drivers. This can be scripted using smbclient and +rpcclient. See the Imprints installation client at: +</p><p> + <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="id2923561"></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="id2923575"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923582"></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 +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="id2923615"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="msdfs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="CUPS-printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 17. Hosting a Microsoft Distributed File System tree on Samba </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 19. CUPS Printing Support in Samba 3.0</td></tr></table></div></body></html> diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html new file mode 100644 index 0000000000..24ddc7c02c --- /dev/null +++ b/docs/htmldocs/problems.html @@ -0,0 +1,138 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 34. Analysing and solving samba 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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part V. Troubleshooting"><link rel="previous" href="diagnosis.html" title="Chapter 33. The Samba checklist"><link rel="next" href="bugreport.html" title="Chapter 35. Reporting Bugs"></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 34. Analysing and solving samba problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a> </td><th width="60%" align="center">Part V. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="bugreport.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></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="problems.html#id2959747">Diagnostics tools</a></dt><dd><dl><dt><a href="problems.html#id2959768">Debugging with Samba itself</a></dt><dt><a href="problems.html#id2959894">Tcpdump</a></dt><dt><a href="problems.html#id2959915">Ethereal</a></dt><dt><a href="problems.html#id2959968">The Windows Network Monitor</a></dt></dl></dd><dt><a href="problems.html#id2960285">Useful URLs</a></dt><dt><a href="problems.html#id2960326">Getting help from the mailing lists</a></dt><dt><a href="problems.html#id2960484">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="id2959747"></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="id2959768"></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="id2959799"></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> +Another helpful method of debugging is to compile samba using the +<b class="userinput"><tt>gcc -g </tt></b> flag. This will include debug +information in the binaries and allow you to attach gdb to the +running smbd / nmbd process. In order to attach gdb to an smbd +process for an NT workstation, first get the workstation to make the +connection. Pressing ctrl-alt-delete and going down to the domain box +is sufficient (at least, on the first time you join the domain) to +generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation +maintains an open connection, and therefore there will be an smbd +process running (assuming that you haven't set a really short smbd +idle timeout) So, in between pressing ctrl alt delete, and actually +typing in your password, you can attach gdb and continue. +</p><p> +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="id2959894"></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="id2959915"></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="id2959968"></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 +netmon that ships with SMS allows for dumping packets between any two +computers (i.e. placing the network interface in promiscuous mode). +The version on the NT Server install CD will only allow monitoring +of network traffic directed to the local NT box and broadcasts on the +local subnet. Be aware that Ethereal can read and write netmon +formatted files. +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2959989"></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 +Workstation 4.0. The process should be similar for other versions of +Windows NT / Netmon. You will need both the Microsoft Windows +NT Server 4.0 Install CD and the Workstation 4.0 Install CD. +</p><p> +Initially you will need to install <span class="application">Network Monitor Tools and Agent</span> +on the NT Server. To do this +</p><div class="itemizedlist"><ul type="disc"><li><p>Goto <span class="guibutton">Start</span> - <span class="guibutton">Settings</span> - <span class="guibutton">Control Panel</span> - + <span class="guibutton">Network</span> - <span class="guibutton">Services</span> - <span class="guibutton">Add</span> </p></li><li><p>Select the <span class="guilabel">Network Monitor Tools and Agent</span> and + click on <span class="guibutton">OK</span>.</p></li><li><p>Click <span class="guibutton">OK</span> on the Network Control Panel. + </p></li><li><p>Insert the Windows NT Server 4.0 install CD + when prompted.</p></li></ul></div><p> +At this point the Netmon files should exist in +<tt class="filename">%SYSTEMROOT%\System32\netmon\*.*</tt>. +Two subdirectories exist as well, <tt class="filename">parsers\</tt> +which contains the necessary DLL's for parsing the netmon packet +dump, and <tt class="filename">captures\</tt>. +</p><p> +In order to install the Netmon tools on an NT Workstation, you will +first need to install the 'Network Monitor Agent' from the Workstation +install CD. +</p><div class="itemizedlist"><ul type="disc"><li><p>Goto <span class="guibutton">Start</span> - <span class="guibutton">Settings</span> - <span class="guibutton">Control Panel</span> - + <span class="guibutton">Network</span> - <span class="guibutton">Services</span> - <span class="guibutton">Add</span></p></li><li><p>Select the <span class="guilabel">Network Monitor Agent</span> and click + on <span class="guibutton">OK</span>.</p></li><li><p>Click <span class="guibutton">OK</span> on the Network Control Panel. + </p></li><li><p>Insert the Windows NT Workstation 4.0 install + CD when prompted.</p></li></ul></div><p> +Now copy the files from the NT Server in <tt class="filename">%SYSTEMROOT%\System32\netmon\*.*</tt> +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="id2960258"></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="id2960285"></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="id2960326"></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>. +</p><p> +For questions relating to Samba TNG go to +<a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a> +It has been requested that you don't post questions about Samba-TNG to the +main stream Samba lists.</p><p> +If you post a message to one of the lists please observe the following guide lines : +</p><div class="itemizedlist"><ul type="disc"><li><p>Always remember that the developers are volunteers, they are +not paid and they never guarantee to produce a particular feature at +a particular time. Any time lines are 'best guess' and nothing more. +</p></li><li><p>Always mention what version of samba you are using and what +operating system its running under. You should probably list the +relevant sections of your <tt class="filename">smb.conf</tt> file, at least the options +in [global] that affect PDC support.</p></li><li><p>In addition to the version, if you obtained Samba via +CVS mention the date when you last checked it out.</p></li><li><p> Try and make your question clear and brief, lots of long, +convoluted questions get deleted before they are completely read ! +Don't post html encoded messages (if you can select colour or font +size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when +you are away, make sure its configured to not answer mailing lists. +</p></li><li><p> Don't cross post. Work out which is the best list to post to +and see what happens, i.e. don't post to both samba-ntdom and samba-technical. +Many people active on the lists subscribe to more +than one list and get annoyed to see the same message two or more times. +Often someone will see a message and thinking it would be better dealt +with on another, will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span> +log files written at a debug level set to as much as 20. +Please don't send the entire log but enough to give the context of the +error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( from the opening of +the pipe to the error ) you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email. +Consider pasting the relevant parts into the body of the message. The samba +mailing lists go to a huge number of people, do they all need a copy of your +smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960484"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bugreport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 33. The Samba checklist </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 35. Reporting Bugs</td></tr></table></div></body></html> diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index e9f1afb0ed..73caf547a2 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -1,392 +1,105 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="rpcclient.1"> - -<refmeta> - <refentrytitle>rpcclient</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>rpcclient</refname> - <refpurpose>tool for executing client side - MS-RPC functions</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">rpcclient</command> - <arg rep="norepeat" choice="opt">-A authfile</arg> - <arg rep="norepeat" choice="opt">-c <command string></arg> - <arg rep="norepeat" choice="opt">-d debuglevel</arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-l logfile</arg> - <arg rep="norepeat" choice="opt">-N</arg> - <arg rep="norepeat" choice="opt">-s <smb config file></arg> - <arg rep="norepeat" choice="opt">-U username[%password]</arg> - <arg rep="norepeat" choice="opt">-W workgroup</arg> - <arg rep="norepeat" choice="opt">-N</arg> - <arg rep="norepeat" choice="opt">-I destinationIP</arg> - <arg rep="norepeat" choice="req">server</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">rpcclient</command> is a utility initially developed +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>rpcclient</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="rpcclient.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>rpcclient — tool for executing client side + MS-RPC functions</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">rpcclient</tt> [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</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">rpcclient</b> is a utility initially developed to test MS-RPC functionality in Samba itself. It has undergone several stages of development and stability. Many system administrators have now written scripts around it to manage Windows NT clients from - their UNIX workstation. </para> -</refsect1> - - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>server</term> - <listitem><para>NetBIOS name of Server to which to connect. + 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 <indexterm><primary>name resolve order</primary></indexterm><parameter moreinfo="none">name resolve order</parameter> line from <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>-c|--command='command string'</term> - <listitem><para>execute semicolon separated commands (listed - below)) </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-I IP-address</term> - <listitem><para><replaceable>IP address</replaceable> is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation. </para> - - <para>Normally the client would attempt to locate a named + 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 + 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 "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 <parameter moreinfo="none">name resolve order</parameter> + mechanism described above in the <i class="parameter"><tt>name resolve order</tt></i> parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being - connected to will be ignored. </para> - - <para>There is no default for this parameter. If not supplied, + connected to will be ignored. </p><p>There is no default for this parameter. If not supplied, it will be determined automatically by the client as described - above. </para></listitem> - </varlistentry> - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + above. </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +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 +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. -</para></listitem> -</varlistentry> - - - -<varlistentry> -<term>-N</term> -<listitem><para>If specified, this parameter suppresses the normal +</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 -accessing a service that does not require a password. </para> - -<para>Unless a password is specified on the command line or +accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or this parameter is specified, the client will request a -password.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-k</term> -<listitem><para> +password.</p></dd><dt><span class="term">-k</span></dt><dd><p> Try to authenticate with kerberos. Only useful in an Active Directory environment. -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>-A|--authfile=filename</term> -<listitem><para>This option allows +</p></dd><dt><span class="term">-A|--authfile=filename</span></dt><dd><p>This option allows you to specify a file from which to read the username and password used in the connection. The format of the file is -</para> - -<para><programlisting format="linespecific"> +</p><pre class="programlisting"> username = <value> password = <value> domain = <value> -</programlisting></para> - -<para>Make certain that the permissions on the file restrict -access from unwanted users. </para></listitem> -</varlistentry> - -<varlistentry> -<term>-U|--user=username[%password]</term> -<listitem><para>Sets the SMB username or username and password. </para> - -<para>If %password is not specified, the user will be prompted. The -client will first check the <envar>USER</envar> environment variable, then the -<envar>LOGNAME</envar> variable and if either exists, the +</pre><p>Make certain that the permissions on the file restrict +access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The +client will first check the <tt class="envar">USER</tt> environment variable, then the +<tt class="envar">LOGNAME</tt> variable and if either exists, the string is uppercased. If these environmental variables are not -found, the username <constant>GUEST</constant> is used. </para> - -<para>A third option is to use a credentials file which +found, the username <tt class="constant">GUEST</tt> is used. </p><p>A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the -<parameter moreinfo="none">-A</parameter> for more details. </para> - -<para>Be cautious about including passwords in scripts. Also, on +<i class="parameter"><tt>-A</tt></i> for more details. </p><p>Be cautious about including passwords in scripts. Also, on many systems the command line of a running process may be seen -via the <command moreinfo="none">ps</command> command. To be safe always allow -<command moreinfo="none">rpcclient</command> to prompt for a password and type -it in directly. </para></listitem> -</varlistentry> - - - - -<varlistentry> -<term>-n <primary NetBIOS name></term> -<listitem><para>This option allows you to override +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 <primary NetBIOS name></span></dt><dd><p>This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the <indexterm><primary>netbios name</primary></indexterm><parameter moreinfo="none">netbios name</parameter> parameter in the <filename moreinfo="none">smb.conf</filename> file. +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. However, a command line setting will take precedence over settings in -<filename moreinfo="none">smb.conf</filename>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-i <scope></term> -<listitem><para>This specifies a NetBIOS scope that -<command moreinfo="none">nmblookup</command> will use to communicate with when +<tt class="filename">smb.conf</tt>.</p></dd><dt><span class="term">-i <scope></span></dt><dd><p>This specifies a NetBIOS scope that +<b class="command">nmblookup</b> will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -<emphasis>very</emphasis> rarely used, only set this parameter +<span class="emphasis"><em>very</em></span> rarely used, only set this parameter if you are the system administrator in charge of all the -NetBIOS systems you communicate with.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-W|--workgroup=domain</term> -<listitem><para>Set the SMB domain of the username. This +NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This overrides the default domain which is the domain defined in smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). </para></listitem> -</varlistentry> - -<varlistentry> -<term>-O socket options</term> -<listitem><para>TCP socket options to set on the client +SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client socket. See the socket options parameter in -the <filename moreinfo="none">smb.conf</filename> manual page for the list of valid -options. </para></listitem> -</varlistentry> - - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>COMMANDS</title> - - <refsect2> - <title>LSARPC</title> - - <variablelist> - <varlistentry><term>lsaquery</term><listitem><para>Query info policy</para></listitem></varlistentry> - - <varlistentry><term>lookupsids</term><listitem><para>Resolve a list +the <tt class="filename">smb.conf</tt> manual page for the list of valid +options. </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>COMMANDS</h2><div class="refsect2" lang="en"><h3>LSARPC</h3><div class="variablelist"><dl><dt><span class="term">lsaquery</span></dt><dd><p>Query info policy</p></dd><dt><span class="term">lookupsids</span></dt><dd><p>Resolve a list of SIDs to usernames. - </para></listitem></varlistentry> - - <varlistentry><term>lookupnames</term><listitem><para>Resolve a list + </p></dd><dt><span class="term">lookupnames</span></dt><dd><p>Resolve a list of usernames to SIDs. - </para></listitem></varlistentry> - - <varlistentry><term>enumtrusts</term><listitem><para>Enumerate trusted domains</para></listitem></varlistentry> - - <varlistentry><term>enumprivs</term><listitem><para>Enumerate privileges</para></listitem></varlistentry> - - <varlistentry><term>getdispname</term><listitem><para>Get the privilege name</para></listitem></varlistentry> - - <varlistentry><term>lsaenumsid</term><listitem><para>Enumerate the LSA SIDS</para></listitem></varlistentry> - - <varlistentry><term>lsaenumprivsaccount</term><listitem><para>Enumerate the privileges of an SID</para></listitem></varlistentry> - - <varlistentry><term>lsaenumacctrights</term><listitem><para>Enumerate the rights of an SID</para></listitem></varlistentry> - - <varlistentry><term>lsaenumacctwithright</term><listitem><para>Enumerate accounts with a right</para></listitem></varlistentry> - - <varlistentry><term>lsaaddacctrights</term><listitem><para>Add rights to an account</para></listitem></varlistentry> - - <varlistentry><term>lsaremoveacctrights</term><listitem><para>Remove rights from an account</para></listitem></varlistentry> - - <varlistentry><term>lsalookupprivvalue</term><listitem><para>Get a privilege value given its name</para></listitem></varlistentry> - - <varlistentry><term>lsaquerysecobj</term><listitem><para>Query LSA security object</para></listitem></varlistentry> - - </variablelist> - </refsect2> - - <refsect2> - <title>LSARPC-DS</title> - - <variablelist> - <varlistentry><term>dsroledominfo</term><listitem><para>Get Primary Domain Information</para></listitem></varlistentry> - </variablelist> - - <para> </para> - - <para><emphasis>DFS</emphasis></para> - <variablelist> - <varlistentry><term>dfsexist</term><listitem><para>Query DFS support</para></listitem></varlistentry> - <varlistentry><term>dfsadd</term><listitem><para>Add a DFS share</para></listitem></varlistentry> - <varlistentry><term>dfsremove</term><listitem><para>Remove a DFS share</para></listitem></varlistentry> - <varlistentry><term>dfsgetinfo</term><listitem><para>Query DFS share info</para></listitem></varlistentry> - <varlistentry><term>dfsenum</term><listitem><para>Enumerate dfs shares</para></listitem></varlistentry> - </variablelist> - - </refsect2> - - <refsect2> - <title>REG</title> - <variablelist> - <varlistentry><term>shutdown</term><listitem><para>Remote Shutdown</para></listitem></varlistentry> - <varlistentry><term>abortshutdown</term><listitem><para>Abort Shutdown</para></listitem></varlistentry> - </variablelist> - - </refsect2> - - <refsect2> - <title>SRVSVC</title> - - <variablelist> - <varlistentry><term>srvinfo</term><listitem><para>Server query info</para></listitem></varlistentry> - - <varlistentry><term>netshareenum</term><listitem><para>Enumerate shares</para></listitem></varlistentry> - - <varlistentry><term>netfileenum</term><listitem><para>Enumerate open files</para></listitem></varlistentry> - - <varlistentry><term>netremotetod</term><listitem><para>Fetch remote time of day</para></listitem></varlistentry> - - </variablelist> - - </refsect2> - - <refsect2> - <title>SAMR</title> - - <variablelist> - <varlistentry><term>queryuser</term><listitem><para>Query user info</para></listitem></varlistentry> - <varlistentry><term>querygroup</term><listitem><para>Query group info</para></listitem></varlistentry> - <varlistentry><term>queryusergroups</term><listitem><para>Query user groups</para></listitem></varlistentry> - <varlistentry><term>querygroupmem</term><listitem><para>Query group membership</para></listitem></varlistentry> - <varlistentry><term>queryaliasmem</term><listitem><para>Query alias membership</para></listitem></varlistentry> - <varlistentry><term>querydispinfo</term><listitem><para>Query display info</para></listitem></varlistentry> - <varlistentry><term>querydominfo</term><listitem><para>Query domain info</para></listitem></varlistentry> - <varlistentry><term>enumdomusers</term><listitem><para>Enumerate domain users</para></listitem></varlistentry> - <varlistentry><term>enumdomgroups</term><listitem><para>Enumerate domain groups</para></listitem></varlistentry> - <varlistentry><term>enumalsgroups</term><listitem><para>Enumerate alias groups</para></listitem></varlistentry> - <varlistentry><term>createdomuser</term><listitem><para>Create domain user</para></listitem></varlistentry> - <varlistentry><term>samlookupnames</term><listitem><para>Look up names</para></listitem></varlistentry> - <varlistentry><term>samlookuprids</term><listitem><para>Look up names</para></listitem></varlistentry> - <varlistentry><term>deletedomuser</term><listitem><para>Delete domain user</para></listitem></varlistentry> - <varlistentry><term>samquerysecobj</term><listitem><para>Query SAMR security object</para></listitem></varlistentry> - <varlistentry><term>getdompwinfo</term><listitem><para>Retrieve domain password info</para></listitem></varlistentry> - <varlistentry><term>lookupdomain</term><listitem><para>Look up domain</para></listitem></varlistentry> - </variablelist> - - </refsect2> - - <refsect2> - <title>SPOOLSS</title> - - <variablelist> - <varlistentry><term>adddriver <arch> <config></term> - <listitem><para> + </p></dd><dt><span class="term">enumtrusts</span></dt><dd><p>Enumerate trusted domains</p></dd><dt><span class="term">enumprivs</span></dt><dd><p>Enumerate privileges</p></dd><dt><span class="term">getdispname</span></dt><dd><p>Get the privilege name</p></dd><dt><span class="term">lsaenumsid</span></dt><dd><p>Enumerate the LSA SIDS</p></dd><dt><span class="term">lsaenumprivsaccount</span></dt><dd><p>Enumerate the privileges of an SID</p></dd><dt><span class="term">lsaenumacctrights</span></dt><dd><p>Enumerate the rights of an SID</p></dd><dt><span class="term">lsaenumacctwithright</span></dt><dd><p>Enumerate accounts with a right</p></dd><dt><span class="term">lsaaddacctrights</span></dt><dd><p>Add rights to an account</p></dd><dt><span class="term">lsaremoveacctrights</span></dt><dd><p>Remove rights from an account</p></dd><dt><span class="term">lsalookupprivvalue</span></dt><dd><p>Get a privilege value given its name</p></dd><dt><span class="term">lsaquerysecobj</span></dt><dd><p>Query LSA security object</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>LSARPC-DS</h3><div class="variablelist"><dl><dt><span class="term">dsroledominfo</span></dt><dd><p>Get Primary Domain Information</p></dd></dl></div><p> </p><p><span class="emphasis"><em>DFS</em></span></p><div class="variablelist"><dl><dt><span class="term">dfsexist</span></dt><dd><p>Query DFS support</p></dd><dt><span class="term">dfsadd</span></dt><dd><p>Add a DFS share</p></dd><dt><span class="term">dfsremove</span></dt><dd><p>Remove a DFS share</p></dd><dt><span class="term">dfsgetinfo</span></dt><dd><p>Query DFS share info</p></dd><dt><span class="term">dfsenum</span></dt><dd><p>Enumerate dfs shares</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>REG</h3><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd><p>Remote Shutdown</p></dd><dt><span class="term">abortshutdown</span></dt><dd><p>Abort Shutdown</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SRVSVC</h3><div class="variablelist"><dl><dt><span class="term">srvinfo</span></dt><dd><p>Server query info</p></dd><dt><span class="term">netshareenum</span></dt><dd><p>Enumerate shares</p></dd><dt><span class="term">netfileenum</span></dt><dd><p>Enumerate open files</p></dd><dt><span class="term">netremotetod</span></dt><dd><p>Fetch remote time of day</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SAMR</h3><div class="variablelist"><dl><dt><span class="term">queryuser</span></dt><dd><p>Query user info</p></dd><dt><span class="term">querygroup</span></dt><dd><p>Query group info</p></dd><dt><span class="term">queryusergroups</span></dt><dd><p>Query user groups</p></dd><dt><span class="term">querygroupmem</span></dt><dd><p>Query group membership</p></dd><dt><span class="term">queryaliasmem</span></dt><dd><p>Query alias membership</p></dd><dt><span class="term">querydispinfo</span></dt><dd><p>Query display info</p></dd><dt><span class="term">querydominfo</span></dt><dd><p>Query domain info</p></dd><dt><span class="term">enumdomusers</span></dt><dd><p>Enumerate domain users</p></dd><dt><span class="term">enumdomgroups</span></dt><dd><p>Enumerate domain groups</p></dd><dt><span class="term">enumalsgroups</span></dt><dd><p>Enumerate alias groups</p></dd><dt><span class="term">createdomuser</span></dt><dd><p>Create domain user</p></dd><dt><span class="term">samlookupnames</span></dt><dd><p>Look up names</p></dd><dt><span class="term">samlookuprids</span></dt><dd><p>Look up names</p></dd><dt><span class="term">deletedomuser</span></dt><dd><p>Delete domain user</p></dd><dt><span class="term">samquerysecobj</span></dt><dd><p>Query SAMR security object</p></dd><dt><span class="term">getdompwinfo</span></dt><dd><p>Retrieve domain password info</p></dd><dt><span class="term">lookupdomain</span></dt><dd><p>Look up domain</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SPOOLSS</h3><div class="variablelist"><dl><dt><span class="term">adddriver <arch> <config></span></dt><dd><p> Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should already exist in the directory returned by - <command moreinfo="none">getdriverdir</command>. Possible values for - <parameter moreinfo="none">arch</parameter> are the same as those for - the <command moreinfo="none">getdriverdir</command> command. - The <parameter moreinfo="none">config</parameter> parameter is defined as - follows: </para> - -<para><programlisting format="linespecific"> + <b class="command">getdriverdir</b>. Possible values for + <i class="parameter"><tt>arch</tt></i> are the same as those for + the <b class="command">getdriverdir</b> command. + The <i class="parameter"><tt>config</tt></i> parameter is defined as + follows: </p><pre class="programlisting"> Long Printer Name:\ Driver File Name:\ Data File Name:\ @@ -395,239 +108,88 @@ Help File Name:\ Language Monitor Name:\ Default Data Type:\ Comma Separated list of Files -</programlisting></para> - - <para>Any empty fields should be enter as the string "NULL". </para> - - <para>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 "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. </para></listitem></varlistentry> - - <varlistentry><term>addprinter <printername> - <sharename> <drivername> <port></term> - <listitem><para> + else the RPC will fail. </p></dd><dt><span class="term">addprinter <printername> + <sharename> <drivername> <port></span></dt><dd><p> Add a printer on the remote server. This printer will be automatically shared. Be aware that the printer driver - must already be installed on the server (see <command moreinfo="none">adddriver</command>) - and the <parameter moreinfo="none">port</parameter>must be a valid port name (see - <command moreinfo="none">enumports</command>.</para> - </listitem></varlistentry> - - - <varlistentry><term>deldriver</term><listitem><para>Delete the + must already be installed on the server (see <b class="command">adddriver</b>) + and the <i class="parameter"><tt>port</tt></i>must be a valid port name (see + <b class="command">enumports</b>.</p></dd><dt><span class="term">deldriver</span></dt><dd><p>Delete the specified printer driver for all architectures. This does not delete the actual driver files from the server, only the entry from the server's list of drivers. - </para></listitem></varlistentry> - - <varlistentry><term>enumdata</term><listitem><para>Enumerate all + </p></dd><dt><span class="term">enumdata</span></dt><dd><p>Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB. This command corresponds to the MS Platform SDK GetPrinterData() function (* This - command is currently unimplemented).</para></listitem></varlistentry> - - <varlistentry><term>enumdataex</term><listitem><para>Enumerate printer data for a key</para></listitem></varlistentry> - - <varlistentry><term>enumjobs <printer></term> - <listitem><para>List the jobs and status of a given printer. + command is currently unimplemented).</p></dd><dt><span class="term">enumdataex</span></dt><dd><p>Enumerate printer data for a key</p></dd><dt><span class="term">enumjobs <printer></span></dt><dd><p>List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() - function</para></listitem></varlistentry> - - <varlistentry><term>enumkey</term><listitem><para>Enumerate - printer keys</para></listitem></varlistentry> - - <varlistentry><term>enumports [level]</term> - <listitem><para> + function</p></dd><dt><span class="term">enumkey</span></dt><dd><p>Enumerate + printer keys</p></dd><dt><span class="term">enumports [level]</span></dt><dd><p> Executes an EnumPorts() call using the specified info level. Currently only info levels 1 and 2 are supported. - </para></listitem></varlistentry> - - - - <varlistentry><term>enumdrivers [level]</term> - <listitem><para> + </p></dd><dt><span class="term">enumdrivers [level]</span></dt><dd><p> Execute an EnumPrinterDrivers() call. This lists the various installed printer drivers for all architectures. Refer to the MS Platform SDK documentation for more details of the various flags and calling - options. Currently supported info levels are 1, 2, and 3.</para></listitem></varlistentry> - - - - <varlistentry><term>enumprinters [level]</term> - <listitem><para>Execute an EnumPrinters() call. This lists the various installed + options. Currently supported info levels are 1, 2, and 3.</p></dd><dt><span class="term">enumprinters [level]</span></dt><dd><p>Execute an EnumPrinters() call. This lists the various installed and share printers. Refer to the MS Platform SDK documentation for more details of the various flags and calling options. Currently - supported info levels are 1, 2 and 5.</para></listitem></varlistentry> - - - - - <varlistentry><term>getdata <printername> <valuename;></term> - <listitem><para>Retrieve the data for a given printer setting. See - the <command moreinfo="none">enumdata</command> command for more information. + supported info levels are 1, 2 and 5.</p></dd><dt><span class="term">getdata <printername> <valuename;></span></dt><dd><p>Retrieve the data for a given printer setting. See + the <b class="command">enumdata</b> command for more information. This command corresponds to the GetPrinterData() MS Platform - SDK function. </para></listitem></varlistentry> - - <varlistentry><term>getdataex</term><listitem><para>Get + SDK function. </p></dd><dt><span class="term">getdataex</span></dt><dd><p>Get printer driver data with - keyname</para></listitem></varlistentry> - - - <varlistentry><term>getdriver <printername></term> - <listitem><para> + keyname</p></dd><dt><span class="term">getdriver <printername></span></dt><dd><p> Retrieve the printer driver information (such as driver file, config file, dependent files, etc...) for the given printer. This command corresponds to the GetPrinterDriver() MS Platform SDK function. Currently info level 1, 2, and 3 are supported. - </para></listitem></varlistentry> - - - <varlistentry><term>getdriverdir <arch></term> - <listitem><para> + </p></dd><dt><span class="term">getdriverdir <arch></span></dt><dd><p> Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible - values for <parameter moreinfo="none">arch</parameter> are "Windows 4.0" + 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". </para></listitem></varlistentry> - - - - <varlistentry><term>getprinter <printername></term> - <listitem><para>Retrieve the current printer information. This command + Alpha_AXP", and "Windows NT R4000". </p></dd><dt><span class="term">getprinter <printername></span></dt><dd><p>Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function. - </para></listitem></varlistentry> - - <varlistentry><term>getprintprocdir</term><listitem><para>Get + </p></dd><dt><span class="term">getprintprocdir</span></dt><dd><p>Get print processor - directory</para></listitem></varlistentry> - - <varlistentry><term>openprinter <printername></term> - <listitem><para>Execute an OpenPrinterEx() and ClosePrinter() RPC - against a given printer. </para></listitem></varlistentry> - - <varlistentry><term>setdriver <printername> - <drivername></term> - <listitem><para>Execute a SetPrinter() command to update the printer driver + directory</p></dd><dt><span class="term">openprinter <printername></span></dt><dd><p>Execute an OpenPrinterEx() and ClosePrinter() RPC + against a given printer. </p></dd><dt><span class="term">setdriver <printername> + <drivername></span></dt><dd><p>Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must - already be correctly installed on the print server. </para> - - <para>See also the <command moreinfo="none">enumprinters</command> and - <command moreinfo="none">enumdrivers</command> commands for obtaining a list of - of installed printers and drivers.</para></listitem></varlistentry> - - <varlistentry><term>addform</term><listitem><para>Add form</para></listitem></varlistentry> - <varlistentry><term>setform</term><listitem><para>Set form</para></listitem></varlistentry> - <varlistentry><term>getform</term><listitem><para>Get form</para></listitem></varlistentry> - <varlistentry><term>deleteform</term><listitem><para>Delete form</para></listitem></varlistentry> - <varlistentry><term>enumforms</term><listitem><para>Enumerate form</para></listitem></varlistentry> - <varlistentry><term>setprinter</term><listitem><para>Set printer comment</para></listitem></varlistentry> - <varlistentry><term>setprinterdata</term><listitem><para>Set REG_SZ printer data</para></listitem></varlistentry> - <varlistentry><term>rffpcnex</term><listitem><para>Rffpcnex test</para></listitem></varlistentry> - - - </variablelist> - - </refsect2> - - <refsect2> - <title>NETLOGON</title> - - <variablelist> - - <varlistentry><term>logonctrl2</term> - <listitem><para>Logon Control 2</para></listitem> - </varlistentry> - - <varlistentry><term>logonctrl</term> - <listitem><para>Logon Control</para></listitem> - </varlistentry> - - <varlistentry><term>samsync</term> - <listitem><para>Sam Synchronisation</para></listitem> - </varlistentry> - - <varlistentry><term>samdeltas</term> - <listitem><para>Query Sam Deltas</para></listitem> - </varlistentry> - - <varlistentry><term>samlogon</term> - <listitem><para>Sam Logon</para></listitem> - </varlistentry> - - </variablelist> - </refsect2> - - <refsect2> - <title>GENERAL COMMANDS</title> - - <variablelist> - <varlistentry><term>debuglevel</term><listitem><para>Set the current - debug level used to log information.</para></listitem></varlistentry> - - <varlistentry><term>help (?)</term><listitem><para>Print a listing of all + already be correctly installed on the print server. </p><p>See also the <b class="command">enumprinters</b> and + <b class="command">enumdrivers</b> commands for obtaining a list of + of installed printers and drivers.</p></dd><dt><span class="term">addform</span></dt><dd><p>Add form</p></dd><dt><span class="term">setform</span></dt><dd><p>Set form</p></dd><dt><span class="term">getform</span></dt><dd><p>Get form</p></dd><dt><span class="term">deleteform</span></dt><dd><p>Delete form</p></dd><dt><span class="term">enumforms</span></dt><dd><p>Enumerate form</p></dd><dt><span class="term">setprinter</span></dt><dd><p>Set printer comment</p></dd><dt><span class="term">setprinterdata</span></dt><dd><p>Set REG_SZ printer data</p></dd><dt><span class="term">rffpcnex</span></dt><dd><p>Rffpcnex test</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>NETLOGON</h3><div class="variablelist"><dl><dt><span class="term">logonctrl2</span></dt><dd><p>Logon Control 2</p></dd><dt><span class="term">logonctrl</span></dt><dd><p>Logon Control</p></dd><dt><span class="term">samsync</span></dt><dd><p>Sam Synchronisation</p></dd><dt><span class="term">samdeltas</span></dt><dd><p>Query Sam Deltas</p></dd><dt><span class="term">samlogon</span></dt><dd><p>Sam Logon</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>GENERAL COMMANDS</h3><div class="variablelist"><dl><dt><span class="term">debuglevel</span></dt><dd><p>Set the current + debug level used to log information.</p></dd><dt><span class="term">help (?)</span></dt><dd><p>Print a listing of all known commands or extended help on a particular command. - </para></listitem></varlistentry> - - <varlistentry><term>quit (exit)</term><listitem><para>Exit <command moreinfo="none">rpcclient - </command>.</para></listitem></varlistentry> - </variablelist> - </refsect2> - -</refsect1> - -<refsect1> - <title>BUGS</title> - - <para><command moreinfo="none">rpcclient</command> is designed as a developer testing tool + </p></dd><dt><span class="term">quit (exit)</span></dt><dd><p>Exit <b class="command">rpcclient + </b>.</p></dd></dl></div></div></div><div class="refsect1" lang="en"><h2>BUGS</h2><p><b class="command">rpcclient</b> is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing). It has been known to generate a core dump upon failures when invalid - parameters where passed to the interpreter. </para> - - <para>From Luke Leighton's original rpcclient man page:</para> - - <para><emphasis>WARNING!</emphasis> The MSRPC over SMB code has + parameters where passed to the interpreter. </p><p>From Luke Leighton's original rpcclient man page:</p><p><span class="emphasis"><em>WARNING!</em></span> The MSRPC over SMB code has been developed from examining Network traces. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work. Microsoft's implementation of these services has been demonstrated (and reported) - to be... a bit flaky in places. </para> - - <para>The development of Samba's implementation is also a bit rough, + to be... a bit flaky in places. </p><p>The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in - versions of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>rpcclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> that are incompatible for some commands or services. Additionally, + versions of <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a href="rpcclient.1.html"><span class="citerefentry"><span class="refentrytitle">rpcclient</span>(1)</span></a> that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may - result in incompatibilities.</para> -</refsect1> - - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of the Samba - suite.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + result in incompatibilities.</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>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 - to the way the Linux kernel is developed.</para> - - <para>The original rpcclient man page was written by Matthew + to the way the Linux kernel is developed.</p><p>The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was - done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html new file mode 100644 index 0000000000..c3be7504e2 --- /dev/null +++ b/docs/htmldocs/samba-bdc.html @@ -0,0 +1,260 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Backup Domain Control</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="samba-pdc.html" title="Chapter 5. Domain Control"><link rel="next" href="domain-member.html" title="Chapter 7. Domain Membership"></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 6. Backup Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="domain-member.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="samba-bdc.html#id2889347">Features And Benefits</a></dt><dt><a href="samba-bdc.html#id2889536">Essential Background Information</a></dt><dd><dl><dt><a href="samba-bdc.html#id2889565">MS Windows NT4 Style Domain Control</a></dt><dt><a href="samba-bdc.html#id2889816">Active Directory Domain Control</a></dt><dt><a href="samba-bdc.html#id2889836">What qualifies a Domain Controller on the network?</a></dt><dt><a href="samba-bdc.html#id2889863">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2889908">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="samba-bdc.html#id2890011">Example Configuration</a></dt></dl></dd><dt><a href="samba-bdc.html#id2890167">Common Errors</a></dt><dd><dl><dt><a href="samba-bdc.html#id2890181">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="samba-bdc.html#id2890212">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="samba-bdc.html#id2890238">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2890283">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.html" 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="id2889347"></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 +effectively using a totally different approach. In the event that you should have a persistent +concern that is not addressed in this book then please email +<a href="mailto:jht@samba.org" target="_top">John H Terpstra</a> clearly setting out your requirements +and / or question and we will do our best to provide a solution. +</p><p> +Samba-3 is capable of acting as a Backup Domain Controller to another Samba Primary Domain +Controller. A Samba-3 PDC can operate with an LDAP Account backend. The LDAP backend can be +either a common master LDAP server, or a slave server. The use of a slave LDAP server has the +benefit that when the master is down clients may still be able to log onto the network. +This effectively gives samba a high degree of scalability iand is a very sweet (nice) solution +for large organisations. +</p><p> +While it is possible to run a Samba-3 BDC with non-LDAP backend, the administrator will +need to figure out precisely what is the best way to replicate (copy / distribute) the +user and machine Accounts backend. +</p><p> +The use of a non-LDAP backend SAM database is particularly problematic because Domain member +servers and workstations periodically change the machine trust account password. The new +password is then stored only locally. This means that in the absence of a centrally stored +accounts database (such as that provided with an LDAP based solution) if Samba-3 is running +as a BDC, the BDC instance of the Domain member trust account password will not reach the +PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs this results in +overwriting of the SAM that contains the updated (changed) trust account password with resulting +breakage of the domain trust. +</p><p> +Considering the number of comments and questions raised concerning how to configure a BDC +lets consider each possible option and look at the pro's and con's for each theoretical solution: +</p><div class="itemizedlist"><p class="title"><b>Backup Domain Backend Account Distribution Options</b></p><ul type="disc"><li><p> + Solution: Passwd Backend is LDAP based, BDCs use a slave LDAP server + </p><p> + Arguments For: This is a neat and manageable solution. The LDAP based SAM (ldapsam) + is constantly kept up to date. + </p><p> + Arguments Against: Complexity + </p></li><li><p> + Passdb Backend is tdbsam based, BDCs use cron based <span class="emphasis"><em>net rpc vampire</em></span> to + obtain the Accounts database from the PDC and place them into the Samba SAM. + <span class="emphasis"><em>net rpc vampire</em></span> is a Samba function of the "net" command. + </p><p> + Arguments For: It would be a nice solution + </p><p> + Arguments Against: It does not work because Samba-3 does not support the required + protocols. This may become a later feature but is not available today. + </p></li><li><p> + Make use of rsync to replicate (pull down) copies of the essential account files + </p><p> + Arguments For: It is a simple solution, easy to set up as a scheduled job + </p><p> + Arguments Against: This will over-write the locally changed machine trust account + passwords. This is a broken and flawed solution. Do NOT do this. + </p></li><li><p> + Operate with an entirely local accounts database (not recommended) + </p><p> + Arguments For: Simple, easy to maintain + </p><p> + 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="id2889536"></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. +</p><p> +When MS Windows NT3.10 was first released, it supported an new style of Domain Control +and with it a new form of the network logon service that has extended functionality. +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="id2889565"></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 +does not validate against the account information that has been stored in the Domain +Control database (the SAM, or Security Account Manager database) then a set of error +codes is returned to the workstation that has made the authentication request. +</p><p> +When the username / password pair has been validated, the Domain Controller +(authentication server) will respond with full enumeration of the account information +that has been stored regarding that user in the User and Machine Accounts database +for that Domain. This information contains a complete network access profile for +the user but excludes any information that is particular to the user's desktop profile, +or for that matter it excludes all desktop profiles for groups that the user may +belong to. It does include password time limits, password uniqueness controls, +network access time limits, account validity information, machine names from which the +user may access the network, and much more. All this information was stored in the SAM +in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0). +</p><p> +The account information (user and machine) on Domain Controllers is stored in two files, +one containing the Security information and the other the SAM. These are stored in files +by the same name in the <tt class="filename">C:\WinNT\System32\config</tt> directory. These +are the files that are involved in replication of the SAM database where Backup Domain +Controllers are present on the network. +</p><p> +There are two situations in which it is desirable to install Backup Domain Controllers: +</p><div class="itemizedlist"><ul type="disc"><li><p> + On the local network that the Primary Domain Controller is on, if there are many + workstations and/or where the PDC is generally very busy. In this case the BDCs + will pick up network logon requests and help to add robustness to network services. + </p></li><li><p> + At each remote site, to reduce wide area network traffic and to add stability to + remote network operations. The design of the network, the strategic placement of + Backup Domain Controllers, together with an implementation that localises as much + of network to client interchange as possible will help to minimise wide area network + bandwidth needs (and thus costs). + </p></li></ul></div><p> +The PDC contains the master copy of the SAM. In the event that an administrator makes a +change to the user account database while physically present on the local network that +has the PDC, the change will likely be made directly to the PDC instance of the master +copy of the SAM. In the event that this update may be performed in a branch office the +change will likely be stored in a delta file on the local BDC. The BDC will then send +a trigger to the PDC to commence the process of SAM synchronisation. The PDC will then +request the delta from the BDC and apply it to the master SAM. The PDC will then contact +all the BDCs in the Domain and trigger them to obtain the update and then apply that to +their own copy of the SAM. +</p><p> +Thus the BDC is said to hold a <span class="emphasis"><em>read-only</em></span> of the SAM from which +it is able to process network logon requests and to authenticate users. The BDC can +continue to provide this service, particularly while, for example, the wide area +network link to the PDC is down. Thus a BDC plays a very important role in both +maintenance of Domain security as well as in network integrity. +</p><p> +In the event that the PDC should need to be taken out of service, or if it dies, then +one of the BDCs can be promoted to a PDC. If this happens while the original PDC is on +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="id2889716"></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="id2889747"></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.html" 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="id2889816"></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="id2889836"></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<#1c> with the WINS server and/or by broadcast on the local network. +The PDC also registers the unique NetBIOS name SAMBA<#1b> with the WINS server. +The name type <#1b> 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="id2889863"></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<#1c>. It assumes that each +of the machines it gets back from the queries is a domain controller and can answer logon +requests. To not open security holes both the workstation and the selected 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="id2889908"></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 + be stored in the file private/MACHINE.SID. This file is not created + since Samba 2.2.5. Nowadays the domain SID is stored in the file + private/secrets.tdb. Simply copying the secrets.tdb + from the PDC to the BDC does not work, as the BDC would + generate a new SID for itself and override the domain SID with this + new BDC SID.</p><p> + To retrieve the domain SID from the PDC or an existing BDC and store it in the + secrets.tdb, execute: + </p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>net rpc getsid</tt></b> +</pre></li><li><p> + The UNIX user database has to be synchronized from the PDC to the + BDC. This means that both the /etc/passwd and /etc/group have to be + replicated from the PDC to the BDC. This can be done manually + whenever changes are made, or the PDC is set up as a NIS master + server and the BDC as a NIS slave server. To set up the BDC as a + mere NIS client would not be enough, as the BDC would not be able to + access its user database in case of a PDC failure. NIS is by no means + the only method to synchronize passwords. An LDAP solution would work + as well. + </p></li><li><p> + The Samba password database has to be replicated from the PDC to the BDC. + As said above, though possible to synchronise the <tt class="filename">smbpasswd</tt> + file with rsync and ssh, this method is broken and flawed, and is + therefore not recommended. A better solution is to set up slave LDAP + servers for each BDC and a master LDAP server for the PDC. + </p></li><li><p> + Any netlogon share has to be replicated from the PDC to the + BDC. This can be done manually whenever login scripts are changed, + or it can be done automatically together with the smbpasswd + synchronization. + </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890011"></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="id2890026"></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<#1c> with the WINS server. This is no +problem as the name SAMBA<#1c> is a NetBIOS group name that is meant to +be registered by more than one machine. The parameter +<a class="indexterm" name="id2890094"></a><i class="parameter"><tt>domain master</tt></i> = no +forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS +name is reserved for the Primary Domain Controller. +</p><p> +The <i class="parameter"><tt>idmap backend</tt></i> will redirect the <b class="command">winbindd</b> utility to +use the LDAP database to resolve all UIDs and GIDs for UNIX accounts. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Samba-3 has introduced a new ID mapping facility. One of the features of this facility is that it +allows greater flexibility in how user and group IDs are handled in respect of NT Domain User and Group +SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Linux UID and GID values +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="id2890167"></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="id2890181"></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 +written when the SAM is copied from the PDC. The result is that the Domain member machine +on start up will find that it's passwords does not match the one now in the database and +since the startup security check will now fail, this machine will not allow logon attempts +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="id2890212"></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. +</p><p> +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="id2890238"></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. +</p><p> +As the smbpasswd file contains plain text password equivalents, it must not be +sent unencrypted over the wire. The best way to set up smbpasswd replication from +the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. +Ssh itself can be set up to accept <span class="emphasis"><em>only</em></span> rsync transfer without requiring the user +to type a password. +</p><p> +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="id2890283"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="domain-member.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Domain Control </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Domain Membership</td></tr></table></div></body></html> diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html new file mode 100644 index 0000000000..aab2d4207c --- /dev/null +++ b/docs/htmldocs/samba-pdc.html @@ -0,0 +1,510 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. Domain Control</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="ServerType.html" title="Chapter 4. Server Types and Security Modes"><link rel="next" href="samba-bdc.html" title="Chapter 6. Backup Domain Control"></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. Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="samba-pdc.html#id2886861">Features and Benefits</a></dt><dt><a href="samba-pdc.html#id2887076">Basics of Domain Control</a></dt><dd><dl><dt><a href="samba-pdc.html#id2887090">Domain Controller Types</a></dt><dt><a href="samba-pdc.html#id2887335">Preparing for Domain Control</a></dt></dl></dd><dt><a href="samba-pdc.html#id2887717">Domain Control - Example Configuration</a></dt><dt><a href="samba-pdc.html#id2888205">Samba ADS Domain Control</a></dt><dt><a href="samba-pdc.html#id2888257">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="samba-pdc.html#id2888272">Domain Network Logon Service</a></dt><dt><a href="samba-pdc.html#id2888704">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="samba-pdc.html#id2888850">Common Errors</a></dt><dd><dl><dt><a href="samba-pdc.html#id2888857">'$' cannot be included in machine name</a></dt><dt><a href="samba-pdc.html#id2888916">Joining domain fails because of existing machine account</a></dt><dt><a href="samba-pdc.html#id2888975">The system can not log you on (C000019B)....</a></dt><dt><a href="samba-pdc.html#id2889059">The machine trust account not accessible</a></dt><dt><a href="samba-pdc.html#id2889131">Account disabled</a></dt><dt><a href="samba-pdc.html#id2889164">Domain Controller Unavailable</a></dt><dt><a href="samba-pdc.html#id2889186">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 +that is already available. +</p><p> +The reader is advised NOT to tackle this section without having first understood +and mastered some basics. MS Windows networking is not particularly forgiving of +misconfiguration. Users of MS Windows networking are likely to complain +of persistent niggles that may be caused by a broken network configuration. +To a great many people however, MS Windows networking starts with a domain controller +that in some magical way is expected to solve all ills. +</p><div class="figure"><a name="domain-example"></a><p class="title"><b>Figure 5.1. An Example Domain</b></p><div class="mediaobject"><img src="projdoc/imagefiles/domain.png" width="270" alt="An Example Domain"></div></div><p> +From the Samba mailing list one can readily identify many common networking issues. +If you are not clear on the following subjects, then it will do much good to read the +sections of this HOWTO that deal with it. These are the most common causes of MS Windows +networking problems: +</p><div class="itemizedlist"><ul type="disc"><li><p>Basic TCP/IP configuration</p></li><li><p>NetBIOS name resolution</p></li><li><p>Authentication configuration</p></li><li><p>User and Group configuration</p></li><li><p>Basic File and Directory Permission Control in UNIX/Linux</p></li><li><p>Understanding of how MS Windows clients interoperate in a network + environment</p></li></ul></div><p> +Do not be put off; on the surface of it MS Windows networking seems so simple that anyone +can do it. In fact, it is not a good idea to set up an MS Windows network with +inadequate training and preparation. But let's get our first indelible principle out of the +way: <span class="emphasis"><em>It is perfectly OK to make mistakes!</em></span> In the right place and at +the right time, mistakes are the essence of learning. It is <span class="emphasis"><em>very much</em></span> +not ok to make mistakes that cause loss of productivity and impose an avoidable financial +burden on an organisation. +</p><p> +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="id2886861"></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 +grail of MS Windows NT and beyond networking. SSO allows users in a well designed network +to log onto any workstation that is a member of the domain that their user account is in +(or in a domain that has an appropriate trust relationship with the domain they are visiting) +and they will be able to log onto the network and access resources (shares, files, and printers) +as if they are sitting at their home (personal) workstation. This is a feature of the Domain +security protocols. +</p><p> +The benefits of Domain security are available to those sites that deploy a Samba PDC. +A Domain provides a unique network security identifier (SID). Domain user and group security +identifiers are comprised of the network SID plus a relative identifier (RID) that is unique to +the account. User and Group SIDs (the network SID plus the RID) can be used to create Access Control +Lists (ACLs) attached to network resources to provide organizational access control. UNIX systems +know only of local security identifiers. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +Network clients of an MS Windows Domain security environment must be Domain members to be +able to gain access to the advanced features provided. Domain membership involves more than just +setting the workgroup name to the Domain name. It requires the creation of a Domain trust account +for the workstation (called a machine account). Please refer to the chapter on +<a href="domain-member.html" title="Chapter 7. Domain Membership">setting up samba as a domain member</a> for more information. +</p></div><p> +The following functionalities are new to the Samba-3 release: +</p><div class="itemizedlist"><ul type="disc"><li><p> + Windows NT4 domain trusts + </p></li><li><p> + Adding users via the User Manager for Domains. This can be done on any MS Windows + client using the Nexus toolkit that is available from Microsoft's web site. + Samba-3 supports the use of the Microsoft Management Console for user management. + </p></li><li><p> + Introduces replaceable and multiple user account (authentication) + back ends. In the case where the back end is placed in an LDAP database, + Samba-3 confers the benefits of a back end that can be distributed, replicated, + and is highly scalable. + </p></li><li><p> + Implements full Unicode support. This simplifies cross locale internationalisation + support. It also opens up the use of protocols that Samba-2.2.x had but could not use due + to the need to fully support Unicode. + </p></li></ul></div><p> +The following functionalities are NOT provided by Samba-3: +</p><div class="itemizedlist"><ul type="disc"><li><p> + SAM replication with Windows NT4 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa). This means samba + cannot operate as a BDC when the PDC is Microsoft-based or + replicate account data to Windows-BDC's. + </p></li><li><p> + Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) - In point of fact, Samba-3 DOES have some + Active Directory Domain Control ability that is at this time + purely experimental <span class="emphasis"><em>AND</em></span> that is certain + to change as it becomes a fully supported feature some time + during the Samba-3 (or later) life cycle. However, Active Directory is + more then just SMB - it's also LDAP, Kerberos, DHCP and other protocols + (with proprietary extensions, of course). + </p></li></ul></div><p> +Windows 9x / Me / XP Home clients are not true members of a domain for reasons outlined +in this chapter. The protocol for support of Windows 9x / Me style network (domain) logons +is completely different from NT4 / Win2k type domain logons and has been officially supported +for some time. These clients use the old LanMan Network Logon facilities that are supported +in Samba since approximately the Samba-1.9.15 series. +</p><p> +Samba-3 has an implementation of group mapping between Windows NT groups +and UNIX groups (this is really quite complicated to explain in a short space). This is +discussed more fully in <a href="groupmapping.html" title="Chapter 12. Mapping MS Windows and UNIX Groups">the chapter on group mapping</a>. +</p><p> +Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store +user and machine trust account information in a suitable backend data store. +Refer <a href="domain-member.html#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.html" 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="id2887076"></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="id2887090"></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 +network, the domain controllers should be the most powerful and most capable machine in the network. +As strange as it may seem to say this here, good over all network performance dictates that +the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-Alone +(or Domain Member) servers than in the domain controllers. +</p><p> +In the case of MS Windows NT4 style domains, it is the PDC that initiates a new Domain Control database. +This forms a part of the Windows registry called the SAM (Security Account Manager). It plays a key +part in NT4 type domain user authentication and in synchronisation of the domain authentication +database with Backup Domain Controllers. +</p><p> +With MS Windows 200x Server based Active Directory domains, one domain controller initiates a potential +hierarchy of domain controllers, each with their own area of delegated control. The master domain +controller has the ability to override any down-stream controller, but a down-line controller has +control only over it's down-line. With Samba-3 this functionality can be implemented using an +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="id2887167" href="#ftn.id2887167">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. +On a network segment that has a BDC and a PDC the BDC will be most likely to service network +logon requests. The PDC will answer network logon requests when the BDC is too busy (high load). +A BDC can be promoted to a PDC. If the PDC is on line at the time that a BDC is promoted to +PDC, the previous PDC is automatically demoted to a BDC. With Samba-3 this is NOT an automatic +operation; the PDC and BDC must be manually configured and changes need to be made likewise. +</p><p> +With MS Windows NT4, it is an install time decision what type of machine the server will be. +It is possible to change the promote a BDC to a PDC and vice versa only, but the only way +to convert a domain controller to a domain member server or a stand-alone server is to +reinstall it. The install time choices offered are: +</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Primary Domain Controller</em></span> - The one that seeds the domain SAM</p></li><li><p><span class="emphasis"><em>Backup Domain Controller</em></span> - One that obtains a copy of the domain SAM</p></li><li><p><span class="emphasis"><em>Domain Member Server</em></span> - One that has NO copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.</p></li><li><p><span class="emphasis"><em>Stand-Alone Server</em></span> - One that plays NO part is SAM synchronisation, has it's own authentication database and plays no role in Domain security.</p></li></ul></div><p> +With MS Windows 2000 the configuration of domain control is done after the server has been +installed. Samba-3 is capable of acting fully as a native member of a Windows 200x server +Active Directory domain. +</p><p> +New to Samba-3 is the ability to function fully as an MS Windows NT4 style Domain Controller, +excluding the SAM replication components. However, please be aware that Samba-3 support the +MS Windows 200x domain control protocols also. +</p><p> +At this time any appearance that Samba-3 is capable of acting as an +<span class="emphasis"><em>Domain Controller</em></span> in native ADS mode is limited and experimental in nature. +This functionality should not be used until the Samba-Team offers formal support for it. +At such a time, the documentation will be revised to duly reflect all configuration and +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="id2887335"></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, +more commonly called <span class="emphasis"><em>Domain</em></span> members. +</p><p> +It should be noted that <span class="emphasis"><em>Workgroup</em></span> membership involve no special configuration +other than the machine being configured so that the network configuration has a commonly used name +for it's workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this +mode of configuration there are NO machine trust accounts and any concept of membership as such +is limited to the fact that all machines appear in the network neighbourhood to be logically +grouped together. Again, just to be clear: <span class="emphasis"><em>workgroup mode does not involve any security machine +accounts</em></span>. +</p><p> +Domain member machines have a machine account in the Domain accounts database. A special procedure +must be followed on each machine to affect Domain membership. This procedure, which can be done +only by the local machine Administrator account, will create the Domain machine account (if +if does not exist), and then initializes that account. When the client first logs onto the +Domain it triggers a machine password change. +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured +as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the +Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to +<a href="domain-member.html" title="Chapter 7. Domain Membership">the chapter on domain membership</a> for information regarding HOW to make your MS Windows clients Domain members. +</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="id2887441"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Consistent configuration of Name Resolution (See chapter on <a href="NetworkBrowsing.html" title="Chapter 10. Samba / MS Windows Network Browsing Guide">Network Browsing</a> and on + <a href="integrate-ms-networks.html" 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="id2887534"></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> +Roaming Profiles and System/Network policies are advanced network administration topics +that are covered in the <a href="ProfileMgmt.html" title="Chapter 24. Desktop Profile Management">Profile Management</a> and +<a href="PolicyMgmt.html" title="Chapter 23. System and Account Policies">Policy Management</a> chapters of this document. However, these are not +necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts. +</p></div><p> +A Domain Controller is an SMB/CIFS server that: +</p><div class="itemizedlist"><ul type="disc"><li><p> + Registers and advertises itself as a Domain Controller (through NetBIOS broadcasts + as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast, + to a WINS server over UDP unicast, or via DNS and Active Directory) + </p></li><li><p> + Provides the NETLOGON service (actually a collection of services that runs over + a number of protocols. These include the LanMan Logon service, the Netlogon service, + the Local Security Account service, and variations of them) + </p></li><li><p> + 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="id2887666"></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="id2887690" href="#ftn.id2887690">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="id2887717"></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="samba-pdc.html#pdc-example" title="Example 5.1. smb.conf for being a PDC">for being a PDC</a>. +</p><p> +</p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example 5.1. 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>netbios name = BELERIAND</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = ldapsam, guest</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 33</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</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>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>domain logons = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>logon path = \\%N\profiles\%u</tt></i></td></tr><tr><td><i class="parameter"><tt>logon drive = H:</tt></i></td></tr><tr><td><i class="parameter"><tt>logon home = \\homeserver\%u\winprofile</tt></i></td></tr><tr><td><i class="parameter"><tt>logon script = logon.cmd</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>path = /var/lib/samba/netlogon</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</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[profiles]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/profiles</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</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></table></div><p> +</p><p> +The basic options shown above are explained as follows: +</p><div class="variablelist"><dl><dt><span class="term">passdb backend</span></dt><dd><p> + This contains all the user and group account information. Acceptable values for a PDC + are: <span class="emphasis"><em>smbpasswd, tdbsam, ldapsam</em></span>. The 'guest' entry provides needed + default accounts.</p><p> + Where is is intended to use backup domain controllers (BDCs) the only logical choice is + to use LDAP so that the passdb backend can be distributed. The tdbsam and smbpasswd files + can not effectively be distributed and therefore should not be used. + </p></dd><dt><span class="term">Domain Control Parameters</span></dt><dd><p> + The parameters <span class="emphasis"><em>os level, preferred master, domain master, security, + encrypt passwords, domain logons</em></span> play a central role in assuring domain + control and network logon support.</p><p> + The <span class="emphasis"><em>os level</em></span> must be set at or above a value of 32. A domain controller + must be the domain master browser, must be set in <span class="emphasis"><em>user</em></span> mode security, + must support Microsoft compatible encrypted passwords, and must provide the network logon + service (domain logons). Encrypted passwords must be enabled, for more details on how + to do this, refer to <a href="passdb.html" title="Chapter 11. Account Information Databases">the chapter on account information databases</a>. + </p></dd><dt><span class="term">Environment Parameters</span></dt><dd><p> + The parameters <span class="emphasis"><em>logon path, logon home, logon drive, logon script</em></span> are + environment support settings that help to facilitate client logon operations and that help + to provide automated control facilities to ease network management overheads. Please refer + to the man page information for these parameters. + </p></dd><dt><span class="term">NETLOGON Share</span></dt><dd><p> + The NETLOGON share plays a central role in domain logon and domain membership support. + This share is provided on all Microsoft domain controllers. It is used to provide logon + scripts, to store Group Policy files (NTConfig.POL), as well as to locate other common + tools that may be needed for logon processing. This is an essential share on a domain controller. + </p></dd><dt><span class="term">PROFILE Share</span></dt><dd><p> + This share is used to store user desktop profiles. Eash user must have a directory at the root + of this share. This directory must be write enabled for the user and must be globally read enabled. + Samba-3 has a VFS module called 'fake_permissions' that may be installed on this share. This will + allow a Samba administrator to make the directory read only to everyone. Of course this is useful + only after the profile has been properly created. + </p></dd></dl></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +The above parameters make for a full set of parameters that may define the server's mode +of operation. The following <tt class="filename">smb.conf</tt> parameters are the essentials alone: +</p><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>netbios name = BELERIAND</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</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</tt></i></td></tr><tr><td><i class="parameter"><tt>security = User</tt></i></td></tr></table><p> +</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="id2888205"></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 +only basis. Please do NOT expect Samba-3 to support these protocols. Do not depend +on any such functionality either now or in the future. The Samba-Team may remove these +experimental features or may change their behaviour. This is mentioned for the benefit of those +who have discovered secret capabilities in samba-3 and who have asked when this functionality will be +completed. The answer is: Maybe or maybe never! +</p><p> +To be sure: Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4 style +domain controllers have. Samba-3 does NOT have all the capabilities of Windows NT4, but it does have +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="id2888257"></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="id2888272"></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="id2888289"></a><i class="parameter"><tt>domain master</tt></i> = Yes +(the Primary Domain Controller); on ALL Backup Domain Controllers <a class="indexterm" name="id2888305"></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="id2888321"></a>Example Configuration</h4></div></div><div></div></div><div class="example"><a name="id2888328"></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="id2888412"></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. +</p></div><p> +To be completely clear: If you want MS Windows XP Home Edition to integrate with your +MS Windows NT4 or Active Directory Domain security understand - IT CAN NOT BE DONE. +Your only choice is to buy the upgrade pack from MS Windows XP Home Edition to +MS Windows XP Professional. +</p><p> +Now that this has been said, please do NOT ask the mailing list, or email any of the +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="id2888450"></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 +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server. Samba-3 does this +now in the same way that MS Windows NT/2K. +</p><p> +The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is identical and +is explained in this documentation under the browsing discussions. +It should be noted, that browsing is totally orthogonal to logon support. +</p><p> +Issues related to the single-logon network model are discussed in this +section. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X/ME clients +which are the focus of this section. +</p><p> +When an SMB client in a domain wishes to logon, it broadcasts requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but ill advised ) to create a domain where the user +database is not shared between servers, i.e. they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains. +</p><p> +Using these features you can make your clients verify their logon via +the Samba server; make clients run a batch file when they logon to +the network and download their preferences, desktop and start menu. +</p><p><span class="emphasis"><em> +MS Windows XP Home edition is NOT able to join a domain and does not permit +the use of domain logons. +</em></span></p><p> +Before launching into the configuration instructions, it is +worthwhile to look at how a Windows 9x/ME client performs a logon: +</p><div class="orderedlist"><ol type="1"><li><p> + The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS name DOMAIN<#1c> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + <tt class="filename">\\SERVER</tt>. + </p></li><li><p> + The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). + </p></li><li><p> + The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. + </p></li><li><p> + The client then connects to the NetLogon share and searches for said script + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. + </p></li><li><p> + The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more than + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. + </p></li><li><p> + The client then connects to the user's home share and searches for the + user's profile. As it turns out, you can specify the user's home share as + a sharename and path. For example, <tt class="filename">\\server\fred\.winprofile</tt>. + If the profiles are found, they are implemented. + </p></li><li><p> + The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for <tt class="filename">CONFIG.POL</tt>, the policies file. If this is + found, it is read and implemented. + </p></li></ol></div><p> +The main difference between a PDC and a Windows 9x logon server configuration is that +</p><div class="itemizedlist"><ul type="disc"><li><p> + Password encryption is not required for a Windows 9x logon server. But note + that beginning with MS Windows 98 the default setting is that plain-text + password support is disabled. It can be re-enabled with the registry + changes that are documented in the chapter on Policies. + </p></li><li><p> + Windows 9x/ME clients do not require and do not use machine trust accounts. + </p></li></ul></div><p> +A Samba PDC will act as a Windows 9x logon server; after all, it does provide the +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="id2888704"></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 +modes other than <tt class="constant">USER</tt>. The only security mode +which will not work due to technical reasons is <tt class="constant">SHARE</tt> +mode security. <tt class="constant">DOMAIN</tt> and <tt class="constant">SERVER</tt> +mode security are really just a variation on SMB user level security. +</p><p> +Actually, this issue is also closely tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to do +so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +A DMB is a Domain Master Browser - see <a href="NetworkBrowsing.html#DMB" title="Setting up WORKGROUP Browsing">Domain Master Browser</a>. +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="id2888773"></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="id2888790"></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="id2888808"></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="id2888832"></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="id2888850"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888857"></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. +</p><p> +The problem is only in the program used to make the entry. Once made, it works perfectly. +Create a user without the '$'. Then use <b class="command">vipw</b> to edit the entry, adding +the '$'. Or create the whole entry with vipw if you like; make sure you use a unique User ID! +</p><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="id2888916"></a>Joining domain fails because of existing machine account</h3></div></div><div></div></div><p>“<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>”</p><p> +This happens if you try to create a machine trust account from the +machine itself and already have a connection (e.g. mapped drive) +to a share (or IPC$) on the Samba PDC. The following command +will remove all network drive connections: +</p><pre class="screen"> +<tt class="prompt">C:\> </tt><b class="userinput"><tt>net use * /d</tt></b> +</pre><p> +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="id2888975"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>“<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>” +</p><p> +This occurs when the domain SID stored in the secrets.tdb database +is changed. The most common cause of a change in domain SID is when +the domain name and/or the server name (NetBIOS name) is changed. +The only way to correct the problem is to restore the original domain +SID or remove the domain client from the domain and rejoin. The domain +SID may be reset using either the net or rpcclient utilities. +</p><p> +The reset or change the domain SID you can use the net command as follows: + +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>net getlocalsid 'OLDNAME'</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>net setlocalsid 'SID'</tt></b> +</pre><p> +</p><p> +Workstation machine trust accounts work only with the Domain (or network) SID. If this SID changes +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="id2889059"></a>The machine trust account not accessible</h3></div></div><div></div></div><p> + “<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>” +</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="id2889085"></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> +Alternatively if you are creating account entries manually then they +have not been created correctly. Make sure that you have the entry +correct for the machine trust account in <tt class="filename">smbpasswd</tt> file on the Samba PDC. +If you added the account using an editor rather than using the smbpasswd +utility, make sure that the account name is the machine NetBIOS name +with a '$' appended to it ( i.e. computer_name$ ). There must be an entry +in both /etc/passwd and the smbpasswd file. +</p><p> +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="id2889131"></a>Account disabled</h3></div></div><div></div></div><p>“<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>”</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="id2889164"></a>Domain Controller Unavailable</h3></div></div><div></div></div><p>“<span class="quote">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</span>”</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="id2889186"></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> + client schannel, server schannel, client signing, server signing</em></span> by executing: + <b class="command">testparm -v | more</b> and looking for the value of these parameters. + </p><p> + Also use the Microsoft Management Console - Local Security Settings. This tool is available from the + Control Panel. The Policy settings are found in the Local Policies / Securty Options area and are prefixed by + <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.id2887167" href="#id2887167">1</a>] </sup>See also <a href="passdb.html" title="Chapter 11. Account Information Databases">the chapter on Account Information Databases</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2887690" href="#id2887690">2</a>] </sup>See also <a href="NetworkBrowsing.html" title="Chapter 10. Samba / MS Windows Network Browsing Guide">the chapter about network browsing</a></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="samba-bdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Server Types and Security Modes </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Backup Domain Control</td></tr></table></div></body></html> diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index e5380131e1..222bdee995 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -1,371 +1,113 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="samba.7"> - -<refmeta> - <refentrytitle>samba</refentrytitle> - <manvolnum>7</manvolnum> -</refmeta> - - -<refnamediv> - <refname>samba</refname> - <refpurpose>A Windows SMB/CIFS fileserver for UNIX</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "><command moreinfo="none">Samba</command></cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>The Samba software suite is a collection of programs +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>samba</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="samba.7"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>samba — A Windows SMB/CIFS fileserver for UNIX</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">Samba</tt> </p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems. This protocol is sometimes also referred to as the Common Internet File System (CIFS). For a - more thorough description, see <ulink url="http://www.ubiqx.org/cifs/"> - http://www.ubiqx.org/cifs/</ulink>. Samba also implements the NetBIOS - protocol in nmbd.</para> - - <variablelist> - <varlistentry> - <term><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbd</command> daemon provides the file and print services to + more thorough description, see <a href="http://www.ubiqx.org/cifs/" target="_top"> + http://www.ubiqx.org/cifs/</a>. Samba also implements the NetBIOS + protocol in nmbd.</p><div class="variablelist"><dl><dt><span class="term"><a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a></span></dt><dd><p>The <b class="command">smbd</b> daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file - for this daemon is described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">nmbd</command> + for this daemon is described in <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> + </p></dd><dt><span class="term"><a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a></span></dt><dd><p>The <b class="command">nmbd</b> daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbclient</command> + is described in <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></p></dd><dt><span class="term"><a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbclient</b> program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to - any SMB server (such as a PC running Windows NT).</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">testparm</command> - utility is a simple syntax checker for Samba's <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> configuration file.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">testprns</command> + any SMB server (such as a PC running Windows NT).</p></dd><dt><span class="term"><a href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a></span></dt><dd><p>The <b class="command">testparm</b> + utility is a simple syntax checker for Samba's <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> configuration file.</p></dd><dt><span class="term"><a href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a></span></dt><dd><p>The <b class="command">testprns</b> utility supports testing printer names defined - in your <filename moreinfo="none">printcap</filename> file used - by Samba.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbstatus</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbstatus</command> + in your <tt class="filename">printcap</tt> file used + by Samba.</p></dd><dt><span class="term"><a href="smbstatus.1.html"><span class="citerefentry"><span class="refentrytitle">smbstatus</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbstatus</b> tool provides access to information about the - current connections to <command moreinfo="none">smbd</command>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>nmblookup</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">nmblookup</command> + current connections to <b class="command">smbd</b>.</p></dd><dt><span class="term"><a href="nmblookup.1.html"><span class="citerefentry"><span class="refentrytitle">nmblookup</span>(1)</span></a></span></dt><dd><p>The <b class="command">nmblookup</b> tools allows NetBIOS name queries to be made - from a UNIX host.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbgroupedit</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbgroupedit</command> + from a UNIX host.</p></dd><dt><span class="term"><a href="smbgroupedit.8.html"><span class="citerefentry"><span class="refentrytitle">smbgroupedit</span>(8)</span></a></span></dt><dd><p>The <b class="command">smbgroupedit</b> tool allows for mapping unix groups to NT Builtin, Domain, or Local groups. Also it allows setting - priviledges for that group, such as saAddUser, etc.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbpasswd</command> + priviledges for that group, such as saAddUser, etc.</p></dd><dt><span class="term"><a href="smbpasswd.8.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(8)</span></a></span></dt><dd><p>The <b class="command">smbpasswd</b> command is a tool for changing LanMan and Windows NT - password hashes on Samba and Windows NT servers.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbcacls</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbcacls</command> command is - a tool to set ACL's on remote CIFS servers. </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbsh</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbsh</command> command is + password hashes on Samba and Windows NT servers.</p></dd><dt><span class="term"><a href="smbcacls.1.html"><span class="citerefentry"><span class="refentrytitle">smbcacls</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbcacls</b> command is + a tool to set ACL's on remote CIFS servers. </p></dd><dt><span class="term"><a href="smbsh.1.html"><span class="citerefentry"><span class="refentrytitle">smbsh</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbsh</b> command is a program that allows you to run a unix shell with - with an overloaded VFS.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbtree</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbtree</command> command - is a text-based network neighborhood tool.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbtar</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">smbtar</command> can make - backups of data on CIFS/SMB servers.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbspool</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">smbspool</command> is a + with an overloaded VFS.</p></dd><dt><span class="term"><a href="smbtree.1.html"><span class="citerefentry"><span class="refentrytitle">smbtree</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbtree</b> command + is a text-based network neighborhood tool.</p></dd><dt><span class="term"><a href="smbtar.1.html"><span class="citerefentry"><span class="refentrytitle">smbtar</span>(1)</span></a></span></dt><dd><p>The <b class="command">smbtar</b> can make + backups of data on CIFS/SMB servers.</p></dd><dt><span class="term"><a href="smbspool.8.html"><span class="citerefentry"><span class="refentrytitle">smbspool</span>(8)</span></a></span></dt><dd><p><b class="command">smbspool</b> is a helper utility for printing on printers connected - to CIFS servers. </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">smbcontrol</command> is a utility + to CIFS servers. </p></dd><dt><span class="term"><a href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a></span></dt><dd><p><b class="command">smbcontrol</b> is a utility that can change the behaviour of running samba daemons. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>rpcclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">rpcclient</command> is a utility + </p></dd><dt><span class="term"><a href="rpcclient.1.html"><span class="citerefentry"><span class="refentrytitle">rpcclient</span>(1)</span></a></span></dt><dd><p><b class="command">rpcclient</b> is a utility that can be used to execute RPC commands on remote - CIFS servers.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>pdbedit</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">pdbedit</command> command + CIFS servers.</p></dd><dt><span class="term"><a href="pdbedit.8.html"><span class="citerefentry"><span class="refentrytitle">pdbedit</span>(8)</span></a></span></dt><dd><p>The <b class="command">pdbedit</b> command can be used to maintain the local user database on - a samba server.</para></listitem></varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>findsmb</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">findsmb</command> command + a samba server.</p></dd><dt><span class="term"><a href="findsmb.1.html"><span class="citerefentry"><span class="refentrytitle">findsmb</span>(1)</span></a></span></dt><dd><p>The <b class="command">findsmb</b> command can be used to find SMB servers on the local network. - </para></listitem></varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>net</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para>The <command moreinfo="none">net</command> command + </p></dd><dt><span class="term"><a href="net.8.html"><span class="citerefentry"><span class="refentrytitle">net</span>(8)</span></a></span></dt><dd><p>The <b class="command">net</b> command is supposed to work similar to the DOS/Windows - NET.EXE command.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>swat</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">swat</command> is a web-based - interface to configuring <filename moreinfo="none">smb.conf</filename>. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">winbindd</command> is a daemon + NET.EXE command.</p></dd><dt><span class="term"><a href="swat.8.html"><span class="citerefentry"><span class="refentrytitle">swat</span>(8)</span></a></span></dt><dd><p><b class="command">swat</b> is a web-based + interface to configuring <tt class="filename">smb.conf</tt>. + </p></dd><dt><span class="term"><a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a></span></dt><dd><p><b class="command">winbindd</b> is a daemon that is used for integrating authentication and - the user database into unix.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>wbinfo</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">wbinfo</command> is a utility + the user database into unix.</p></dd><dt><span class="term"><a href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a></span></dt><dd><p><b class="command">wbinfo</b> is a utility that retrieves and stores information related to winbind. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>editreg</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">editreg</command> is a command-line + </p></dd><dt><span class="term"><a href="editreg.1.html"><span class="citerefentry"><span class="refentrytitle">editreg</span>(1)</span></a></span></dt><dd><p><b class="command">editreg</b> is a command-line utility that can edit windows registry files. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>profiles</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">profiles</command> is a command-line + </p></dd><dt><span class="term"><a href="profiles.1.html"><span class="citerefentry"><span class="refentrytitle">profiles</span>(1)</span></a></span></dt><dd><p><b class="command">profiles</b> is a command-line utility that can be used to replace all occurences of a certain SID with another SID. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>vfstest</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">vfstest</command> is a utility - that can be used to test vfs modules.</para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>ntlm_auth</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">ntlm_auth</command> is a helper-utility + </p></dd><dt><span class="term"><a href="vfstest.1.html"><span class="citerefentry"><span class="refentrytitle">vfstest</span>(1)</span></a></span></dt><dd><p><b class="command">vfstest</b> is a utility + that can be used to test vfs modules.</p></dd><dt><span class="term"><a href="ntlm_auth.1.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(1)</span></a></span></dt><dd><p><b class="command">ntlm_auth</b> is a helper-utility for external programs wanting to do NTLM-authentication. - </para></listitem></varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbumount</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbmount</refentrytitle><manvolnum>8</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">smbmount</command>,<command moreinfo="none">smbmnt</command> and <command moreinfo="none">smbmnt</command> are commands that can be used to + </p></dd><dt><span class="term"><a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a>, <a href="smbumount.8.html"><span class="citerefentry"><span class="refentrytitle">smbumount</span>(8)</span></a>, <a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a></span></dt><dd><p><b class="command">smbmount</b>,<b class="command">smbmnt</b> and <b class="command">smbmnt</b> are commands that can be used to mount CIFS/SMB shares on Linux. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><citerefentry><refentrytitle>smbcquotas</refentrytitle> - <manvolnum>1</manvolnum></citerefentry></term> - <listitem><para><command moreinfo="none">smbcquotas</command> is a tool that - can set remote QUOTA's on server with NTFS 5. </para> - </listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>COMPONENTS</title> - - <para>The Samba suite is made up of several components. Each + </p></dd><dt><span class="term"><a href="smbcquotas.1.html"><span class="citerefentry"><span class="refentrytitle">smbcquotas</span>(1)</span></a></span></dt><dd><p><b class="command">smbcquotas</b> is a tool that + can set remote QUOTA's on server with NTFS 5. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMPONENTS</h2><p>The Samba suite is made up of several components. Each component is described in a separate manual page. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use. If the manual pages and documents aren't clear enough then please visit - <ulink url="http://devel.samba.org/">http://devel.samba.org</ulink> - for information on how to file a bug report or submit a patch.</para> - - <para>If you require help, visit the Samba webpage at - <ulink url="http://samba.org/">http://www.samba.org/</ulink> and + <a href="http://devel.samba.org/" target="_top">http://devel.samba.org</a> + for information on how to file a bug report or submit a patch.</p><p>If you require help, visit the Samba webpage at + <a href="http://samba.org/" target="_top">http://www.samba.org/</a> and explore the many option available to you. - </para> -</refsect1> - -<refsect1> - <title>AVAILABILITY</title> - - <para>The Samba software suite is licensed under the + </p></div><div class="refsect1" lang="en"><h2>AVAILABILITY</h2><p>The Samba software suite is licensed under the GNU Public License(GPL). A copy of that license should have come with the package in the file COPYING. You are encouraged to distribute copies of the Samba suite, but - please obey the terms of this license.</para> - - <para>The latest version of the Samba suite can be + please obey the terms of this license.</p><p>The latest version of the Samba suite can be obtained via anonymous ftp from samba.org in the directory pub/samba/. It is also available on several - mirror sites worldwide.</para> - - <para>You may also find useful information about Samba - on the newsgroup <ulink url="news:comp.protocols.smb"> - comp.protocol.smb</ulink> and the Samba mailing + mirror sites worldwide.</p><p>You may also find useful information about Samba + on the newsgroup <a href="news:comp.protocols.smb" target="_top"> + comp.protocol.smb</a> and the Samba mailing list. Details on how to join the mailing list are given in - the README file that comes with Samba.</para> - - <para>If you have access to a WWW viewer (such as Mozilla + the README file that comes with Samba.</p><p>If you have access to a WWW viewer (such as Mozilla or Konqueror) then you will also find lots of useful information, including back issues of the Samba mailing list, at - <ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>.</para> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of the - Samba suite. </para> -</refsect1> - -<refsect1> - <title>CONTRIBUTIONS</title> - - <para>If you wish to contribute to the Samba project, + <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.</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>CONTRIBUTIONS</h2><p>If you wish to contribute to the Samba project, then I suggest you join the Samba mailing list at - <ulink url="http://lists.samba.org/">http://lists.samba.org</ulink>. - </para> - - <para>If you have patches to submit, visit - <ulink url="http://devel.samba.org/">http://devel.samba.org/</ulink> + <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>. + </p><p>If you have patches to submit, visit + <a href="http://devel.samba.org/" target="_top">http://devel.samba.org/</a> for information on how to do it properly. We prefer patches - in <command moreinfo="none">diff -u</command> format.</para> -</refsect1> - -<refsect1> - <title>CONTRIBUTORS</title> - - <para>Contributors to the project are now too numerous + in <b class="command">diff -u</b> format.</p></div><div class="refsect1" lang="en"><h2>CONTRIBUTORS</h2><p>Contributors to the project are now too numerous to mention here but all deserve the thanks of all Samba users. To see a full list, look at the - <filename moreinfo="none">change-log</filename> in the source package - for the pre-CVS changes and at <ulink url="http://cvs.samba.org/"> - http://cvs.samba.org/</ulink> + <tt class="filename">change-log</tt> in the source package + for the pre-CVS changes and at <a href="http://cvs.samba.org/" target="_top"> + http://cvs.samba.org/</a> for the contributors to Samba post-CVS. CVS is the Open Source source code control system used by the Samba Team to develop - Samba. The project would have been unmanageable without it.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + Samba. The project would have been unmanageable without it.</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML - 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/securing-samba.html b/docs/htmldocs/securing-samba.html new file mode 100644 index 0000000000..492780765e --- /dev/null +++ b/docs/htmldocs/securing-samba.html @@ -0,0 +1,192 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 15. Securing Samba</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="locking.html" title="Chapter 14. File and Record Locking"><link rel="next" href="InterdomainTrusts.html" title="Chapter 16. Interdomain Trust Relationships"></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 15. Securing Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="locking.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="InterdomainTrusts.html">Next</a></td></tr></table><hr></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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="securing-samba.html#id2910685">Introduction</a></dt><dt><a href="securing-samba.html#id2910722">Features and Benefits</a></dt><dt><a href="securing-samba.html#id2910796">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="securing-samba.html#id2910816">Using host based protection</a></dt><dt><a href="securing-samba.html#id2910915">User based protection</a></dt><dt><a href="securing-samba.html#id2910975">Using interface protection</a></dt><dt><a href="securing-samba.html#id2911042">Using a firewall</a></dt><dt><a href="securing-samba.html#id2911098">Using a IPC$ share deny</a></dt><dt><a href="securing-samba.html#id2911187">NTLMv2 Security</a></dt></dl></dd><dt><a href="securing-samba.html#id2911245">Upgrading Samba</a></dt><dt><a href="securing-samba.html#id2911271">Common Errors</a></dt><dd><dl><dt><a href="securing-samba.html#id2911289">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="securing-samba.html#id2911314">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="id2910685"></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. +</p><p> +A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, +if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning +on it!" +</p><p> +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="id2910722"></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. +</p><p> +Samba permits a most flexible approach to network security. As far as possible Samba implements +the latest protocols to permit more secure MS Windows file and print operations. +</p><p> +Samba may be secured from connections that originate from outside the local network. This may be +done using <span class="emphasis"><em>host based protection</em></span> (using samba's implementation of a technology +known as "tcpwrappers", or it may be done be using <span class="emphasis"><em>interface based exclusion</em></span> +so that <span class="application">smbd</span> will bind only to specifically permitted interfaces. It is also +possible to set specific share or resource based exclusions, eg: on the <i class="parameter"><tt>[IPC$]</tt></i> +auto-share. The <i class="parameter"><tt>[IPC$]</tt></i> share is used for browsing purposes as well as to establish +TCP/IP connections. +</p><p> +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="id2910796"></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="id2910816"></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="id2910838"></a><i class="parameter"><tt>hosts allow</tt></i> and + <a class="indexterm" name="id2910852"></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> + The above will only allow SMB connections from 'localhost' (your own + computer) and from the two private networks 192.168.2 and + 192.168.3. All other connections will be refused 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="id2910915"></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="id2910975"></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 + links. This may not be what you want. + </p><p> + You can change this behaviour using options like the following: + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>interfaces = eth* lo</tt></i></td></tr><tr><td><i class="parameter"><tt>bind interfaces only = yes</tt></i></td></tr></table><p> + This tells Samba to only listen for connections on interfaces with a + name starting with 'eth' such as eth0, eth1, plus on the loopback + interface called 'lo'. The name you will need to use depends on what + OS you are using, in the above I used the common name for Ethernet + adapters on Linux. + </p><p> + If you use the above and someone tries to make a SMB connection to + your host over a PPP interface called 'ppp0' then they will get a TCP + connection refused reply. In that case no Samba code is run at all as + the operating system has been told not to pass connections from that + interface to any samba process. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911042"></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 + methods so that you are protected even if your firewall is not active + for some reason. + </p><p> + If you are setting up a firewall then you need to know what TCP and + UDP ports to allow and block. Samba uses the following: + </p><table class="simplelist" border="0" summary="Simple list"><tr><td>UDP/137 - used by nmbd</td></tr><tr><td>UDP/138 - used by nmbd</td></tr><tr><td>TCP/139 - used by smbd</td></tr><tr><td>TCP/445 - used by smbd</td></tr></table><p> + The last one is important as many older firewall setups may not be + aware of it, given that this port was only added to the protocol in + recent years. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911098"></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 + shares while denying access to IPC$ from potentially untrustworthy + hosts. + </p><p> + To do that you could use: + </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[ipc$]</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = 192.168.115.0/24 127.0.0.1</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0/0</tt></i></td></tr></table><p> + this would tell Samba that IPC$ connections are not allowed from + anywhere but the two listed places (localhost and a local + subnet). Connections to other shares would still be allowed. As the + IPC$ share is the only share that is always accessible anonymously + this provides some level of protection against attackers that do not + know a username/password for your host. + </p><p> + If you use this method then clients will be given a <span class="errorname">access denied</span> + reply when they try to access the IPC$ share. That means that those + clients will not be able to browse shares, and may also be unable to + access some other resources. + </p><p> + This is not recommended unless you cannot use one of the other + methods listed above for some reason. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911187"></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"> + [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] + "lmcompatibilitylevel"=dword:00000003 + </pre><p> + </p><p> + 0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication, + use NTLMv2 session security if the server supports it. Domain + controllers accept LM, NTLM and NTLMv2 authentication. + </p><p> + </p><pre class="screen"> + [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] + "NtlmMinClientSec"=dword:00080000 + </pre><p> + </p><p> + 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="id2911245"></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="id2911271"></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="id2911289"></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="id2911314"></a>Why can users access home directories of other users?</h3></div></div><div></div></div><p> + “<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 + to enter their own password. I have not found *any* method that I can + use to configure samba to enforce that only a user may map their own + home directory. + </span>” + </p><p>“<span class="quote"> + User xyzzy can map his home directory. Once mapped user xyzzy can also map + *anyone* else's home directory! + </span>”</p><p> + This is not a security flaw, it is by design. Samba allows + users to have *exactly* the same access to the UNIX filesystem + as they would if they were logged onto the UNIX box, except + that it only allows such views onto the file system as are + allowed by the defined shares. + </p><p> + This means that if your UNIX home directories are set up + such that one user can happily cd into another users + directory and do an ls, the UNIX security solution is to + change the UNIX file permissions on the users home directories + such that the cd and ls would be denied. + </p><p> + Samba tries very hard not to second guess the UNIX administrators + security policies, and trusts the UNIX admin to set + 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="id2911373"></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, + so to get the behavior you require, add the line : + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>users = %S</tt></i></td></tr></table><p> + this is equivalent to: + </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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="locking.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="InterdomainTrusts.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 14. File and Record Locking </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 16. Interdomain Trust Relationships</td></tr></table></div></body></html> diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 4928d41048..926d8fcbb4 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -244,8 +244,8 @@ alias|alias|alias|alias... 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="#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="#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="#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="#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> 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 @@ -322,7 +322,7 @@ alias|alias|alias|alias... created for all users accessing files on this server. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the - Windows NT PDC is an onerous task. This option allows <a href="smbd.8.html" target="_top">smbd</a> to create the required UNIX users + Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users <span class="emphasis"><em>ON DEMAND</em></span> when a user accesses the Samba server.</p><p>In order to use this option, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> must <span class="emphasis"><em>NOT</em></span> be set to <i class="parameter"><tt>security = share</tt></i> and <i class="parameter"><tt>add user script</tt></i> must be set to a full pathname for a script that will create a UNIX @@ -367,7 +367,7 @@ alias|alias|alias|alias... <i class="parameter"><tt>security</tt></i></a> option is set to <tt class="constant">server</tt> or <tt class="constant">domain</tt>. If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which <a href="smbd.8.html" target="_top">smbd</a> is running + a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication.</p><p>This is useful if you only want your Samba server to serve resources to users in the domain it is a member of. As @@ -525,6 +525,9 @@ alias|alias|alias|alias... 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 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. </p><p>Default: <span class="emphasis"><em>client use spnego = yes</em></span></p></dd><dt><span class="term"><a name="COMMENT"></a>comment (S)</span></dt><dd><p>This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via <b class="command">net view</b> to list what shares @@ -1049,12 +1052,18 @@ df $1 | tail -1 | awk '{print $2" "$4}' for a share. The default type is <tt class="constant">NTFS</tt> for compatibility with Windows NT but this can be changed to other strings such as <tt class="constant">Samba</tt> or <tt class="constant">FAT - </tt> if required.</p><p>Default: <b class="command">fstype = NTFS</b></p><p>Example: <b class="command">fstype = Samba</b></p></dd><dt><span class="term"><a name="GETWDCACHE"></a>getwd cache (G)</span></dt><dd><p>This is a tuning option. When this is enabled a + </tt> if required.</p><p>Default: <b class="command">fstype = NTFS</b></p><p>Example: <b class="command">fstype = Samba</b></p></dd><dt><span class="term"><a name="GETQUOTACOMMAND"></a>get quota command (G)</span></dt><dd><p>The <b class="command">get quota command</b> should only be used + whenever there is no operating system API available from the OS that + samba can use.</p><p>This parameter should specify the path to a script that + queries the quota information for the specified + user/group for the partition that + the specified directory is on.</p><p>Such a script should take 3 arguments:</p><div class="itemizedlist"><ul type="disc"><li><p>directory</p></li><li><p>type of query</p></li><li><p>uid of user or gid of group</p></li></ul></div><p>The type of query can be one of :</p><div class="itemizedlist"><ul type="disc"><li><p>1 - user quotas</p></li><li><p>2 - user default quotas (uid = -1)</p></li><li><p>3 - group quotas</p></li><li><p>4 - group default quotas (gid = -1)</p></li></ul></div><p>This script should print its output according to the following format:</p><div class="itemizedlist"><ul type="disc"><li><p>Line 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)</p></li><li><p>Line 2 - number of currently used blocks</p></li><li><p>Line 3 - the softlimit number of blocks</p></li><li><p>Line 4 - the hardlimit number of blocks</p></li><li><p>Line 5 - currently used number of inodes</p></li><li><p>Line 6 - the softlimit number of inodes</p></li><li><p>Line 7 - the hardlimit number of inodes</p></li><li><p>Line 8(optional) - the number of bytes in a block(default is 1024)</p></li></ul></div><p>See also the <a href="#SETQUOTACOMMAND"><i class="parameter"><tt>set quota command</tt></i></a> parameter. + </p><p>Default: <b class="command">get quota command = </b></p><p>Example: <b class="command">get quota command = /usr/local/sbin/query_quota</b></p></dd><dt><span class="term"><a name="GETWDCACHE"></a>getwd cache (G)</span></dt><dd><p>This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls. This can have a significant impact on performance, especially when the <a href="#WIDELINKS"><i class="parameter"><tt>wide links</tt></i> </a> parameter is set to <tt class="constant">no</tt>.</p><p>Default: <b class="command">getwd cache = yes</b></p></dd><dt><span class="term"><a name="GROUP"></a>group (S)</span></dt><dd><p>Synonym for <a href="#FORCEGROUP"> - <i class="parameter"><tt>force group</tt></i></a>.</p></dd><dt><span class="term"><a name="GUESTACCOUNT"></a>guest account (G)</span></dt><dd><p>This is a username which will be used for access + <i class="parameter"><tt>force group</tt></i></a>.</p></dd><dt><span class="term"><a name="GUESTACCOUNT"></a>guest account (G,S)</span></dt><dd><p>This is a username which will be used for access to services which are specified as <a href="#GUESTOK"><i class="parameter"><tt> guest ok</tt></i></a> (see below). Whatever privileges this user has will be available to any client connecting to the guest service. @@ -1062,7 +1071,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' 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>On some systems the default guest account "nobody" 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 @@ -1117,12 +1126,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' automounter) maps.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>A working NIS client is required on the system for this option to work.</p></div><p>See also <a href="#NISHOMEDIR"><i class="parameter"><tt>nis homedir</tt></i> </a>, <a href="#DOMAINLOGONS"><i class="parameter"><tt>domain logons</tt></i> - </a>.</p><p>Default: <b class="command">homedir map = <empty string></b></p><p>Example: <b class="command">homedir map = amd.homedir</b></p></dd><dt><span class="term"><a name="HOSTMSDFS"></a>host msdfs (G)</span></dt><dd><p>If set to <tt class="constant">yes</tt>, + </a>.</p><p>Default: <b class="command">homedir map = <empty string></b></p><p>Example: <b class="command">homedir map = amd.homedir</b></p></dd><dt><span class="term"><a name="HOSTMSDFS"></a>host msdfs (G)</span></dt><dd><p>This boolean parameter is only available + if Samba has been configured and compiled with the <b class="command"> + --with-msdfs</b> option. If set to <tt class="constant">yes</tt>, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server.</p><p>See also the <a href="#MSDFSROOT"><i class="parameter"><tt> msdfs root</tt></i></a> share level parameter. For more information on setting up a Dfs tree on Samba, - refer to <a href="msdfs_setup.html" target="_top">msdfs_setup.html</a>. + refer to <a href="#">???</a>. </p><p>Default: <b class="command">host msdfs = no</b></p></dd><dt><span class="term"><a name="HOSTNAMELOOKUPS"></a>hostname lookups (G)</span></dt><dd><p>Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead. An example place where hostname lookups are currently used is when checking @@ -1169,7 +1180,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' 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 = <empty string></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 - the purpose of mapping UNIX groups to NT group SIDs. This range of group ids should have no + 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 = <empty string></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 in mapping UNIX users to NT user SIDs. This range of ids should have no existing local @@ -1469,8 +1480,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' suggested command would be to add <b class="command">NET TIME \\SERVER /SET /YES</b>, to force every machine to synchronize clocks with the same time server. Another use would be to add <b class="command">NET USE - U: \\SERVER\UTILS</b> for commonly used utilities, or <b class="command"> - NET USE Q: \\SERVER\ISO9001_QA</b> for example.</p><p>Note that it is particularly important not to allow write + U: \\SERVER\UTILS</b> for commonly used utilities, or </p><pre class="screen"> + <b class="userinput"><tt>NET USE Q: \\SERVER\ISO9001_QA</tt></b></pre><p> for example.</p><p>Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be @@ -1545,8 +1556,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' </tt></i></a> parameter.</p><p>Default: <span class="emphasis"><em>depends on the setting of <i class="parameter"><tt>printing </tt></i></em></span></p><p>Example 1: <b class="command">lprm command = /usr/bin/lprm -P%p %j</b></p><p>Example 2: <b class="command">lprm command = /usr/bin/cancel %p-%j</b></p></dd><dt><span class="term"><a name="MACHINEPASSWORDTIMEOUT"></a>machine password timeout (G)</span></dt><dd><p>If a Samba server is a member of a Windows NT Domain (see the <a href="#SECURITYEQUALSDOMAIN">security = domain</a>) - parameter) then periodically a running <a href="smbd.8.html" target="_top"> - smbd(8)</a> process will try and change the MACHINE ACCOUNT + parameter) then periodically a running smbd + process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called <tt class="filename">private/secrets.tdb </tt>. This parameter specifies how often this password will be changed, in seconds. The default is one week (expressed in @@ -1799,14 +1810,15 @@ df $1 | tail -1 | awk '{print $2" "$4}' the SMB-Dfs protocol.</p><p>Only Dfs roots can act as proxy shares. Take a look at the <a href="#MSDFSROOT"><i class="parameter"><tt>msdfs root</tt></i></a> and <a href="#HOSTMSDFS"><i class="parameter"><tt>host msdfs</tt></i></a> - options to find out how to set up a Dfs root share.</p><p>Example: <b class="command">msdfs proxy = \\\\otherserver\\someshare</b></p></dd><dt><span class="term"><a name="MSDFSROOT"></a>msdfs root (S)</span></dt><dd><p>If set to <tt class="constant">yes</tt>, + options to find out how to set up a Dfs root share.</p><p>Example: <b class="command">msdfs proxy = \\\\otherserver\\someshare</b></p></dd><dt><span class="term"><a name="MSDFSROOT"></a>msdfs root (S)</span></dt><dd><p>This boolean parameter is only available if + Samba is configured and compiled with the <b class="command"> + --with-msdfs</b> option. If set to <tt class="constant">yes</tt>, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. Dfs links are specified in the share directory by symbolic links of the form <tt class="filename">msdfs:serverA\\shareA,serverB\\shareB</tt> and so on. For more information on setting up a Dfs tree - on Samba, refer to <a href="msdfs.html" target="_top">"Hosting a Microsoft - Distributed File System tree on Samba"</a> document.</p><p>See also <a href="#HOSTMSDFS"><i class="parameter"><tt>host msdfs</tt></i></a></p><p>Default: <b class="command">msdfs root = no</b></p></dd><dt><span class="term"><a name="NAMECACHETIMEOUT"></a>name cache timeout (G)</span></dt><dd><p>Specifies the number of seconds it takes before + on Samba, refer to <a href="#">???</a>.</p><p>See also <a href="#HOSTMSDFS"><i class="parameter"><tt>host msdfs</tt></i></a></p><p>Default: <b class="command">msdfs root = no</b></p></dd><dt><span class="term"><a name="NAMECACHETIMEOUT"></a>name cache timeout (G)</span></dt><dd><p>Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out. If the timeout is set to 0. the caching is disabled. </p><p>Default: <b class="command">name cache timeout = 660</b></p><p>Example: <b class="command">name cache timeout = 0</b></p></dd><dt><span class="term"><a name="NAMERESOLVEORDER"></a>name resolve order (G)</span></dt><dd><p>This option is used by the programs in the Samba @@ -1837,7 +1849,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' first, followed by a broadcast attempt, followed by a normal system hostname lookup.</p><p>When Samba is functioning in ADS security mode (<b class="command">security = ads</b>) it is advised to use following settings for <i class="parameter"><tt>name resolve order</tt></i>:</p><p><b class="command">name resolve order = wins bcast</b></p><p>DC lookups will still be done via DNS, but fallbacks to netbios names will - not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups.</p></dd><dt><span class="term"><a name="NETBIOSALIASES"></a>netbios aliases (G)</span></dt><dd><p>This is a list of NetBIOS names that <a href="nmbd.8.html" target="_top">nmbd(8)</a> will + not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups.</p></dd><dt><span class="term"><a name="NETBIOSALIASES"></a>netbios aliases (G)</span></dt><dd><p>This is a list of NetBIOS names that nmbd will advertise as additional names by which the Samba server is known. This allows one machine to appear in browse lists under multiple names. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon @@ -1943,9 +1955,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' names to OS/2 printer driver names. The format is:</p><p><nt driver name> = <os2 driver name>.<device name></p><p>For example, a valid entry using the HP LaserJet 5 printer driver would appear as <b class="command">HP LaserJet 5L = LASERJET.HP LaserJet 5L</b>.</p><p>The need for the file is due to the printer driver namespace - problem described in the <a href="printing.html" target="_top">Samba - Printing HOWTO</a>. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO containing in the Samba documentation.</p><p>Default: <b class="command">os2 driver map = <empty string></b></p></dd><dt><span class="term"><a name="OSLEVEL"></a>os level (G)</span></dt><dd><p>This integer value controls what level Samba + problem described in <a href="#">???</a>. For more details on OS/2 clients, please + refer to <a href="#">???</a>.</p><p>Default: <b class="command">os2 driver map = <empty string></b></p></dd><dt><span class="term"><a name="OSLEVEL"></a>os level (G)</span></dt><dd><p>This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> has a chance of becoming a local master browser for the <i class="parameter"><tt> @@ -1995,12 +2006,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' The MySQL based passdb backend. Takes an identifier as argument. Read the Samba HOWTO Collection for configuration details. - </p></li><li><p><b class="command">guest</b> - - Very simple backend that only provides one user: the guest user. - Only maps the NT guest user to the <i class="parameter"><tt>guest account</tt></i>. - Required in pretty much all situations. </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 guest</b></p><p>Example: <b class="command">passdb backend = ldapsam:ldaps://ldap.example.com guest</b></p><p>Example: <b class="command">passdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb guest</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 + </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 @@ -2058,19 +2065,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' it.</p><p><span class="emphasis"><em>Note</em></span> that if the <i class="parameter"><tt>unix password sync</tt></i> parameter is set to <tt class="constant">yes </tt> then this program is called <span class="emphasis"><em>AS ROOT</em></span> - before the SMB password in the <a href="smbpasswd.5.html" target="_top"><a href="smbpasswd.5.html"><span class="citerefentry"><span class="refentrytitle">smbpasswd</span>(5)</span></a> - </a> file is changed. If this UNIX password change fails, then + before the SMB password in the smbpasswd + file is changed. If this UNIX password change fails, then <b class="command">smbd</b> will fail to change the SMB password also (this is by design).</p><p>If the <i class="parameter"><tt>unix password sync</tt></i> parameter is set this parameter <span class="emphasis"><em>MUST USE ABSOLUTE PATHS</em></span> for <span class="emphasis"><em>ALL</em></span> programs called, and must be examined for security implications. Note that by default <i class="parameter"><tt>unix - password sync</tt></i> is set to <tt class="constant">no</tt>.</p><p>Not that this program is only invoked when a password change is - done via the smbd program, not when smbpasswd is used locally as root to - change a password. This means that you cannot run "smbpasswd USERNAME" as - root on the SMB server in order to test this parameter, but should run the - command "smbpasswd -r SMBMACHINE" as a non-root user instead if you want - to test the invocation of this program.</p><p>See also <a href="#UNIXPASSWORDSYNC"><i class="parameter"><tt>unix + password sync</tt></i> is set to <tt class="constant">no</tt>.</p><p>See also <a href="#UNIXPASSWORDSYNC"><i class="parameter"><tt>unix password sync</tt></i></a>.</p><p>Default: <b class="command">passwd program = /bin/passwd</b></p><p>Example: <b class="command">passwd program = /sbin/npasswd %u</b></p></dd><dt><span class="term"><a name="PASSWORDLEVEL"></a>password level (G)</span></dt><dd><p>Some client/server combinations have difficulty with mixed-case passwords. One offending client is Windows for Workgroups, which for some reason forces passwords to upper @@ -2300,7 +2302,8 @@ print5|My Printer 5 Windows XP clients. New versions of Windows 2000 or Windows XP service packs do security ACL checking on the owner and ability to write of the profile directory stored on a local workstation when copied from a Samba - share. When not in domain mode with winbindd then the security info copied + share. +</p><p>When not in domain mode with winbindd then the security info copied onto the local workstation has no meaning to the logged in user (SID) on that workstation so the profile storing fails. Adding this parameter onto a share used for profile storage changes two things about the @@ -2309,14 +2312,14 @@ print5|My Printer 5 BUILTIN\\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly 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. Note that if you have multiple users logging + 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 "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 tree to the owning user. - </p><p>Default: <b class="command">profile acls = no</b></p></dd><dt><span class="term"><a name="PROTOCOL"></a>protocol (G)</span></dt><dd><p>Synonym for <a href="#MAXPROTOCOL"> +</p><p>Default: <b class="command">profile acls = no</b></p></dd><dt><span class="term"><a name="PROTOCOL"></a>protocol (G)</span></dt><dd><p>Synonym for <a href="#MAXPROTOCOL"> <i class="parameter"><tt>max protocol</tt></i></a>.</p></dd><dt><span class="term"><a name="PUBLIC"></a>public (S)</span></dt><dd><p>Synonym for <a href="#GUESTOK"><i class="parameter"><tt>guest ok</tt></i></a>.</p></dd><dt><span class="term"><a name="QUEUEPAUSECOMMAND"></a>queuepause command (S)</span></dt><dd><p>This parameter specifies the command to be executed on the server host in order to pause the printer queue.</p><p>This command should be a program or script which takes @@ -2393,8 +2396,7 @@ print5|My Printer 5 the <a href="#WORKGROUP"><i class="parameter"><tt>workgroup</tt></i></a> parameter is used instead.</p><p>The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses - of known browse masters if your network config is that stable.</p><p>See the documentation file <a href="improved-browsing.html" target="_top">BROWSING</a> - in the <tt class="filename">docs/</tt> directory.</p><p>Default: <b class="command">remote announce = <empty string></b></p></dd><dt><span class="term"><a name="REMOTEBROWSESYNC"></a>remote browse sync (G)</span></dt><dd><p>This option allows you to setup <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to periodically request + of known browse masters if your network config is that stable.</p><p>See <a href="#">???</a>.</p><p>Default: <b class="command">remote announce = <empty string></b></p></dd><dt><span class="term"><a name="REMOTEBROWSESYNC"></a>remote browse sync (G)</span></dt><dd><p>This option allows you to setup <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This @@ -2488,8 +2490,8 @@ print5|My Printer 5 information to the server.</p><p>The default is <b class="command">security = user</b>, as this is the most common setting needed when talking to Windows 98 and Windows NT.</p><p>The alternatives are <b class="command">security = share</b>, - <b class="command">security = server</b>, <b class="command">security = domain - </b>, or <b class="command">security = ads</b>.</p><p>In versions of Samba prior to 2.0.0, the default was + <b class="command">security = server</b> or <b class="command">security = domain + </b>.</p><p>In versions of Samba prior to 2.0.0, the default was <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 @@ -2655,7 +2657,13 @@ print5|My Printer 5 vampire</b>. <i class="parameter"><tt>%u</tt></i> will be replaced with the user whose primary group is to be set. <i class="parameter"><tt>%g</tt></i> will be replaced with the group to - set.</p><p>Default: <span class="emphasis"><em>No default value</em></span></p><p>Example: <b class="command">set primary group script = /usr/sbin/usermod -g '%g' '%u'</b></p></dd><dt><span class="term"><a name="SHAREMODES"></a>share modes (S)</span></dt><dd><p>This enables or disables the honoring of + set.</p><p>Default: <span class="emphasis"><em>No default value</em></span></p><p>Example: <b class="command">set primary group script = /usr/sbin/usermod -g '%g' '%u'</b></p></dd><dt><span class="term"><a name="SETQUOTACOMMAND"></a>set quota command (G)</span></dt><dd><p>The <b class="command">set quota command</b> should only be used + whenever there is no operating system API available from the OS that + samba can use.</p><p>This parameter should specify the path to a script that + can set quota for the specified arguments.</p><p>The specified script should take the following arguments:</p><div class="itemizedlist"><ul type="disc"><li><p>1 - quota type + </p><div class="itemizedlist"><ul type="circle"><li><p>1 - user quotas</p></li><li><p>2 - user default quotas (uid = -1)</p></li><li><p>3 - group quotas</p></li><li><p>4 - group default quotas (gid = -1)</p></li></ul></div><p> + </p></li><li><p>2 - id (uid for user, gid for group, -1 if N/A)</p></li><li><p>3 - quota state (0 = disable, 1 = enable, 2 = enable and enforce)</p></li><li><p>4 - block softlimit</p></li><li><p>5 - block hardlimit</p></li><li><p>6 - inode softlimit</p></li><li><p>7 - inode hardlimit</p></li><li><p>8(optional) - block size, defaults to 1024</p></li></ul></div><p>The script should output at least one line of data.</p><p>See also the <a href="#GETQUOTACOMMAND"><i class="parameter"><tt>get quota command</tt></i></a> parameter. + </p><p>Default: <b class="command">set quota command = </b></p><p>Example: <b class="command">set quota command = /usr/local/sbin/set_quota</b></p></dd><dt><span class="term"><a name="SHAREMODES"></a>share modes (S)</span></dt><dd><p>This enables or disables the honoring of the <i class="parameter"><tt>share modes</tt></i> during a file open. These modes are used by clients to gain exclusive read or write access to a file.</p><p>These open modes are not directly supported by UNIX, so @@ -2699,7 +2707,7 @@ print5|My Printer 5 switch <span class="emphasis"><em>-r</em></span>. It means reboot after shutdown for NT.</p></li><li><p><i class="parameter"><tt>%f</tt></i> will be substituted with the switch <span class="emphasis"><em>-f</em></span>. It means force the shutdown - even if applications do not respond for NT.</p></li></ul></div><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b class="command">abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</b></p><p>Shutdown script example: + even if applications do not respond for NT.</p></li></ul></div><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b class="command">shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</b></p><p>Shutdown script example: </p><pre class="programlisting"> #!/bin/bash @@ -2973,11 +2981,13 @@ guest = * this parameter determines access to the services.</p><p>Default: <b class="command">The guest account if a guest service, else <empty string>.</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 the underlying operating + 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 + 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.</p><p>Default: <b class="command">use sendfile = no</b></p></dd><dt><span class="term"><a name="USESPNEGO"></a>use spnego (G)</span></dt><dd><p> This variable controls controls whether samba will try + and cause Samba to be faster. This is off by default as it's effects are unknown + as yet.</p><p>Default: <b class="command">use sendfile = no</b></p></dd><dt><span class="term"><a name="USESPNEGO"></a>use spnego (G)</span></dt><dd><p> This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism. Unless further issues are discovered with our SPNEGO @@ -3055,13 +3065,10 @@ 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 module names which + 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>Options for a given VFS module are specified one per line - smb.conf perfaced by the module name and a colon (:). Such as</p><p>foo:bar=biddle</p><p>where 'foo' is the name of VFS module, 'bar' is a parameter supported - by ;foo;, and 'biddle' is the value of the option 'bar'. Refer to the - manpage for a given VFS modules regarding the options supported by that module.</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 + 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 <a href="#VFSOBJECTS"> <i class="parameter"><tt>vfs objects</tt></i> </a>. @@ -3162,7 +3169,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ seperated from the ip address by a colon. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet - browsing to work correctly.</p></div><p>See the documentation file <a href="improved-browsing.html" target="_top">Browsing</a> in the samba howto collection.</p><p>Default: <span class="emphasis"><em>not enabled</em></span></p><p>Example: <b class="command">wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61</b></p><p>For this example when querying a certain name, 192.19.200.1 will + browsing to work correctly.</p></div><p>See the <a href="#">???</a>.</p><p>Default: <span class="emphasis"><em>not enabled</em></span></p><p>Example: <b class="command">wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61</b></p><p>For this example when querying a certain name, 192.19.200.1 will be asked first and if that doesn't respond 192.168.2.61. If either of those doesn't know the name 192.168.3.199 will be queried. </p><p>Example: <b class="command">wins server = 192.9.200.1 192.168.2.61</b></p></dd><dt><span class="term"><a name="WINSSUPPORT"></a>wins support (G)</span></dt><dd><p>This boolean controls if the <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> process in Samba will act as a WINS server. You should diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index a5d22a3197..44585bc1f7 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -48,7 +48,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="id2796922"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796911"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 1535856433..1ee5fd26da 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -84,12 +84,7 @@ messages. </p></dd><dt><span class="term">-p port</span></dt><dd><p>This number is the TCP port number that will be used when making connections to the server. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the - default. </p></dd><dt><span class="term">-l logfilename</span></dt><dd><p>If specified, <i class="replaceable"><tt>logfilename</tt></i> specifies a base filename - into which operational data from the running client will be - logged. </p><p>The default base name is specified at compile time.</p><p>The base name is used to generate actual log file names. - For example, if the name specified was "log", the debug file - would be <tt class="filename">log.client</tt>.</p><p>The log file generated 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. + default. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. </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 "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 @@ -140,7 +135,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 <font color="red"><smbconfoption><font color="red"><name>log level</name></font></smbconfoption></font> parameter +override the <a class="indexterm" name="id2797426"></a><i class="parameter"><tt>log level</tt></i> 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. @@ -175,7 +170,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 <primary NetBIOS name></span></dt><dd><p>This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the <font color="red"><smbconfoption><font color="red"><name>netbios name</name></font></smbconfoption></font> parameter in the <tt class="filename">smb.conf</tt> file. +to setting the <a class="indexterm" name="id2797632"></a><i class="parameter"><tt>netbios name</tt></i> 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 <scope></span></dt><dd><p>This specifies a NetBIOS scope that diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 2fe363a4ac..e7ccd27f26 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -1,315 +1,72 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbcontrol.1"> - -<refmeta> - <refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbcontrol</refname> - <refpurpose>send messages to smbd, nmbd or winbindd processes</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbcontrol</command> - <arg choice="opt" rep="norepeat">-i</arg> - <arg choice="opt" rep="norepeat">-s</arg> - </cmdsynopsis> - - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbcontrol</command> - <arg choice="opt" rep="norepeat">destination</arg> - <arg choice="opt" rep="norepeat">message-type</arg> - <arg choice="opt" rep="norepeat">parameter</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">smbcontrol</command> is a very small program, which - sends messages to a <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, a <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, or a <citerefentry><refentrytitle>winbindd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> daemon running on the system.</para> -</refsect1> - - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcontrol</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="smbcontrol.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbcontrol — send messages to smbd, nmbd or winbindd processes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbcontrol</tt> [-i] [-s]</p></div><div class="cmdsynopsis"><p><tt class="command">smbcontrol</tt> [destination] [message-type] [parameter]</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">smbcontrol</b> is a very small program, which + sends messages to a <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, a <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, or a <a href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> daemon running on the system.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - <varlistentry> - <term>-i</term> - <listitem><para>Run interactively. Individual commands +compile time.</p></dd><dt><span class="term">-i</span></dt><dd><p>Run interactively. Individual commands of the form destination message-type parameters can be entered on STDIN. An empty command line or a "q" will quit the - program.</para></listitem> - </varlistentry> - - <varlistentry> - <term>destination</term> - <listitem><para>One of <parameter moreinfo="none">nmbd</parameter>, <parameter moreinfo="none">smbd</parameter> or a process ID.</para> - - <para>The <parameter moreinfo="none">smbd</parameter> destination causes the - message to "broadcast" to all smbd daemons.</para> - - <para>The <parameter moreinfo="none">nmbd</parameter> destination causes the + program.</p></dd><dt><span class="term">destination</span></dt><dd><p>One of <i class="parameter"><tt>nmbd</tt></i>, <i class="parameter"><tt>smbd</tt></i> or a process ID.</p><p>The <i class="parameter"><tt>smbd</tt></i> destination causes the + message to "broadcast" to all smbd daemons.</p><p>The <i class="parameter"><tt>nmbd</tt></i> destination causes the message to be sent to the nmbd daemon specified in the - <filename moreinfo="none">nmbd.pid</filename> file.</para> - - <para>If a single process ID is given, the message is sent - to only that process.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>message-type</term> - <listitem><para>Type of message to send. See - the section <constant>MESSAGE-TYPES</constant> for details. - </para></listitem></varlistentry> - - - - <varlistentry> - <term>parameters</term> - <listitem><para>any parameters required for the message-type</para> - </listitem> - </varlistentry> - </variablelist> - -</refsect1> - -<refsect1> - <title>MESSAGE-TYPES</title> - - <para>Available message types are:</para> - - <variablelist> - <varlistentry><term>close-share</term> - <listitem><para>Order smbd to close the client + <tt class="filename">nmbd.pid</tt> file.</p><p>If a single process ID is given, the message is sent + to only that process.</p></dd><dt><span class="term">message-type</span></dt><dd><p>Type of message to send. See + the section <tt class="constant">MESSAGE-TYPES</tt> for details. + </p></dd><dt><span class="term">parameters</span></dt><dd><p>any parameters required for the message-type</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>MESSAGE-TYPES</h2><p>Available message types are:</p><div class="variablelist"><dl><dt><span class="term">close-share</span></dt><dd><p>Order smbd to close the client connections to the named share. Note that this doesn't affect client connections to any other shares. This message-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares. This may be useful if you made changes to the access controls on the share. - This message can only be sent to <constant>smbd</constant>.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>debug</term> - <listitem><para>Set debug level to the value specified by the - parameter. This can be sent to any of the destinations.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>force-election</term> - <listitem><para>This message causes the <command moreinfo="none">nmbd</command> daemon to - force a new browse master election. </para> - </listitem></varlistentry> - - <varlistentry> - <term>ping</term> - <listitem><para> + This message can only be sent to <tt class="constant">smbd</tt>.</p></dd><dt><span class="term">debug</span></dt><dd><p>Set debug level to the value specified by the + parameter. This can be sent to any of the destinations.</p></dd><dt><span class="term">force-election</span></dt><dd><p>This message causes the <b class="command">nmbd</b> daemon to + force a new browse master election. </p></dd><dt><span class="term">ping</span></dt><dd><p> Send specified number of "ping" messages and wait for the same number of reply "pong" messages. This can be sent to - any of the destinations.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>profile</term> - <listitem><para>Change profile settings of a daemon, based on the + any of the destinations.</p></dd><dt><span class="term">profile</span></dt><dd><p>Change profile settings of a daemon, based on the parameter. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats. This can - be sent to any smbd or nmbd destinations.</para> - </listitem></varlistentry> - - <varlistentry> - <term>debuglevel</term> - <listitem><para> + be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">debuglevel</span></dt><dd><p> Request debuglevel of a certain daemon and write it to stdout. This - can be sent to any of the destinations.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>profilelevel</term> - <listitem><para> + can be sent to any of the destinations.</p></dd><dt><span class="term">profilelevel</span></dt><dd><p> Request profilelevel of a certain daemon and write it to stdout. - This can be sent to any smbd or nmbd destinations.</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>printnotify</term> - <listitem><para> + This can be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">printnotify</span></dt><dd><p> Order smbd to send a printer notify message to any Windows NT clients connected to a printer. This message-type takes the following arguments: - </para> - - <variablelist> - - <varlistentry> - <term>queuepause printername</term> - <listitem><para>Send a queue pause change notify - message to the printer specified.</para></listitem> - </varlistentry> - - <varlistentry> - <term>queueresume printername</term> - <listitem><para>Send a queue resume change notify - message for the printer specified.</para></listitem> - </varlistentry> - - <varlistentry> - <term>jobpause printername unixjobid</term> - <listitem><para>Send a job pause change notify + </p><div class="variablelist"><dl><dt><span class="term">queuepause printername</span></dt><dd><p>Send a queue pause change notify + message to the printer specified.</p></dd><dt><span class="term">queueresume printername</span></dt><dd><p>Send a queue resume change notify + message for the printer specified.</p></dd><dt><span class="term">jobpause printername unixjobid</span></dt><dd><p>Send a job pause change notify message for the printer and unix jobid - specified.</para></listitem> - </varlistentry> - - <varlistentry> - <term>jobresume printername unixjobid</term> - <listitem><para>Send a job resume change notify + specified.</p></dd><dt><span class="term">jobresume printername unixjobid</span></dt><dd><p>Send a job resume change notify message for the printer and unix jobid - specified.</para></listitem> - </varlistentry> - - <varlistentry> - <term>jobdelete printername unixjobid</term> - <listitem><para>Send a job delete change notify + specified.</p></dd><dt><span class="term">jobdelete printername unixjobid</span></dt><dd><p>Send a job delete change notify message for the printer and unix jobid - specified.</para></listitem> - </varlistentry> - </variablelist> - - <para> + specified.</p></dd></dl></div><p> Note that this message only sends notification that an event has occured. It doesn't actually cause the event to happen. - </para> - - <para>This message can only be sent to <constant>smbd</constant>. </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>samsync</term> - <listitem><para>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <constant>smbd</constant>. </para> - <note><para>Not working at the moment</para></note> - </listitem> - </varlistentry> - - <varlistentry> - <term>samrepl</term> - <listitem><para>Send sam replication message, with specified serial. Can only be sent to <constant>smbd</constant>. Should not be used manually.</para></listitem> - </varlistentry> - - <varlistentry> - <term>dmalloc-mark</term> - <listitem><para>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </para></listitem> - </varlistentry> - - <varlistentry> - <term>dmalloc-log-changed</term> - <listitem><para> + </p><p>This message can only be sent to <tt class="constant">smbd</tt>. </p></dd><dt><span class="term">samsync</span></dt><dd><p>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <tt class="constant">smbd</tt>. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Not working at the moment</p></div></dd><dt><span class="term">samrepl</span></dt><dd><p>Send sam replication message, with specified serial. Can only be sent to <tt class="constant">smbd</tt>. Should not be used manually.</p></dd><dt><span class="term">dmalloc-mark</span></dt><dd><p>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">dmalloc-log-changed</span></dt><dd><p> Dump the pointers that have changed since the mark set by dmalloc-mark. - Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </para></listitem> - </varlistentry> - - <varlistentry> - <term>shutdown</term> - <listitem><para>Shut down specified daemon. Can be sent to both smbd and nmbd.</para></listitem> - </varlistentry> - - <varlistentry> - <term>pool-usage</term> - <listitem><para>Print a human-readable description of all + Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">shutdown</span></dt><dd><p>Shut down specified daemon. Can be sent to both smbd and nmbd.</p></dd><dt><span class="term">pool-usage</span></dt><dd><p>Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process. Available - for both smbd and nmbd.</para></listitem> - </varlistentry> - - <varlistentry> - <term>drvupgrade</term> - <listitem><para>Force clients of printers using specified driver + for both smbd and nmbd.</p></dd><dt><span class="term">drvupgrade</span></dt><dd><p>Force clients of printers using specified driver to update their local version of the driver. Can only be - sent to smbd.</para></listitem> - </varlistentry> - - <varlistentry> - <term>reload-config</term> - <listitem><para>Force daemon to reload smb.conf configuration file. Can be sent - to <constant>smbd</constant>, <constant>nmbd</constant>, or <constant>winbindd</constant>. - </para></listitem> - </varlistentry> - -</variablelist> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + sent to smbd.</p></dd><dt><span class="term">reload-config</span></dt><dd><p>Force daemon to reload smb.conf configuration file. Can be sent + to <tt class="constant">smbd</tt>, <tt class="constant">nmbd</tt>, or <tt class="constant">winbindd</tt>. + </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 suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> and <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbcquotas.1.html b/docs/htmldocs/smbcquotas.1.html index df8cffcd26..59dcd106ed 100644 --- a/docs/htmldocs/smbcquotas.1.html +++ b/docs/htmldocs/smbcquotas.1.html @@ -28,7 +28,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="id2796856"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796846"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 47c41714e8..291ddbc0f6 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -1,431 +1,178 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbd.8"> - -<refmeta> - <refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbd</refname> - <refpurpose>server to provide SMB/CIFS services to clients</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbd</command> - <arg rep="norepeat" choice="opt">-D</arg> - <arg rep="norepeat" choice="opt">-F</arg> - <arg rep="norepeat" choice="opt">-S</arg> - <arg rep="norepeat" choice="opt">-i</arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-V</arg> - <arg rep="norepeat" choice="opt">-b</arg> - <arg rep="norepeat" choice="opt">-d <debug level></arg> - <arg rep="norepeat" choice="opt">-l <log directory></arg> - <arg rep="norepeat" choice="opt">-p <port number></arg> - <arg rep="norepeat" choice="opt">-O <socket option></arg> - <arg rep="norepeat" choice="opt">-s <configuration file></arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - <para>This program is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">smbd</command> is the server daemon that +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</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="smbd.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbd — server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbd</tt> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program 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">smbd</b> is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, - OS/2, DAVE for Macintosh, and smbfs for Linux.</para> - - <para>An extensive description of the services that the + OS/2, DAVE for Macintosh, and smbfs for Linux.</p><p>An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those - services (see <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>. This man page will not describe the + services (see <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>. This man page will not describe the services, but will concentrate on the administrative aspects - of running the server.</para> - - <para>Please note that there are significant security - implications to running this server, and the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> manual page should be regarded as mandatory reading before - proceeding with installation.</para> - - <para>A session is created whenever a client requests one. + of running the server.</p><p>Please note that there are significant security + implications to running this server, and the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> manual page should be regarded as mandatory reading before + proceeding with installation.</p><p>A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all connections from its client are closed, - the copy of the server for that client terminates.</para> - - <para>The configuration file, and any files that it includes, + the copy of the server for that client terminates.</p><p>The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to - disconnect from the service, or <command moreinfo="none">smbd</command> killed and restarted.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-D</term> - <listitem><para>If specified, this parameter causes + disconnect from the service, or <b class="command">smbd</b> killed and restarted.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a - daemon is the recommended way of running <command moreinfo="none">smbd</command> for + daemon is the recommended way of running <b class="command">smbd</b> for servers that provide more than casual use file and - print services. This switch is assumed if <command moreinfo="none">smbd - </command> is executed on the command line of a shell. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-F</term> - <listitem><para>If specified, this parameter causes - the main <command moreinfo="none">smbd</command> process to not daemonize, + print services. This switch is assumed if <b class="command">smbd + </b> is executed on the command line of a shell. + </p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes + the main <b class="command">smbd</b> process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running - <command moreinfo="none">smbd</command> under process supervisors such - as <command moreinfo="none">supervise</command> and <command moreinfo="none">svscan</command> - from Daniel J. Bernstein's <command moreinfo="none">daemontools</command> + <b class="command">smbd</b> under process supervisors such + as <b class="command">supervise</b> and <b class="command">svscan</b> + from Daniel J. Bernstein's <b class="command">daemontools</b> package, or the AIX process monitor. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-S</term> - <listitem><para>If specified, this parameter causes - <command moreinfo="none">smbd</command> to log to standard output rather - than a file.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-i</term> - <listitem><para>If this parameter is specified it causes the + </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes + <b class="command">smbd</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 "interactively", not as a daemon, even if the server is executed on the command line of a shell. Setting this parameter negates the implicit deamon mode when run from the - command line. <command moreinfo="none">smbd</command> also logs to standard - output, as if the <command moreinfo="none">-S</command> parameter had been + command line. <b class="command">smbd</b> also logs to standard + output, as if the <b class="command">-S</b> parameter had been given. - </para></listitem> - </varlistentry> - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will +override the <a class="indexterm" name="id2796921"></a><i class="parameter"><tt>log level</tt></i> 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. -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - <varlistentry> - <term>-b</term> - <listitem><para>Prints information about how - Samba was built.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-l <log directory></term> - <listitem><para>If specified, - <replaceable>log directory</replaceable> +</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-b</span></dt><dd><p>Prints information about how + Samba was built.</p></dd><dt><span class="term">-l <log directory></span></dt><dd><p>If specified, + <i class="replaceable"><tt>log directory</tt></i> specifies a log directory into which the "log.smbd" log file will be created for informational and debug messages from the running server. The log file generated is never removed by the server although its size may be controlled by the - <indexterm><primary>max log size</primary></indexterm><parameter moreinfo="none">max log size</parameter> - option in the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file. <emphasis>Beware:</emphasis> - If the directory specified does not exist, <command moreinfo="none">smbd</command> + <a class="indexterm" name="id2797022"></a><i class="parameter"><tt>max log size</tt></i> + option in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. <span class="emphasis"><em>Beware:</em></span> + If the directory specified does not exist, <b class="command">smbd</b> will log to the default debug log location defined at compile time. - </para> - - <para>The default log directory is specified at - compile time.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-p <port number></term> - <listitem><para><replaceable>port number</replaceable> is a positive integer + </p><p>The default log directory is specified at + compile time.</p></dd><dt><span class="term">-p <port number></span></dt><dd><p><i class="replaceable"><tt>port number</tt></i> is a positive integer value. The default value if this parameter is not - specified is 139.</para> - - <para>This number is the port number that will be + specified is 139.</p><p>This number is the port number that will be used when making connections to the server from client software. The standard (well-known) port number for the SMB over TCP is 139, hence the default. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator - for help if you are in this situation.</para> - - <para>In order for the server to be useful by most + for help if you are in this situation.</p><p>In order for the server to be useful by most clients, should you configure it on a port other than 139, you will require port redirection services on port 139, details of which are outlined in rfc1002.txt - section 4.3.5.</para> - - <para>This parameter is not normally specified except - in the above situation.</para></listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>FILES</title> - - <variablelist> - <varlistentry> - <term><filename moreinfo="none">/etc/inetd.conf</filename></term> - <listitem><para>If the server is to be run by the - <command moreinfo="none">inetd</command> meta-daemon, this file + section 4.3.5.</p><p>This parameter is not normally specified except + in the above situation.</p></dd></dl></div></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>If the server is to be run by the + <b class="command">inetd</b> meta-daemon, this file must contain suitable startup information for the meta-daemon. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/etc/rc</filename></term> - <listitem><para>or whatever initialization script your - system uses).</para> - - <para>If running the server as a daemon at startup, + </p></dd><dt><span class="term"><tt class="filename">/etc/rc</tt></span></dt><dd><p>or whatever initialization script your + system uses).</p><p>If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/etc/services</filename></term> - <listitem><para>If running the server via the - meta-daemon <command moreinfo="none">inetd</command>, this file + sequence for the server. </p></dd><dt><span class="term"><tt class="filename">/etc/services</tt></span></dt><dd><p>If running the server via the + meta-daemon <b class="command">inetd</b>, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of the <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> server configuration file. Other common places that systems - install this file are <filename moreinfo="none">/usr/samba/lib/smb.conf</filename> - and <filename moreinfo="none">/etc/samba/smb.conf</filename>.</para> - - <para>This file describes all the services the server - is to make available to clients. See <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> for more information.</para> - </listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>LIMITATIONS</title> - <para>On some systems <command moreinfo="none">smbd</command> cannot change uid back + </p></dd><dt><span class="term"><tt class="filename">/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server 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>This file describes all the services the server + is to make available to clients. See <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>LIMITATIONS</h2><p>On some systems <b class="command">smbd</b> cannot change uid back to root after a setuid() call. Such systems are called trapdoor uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or - similar.</para> -</refsect1> - -<refsect1> - <title>ENVIRONMENT VARIABLES</title> - - <variablelist> - <varlistentry> - <term><envar>PRINTER</envar></term> - <listitem><para>If no printer name is specified to + similar.</p></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><tt class="envar">PRINTER</tt></span></dt><dd><p>If no printer name is specified to printable services, most systems will use the value of - this variable (or <constant>lp</constant> if this variable is + this variable (or <tt class="constant">lp</tt> if this variable is not defined) as the name of the printer to use. This - is not specific to the server, however.</para></listitem> - </varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>PAM INTERACTION</title> - <para>Samba uses PAM for authentication (when presented with a plaintext + is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the <indexterm><primary>obey pam restrictions</primary></indexterm><parameter moreinfo="none">obey pam restrictions</parameter> <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> paramater. When this is set, the following restrictions apply: - </para> - - <itemizedlist> - <listitem><para><emphasis>Account Validation</emphasis>: All accesses to a + by the limitations of the SMB protocol and the <a class="indexterm" name="id2797347"></a><i class="parameter"><tt>obey pam restrictions</tt></i> <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> paramater. When this is set, the following restrictions apply: + </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time. This also applies to encrypted logins. - </para></listitem> - - <listitem><para><emphasis>Session Management</emphasis>: When not using share + </p></li><li><p><span class="emphasis"><em>Session Management</em></span>: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support. - </para></listitem> - </itemizedlist> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>DIAGNOSTICS</title> - - <para>Most diagnostics issued by the server are logged + </p></li></ul></div></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>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged in a specified log file. The log file name is specified - at compile time, but may be overridden on the command line.</para> - - <para>The number and nature of diagnostics available depends + at compile time, but may be overridden on the command line.</p><p>The number and nature of diagnostics available depends on the debug level used by the server. If you have problems, set - the debug level to 3 and peruse the log files.</para> - - <para>Most messages are reasonably self-explanatory. Unfortunately, + the debug level to 3 and peruse the log files.</p><p>Most messages are reasonably self-explanatory. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the - diagnostics you are seeing.</para> -</refsect1> - -<refsect1> - <title>SIGNALS</title> - - <para>Sending the <command moreinfo="none">smbd</command> a SIGHUP will cause it to - reload its <filename moreinfo="none">smb.conf</filename> configuration - file within a short period of time.</para> - - <para>To shut down a user's <command moreinfo="none">smbd</command> process it is recommended - that <command moreinfo="none">SIGKILL (-9)</command> <emphasis>NOT</emphasis> + diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>Sending the <b class="command">smbd</b> a SIGHUP will cause it to + reload its <tt class="filename">smb.conf</tt> configuration + file within a short period of time.</p><p>To shut down a user's <b class="command">smbd</b> process it is recommended + that <b class="command">SIGKILL (-9)</b> <span class="emphasis"><em>NOT</em></span> be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate - an <command moreinfo="none">smbd</command> is to send it a SIGTERM (-15) signal and wait for - it to die on its own.</para> - - <para>The debug log level of <command moreinfo="none">smbd</command> may be raised - or lowered using <citerefentry><refentrytitle>smbcontrol</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> program (SIGUSR[1|2] signals are no longer + an <b class="command">smbd</b> is to send it a SIGTERM (-15) signal and wait for + it to die on its own.</p><p>The debug log level of <b class="command">smbd</b> may be raised + or lowered using <a href="smbcontrol.1.html"><span class="citerefentry"><span class="refentrytitle">smbcontrol</span>(1)</span></a> program (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, - whilst still running at a normally low log level.</para> - - <para>Note that as the signal handlers send a debug write, - they are not re-entrant in <command moreinfo="none">smbd</command>. This you should wait until - <command moreinfo="none">smbd</command> is in a state of waiting for an incoming SMB before + whilst still running at a normally low log level.</p><p>Note that as the signal handlers send a debug write, + they are not re-entrant in <b class="command">smbd</b>. This you should wait until + <b class="command">smbd</b> is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking - them after, however this would affect performance.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>hosts_access</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>inetd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>nmbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>smbclient</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>testprns</refentrytitle> - <manvolnum>1</manvolnum></citerefentry>, and the - Internet RFC's <filename moreinfo="none">rfc1001.txt</filename>, <filename moreinfo="none">rfc1002.txt</filename>. + them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="hosts_access.5.html"><span class="citerefentry"><span class="refentrytitle">hosts_access</span>(5)</span></a>, <a href="inetd.8.html"><span class="citerefentry"><span class="refentrytitle">inetd</span>(8)</span></a>, <a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a href="testparm.1.html"><span class="citerefentry"><span class="refentrytitle">testparm</span>(1)</span></a>, <a href="testprns.1.html"><span class="citerefentry"><span class="refentrytitle">testprns</span>(1)</span></a>, and the + Internet RFC's <tt class="filename">rfc1001.txt</tt>, <tt class="filename">rfc1002.txt</tt>. In addition the CIFS (formerly SMB) specification is available - as a link from the Web page <ulink url="http://samba.org/cifs/"> - http://samba.org/cifs/</ulink>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + as a link from the Web page <a href="http://samba.org/cifs/" target="_top"> + http://samba.org/cifs/</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index 1f5f83f751..8caedac3f5 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -1,127 +1,24 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbmnt.8"> - -<refmeta> - <refentrytitle>smbmnt</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbmnt</refname> - <refpurpose>helper utility for mounting SMB filesystems</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbmnt</command> - <arg rep="norepeat" choice="req">mount-point</arg> - <arg rep="norepeat" choice="opt">-s <share></arg> - <arg rep="norepeat" choice="opt">-r</arg> - <arg rep="norepeat" choice="opt">-u <uid></arg> - <arg rep="norepeat" choice="opt">-g <gid></arg> - <arg rep="norepeat" choice="opt">-f <mask></arg> - <arg rep="norepeat" choice="opt">-d <mask></arg> - <arg rep="norepeat" choice="opt">-o <options></arg> - <arg rep="norepeat" choice="opt">-h</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para><command moreinfo="none">smbmnt</command> is a helper application used +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmnt</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="smbmnt.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbmnt — helper utility for mounting SMB filesystems</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbmnt</tt> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b class="command">smbmnt</b> is a helper application used by the smbmount program to do the actual mounting of SMB shares. - <command moreinfo="none">smbmnt</command> can be installed setuid root if you want - normal users to be able to mount their SMB shares.</para> - - <para>A setuid smbmnt will only allow mounts on directories owned - by the user, and that the user has write permission on.</para> - - <para>The <command moreinfo="none">smbmnt</command> program is normally invoked - by <citerefentry><refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>. It should not be invoked directly by users. </para> - - <para>smbmount searches the normal PATH for smbmnt. You must ensure - that the smbmnt version in your path matches the smbmount used.</para> - -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-r</term> - <listitem><para>mount the filesystem read-only - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-u uid</term> - <listitem><para>specify the uid that the files will - be owned by </para></listitem> - </varlistentry> - - <varlistentry> - <term>-g gid</term> - <listitem><para>specify the gid that the files will be - owned by </para></listitem> - </varlistentry> - - <varlistentry> - <term>-f mask</term> - <listitem><para>specify the octal file mask applied - </para></listitem> - </varlistentry> - - <varlistentry> - <term>-d mask</term> - <listitem><para>specify the octal directory mask - applied </para></listitem> - </varlistentry> - - <varlistentry> - <term>-o options</term> - <listitem><para> + <b class="command">smbmnt</b> can be installed setuid root if you want + normal users to be able to mount their SMB shares.</p><p>A setuid smbmnt will only allow mounts on directories owned + by the user, and that the user has write permission on.</p><p>The <b class="command">smbmnt</b> program is normally invoked + by <a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a>. It should not be invoked directly by users. </p><p>smbmount searches the normal PATH for smbmnt. You must ensure + that the smbmnt version in your path matches the smbmount used.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>mount the filesystem read-only + </p></dd><dt><span class="term">-u uid</span></dt><dd><p>specify the uid that the files will + be owned by </p></dd><dt><span class="term">-g gid</span></dt><dd><p>specify the gid that the files will be + owned by </p></dd><dt><span class="term">-f mask</span></dt><dd><p>specify the octal file mask applied + </p></dd><dt><span class="term">-d mask</span></dt><dd><p>specify the octal directory mask + applied </p></dd><dt><span class="term">-o options</span></dt><dd><p> list of options that are passed as-is to smbfs, if this command is run on a 2.4 or higher Linux kernel. - </para></listitem> - </varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - </variablelist> -</refsect1> - - -<refsect1> - <title>AUTHOR</title> - - <para>Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.</para> - - <para>The current maintainer of smbfs and the userspace - tools <command moreinfo="none">smbmount</command>, <command moreinfo="none">smbumount</command>, - and <command moreinfo="none">smbmnt</command> is <ulink url="mailto:urban@teststation.com">Urban Widmark</ulink>. - The <ulink url="mailto:samba@samba.org">SAMBA Mailing list</ulink> + </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>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.</p><p>The current maintainer of smbfs and the userspace + tools <b class="command">smbmount</b>, <b class="command">smbumount</b>, + and <b class="command">smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>. + The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a> is the preferred place to ask questions regarding these programs. - </para> - - <para>The conversion of this manpage for Samba 2.2 was performed + </p><p>The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index 60e0288035..233dee51d7 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -1,237 +1,71 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbmount.8"> - -<refmeta> - <refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbmount</refname> - <refpurpose>mount an smbfs filesystem</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbmount</command> - <arg rep="norepeat" choice="req">service</arg> - <arg rep="norepeat" choice="req">mount-point</arg> - <arg rep="norepeat" choice="opt">-o options</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para><command moreinfo="none">smbmount</command> mounts a Linux SMB filesystem. It - is usually invoked as <command moreinfo="none">mount.smbfs</command> by - the <citerefentry><refentrytitle>mount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> command when using the +<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 — 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 "-t smbfs" option. This command only works in Linux, and the kernel must - support the smbfs filesystem. </para> - - <para>Options to <command moreinfo="none">smbmount</command> are specified as a comma-separated + 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.</para> - - <para><command moreinfo="none">smbmount</command> is a daemon. After mounting it keeps running until + 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 "machine name" smbmount, so - typically this output will end up in <filename moreinfo="none">log.smbmount</filename>. The <command moreinfo="none"> - smbmount</command> process may also be called mount.smbfs.</para> - - <note><para> <command moreinfo="none">smbmount</command> - calls <citerefentry><refentrytitle>smbmnt</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> to do the actual mount. You - must make sure that <command moreinfo="none">smbmnt</command> is in the path so - that it can be found. </para></note> - -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>username=<arg></term> - <listitem><para>specifies the username to connect as. If - this is not given, then the environment variable <envar> - USER</envar> is used. This option can also take the + 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 + must make sure that <b class="command">smbmnt</b> is in the path so + 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=<arg></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 "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup - to be specified as part of the username.</para></listitem> - </varlistentry> - - <varlistentry> - <term>password=<arg></term> - <listitem><para>specifies the SMB password. If this + to be specified as part of the username.</p></dd><dt><span class="term">password=<arg></span></dt><dd><p>specifies the SMB password. If this option is not given then the environment variable - <envar>PASSWD</envar> is used. If it can find - no password <command moreinfo="none">smbmount</command> will prompt + <tt class="envar">PASSWD</tt> is used. If it can find + no password <b class="command">smbmount</b> will prompt for a passeword, unless the guest option is - given. </para> - - <para> + given. </p><p> Note that passwords which contain the argument delimiter character (i.e. a comma ',') will failed to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>credentials=<filename></term> - <listitem><para>specifies a file that contains a username and/or password. + </p></dd><dt><span class="term">credentials=<filename></span></dt><dd><p>specifies a file that contains a username and/or password. The format of the file is: -<programlisting format="linespecific"> +</p><pre class="programlisting"> username = <value> password = <value> -</programlisting></para> - - <para>This is preferred over having passwords in plaintext in a - shared file, such as <filename moreinfo="none">/etc/fstab</filename>. Be sure to protect any +</pre><p>This is preferred over having passwords in plaintext in a + shared file, such as <tt class="filename">/etc/fstab</tt>. Be sure to protect any credentials file properly. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>krb</term> - <listitem><para>Use kerberos (Active Directory). </para></listitem> - </varlistentry> - - <varlistentry> - <term>netbiosname=<arg></term> - <listitem><para>sets the source NetBIOS name. It defaults - to the local hostname. </para></listitem> - </varlistentry> - - <varlistentry> - <term>uid=<arg></term> - <listitem><para>sets the uid that will own all files on + </p></dd><dt><span class="term">krb</span></dt><dd><p>Use kerberos (Active Directory). </p></dd><dt><span class="term">netbiosname=<arg></span></dt><dd><p>sets the source NetBIOS name. It defaults + to the local hostname. </p></dd><dt><span class="term">uid=<arg></span></dt><dd><p>sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>gid=<arg></term> - <listitem><para>sets the gid that will own all files on + </p></dd><dt><span class="term">gid=<arg></span></dt><dd><p>sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric - gid. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>port=<arg></term> - <listitem><para>sets the remote SMB port number. The default - is 139. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>fmask=<arg></term> - <listitem><para>sets the file mask. This determines the + gid. </p></dd><dt><span class="term">port=<arg></span></dt><dd><p>sets the remote SMB port number. The default + is 139. </p></dd><dt><span class="term">fmask=<arg></span></dt><dd><p>sets the file mask. This determines the permissions that remote files have in the local filesystem. This is not a umask, but the actual permissions for the files. - The default is based on the current umask. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>dmask=<arg></term> - <listitem><para>Sets the directory mask. This determines the + The default is based on the current umask. </p></dd><dt><span class="term">dmask=<arg></span></dt><dd><p>Sets the directory mask. This determines the permissions that remote directories have in the local filesystem. This is not a umask, but the actual permissions for the directories. - The default is based on the current umask. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>debug=<arg></term> - <listitem><para>Sets the debug level. This is useful for + The default is based on the current umask. </p></dd><dt><span class="term">debug=<arg></span></dt><dd><p>Sets the debug level. This is useful for tracking down SMB connection problems. A suggested value to start with is 4. If set too high there will be a lot of - output, possibly hiding the useful output.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>ip=<arg></term> - <listitem><para>Sets the destination host or IP address. - </para></listitem> - </varlistentry> - - - - <varlistentry> - <term>workgroup=<arg></term> - <listitem><para>Sets the workgroup on the destination </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>sockopt=<arg></term> - <listitem><para>Sets the TCP socket options. See the <ulink url="smb.conf.5.html#SOCKETOPTIONS"><citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></ulink> <parameter moreinfo="none">socket options</parameter> option. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>scope=<arg></term> - <listitem><para>Sets the NetBIOS scope </para></listitem> - </varlistentry> - - <varlistentry> - <term>guest</term> - <listitem><para>Don't prompt for a password </para></listitem> - </varlistentry> - - <varlistentry> - <term>ro</term> - <listitem><para>mount read-only </para></listitem> - </varlistentry> - - <varlistentry> - <term>rw</term><listitem><para>mount read-write </para></listitem> - </varlistentry> - - <varlistentry> - <term>iocharset=<arg></term> - <listitem><para> + output, possibly hiding the useful output.</p></dd><dt><span class="term">ip=<arg></span></dt><dd><p>Sets the destination host or IP address. + </p></dd><dt><span class="term">workgroup=<arg></span></dt><dd><p>Sets the workgroup on the destination </p></dd><dt><span class="term">sockopt=<arg></span></dt><dd><p>Sets the TCP socket options. See the <a href="smb.conf.5.html#SOCKETOPTIONS" target="_top"><a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></a> <i class="parameter"><tt>socket options</tt></i> option. + </p></dd><dt><span class="term">scope=<arg></span></dt><dd><p>Sets the NetBIOS scope </p></dd><dt><span class="term">guest</span></dt><dd><p>Don't prompt for a password </p></dd><dt><span class="term">ro</span></dt><dd><p>mount read-only </p></dd><dt><span class="term">rw</span></dt><dd><p>mount read-write </p></dd><dt><span class="term">iocharset=<arg></span></dt><dd><p> sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later) - </para></listitem> - </varlistentry> - - <varlistentry> - <term>codepage=<arg></term> - <listitem><para> + </p></dd><dt><span class="term">codepage=<arg></span></dt><dd><p> sets the codepage the server uses. See the iocharset option. Example value cp850. (Note: only kernel 2.4.0 or later) - </para></listitem> - </varlistentry> - - <varlistentry> - <term>ttl=<arg></term> - <listitem><para> + </p></dd><dt><span class="term">ttl=<arg></span></dt><dd><p> sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes). A higher value means that changes on the @@ -241,96 +75,34 @@ password = <value> like 10000ms (10 seconds) is probably more reasonable in many cases. (Note: only kernel 2.4.2 or later) - </para></listitem> - </varlistentry> - - </variablelist> - - -</refsect1> - -<refsect1> - <title>ENVIRONMENT VARIABLES</title> - - <para>The variable <envar>USER</envar> may contain the username of the + </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The variable <tt class="envar">USER</tt> may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. The variable can be used to set both username and - password by using the format username%password.</para> - - <para>The variable <envar>PASSWD</envar> may contain the password of the + password by using the format username%password.</p><p>The variable <tt class="envar">PASSWD</tt> may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level - passwords.</para> - - <para>The variable <envar>PASSWD_FILE</envar> may contain the pathname + passwords.</p><p>The variable <tt class="envar">PASSWD_FILE</tt> may contain the pathname of a file to read the password from. A single line of input is - read and used as the password.</para> -</refsect1> - - -<refsect1> - <title>BUGS</title> - - <para>Passwords and other options containing , can not be handled. + read and used as the password.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>Passwords and other options containing , can not be handled. For passwords an alternative way of passing them is in a credentials - file or in the PASSWD environment.</para> - - <para>The credentials file does not handle usernames or passwords with - leading space.</para> - - <para>One smbfs bug is important enough to mention here, even if it - is a bit misplaced:</para> - - <itemizedlist> - - <listitem><para>Mounts sometimes stop working. This is usually + file or in the PASSWD environment.</p><p>The credentials file does not handle usernames or passwords with + leading space.</p><p>One smbfs bug is important enough to mention here, even if it + is a bit misplaced:</p><div class="itemizedlist"><ul type="disc"><li><p>Mounts sometimes stop working. This is usually caused by smbmount terminating. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead. An umount/mount normally fixes this. At least 2 ways to - trigger this bug are known.</para></listitem> - - </itemizedlist> - - <para>Note that the typical response to a bug report is suggestion + trigger this bug are known.</p></li></ul></div><p>Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software - when reporting bugs (minimum: samba, kernel, distribution)</para> - -</refsect1> - - -<refsect1> - <title>SEE ALSO</title> - - <para>Documentation/filesystems/smbfs.txt in the linux kernel - source tree may contain additional options and information.</para> - - <para>FreeBSD also has a smbfs, but it is not related to smbmount</para> - - <para>For Solaris, HP-UX and others you may want to look at <citerefentry><refentrytitle>smbsh</refentrytitle> - <manvolnum>1</manvolnum></citerefentry> or at other solutions, such as - Sharity or perhaps replacing the SMB server with a NFS server.</para> - -</refsect1> - - -<refsect1> - <title>AUTHOR</title> - - <para>Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.</para> - - <para>The current maintainer of smbfs and the userspace - tools <command moreinfo="none">smbmount</command>, <command moreinfo="none">smbumount</command>, - and <command moreinfo="none">smbmnt</command> is <ulink url="mailto:urban@teststation.com">Urban Widmark</ulink>. - The <ulink url="mailto:samba@samba.org">SAMBA Mailing list</ulink> + when reporting bugs (minimum: samba, kernel, distribution)</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>Documentation/filesystems/smbfs.txt in the linux kernel + source tree may contain additional options and information.</p><p>FreeBSD also has a smbfs, but it is not related to smbmount</p><p>For Solaris, HP-UX and others you may want to look at <a href="smbsh.1.html"><span class="citerefentry"><span class="refentrytitle">smbsh</span>(1)</span></a> or at other solutions, such as + Sharity or perhaps replacing the SMB server with a NFS server.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.</p><p>The current maintainer of smbfs and the userspace + tools <b class="command">smbmount</b>, <b class="command">smbumount</b>, + and <b class="command">smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>. + The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a> is the preferred place to ask questions regarding these programs. - </para> - - <para>The conversion of this manpage for Samba 2.2 was performed + </p><p>The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 7f51bed5d9..700f986f30 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -1,71 +1,18 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbpasswd.5"> - -<refmeta> - <refentrytitle>smbpasswd</refentrytitle> - <manvolnum>5</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbpasswd</refname> - <refpurpose>The Samba encrypted password file</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <para><filename moreinfo="none">smbpasswd</filename></para> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para>smbpasswd is the Samba encrypted password file. It contains +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</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="smbpasswd.5"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd — The Samba encrypted password file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><tt class="filename">smbpasswd</tt></p></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>smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with - Samba and has had several different formats in the past. </para> -</refsect1> - -<refsect1> - <title>FILE FORMAT</title> - - <para>The format of the smbpasswd file used by Samba 2.2 - is very similar to the familiar Unix <filename moreinfo="none">passwd(5)</filename> + Samba and has had several different formats in the past. </p></div><div class="refsect1" lang="en"><h2>FILE FORMAT</h2><p>The format of the smbpasswd file used by Samba 2.2 + is very similar to the familiar Unix <tt class="filename">passwd(5)</tt> file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The smbpasswd file contains the - following information for each user: </para> - - <variablelist> - <varlistentry> - <term>name</term> - <listitem><para> This is the user name. It must be a name that - already exists in the standard UNIX passwd file. </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>uid</term> - <listitem><para>This is the UNIX uid. It must match the uid + following information for each user: </p><div class="variablelist"><dl><dt><span class="term">name</span></dt><dd><p> This is the user name. It must be a name that + already exists in the standard UNIX passwd file. </p></dd><dt><span class="term">uid</span></dt><dd><p>This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>Lanman Password Hash</term> - <listitem><para>This is the LANMAN hash of the user's password, + </p></dd><dt><span class="term">Lanman Password Hash</span></dt><dd><p>This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. @@ -76,135 +23,68 @@ 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 - <constant>disabled</constant> and the user will not be able to - log onto the Samba server. </para> - - <para><emphasis>WARNING !!</emphasis> Note that, due to + <tt class="constant">disabled</tt> and the user will not be able to + log onto the Samba server. </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 - reason these hashes are known as <emphasis>plain text - equivalents</emphasis> and must <emphasis>NOT</emphasis> be made + reason these hashes are known as <span class="emphasis"><em>plain text + equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no - other access. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>NT Password Hash</term> - <listitem><para>This is the Windows NT hash of the user's + other access. </p></dd><dt><span class="term">NT Password Hash</span></dt><dd><p>This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 - (internet rfc1321) hashing algorithm to it. </para> - - <para>This password hash is considered more secure than + (internet rfc1321) hashing algorithm to it. </p><p>This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the 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 "salted" as the UNIX password is). </para> - - <para><emphasis>WARNING !!</emphasis>. 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 - reason these hashes are known as <emphasis>plain text - equivalents</emphasis> and must <emphasis>NOT</emphasis> be made + reason these hashes are known as <span class="emphasis"><em>plain text + equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no - other access. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>Account Flags</term> - <listitem><para>This section contains flags that describe + other access. </p></dd><dt><span class="term">Account Flags</span></dt><dd><p>This section contains flags that describe the attributes of the users account. In the Samba 2.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters: - </para> - - <itemizedlist> - <listitem><para><emphasis>U</emphasis> - This means + </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>U</em></span> - This means this is a "User" account, i.e. an ordinary user. Only User and Workstation Trust accounts are currently supported - in the smbpasswd file. </para></listitem> - - <listitem><para><emphasis>N</emphasis> - This means the + 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 Password Hash and NT Password Hash are ignored). Note that this - will only allow users to log on with no password if the <parameter moreinfo="none"> - null passwords</parameter> parameter is set in the - <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> config file. </para></listitem> - - <listitem><para><emphasis>D</emphasis> - This means the account - is disabled and no SMB/CIFS logins will be allowed for this user. </para></listitem> - - <listitem><para><emphasis>W</emphasis> - This means this account + will only allow users to log on with no password if the <i class="parameter"><tt> + 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 "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. </para> - </listitem> - </itemizedlist> - - <para>Other flags may be added as the code is extended in future. - The rest of this field space is filled in with spaces. </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>Last Change Time</term> - <listitem><para>This field consists of the time the account was + 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 "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made. - </para></listitem> - </varlistentry> - </variablelist> - - <para>All other colon separated fields are ignored at this time.</para> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbpasswd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry>, and + </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 the Internet RFC1321 for details on the MD4 algorithm. - </para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + </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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index f74e0b330a..73feaecf14 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -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="id2797350"></a><i class="parameter"><tt>ldap admin dn</tt></i>. Note that the password is stored in + <a class="indexterm" name="id2797339"></a><i class="parameter"><tt>ldap admin dn</tt></i>. 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 diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 1fce592ae6..c9feebe01b 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="id2796710"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796723"></a><i class="parameter"><tt>log level</tt></i> parameter in the <tt class="filename">smb.conf</tt> file.</p></dd><dt><span class="term">-R <name resolve order></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="id2796864"></a><i class="parameter"><tt>name resolve order</tt></i>) will be used. +(<a class="indexterm" name="id2796877"></a><i class="parameter"><tt>name resolve order</tt></i>) 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="id2796883"></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="id2796896"></a><i class="parameter"><tt>name resolve order</tt></i> 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/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index 44fa5d41a1..99b152e75c 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -1,200 +1,42 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbstatus.1"> - -<refmeta> - <refentrytitle>smbstatus</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbstatus</refname> - <refpurpose>report on current Samba connections</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbstatus</command> - <arg rep="norepeat" choice="opt">-P</arg> - <arg rep="norepeat" choice="opt">-b</arg> - <arg rep="norepeat" choice="opt">-d <debug level></arg> - <arg rep="norepeat" choice="opt">-v</arg> - <arg rep="norepeat" choice="opt">-L</arg> - <arg rep="norepeat" choice="opt">-B</arg> - <arg rep="norepeat" choice="opt">-p</arg> - <arg rep="norepeat" choice="opt">-S</arg> - <arg rep="norepeat" choice="opt">-s <configuration file></arg> - <arg rep="norepeat" choice="opt">-u <username></arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">smbstatus</command> is a very simple program to - list the current Samba connections.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-P|--profile</term> - <listitem><para>If samba has been compiled with the +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbstatus</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="smbstatus.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbstatus — report on current Samba connections</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbstatus</tt> [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]</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">smbstatus</b> is a very simple program to + list the current Samba connections.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-P|--profile</span></dt><dd><p>If samba has been compiled with the profiling option, print only the contents of the profiling - shared memory area.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-b|--brief</term> - <listitem><para>gives brief output.</para></listitem> - </varlistentry> - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + shared memory area.</p></dd><dt><span class="term">-b|--brief</span></dt><dd><p>gives brief output.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will +override the <a class="indexterm" name="id2796685"></a><i class="parameter"><tt>log level</tt></i> 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. -</para></listitem> -</varlistentry> - - - <varlistentry> - <term>-v|--verbose</term> - <listitem><para>gives verbose output.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>-L|--locks</term> - <listitem><para>causes smbstatus to only list locks.</para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>-B|--byterange</term> - <listitem><para>causes smbstatus to include byte range locks. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-p|--processes</term> - <listitem><para>print a list of <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> processes and exit. - Useful for scripting.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>-S|--shares</term> - <listitem><para>causes smbstatus to only list shares.</para> - </listitem> - </varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - <varlistentry> - <term>-u|--user=<username></term> - <listitem><para>selects information relevant to - <parameter moreinfo="none">username</parameter> only.</para> - </listitem> - </varlistentry> - - </variablelist> -</refsect1> - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities +</p></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>gives verbose output.</p></dd><dt><span class="term">-L|--locks</span></dt><dd><p>causes smbstatus to only list locks.</p></dd><dt><span class="term">-B|--byterange</span></dt><dd><p>causes smbstatus to include byte range locks. + </p></dd><dt><span class="term">-p|--processes</span></dt><dd><p>print a list of <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> processes and exit. + Useful for scripting.</p></dd><dt><span class="term">-S|--shares</span></dt><dd><p>causes smbstatus to only list shares.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-u|--user=<username></span></dt><dd><p>selects information relevant to + <i class="parameter"><tt>username</tt></i> only.</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 suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> and <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index 962b2a82e0..30058d1860 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -1,238 +1,39 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbtar.1"> - -<refmeta> - <refentrytitle>smbtar</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbtar</refname> - <refpurpose>shell script for backing up SMB/CIFS shares - directly to UNIX tape drives</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbtar</command> - <arg rep="norepeat" choice="opt">-r</arg> - <arg rep="norepeat" choice="opt">-i</arg> - <arg rep="norepeat" choice="opt">-a</arg> - <arg rep="norepeat" choice="opt">-v</arg> - <arg rep="norepeat" choice="req">-s server</arg> - <arg rep="norepeat" choice="opt">-p password</arg> - <arg rep="norepeat" choice="opt">-x services</arg> - <arg rep="norepeat" choice="opt">-X</arg> - <arg rep="norepeat" choice="opt">-N filename</arg> - <arg rep="norepeat" choice="opt">-b blocksize</arg> - <arg rep="norepeat" choice="opt">-d directory</arg> - <arg rep="norepeat" choice="opt">-l loglevel</arg> - <arg rep="norepeat" choice="opt">-u user</arg> - <arg rep="norepeat" choice="opt">-t tape</arg> - <arg rep="norepeat" choice="req">filenames</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">smbtar</command> is a very small shell script on top - of <citerefentry><refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry> which dumps SMB shares directly to tape.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-s server</term> - <listitem><para>The SMB/CIFS server that the share resides - upon.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>-x service</term> - <listitem><para>The share name on the server to connect to. - The default is "backup".</para></listitem> - </varlistentry> - - - <varlistentry> - <term>-X</term> - <listitem><para>Exclude mode. Exclude filenames... from tar - create or restore. </para></listitem> - </varlistentry> - - - - <varlistentry> - <term>-d directory</term> - <listitem><para>Change to initial <parameter moreinfo="none">directory - </parameter> before restoring / backing up files. </para></listitem> - </varlistentry> - - - - <varlistentry> - <term>-v</term> - <listitem><para>Verbose mode.</para></listitem> - </varlistentry> - - - - <varlistentry> - <term>-p password</term> - <listitem><para>The password to use to access a share. - Default: none </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-u user</term> - <listitem><para>The user id to connect as. Default: - UNIX login name. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-a</term> - <listitem><para>Reset DOS archive bit mode to - indicate file has been archived. </para></listitem> - </varlistentry> - - <varlistentry> - <term>-t tape</term> - <listitem><para>Tape device. May be regular file or tape - device. Default: <parameter moreinfo="none">$TAPE</parameter> environmental - variable; if not set, a file called <filename moreinfo="none">tar.out - </filename>. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-b blocksize</term> - <listitem><para>Blocking factor. Defaults to 20. See - <command moreinfo="none">tar(1)</command> for a fuller explanation. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-N filename</term> - <listitem><para>Backup only files newer than filename. Could +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtar</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="smbtar.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbtar — shell script for backing up SMB/CIFS shares + 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 "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: + UNIX login name. </p></dd><dt><span class="term">-a</span></dt><dd><p>Reset DOS archive bit mode to + indicate file has been archived. </p></dd><dt><span class="term">-t tape</span></dt><dd><p>Tape device. May be regular file or tape + device. Default: <i class="parameter"><tt>$TAPE</tt></i> environmental + variable; if not set, a file called <tt class="filename">tar.out + </tt>. </p></dd><dt><span class="term">-b blocksize</span></dt><dd><p>Blocking factor. Defaults to 20. See + <b class="command">tar(1)</b> for a fuller explanation. </p></dd><dt><span class="term">-N filename</span></dt><dd><p>Backup only files newer than filename. Could be used (for example) on a log file to implement incremental - backups. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-i</term> - <listitem><para>Incremental mode; tar files are only backed + backups. </p></dd><dt><span class="term">-i</span></dt><dd><p>Incremental mode; tar files are only backed up if they have the archive bit set. The archive bit is reset - after each file is read. </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-r</term> - <listitem><para>Restore. Files are restored to the share - from the tar file. </para></listitem> - </varlistentry> - - - - <varlistentry> - <term>-l log level</term> - <listitem><para>Log (debug) level. Corresponds to the - <parameter moreinfo="none">-d</parameter> flag of <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>.</para></listitem> - </varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>ENVIRONMENT VARIABLES</title> - - <para>The <parameter moreinfo="none">$TAPE</parameter> variable specifies the + after each file is read. </p></dd><dt><span class="term">-r</span></dt><dd><p>Restore. Files are restored to the share + from the tar file. </p></dd><dt><span class="term">-l log level</span></dt><dd><p>Log (debug) level. Corresponds to the + <i class="parameter"><tt>-d</tt></i> flag of <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The <i class="parameter"><tt>$TAPE</tt></i> variable specifies the default tape device to write to. May be overridden - with the -t option. </para> -</refsect1> - - -<refsect1> - <title>BUGS</title> - - <para>The <command moreinfo="none">smbtar</command> script has different - options from ordinary tar and from smbclient's tar command. </para> - -</refsect1> - -<refsect1> - <title>CAVEATS</title> - - <para>Sites that are more careful about security may not like + with the -t option. </p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>The <b class="command">smbtar</b> script has different + options from ordinary tar and from smbclient's tar command. </p></div><div class="refsect1" lang="en"><h2>CAVEATS</h2><p>Sites that are more careful about security may not like the way the script handles PC passwords. Backup and restore work on entire shares; should work on file lists. smbtar works best - with GNU tar and may not work well with other versions. </para> -</refsect1> - - -<refsect1> - <title>DIAGNOSTICS</title> - - <para>See the <emphasis>DIAGNOSTICS</emphasis> section for the <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry> command.</para> -</refsect1> - - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry>, <citerefentry> - <refentrytitle>smbclient</refentrytitle><manvolnum>1</manvolnum> - </citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry>.</para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + with GNU tar and may not work well with other versions. </p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>See the <span class="emphasis"><em>DIAGNOSTICS</em></span> section for the <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a> command.</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="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a href="smbclient.1.html"><span class="citerefentry"><span class="refentrytitle">smbclient</span>(1)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</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 - to the way the Linux kernel is developed.</para> - -<para><ulink url="mailto:poultenr@logica.co.uk">Ricky Poulten</ulink> - wrote the tar extension and this man page. The <command moreinfo="none">smbtar</command> - script was heavily rewritten and improved by <ulink url="mailto:Martin.Kraemer@mch.sni.de">Martin Kraemer</ulink>. Many + to the way the Linux kernel is developed.</p><p><a href="mailto:poultenr@logica.co.uk" target="_top">Ricky Poulten</a> + wrote the tar extension and this man page. The <b class="command">smbtar</b> + script was heavily rewritten and improved by <a href="mailto:Martin.Kraemer@mch.sni.de" target="_top">Martin Kraemer</a>. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/smbtree.1.html b/docs/htmldocs/smbtree.1.html index fdecb1c1c0..26120161d5 100644 --- a/docs/htmldocs/smbtree.1.html +++ b/docs/htmldocs/smbtree.1.html @@ -31,7 +31,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="id2796654"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796642"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 0221202644..f0aa0f974d 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -1,79 +1,16 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="smbumount.8"> - -<refmeta> - <refentrytitle>smbumount</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>smbumount</refname> - <refpurpose>smbfs umount for normal users</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">smbumount</command> - <arg rep="norepeat" choice="req">mount-point</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>With this program, normal users can unmount smb-filesystems, - provided that it is suid root. <command moreinfo="none">smbumount</command> has +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbumount</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="smbumount.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>smbumount — smbfs umount for normal users</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">smbumount</tt> {mount-point}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>With this program, normal users can unmount smb-filesystems, + provided that it is suid root. <b class="command">smbumount</b> has been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount program works perfectly well, but it would certainly be problematic - to make umount setuid root.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>mount-point</term> - <listitem><para>The directory to unmount.</para></listitem> - </varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>SEE ALSO</title> - - <para><citerefentry><refentrytitle>smbmount</refentrytitle> - <manvolnum>8</manvolnum></citerefentry></para> -</refsect1> - - -<refsect1> - <title>AUTHOR</title> - - <para>Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.</para> - - <para>The current maintainer of smbfs and the userspace - tools <command moreinfo="none">smbmount</command>, <command moreinfo="none">smbumount</command>, - and <command moreinfo="none">smbmnt</command> is <ulink url="mailto:urban@teststation.com">Urban Widmark</ulink>. - The <ulink url="mailto:samba@samba.org">SAMBA Mailing list</ulink> + to make umount setuid root.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">mount-point</span></dt><dd><p>The directory to unmount.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbmount.8.html"><span class="citerefentry"><span class="refentrytitle">smbmount</span>(8)</span></a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.</p><p>The current maintainer of smbfs and the userspace + tools <b class="command">smbmount</b>, <b class="command">smbumount</b>, + and <b class="command">smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>. + The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a> is the preferred place to ask questions regarding these programs. - </para> - - <para>The conversion of this manpage for Samba 2.2 was performed + </p><p>The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html new file mode 100644 index 0000000000..47f19abb70 --- /dev/null +++ b/docs/htmldocs/speed.html @@ -0,0 +1,140 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 39. Samba Performance Tuning</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="Part VI. Appendixes"><link rel="previous" href="Other-Clients.html" title="Chapter 38. Samba and other CIFS clients"><link rel="next" href="DNSDHCP.html" title="Chapter 40. DNS and DHCP Configuration Guide"></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 39. Samba Performance Tuning</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a> </td><th width="60%" align="center">Part VI. Appendixes</th><td width="20%" align="right"> <a accesskey="n" href="DNSDHCP.html">Next</a></td></tr></table><hr></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"><<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="speed.html#id2964209">Comparisons</a></dt><dt><a href="speed.html#id2964253">Socket options</a></dt><dt><a href="speed.html#id2964343">Read size</a></dt><dt><a href="speed.html#id2964393">Max xmit</a></dt><dt><a href="speed.html#id2964453">Log level</a></dt><dt><a href="speed.html#id2964483">Read raw</a></dt><dt><a href="speed.html#id2964567">Write raw</a></dt><dt><a href="speed.html#id2964630">Slow Logins</a></dt><dt><a href="speed.html#id2964659">Client tuning</a></dt><dt><a href="speed.html#id2964684">Samba performance problem due changing kernel</a></dt><dt><a href="speed.html#id2964716">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="id2964209"></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 +programs for file transfer that use TCP are ftp or another TCP based +SMB server. +</p><p> +If you want to test against something like a NT or WfWg server then +you will have to disable all but TCP on either the client or +server. Otherwise you may well be using a totally different protocol +(such as NetBEUI) and comparisons may not be valid. +</p><p> +Generally you should find that Samba performs similarly to ftp at raw +transfer speed. It should perform quite a bit faster than NFS, +although this very much depends on your system. +</p><p> +Several people have done comparisons between Samba and Novell, NFS or +WinNT. In some cases Samba performed the best, in others the worst. I +suspect the biggest factor is not Samba vs some other system but the +hardware and drivers used on the various systems. Given similar +hardware Samba should certainly be competitive in speed with other +systems. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964253"></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="id2964287"></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 +performance, but getting them wrong can degrade it by just as +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="id2964323"></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="id2964343"></a>Read size</h2></div></div><div></div></div><p> +The option <a class="indexterm" name="id2964353"></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 +the data before it has received the whole packet from the network, or +in the case of SMBreadbraw, it begins writing to the network before +all the data has been read from disk. +</p><p> +This overlapping works best when the speeds of disk and network access +are similar, having very little effect when the speed of one is much +greater than the other. +</p><p> +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="id2964393"></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="id2964414"></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 +honours this limit. +</p><p> +It defaults to 65536 bytes (the maximum), but it is possible that some +clients may perform better with a smaller transmit unit. Trying values +of less than 2048 is likely to cause severe problems. +</p><p> +In 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="id2964453"></a>Log level</h2></div></div><div></div></div><p> +If you set the log level (also known as <a class="indexterm" name="id2964463"></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="id2964483"></a>Read raw</h2></div></div><div></div></div><p> +The <a class="indexterm" name="id2964492"></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="id2964510"></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="id2964528"></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="id2964549"></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="id2964567"></a>Write raw</h2></div></div><div></div></div><p> +The <a class="indexterm" name="id2964577"></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="id2964594"></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="id2964613"></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="id2964630"></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="id2964641"></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="id2964659"></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.html" 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="id2964684"></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 +many of you will probably say that move to vanilla sources...well I tried +it too and it didn't work. I have 100mb LAN and two computers (linux + +Windows2000). Linux server shares directory with DivX files, client +(windows2000) plays them via LAN. Before when I was running 2.4.19 kernel +everything was fine, but now movies freezes and stops...I tried moving +files between server and Windows and it's terribly slow. +</p><p> +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="id2964716"></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. +But today all shares went SLOW; very slow. Also the main smbd kept +spawning new processes so we had 1600+ running smbd's (normally we avg. 250). +It crashed the SUN E3500 cluster twice. After a lot of searching I +decided to <b class="command">rm /var/locks/*.tdb</b>. Happy again. +</p><p> +Q1) Is there any method of keeping the *.tdb files in top condition or +how to early detect corruption? +</p><p> +A1) Yes, run <b class="command">tdbbackup</b> each time after stopping nmbd and before starting nmbd. +</p><p> +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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Other-Clients.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Appendixes.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="DNSDHCP.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 38. Samba and other CIFS clients </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 40. DNS and DHCP Configuration Guide</td></tr></table></div></body></html> diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 77027d0cda..33e595e0c3 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -1,287 +1,85 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="swat.8"> - -<refmeta> - <refentrytitle>swat</refentrytitle> - <manvolnum>8</manvolnum> -</refmeta> - - -<refnamediv> - <refname>swat</refname> - <refpurpose>Samba Web Administration Tool</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">swat</command> - <arg rep="norepeat" choice="opt">-s <smb config file></arg> - <arg rep="norepeat" choice="opt">-a</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - - <para><command moreinfo="none">swat</command> allows a Samba administrator to - configure the complex <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry> file via a Web browser. In addition, - a <command moreinfo="none">swat</command> configuration page has help links - to all the configurable options in the <filename moreinfo="none">smb.conf</filename> file allowing an - administrator to easily look up the effects of any change. </para> - - <para><command moreinfo="none">swat</command> is run from <command moreinfo="none">inetd</command> </para> -</refsect1> - - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-s smb configuration file</term> - <listitem><para>The default configuration file path is +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>swat</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="swat.8"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>swat — Samba Web Administration Tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">swat</tt> [-s <smb config file>] [-a]</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">swat</b> allows a Samba administrator to + configure the complex <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file via a Web browser. In addition, + a <b class="command">swat</b> configuration page has help links + to all the configurable options in the <tt class="filename">smb.conf</tt> file allowing an + administrator to easily look up the effects of any change. </p><p><b class="command">swat</b> is run from <b class="command">inetd</b> </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s smb configuration file</span></dt><dd><p>The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> server. This is the file - that <command moreinfo="none">swat</command> will modify. + the configuration details required by the <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> server. This is the file + that <b class="command">swat</b> will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. - See <filename moreinfo="none">smb.conf</filename> for more information. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>-a</term> - <listitem><para>This option disables authentication and puts - <command moreinfo="none">swat</command> in demo mode. In that mode anyone will be able to modify - the <filename moreinfo="none">smb.conf</filename> file. </para> - - <para><emphasis>WARNING: Do NOT enable this option on a production - server. </emphasis></para></listitem> - </varlistentry> - - - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-s <configuration file></term> -<listitem><para>The file specified contains the + See <tt class="filename">smb.conf</tt> for more information. + </p></dd><dt><span class="term">-a</span></dt><dd><p>This option disables authentication and puts + <b class="command">swat</b> in demo mode. In that mode anyone will be able to modify + the <tt class="filename">smb.conf</tt> file. </p><p><span class="emphasis"><em>WARNING: Do NOT enable this option on a production + server. </em></span></p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See <filename moreinfo="none">smb.conf</filename> for more information. +to provide. See <tt class="filename">smb.conf</tt> for more information. The default configuration file name is determined at -compile time.</para></listitem> -</varlistentry> - -<varlistentry> -<term>-d|--debug=debuglevel</term> -<listitem> -<para><replaceable>debuglevel</replaceable> is an integer +compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i class="replaceable"><tt>debuglevel</tt></i> is an integer from 0 to 10. The default value if this parameter is -not specified is zero.</para> - -<para>The higher this value, the more detail will be +not specified is zero.</p><p>The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.</para> - -<para>Levels above 1 will generate considerable +information about operations carried out.</p><p>Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.</para> - -<para>Note that specifying this parameter here will -override the <indexterm><primary>log level</primary></indexterm><parameter moreinfo="none">log level</parameter> parameter -in the <filename moreinfo="none">smb.conf</filename> file.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term>-l|--logfile=logbasename</term> -<listitem><para>File name for log/debug files. The extension -<constant>".client"</constant> will be appended. The log file is +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 +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. -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - - </variablelist> - -</refsect1> - -<refsect1> - - <title>INSTALLATION</title> - - <para>Swat is included as binary package with most distributions. The +</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 package manager in this case takes care of the installation and configuration. This section is only for those who have compiled swat from scratch. - </para> - - <para>After you compile SWAT you need to run <command moreinfo="none">make install - </command> to install the <command moreinfo="none">swat</command> binary + </p><p>After you compile SWAT you need to run <b class="command">make install + </b> to install the <b class="command">swat</b> binary and the various help files and images. A default install would put - these in: </para> - - <itemizedlist> - <listitem><para>/usr/local/samba/bin/swat</para></listitem> - <listitem><para>/usr/local/samba/swat/images/*</para></listitem> - <listitem><para>/usr/local/samba/swat/help/*</para></listitem> - </itemizedlist> - - <refsect2> - <title>Inetd Installation</title> - - <para>You need to edit your <filename moreinfo="none">/etc/inetd.conf - </filename> and <filename moreinfo="none">/etc/services</filename> - to enable SWAT to be launched via <command moreinfo="none">inetd</command>.</para> - - <para>In <filename moreinfo="none">/etc/services</filename> you need to - add a line like this: </para> - - <para><command moreinfo="none">swat 901/tcp</command></para> - - <para>Note for NIS/YP and LDAP users - you may need to rebuild the - NIS service maps rather than alter your local <filename moreinfo="none"> - /etc/services</filename> file. </para> - - <para>the choice of port number isn't really important + these in: </p><div class="itemizedlist"><ul type="disc"><li><p>/usr/local/samba/bin/swat</p></li><li><p>/usr/local/samba/swat/images/*</p></li><li><p>/usr/local/samba/swat/help/*</p></li></ul></div><div class="refsect2" lang="en"><h3>Inetd Installation</h3><p>You need to edit your <tt class="filename">/etc/inetd.conf + </tt> and <tt class="filename">/etc/services</tt> + to enable SWAT to be launched via <b class="command">inetd</b>.</p><p>In <tt class="filename">/etc/services</tt> you need to + add a line like this: </p><p><b class="command">swat 901/tcp</b></p><p>Note for NIS/YP and LDAP users - you may need to rebuild the + NIS service maps rather than alter your local <tt class="filename"> + /etc/services</tt> file. </p><p>the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your - <command moreinfo="none">inetd</command> daemon). </para> - - <para>In <filename moreinfo="none">/etc/inetd.conf</filename> you should - add a line like this: </para> - - <para><command moreinfo="none">swat stream tcp nowait.400 root - /usr/local/samba/bin/swat swat</command></para> - - <para>One you have edited <filename moreinfo="none">/etc/services</filename> - and <filename moreinfo="none">/etc/inetd.conf</filename> you need to send a - HUP signal to inetd. To do this use <command moreinfo="none">kill -1 PID - </command> where PID is the process ID of the inetd daemon. </para> - - </refsect2> - - - -</refsect1> - -<refsect1> - <title>LAUNCHING</title> - - <para>To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/".</para> - - <para>Note that you can attach to SWAT from any IP connected + <b class="command">inetd</b> daemon). </p><p>In <tt class="filename">/etc/inetd.conf</tt> you should + add a line like this: </p><p><b class="command">swat stream tcp nowait.400 root + /usr/local/samba/bin/swat swat</b></p><p>One you have edited <tt class="filename">/etc/services</tt> + 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 "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. </para> -</refsect1> - -<refsect1> - <title>FILES</title> - - <variablelist> - <varlistentry> - <term><filename moreinfo="none">/etc/inetd.conf</filename></term> - <listitem><para>This file must contain suitable startup - information for the meta-daemon.</para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/etc/services</filename></term> - <listitem><para>This file must contain a mapping of service name + 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 + information for the meta-daemon.</p></dd><dt><span class="term"><tt class="filename">/etc/services</tt></span></dt><dd><p>This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type - (e.g., tcp). </para></listitem> - </varlistentry> - - <varlistentry> - <term><filename moreinfo="none">/usr/local/samba/lib/smb.conf</filename></term> - <listitem><para>This is the default location of the <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> server configuration file that swat edits. Other - common places that systems install this file are <filename moreinfo="none"> - /usr/samba/lib/smb.conf</filename> and <filename moreinfo="none">/etc/smb.conf - </filename>. This file describes all the services the server - is to make available to clients. </para></listitem> - </varlistentry> - </variablelist> -</refsect1> - - -<refsect1> - <title>WARNINGS</title> - - <para><command moreinfo="none">swat</command> will rewrite your <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file. It will rearrange the entries and delete all - comments, <parameter moreinfo="none">include=</parameter> and <parameter moreinfo="none">copy= - </parameter> options. If you have a carefully crafted <filename moreinfo="none"> - smb.conf</filename> then back it up or don't use swat! </para> -</refsect1> - - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><command moreinfo="none">inetd(5)</command>, <citerefentry> - <refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry>, <citerefentry><refentrytitle>smb.conf</refentrytitle> - <manvolnum>5</manvolnum></citerefentry></para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + (e.g., tcp). </p></dd><dt><span class="term"><tt class="filename">/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> server configuration file that swat edits. Other + common places that systems install this file are <tt class="filename"> + /usr/samba/lib/smb.conf</tt> and <tt class="filename">/etc/smb.conf + </tt>. This file describes all the services the server + is to make available to clients. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>WARNINGS</h2><p><b class="command">swat</b> will rewrite your <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file. It will rearrange the entries and delete all + comments, <i class="parameter"><tt>include=</tt></i> and <i class="parameter"><tt>copy= + </tt></i> options. If you have a carefully crafted <tt class="filename"> + smb.conf</tt> then back it up or don't use swat! </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><b class="command">inetd(5)</b>, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 03adba0f38..3732b53f4c 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -1,203 +1,51 @@ -<?xml version="1.0"?> - -<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ - - <!ENTITY % globalentities SYSTEM 'global.ent'> %globalentities; - ]> -<refentry id="testparm.1"> - -<refmeta> - <refentrytitle>testparm</refentrytitle> - <manvolnum>1</manvolnum> -</refmeta> - - -<refnamediv> - <refname>testparm</refname> - <refpurpose>check an smb.conf configuration file for - internal correctness</refpurpose> -</refnamediv> - -<refsynopsisdiv> - <cmdsynopsis sepchar=" "> - <command moreinfo="none">testparm</command> - <arg rep="norepeat" choice="opt">-s</arg> - <arg rep="norepeat" choice="opt">-h</arg> - <arg rep="norepeat" choice="opt">-v</arg> - <arg rep="norepeat" choice="opt">-L <servername></arg> - <arg rep="norepeat" choice="opt">-t <encoding></arg> - <arg rep="norepeat" choice="req">config filename</arg> - <arg rep="norepeat" choice="opt">hostname hostIP</arg> - </cmdsynopsis> -</refsynopsisdiv> - -<refsect1> - <title>DESCRIPTION</title> - - <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle> - <manvolnum>7</manvolnum></citerefentry> suite.</para> - - <para><command moreinfo="none">testparm</command> is a very simple test program - to check an <citerefentry><refentrytitle>smbd</refentrytitle> - <manvolnum>8</manvolnum></citerefentry> configuration file for +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testparm</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="testparm.1"></a><div class="titlepage"><div></div><div></div></div><div class="refnamediv"><h2>Name</h2><p>testparm — check an smb.conf configuration file for + internal correctness</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt class="command">testparm</tt> [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]</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">testparm</b> is a very simple test program + to check an <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> configuration file for internal correctness. If this program reports no problems, you - can use the configuration file with confidence that <command moreinfo="none">smbd - </command> will successfully load the configuration file.</para> - - - <para>Note that this is <emphasis>NOT</emphasis> a guarantee that + can use the configuration file with confidence that <b class="command">smbd + </b> will successfully load the configuration file.</p><p>Note that this is <span class="emphasis"><em>NOT</em></span> a guarantee that the services specified in the configuration file will be - available or will operate as expected. </para> - - <para>If the optional host name and host IP address are + available or will operate as expected. </p><p>If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host - has access to each service. </para> - - <para>If <command moreinfo="none">testparm</command> finds an error in the <filename moreinfo="none"> - smb.conf</filename> file it returns an exit code of 1 to the calling + has access to each service. </p><p>If <b class="command">testparm</b> finds an error in the <tt class="filename"> + smb.conf</tt> file it returns an exit code of 1 to the calling program, else it returns an exit code of 0. This allows shell scripts - to test the output from <command moreinfo="none">testparm</command>.</para> -</refsect1> - -<refsect1> - <title>OPTIONS</title> - - <variablelist> - <varlistentry> - <term>-s</term> - <listitem><para>Without this option, <command moreinfo="none">testparm</command> + to test the output from <b class="command">testparm</b>.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s</span></dt><dd><p>Without this option, <b class="command">testparm</b> will prompt for a carriage return after printing the service - names and before dumping the service definitions.</para></listitem> - </varlistentry> - - -<varlistentry> -<term>-h|--help</term> -<listitem><para>Print a summary of command line options. -</para></listitem> -</varlistentry> - -<varlistentry> -<term>-V</term> -<listitem><para>Prints the version number for -<command moreinfo="none">smbd</command>.</para></listitem> -</varlistentry> - - <varlistentry> - <term>-L servername</term> - <listitem><para>Sets the value of the %L macro to <replaceable>servername</replaceable>. + names and before dumping the service definitions.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options. +</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for +<b class="command">smbd</b>.</p></dd><dt><span class="term">-L servername</span></dt><dd><p>Sets the value of the %L macro to <i class="replaceable"><tt>servername</tt></i>. This is useful for testing include files specified with the - %L macro. </para></listitem> - </varlistentry> - - <varlistentry> - <term>-v</term> - <listitem><para>If this option is specified, testparm - will also output all options that were not used in <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> and are thus set to their defaults.</para></listitem> - </varlistentry> - - <varlistentry> - <term>-t encoding</term> - <listitem><para> + %L macro. </p></dd><dt><span class="term">-v</span></dt><dd><p>If this option is specified, testparm + will also output all options that were not used in <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> and are thus set to their defaults.</p></dd><dt><span class="term">-t encoding</span></dt><dd><p> Output data in specified encoding. - </para></listitem> - </varlistentry> - - <varlistentry> - <term>configfilename</term> - <listitem><para>This is the name of the configuration file + </p></dd><dt><span class="term">configfilename</span></dt><dd><p>This is the name of the configuration file to check. If this parameter is not present then the - default <citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file will be checked. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term>hostname</term> - <listitem><para>If this parameter and the following are - specified, then <command moreinfo="none">testparm</command> will examine the <parameter moreinfo="none">hosts - allow</parameter> and <parameter moreinfo="none">hosts deny</parameter> - parameters in the <citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry> file to + default <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file will be checked. + </p></dd><dt><span class="term">hostname</span></dt><dd><p>If this parameter and the following are + specified, then <b class="command">testparm</b> will examine the <i class="parameter"><tt>hosts + allow</tt></i> and <i class="parameter"><tt>hosts deny</tt></i> + parameters in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file to determine if the hostname with this IP address would be - allowed access to the <command moreinfo="none">smbd</command> server. If + allowed access to the <b class="command">smbd</b> server. If this parameter is supplied, the hostIP parameter must also - be supplied.</para></listitem> - </varlistentry> - - - <varlistentry> - <term>hostIP</term> - <listitem><para>This is the IP address of the host specified + be supplied.</p></dd><dt><span class="term">hostIP</span></dt><dd><p>This is the IP address of the host specified in the previous parameter. This address must be supplied - if the hostname parameter is supplied. </para></listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>FILES</title> - - <variablelist> - <varlistentry> - <term><citerefentry><refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry></term> - <listitem><para>This is usually the name of the configuration - file used by <citerefentry><refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry>. - </para></listitem> - </varlistentry> - </variablelist> -</refsect1> - -<refsect1> - <title>DIAGNOSTICS</title> - - <para>The program will issue a message saying whether the + if the hostname parameter is supplied. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a></span></dt><dd><p>This is usually the name of the configuration + file used by <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a>. + </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>The program will issue a message saying whether the configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details - to stdout. </para> -</refsect1> - - -<refsect1> - <title>VERSION</title> - - <para>This man page is correct for version 3.0 of - the Samba suite.</para> -</refsect1> - -<refsect1> - <title>SEE ALSO</title> - <para><citerefentry> - <refentrytitle>smb.conf</refentrytitle><manvolnum>5</manvolnum> - </citerefentry>, <citerefentry> - <refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum> - </citerefentry></para> -</refsect1> - -<refsect1> - <title>AUTHOR</title> - - <para>The original Samba software and related utilities + to stdout. </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="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</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 - to the way the Linux kernel is developed.</para> - - <para>The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> - ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top"> + ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.</para> -</refsect1> - -</refentry> + for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html> diff --git a/docs/htmldocs/troubleshooting.html b/docs/htmldocs/troubleshooting.html new file mode 100644 index 0000000000..d18399caeb --- /dev/null +++ b/docs/htmldocs/troubleshooting.html @@ -0,0 +1 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part V. Troubleshooting</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="samba-doc.html" title="SAMBA Project Documentation"><link rel="previous" href="SWAT.html" title="Chapter 32. SWAT - The Samba Web Administration Tool"><link rel="next" href="diagnosis.html" title="Chapter 33. The Samba checklist"></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">Part V. Troubleshooting</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SWAT.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="diagnosis.html">Next</a></td></tr></table><hr></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.html">The Samba checklist</a></dt><dd><dl><dt><a href="diagnosis.html#id2957982">Introduction</a></dt><dt><a href="diagnosis.html#id2958022">Assumptions</a></dt><dt><a href="diagnosis.html#id2958249">The tests</a></dt></dl></dd><dt>34. <a href="problems.html">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="problems.html#id2959747">Diagnostics tools</a></dt><dd><dl><dt><a href="problems.html#id2959768">Debugging with Samba itself</a></dt><dt><a href="problems.html#id2959894">Tcpdump</a></dt><dt><a href="problems.html#id2959915">Ethereal</a></dt><dt><a href="problems.html#id2959968">The Windows Network Monitor</a></dt></dl></dd><dt><a href="problems.html#id2960285">Useful URLs</a></dt><dt><a href="problems.html#id2960326">Getting help from the mailing lists</a></dt><dt><a href="problems.html#id2960484">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="bugreport.html">Reporting Bugs</a></dt><dd><dl><dt><a href="bugreport.html#id2960613">Introduction</a></dt><dt><a href="bugreport.html#id2960681">General info</a></dt><dt><a href="bugreport.html#id2960718">Debug levels</a></dt><dt><a href="bugreport.html#id2960926">Internal errors</a></dt><dt><a href="bugreport.html#id2961060">Attaching to a running process</a></dt><dt><a href="bugreport.html#id2961107">Patches</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SWAT.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-doc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="diagnosis.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 32. SWAT - The Samba Web Administration Tool </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 33. The Samba checklist</td></tr></table></div></body></html> diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html new file mode 100644 index 0000000000..5322995de4 --- /dev/null +++ b/docs/htmldocs/type.html @@ -0,0 +1,5 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part II. Server Configuration Basics</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="samba-doc.html" title="SAMBA Project Documentation"><link rel="previous" href="FastStart.html" title="Chapter 3. Fast Start for the Impatient"><link rel="next" href="ServerType.html" title="Chapter 4. Server Types and Security Modes"></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">Part II. Server Configuration Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FastStart.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ServerType.html">Next</a></td></tr></table><hr></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="id2884814"></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.html">Server Types and Security Modes</a></dt><dd><dl><dt><a href="ServerType.html#id2884977">Features and Benefits</a></dt><dt><a href="ServerType.html#id2885071">Server Types</a></dt><dt><a href="ServerType.html#id2885157">Samba Security Modes</a></dt><dd><dl><dt><a href="ServerType.html#id2885276">User Level Security</a></dt><dt><a href="ServerType.html#id2885414">Share Level Security</a></dt><dt><a href="ServerType.html#id2885551">Domain Security Mode (User Level Security)</a></dt><dt><a href="ServerType.html#id2885808">ADS Security Mode (User Level Security)</a></dt><dt><a href="ServerType.html#id2885909">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="ServerType.html#id2886191">Password checking</a></dt><dt><a href="ServerType.html#id2886386">Common Errors</a></dt><dd><dl><dt><a href="ServerType.html#id2886414">What makes Samba a SERVER?</a></dt><dt><a href="ServerType.html#id2886453">What makes Samba a Domain Controller?</a></dt><dt><a href="ServerType.html#id2886490">What makes Samba a Domain Member?</a></dt><dt><a href="ServerType.html#id2886529">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="samba-pdc.html">Domain Control</a></dt><dd><dl><dt><a href="samba-pdc.html#id2886861">Features and Benefits</a></dt><dt><a href="samba-pdc.html#id2887076">Basics of Domain Control</a></dt><dd><dl><dt><a href="samba-pdc.html#id2887090">Domain Controller Types</a></dt><dt><a href="samba-pdc.html#id2887335">Preparing for Domain Control</a></dt></dl></dd><dt><a href="samba-pdc.html#id2887717">Domain Control - Example Configuration</a></dt><dt><a href="samba-pdc.html#id2888205">Samba ADS Domain Control</a></dt><dt><a href="samba-pdc.html#id2888257">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="samba-pdc.html#id2888272">Domain Network Logon Service</a></dt><dt><a href="samba-pdc.html#id2888704">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="samba-pdc.html#id2888850">Common Errors</a></dt><dd><dl><dt><a href="samba-pdc.html#id2888857">'$' cannot be included in machine name</a></dt><dt><a href="samba-pdc.html#id2888916">Joining domain fails because of existing machine account</a></dt><dt><a href="samba-pdc.html#id2888975">The system can not log you on (C000019B)....</a></dt><dt><a href="samba-pdc.html#id2889059">The machine trust account not accessible</a></dt><dt><a href="samba-pdc.html#id2889131">Account disabled</a></dt><dt><a href="samba-pdc.html#id2889164">Domain Controller Unavailable</a></dt><dt><a href="samba-pdc.html#id2889186">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="samba-bdc.html">Backup Domain Control</a></dt><dd><dl><dt><a href="samba-bdc.html#id2889347">Features And Benefits</a></dt><dt><a href="samba-bdc.html#id2889536">Essential Background Information</a></dt><dd><dl><dt><a href="samba-bdc.html#id2889565">MS Windows NT4 Style Domain Control</a></dt><dt><a href="samba-bdc.html#id2889816">Active Directory Domain Control</a></dt><dt><a href="samba-bdc.html#id2889836">What qualifies a Domain Controller on the network?</a></dt><dt><a href="samba-bdc.html#id2889863">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2889908">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="samba-bdc.html#id2890011">Example Configuration</a></dt></dl></dd><dt><a href="samba-bdc.html#id2890167">Common Errors</a></dt><dd><dl><dt><a href="samba-bdc.html#id2890181">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="samba-bdc.html#id2890212">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="samba-bdc.html#id2890238">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2890283">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="domain-member.html">Domain Membership</a></dt><dd><dl><dt><a href="domain-member.html#id2890490">Features and Benefits</a></dt><dt><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="domain-member.html#id2890821">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="domain-member.html#id2891126">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="domain-member.html#id2891341">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="domain-member.html#id2891414">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="domain-member.html#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="domain-member.html#id2891624">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="domain-member.html#id2892061">Why is this better than security = server?</a></dt></dl></dd><dt><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="domain-member.html#id2892246">Setup your smb.conf</a></dt><dt><a href="domain-member.html#id2892373">Setup your /etc/krb5.conf</a></dt><dt><a href="domain-member.html#ads-create-machine-account">Create the computer account</a></dt><dt><a href="domain-member.html#ads-test-server">Test your server setup</a></dt><dt><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="domain-member.html#id2892751">Notes</a></dt></dl></dd><dt><a href="domain-member.html#id2892773">Common Errors</a></dt><dd><dl><dt><a href="domain-member.html#id2892816">Can Not Add Machine Back to Domain</a></dt><dt><a href="domain-member.html#id2892848">Adding Machine to Domain Fails</a></dt><dt><a href="domain-member.html#id2892992">I can't join a Windows 2003 PDC</a></dt></dl></dd></dl></dd><dt>8. <a href="StandAloneServer.html">Stand-Alone Servers</a></dt><dd><dl><dt><a href="StandAloneServer.html#id2893079">Features and Benefits</a></dt><dt><a href="StandAloneServer.html#id2893117">Background</a></dt><dt><a href="StandAloneServer.html#id2893191">Example Configuration</a></dt><dd><dl><dt><a href="StandAloneServer.html#RefDocServer">Reference Documentation Server</a></dt><dt><a href="StandAloneServer.html#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="StandAloneServer.html#id2893714">Common Errors</a></dt></dl></dd><dt>9. <a href="ClientConfig.html">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="ClientConfig.html#id2893778">Note</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FastStart.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-doc.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ServerType.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Fast Start for the Impatient </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Server Types and Security Modes</td></tr></table></div></body></html> diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html new file mode 100644 index 0000000000..a4f568576d --- /dev/null +++ b/docs/htmldocs/unicode.html @@ -0,0 +1,67 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 27. Unicode/Charsets</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="integrate-ms-networks.html" title="Chapter 26. Integrating MS Windows networks with Samba"><link rel="next" href="Backup.html" title="Chapter 28. Samba Backup Techniques"></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 27. Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="Backup.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></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="unicode.html#id2953342">Features and Benefits</a></dt><dt><a href="unicode.html#id2953385">What are charsets and unicode?</a></dt><dt><a href="unicode.html#id2953454">Samba and charsets</a></dt><dt><a href="unicode.html#id2953583">Conversion from old names</a></dt><dt><a href="unicode.html#id2953612">Japanese charsets</a></dt><dt><a href="unicode.html#id2953751">Common errors</a></dt><dd><dl><dt><a href="unicode.html#id2953758">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="id2953342"></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 +ago it was common for software to be written for exclusive use in the country of +origin. +</p><p> +Of all the effort that has been brought to bear on providing native language support +for all computer users, the efforts of the <a href="http://www.openi18n.org/" target="_top">Openi18n organisation</a> is deserving of +special mention. +</p><p> +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="id2953385"></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) +</em></span> that is used. +A charset can be seen as a table that is used to translate numbers to +letters. Not all computers use the same charset (there are charsets +with German umlauts, Japanese characters, etc). Usually a charset contains +256 characters, which means that storing a character with it takes +exactly one byte. </p><p> +There are also charsets that support even more characters, +but those need twice(or even more) as much storage space. These +charsets can contain <b class="command">256 * 256 = 65536</b> characters, which +is more then all possible characters one could think of. They are called +multibyte charsets (because they use more then one byte to +store one character). +</p><p> + A standardised multibyte charset is <a href="http://www.unicode.org/" target="_top">unicode</a>. +A big advantage of using a multibyte charset is that you only need one; there +is no need to make sure two computers use the same charset when they are +communicating. +</p><p>Old windows clients use single-byte charsets, named +'codepages' by Microsoft. However, there is no support for +negotiating the charset to be used in the smb protocol. Thus, you +have to make sure you are using the same charset when talking to an 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="id2953454"></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="id2953476"></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="id2953514"></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="id2953548"></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="id2953583"></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="id2953612"></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="id2953633"></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="id2953663"></a><i class="parameter"><tt>dos charset</tt></i> = CP932, not +Shift_JIS, SJIS...</p></li><li><p>Currently only <a class="indexterm" name="id2953683"></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="id2953699"></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="id2953718"></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="id2953751"></a>Common errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953758"></a>CP850.so can't be found</h3></div></div><div></div></div><p>“<span class="quote">Samba is complaining about a missing <tt class="filename">CP850.so</tt> file</span>”.</p><p>CP850 is the default <a class="indexterm" name="id2953783"></a><i class="parameter"><tt>dos charset</tt></i>. The <a class="indexterm" name="id2953797"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Backup.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 26. Integrating MS Windows networks with Samba </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 28. Samba Backup Techniques</td></tr></table></div></body></html> diff --git a/docs/htmldocs/upgrading-to-3.0.html b/docs/htmldocs/upgrading-to-3.0.html new file mode 100644 index 0000000000..e7c1c61234 --- /dev/null +++ b/docs/htmldocs/upgrading-to-3.0.html @@ -0,0 +1,176 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="migration.html" title="Part IV. Migration and Updating"><link rel="previous" href="migration.html" title="Part IV. Migration and Updating"><link rel="next" href="NT4Migration.html" title="Chapter 31. Migration from NT4 PDC to Samba-3 PDC"></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 30. Upgrading from Samba-2.x to Samba-3.0.0</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="migration.html">Prev</a> </td><th width="60%" align="center">Part IV. Migration and Updating</th><td width="20%" align="right"> <a accesskey="n" href="NT4Migration.html">Next</a></td></tr></table><hr></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></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="upgrading-to-3.0.html#id2954094">New Features in Samba-3</a></dt><dt><a href="upgrading-to-3.0.html#id2954229">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2954244">Removed Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2954370">New Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2954767">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="upgrading-to-3.0.html#id2954842">New Functionality</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2954849">Databases</a></dt><dt><a href="upgrading-to-3.0.html#id2955083">Changes in Behavior</a></dt><dt><a href="upgrading-to-3.0.html#id2955133">Charsets</a></dt><dt><a href="upgrading-to-3.0.html#id2955156">Passdb Backends and Authentication</a></dt><dt><a href="upgrading-to-3.0.html#id2955274">Charsets</a></dt><dt><a href="upgrading-to-3.0.html#id2955299">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="id2954094"></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 + as a member server and authenticate users using LDAP/kerberos. + </p></li><li><p> + Unicode support. Samba will now negotiate UNICODE on the wire and + internally there is now a much better infrastructure for multi-byte + and UNICODE character sets. + </p></li><li><p> + New authentication system. The internal authentication system has + been almost completely rewritten. Most of the changes are internal, + but the new auth system is also very configurable. + </p></li><li><p> + New filename mangling system. The filename mangling system has been + completely rewritten. An internal database now stores mangling maps + persistently. This needs lots of testing. + </p></li><li><p> + New "net" command. A new "net" command has been added. It is + somewhat similar to the "net" command in windows. Eventually we + plan to replace a bunch of other utilities (such as smbpasswd) + with subcommands in "net", at the moment only a few things are + implemented. + </p></li><li><p> + Samba now negotiates NT-style status32 codes on the wire. This + improves error handling a lot. + </p></li><li><p> + Better Windows 2000/XP/2003 printing support including publishing + printer attributes in active directory + </p></li><li><p> + New loadable RPC modules + </p></li><li><p> + New dual-daemon winbindd support (-B) for better performance + </p></li><li><p> + Support for migrating from a Windows NT 4.0 domain to a Samba + domain and maintaining user, group and domain SIDs + </p></li><li><p> + Support for establishing trust relationships with Windows NT 4.0 + domain controllers + </p></li><li><p> + Initial support for a distributed Winbind architecture using + an LDAP directory for storing SID to uid/gid mappings + </p></li><li><p> + 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="id2954229"></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="id2954244"></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="id2954370"></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="id2954767"></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="id2954842"></a>New Functionality</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954849"></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="id2954868"></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="id2955083"></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> + When operating as a member of a Windows domain, Samba 2.2 would + map any users authenticated by the remote DC to the 'guest account' + if a uid could not be obtained via the getpwnam() call. Samba 3.0 + rejects the connection as NT_STATUS_LOGON_FAILURE. There is no + current work around to re-establish the 2.2 behavior. + </p></li><li><p> + When adding machines to a Samba 2.2 controlled domain, the + 'add user script' was used to create the UNIX identity of the + machine trust account. Samba 3.0 introduces a new 'add machine + 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="id2955133"></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.html" 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="id2955156"></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> + Encrypted passwords have been enabled by default in order to + inter-operate better with out-of-the-box Windows client + installations. This does mean that either (a) a samba account + 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="id2955194"></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="id2955217"></a><i class="parameter"><tt>auth methods</tt></i>) and account + storage backends + (<a class="indexterm" name="id2955232"></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.html" 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 + values actually mean in order to ensure Samba operates correctly. + </p><p> + 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="id2955274"></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.html" 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="id2955299"></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="id2955311"></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 + conversion script (examples/LDAP/convertSambaAccount) to modify and LDIF + file to the new schema. + </p><p> + Example: + </p><pre class="screen"> + <tt class="prompt">$ </tt>ldapsearch .... -b "ou=people,dc=..." > old.ldif + <tt class="prompt">$ </tt>convertSambaAccount <DOM SID> old.ldif new.ldif + </pre><p> + The <DOM SID> can be obtained by running 'net getlocalsid <DOMAINNAME> + on the Samba PDC as root. + </p><p> + The old sambaAccount schema may still be used by specifying the + "ldapsam_compat" passdb backend. However, the sambaAccount and + associated attributes have been moved to the historical section of + the schema file and must be uncommented before use if needed. + The 2.2 object class declaration for a sambaAccount has not changed + in the 3.0 samba.schema file. + </p><p> + Other new object classes and their uses include: + </p><div class="itemizedlist"><ul type="disc"><li><p> + sambaDomain - domain information used to allocate rids + for users and groups as necessary. The attributes are added + in 'ldap suffix' directory entry automatically if + an idmap uid/gid range has been set and the 'ldapsam' + passdb backend has been selected. + </p></li><li><p> + sambaGroupMapping - an object representing the + relationship between a posixGroup and a Windows + group/SID. These entries are stored in the 'ldap + group suffix' and managed by the 'net groupmap' command. + </p></li><li><p> + sambaUnixIdPool - created in the 'ldap idmap suffix' entry + automatically and contains the next available 'idmap uid' and + 'idmap gid' + </p></li><li><p> + 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="id2955433"></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. + </p><div class="itemizedlist"><ul type="disc"><li><p>ldap suffix - used to search for user and computer accounts</p></li><li><p>ldap user suffix - used to store user accounts</p></li><li><p>ldap machine suffix - used to store machine trust accounts</p></li><li><p>ldap group suffix - location of posixGroup/sambaGroupMapping entries</p></li><li><p>ldap idmap suffix - location of sambaIdmapEntry objects</p></li></ul></div><p> + If an 'ldap suffix' is defined, it will be appended to all of the + remaining sub-suffix parameters. In this case, the order of the suffix + listings in smb.conf is important. Always place the 'ldap suffix' first + in the list. + </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="id2955500"></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, + dc=org" partition. + </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><i class="parameter"><tt>idmap backend = ldap:ldap://onterose/</tt></i></td></tr><tr><td><i class="parameter"><tt>ldap idmap suffix = ou=idmap,dc=plainjoe,dc=org</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap uid = 40000-50000</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap gid = 40000-50000</tt></i></td></tr></table><p> + 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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="migration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="NT4Migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part IV. Migration and Updating </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 31. Migration from NT4 PDC to Samba-3 PDC</td></tr></table></div></body></html> diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 138ec374bd..561b3deb45 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -28,7 +28,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="id2796662"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796651"></a><i class="parameter"><tt>log level</tt></i> 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. diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html new file mode 100644 index 0000000000..1ee1de9f2f --- /dev/null +++ b/docs/htmldocs/winbind.html @@ -0,0 +1,721 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 21. Winbind: Use of Domain Accounts</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-doc.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="VFS.html" title="Chapter 20. Stackable VFS modules"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter 22. Advanced Network Management"></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 21. Winbind: Use of Domain Accounts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></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"><<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>></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"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>></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"><<a href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>></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"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a href="mailto:jht@samba.org">jht@samba.org</a>></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="winbind.html#id2941150">Features and Benefits</a></dt><dt><a href="winbind.html#id2941246">Introduction</a></dt><dt><a href="winbind.html#id2941324">What Winbind Provides</a></dt><dd><dl><dt><a href="winbind.html#id2941400">Target Uses</a></dt></dl></dd><dt><a href="winbind.html#id2941431">How Winbind Works</a></dt><dd><dl><dt><a href="winbind.html#id2941460">Microsoft Remote Procedure Calls</a></dt><dt><a href="winbind.html#id2941493">Microsoft Active Directory Services</a></dt><dt><a href="winbind.html#id2941516">Name Service Switch</a></dt><dt><a href="winbind.html#id2941652">Pluggable Authentication Modules</a></dt><dt><a href="winbind.html#id2941724">User and Group ID Allocation</a></dt><dt><a href="winbind.html#id2941757">Result Caching</a></dt></dl></dd><dt><a href="winbind.html#id2941785">Installation and Configuration</a></dt><dd><dl><dt><a href="winbind.html#id2941792">Introduction</a></dt><dt><a href="winbind.html#id2941859">Requirements</a></dt><dt><a href="winbind.html#id2941953">Testing Things Out</a></dt></dl></dd><dt><a href="winbind.html#id2943561">Conclusion</a></dt><dt><a href="winbind.html#id2943580">Common Errors</a></dt><dd><dl><dt><a href="winbind.html#id2943633">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="id2941150"></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. + </p><p> + There is one other facility without which UNIX and Microsoft Windows network + interoperability would suffer greatly. It is imperative that there be a + mechanism for sharing files across UNIX systems and to be able to assign + domain user and group ownerships with integrity. + </p><p> + <span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs + solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft + RPC calls, Pluggable Authentication Modules, and the Name Service Switch to + allow Windows NT domain users to appear and operate as UNIX users on a UNIX + machine. This chapter describes the winbind system, explaining the functionality + it provides, how it is configured, and how it works internally. + </p><p> + Winbind provides three separate functions: + </p><div class="itemizedlist"><ul type="disc"><li><p> + Authentication of user credentials (via PAM) + </p></li><li><p> + Identity resolution (via NSS)` + </p></li><li><p> + Windindd maintains a database called winbind_idmap.tdb in which it stores + mappings between UNIX UIDs / GIDs and NT SIDs. This mapping is used only + for users and groups that do not have a local UID/GID. It stored the UID/GID + allocated from the idmap uid/gid range that it has mapped to the NT SID. + If <i class="parameter"><tt>idmap backend</tt></i> has been specified as ldapsam:url + then instead of using a local mapping winbindd will obtain this information + from the LDAP database. + </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + 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="id2941246"></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 + manner.</p><p>One common solution in use today has been to create + identically named user accounts on both the UNIX and Windows systems + and use the Samba suite of programs to provide file and print services + between the two. This solution is far from perfect however, as + adding and deleting users on both sets of machines becomes a chore + and two sets of passwords are required both of which + can lead to synchronization problems between the UNIX and Windows + systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into + three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information + </p></li><li><p>Authenticating Windows NT users + </p></li><li><p>Password changing for Windows NT users + </p></li></ul></div><p>Ideally, a prospective solution to the unified logon problem + would satisfy all the above components without duplication of + information on the UNIX machines and without creating additional + tasks for the system administrator when maintaining users and + groups on either system. The winbind system provides a simple + and elegant solution to all three components of the unified logon + problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941324"></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 + to be used in much the same manner that NIS+ is used within + UNIX-only environments.</p><p>The end result is that whenever any + program on the UNIX machine asks the operating system to lookup + a user or group name, the query will be resolved by asking the + NT domain controller for the specified domain to do the lookup. + Because Winbind hooks into the operating system at a low level + (via the NSS name resolution modules in the C library) this + redirection to the NT domain controller is completely + transparent.</p><p>Users on the UNIX machine can then use NT user and group + names as they would use "native" UNIX names. They can chown files + so that they are owned by NT domain users or even login to the + UNIX machine and run a UNIX X-Window session as a domain user.</p><p>The only obvious indication that Winbind is being used is + that user and group names take the form DOMAIN\user and + DOMAIN\group. This is necessary as it allows Winbind to determine + that redirection to a domain controller is wanted for a particular + lookup and which trusted domain is being referenced.</p><p>Additionally, Winbind provides an authentication service + that hooks into the Pluggable Authentication Modules (PAM) system + to provide authentication via a NT domain to any PAM enabled + applications. This capability solves the problem of synchronizing + passwords between systems since all passwords are stored in a single + location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941400"></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 + maintain a separate account infrastructure. This greatly + simplifies the administrative overhead of deploying UNIX + workstations into a NT based organization.</p><p>Another interesting way in which we expect Winbind to + be used is as a central part of UNIX based appliances. Appliances + that provide file and print services to Microsoft based networks + will be able to use Winbind to provide seamless integration of + the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941431"></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="id2941460"></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 + Windows NT machines including remote management, user authentication + and print spooling. Although initially this work was done + to aid the implementation of Primary Domain Controller (PDC) + functionality in Samba, it has also yielded a body of code which + can be used for other purposes.</p><p>Winbind uses various MSRPC calls to enumerate domain users + and groups and to obtain detailed information about individual + users or groups. Other MSRPC calls can be used to authenticate + NT domain users and to change user passwords. By directly querying + a Windows PDC for user and group information, winbind maps the + NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941493"></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. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941516"></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 + UNIX workstation may resolve system information from a series of + flat files stored on the local filesystem. A networked workstation + may first attempt to resolve system information from local files, + and then consult a NIS database for user information or a DNS server + for hostname information.</p><p>The NSS application programming interface allows winbind + to present itself as a source of system information when + resolving UNIX usernames and groups. Winbind uses this interface, + and information obtained from a Windows NT server using MSRPC + calls to provide a new source of account enumeration. Using standard + UNIX library calls, one can enumerate the users and groups on + a UNIX machine running winbind and see all users and groups in + a NT domain plus any trusted domain as though they were local + users and groups.</p><p>The primary control file for NSS is + <tt class="filename">/etc/nsswitch.conf</tt>. + When a UNIX application makes a request to do a lookup + the C library looks in <tt class="filename">/etc/nsswitch.conf</tt> + for a line which matches the service type being requested, for + example the "passwd" service type is used when user or group names + are looked up. This config line specifies which implementations + of that service should be tried and in what order. If the passwd + config line is:</p><pre class="programlisting"> +passwd: files example + </pre><p>then the C library will first load a module called + <tt class="filename">/lib/libnss_files.so</tt> followed by + the module <tt class="filename">/lib/libnss_example.so</tt>. The + C library will dynamically load each of these modules in turn + and call resolver functions within the modules to try to resolve + the request. Once the request is resolved the C library returns the + result to the application.</p><p>This NSS interface provides a very easy way for Winbind + to hook into the operating system. All that needs to be done + is to put <tt class="filename">libnss_winbind.so</tt> in <tt class="filename">/lib/</tt> + then add "winbind" into <tt class="filename">/etc/nsswitch.conf</tt> at + the appropriate place. The C library will then call Winbind to + resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941652"></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 + having to recompile these applications. PAM is also useful + for implementing a particular policy for authorization. For example, + a system administrator may only allow console logins from users + stored in the local password file but only allow users resolved from + a NIS database to log in over the network.</p><p>Winbind uses the authentication management and password + management PAM interface to integrate Windows NT users into a + UNIX system. This allows Windows NT users to log in to a UNIX + machine and be authenticated against a suitable Primary Domain + Controller. These users can also change their passwords and have + this change take effect directly on the Primary Domain Controller. + </p><p>PAM is configured by providing control files in the directory + <tt class="filename">/etc/pam.d/</tt> for each of the services that + require authentication. When an authentication request is made + by an application the PAM code in the C library looks up this + control file to determine what modules to load to do the + authentication check and in what order. This interface makes adding + a new authentication service for Winbind very easy, all that needs + to be done is that the <tt class="filename">pam_winbind.so</tt> module + is copied to <tt class="filename">/lib/security/</tt> and the PAM + control files for relevant services are updated to allow + authentication via winbind. See the PAM documentation + for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941724"></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 + groups. It is winbind's job to convert RIDs to UNIX id numbers and + vice versa. When winbind is configured it is given part of the UNIX + user id space and a part of the UNIX group id space in which to + store Windows NT users and groups. If a Windows NT user is + resolved for the first time, it is allocated the next UNIX id from + the range. The same process applies for Windows NT groups. Over + time, winbind will have mapped all Windows NT users and groups + to UNIX user ids and group ids.</p><p>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="id2941757"></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 + by a PDC is cached by winbind along with a sequence number also + returned by the PDC. This sequence number is incremented by + Windows NT whenever any user or group information is modified. If + a cached entry has expired, the sequence number is requested from + the PDC and compared against the sequence number of the cached entry. + If the sequence numbers do not match, then the cached information + is discarded and up to date information is requested directly + from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941785"></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="id2941792"></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 +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services. +</p><div class="itemizedlist"><ul type="disc"><li><p> + <span class="emphasis"><em>Why should I to this?</em></span> + </p><p>This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. + </p></li><li><p> + <span class="emphasis"><em>Who should be reading this document?</em></span> + </p><p> + This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. + </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941859"></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 +contents!</em></span> If you haven't already made a boot disk, +<span class="emphasis"><em>MAKE ONE NOW!</em></span> +</p><p> +Messing with the PAM configuration files can make it nearly impossible +to log in to your machine. That's why you want to be able to boot back +into your machine in single user mode and restore your +<tt class="filename">/etc/pam.d</tt> back to the original state they were in if +you get frustrated with the way things are going. ;-) +</p><p> +The latest version of SAMBA (version 3.0 as of this writing), now +includes a functioning winbindd daemon. Please refer to the +<a href="http://samba.org/" target="_top">main SAMBA web page</a> or, +better yet, your closest SAMBA mirror site for instructions on +downloading the source code. +</p><p> +To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means <tt class="filename">pam-0.74-22</tt>. For best results, it is helpful to also +install the development packages in <tt class="filename">pam-devel-0.74-22</tt>. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941953"></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 +be running. To use PAM, you will want to make sure that you have the +standard PAM package which supplies the <tt class="filename">/etc/pam.d</tt> +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the <tt class="filename">/usr/doc</tt> +and <tt class="filename">/usr/man</tt> entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2942015"></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 +</p><p> +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>cp ../samba/source/nsswitch/libnss_winbind.so /lib</tt></b> +</pre><p> +</p><p> +I also found it necessary to make the following symbolic link: +</p><p> +<tt class="prompt">root# </tt> <b class="userinput"><tt>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</tt></b> +</p><p>And, in the case of Sun Solaris:</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</tt></b> +<tt class="prompt">root# </tt><b class="userinput"><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</tt></b> +</pre><p> +Now, as root you need to edit <tt class="filename">/etc/nsswitch.conf</tt> to +allow user and group entries to be visible from the <span class="application">winbindd</span> +daemon. My <tt class="filename">/etc/nsswitch.conf</tt> file look like +this after editing: +</p><pre class="programlisting"> + passwd: files winbind + shadow: files + group: files winbind +</pre><p> +The libraries needed by the winbind daemon will be automatically +entered into the <b class="command">ldconfig</b> cache the next time +your system reboots, but it +is faster (and you don't need to reboot) if you do it manually: +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>/sbin/ldconfig -v | grep winbind</tt></b> +</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="id2942224"></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 +should be named WINBIND. A stanza like the following: +</p><pre class="programlisting"> +WINBIND: + program = /usr/lib/security/WINBIND + options = authonly +</pre><p>can then be added to +<tt class="filename">/usr/lib/security/methods.cfg</tt>. This module only +supports identification, but there have been success reports using the +standard winbind pam module for authentication. Use caution configuring +loadable authentication modules as it is possible to make it impossible +to logon to the system. More information about the AIX authentication +module API can be found at "Kernel Extensions and Device Support +Programming Concepts for AIX": <a href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm" target="_top"> +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="id2942302"></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="id2942349"></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="id2942460"></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 +a domain user who has administrative privileges in the domain. +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</tt></b> +</p><p> +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="id2942516"></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 +portion first. To start up winbind services, enter the following +command as root: +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/local/samba/bin/winbindd</tt></b> +</p><p> +Winbindd can now also run in 'dual daemon mode'. This will make it +run as 2 processes. The first will answer all requests from the cache, +thus making responses to clients faster. The other will +update the cache for the query that the first has just responded. +Advantage of this is that responses stay accurate and are faster. +You can enable dual daemon mode by adding <tt class="option">-B</tt> to the commandline: +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/local/samba/bin/winbindd -B</tt></b> +</p><p> +I'm always paranoid and like to make sure the daemon +is really running... +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>ps -ae | grep winbindd</tt></b> +</p><p> +This command should produce output like this, if the daemon is running +</p><pre class="screen"> +3025 ? 00:00:00 winbindd +</pre><p> +Now... for the real test, try to get some information about the +users on your PDC +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/local/samba/bin/wbinfo -u</tt></b> +</p><p> +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response: +</p><pre class="screen"> + CEO+Administrator + CEO+burdell + CEO+Guest + CEO+jt-ad + CEO+krbtgt + CEO+TsInternetUser +</pre><p> + Obviously, I have named my domain 'CEO' and my <a class="indexterm" name="id2942662"></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: +</p><pre class="screen"> +<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/local/samba/bin/wbinfo -g</tt></b> + CEO+Domain Admins + CEO+Domain Users + CEO+Domain Guests + CEO+Domain Computers + CEO+Domain Controllers + CEO+Cert Publishers + CEO+Schema Admins + CEO+Enterprise Admins + CEO+Group Policy Creator Owners +</pre><p> +The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command: +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>getent passwd</tt></b> +</p><p> +You should get a list that looks like your <tt class="filename">/etc/passwd</tt> +list followed by the domain users with their new uids, gids, home +directories and default shells. +</p><p> +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="id2942766"></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="id2942773"></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. +They are located at <tt class="filename">/etc/init.d/smb</tt> in RedHat and +<tt class="filename">/etc/init.d/samba</tt> in Debian. +script to add commands to invoke this daemon in the proper sequence. My +startup script starts up <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> from the +<tt class="filename">/usr/local/samba/bin</tt> directory directly. The 'start' +function in the script looks like this: +</p><pre class="programlisting"> +start() { + KIND="SMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/smbd $SMBDOPTIONS + RETVAL=$? + echo + KIND="NMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/winbindd + RETVAL3=$? + echo + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \ + touch /var/lock/subsys/smb || RETVAL=1 + return $RETVAL +} +</pre><p>If you would like to run winbindd in dual daemon mode, replace +the line +</p><pre class="programlisting"> + daemon /usr/local/samba/bin/winbindd +</pre><p> + +in the example above with: + +</p><pre class="programlisting"> + daemon /usr/local/samba/bin/winbindd -B +</pre><p>. +</p><p> +The 'stop' function has a corresponding entry to shut down the +services and looks like this: +</p><pre class="programlisting"> +stop() { + KIND="SMB" + echo -n $"Shutting down $KIND services: " + killproc smbd + RETVAL=$? + echo + KIND="NMB" + echo -n $"Shutting down $KIND services: " + killproc nmbd + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Shutting down $KIND services: " + killproc winbindd + RETVAL3=$? + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \ + rm -f /var/lock/subsys/smb + echo "" + return $RETVAL +} +</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2942942"></a>Solaris</h5></div></div><div></div></div><p>Winbind doesn't work on Solaris 9, see the <a href="Portability.html#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>, +the file could contains something like this: +</p><pre class="programlisting"> + ## + ## samba.server + ## + + if [ ! -d /usr/bin ] + then # /usr not mounted + exit + fi + + killproc() { # kill the named process(es) + pid=`/usr/bin/ps -e | + /usr/bin/grep -w $1 | + /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` + [ "$pid" != "" ] && kill $pid + } + + # Start/stop processes required for samba server + + case "$1" in + + 'start') + # + # Edit these lines to suit your installation (paths, workgroup, host) + # + echo Starting SMBD + /usr/local/samba/bin/smbd -D -s \ + /usr/local/samba/smb.conf + + echo Starting NMBD + /usr/local/samba/bin/nmbd -D -l \ + /usr/local/samba/var/log -s /usr/local/samba/smb.conf + + echo Starting Winbind Daemon + /usr/local/samba/bin/winbindd + ;; + + 'stop') + killproc nmbd + killproc smbd + killproc winbindd + ;; + + *) + echo "Usage: /etc/init.d/samba.server { start | stop }" + ;; + esac +</pre><p> +Again, if you would like to run samba in dual daemon mode, replace +</p><pre class="programlisting"> + /usr/local/samba/bin/winbindd +</pre><p> + +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="id2943053"></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="id2943089"></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 +this step. (Did you remember to make backups of your original +<tt class="filename">/etc/pam.d</tt> files? If not, do it now.) +</p><p> +You will need a pam module to use winbindd with these other services. This +module will be compiled in the <tt class="filename">../source/nsswitch</tt> directory +by invoking the command +</p><p> +<tt class="prompt">root# </tt><b class="userinput"><tt>make nsswitch/pam_winbind.so</tt></b> +</p><p> +from the <tt class="filename">../source</tt> directory. The +<tt class="filename">pam_winbind.so</tt> file should be copied to the location of +your other pam security modules. On my RedHat system, this was the +<tt class="filename">/lib/security</tt> directory. On Solaris, the pam security +modules reside in <tt class="filename">/usr/lib/security</tt>. +</p><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="id2943196"></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"> + auth required /lib/security/pam_stack.so service=system-auth + account required /lib/security/pam_stack.so service=system-auth +</pre><p> +The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in +<tt class="filename">/etc/xinetd.d</tt> (or <tt class="filename">/etc/inetd.conf</tt>). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in <tt class="filename">/etc/xinetd.d/telnet</tt> +and <tt class="filename">/etc/xinetd.d/wu-ftp</tt> from +</p><pre class="programlisting"> + enable = no +</pre><p> +to +</p><pre class="programlisting"> + enable = yes +</pre><p> +For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the <tt class="filename">smb.conf</tt> global entry +<a class="indexterm" name="id2943302"></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 +samba file. My <tt class="filename">/etc/pam.d/ftp</tt> file was +changed to look like this: +</p><pre class="programlisting"> + auth required /lib/security/pam_listfile.so item=user sense=deny \ + file=/etc/ftpusers onerr=succeed + auth sufficient /lib/security/pam_winbind.so + auth required /lib/security/pam_stack.so service=system-auth + auth required /lib/security/pam_shells.so + account sufficient /lib/security/pam_winbind.so + account required /lib/security/pam_stack.so service=system-auth + session required /lib/security/pam_stack.so service=system-auth +</pre><p> +The <tt class="filename">/etc/pam.d/login</tt> file can be changed nearly the +same way. It now looks like this: +</p><pre class="programlisting"> + auth required /lib/security/pam_securetty.so + auth sufficient /lib/security/pam_winbind.so + auth sufficient /lib/security/pam_unix.so use_first_pass + auth required /lib/security/pam_stack.so service=system-auth + auth required /lib/security/pam_nologin.so + account sufficient /lib/security/pam_winbind.so + account required /lib/security/pam_stack.so service=system-auth + password required /lib/security/pam_stack.so service=system-auth + session required /lib/security/pam_stack.so service=system-auth + session optional /lib/security/pam_console.so +</pre><p> +In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p> +lines as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p> +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="id2943437"></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 +be sure of those changes because in the worst case it will leave your system +nearly impossible to boot. +</p><pre class="programlisting"> + # + #ident "@(#)pam.conf 1.14 99/09/16 SMI" + # + # Copyright (c) 1996-1999, Sun Microsystems, Inc. + # All Rights Reserved. + # + # PAM configuration + # + # Authentication management + # + login auth required /usr/lib/security/pam_winbind.so + login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass + login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass + # + rlogin auth sufficient /usr/lib/security/pam_winbind.so + rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1 + rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass + # + dtlogin auth sufficient /usr/lib/security/pam_winbind.so + dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass + # + rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1 + other auth sufficient /usr/lib/security/pam_winbind.so + other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass + # + # Account management + # + login account sufficient /usr/lib/security/pam_winbind.so + login account requisite /usr/lib/security/$ISA/pam_roles.so.1 + login account required /usr/lib/security/$ISA/pam_unix.so.1 + # + dtlogin account sufficient /usr/lib/security/pam_winbind.so + dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1 + dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1 + # + other account sufficient /usr/lib/security/pam_winbind.so + other account requisite /usr/lib/security/$ISA/pam_roles.so.1 + other account required /usr/lib/security/$ISA/pam_unix.so.1 + # + # Session management + # + other session required /usr/lib/security/$ISA/pam_unix.so.1 + # + # Password management + # + #other password sufficient /usr/lib/security/pam_winbind.so + other password required /usr/lib/security/$ISA/pam_unix.so.1 + dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 + # + # Support for Kerberos V5 authentication (uncomment to use Kerberos) + # + #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass + #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass + #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass + #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass + #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1 + #other account optional /usr/lib/security/$ISA/pam_krb5.so.1 + #other session optional /usr/lib/security/$ISA/pam_krb5.so.1 + #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass +</pre><p> +I also added a try_first_pass line after the winbind.so line to get rid of +annoying double prompts for passwords. +</p><p> +Now restart your Samba and try connecting through your application that you +configured in the pam.conf. +</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943561"></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="id2943580"></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 + systems are certainly possible. For such ports to be feasible, + we require the C library of the target operating system to + support the Name Service Switch and Pluggable Authentication + Modules systems. This is becoming more common as NSS and + PAM gain support among UNIX vendors.</p></li><li><p>The mappings of Windows NT RIDs to UNIX ids + is not made algorithmically and depends on the order in which + unmapped users or groups are seen by winbind. It may be difficult + to recover the mappings of rid to UNIX id mapping if the file + containing this information is corrupted or destroyed.</p></li><li><p>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="id2943633"></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="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 20. Stackable VFS modules </td><td width="20%" align="center"><a accesskey="h" href="samba-doc.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 22. Advanced Network Management</td></tr></table></div></body></html> diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index fdcde9fba8..748dbe1e4b 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="id2796930"></a><i class="parameter"><tt>log level</tt></i> parameter +override the <a class="indexterm" name="id2796919"></a><i class="parameter"><tt>log level</tt></i> 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="id2797162"></a><i class="parameter"><tt>winbind separator</tt></i></p></li><li><p> - <a class="indexterm" name="id2797180"></a><i class="parameter"><tt>idmap uid</tt></i></p></li><li><p> - <a class="indexterm" name="id2797198"></a><i class="parameter"><tt>idmap gid</tt></i></p></li><li><p> - <a class="indexterm" name="id2797216"></a><i class="parameter"><tt>winbind cache time</tt></i></p></li><li><p> - <a class="indexterm" name="id2797234"></a><i class="parameter"><tt>winbind enum users</tt></i></p></li><li><p> - <a class="indexterm" name="id2797252"></a><i class="parameter"><tt>winbind enum groups</tt></i></p></li><li><p> - <a class="indexterm" name="id2797270"></a><i class="parameter"><tt>template homedir</tt></i></p></li><li><p> - <a class="indexterm" name="id2797288"></a><i class="parameter"><tt>template shell</tt></i></p></li><li><p> - <a class="indexterm" name="id2797307"></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="id2797151"></a><i class="parameter"><tt>winbind separator</tt></i></p></li><li><p> + <a class="indexterm" name="id2797169"></a><i class="parameter"><tt>idmap uid</tt></i></p></li><li><p> + <a class="indexterm" name="id2797187"></a><i class="parameter"><tt>idmap gid</tt></i></p></li><li><p> + <a class="indexterm" name="id2797205"></a><i class="parameter"><tt>winbind cache time</tt></i></p></li><li><p> + <a class="indexterm" name="id2797223"></a><i class="parameter"><tt>winbind enum users</tt></i></p></li><li><p> + <a class="indexterm" name="id2797241"></a><i class="parameter"><tt>winbind enum groups</tt></i></p></li><li><p> + <a class="indexterm" name="id2797259"></a><i class="parameter"><tt>template homedir</tt></i></p></li><li><p> + <a class="indexterm" name="id2797277"></a><i class="parameter"><tt>template shell</tt></i></p></li><li><p> + <a class="indexterm" name="id2797296"></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 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: |