diff options
| author | Jelmer Vernooij <jelmer@samba.org> | 2003-07-01 22:58:52 +0000 |
|---|---|---|
| committer | Jelmer Vernooij <jelmer@samba.org> | 2003-07-01 22:58:52 +0000 |
| commit | 3878085eca35d5c3b08761f61281de0b1b49ce2d (patch) | |
| tree | aa9e3aa50d1fc99ce341ee2eff24352266c2063b /docs/htmldocs/Samba-HOWTO-Collection.html | |
| parent | b32d48533f3ad9e8a510c83c8acf4d543556549d (diff) | |
| download | samba-3878085eca35d5c3b08761f61281de0b1b49ce2d.tar.gz samba-3878085eca35d5c3b08761f61281de0b1b49ce2d.tar.bz2 samba-3878085eca35d5c3b08761f61281de0b1b49ce2d.zip | |
regenerate docs
(This used to be commit cc02d3bc170fe5c8c4474156edb6c83720a47aa0)
Diffstat (limited to 'docs/htmldocs/Samba-HOWTO-Collection.html')
| -rw-r--r-- | docs/htmldocs/Samba-HOWTO-Collection.html | 3611 |
1 files changed, 1832 insertions, 1779 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index f233e85edd..27faf25f17 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -14,16 +14,16 @@ or without their knowledge contributed to this update. The size and scope of thi project would not have been possible without significant community contribution. A not insignificant number of ideas for inclusion (if not content itself) has been obtained from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. -Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and +Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. -"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>SAMBA Project Documentation</h1></div><div><div class="authorgroup"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><h3 class="editor"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><h3 class="editor"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3></div></div><div><div xmlns:ns1="" class="legalnotice"><p> +"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>SAMBA Project Documentation</h1></div><div><div class="authorgroup"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><h3 class="editor"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><h3 class="editor"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3></div></div><div><div class="legalnotice"><p> This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a> -</p><ns1:p><b>Attributions. </b> - </ns1:p><div class="variablelist"><dl><dt><span class="term"><a href="#IntroSMB" title="Chapter 1. Introduction to Samba">Introduction to Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>David Lechnyr <<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#install" title="Chapter 2. How to Install and Test SAMBA">How to Install and Test SAMBA</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Karl Auer</p></li></ul></div></dd><dt><span class="term"><a href="#FastStart" title="Chapter 3. FastStart for the Impatient">FastStart for the Impatient</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ServerType" title="Chapter 4. Server Types and Security Modes">Server Types and Security Modes</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#samba-pdc" title="Chapter 5. Domain Control">Domain Control</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#samba-bdc" title="Chapter 6. Backup Domain Control">Backup Domain Control</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Volker Lendecke <<a href="mailto:Volker.Lendecke@SerNet.DE" target="_top">Volker.Lendecke@SerNet.DE</a>></p></li></ul></div></dd><dt><span class="term"><a href="#domain-member" title="Chapter 7. Domain Membership">Domain Membership</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#StandAloneServer" title="Chapter 8. Stand-Alone Servers">Stand-Alone Servers</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ClientConfig" title="Chapter 9. MS Windows Network Configuration Guide">MS Windows Network Configuration Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#NetworkBrowsing" title="Chapter 10. Samba / MS Windows Network Browsing Guide">Samba / MS Windows Network Browsing Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#passdb" title="Chapter 11. Account Information Databases">Account Information Databases</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Olivier (lem) Lemaire <<a href="mailto:olem@IDEALX.org" target="_top">olem@IDEALX.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#groupmapping" title="Chapter 12. Mapping MS Windows and Unix Groups">Mapping MS Windows and Unix Groups</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jean François Micouleau</p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#AccessControls" title="Chapter 13. File, Directory and Share Access Controls">File, Directory and Share Access Controls</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#locking" title="Chapter 14. File and Record Locking">File and Record Locking</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Eric Roseme <<a href="mailto:eric.roseme@hp.com" target="_top">eric.roseme@hp.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#securing-samba" title="Chapter 15. Securing Samba">Securing Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#InterdomainTrusts" title="Chapter 16. Interdomain Trust Relationships">Interdomain Trust Relationships</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Rafal Szczesniak <<a href="mailto:mimir@samba.org" target="_top">mimir@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#msdfs" title="Chapter 17. Hosting a Microsoft Distributed File System tree on Samba">Hosting a Microsoft Distributed File System tree on Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Shirish Kalele <<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#printing" title="Chapter 18. Classical Printing Support">Classical Printing Support</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#CUPS-printing" title="Chapter 19. CUPS Printing Support in Samba 3.0">CUPS Printing Support in Samba 3.0</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Ciprian Vizitiu <<a href="mailto:CVizitiu@gbif.org" target="_top">CVizitiu@gbif.org</a>> (drawings) </p></li></ul></div></dd><dt><span class="term"><a href="#VFS" title="Chapter 20. Stackable VFS modules">Stackable VFS modules</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Alexander Bokovoy</p></li><li><p>Tim Potter</p></li><li><p>Simo Sorce</p></li></ul></div></dd><dt><span class="term"><a href="#winbind" title="Chapter 21. Integrated Logon Support using Winbind">Integrated Logon Support using Winbind</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Tim Potter <<a href="mailto:tpot@linuxcare.com.au" target="_top">tpot@linuxcare.com.au</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Naag Mummaneni <<a href="mailto:getnag@rediffmail.com" target="_top">getnag@rediffmail.com</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#AdvancedNetworkManagement" title="Chapter 22. Advanced Network Manangement">Advanced Network Manangement</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#PolicyMgmt" title="Chapter 23. System and Account Policies">System and Account Policies</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ProfileMgmt" title="Chapter 24. Desktop Profile Management">Desktop Profile Management</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#pam" title="Chapter 25. PAM based Distributed Authentication">PAM based Distributed Authentication</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Stephen Langasek <<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>></p></li></ul></div></dd><dt><span class="term"><a href="#integrate-ms-networks" title="Chapter 26. Integrating MS Windows networks with Samba">Integrating MS Windows networks with Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#unicode" title="Chapter 27. Unicode/Charsets">Unicode/Charsets</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>TAKAHASHI Motonobu <<a href="mailto:monyo@home.monyo.com" target="_top">monyo@home.monyo.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#Backup" title="Chapter 28. Samba Backup Techniques">Samba Backup Techniques</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#SambaHA" title="Chapter 29. High Availability Options">High Availability Options</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#upgrading-to-3.0" title="Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0">Upgrading from Samba-2.x to Samba-3.0.0</a></span></dt><dd><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></dd><dt><span class="term"><a href="#NT4Migration" title="Chapter 31. Migration from NT4 PDC to Samba-3 PDC">Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#SWAT" title="Chapter 32. SWAT - The Samba Web Administration Tool">SWAT - The Samba Web Administration Tool</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#diagnosis" title="Chapter 33. The samba checklist">The samba checklist</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#problems" title="Chapter 34. Analysing and solving samba problems">Analysing and solving samba problems</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#bugreport" title="Chapter 35. Reporting Bugs">Reporting Bugs</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p> Someone; Tridge or Karl Auer perhaps?</p></li></ul></div></dd><dt><span class="term"><a href="#compiling" title="Chapter 36. How to compile SAMBA">How to compile SAMBA</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p> Someone; Jerry perhaps?</p></li></ul></div></dd><dt><span class="term"><a href="#Portability" title="Chapter 37. Portability">Portability</a></span></dt><dd><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></dd><dt><span class="term"><a href="#Other-Clients" title="Chapter 38. Samba and other CIFS clients">Samba and other CIFS clients</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jim McDonough <<a href="mailto:jmcd@us.ibm.com" target="_top">jmcd@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></dd><dt><span class="term"><a href="#speed" title="Chapter 39. Samba Performance Tuning">Samba Performance Tuning</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Paul Cochrane <<a href="mailto:paulc@dth.scot.nhs.uk" target="_top">paulc@dth.scot.nhs.uk</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#DNSDHCP" title="Chapter 40. DNS and DHCP Configuration Guide">DNS and DHCP Configuration Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#Further-Resources" title="Chapter 41. Further Resources">Further Resources</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>David Lechnyr <<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>></p></li></ul></div></dd></dl></div><ns1:p> +</p><p><b>Attributions. </b> + </p><div class="variablelist"><dl><dt><span class="term"><a href="#IntroSMB" title="Chapter 1. Introduction to Samba">Introduction to Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>David Lechnyr <<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#install" title="Chapter 2. How to Install and Test SAMBA">How to Install and Test SAMBA</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Karl Auer</p></li></ul></div></dd><dt><span class="term"><a href="#FastStart" title="Chapter 3. Fast Start for the Impatient">Fast Start for the Impatient</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ServerType" title="Chapter 4. Server Types and Security Modes">Server Types and Security Modes</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#samba-pdc" title="Chapter 5. Domain Control">Domain Control</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#samba-bdc" title="Chapter 6. Backup Domain Control">Backup Domain Control</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Volker Lendecke <<a href="mailto:Volker.Lendecke@SerNet.DE" target="_top">Volker.Lendecke@SerNet.DE</a>></p></li></ul></div></dd><dt><span class="term"><a href="#domain-member" title="Chapter 7. Domain Membership">Domain Membership</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#StandAloneServer" title="Chapter 8. Stand-Alone Servers">Stand-Alone Servers</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ClientConfig" title="Chapter 9. MS Windows Network Configuration Guide">MS Windows Network Configuration Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#NetworkBrowsing" title="Chapter 10. Samba / MS Windows Network Browsing Guide">Samba / MS Windows Network Browsing Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#passdb" title="Chapter 11. Account Information Databases">Account Information Databases</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Olivier (lem) Lemaire <<a href="mailto:olem@IDEALX.org" target="_top">olem@IDEALX.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#groupmapping" title="Chapter 12. Mapping MS Windows and Unix Groups">Mapping MS Windows and Unix Groups</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jean François Micouleau</p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#AccessControls" title="Chapter 13. File, Directory and Share Access Controls">File, Directory and Share Access Controls</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#locking" title="Chapter 14. File and Record Locking">File and Record Locking</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Eric Roseme <<a href="mailto:eric.roseme@hp.com" target="_top">eric.roseme@hp.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#securing-samba" title="Chapter 15. Securing Samba">Securing Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#InterdomainTrusts" title="Chapter 16. Interdomain Trust Relationships">Interdomain Trust Relationships</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Rafal Szczesniak <<a href="mailto:mimir@samba.org" target="_top">mimir@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#msdfs" title="Chapter 17. Hosting a Microsoft Distributed File System tree on Samba">Hosting a Microsoft Distributed File System tree on Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Shirish Kalele <<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#printing" title="Chapter 18. Classical Printing Support">Classical Printing Support</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#CUPS-printing" title="Chapter 19. CUPS Printing Support in Samba 3.0">CUPS Printing Support in Samba 3.0</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Ciprian Vizitiu <<a href="mailto:CVizitiu@gbif.org" target="_top">CVizitiu@gbif.org</a>> (drawings) </p></li></ul></div></dd><dt><span class="term"><a href="#VFS" title="Chapter 20. Stackable VFS modules">Stackable VFS modules</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Tim Potter</p></li><li><p>Simo Sorce (original vfs_skel README) </p></li><li><p>Alexander Bokovoy (original vfs_netatalk docs) </p></li><li><p>Stefan Metzmacher (Update for multiple modules) </p></li></ul></div></dd><dt><span class="term"><a href="#winbind" title="Chapter 21. Integrated Logon Support using Winbind">Integrated Logon Support using Winbind</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Tim Potter <<a href="mailto:tpot@linuxcare.com.au" target="_top">tpot@linuxcare.com.au</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Naag Mummaneni <<a href="mailto:getnag@rediffmail.com" target="_top">getnag@rediffmail.com</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#AdvancedNetworkManagement" title="Chapter 22. Advanced Network Management">Advanced Network Management</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#PolicyMgmt" title="Chapter 23. System and Account Policies">System and Account Policies</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#ProfileMgmt" title="Chapter 24. Desktop Profile Management">Desktop Profile Management</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#pam" title="Chapter 25. PAM based Distributed Authentication">PAM based Distributed Authentication</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Stephen Langasek <<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>></p></li></ul></div></dd><dt><span class="term"><a href="#integrate-ms-networks" title="Chapter 26. Integrating MS Windows networks with Samba">Integrating MS Windows networks with Samba</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#unicode" title="Chapter 27. Unicode/Charsets">Unicode/Charsets</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>TAKAHASHI Motonobu <<a href="mailto:monyo@home.monyo.com" target="_top">monyo@home.monyo.com</a>></p></li></ul></div></dd><dt><span class="term"><a href="#Backup" title="Chapter 28. Samba Backup Techniques">Samba Backup Techniques</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#SambaHA" title="Chapter 29. High Availability Options">High Availability Options</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#upgrading-to-3.0" title="Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0">Upgrading from Samba-2.x to Samba-3.0.0</a></span></dt><dd><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></dd><dt><span class="term"><a href="#NT4Migration" title="Chapter 31. Migration from NT4 PDC to Samba-3 PDC">Migration from NT4 PDC to Samba-3 PDC</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#SWAT" title="Chapter 32. SWAT - The Samba Web Administration Tool">SWAT - The Samba Web Administration Tool</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#diagnosis" title="Chapter 33. The Samba checklist">The Samba checklist</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#problems" title="Chapter 34. Analysing and solving samba problems">Analysing and solving samba problems</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Gerald Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#bugreport" title="Chapter 35. Reporting Bugs">Reporting Bugs</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p> Someone; Tridge or Karl Auer perhaps?</p></li></ul></div></dd><dt><span class="term"><a href="#compiling" title="Chapter 36. How to compile SAMBA">How to compile SAMBA</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p> Someone; Jerry perhaps?</p></li></ul></div></dd><dt><span class="term"><a href="#Portability" title="Chapter 37. Portability">Portability</a></span></dt><dd><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></dd><dt><span class="term"><a href="#Other-Clients" title="Chapter 38. Samba and other CIFS clients">Samba and other CIFS clients</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jim McDonough <<a href="mailto:jmcd@us.ibm.com" target="_top">jmcd@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></dd><dt><span class="term"><a href="#speed" title="Chapter 39. Samba Performance Tuning">Samba Performance Tuning</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Paul Cochrane <<a href="mailto:paulc@dth.scot.nhs.uk" target="_top">paulc@dth.scot.nhs.uk</a>></p></li><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#DNSDHCP" title="Chapter 40. DNS and DHCP Configuration Guide">DNS and DHCP Configuration Guide</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>John Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div></dd><dt><span class="term"><a href="#Further-Resources" title="Chapter 41. Further Resources">Further Resources</a></span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Jelmer Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>David Lechnyr <<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>></p></li></ul></div></dd></dl></div><p> - </ns1:p></div></div><div><p class="pubdate">Monday April 21, 2003</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p> + </p></div></div><div><p class="pubdate">Monday April 21, 2003</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p> This book is a collection of HOWTOs added to Samba documentation over the years. Samba is always under development, and so is its' documentation. This release of the documentation represents a major revision or layout as well as contents. @@ -39,45 +39,45 @@ or without their knowledge contributed to this update. The size and scope of thi project would not have been possible without significant community contribution. A not insignificant number of ideas for inclusion (if not content itself) has been obtained from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. -Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and +Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. -</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2867729">Background</a></dt><dt><a href="#id2867783">Terminology</a></dt><dt><a href="#id2866506">Related Projects</a></dt><dt><a href="#id2866575">SMB Methodology</a></dt><dt><a href="#id2866662">Epilogue</a></dt><dt><a href="#id2866735">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2867501">Obtaining and installing samba</a></dt><dt><a href="#id2867544">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2867117">Example Configuration</a></dt><dt><a href="#id2867260">SWAT</a></dt></dl></dd><dt><a href="#id2867305">Try listing the shares available on your - server</a></dt><dt><a href="#id2866810">Try connecting with the unix client</a></dt><dt><a href="#id2866912">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2866973">What If Things Don't Work?</a></dt><dt><a href="#id2867003">Common Errors</a></dt><dd><dl><dt><a href="#id2867016">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2868395">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">FastStart for the Impatient</a></dt><dd><dl><dt><a href="#id2868843">Note</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2871915">Features and Benefits</a></dt><dt><a href="#id2872007">Server Types</a></dt><dt><a href="#id2872088">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2868518">User Level Security</a></dt><dt><a href="#id2868651">Share Level Security</a></dt><dt><a href="#id2869720">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2869962">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2870046">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2870271">Seamless Windows Network Integration</a></dt><dt><a href="#id2870448">Common Errors</a></dt><dd><dl><dt><a href="#id2870476">What makes Samba a SERVER?</a></dt><dt><a href="#id2870509">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2870537">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872449">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2875080">Features and Benefits</a></dt><dt><a href="#id2872678">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2872693">Domain Controller Types</a></dt><dt><a href="#id2872892">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2873207">Domain Control - Example Configuration</a></dt><dt><a href="#id2873503">Samba ADS Domain Control</a></dt><dt><a href="#id2873526">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2873540">Domain Network Logon Service</a></dt><dt><a href="#id2876260">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876365">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876372">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876411">I get told "You already have a connection to the Domain...." +</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2868116">Background</a></dt><dt><a href="#id2868327">Terminology</a></dt><dt><a href="#id2868481">Related Projects</a></dt><dt><a href="#id2868550">SMB Methodology</a></dt><dt><a href="#id2868638">Epilogue</a></dt><dt><a href="#id2868711">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2869372">Obtaining and installing samba</a></dt><dt><a href="#id2869412">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2869449">Example Configuration</a></dt><dt><a href="#id2869599">SWAT</a></dt></dl></dd><dt><a href="#id2869643">Try listing the shares available on your + server</a></dt><dt><a href="#id2869694">Try connecting with the unix client</a></dt><dt><a href="#id2869795">Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</a></dt><dt><a href="#id2869858">What If Things Don't Work?</a></dt><dt><a href="#id2869892">Common Errors</a></dt><dd><dl><dt><a href="#id2869904">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2870119">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2869247">Note</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2871270">Features and Benefits</a></dt><dt><a href="#id2871366">Server Types</a></dt><dt><a href="#id2871450">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2871565">User Level Security</a></dt><dt><a href="#id2871698">Share Level Security</a></dt><dt><a href="#id2871820">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2872071">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2872158">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2872383">Seamless Windows Network Integration</a></dt><dt><a href="#id2872559">Common Errors</a></dt><dd><dl><dt><a href="#id2872587">What makes Samba a SERVER?</a></dt><dt><a href="#id2872620">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2872649">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872682">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2874489">Features and Benefits</a></dt><dt><a href="#id2874793">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2874809">Domain Controller Types</a></dt><dt><a href="#id2875020">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2875340">Domain Control - Example Configuration</a></dt><dt><a href="#id2875639">Samba ADS Domain Control</a></dt><dt><a href="#id2875661">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2875676">Domain Network Logon Service</a></dt><dt><a href="#id2876003">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876111">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876118">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876157">I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876460">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876531">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2876588">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt><dt><a href="#id2876615">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2878646">Features And Benefits</a></dt><dt><a href="#id2878811">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878839">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2876805">Active Directory Domain Control</a></dt><dt><a href="#id2876826">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2876850">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2876875">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2876945">Example Configuration</a></dt></dl></dd><dt><a href="#id2876995">Common Errors</a></dt><dd><dl><dt><a href="#id2877009">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2877034">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2877067">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2877096">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2877621">Features and Benefits</a></dt><dt><a href="#id2877192">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2877352">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879134">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2879331">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879386">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#id2879531">Domain Member Server</a></dt><dd><dl><dt><a href="#id2879579">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2882177">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2882315">Setup your smb.conf</a></dt><dt><a href="#id2882398">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882740">Notes</a></dt></dl></dd><dt><a href="#id2882762">Common Errors</a></dt><dd><dl><dt><a href="#id2882784">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882816">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2884259">Features and Benefits</a></dt><dt><a href="#id2884297">Background</a></dt><dt><a href="#id2884365">Example Configuration</a></dt><dd><dl><dt><a href="#id2882967">Reference Documentation Server</a></dt><dt><a href="#id2883015">Central Print Serving</a></dt></dl></dd><dt><a href="#id2883221">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2883589">Note</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2883706">Features and Benefits</a></dt><dt><a href="#id2883784">What is Browsing?</a></dt><dt><a href="#id2883967">Discussion</a></dt><dd><dl><dt><a href="#id2883983">NetBIOS over TCP/IP</a></dt><dt><a href="#id2883290">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2883418">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2883554">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2884860">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2885066">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2885332">Making samba the domain master</a></dt><dt><a href="#id2888727">Note about broadcast addresses</a></dt><dt><a href="#id2888744">Multiple interfaces</a></dt><dt><a href="#id2888773">Use of the Remote Announce parameter</a></dt><dt><a href="#id2888877">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2888938">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2889089">Setting up a WINS server</a></dt><dt><a href="#id2889284">WINS Replication</a></dt><dt><a href="#id2889309">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2889340">Helpful Hints</a></dt><dd><dl><dt><a href="#id2889353">Windows Networking Protocols</a></dt><dt><a href="#id2889420">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2889541">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2889588">Browsing support in samba</a></dt><dt><a href="#id2889695">Problem resolution</a></dt><dt><a href="#id2889774">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2890391">Common Errors</a></dt><dd><dl><dt><a href="#id2890406">How can one flush the Samba NetBIOS name cache without restarting samba?</a></dt><dt><a href="#id2890435">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2890530">Features and Benefits</a></dt><dt><a href="#id2890854">Technical Information</a></dt><dd><dl><dt><a href="#id2890917">Important Notes About Security</a></dt><dt><a href="#id2891160">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2891216">Account Management Tools</a></dt><dd><dl><dt><a href="#id2891247">The smbpasswd Command</a></dt><dt><a href="#id2891513">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2891647">Password Backends</a></dt><dd><dl><dt><a href="#id2895859">Plain Text</a></dt><dt><a href="#id2895899">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2896006">tdbsam</a></dt><dt><a href="#id2896034">ldapsam</a></dt><dt><a href="#id2897524">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2898328">Common Errors</a></dt><dd><dl><dt><a href="#id2898335">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2898350">Users are being added to the wrong backend database</a></dt><dt><a href="#id2898409">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and Unix Groups</a></dt><dd><dl><dt><a href="#id2898582">Features and Benefits</a></dt><dt><a href="#id2898682">Discussion</a></dt><dd><dl><dt><a href="#id2898871">Example Configuration</a></dt></dl></dd><dt><a href="#id2898936">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2898950">Sample smb.conf add group script</a></dt><dt><a href="#id2899017">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2899091">Common Errors</a></dt><dd><dl><dt><a href="#id2899107">Adding Groups Fails</a></dt><dt><a href="#id2899167">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2902353">Features and Benefits</a></dt><dt><a href="#id2902478">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902496">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2899413">Managing Directories</a></dt><dt><a href="#id2899508">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2899915">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2899943">User and Group Based Controls</a></dt><dt><a href="#id2900215">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2900461">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905044">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905115">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905414">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905422">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905460">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905539">Viewing file ownership</a></dt><dt><a href="#id2905661">Viewing File or Directory Permissions</a></dt><dt><a href="#id2905889">Modifying file or directory permissions</a></dt><dt><a href="#id2906041">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2906370">Interaction with the standard Samba file attribute - mapping</a></dt></dl></dd><dt><a href="#id2906446">Common Errors</a></dt><dd><dl><dt><a href="#id2906460">Users can not write to a public share</a></dt><dt><a href="#id2906838">I have set force user and samba still makes root the owner of all the files - I touch!</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2908960">Features and Benefits</a></dt><dt><a href="#id2909016">Discussion</a></dt><dd><dl><dt><a href="#id2906890">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2907521">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2907630">Example Configuration</a></dt></dl></dd><dt><a href="#id2907890">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2910326">Workstation Service Entries</a></dt><dt><a href="#id2910353">Server Service Entries</a></dt></dl></dd><dt><a href="#id2910432">Persistent Data Corruption</a></dt><dt><a href="#id2910463">Common Errors</a></dt><dd><dl><dt><a href="#id2910536">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2910566">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2911991">Introduction</a></dt><dt><a href="#id2912024">Features and Benefits</a></dt><dt><a href="#id2910684">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2910702">Using host based protection</a></dt><dt><a href="#id2910771">User based protection</a></dt><dt><a href="#id2910822">Using interface protection</a></dt><dt><a href="#id2910872">Using a firewall</a></dt><dt><a href="#id2910929">Using a IPC$ share deny</a></dt><dt><a href="#id2910994">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2911033">Upgrading Samba</a></dt><dt><a href="#id2911056">Common Errors</a></dt><dd><dl><dt><a href="#id2911075">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2911100">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2911618">Features and Benefits</a></dt><dt><a href="#id2911646">Trust Relationship Background</a></dt><dt><a href="#id2911730">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2911742">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2913717">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2913754">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2913781">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2913908">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2911286">Common Errors</a></dt><dd><dl><dt><a href="#id2911301">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2911399">Features and Benefits</a></dt><dt><a href="#id2912809">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2914332">Features and Benefits</a></dt><dt><a href="#id2914396">Technical Introduction</a></dt><dd><dl><dt><a href="#id2914432">What happens if you send a Job from a Client</a></dt><dt><a href="#id2914502">Printing Related Configuration Parameters</a></dt><dt><a href="#id2917610">Parameters Recommended for Use</a></dt><dt><a href="#id2912970">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2913079">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2913172">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2915178">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2915261">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2915568">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2915660">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2915673">The [global] Section</a></dt><dt><a href="#id2925133">The [printers] Section</a></dt><dt><a href="#id2925462">Any [my_printer_name] Section</a></dt><dt><a href="#id2925683">Print Commands</a></dt><dt><a href="#id2925734">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2926260">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2926537">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2926691">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2926842">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2926955">Creating the [print$] Share</a></dt><dt><a href="#id2927026">Parameters in the [print$] Section</a></dt><dt><a href="#id2927247">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2927408">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2927502">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2927686">Setting Drivers for existing Printers with -rpcclient</a></dt></dl></dd><dt><a href="#id2929284">"The Proof of the Pudding lies in the Eating" (Client Driver Insta -Procedure)</a></dt><dd><dl><dt><a href="#id2929305">The first Client Driver Installation</a></dt><dt><a href="#id2929502">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2929792">Further Client Driver Install Procedures</a></dt><dt><a href="#id2929887">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2930029">Other Gotchas</a></dt><dd><dl><dt><a href="#id2930062">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2930496">Supporting large Numbers of Printers</a></dt><dt><a href="#id2930798">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2931042">Weird Error Message Cannot connect under a -different Name</a></dt><dt><a href="#id2931140">Be careful when assembling Driver Files</a></dt><dt><a href="#id2931411">Samba and Printer Ports</a></dt><dt><a href="#id2931481">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2931504">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2931549">What is Imprints?</a></dt><dt><a href="#id2931590">Creating Printer Driver Packages</a></dt><dt><a href="#id2931609">The Imprints Server</a></dt><dt><a href="#id2931634">The Installation Client</a></dt></dl></dd><dt><a href="#id2931786">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2932115">The addprinter command</a></dt><dt><a href="#id2932160">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2932329">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2932343">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2932356">I give my root password but I don't get access</a></dt><dt><a href="#id2932390">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2939414">Introduction</a></dt><dd><dl><dt><a href="#id2939421">Features and Benefits</a></dt><dt><a href="#id2939469">Overview</a></dt></dl></dd><dt><a href="#id2939521">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2939600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2932509">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2932572">More complex smb.conf Settings for -CUPS</a></dt></dl></dd><dt><a href="#id2932671">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2932692">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2932719">CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2932755">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2932814">Explicitly enable "raw" printing for -application/octet-stream!</a></dt><dt><a href="#id2932975">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2933068">Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2933143">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2933188">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2933286">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2933358">PostScript and Ghostscript</a></dt><dt><a href="#id2933454">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2933550">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2946373">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2946462">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2946485">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2946623">MIME types and CUPS Filters</a></dt><dt><a href="#id2946811">MIME type Conversion Rules</a></dt><dt><a href="#id2946927">Filter Requirements</a></dt><dt><a href="#id2947096">Prefilters</a></dt><dt><a href="#id2947181">pstops</a></dt><dt><a href="#id2947284">pstoraster</a></dt><dt><a href="#id2947440">imagetops and imagetoraster</a></dt><dt><a href="#id2947495">rasterto [printerspecific]</a></dt><dt><a href="#id2947580">CUPS Backends</a></dt><dt><a href="#id2947894">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2947997">The Complete Picture</a></dt><dt><a href="#id2948012">mime.convs</a></dt><dt><a href="#id2948065">"Raw" printing</a></dt><dt><a href="#id2948120">"application/octet-stream" printing</a></dt><dt><a href="#id2948335">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2948562">Difference between cupsomatic/foomatic-rip and -native CUPS printing</a></dt><dt><a href="#id2948719">Examples for filtering Chains</a></dt><dt><a href="#id2948948">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2949073">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2949135">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2949151">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2949190">Driver Execution on the Client</a></dt><dt><a href="#id2949249">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2949312">Network Printing (Windows clients -- UNIX/Samba Print -Servers)</a></dt><dd><dl><dt><a href="#id2949333">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2949493">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2949571">Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2949626">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2949667">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2949732">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2949750">Printer Drivers running in "Kernel Mode" cause many -Problems</a></dt><dt><a href="#id2949784">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2949805">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2949832">PostScript Drivers with no major problems -- even in Kernel -Mode</a></dt></dl></dd><dt><a href="#id2949866"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2949885">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2949976">Prepare your smb.conf for -cupsaddsmb</a></dt><dt><a href="#id2950023">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2950220">Recognize the different Driver Files</a></dt><dt><a href="#id2950278">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2950311">ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"</a></dt><dt><a href="#id2950361">Caveats to be considered</a></dt><dt><a href="#id2950582">What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2950763">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2950864">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2951007">Understanding cupsaddsmb</a></dt><dt><a href="#id2951101">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2951188">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2951223">cupsaddsmb Flowchart</a></dt><dt><a href="#id2951274">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2951389">Avoiding critical PostScript Driver Settings on the -Client</a></dt></dl></dd><dt><a href="#id2951523">Installing PostScript Driver Files manually (using -rpcclient)</a></dt><dd><dl><dt><a href="#id2951638">A Check of the rpcclient man Page</a></dt><dt><a href="#id2951750">Understanding the rpcclient man Page</a></dt><dt><a href="#id2951829">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2951919">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2952081">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2952701">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2952803">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2952906">Trivial DataBase Files</a></dt><dt><a href="#id2952976">Binary Format</a></dt><dt><a href="#id2953038">Losing *.tdb Files</a></dt><dt><a href="#id2953097">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2953159">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2953265">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2953893">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2954351">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2954382">Setting up Quotas</a></dt><dt><a href="#id2954413">Correct and incorrect Accounting</a></dt><dt><a href="#id2954454">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2954526">The page_log File Syntax</a></dt><dt><a href="#id2954628">Possible Shortcomings</a></dt><dt><a href="#id2954699">Future Developments</a></dt><dt><a href="#id2954747">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2954762">Additional Material</a></dt><dt><a href="#id2954956">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2955001">CUPS Configuration Settings explained</a></dt><dt><a href="#id2955083">Pre-conditions</a></dt><dt><a href="#id2955144">Manual Configuration</a></dt></dl></dd><dt><a href="#id2955162">When not to use Samba to print to -CUPS</a></dt><dt><a href="#id2955180">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2955214">Where to find Documentation</a></dt><dt><a href="#id2955227">How to ask for Help</a></dt><dt><a href="#id2955240">Where to find Help</a></dt></dl></dd><dt><a href="#id2955254">Appendix</a></dt><dd><dl><dt><a href="#id2955261">Printing from CUPS to Windows attached -Printers</a></dt><dt><a href="#id2955455">More CUPS filtering Chains</a></dt><dt><a href="#id2955709">Trouble Shooting Guidelines to fix typical Samba printing -Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2958218">Features and Benefits</a></dt><dt><a href="#id2958235">Discussion</a></dt><dt><a href="#id2958286">Included modules</a></dt><dd><dl><dt><a href="#id2956883">audit</a></dt><dt><a href="#id2956922">extd_audit</a></dt><dt><a href="#id2957044">fake_perms</a></dt><dt><a href="#id2957063">recycle</a></dt><dt><a href="#id2957202">netatalk</a></dt></dl></dd><dt><a href="#id2957247">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2957269">DatabaseFS</a></dt><dt><a href="#id2957323">vscan</a></dt></dl></dd><dt><a href="#id2957352">Common Errors</a></dt></dl></dd><dt>21. <a href="#winbind">Integrated Logon Support using Winbind</a></dt><dd><dl><dt><a href="#id2957847">Features and Benefits</a></dt><dt><a href="#id2957875">Introduction</a></dt><dt><a href="#id2959857">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2959916">Target Uses</a></dt></dl></dd><dt><a href="#id2959947">How Winbind Works</a></dt><dd><dl><dt><a href="#id2959975">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2960008">Microsoft Active Directory Services</a></dt><dt><a href="#id2960031">Name Service Switch</a></dt><dt><a href="#id2957393">Pluggable Authentication Modules</a></dt><dt><a href="#id2957465">User and Group ID Allocation</a></dt><dt><a href="#id2957499">Result Caching</a></dt></dl></dd><dt><a href="#id2957528">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2957555">Introduction</a></dt><dt><a href="#id2957630">Requirements</a></dt><dt><a href="#id2958907">Testing Things Out</a></dt></dl></dd><dt><a href="#id2963255">Conclusion</a></dt><dt><a href="#id2963274">Common Errors</a></dt></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2964647">Features and Benefits</a></dt><dt><a href="#id2964678">Remote Server Administration</a></dt><dt><a href="#id2963360">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2963377">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2963579">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2963774">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2963806">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2964204">Features and Benefits</a></dt><dt><a href="#id2964256">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2964367">Windows 9x/Me Policies</a></dt><dt><a href="#id2963915">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2964048">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2965490">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2965591">Samba Editreg Toolset</a></dt><dt><a href="#id2965611">Windows NT4/200x</a></dt><dt><a href="#id2965631">Samba PDC</a></dt></dl></dd><dt><a href="#id2965676">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2965823">Common Errors</a></dt><dd><dl><dt><a href="#id2965837">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2965940">Features and Benefits</a></dt><dt><a href="#id2965973">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2966014">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971377">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972314">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972378">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972638">Mandatory profiles</a></dt><dt><a href="#id2972696">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972742">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972762">MS Windows 9x/Me</a></dt><dt><a href="#id2972910">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973464">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2973968">Common Errors</a></dt><dd><dl><dt><a href="#id2973980">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974043">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974262">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2975719">Features and Benefits</a></dt><dt><a href="#id2974574">Technical Discussion</a></dt><dd><dl><dt><a href="#id2974590">PAM Configuration Syntax</a></dt><dt><a href="#id2975256">Example System Configurations</a></dt><dt><a href="#id2977688">smb.conf PAM Configuration</a></dt><dt><a href="#id2977745">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2977829">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2978196">Common Errors</a></dt><dd><dl><dt><a href="#id2978209">pam_winbind problem</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2979952">Features and Benefits</a></dt><dt><a href="#id2979977">Background Information</a></dt><dt><a href="#id2980022">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2980073">/etc/hosts</a></dt><dt><a href="#id2980198">/etc/resolv.conf</a></dt><dt><a href="#id2978348">/etc/host.conf</a></dt><dt><a href="#id2978390">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2978479">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2978604">The NetBIOS Name Cache</a></dt><dt><a href="#id2978648">The LMHOSTS file</a></dt><dt><a href="#id2978762">HOSTS file</a></dt><dt><a href="#id2978795">DNS Lookup</a></dt><dt><a href="#id2978820">WINS Lookup</a></dt></dl></dd><dt><a href="#id2978890">Common Errors</a></dt><dd><dl><dt><a href="#id2978906">My Boomerang Won't Come Back</a></dt><dt><a href="#id2978938">Very Slow Network Connections</a></dt><dt><a href="#id2978989">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2979144">Features and Benefits</a></dt><dt><a href="#id2979186">What are charsets and unicode?</a></dt><dt><a href="#id2979255">Samba and charsets</a></dt><dt><a href="#id2979355">Conversion from old names</a></dt><dt><a href="#id2979401">Japanese charsets</a></dt></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2981995">Note</a></dt><dt><a href="#id2982016">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2981826">Note</a></dt></dl></dd></dl></dd><dt>IV. <a href="#migration">Migration and Updating</a></dt><dd><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2983161">Charsets</a></dt><dt><a href="#id2983184">Obsolete configuration options</a></dt><dt><a href="#id2983238">Password Backend</a></dt></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2982481">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2982505">Objectives</a></dt><dt><a href="#id2981433">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2983650">Migration Options</a></dt><dd><dl><dt><a href="#id2983731">Planning for Success</a></dt><dt><a href="#id2983972">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2984279">Features and Benefits</a></dt><dd><dl><dt><a href="#id2984129">Enabling SWAT for use</a></dt><dt><a href="#id2985018">Securing SWAT through SSL</a></dt><dt><a href="#id2985131">The SWAT Home Page</a></dt><dt><a href="#id2985194">Global Settings</a></dt><dt><a href="#id2985300">Share Settings</a></dt><dt><a href="#id2985365">Printers Settings</a></dt><dt><a href="#id2985429">The SWAT Wizard</a></dt><dt><a href="#id2985477">The Status Page</a></dt><dt><a href="#id2985529">The View Page</a></dt><dt><a href="#id2985552">The Password Change Page</a></dt></dl></dd></dl></dd></dl></dd><dt>V. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>33. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2985673">Introduction</a></dt><dt><a href="#id2985707">Assumptions</a></dt><dt><a href="#id2985879">The tests</a></dt><dt><a href="#id2989430">Still having troubles?</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2990823">Diagnostics tools</a></dt><dt><a href="#id2989549">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2989832">Useful URL's</a></dt><dt><a href="#id2989876">Getting help from the mailing lists</a></dt><dt><a href="#id2990029">How to get off the mailinglists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2992343">Introduction</a></dt><dt><a href="#id2992402">General info</a></dt><dt><a href="#id2992438">Debug levels</a></dt><dt><a href="#id2990534">Internal errors</a></dt><dt><a href="#id2990642">Attaching to a running process</a></dt><dt><a href="#id2990144">Patches</a></dt></dl></dd></dl></dd><dt>VI. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>36. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2990261">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2990268">Introduction</a></dt><dt><a href="#id2990297">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2991766">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2991814">Verifying Samba's PGP signature</a></dt><dt><a href="#id2991949">Building the Binaries</a></dt><dd><dl><dt><a href="#id2992086">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2992982">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2993073">Starting from inetd.conf</a></dt><dt><a href="#id2993277">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2993372">Common Errors</a></dt></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2994651">HPUX</a></dt><dt><a href="#id2994736">SCO Unix</a></dt><dt><a href="#id2994764">DNIX</a></dt><dt><a href="#id2994934">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2994978">AIX</a></dt><dd><dl><dt><a href="#id2994984">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2995010">Solaris</a></dt><dd><dl><dt><a href="#id2995017">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2995794">Macintosh clients?</a></dt><dt><a href="#id2995866">OS2 Client</a></dt><dd><dl><dt><a href="#id2995873">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2995488">How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2995548">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2995645">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2995107">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2995197">Delete .pwl files after password change</a></dt><dt><a href="#id2995227">Configure WfW password handling</a></dt><dt><a href="#id2995273">Case handling of passwords</a></dt><dt><a href="#id2995303">Use TCP/IP as default protocol</a></dt><dt><a href="#id2995320">Speed improvement</a></dt></dl></dd><dt><a href="#id2995367">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2996396">Speed improvement</a></dt></dl></dd><dt><a href="#id2996420">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2996531">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2996649">Comparisons</a></dt><dt><a href="#id2996693">Socket options</a></dt><dt><a href="#id2996767">Read size</a></dt><dt><a href="#id2996811">Max xmit</a></dt><dt><a href="#id2996864">Log level</a></dt><dt><a href="#id2996886">Read raw</a></dt><dt><a href="#id2997829">Write raw</a></dt><dt><a href="#id2997871">Slow Logins</a></dt><dt><a href="#id2997892">LDAP</a></dt><dt><a href="#id2997917">Client tuning</a></dt><dt><a href="#id2997940">Samba performance problem due changing kernel</a></dt><dt><a href="#id2997973">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2998691">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2998110">Websites</a></dt><dt><a href="#id2998494">Related updates from microsoft</a></dt><dt><a href="#id2998561">Books</a></dt></dl></dd></dl></dd><dt><a href="#id2998572">Index</a></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>19.1. <a href="#id2933252">Windows Printing to a local Printer</a></dt><dt>19.2. <a href="#id2933404">Printing to a Postscript Printer</a></dt><dt>19.3. <a href="#id2933484">Ghostscript as a RIP for non-postscript printers</a></dt><dt>19.4. <a href="#id2947147">Prefiltering in CUPS to form Postscript</a></dt><dt>19.5. <a href="#id2947212">Adding Device-specific Print Options</a></dt><dt>19.6. <a href="#id2947314">Postscript to intermediate Raster format</a></dt><dt>19.7. <a href="#id2947366">CUPS-raster production using Ghostscript</a></dt><dt>19.8. <a href="#id2947461">Image format to CUPS-raster format conversion</a></dt><dt>19.9. <a href="#id2947546">Raster to Printer Specific formats</a></dt><dt>19.10. <a href="#id2948613">cupsomatic/foomatic processing versus Native CUPS</a></dt><dt>19.11. <a href="#id2949215">Print Driver execution on the Client</a></dt><dt>19.12. <a href="#id2949271">Print Driver execution on the Server</a></dt><dt>19.13. <a href="#id2949459">Printing via CUPS/samba server</a></dt><dt>19.14. <a href="#id2951240">cupsaddsmb flowchart</a></dt><dt>19.15. <a href="#id2956826">CUPS Printing Overview</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id2879589">Assumptions</a></dt><dt>10.1. <a href="#id2889940">Browse subnet example 1</a></dt><dt>10.2. <a href="#id2890050">Browse subnet example 2</a></dt><dt>10.3. <a href="#id2890149">Browse subnet example 3</a></dt><dt>10.4. <a href="#id2890249">Browse subnet example 4</a></dt><dt>11.1. <a href="#id2896974">Attributes in the sambaAccount objectclass (LDAP)</a></dt><dt>11.2. <a href="#id2897685">Basic smb.conf options for MySQL passdb backend</a></dt><dt>11.3. <a href="#id2897810">MySQL field names for MySQL passdb backend</a></dt><dt>13.1. <a href="#id2899431">Managing directories with unix and windows</a></dt><dt>13.2. <a href="#id2900001">User and Group Based Controls</a></dt><dt>13.3. <a href="#id2900234">File and Directory Permission Based Controls</a></dt><dt>13.4. <a href="#id2900482">Other Controls</a></dt><dt>20.1. <a href="#id2956961">Extended Auditing Log Information</a></dt><dt>24.1. <a href="#id2973257">User Shell Folder registry keys default values</a></dt><dt>24.2. <a href="#id2973402">Defaults of profile settings registry keys</a></dt><dt>24.3. <a href="#id2973656">Defaults of default user profile paths registry keys</a></dt><dt>25.1. <a href="#id2977860">Options recognized by pam_smbpass</a></dt><dt>31.1. <a href="#id2983665">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2983801">Nature of the Conversion Choices</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>12.1. <a href="#id2898973">smbgrpadd.sh</a></dt><dt>13.1. <a href="#id2899836">Example File</a></dt></dl></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2866390"></a>Preparing Samba for Configuration</h1></div></div><div></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba +existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876206">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876277">The machine trust account for this computer either does not +exist or is not accessible.</a></dt><dt><a href="#id2876340">When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.</a></dt><dt><a href="#id2876367">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2878532">Features And Benefits</a></dt><dt><a href="#id2878705">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878734">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2878954">Active Directory Domain Control</a></dt><dt><a href="#id2878975">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2879001">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2879047">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2879149">Example Configuration</a></dt></dl></dd><dt><a href="#id2879210">Common Errors</a></dt><dd><dl><dt><a href="#id2879224">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2879254">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2879287">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2879332">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2880401">Features and Benefits</a></dt><dt><a href="#id2880516">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2880692">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2880944">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2881141">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2881203">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2881406">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2881788">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2881929">Setup your smb.conf</a></dt><dt><a href="#id2882013">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882376">Notes</a></dt></dl></dd><dt><a href="#id2882398">Common Errors</a></dt><dd><dl><dt><a href="#id2882423">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882455">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2884809">Features and Benefits</a></dt><dt><a href="#id2885005">Background</a></dt><dt><a href="#id2885077">Example Configuration</a></dt><dd><dl><dt><a href="#id2885092">Reference Documentation Server</a></dt><dt><a href="#id2885142">Central Print Serving</a></dt></dl></dd><dt><a href="#id2885356">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2884469">Note</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2886062">Features and Benefits</a></dt><dt><a href="#id2886141">What is Browsing?</a></dt><dt><a href="#id2886251">Discussion</a></dt><dd><dl><dt><a href="#id2886267">NetBIOS over TCP/IP</a></dt><dt><a href="#id2886430">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2886562">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2886698">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2886824">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2887045">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2887315">Making Samba the domain master</a></dt><dt><a href="#id2887471">Note about broadcast addresses</a></dt><dt><a href="#id2887488">Multiple interfaces</a></dt><dt><a href="#id2887517">Use of the Remote Announce parameter</a></dt><dt><a href="#id2887626">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2887687">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2887846">Setting up a WINS server</a></dt><dt><a href="#id2888045">WINS Replication</a></dt><dt><a href="#id2888070">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2888154">Helpful Hints</a></dt><dd><dl><dt><a href="#id2888167">Windows Networking Protocols</a></dt><dt><a href="#id2888234">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2888372">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2888419">Browsing support in Samba</a></dt><dt><a href="#id2888526">Problem resolution</a></dt><dt><a href="#id2888605">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2889225">Common Errors</a></dt><dd><dl><dt><a href="#id2889240">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2889269">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2892812">Features and Benefits</a></dt><dt><a href="#id2893140">Technical Information</a></dt><dd><dl><dt><a href="#id2893204">Important Notes About Security</a></dt><dt><a href="#id2893458">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2893513">Account Management Tools</a></dt><dd><dl><dt><a href="#id2893545">The smbpasswd Command</a></dt><dt><a href="#id2893811">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2893963">Password Backends</a></dt><dd><dl><dt><a href="#id2893999">Plain Text</a></dt><dt><a href="#id2894038">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2894145">tdbsam</a></dt><dt><a href="#id2894173">ldapsam</a></dt><dt><a href="#id2895689">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2896493">Common Errors</a></dt><dd><dl><dt><a href="#id2896501">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2896516">Users are being added to the wrong backend database</a></dt><dt><a href="#id2896576">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and Unix Groups</a></dt><dd><dl><dt><a href="#id2903953">Features and Benefits</a></dt><dt><a href="#id2904055">Discussion</a></dt><dd><dl><dt><a href="#id2904246">Example Configuration</a></dt></dl></dd><dt><a href="#id2904310">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2904325">Sample smb.conf add group script</a></dt><dt><a href="#id2904393">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2904485">Common Errors</a></dt><dd><dl><dt><a href="#id2904501">Adding Groups Fails</a></dt><dt><a href="#id2904562">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2902775">Features and Benefits</a></dt><dt><a href="#id2902812">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902830">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2903087">Managing Directories</a></dt><dt><a href="#id2903183">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2903398">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2904578">User and Group Based Controls</a></dt><dt><a href="#id2904850">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2905095">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905311">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905383">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905682">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905690">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905728">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905807">Viewing file ownership</a></dt><dt><a href="#id2905929">Viewing File or Directory Permissions</a></dt><dt><a href="#id2906157">Modifying file or directory permissions</a></dt><dt><a href="#id2906309">Interaction with the standard Samba create mask + parameters</a></dt><dt><a href="#id2906639">Interaction with the standard Samba file attribute + mapping</a></dt></dl></dd><dt><a href="#id2906714">Common Errors</a></dt><dd><dl><dt><a href="#id2906729">Users can not write to a public share</a></dt><dt><a href="#id2907109">I have set force user and Samba still makes root the owner of all the files + I touch!</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2910721">Features and Benefits</a></dt><dt><a href="#id2910776">Discussion</a></dt><dd><dl><dt><a href="#id2910908">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2911554">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2911664">Example Configuration</a></dt></dl></dd><dt><a href="#id2911924">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2912154">Workstation Service Entries</a></dt><dt><a href="#id2912180">Server Service Entries</a></dt></dl></dd><dt><a href="#id2912260">Persistent Data Corruption</a></dt><dt><a href="#id2912291">Common Errors</a></dt><dd><dl><dt><a href="#id2912365">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2912394">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2914448">Introduction</a></dt><dt><a href="#id2914481">Features and Benefits</a></dt><dt><a href="#id2914555">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2914574">Using host based protection</a></dt><dt><a href="#id2914645">User based protection</a></dt><dt><a href="#id2914697">Using interface protection</a></dt><dt><a href="#id2914749">Using a firewall</a></dt><dt><a href="#id2914805">Using a IPC$ share deny</a></dt><dt><a href="#id2914866">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2914907">Upgrading Samba</a></dt><dt><a href="#id2914932">Common Errors</a></dt><dd><dl><dt><a href="#id2914949">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2914974">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2915881">Features and Benefits</a></dt><dt><a href="#id2915909">Trust Relationship Background</a></dt><dt><a href="#id2915993">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2916006">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2916091">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2916127">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2916155">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2916295">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2916428">Common Errors</a></dt><dd><dl><dt><a href="#id2916443">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2915783">Features and Benefits</a></dt><dt><a href="#id2917436">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2917027">Features and Benefits</a></dt><dt><a href="#id2917095">Technical Introduction</a></dt><dd><dl><dt><a href="#id2917133">What happens if you send a Job from a Client</a></dt><dt><a href="#id2917203">Printing Related Configuration Parameters</a></dt><dt><a href="#id2918120">Parameters Recommended for Use</a></dt><dt><a href="#id2918450">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2918559">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2918652">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2918721">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2918810">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2919116">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2919220">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2919234">The [global] Section</a></dt><dt><a href="#id2919616">The [printers] Section</a></dt><dt><a href="#id2919945">Any [my_printer_name] Section</a></dt><dt><a href="#id2920166">Print Commands</a></dt><dt><a href="#id2920216">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2920741">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2921021">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2921186">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2921338">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2921450">Creating the [print$] Share</a></dt><dt><a href="#id2921521">Parameters in the [print$] Section</a></dt><dt><a href="#id2921752">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2921913">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2922008">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2922192">Setting Drivers for existing Printers with +rpcclient</a></dt></dl></dd><dt><a href="#id2923912">"The Proof of the Pudding lies in the Eating" (Client Driver Install +Procedure)</a></dt><dd><dl><dt><a href="#id2923933">The first Client Driver Installation</a></dt><dt><a href="#id2924131">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2924420">Further Client Driver Install Procedures</a></dt><dt><a href="#id2924516">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2924657">Other Gotchas</a></dt><dd><dl><dt><a href="#id2924690">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2925127">Supporting large Numbers of Printers</a></dt><dt><a href="#id2925430">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2925673">Weird Error Message Cannot connect under a +different Name</a></dt><dt><a href="#id2925771">Be careful when assembling Driver Files</a></dt><dt><a href="#id2926117">Samba and Printer Ports</a></dt><dt><a href="#id2926188">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2926210">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2926256">What is Imprints?</a></dt><dt><a href="#id2926297">Creating Printer Driver Packages</a></dt><dt><a href="#id2926316">The Imprints Server</a></dt><dt><a href="#id2926340">The Installation Client</a></dt></dl></dd><dt><a href="#id2926492">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2926822">The addprinter command</a></dt><dt><a href="#id2926867">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2927036">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2927051">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2927064">I give my root password but I don't get access</a></dt><dt><a href="#id2927097">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2936290">Introduction</a></dt><dd><dl><dt><a href="#id2936298">Features and Benefits</a></dt><dt><a href="#id2936350">Overview</a></dt></dl></dd><dt><a href="#id2936405">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2936484">Linking of smbd with libcups.so</a></dt><dt><a href="#id2936628">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2936710">More complex smb.conf Settings for +CUPS</a></dt></dl></dd><dt><a href="#id2936828">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2936848">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2936875">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2936912">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2936970">Explicitly enable "raw" printing for +application/octet-stream!</a></dt><dt><a href="#id2937131">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2937224">Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2937300">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2937344">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2937445">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2937533">PostScript and Ghostscript</a></dt><dt><a href="#id2937630">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2937742">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2937813">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2937902">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2937925">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2938065">MIME types and CUPS Filters</a></dt><dt><a href="#id2938252">MIME type Conversion Rules</a></dt><dt><a href="#id2938369">Filter Requirements</a></dt><dt><a href="#id2938539">Prefilters</a></dt><dt><a href="#id2938624">pstops</a></dt><dt><a href="#id2938727">pstoraster</a></dt><dt><a href="#id2938883">imagetops and imagetoraster</a></dt><dt><a href="#id2938940">rasterto [printers specific]</a></dt><dt><a href="#id2939024">CUPS Backends</a></dt><dt><a href="#id2939336">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2939448">The Complete Picture</a></dt><dt><a href="#id2939464">mime.convs</a></dt><dt><a href="#id2939517">"Raw" printing</a></dt><dt><a href="#id2939571">"application/octet-stream" printing</a></dt><dt><a href="#id2939786">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2940015">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a></dt><dt><a href="#id2940170">Examples for filtering Chains</a></dt><dt><a href="#id2940401">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2940530">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2940605">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2940620">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2940659">Driver Execution on the Client</a></dt><dt><a href="#id2940731">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2940794">Network Printing (Windows clients -- UNIX/Samba Print +Servers)</a></dt><dd><dl><dt><a href="#id2940814">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2940978">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2941054">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2941110">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2941150">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2941216">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2941233">Printer Drivers running in "Kernel Mode" cause many +Problems</a></dt><dt><a href="#id2941268">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2941289">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2941316">PostScript Drivers with no major problems -- even in Kernel +Mode</a></dt></dl></dd><dt><a href="#id2941369"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2941388">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2941480">Prepare your smb.conf for +cupsaddsmb</a></dt><dt><a href="#id2941526">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2941724">Recognize the different Driver Files</a></dt><dt><a href="#id2941782">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2941814">ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"</a></dt><dt><a href="#id2941864">Caveats to be considered</a></dt><dt><a href="#id2942086">What are the Benefits of using the "CUPS PostScript Driver for +Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2942268">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2942369">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2942596">Understanding cupsaddsmb</a></dt><dt><a href="#id2942690">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2942777">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2942812">cupsaddsmb Flowchart</a></dt><dt><a href="#id2942865">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2942978">Avoiding critical PostScript Driver Settings on the +Client</a></dt></dl></dd><dt><a href="#id2943112">Installing PostScript Driver Files manually (using +rpcclient)</a></dt><dd><dl><dt><a href="#id2943227">A Check of the rpcclient man Page</a></dt><dt><a href="#id2943340">Understanding the rpcclient man Page</a></dt><dt><a href="#id2943429">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2943519">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2943682">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2944334">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2944435">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2944537">Trivial DataBase Files</a></dt><dt><a href="#id2944608">Binary Format</a></dt><dt><a href="#id2944670">Losing *.tdb Files</a></dt><dt><a href="#id2944728">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2944795">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2944903">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2945532">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2945993">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2946024">Setting up Quotas</a></dt><dt><a href="#id2946056">Correct and incorrect Accounting</a></dt><dt><a href="#id2946097">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2946169">The page_log File Syntax</a></dt><dt><a href="#id2946270">Possible Shortcomings</a></dt><dt><a href="#id2946341">Future Developments</a></dt><dt><a href="#id2946390">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2946404">Additional Material</a></dt><dt><a href="#id2946598">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2946644">CUPS Configuration Settings explained</a></dt><dt><a href="#id2946726">Pre-conditions</a></dt><dt><a href="#id2946787">Manual Configuration</a></dt></dl></dd><dt><a href="#id2946805">When not to use Samba to print to +CUPS</a></dt><dt><a href="#id2946822">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2946857">Where to find Documentation</a></dt><dt><a href="#id2946870">How to ask for Help</a></dt><dt><a href="#id2946883">Where to find Help</a></dt></dl></dd><dt><a href="#id2946896">Appendix</a></dt><dd><dl><dt><a href="#id2946904">Printing from CUPS to Windows attached +Printers</a></dt><dt><a href="#id2947118">More CUPS filtering Chains</a></dt><dt><a href="#id2947424">Trouble Shooting Guidelines to fix typical Samba printing +Problems</a></dt><dt><a href="#id2948546">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2960717">Features and Benefits</a></dt><dt><a href="#id2960735">Discussion</a></dt><dt><a href="#id2960826">Included modules</a></dt><dd><dl><dt><a href="#id2960833">audit</a></dt><dt><a href="#id2960871">extd_audit</a></dt><dt><a href="#id2960995">fake_perms</a></dt><dt><a href="#id2961013">recycle</a></dt><dt><a href="#id2961151">netatalk</a></dt></dl></dd><dt><a href="#id2961195">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2961218">DatabaseFS</a></dt><dt><a href="#id2961273">vscan</a></dt></dl></dd><dt><a href="#id2961303">Common Errors</a></dt></dl></dd><dt>21. <a href="#winbind">Integrated Logon Support using Winbind</a></dt><dd><dl><dt><a href="#id2962201">Features and Benefits</a></dt><dt><a href="#id2962229">Introduction</a></dt><dt><a href="#id2962301">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2962361">Target Uses</a></dt></dl></dd><dt><a href="#id2962392">How Winbind Works</a></dt><dd><dl><dt><a href="#id2962420">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2962454">Microsoft Active Directory Services</a></dt><dt><a href="#id2962477">Name Service Switch</a></dt><dt><a href="#id2962613">Pluggable Authentication Modules</a></dt><dt><a href="#id2962685">User and Group ID Allocation</a></dt><dt><a href="#id2962720">Result Caching</a></dt></dl></dd><dt><a href="#id2962747">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2962776">Introduction</a></dt><dt><a href="#id2962851">Requirements</a></dt><dt><a href="#id2962944">Testing Things Out</a></dt></dl></dd><dt><a href="#id2964563">Conclusion</a></dt><dt><a href="#id2964582">Common Errors</a></dt></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2967075">Features and Benefits</a></dt><dt><a href="#id2967264">Remote Server Administration</a></dt><dt><a href="#id2967363">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2967381">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2967592">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2967788">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2967822">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2966885">Features and Benefits</a></dt><dt><a href="#id2966939">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2968722">Windows 9x/Me Policies</a></dt><dt><a href="#id2968817">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2968950">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2969202">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2969303">Samba Editreg Toolset</a></dt><dt><a href="#id2969324">Windows NT4/200x</a></dt><dt><a href="#id2969344">Samba PDC</a></dt></dl></dd><dt><a href="#id2969388">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2969535">Common Errors</a></dt><dd><dl><dt><a href="#id2969549">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2970756">Features and Benefits</a></dt><dt><a href="#id2970790">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2970831">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971236">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972407">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972472">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972737">Mandatory profiles</a></dt><dt><a href="#id2972795">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972841">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972861">MS Windows 9x/Me</a></dt><dt><a href="#id2973009">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973563">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2974067">Common Errors</a></dt><dd><dl><dt><a href="#id2974080">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974143">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974365">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2978309">Features and Benefits</a></dt><dt><a href="#id2978577">Technical Discussion</a></dt><dd><dl><dt><a href="#id2978595">PAM Configuration Syntax</a></dt><dt><a href="#id2979265">Example System Configurations</a></dt><dt><a href="#id2979567">smb.conf PAM Configuration</a></dt><dt><a href="#id2979625">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2979709">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2980075">Common Errors</a></dt><dd><dl><dt><a href="#id2980089">pam_winbind problem</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2982211">Features and Benefits</a></dt><dt><a href="#id2982236">Background Information</a></dt><dt><a href="#id2982281">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2982337">/etc/hosts</a></dt><dt><a href="#id2982462">/etc/resolv.conf</a></dt><dt><a href="#id2982506">/etc/host.conf</a></dt><dt><a href="#id2982548">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2982637">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2982784">The NetBIOS Name Cache</a></dt><dt><a href="#id2982829">The LMHOSTS file</a></dt><dt><a href="#id2983073">HOSTS file</a></dt><dt><a href="#id2983105">DNS Lookup</a></dt><dt><a href="#id2983130">WINS Lookup</a></dt></dl></dd><dt><a href="#id2983200">Common Errors</a></dt><dd><dl><dt><a href="#id2983216">My Boomerang Won't Come Back</a></dt><dt><a href="#id2983248">Very Slow Network Connections</a></dt><dt><a href="#id2983300">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2984418">Features and Benefits</a></dt><dt><a href="#id2984620">What are charsets and unicode?</a></dt><dt><a href="#id2984690">Samba and charsets</a></dt><dt><a href="#id2984790">Conversion from old names</a></dt><dt><a href="#id2984835">Japanese charsets</a></dt></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2984038">Note</a></dt><dt><a href="#id2984063">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2985605">Note</a></dt></dl></dd></dl></dd><dt>IV. <a href="#migration">Migration and Updating</a></dt><dd><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2984190">Charsets</a></dt><dt><a href="#id2984215">Obsolete configuration options</a></dt><dt><a href="#id2985825">Password Backend</a></dt></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2983845">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2983873">Objectives</a></dt><dt><a href="#id2986549">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2986887">Migration Options</a></dt><dd><dl><dt><a href="#id2986968">Planning for Success</a></dt><dt><a href="#id2987210">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2986434">Features and Benefits</a></dt><dd><dl><dt><a href="#id2986468">Enabling SWAT for use</a></dt><dt><a href="#id2988827">Securing SWAT through SSL</a></dt><dt><a href="#id2988941">The SWAT Home Page</a></dt><dt><a href="#id2989005">Global Settings</a></dt><dt><a href="#id2989110">Share Settings</a></dt><dt><a href="#id2989175">Printers Settings</a></dt><dt><a href="#id2989239">The SWAT Wizard</a></dt><dt><a href="#id2989287">The Status Page</a></dt><dt><a href="#id2989339">The View Page</a></dt><dt><a href="#id2989362">The Password Change Page</a></dt></dl></dd></dl></dd></dl></dd><dt>V. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2988578">Introduction</a></dt><dt><a href="#id2990437">Assumptions</a></dt><dt><a href="#id2990614">The tests</a></dt><dt><a href="#id2991790">Still having troubles?</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2993414">Diagnostics tools</a></dt><dt><a href="#id2993555">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2993839">Useful URLs</a></dt><dt><a href="#id2993884">Getting help from the mailing lists</a></dt><dt><a href="#id2994036">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2994775">Introduction</a></dt><dt><a href="#id2994997">General info</a></dt><dt><a href="#id2995034">Debug levels</a></dt><dt><a href="#id2995176">Internal errors</a></dt><dt><a href="#id2995284">Attaching to a running process</a></dt><dt><a href="#id2995331">Patches</a></dt></dl></dd></dl></dd><dt>VI. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>36. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2994651">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2994658">Introduction</a></dt><dt><a href="#id2994688">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2996207">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2996256">Verifying Samba's PGP signature</a></dt><dt><a href="#id2996392">Building the Binaries</a></dt><dd><dl><dt><a href="#id2996529">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2996694">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2996786">Starting from inetd.conf</a></dt><dt><a href="#id2996990">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2997085">Common Errors</a></dt></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2995985">HPUX</a></dt><dt><a href="#id2998515">SCO Unix</a></dt><dt><a href="#id2998546">DNIX</a></dt><dt><a href="#id2998716">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2998760">AIX</a></dt><dd><dl><dt><a href="#id2998767">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2998793">Solaris</a></dt><dd><dl><dt><a href="#id2998800">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2998169">Macintosh clients?</a></dt><dt><a href="#id2999522">OS2 Client</a></dt><dd><dl><dt><a href="#id2999529">How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2999608">How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2999670">How do I get printer driver download working + for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2999766">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2999774">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2999864">Delete .pwl files after password change</a></dt><dt><a href="#id2999894">Configure WfW password handling</a></dt><dt><a href="#id2999940">Case handling of passwords</a></dt><dt><a href="#id2999970">Use TCP/IP as default protocol</a></dt><dt><a href="#id2999988">Speed improvement</a></dt></dl></dd><dt><a href="#id3000034">Windows '95/'98</a></dt><dd><dl><dt><a href="#id3000107">Speed improvement</a></dt></dl></dd><dt><a href="#id3000131">Windows 2000 Service Pack 2</a></dt><dt><a href="#id3000242">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id3001274">Comparisons</a></dt><dt><a href="#id3001319">Socket options</a></dt><dt><a href="#id3001394">Read size</a></dt><dt><a href="#id3001437">Max xmit</a></dt><dt><a href="#id3001490">Log level</a></dt><dt><a href="#id3001513">Read raw</a></dt><dt><a href="#id3001570">Write raw</a></dt><dt><a href="#id3001612">Slow Logins</a></dt><dt><a href="#id3001633">Client tuning</a></dt><dt><a href="#id3001658">Samba performance problem due changing kernel</a></dt><dt><a href="#id3001692">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id3001112">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id3001272">Websites</a></dt><dt><a href="#id3002922">Related updates from Microsoft</a></dt><dt><a href="#id3002990">Books</a></dt></dl></dd></dl></dd><dt><a href="#id3001039">Index</a></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>19.1. <a href="#id2937409">Windows Printing to a local Printer</a></dt><dt>19.2. <a href="#id2937580">Printing to a Postscript Printer</a></dt><dt>19.3. <a href="#id2937660">Ghostscript as a RIP for non-postscript printers</a></dt><dt>19.4. <a href="#id2938589">Prefiltering in CUPS to form Postscript</a></dt><dt>19.5. <a href="#id2938654">Adding Device-specific Print Options</a></dt><dt>19.6. <a href="#id2938756">Postscript to intermediate Raster format</a></dt><dt>19.7. <a href="#id2938809">CUPS-raster production using Ghostscript</a></dt><dt>19.8. <a href="#id2938904">Image format to CUPS-raster format conversion</a></dt><dt>19.9. <a href="#id2938988">Raster to Printer Specific formats</a></dt><dt>19.10. <a href="#id2940065">cupsomatic/foomatic processing versus Native CUPS</a></dt><dt>19.11. <a href="#id2940695">Print Driver execution on the Client</a></dt><dt>19.12. <a href="#id2940753">Print Driver execution on the Server</a></dt><dt>19.13. <a href="#id2940943">Printing via CUPS/samba server</a></dt><dt>19.14. <a href="#id2942830">cupsaddsmb flowchart</a></dt><dt>19.15. <a href="#id2948557">CUPS Printing Overview</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id2881417">Assumptions</a></dt><dt>10.1. <a href="#id2888772">Browse subnet example 1</a></dt><dt>10.2. <a href="#id2888886">Browse subnet example 2</a></dt><dt>10.3. <a href="#id2888985">Browse subnet example 3</a></dt><dt>10.4. <a href="#id2889086">Browse subnet example 4</a></dt><dt>11.1. <a href="#id2895163">Attributes in the sambaSamAccount objectclass (LDAP)</a></dt><dt>11.2. <a href="#id2895850">Basic smb.conf options for MySQL passdb backend</a></dt><dt>11.3. <a href="#id2895975">MySQL field names for MySQL passdb backend</a></dt><dt>13.1. <a href="#id2903107">Managing directories with unix and windows</a></dt><dt>13.2. <a href="#id2904638">User and Group Based Controls</a></dt><dt>13.3. <a href="#id2904871">File and Directory Permission Based Controls</a></dt><dt>13.4. <a href="#id2905118">Other Controls</a></dt><dt>20.1. <a href="#id2960912">Extended Auditing Log Information</a></dt><dt>24.1. <a href="#id2973359">User Shell Folder registry keys default values</a></dt><dt>24.2. <a href="#id2973503">Defaults of profile settings registry keys</a></dt><dt>24.3. <a href="#id2973759">Defaults of default user profile paths registry keys</a></dt><dt>25.1. <a href="#id2979741">Options recognized by pam_smbpass</a></dt><dt>31.1. <a href="#id2986904">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2987041">Nature of the Conversion Choices</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>12.1. <a href="#id2904348">smbgrpadd.sh</a></dt><dt>13.1. <a href="#id2903320">Example File</a></dt></dl></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2866833"></a>Preparing Samba for Configuration</h1></div></div><div></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba and how to configure the parts of samba you will most likely need. -PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2867729">Background</a></dt><dt><a href="#id2867783">Terminology</a></dt><dt><a href="#id2866506">Related Projects</a></dt><dt><a href="#id2866575">SMB Methodology</a></dt><dt><a href="#id2866662">Epilogue</a></dt><dt><a href="#id2866735">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2867501">Obtaining and installing samba</a></dt><dt><a href="#id2867544">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2867117">Example Configuration</a></dt><dt><a href="#id2867260">SWAT</a></dt></dl></dd><dt><a href="#id2867305">Try listing the shares available on your - server</a></dt><dt><a href="#id2866810">Try connecting with the unix client</a></dt><dt><a href="#id2866912">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2866973">What If Things Don't Work?</a></dt><dt><a href="#id2867003">Common Errors</a></dt><dd><dl><dt><a href="#id2867016">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2868395">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">FastStart for the Impatient</a></dt><dd><dl><dt><a href="#id2868843">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Chapter 1. Introduction to Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email"><<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>></tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867729">Background</a></dt><dt><a href="#id2867783">Terminology</a></dt><dt><a href="#id2866506">Related Projects</a></dt><dt><a href="#id2866575">SMB Methodology</a></dt><dt><a href="#id2866662">Epilogue</a></dt><dt><a href="#id2866735">Miscellaneous</a></dt></dl></div><p>“<span class="quote"> +PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2868116">Background</a></dt><dt><a href="#id2868327">Terminology</a></dt><dt><a href="#id2868481">Related Projects</a></dt><dt><a href="#id2868550">SMB Methodology</a></dt><dt><a href="#id2868638">Epilogue</a></dt><dt><a href="#id2868711">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2869372">Obtaining and installing samba</a></dt><dt><a href="#id2869412">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2869449">Example Configuration</a></dt><dt><a href="#id2869599">SWAT</a></dt></dl></dd><dt><a href="#id2869643">Try listing the shares available on your + server</a></dt><dt><a href="#id2869694">Try connecting with the unix client</a></dt><dt><a href="#id2869795">Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</a></dt><dt><a href="#id2869858">What If Things Don't Work?</a></dt><dt><a href="#id2869892">Common Errors</a></dt><dd><dl><dt><a href="#id2869904">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2870119">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2869247">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Chapter 1. Introduction to Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email"><<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>></tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2868116">Background</a></dt><dt><a href="#id2868327">Terminology</a></dt><dt><a href="#id2868481">Related Projects</a></dt><dt><a href="#id2868550">SMB Methodology</a></dt><dt><a href="#id2868638">Epilogue</a></dt><dt><a href="#id2868711">Miscellaneous</a></dt></dl></div><p>“<span class="quote"> "If you understand what you're doing, you're not learning anything." -- Anonymous </span>”</p><p> @@ -86,7 +86,7 @@ transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of strengths is that you can use it to blend your mix of Windows and Linux machines together without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867729"></a>Background</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868116"></a>Background</h2></div></div><div></div></div><p> Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only @@ -112,7 +112,7 @@ been dutifully waded through during the information-gathering stages of this pro are *still* many missing pieces... While often tedious, at least the way has been generously littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they thinking? -</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867783"></a>Terminology</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> +</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868327"></a>Terminology</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. </p></li><li><p> CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently @@ -162,7 +162,7 @@ thinking? W3K: Acronym for Windows 2003 Server </p></li></ul></div><p>If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at <a href="http://www.samba.org/" target="_top">http://www.samba.org</a>). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866506"></a>Related Projects</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868481"></a>Related Projects</h2></div></div><div></div></div><p> There are currently two network filesystem client projects for Linux that are directly related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself. </p><div class="itemizedlist"><ul type="disc"><li><p> @@ -173,7 +173,7 @@ related to Samba: SMBFS and CIFS VFS. These are both available in the Linux ker </p></li><li><p> CIFS VFS (Common Internet File System Virtual File System) is the successor to SMBFS, and is being actively developed for the upcoming version of the Linux kernel. The intent of this module - is to provide advanced network file system functionality including support for dfs (heirarchical + is to provide advanced network file system functionality including support for dfs (hierarchical name space), secure per-user session establishment, safe distributed caching (oplock), optional packet signing, Unicode and other internationalization improvements, and optional Winbind (nsswitch) integration. @@ -184,7 +184,7 @@ nothing to do with acting as a file and print server for SMB/CIFS clients. There are other Open Source CIFS client implementations, such as the <a href="http://jcifs.samba.org/" target="_top">jCIFS project</a> which provides an SMB client toolkit written in Java. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866575"></a>SMB Methodology</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868550"></a>SMB Methodology</h2></div></div><div></div></div><p> Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good @@ -216,7 +216,7 @@ up a single file. In general, SMB sessions are established in the following orde A good way to examine this process in depth is to try out <a href="http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html" target="_top">SecurityFriday's SWB program</a>. It allows you to walk through the establishment of a SMB/CIFS session step by step. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866662"></a>Epilogue</h2></div></div><div></div></div><p>“<span class="quote"> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868638"></a>Epilogue</h2></div></div><div></div></div><p>“<span class="quote"> What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft @@ -245,14 +245,14 @@ not the completely clueless user who probably sits there shivering thinking That's what's really irritating to me." </span>”</p><p>-- <a href="http://hr.uoregon.edu/davidrl/boot.txt" target="_top">Linus Torvalds, from an interview with BOOT Magazine, Sept 1998</a> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866735"></a>Miscellaneous</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868711"></a>Miscellaneous</h2></div></div><div></div></div><p> This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter 2. How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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 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">Karl</span> <span class="surname">Auer</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867501">Obtaining and installing samba</a></dt><dt><a href="#id2867544">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2867117">Example Configuration</a></dt><dt><a href="#id2867260">SWAT</a></dt></dl></dd><dt><a href="#id2867305">Try listing the shares available on your - server</a></dt><dt><a href="#id2866810">Try connecting with the unix client</a></dt><dt><a href="#id2866912">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2866973">What If Things Don't Work?</a></dt><dt><a href="#id2867003">Common Errors</a></dt><dd><dl><dt><a href="#id2867016">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2868395">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867501"></a>Obtaining and installing samba</h2></div></div><div></div></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter 2. How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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 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">Karl</span> <span class="surname">Auer</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869372">Obtaining and installing samba</a></dt><dt><a href="#id2869412">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2869449">Example Configuration</a></dt><dt><a href="#id2869599">SWAT</a></dt></dl></dd><dt><a href="#id2869643">Try listing the shares available on your + server</a></dt><dt><a href="#id2869694">Try connecting with the unix client</a></dt><dt><a href="#id2869795">Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client</a></dt><dt><a href="#id2869858">What If Things Don't Work?</a></dt><dt><a href="#id2869892">Common Errors</a></dt><dd><dl><dt><a href="#id2869904">Why are so many smbd processes eating memory?</a></dt><dt><a href="#id2870119">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869372"></a>Obtaining and installing samba</h2></div></div><div></div></div><p> Binary packages of samba are included in almost any Linux or Unix distribution. There are also some packages available at <a href="http://samba.org/" target="_top">the samba homepage</a>. @@ -260,41 +260,41 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li <a href="#compiling" title="Chapter 36. How to compile SAMBA">appropriate appendix chapter</a>.</p><p>If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow - for information about updating samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867544"></a>Configuring samba (smb.conf)</h2></div></div><div></div></div><p> + for information about updating samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869412"></a>Configuring samba (smb.conf)</h2></div></div><div></div></div><p> Samba's configuration is stored in the <tt class="filename">smb.conf</tt> file, that usually resides in <tt class="filename">/etc/samba/smb.conf</tt> or <tt class="filename">/usr/local/samba/lib/smb.conf</tt>. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the web-based interface swat, that is included with samba. - </p><div xmlns:ns2="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867117"></a>Example Configuration</h3></div></div><div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869449"></a>Example Configuration</h3></div></div><div></div></div><p> There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options. </p><p> The simplest useful configuration file would be something like this: - </p><ns2:p> - </ns2:p><pre class="programlisting"> + </p><p> + </p><pre class="programlisting"> [global] workgroup = MYGROUP [homes] guest ok = no read only = no - </pre><ns2:p> - </ns2:p><p> + </pre><p> + </p><p> This will allow connections by anyone with an account on the server, using either their login name or "<i class="parameter"><tt>homes</tt></i>" as the service name. (Note that the workgroup that Samba must also be set.) </p><p> Make sure you put the <tt class="filename">smb.conf</tt> file in the same place - you specified in the<tt class="filename">Makefile</tt> (the default is to + you specified in the <tt class="filename">Makefile</tt> (the default is to look for it in <tt class="filename">/usr/local/samba/lib/</tt>). </p><p> For more information about security settings for the <i class="parameter"><tt>[homes]</tt></i> share please refer to the chapter <a href="#securing-samba" title="Chapter 15. Securing Samba">Securing Samba</a>. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867207"></a>Test your config file with <b class="command">testparm</b></h4></div></div><div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869544"></a>Test your config file with <b class="command">testparm</b></h4></div></div><div></div></div><p> It's important that you test the validity of your <tt class="filename">smb.conf</tt> file using the <span class="application">testparm</span> program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -302,7 +302,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li Make sure it runs OK and that the services look reasonable before proceeding. </p><p> Always run testparm again when you change <tt class="filename">smb.conf</tt>! - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867260"></a>SWAT</h3></div></div><div></div></div><p> + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869599"></a>SWAT</h3></div></div><div></div></div><p> SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage @@ -318,7 +318,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867305"></a>Try listing the shares available on your + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869643"></a>Try listing the shares available on your server</h2></div></div><div></div></div><p><tt class="prompt">$ </tt><b class="userinput"><tt>smbclient -L <i class="replaceable"><tt>yourhostname</tt></i></tt></b></p><p>You should get back a list of shares available on your server. If you don't then something is incorrectly setup. @@ -328,7 +328,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li See the <b class="command">smbclient</b> man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866810"></a>Try connecting with the unix client</h2></div></div><div></div></div><p><tt class="prompt">$ </tt><b class="userinput"><tt>smbclient <i class="replaceable"><tt> + with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869694"></a>Try connecting with the unix client</h2></div></div><div></div></div><p><tt class="prompt">$ </tt><b class="userinput"><tt>smbclient <i class="replaceable"><tt> //yourhostname/aservice</tt></i></tt></b></p><p>Typically the <i class="replaceable"><tt>yourhostname</tt></i> would be the name of the host where you installed <span class="application">smbd</span>. The <i class="replaceable"><tt>aservice</tt></i> is @@ -337,18 +337,18 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li section in <tt class="filename">smb.conf</tt>.</p><p>For example if your unix host is <i class="replaceable"><tt>bambi</tt></i> and your login name is <i class="replaceable"><tt>fred</tt></i> you would type:</p><p><tt class="prompt">$ </tt><b class="userinput"><tt>smbclient //<i class="replaceable"><tt>bambi</tt></i>/<i class="replaceable"><tt>fred</tt></i> - </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866912"></a>Try connecting from a DOS, WfWg, Win9x, WinNT, + </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869795"></a>Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</h2></div></div><div></div></div><p>Try mounting disks. eg:</p><p><tt class="prompt">C:\WINDOWS\> </tt><b class="userinput"><tt>net use d: \\servername\service </tt></b></p><p>Try printing. eg:</p><p><tt class="prompt">C:\WINDOWS\> </tt><b class="userinput"><tt>net use lpt1: \\servername\spoolservice</tt></b></p><p><tt class="prompt">C:\WINDOWS\> </tt><b class="userinput"><tt>print filename - </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866973"></a>What If Things Don't Work?</h2></div></div><div></div></div><p>Then you might read the file chapter - <a href="#diagnosis" title="Chapter 33. The samba checklist">Diagnosis</a> and the + </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869858"></a>What If Things Don't Work?</h2></div></div><div></div></div><p>Then you might read the file chapter + <a href="#diagnosis" title="Chapter 33. The Samba checklist">Diagnosis</a> and the FAQ. If you are still stuck then try to follow the <a href="#problems" title="Chapter 34. Analysing and solving samba problems">Analysing and Solving Problems chapter</a> Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867003"></a>Common Errors</h2></div></div><div></div></div><p> + so maybe someone else has hit your problem and has overcome it. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869892"></a>Common Errors</h2></div></div><div></div></div><p> The following questions and issues get raised on the samba mailing list over and over again. -</p><div xmlns:ns3="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867016"></a>Why are so many smbd processes eating memory?</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869904"></a>Why are so many smbd processes eating memory?</h3></div></div><div></div></div><p> “<span class="quote"> Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba. Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem @@ -360,8 +360,8 @@ processes of smbd running: Is samba suppose to start this many different smbd processes? Or does it run as one smbd process? Also is it normal for it to be taking up this much memory? </span>” -</p><ns3:p> -</ns3:p><pre class="screen"> +</p><p> +</p><pre class="screen"> Inuse * 4096 = amount of memory being used by this process Pid Command Inuse Pin Pgsp Virtual 64-bit Mthrd @@ -388,8 +388,8 @@ Inuse * 4096 = amount of memory being used by this process 19110 smbd 8404 1906 181 4862 N N Total memory used: 841,592,832 bytes -</pre><ns3:p> -</ns3:p><p> +</pre><p> +</p><p> Samba consists on three core programs: <span class="application">nmbd</span>, <span class="application">smbd</span>, <span class="application">winbindd</span>. <span class="application">nmbd</span> is the name server message daemon, <span class="application">smbd</span> is the server message daemon, <span class="application">winbindd</span> is the daemon that @@ -404,22 +404,22 @@ connection made. That is why you are seeing so many of them, one (1) per client </p><p> <span class="application">winbindd</span> will run as one or two daemons, depending on whether or not it is being run in "split mode" (in which case there will be two instances). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868395"></a>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</h3></div></div><div></div></div><p>Your loopback device isn't working correctly. Make sure it's running. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter 3. FastStart for the Impatient</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2868843">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868843"></a>Note</h2></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870119"></a>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</h3></div></div><div></div></div><p>Your loopback device isn't working correctly. Make sure it's running. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter 3. Fast Start for the Impatient</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2869247">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869247"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. -</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2868870"></a>First Steps in Server Configuration</h1></div></div><div></div></div><p> +</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2869315"></a>First Steps in Server Configuration</h1></div></div><div></div></div><p> Samba can operate in various modes within SMB networks. This HOWTO section contains information on configuring samba to function as the type of server your network requires. Please read this section carefully. -</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2871915">Features and Benefits</a></dt><dt><a href="#id2872007">Server Types</a></dt><dt><a href="#id2872088">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2868518">User Level Security</a></dt><dt><a href="#id2868651">Share Level Security</a></dt><dt><a href="#id2869720">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2869962">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2870046">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2870271">Seamless Windows Network Integration</a></dt><dt><a href="#id2870448">Common Errors</a></dt><dd><dl><dt><a href="#id2870476">What makes Samba a SERVER?</a></dt><dt><a href="#id2870509">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2870537">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872449">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2875080">Features and Benefits</a></dt><dt><a href="#id2872678">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2872693">Domain Controller Types</a></dt><dt><a href="#id2872892">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2873207">Domain Control - Example Configuration</a></dt><dt><a href="#id2873503">Samba ADS Domain Control</a></dt><dt><a href="#id2873526">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2873540">Domain Network Logon Service</a></dt><dt><a href="#id2876260">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876365">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876372">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876411">I get told "You already have a connection to the Domain...." +</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2871270">Features and Benefits</a></dt><dt><a href="#id2871366">Server Types</a></dt><dt><a href="#id2871450">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2871565">User Level Security</a></dt><dt><a href="#id2871698">Share Level Security</a></dt><dt><a href="#id2871820">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2872071">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2872158">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2872383">Seamless Windows Network Integration</a></dt><dt><a href="#id2872559">Common Errors</a></dt><dd><dl><dt><a href="#id2872587">What makes Samba a SERVER?</a></dt><dt><a href="#id2872620">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2872649">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872682">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2874489">Features and Benefits</a></dt><dt><a href="#id2874793">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2874809">Domain Controller Types</a></dt><dt><a href="#id2875020">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2875340">Domain Control - Example Configuration</a></dt><dt><a href="#id2875639">Samba ADS Domain Control</a></dt><dt><a href="#id2875661">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2875676">Domain Network Logon Service</a></dt><dt><a href="#id2876003">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876111">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876118">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876157">I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876460">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876531">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2876588">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt><dt><a href="#id2876615">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2878646">Features And Benefits</a></dt><dt><a href="#id2878811">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878839">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2876805">Active Directory Domain Control</a></dt><dt><a href="#id2876826">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2876850">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2876875">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2876945">Example Configuration</a></dt></dl></dd><dt><a href="#id2876995">Common Errors</a></dt><dd><dl><dt><a href="#id2877009">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2877034">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2877067">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2877096">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2877621">Features and Benefits</a></dt><dt><a href="#id2877192">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2877352">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879134">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2879331">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879386">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#id2879531">Domain Member Server</a></dt><dd><dl><dt><a href="#id2879579">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2882177">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2882315">Setup your smb.conf</a></dt><dt><a href="#id2882398">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882740">Notes</a></dt></dl></dd><dt><a href="#id2882762">Common Errors</a></dt><dd><dl><dt><a href="#id2882784">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882816">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2884259">Features and Benefits</a></dt><dt><a href="#id2884297">Background</a></dt><dt><a href="#id2884365">Example Configuration</a></dt><dd><dl><dt><a href="#id2882967">Reference Documentation Server</a></dt><dt><a href="#id2883015">Central Print Serving</a></dt></dl></dd><dt><a href="#id2883221">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2883589">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter 4. Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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 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="#id2871915">Features and Benefits</a></dt><dt><a href="#id2872007">Server Types</a></dt><dt><a href="#id2872088">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2868518">User Level Security</a></dt><dt><a href="#id2868651">Share Level Security</a></dt><dt><a href="#id2869720">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2869962">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2870046">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2870271">Seamless Windows Network Integration</a></dt><dt><a href="#id2870448">Common Errors</a></dt><dd><dl><dt><a href="#id2870476">What makes Samba a SERVER?</a></dt><dt><a href="#id2870509">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2870537">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872449">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></div><p> +existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876206">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876277">The machine trust account for this computer either does not +exist or is not accessible.</a></dt><dt><a href="#id2876340">When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.</a></dt><dt><a href="#id2876367">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2878532">Features And Benefits</a></dt><dt><a href="#id2878705">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878734">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2878954">Active Directory Domain Control</a></dt><dt><a href="#id2878975">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2879001">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2879047">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2879149">Example Configuration</a></dt></dl></dd><dt><a href="#id2879210">Common Errors</a></dt><dd><dl><dt><a href="#id2879224">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2879254">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2879287">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2879332">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2880401">Features and Benefits</a></dt><dt><a href="#id2880516">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2880692">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2880944">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2881141">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2881203">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2881406">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2881788">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2881929">Setup your smb.conf</a></dt><dt><a href="#id2882013">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882376">Notes</a></dt></dl></dd><dt><a href="#id2882398">Common Errors</a></dt><dd><dl><dt><a href="#id2882423">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882455">Adding Machine to Domain Fails</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2884809">Features and Benefits</a></dt><dt><a href="#id2885005">Background</a></dt><dt><a href="#id2885077">Example Configuration</a></dt><dd><dl><dt><a href="#id2885092">Reference Documentation Server</a></dt><dt><a href="#id2885142">Central Print Serving</a></dt></dl></dd><dt><a href="#id2885356">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2884469">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter 4. Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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 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="#id2871270">Features and Benefits</a></dt><dt><a href="#id2871366">Server Types</a></dt><dt><a href="#id2871450">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2871565">User Level Security</a></dt><dt><a href="#id2871698">Share Level Security</a></dt><dt><a href="#id2871820">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2872071">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2872158">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2872383">Seamless Windows Network Integration</a></dt><dt><a href="#id2872559">Common Errors</a></dt><dd><dl><dt><a href="#id2872587">What makes Samba a SERVER?</a></dt><dt><a href="#id2872620">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2872649">What makes Samba a Domain Member?</a></dt><dt><a href="#id2872682">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></div><p> This chapter provides information regarding the types of server that Samba may be configured to be. A Microsoft network administrator who wishes to migrate to or to use Samba will want to know what, within a Samba context, terms familiar to MS Windows -adminstrator mean. This means that it is essential also to define how critical security +administrator mean. This means that it is essential also to define how critical security modes function BEFORE we get into the details of how to configure the server itself. </p><p> The chapter provides an overview of the security modes of which Samba is capable @@ -428,9 +428,9 @@ and how these relate to MS Windows servers and clients. Firstly we should recognise the question so often asked, "Why would I want to use Samba?" So, in those chapters where the answer may be important you will see a section that highlights features and benefits. These may be for or against Samba. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871915"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871270"></a>Features and Benefits</h2></div></div><div></div></div><p> Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It -hurt his toe and lodged in his sandle. He took the stone out and cursed it with a passion +hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion and fury fitting his anguish. The other looked at the stone and said, that is a garnet - I can turn that into a precious gem and some day it will make a princess very happy! </p><p> @@ -464,13 +464,13 @@ So now, what are the benefits of features mentioned in this chapter? greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872007"></a>Server Types</h2></div></div><div></div></div><p>Adminstrators of Microsoft networks often refer to three + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871366"></a>Server Types</h2></div></div><div></div></div><p>Administrators of Microsoft networks often refer to three different type of servers:</p><div class="itemizedlist"><ul type="disc"><li><p>Domain Controller</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Primary Domain Controller</td></tr><tr><td>Backup Domain Controller</td></tr><tr><td>ADS Domain Controller</td></tr></table></li><li><p>Domain Member Server</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Active Directory Member Server</td></tr><tr><td>NT4 Style Domain Member Server</td></tr></table></li><li><p>Stand Alone Server</p></li></ul></div><p> The chapters covering Domain Control, Backup Domain Control and Domain Membership provide pertinent information regarding Samba-3 configuration for each of these server roles. The reader is strongly encouraged to become intimately familiar with the information presented. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872088"></a>Samba Security Modes</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="id2871450"></a>Samba Security Modes</h2></div></div><div></div></div><p> In this section the function and purpose of Samba's <i class="parameter"><tt>security</tt></i> modes are described. An accurate understanding of how Samba implements each security mode as well as how to configure MS Windows clients for each mode will significantly @@ -494,7 +494,7 @@ the way the client then tries to authenticate itself. It does not directly affec but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is allowed. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868518"></a>User Level Security</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871565"></a>User Level Security</h3></div></div><div></div></div><p> We will describe <i class="parameter"><tt>user level</tt></i> security first, as it's simpler. In <span class="emphasis"><em>user level</em></span> security, the client will send a <span class="emphasis"><em>session setup</em></span> command directly after the protocol negotiation. @@ -512,13 +512,13 @@ It is also possible for a client to send multiple <span class="emphasis"><em>ses requests. When the server responds, it gives the client a <span class="emphasis"><em>uid</em></span> to use as an authentication tag for that username/password. The client can maintain multiple authentication contexts in this way (WinDD is an example of an application that does this). -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868612"></a>Example Configuration</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871659"></a>Example Configuration</h4></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>User Level Security</em></span> is: </p><pre class="programlisting"> security = user </pre><p> This is the default setting since samba-2.2.x. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868651"></a>Share Level Security</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871698"></a>Share Level Security</h3></div></div><div></div></div><p> Ok, now for share level security. In share level security, the client authenticates itself separately for each share. It will send a password along with each <span class="emphasis"><em>tree connection</em></span> (share mount). It does not explicitly send a @@ -541,18 +541,18 @@ of the share they try to connect to (useful for home directories) and any users listed in the <i class="parameter"><tt>user =</tt></i> <tt class="filename">smb.conf</tt> line. The password is then checked in turn against these <span class="emphasis"><em>possible usernames</em></span>. If a match is found then the client is authenticated as that user. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868731"></a>Example Configuration</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871778"></a>Example Configuration</h4></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>Share Level Security</em></span> is: </p><pre class="programlisting"> security = share </pre><p> Please note that there are reports that recent MS Windows clients do not like to work with share mode security servers. You are strongly discouraged from using share level security. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869720"></a>Domain Security Mode (User Level Security)</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871820"></a>Domain Security Mode (User Level Security)</h3></div></div><div></div></div><p> When Samba is operating in <i class="parameter"><tt>security = domain</tt></i> mode, the Samba server has a domain security trust account (a machine account) and will cause all authentication requests to be passed through to the domain controllers. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869742"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2871842"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> Samba as a Domain Member Server </em></span></p><p> This method involves addition of the following parameters in the <tt class="filename">smb.conf</tt> file: @@ -564,20 +564,20 @@ In order for this method to work, the Samba server needs to join the MS Windows security domain. This is done as follows: </p><div class="procedure"><ol type="1"><li><p>On the MS Windows NT domain controller, using the Server Manager, add a machine account for the Samba server. - </p></li><li><p>Next, on the Unix/Linux system execute:</p><p><tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -j DOMAIN_NAME -r PDC_NAME</tt></b> (samba-2.x)</p><p><tt class="prompt">root# </tt><b class="userinput"><tt>net join -U administrator%password</tt></b> (samba-3)</p></li></ol></div><div xmlns:ns4="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><ns4:p> + </p></li><li><p>Next, on the Unix/Linux system execute:</p><p><tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -j DOMAIN_NAME -r PDC_NAME</tt></b> (samba-2.x)</p><p><tt class="prompt">root# </tt><b class="userinput"><tt>net join -U administrator%password</tt></b> (samba-3)</p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> As of Samba-2.2.4 the Samba 2.2.x series can auto-join a Windows NT4 style Domain just by executing: -</ns4:p><pre class="screen"> +</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -j <i class="replaceable"><tt>DOMAIN_NAME</tt></i> -r <i class="replaceable"><tt>PDC_NAME</tt></i> -U Administrator%<i class="replaceable"><tt>password</tt></i></tt></b> -</pre><ns4:p> +</pre><p> As of Samba-3 the same can be done by executing: -</ns4:p><pre class="screen"> +</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net join -U Administrator%<i class="replaceable"><tt>password</tt></i></tt></b> -</pre><ns4:p> +</pre><p> It is not necessary with Samba-3 to specify the <i class="replaceable"><tt>DOMAIN_NAME</tt></i> or the <i class="replaceable"><tt>PDC_NAME</tt></i> as it figures this out from the <tt class="filename">smb.conf</tt> file settings. -</ns4:p></div><p> +</p></div><p> Use of this mode of authentication does require there to be a standard Unix account for each user in order to assign a uid once the account has been authenticated by the remote Windows DC. This account can be blocked to prevent logons by clients other than @@ -590,7 +590,7 @@ in this HOWTO collection. </p><p> For more information of being a domain member, see the <a href="#domain-member" title="Chapter 7. Domain Membership">Domain Member</a> section of this Howto. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869962"></a>ADS Security Mode (User Level Security)</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872071"></a>ADS Security Mode (User Level Security)</h3></div></div><div></div></div><p> Both Samba 2.2 and 3.0 can join an Active Directory domain. This is possible even if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style domain members, contrary to @@ -604,7 +604,7 @@ authentication protocols. All your machines are running Windows 2000 and above and all use full Kerberos. In this case Samba as a NT4-style domain would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2869993"></a>Example Configuration</h4></div></div><div></div></div><pre class="programlisting"> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872101"></a>Example Configuration</h4></div></div><div></div></div><pre class="programlisting"> realm = your.kerberos.REALM security = ADS </pre><p> @@ -614,7 +614,7 @@ AD-member mode can accept Kerberos. </pre><p> Please refer to the <a href="#domain-member" title="Chapter 7. Domain Membership">Domain Membership</a> and <a href="#ads-member" title="Samba ADS Domain Membership">Active Directory Membership</a> sections for more information regarding this configuration option. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870046"></a>Server Security (User Level Security)</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872158"></a>Server Security (User Level Security)</h3></div></div><div></div></div><p> Server security mode is a left over from the time when Samba was not capable of acting as a domain member server. It is highly recommended NOT to use this feature. Server security mode has many draw backs. The draw backs include: @@ -646,7 +646,7 @@ lookups because the choice of the target authentication server is arbitrary and be determined from a domain name. In essence, a Samba server that is in <span class="emphasis"><em>server security mode</em></span> is operating in what used to be known as workgroup mode. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870203"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872314"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> Using MS Windows NT as an authentication server </em></span></p><p> This method involves the additions of the following parameters in the <tt class="filename">smb.conf</tt> file: @@ -667,7 +667,7 @@ certain number of failed authentication attempts this will result in user lockou </p><p> Use of this mode of authentication does require there to be a standard Unix account for the user, though this account can be blocked to prevent logons by non-SMB/CIFS clients. -</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870271"></a>Seamless Windows Network Integration</h2></div></div><div></div></div><p> +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872383"></a>Seamless Windows Network Integration</h2></div></div><div></div></div><p> MS Windows clients may use encrypted passwords as part of a challenge/response authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear text strings for simple password based authentication. It should be realized that with the SMB protocol, @@ -679,7 +679,7 @@ is encrypted in two ways: </p><div class="itemizedlist"><ul type="disc"><li><p>An MD4 hash of the UNICODE of the password string. This is known as the NT hash. </p></li><li><p>The password is converted to upper case, - and then padded or trucated to 14 bytes. This string is + and then padded or truncated to 14 bytes. This string is then appended with 5 bytes of NULL characters and split to form two 56 bit DES keys to encrypt a "magic" 8 byte value. The resulting 16 bytes form the LanMan hash. @@ -705,7 +705,7 @@ The following parameters can be used to work around the issue of Windows 9x clie upper casing usernames and password before transmitting them to the SMB server when using clear text authentication. </p><pre class="programlisting"> - <a href="smb.conf.5.html#PASSWORDLEVEL" target="_top">passsword level</a> = <i class="replaceable"><tt>integer</tt></i> + <a href="smb.conf.5.html#PASSWORDLEVEL" target="_top">password level</a> = <i class="replaceable"><tt>integer</tt></i> <a href="smb.conf.5.html#USERNAMELEVEL" target="_top">username level</a> = <i class="replaceable"><tt>integer</tt></i> </pre><p> By default Samba will lower case the username before attempting to lookup the user @@ -726,29 +726,29 @@ try them one by one until a match is located (or all combinations fail). The best option to adopt is to enable support for encrypted passwords where ever Samba is used. Most attempts to apply the registry change to re-enable plain text passwords will eventually lead to user complaints and unhappiness. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870448"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872559"></a>Common Errors</h2></div></div><div></div></div><p> We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake made in a developmental test lab is expected. </p><p> Here we look at common mistakes and misapprehensions that have been the subject of discussions on the Samba mailing lists. Many of these are avoidable by doing you homework before attempting -a Samba implementation. Some are the result of misundertanding of the English language. The +a Samba implementation. Some are the result of misunderstanding of the English language. The English language has many turns of phrase that are potentially vague and may be highly confusing to those for whom English is not their native tongue. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870476"></a>What makes Samba a SERVER?</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872587"></a>What makes Samba a SERVER?</h3></div></div><div></div></div><p> To some the nature of the Samba <span class="emphasis"><em>security</em></span> mode is very obvious, but entirely wrong all the same. It is assumed that <i class="parameter"><tt>security = server</tt></i> means that Samba will act as a server. Not so! See above - this setting means that Samba will <span class="emphasis"><em>try</em></span> to use another SMB server as its source of user authentication alone. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870509"></a>What makes Samba a Domain Controller?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872620"></a>What makes Samba a Domain Controller?</h3></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter <i class="parameter"><tt>security = domain</tt></i> does NOT really make Samba behave as a Domain Controller! This setting means we want Samba to be a domain member! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870537"></a>What makes Samba a Domain Member?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872649"></a>What makes Samba a Domain Member?</h3></div></div><div></div></div><p> Guess! So many others do. But whatever you do, do NOT think that <i class="parameter"><tt>security = user</tt></i> makes Samba act as a domain member. Read the manufacturers manual before the warranty expires! See the <a href="#domain-member" title="Chapter 7. Domain Membership">Domain Member</a> section of this Howto for more information. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872449"></a>Constantly Losing Connections to Password Server</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872682"></a>Constantly Losing Connections to Password Server</h3></div></div><div></div></div><p> Why does server_validate() simply give up rather than re-establishing its connection to the password server? Though I am not fluent in the SMB protocol, perhaps the cluster server process passes along to its client workstation the session key it receives from the password @@ -757,11 +757,11 @@ connection, whose session key would be different. So server_validate() must giv </p><p> Indeed. That's why security = server is at best a nasty hack. Please use security = domain. <i class="parameter"><tt>security = server</tt></i> mode is also known as pass-through authentication. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter 5. Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2875080">Features and Benefits</a></dt><dt><a href="#id2872678">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2872693">Domain Controller Types</a></dt><dt><a href="#id2872892">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2873207">Domain Control - Example Configuration</a></dt><dt><a href="#id2873503">Samba ADS Domain Control</a></dt><dt><a href="#id2873526">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2873540">Domain Network Logon Service</a></dt><dt><a href="#id2876260">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876365">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876372">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876411">I get told "You already have a connection to the Domain...." +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter 5. Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2874489">Features and Benefits</a></dt><dt><a href="#id2874793">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2874809">Domain Controller Types</a></dt><dt><a href="#id2875020">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2875340">Domain Control - Example Configuration</a></dt><dt><a href="#id2875639">Samba ADS Domain Control</a></dt><dt><a href="#id2875661">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2875676">Domain Network Logon Service</a></dt><dt><a href="#id2876003">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2876111">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2876118">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2876157">I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876460">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876531">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2876588">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt><dt><a href="#id2876615">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</a></dt></dl></dd></dl></div><p><b><span class="emphasis"><em>The Essence of Learning:</em></span> </b> +existing set.." when creating a machine trust account.</a></dt><dt><a href="#id2876206">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2876277">The machine trust account for this computer either does not +exist or is not accessible.</a></dt><dt><a href="#id2876340">When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.</a></dt><dt><a href="#id2876367">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</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 @@ -774,7 +774,7 @@ of persistent niggles that may be caused by broken network or system configurati 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><p> -From the Samba mailing list one can readilly identify many common networking issues. +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: @@ -791,7 +791,7 @@ burden on an organisation. Where is the right place to make mistakes? Only out of harm's way! If you are going to make mistakes, then please do this on a test network, away from users and in such a way as to not inflict pain on others. Do your learning on a test network. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875080"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874489"></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 @@ -854,7 +854,7 @@ Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to user and machine trust account information in a suitable backend data store. With Samba-3 there can be multiple back-ends for this including: </p><div class="itemizedlist"><ul type="disc"><li><p> - <span class="emphasis"><em>smbpasswd</em></span> - the plain ascii file stored used by + <span class="emphasis"><em>smbpasswd</em></span> - the plain ASCII file stored used by earlier versions of Samba. This file configuration option requires a Unix/Linux system account for EVERY entry (ie: both for user and for machine accounts). This file will be located in the <span class="emphasis"><em>private</em></span> @@ -863,7 +863,7 @@ there can be multiple back-ends for this including: <span class="emphasis"><em>tdbsam</em></span> - a binary database backend that will be stored in the <span class="emphasis"><em>private</em></span> directory in a file called <span class="emphasis"><em>passdb.tdb</em></span>. The key benefit of this binary format - file is that it can store binary objects that can not be accomodated + file is that it can store binary objects that can not be accommodated in the traditional plain text smbpasswd file. These permit the extended account controls that MS Windows NT4 and later also have. </p></li><li><p> @@ -889,11 +889,11 @@ per user settings for many parameters, over-riding global settings given in the Thus, with samba-3 it is possible to have a default system configuration for profiles, and on a per user basis to over-ride this for those users who should not be subject to the default configuration. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872678"></a>Basics of Domain Control</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2874793"></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="id2872693"></a>Domain Controller Types</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874809"></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 and Windows 200x Domain Control architecture, but not in the manner that so many expect. There is folk lore that dictates that because of it's role in the MS Windows @@ -908,7 +908,7 @@ part in NT4 type domain user authentication and in synchronisation of the domain database with Backup Domain Controllers. </p><p> With MS Windows 200x Server based Active Directory domains, one domain controller seeds a potential -hierachy of domain controllers, each with their own area of delegated control. The master domain +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. @@ -925,10 +925,10 @@ On a network segment that has a BDC and a PDC the BDC will be most likely to ser 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 PDB and BDC must be manually configured and changes need to be made likewise. +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 vica versa only, but the only way +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> @@ -945,7 +945,7 @@ At this time any appearance that Samba-3 is capable of acting as an 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. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872892"></a>Preparing for Domain Control</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875020"></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, @@ -977,7 +977,7 @@ NT4 / 200x / XP clients. <a href="#integrate-ms-networks" title="Chapter 26. Integrating MS Windows networks with Samba">MS Windows network Integration</a>)</td></tr><tr><td>Domain logons for Windows NT4 / 200x / XP Professional clients</td></tr><tr><td>Configuration of Roaming Profiles or explicit configuration to force local profile usage</td></tr><tr><td>Configuration of Network/System Policies</td></tr><tr><td>Adding and managing domain user accounts</td></tr><tr><td>Configuring MS Windows client machines to become domain members</td></tr></table><p> The following provisions are required to serve MS Windows 9x / Me Clients: </p><table class="simplelist" border="0" summary="Simple list"><tr><td>Configuration of basic TCP/IP and MS Windows Networking</td></tr><tr><td>Correct designation of the Server Role (<i class="parameter"><tt>security = user</tt></i>)</td></tr><tr><td>Network Logon Configuration (Since Windows 9x / XP Home are not technically domain - members, they do not really particpate in the security aspects of Domain logons as such)</td></tr><tr><td>Roaming Profile Configuration</td></tr><tr><td>Configuration of System Policy handling</td></tr><tr><td>Installation of the Network driver "Client for MS Windows Networks" and configuration + members, they do not really participate in the security aspects of Domain logons as such)</td></tr><tr><td>Roaming Profile Configuration</td></tr><tr><td>Configuration of System Policy handling</td></tr><tr><td>Installation of the Network driver "Client for MS Windows Networks" and configuration to log onto the domain</td></tr><tr><td>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.</td></tr><tr><td>Adding and managing domain user accounts</td></tr></table><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 @@ -1006,7 +1006,7 @@ domain/workgroup. Local master browsers in the same domain/workgroup on broadcas 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="id2873207"></a>Domain Control - Example Configuration</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875340"></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>. Here we attempt to explain the parameters that are covered in the <tt class="filename">smb.conf</tt> man page. @@ -1060,20 +1060,20 @@ Here is an example <tt class="filename">smb.conf</tt> for acting as a PDC: <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = no <a href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> = 0600 <a href="smb.conf.5.html#DIRECTORYMASK" target="_top">directory mask</a> = 0700 -</pre><div xmlns:ns5="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><ns5:p> +</pre><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 parameters are the essentials alone: -</ns5:p><pre class="programlisting"> +</p><pre class="programlisting"> workgroup = NARNIA domain logons = Yes domain master = Yes security = User -</pre><ns5:p> +</pre><p> The additional parameters shown in the longer listing above just makes for a more complete environment. -</ns5:p></div><p> +</p></div><p> There are a couple of points to emphasize in the above configuration. </p><div class="itemizedlist"><ul type="disc"><li><p> Encrypted passwords must be enabled. For more details on how @@ -1086,23 +1086,23 @@ There are a couple of points to emphasize in the above configuration. client to locate the server as a DC. Please refer to the various Network Browsing documentation included with this distribution for details. - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873503"></a>Samba ADS Domain Control</h2></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875639"></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 is have been partially implemented on an experimental only basis. Please do NOT expect Samba-3 to support these protocols - nor should you depend on any such functionality either now or in the future. The Samba-Team may well remove such -experiemental features or may change their behaviour. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2873526"></a>Domain and Network Logon Configuration</h2></div></div><div></div></div><p> +experimental features or may change their behaviour. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875661"></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 rightly 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="id2873540"></a>Domain Network Logon Service</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875676"></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 <i class="parameter"><tt>domain master = Yes</tt></i> (the Primary Domain Controller); on ALL Backup Domain Controllers <i class="parameter"><tt>domain master = No</tt></i> must be set. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873573"></a>Example Configuration</h4></div></div><div></div></div><pre class="programlisting"> - [globals] +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875709"></a>Example Configuration</h4></div></div><div></div></div><pre class="programlisting"> + [global] domain logons = Yes domain master = (Yes on PDC, No on BDCs) @@ -1111,7 +1111,7 @@ must be set. path = /var/lib/samba/netlogon guest ok = Yes browseable = No -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873592"></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> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875729"></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. @@ -1123,7 +1123,7 @@ 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. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873628"></a>The Special Case of Windows 9x / Me</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875765"></a>The Special Case of Windows 9x / Me</h4></div></div><div></div></div><p> A domain and a workgroup are exactly the same thing in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a @@ -1203,7 +1203,7 @@ The main difference between a PDC and a Windows 9x logon server configuration is </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></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876260"></a>Security Mode and Master Browsers</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876003"></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 @@ -1237,7 +1237,7 @@ 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 <i class="parameter"><tt>security = user</tt></i>. 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="id2876365"></a>Common Problems and Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876372"></a>I cannot include a '$' in a machine name</h3></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876111"></a>Common Problems and Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876118"></a>I cannot include a '$' in a 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. @@ -1245,7 +1245,7 @@ systems?) won't create a user with a '$' in their name. 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><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876411"></a>I get told "You already have a connection to the Domain...." +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876157"></a>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.</h3></div></div><div></div></div><p> This happens if you try to create a machine trust account from the @@ -1259,7 +1259,7 @@ Further, if the machine is already a 'member of a workgroup' that is the same name as the domain you are joining (bad idea) you will get this message. Change the workgroup name to something else, it does not matter what, reboot, and try again. -</p></div><div xmlns:ns6="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876460"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>I joined the domain successfully but after upgrading +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876206"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>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. @@ -1270,14 +1270,14 @@ 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><ns6:p> +</p><p> The reset or change the domain SID you can use the net command as follows: -</ns6:p><pre class="screen"> +</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><ns6:p> -</ns6:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876531"></a>The machine trust account for this computer either does not +</pre><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876277"></a>The machine trust account for this computer either does not exist or is not accessible.</h3></div></div><div></div></div><p> 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 @@ -1290,7 +1290,7 @@ admin user system is working. </p><p> Alternatively if you are creating account entries manually then they have not been created correctly. Make sure that you have the entry -correct for the machine trust account in smbpasswd file on the Samba PDC. +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 @@ -1300,20 +1300,20 @@ 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="id2876588"></a>When I attempt to login to a Samba Domain from a NT4/W2K workstation, +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876340"></a>When I attempt to login to a Samba Domain from a NT4/W2K workstation, I get a message about my account being disabled.</h3></div></div><div></div></div><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="id2876615"></a>Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876367"></a>Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</h3></div></div><div></div></div><p> A domain controller has to announce on the network who it is. This usually takes a while. - </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter 6. Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2878646">Features And Benefits</a></dt><dt><a href="#id2878811">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878839">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2876805">Active Directory Domain Control</a></dt><dt><a href="#id2876826">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2876850">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2876875">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2876945">Example Configuration</a></dt></dl></dd><dt><a href="#id2876995">Common Errors</a></dt><dd><dl><dt><a href="#id2877009">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2877034">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2877067">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2877096">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="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="#id2878532">Features And Benefits</a></dt><dt><a href="#id2878705">Essential Background Information</a></dt><dd><dl><dt><a href="#id2878734">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2878954">Active Directory Domain Control</a></dt><dt><a href="#id2878975">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2879001">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2879047">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2879149">Example Configuration</a></dt></dl></dd><dt><a href="#id2879210">Common Errors</a></dt><dd><dl><dt><a href="#id2879224">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2879254">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2879287">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2879332">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 the -<a href="Samba-PDC-HOWTO.html" target="_top">Domain Control Chapter</a>. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878646"></a>Features And Benefits</h2></div></div><div></div></div><p> -This is one of the most difficult chapters to summarise. It matters not what we say here +<a href="#samba-pdc" title="Chapter 5. Domain Control">Domain Control</a> chapter. +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878532"></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 for more +that are either not yet capable of being delivered, or that can be achieved far more effectively using a totally different approach. Since this HOWTO is already so large and extensive, we have taken the decision to provide sufficient (but not comprehensive) information regarding Backup Domain Control. In the event that you should have a persistent @@ -1334,7 +1334,7 @@ The use of a non-LDAP backend SAM database is particularly problematic because D 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 PDC instance of the Domain member trust account password will not reach the +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. @@ -1349,7 +1349,7 @@ lets consider each possible option and look at the pro's and con's for each theo </p><p> Arguments Against: Complexity </p></li><li><p> - Passdb Backend is tdbsam based, BDCs use cron based "net rcp vampire" to + Passdb Backend is tdbsam based, BDCs use cron based "net rpc vampire" to suck down the Accounts database from the PDC </p><p> Arguments For: It would be a nice solution @@ -1371,22 +1371,22 @@ lets consider each possible option and look at the pro's and con's for each theo Arguments Against: All machine trust accounts and user accounts will be locally maintained. Domain users will NOT be able to roam from office to office. This is a broken and flawed solution. Do NOT do this. - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878811"></a>Essential Background Information</h2></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878705"></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 +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="id2878839"></a>MS Windows NT4 Style Domain Control</h3></div></div><div></div></div><p> -Whenever a user logs into a Windows NT4 / 200x / XP Profresional Workstation, +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878734"></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 Accounts Manager database) then a set of error +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 @@ -1408,7 +1408,7 @@ 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 + 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> @@ -1424,7 +1424,7 @@ has the PDC, the change will likely be made directly to the PDC instance of the 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 +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> @@ -1439,7 +1439,7 @@ one of the BDCs can be promoted to a PDC. If this happens while the original PDC line then it is automatically demoted to a BDC. This is an important aspect of Domain Controller management. The tool that is used to affect a promotion or a demotion is the Server Manager for Domains. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2876742"></a>Example PDC Configuration</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2878883"></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: @@ -1450,29 +1450,29 @@ parameters in the <i class="parameter"><tt>[global]</tt></i>-section of the <tt </pre><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 the chapter on Domain Control. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876805"></a>Active Directory Domain Control</h3></div></div><div></div></div><p> +chapter, for more information please refer to the chapter on <a href="#samba-pdc" title="Chapter 5. Domain Control">Domain Control</a>. +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878954"></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 Contoller to an Active Directory Domain Controller. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876826"></a>What qualifies a Domain Controller on the network?</h3></div></div><div></div></div><p> +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="id2878975"></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="id2876850"></a>How does a Workstation find its domain controller?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879001"></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 valdation. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876875"></a>Backup Domain Controller Configuration</h2></div></div><div></div></div><p> +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="id2879047"></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 @@ -1483,25 +1483,31 @@ Several things have to be done: generate a new SID for itself and override the domain SID with this new BDC SID.</p><p> To retrieve the domain SID from the PDC or an existing BDC and store it in the - secrets.tdb, execute 'net rpc getsid' on the BDC. - </p></li><li><p> + 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. + 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 in the file private/smbpasswd has to be - replicated from the PDC to the BDC. This is a bit tricky, see the - next section. + 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="id2876945"></a>Example Configuration</h3></div></div><div></div></div><p> + </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879149"></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><pre class="programlisting"> workgroup = SAMBA @@ -1514,18 +1520,21 @@ problem as the name SAMBA<#1c> is a NetBIOS group name that is meant to be registered by more than one machine. The parameter 'domain master = no' forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS name is reserved for the Primary Domain Controller. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876995"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879210"></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="id2877009"></a>Machine Accounts keep expiring, what can I do?</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879224"></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 procede and the account expiry error will be reported. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877034"></a>Can Samba be a Backup Domain Controller to an NT4 PDC?</h3></div></div><div></div></div><p> +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="id2879254"></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 version 2.2. @@ -1536,7 +1545,7 @@ mechanism has progressed, and some form of NT4 BDC support is expected soon. Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to 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="id2877067"></a>How do I replicate the smbpasswd file?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879287"></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. @@ -1544,14 +1553,18 @@ has to be replicated to the BDC. So replicating the smbpasswd file very often is As the smbpasswd file contains plain text password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. -Ssh itself can be set up to accept *only* rsync transfer without requiring the user +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></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877096"></a>Can I do this all with LDAP?</h3></div></div><div></div></div><p> +</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="id2879332"></a>Can I do this all with LDAP?</h3></div></div><div></div></div><p> The simple answer is YES. Samba's pdb_ldap code supports binding to a replica LDAP server, and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read only, so this will not occur often). -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 7. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2877621">Features and Benefits</a></dt><dt><a href="#id2877192">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2877352">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879134">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2879331">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2879386">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#id2879531">Domain Member Server</a></dt><dd><dl><dt><a href="#id2879579">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2882177">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2882315">Setup your smb.conf</a></dt><dt><a href="#id2882398">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882740">Notes</a></dt></dl></dd><dt><a href="#id2882762">Common Errors</a></dt><dd><dl><dt><a href="#id2882784">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882816">Adding Machine to Domain Fails</a></dt></dl></dd></dl></div><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 7. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2880401">Features and Benefits</a></dt><dt><a href="#id2880516">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2880692">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2880944">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2881141">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2881203">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2881406">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2881788">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2881929">Setup your smb.conf</a></dt><dt><a href="#id2882013">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2882376">Notes</a></dt></dl></dd><dt><a href="#id2882398">Common Errors</a></dt><dd><dl><dt><a href="#id2882423">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2882455">Adding Machine to Domain Fails</a></dt></dl></dd></dl></div><p> Domain Membership is a subject of vital concern, Samba must be able to participate as a member server in a Microsoft Domain security context, and Samba must be capable of providing Domain machine member trust accounts, @@ -1564,7 +1577,7 @@ within the current MS Windows networking world and particularly in the Unix/Linux networking and administration world, a considerable level of mis-information, incorrect understanding, and a lack of knowledge. Hopefully this chapter will fill the voids. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877621"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880401"></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 @@ -1582,7 +1595,7 @@ Domain membership has many advantages: 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 Accounts Management) database + 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> @@ -1593,7 +1606,7 @@ Domain membership has many advantages: 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 + 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 @@ -1601,7 +1614,7 @@ Domain membership has many advantages: client or server, other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an LDAP directory, or via an Active Directory infrastructure) - </p></li></ul></div></div><div xmlns:ns7="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877192"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880516"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div><div></div></div><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, @@ -1620,11 +1633,11 @@ shared secret with the domain controller. 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><ns7:p> +</p><p> A Samba PDC, however, stores each machine trust account in two parts, as follows: -</ns7:p><div class="itemizedlist"><ul type="disc"><li><p> +</p><div class="itemizedlist"><ul type="disc"><li><p> A Domain Security Account (stored in the <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 @@ -1644,8 +1657,8 @@ as follows: <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><ns7:p> -</ns7:p><p> + </p></li></ul></div><p> +</p><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 @@ -1660,7 +1673,7 @@ There are three ways to create machine trust accounts: created by Samba at the time the client is joined to the domain. (For security, this is the recommended method.) The corresponding Unix account may be created automatically or manually. - </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877352"></a>Manual Creation of Machine Trust Accounts</h3></div></div><div></div></div><p> + </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880692"></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 @@ -1692,11 +1705,11 @@ Now that the corresponding Unix account has been created, the next step is to cr the Samba account for the client containing the well-known initial machine trust account password. This can be done using the <a href="smbpasswd.8.html" target="_top"><b class="command">smbpasswd(8)</b></a> command as shown here: -</p><ns7:p> -</ns7:p><pre class="screen"> +</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><ns7:p>> -</ns7:p><p> +</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. @@ -1709,7 +1722,7 @@ the corresponding Unix account. 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="id2879134"></a>Using NT4 Server Manager to Add Machine Accounts to the Domain</h3></div></div><div></div></div><p> + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880944"></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</span> then the tool of choice is the package called <b class="command">SRVTOOLS.EXE</b>. @@ -1740,7 +1753,7 @@ Launch the <b class="command">srvmgr.exe</b> (Server Manager for Domains) and fo <span class="guilabel">Add NT Workstation of Server</span>, then enter the machine name in the field provided, then click the <span class="guibutton">Add</span> button. - </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879331"></a>"On-the-Fly" Creation of Machine Trust Accounts</h3></div></div><div></div></div><p> + </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881141"></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. @@ -1755,10 +1768,10 @@ Below is an example for a RedHat Linux system. [global] # <...remainder of parameters...> add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879386"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881203"></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="id2879399"></a>Windows 200x XP Professional</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881216"></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 @@ -1778,7 +1791,7 @@ with the version of Windows: 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="id2879467"></a>Windows NT4</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881283"></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>. @@ -1791,10 +1804,10 @@ with the version of Windows: Domain</span>. In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when prompted). - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2879508"></a>Samba</h4></div></div><div></div></div><p>Joining a samba client to a domain is documented in - the <a href="#domain-member" title="Chapter 7. Domain Membership">Domain Member</a> chapter. - </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879531"></a>Domain Member Server</h2></div></div><div></div></div><p> -This mode of server operation involves the samba machine being made a member + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881324"></a>Samba</h4></div></div><div></div></div><p>Joining a Samba client to a domain is documented in + the <a href="#domain-member-server" title="Domain Member Server">Domain Member Server</a> section of this chapter chapter. + </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) @@ -1811,30 +1824,30 @@ Server, etc. Please refer to the <a href="#samba-pdc" title="Chapter 5. Domain Control">Domain Control chapter</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 +regarding how to enable the Samba domain member machine to join the domain and to be fully trusted by it. -</p><div xmlns:ns8="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879579"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><ns8:p> - </ns8:p><div class="table"><a name="id2879589"></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">DOM</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><ns8:p> -</ns8:p><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881406"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><p> + </p><div class="table"><a name="id2881417"></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">DOM</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 href="smb.conf.5.html#SECURITY" target="_top"> <i class="parameter"><tt>security</tt></i></a> line in the [global] section of your <tt class="filename">smb.conf</tt> to read: -</p><ns8:p> -</ns8:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> security = domain -</pre><ns8:p> -</ns8:p><p> +</pre><p> +</p><p> Next change the <a href="smb.conf.5.html#WORKGROUP" target="_top"><i class="parameter"><tt> workgroup</tt></i></a> line in the <i class="parameter"><tt>[global]</tt></i> section to read: -</p><ns8:p> -</ns8:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> workgroup = DOM -</pre><ns8:p> -</ns8:p><p> +</pre><p> +</p><p> as this is the name of the domain we are joining. </p><p> You must also have the parameter <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top"> @@ -1844,11 +1857,11 @@ You must also have the parameter <a href="smb.conf.5.html#ENCRYPTPASSWORDS" targ Finally, add (or modify) a <a href="smb.conf.5.html#PASSWORDSERVER" target="_top"> <i class="parameter"><tt>password server</tt></i></a> line in the [global] section to read: -</p><ns8:p> -</ns8:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> password server = DOMPDC DOMBDC1 DOMBDC2 -</pre><ns8:p> -</ns8:p><p> +</pre><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 @@ -1858,27 +1871,28 @@ among domain controllers. Alternatively, if you want smbd to automatically determine the list of Domain controllers to use for authentication, you may set this line to be: -</p><ns8:p> -</ns8:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> password server = * -</pre><ns8:p> -</ns8:p><p> -This method, allows Samba to use exactly the same mechanism that NT does. This +</pre><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><ns8:p> -</ns8:p><pre class="screen"> +</p><p> +</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net join -S DOMPDC -U<i class="replaceable"><tt>Administrator%password</tt></i></tt></b> -</pre><ns8:p> -</ns8:p><p> +</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. The <i class="replaceable"><tt>Administrator%password</tt></i> is +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: @@ -1895,7 +1909,7 @@ trust account on the PDC beforehand. This command goes through the machine account password change protocol, then writes the new (random) machine account password for this Samba server into a file in the same directory -in which an smbpasswd file would be stored - normally : +in which an smbpasswd file would be stored - normally: </p><p> <tt class="filename">/usr/local/samba/private/secrets.tdb</tt> </p><p> @@ -1906,7 +1920,7 @@ as a shadow password file. </p><p> Finally, restart your Samba daemons and get ready for clients to begin using domain security! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882177"></a>Why is this better than security = server?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881788"></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 @@ -1917,8 +1931,8 @@ filesystem. This is very similar to the older Samba security mode 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 the <a href="winbind.html" target="_top">Winbind -paper</a> for information on a system to automatically +Please refer to the <a href="#winbind" title="Chapter 21. Integrated Logon Support using Winbind">Winbind</a> chapter +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 @@ -1948,27 +1962,27 @@ 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><p> -This is a rough guide to setting up Samba 3.0 with kerberos authentication against a -Windows2000 KDC. -</p><div xmlns:ns9="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882315"></a>Setup your <tt class="filename">smb.conf</tt></h3></div></div><div></div></div><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="id2881929"></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><pre class="programlisting"> realm = your.kerberos.REALM security = ADS encrypt passwords = yes -</pre><ns9:p> +</pre><p> In case samba can't figure out your ads server using your realm name, use the <i class="parameter"><tt>ads server</tt></i> option in <tt class="filename">smb.conf</tt>: -</ns9:p><pre class="programlisting"> +</p><pre class="programlisting"> ads server = your.kerberos.server -</pre><ns9:p> -</ns9:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</pre><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 <i class="parameter"><tt>security = domain</tt></i>, 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="id2882398"></a>Setup your <tt class="filename">/etc/krb5.conf</tt></h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882013"></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"> [realms] @@ -1981,7 +1995,7 @@ Test your config by doing a <b class="userinput"><tt>kinit 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 +requested realm while getting initial credentials</span> error. </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> @@ -1989,70 +2003,70 @@ 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 +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 +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 +If all you want is Kerberos support in <span class="application">smbclient</span> then you can skip straight to <a href="#ads-test-smbclient" title="Testing with smbclient">Test with <span class="application">smbclient</span></a> now. <a href="#ads-create-machine-account" title="Create the computer account">Creating a computer account</a> and <a href="#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 xmlns:ns10="" 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><ns10:p> +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: -</ns10:p><pre class="programlisting"> - <b class="userinput"><tt>net join -U Administrator%password</tt></b> -</pre><ns10:p> -</ns10:p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882589"></a>Possible errors</h4></div></div><div></div></div><ns10:p> -</ns10: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><pre class="programlisting"> + <tt class="prompt">root# </tt><b class="userinput"><tt>net join -U Administrator%password</tt></b> +</pre><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882222"></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 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><ns10:p> -</ns10: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> + 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 +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><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 <i class="parameter"><tt>-k</tt></i> option to choose kerberos authentication. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882740"></a>Notes</h3></div></div><div></div></div><p> +server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but +specify the <i class="parameter"><tt>-k</tt></i> option to choose Kerberos authentication. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882376"></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 fixed in service packs? -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882762"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882398"></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 "little" things that can go wrong. +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. easily overcome. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882784"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882423"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p> <span class="emphasis"><em>Problem:</em></span> 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 doen't. Why is this failing? +exists on the network - I know it doesn't. Why is this failing? </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="id2882816"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882455"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p> 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? @@ -2077,12 +2091,12 @@ Possible causes include: then make sure that the machine name you are trying to add can be added using this tool. <b class="command">Useradd</b> on some systems will not allow any upper case characters nor will it allow spaces in the name. - </p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter 8. Stand-Alone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2884259">Features and Benefits</a></dt><dt><a href="#id2884297">Background</a></dt><dt><a href="#id2884365">Example Configuration</a></dt><dd><dl><dt><a href="#id2882967">Reference Documentation Server</a></dt><dt><a href="#id2883015">Central Print Serving</a></dt></dl></dd><dt><a href="#id2883221">Common Errors</a></dt></dl></div><p> -Stand-Alone servers are independant of Domain Controllers on the network. + </p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter 8. Stand-Alone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2884809">Features and Benefits</a></dt><dt><a href="#id2885005">Background</a></dt><dt><a href="#id2885077">Example Configuration</a></dt><dd><dl><dt><a href="#id2885092">Reference Documentation Server</a></dt><dt><a href="#id2885142">Central Print Serving</a></dt></dl></dd><dt><a href="#id2885356">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 readilly accessible to all users. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884259"></a>Features and Benefits</h2></div></div><div></div></div><p> +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="id2884809"></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. @@ -2099,7 +2113,7 @@ that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to affect any access controls and no files will be served from the print server. Again a share mode stand-alone server makes a great solution. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884297"></a>Background</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885005"></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 @@ -2109,30 +2123,30 @@ 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 log onto it. Whatever logon facility -the workstations are subject to is independant of this machine. It is however -necessary to accomodate any network user so that the logon name they use will +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 cane be done. +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. +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) 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 +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="id2884365"></a>Example Configuration</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885077"></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="id2882967"></a>Reference Documentation Server</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885092"></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 @@ -2155,18 +2169,18 @@ Unix system database. This is a very simple system to administer. 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 -unprivilidged account names to be used. Given that there is a WINS server on this network +unprivileged account names to be used. Given that there is a WINS server on this network we do use it. -</p></div><div xmlns:ns13="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883015"></a>Central Print Serving</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885142"></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 the chapter on printing for more information). + (Please refer to the <a href="#CUPS-printing" title="Chapter 19. CUPS Printing Support in Samba 3.0">CUPS Printing</a> chapter for more information). </p></li><li><p> - All printers will that the print server will service will be network + 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> @@ -2175,29 +2189,29 @@ on your system. </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>Enablement for Anonymous Printing</b></p><ul type="disc"><li xmlns:ns11=""><ns11:p> +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: - </ns11:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>testparm -s -v | grep "guest account"</tt></b> - </pre><ns11:p> + </pre><p> Then make sure that this account exists in your system password database (<tt class="filename">/etc/passwd</tt>). - </ns11:p></li><li xmlns:ns12=""><ns12:p> + </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: - </ns12:p><pre class="screen"> + </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><ns12:p> - </ns12:p></li></ul></div><ns13:p> -</ns13:p><pre class="programlisting"> + </pre><p> + </p></li></ul></div><p> +</p><pre class="programlisting"> # Global parameters [global] workgroup = MYGROUP @@ -2215,42 +2229,42 @@ the anonymous (guest) user two things will be required: printing = cups use client driver = Yes browseable = No -</pre><ns13:p> -</ns13:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883221"></a>Common Errors</h2></div></div><div></div></div><p> +</pre><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885356"></a>Common Errors</h2></div></div><div></div></div><p> The greatest mistake so often made is to make a network configuration too complex. It pays to use the simplest solution that will meet the needs of the moment. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter 9. MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2883589">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883589"></a>Note</h2></div></div><div></div></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter 9. MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2884469">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2884469"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. -</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2883617"></a>Valuable Nuts and Bolts Information</h1></div></div><div></div></div><p> +</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2884234"></a>Valuable Nuts and Bolts Information</h1></div></div><div></div></div><p> Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. -</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2883706">Features and Benefits</a></dt><dt><a href="#id2883784">What is Browsing?</a></dt><dt><a href="#id2883967">Discussion</a></dt><dd><dl><dt><a href="#id2883983">NetBIOS over TCP/IP</a></dt><dt><a href="#id2883290">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2883418">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2883554">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2884860">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2885066">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2885332">Making samba the domain master</a></dt><dt><a href="#id2888727">Note about broadcast addresses</a></dt><dt><a href="#id2888744">Multiple interfaces</a></dt><dt><a href="#id2888773">Use of the Remote Announce parameter</a></dt><dt><a href="#id2888877">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2888938">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2889089">Setting up a WINS server</a></dt><dt><a href="#id2889284">WINS Replication</a></dt><dt><a href="#id2889309">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2889340">Helpful Hints</a></dt><dd><dl><dt><a href="#id2889353">Windows Networking Protocols</a></dt><dt><a href="#id2889420">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2889541">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2889588">Browsing support in samba</a></dt><dt><a href="#id2889695">Problem resolution</a></dt><dt><a href="#id2889774">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2890391">Common Errors</a></dt><dd><dl><dt><a href="#id2890406">How can one flush the Samba NetBIOS name cache without restarting samba?</a></dt><dt><a href="#id2890435">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2890530">Features and Benefits</a></dt><dt><a href="#id2890854">Technical Information</a></dt><dd><dl><dt><a href="#id2890917">Important Notes About Security</a></dt><dt><a href="#id2891160">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2891216">Account Management Tools</a></dt><dd><dl><dt><a href="#id2891247">The smbpasswd Command</a></dt><dt><a href="#id2891513">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2891647">Password Backends</a></dt><dd><dl><dt><a href="#id2895859">Plain Text</a></dt><dt><a href="#id2895899">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2896006">tdbsam</a></dt><dt><a href="#id2896034">ldapsam</a></dt><dt><a href="#id2897524">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2898328">Common Errors</a></dt><dd><dl><dt><a href="#id2898335">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2898350">Users are being added to the wrong backend database</a></dt><dt><a href="#id2898409">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and Unix Groups</a></dt><dd><dl><dt><a href="#id2898582">Features and Benefits</a></dt><dt><a href="#id2898682">Discussion</a></dt><dd><dl><dt><a href="#id2898871">Example Configuration</a></dt></dl></dd><dt><a href="#id2898936">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2898950">Sample smb.conf add group script</a></dt><dt><a href="#id2899017">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2899091">Common Errors</a></dt><dd><dl><dt><a href="#id2899107">Adding Groups Fails</a></dt><dt><a href="#id2899167">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2902353">Features and Benefits</a></dt><dt><a href="#id2902478">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902496">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2899413">Managing Directories</a></dt><dt><a href="#id2899508">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2899915">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2899943">User and Group Based Controls</a></dt><dt><a href="#id2900215">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2900461">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905044">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905115">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905414">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905422">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905460">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905539">Viewing file ownership</a></dt><dt><a href="#id2905661">Viewing File or Directory Permissions</a></dt><dt><a href="#id2905889">Modifying file or directory permissions</a></dt><dt><a href="#id2906041">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2906370">Interaction with the standard Samba file attribute - mapping</a></dt></dl></dd><dt><a href="#id2906446">Common Errors</a></dt><dd><dl><dt><a href="#id2906460">Users can not write to a public share</a></dt><dt><a href="#id2906838">I have set force user and samba still makes root the owner of all the files - I touch!</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2908960">Features and Benefits</a></dt><dt><a href="#id2909016">Discussion</a></dt><dd><dl><dt><a href="#id2906890">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2907521">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2907630">Example Configuration</a></dt></dl></dd><dt><a href="#id2907890">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2910326">Workstation Service Entries</a></dt><dt><a href="#id2910353">Server Service Entries</a></dt></dl></dd><dt><a href="#id2910432">Persistent Data Corruption</a></dt><dt><a href="#id2910463">Common Errors</a></dt><dd><dl><dt><a href="#id2910536">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2910566">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2911991">Introduction</a></dt><dt><a href="#id2912024">Features and Benefits</a></dt><dt><a href="#id2910684">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2910702">Using host based protection</a></dt><dt><a href="#id2910771">User based protection</a></dt><dt><a href="#id2910822">Using interface protection</a></dt><dt><a href="#id2910872">Using a firewall</a></dt><dt><a href="#id2910929">Using a IPC$ share deny</a></dt><dt><a href="#id2910994">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2911033">Upgrading Samba</a></dt><dt><a href="#id2911056">Common Errors</a></dt><dd><dl><dt><a href="#id2911075">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2911100">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2911618">Features and Benefits</a></dt><dt><a href="#id2911646">Trust Relationship Background</a></dt><dt><a href="#id2911730">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2911742">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2913717">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2913754">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2913781">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2913908">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2911286">Common Errors</a></dt><dd><dl><dt><a href="#id2911301">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2911399">Features and Benefits</a></dt><dt><a href="#id2912809">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2914332">Features and Benefits</a></dt><dt><a href="#id2914396">Technical Introduction</a></dt><dd><dl><dt><a href="#id2914432">What happens if you send a Job from a Client</a></dt><dt><a href="#id2914502">Printing Related Configuration Parameters</a></dt><dt><a href="#id2917610">Parameters Recommended for Use</a></dt><dt><a href="#id2912970">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2913079">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2913172">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2915178">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2915261">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2915568">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2915660">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2915673">The [global] Section</a></dt><dt><a href="#id2925133">The [printers] Section</a></dt><dt><a href="#id2925462">Any [my_printer_name] Section</a></dt><dt><a href="#id2925683">Print Commands</a></dt><dt><a href="#id2925734">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2926260">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2926537">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2926691">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2926842">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2926955">Creating the [print$] Share</a></dt><dt><a href="#id2927026">Parameters in the [print$] Section</a></dt><dt><a href="#id2927247">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2927408">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2927502">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2927686">Setting Drivers for existing Printers with -rpcclient</a></dt></dl></dd><dt><a href="#id2929284">"The Proof of the Pudding lies in the Eating" (Client Driver Insta -Procedure)</a></dt><dd><dl><dt><a href="#id2929305">The first Client Driver Installation</a></dt><dt><a href="#id2929502">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2929792">Further Client Driver Install Procedures</a></dt><dt><a href="#id2929887">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2930029">Other Gotchas</a></dt><dd><dl><dt><a href="#id2930062">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2930496">Supporting large Numbers of Printers</a></dt><dt><a href="#id2930798">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2931042">Weird Error Message Cannot connect under a -different Name</a></dt><dt><a href="#id2931140">Be careful when assembling Driver Files</a></dt><dt><a href="#id2931411">Samba and Printer Ports</a></dt><dt><a href="#id2931481">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2931504">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2931549">What is Imprints?</a></dt><dt><a href="#id2931590">Creating Printer Driver Packages</a></dt><dt><a href="#id2931609">The Imprints Server</a></dt><dt><a href="#id2931634">The Installation Client</a></dt></dl></dd><dt><a href="#id2931786">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2932115">The addprinter command</a></dt><dt><a href="#id2932160">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2932329">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2932343">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2932356">I give my root password but I don't get access</a></dt><dt><a href="#id2932390">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2939414">Introduction</a></dt><dd><dl><dt><a href="#id2939421">Features and Benefits</a></dt><dt><a href="#id2939469">Overview</a></dt></dl></dd><dt><a href="#id2939521">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2939600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2932509">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2932572">More complex smb.conf Settings for -CUPS</a></dt></dl></dd><dt><a href="#id2932671">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2932692">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2932719">CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2932755">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2932814">Explicitly enable "raw" printing for -application/octet-stream!</a></dt><dt><a href="#id2932975">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2933068">Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2933143">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2933188">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2933286">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2933358">PostScript and Ghostscript</a></dt><dt><a href="#id2933454">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2933550">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2946373">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2946462">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2946485">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2946623">MIME types and CUPS Filters</a></dt><dt><a href="#id2946811">MIME type Conversion Rules</a></dt><dt><a href="#id2946927">Filter Requirements</a></dt><dt><a href="#id2947096">Prefilters</a></dt><dt><a href="#id2947181">pstops</a></dt><dt><a href="#id2947284">pstoraster</a></dt><dt><a href="#id2947440">imagetops and imagetoraster</a></dt><dt><a href="#id2947495">rasterto [printerspecific]</a></dt><dt><a href="#id2947580">CUPS Backends</a></dt><dt><a href="#id2947894">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2947997">The Complete Picture</a></dt><dt><a href="#id2948012">mime.convs</a></dt><dt><a href="#id2948065">"Raw" printing</a></dt><dt><a href="#id2948120">"application/octet-stream" printing</a></dt><dt><a href="#id2948335">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2948562">Difference between cupsomatic/foomatic-rip and -native CUPS printing</a></dt><dt><a href="#id2948719">Examples for filtering Chains</a></dt><dt><a href="#id2948948">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2949073">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2949135">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2949151">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2949190">Driver Execution on the Client</a></dt><dt><a href="#id2949249">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2949312">Network Printing (Windows clients -- UNIX/Samba Print -Servers)</a></dt><dd><dl><dt><a href="#id2949333">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2949493">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2949571">Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2949626">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2949667">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2949732">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2949750">Printer Drivers running in "Kernel Mode" cause many -Problems</a></dt><dt><a href="#id2949784">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2949805">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2949832">PostScript Drivers with no major problems -- even in Kernel -Mode</a></dt></dl></dd><dt><a href="#id2949866"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2949885">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2949976">Prepare your smb.conf for -cupsaddsmb</a></dt><dt><a href="#id2950023">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2950220">Recognize the different Driver Files</a></dt><dt><a href="#id2950278">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2950311">ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"</a></dt><dt><a href="#id2950361">Caveats to be considered</a></dt><dt><a href="#id2950582">What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2950763">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2950864">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2951007">Understanding cupsaddsmb</a></dt><dt><a href="#id2951101">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2951188">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2951223">cupsaddsmb Flowchart</a></dt><dt><a href="#id2951274">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2951389">Avoiding critical PostScript Driver Settings on the -Client</a></dt></dl></dd><dt><a href="#id2951523">Installing PostScript Driver Files manually (using -rpcclient)</a></dt><dd><dl><dt><a href="#id2951638">A Check of the rpcclient man Page</a></dt><dt><a href="#id2951750">Understanding the rpcclient man Page</a></dt><dt><a href="#id2951829">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2951919">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2952081">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2952701">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2952803">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2952906">Trivial DataBase Files</a></dt><dt><a href="#id2952976">Binary Format</a></dt><dt><a href="#id2953038">Losing *.tdb Files</a></dt><dt><a href="#id2953097">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2953159">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2953265">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2953893">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2954351">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2954382">Setting up Quotas</a></dt><dt><a href="#id2954413">Correct and incorrect Accounting</a></dt><dt><a href="#id2954454">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2954526">The page_log File Syntax</a></dt><dt><a href="#id2954628">Possible Shortcomings</a></dt><dt><a href="#id2954699">Future Developments</a></dt><dt><a href="#id2954747">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2954762">Additional Material</a></dt><dt><a href="#id2954956">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2955001">CUPS Configuration Settings explained</a></dt><dt><a href="#id2955083">Pre-conditions</a></dt><dt><a href="#id2955144">Manual Configuration</a></dt></dl></dd><dt><a href="#id2955162">When not to use Samba to print to -CUPS</a></dt><dt><a href="#id2955180">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2955214">Where to find Documentation</a></dt><dt><a href="#id2955227">How to ask for Help</a></dt><dt><a href="#id2955240">Where to find Help</a></dt></dl></dd><dt><a href="#id2955254">Appendix</a></dt><dd><dl><dt><a href="#id2955261">Printing from CUPS to Windows attached -Printers</a></dt><dt><a href="#id2955455">More CUPS filtering Chains</a></dt><dt><a href="#id2955709">Trouble Shooting Guidelines to fix typical Samba printing -Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2958218">Features and Benefits</a></dt><dt><a href="#id2958235">Discussion</a></dt><dt><a href="#id2958286">Included modules</a></dt><dd><dl><dt><a href="#id2956883">audit</a></dt><dt><a href="#id2956922">extd_audit</a></dt><dt><a href="#id2957044">fake_perms</a></dt><dt><a href="#id2957063">recycle</a></dt><dt><a href="#id2957202">netatalk</a></dt></dl></dd><dt><a href="#id2957247">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2957269">DatabaseFS</a></dt><dt><a href="#id2957323">vscan</a></dt></dl></dd><dt><a href="#id2957352">Common Errors</a></dt></dl></dd><dt>21. <a href="#winbind">Integrated Logon Support using Winbind</a></dt><dd><dl><dt><a href="#id2957847">Features and Benefits</a></dt><dt><a href="#id2957875">Introduction</a></dt><dt><a href="#id2959857">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2959916">Target Uses</a></dt></dl></dd><dt><a href="#id2959947">How Winbind Works</a></dt><dd><dl><dt><a href="#id2959975">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2960008">Microsoft Active Directory Services</a></dt><dt><a href="#id2960031">Name Service Switch</a></dt><dt><a href="#id2957393">Pluggable Authentication Modules</a></dt><dt><a href="#id2957465">User and Group ID Allocation</a></dt><dt><a href="#id2957499">Result Caching</a></dt></dl></dd><dt><a href="#id2957528">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2957555">Introduction</a></dt><dt><a href="#id2957630">Requirements</a></dt><dt><a href="#id2958907">Testing Things Out</a></dt></dl></dd><dt><a href="#id2963255">Conclusion</a></dt><dt><a href="#id2963274">Common Errors</a></dt></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2964647">Features and Benefits</a></dt><dt><a href="#id2964678">Remote Server Administration</a></dt><dt><a href="#id2963360">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2963377">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2963579">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2963774">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2963806">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2964204">Features and Benefits</a></dt><dt><a href="#id2964256">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2964367">Windows 9x/Me Policies</a></dt><dt><a href="#id2963915">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2964048">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2965490">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2965591">Samba Editreg Toolset</a></dt><dt><a href="#id2965611">Windows NT4/200x</a></dt><dt><a href="#id2965631">Samba PDC</a></dt></dl></dd><dt><a href="#id2965676">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2965823">Common Errors</a></dt><dd><dl><dt><a href="#id2965837">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2965940">Features and Benefits</a></dt><dt><a href="#id2965973">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2966014">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971377">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972314">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972378">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972638">Mandatory profiles</a></dt><dt><a href="#id2972696">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972742">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972762">MS Windows 9x/Me</a></dt><dt><a href="#id2972910">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973464">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2973968">Common Errors</a></dt><dd><dl><dt><a href="#id2973980">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974043">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974262">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2975719">Features and Benefits</a></dt><dt><a href="#id2974574">Technical Discussion</a></dt><dd><dl><dt><a href="#id2974590">PAM Configuration Syntax</a></dt><dt><a href="#id2975256">Example System Configurations</a></dt><dt><a href="#id2977688">smb.conf PAM Configuration</a></dt><dt><a href="#id2977745">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2977829">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2978196">Common Errors</a></dt><dd><dl><dt><a href="#id2978209">pam_winbind problem</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2979952">Features and Benefits</a></dt><dt><a href="#id2979977">Background Information</a></dt><dt><a href="#id2980022">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2980073">/etc/hosts</a></dt><dt><a href="#id2980198">/etc/resolv.conf</a></dt><dt><a href="#id2978348">/etc/host.conf</a></dt><dt><a href="#id2978390">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2978479">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2978604">The NetBIOS Name Cache</a></dt><dt><a href="#id2978648">The LMHOSTS file</a></dt><dt><a href="#id2978762">HOSTS file</a></dt><dt><a href="#id2978795">DNS Lookup</a></dt><dt><a href="#id2978820">WINS Lookup</a></dt></dl></dd><dt><a href="#id2978890">Common Errors</a></dt><dd><dl><dt><a href="#id2978906">My Boomerang Won't Come Back</a></dt><dt><a href="#id2978938">Very Slow Network Connections</a></dt><dt><a href="#id2978989">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2979144">Features and Benefits</a></dt><dt><a href="#id2979186">What are charsets and unicode?</a></dt><dt><a href="#id2979255">Samba and charsets</a></dt><dt><a href="#id2979355">Conversion from old names</a></dt><dt><a href="#id2979401">Japanese charsets</a></dt></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2981995">Note</a></dt><dt><a href="#id2982016">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2981826">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter 10. Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2883706">Features and Benefits</a></dt><dt><a href="#id2883784">What is Browsing?</a></dt><dt><a href="#id2883967">Discussion</a></dt><dd><dl><dt><a href="#id2883983">NetBIOS over TCP/IP</a></dt><dt><a href="#id2883290">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2883418">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2883554">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2884860">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2885066">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2885332">Making samba the domain master</a></dt><dt><a href="#id2888727">Note about broadcast addresses</a></dt><dt><a href="#id2888744">Multiple interfaces</a></dt><dt><a href="#id2888773">Use of the Remote Announce parameter</a></dt><dt><a href="#id2888877">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2888938">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2889089">Setting up a WINS server</a></dt><dt><a href="#id2889284">WINS Replication</a></dt><dt><a href="#id2889309">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2889340">Helpful Hints</a></dt><dd><dl><dt><a href="#id2889353">Windows Networking Protocols</a></dt><dt><a href="#id2889420">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2889541">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2889588">Browsing support in samba</a></dt><dt><a href="#id2889695">Problem resolution</a></dt><dt><a href="#id2889774">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2890391">Common Errors</a></dt><dd><dl><dt><a href="#id2890406">How can one flush the Samba NetBIOS name cache without restarting samba?</a></dt><dt><a href="#id2890435">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></div><p> +</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2886062">Features and Benefits</a></dt><dt><a href="#id2886141">What is Browsing?</a></dt><dt><a href="#id2886251">Discussion</a></dt><dd><dl><dt><a href="#id2886267">NetBIOS over TCP/IP</a></dt><dt><a href="#id2886430">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2886562">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2886698">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2886824">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2887045">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2887315">Making Samba the domain master</a></dt><dt><a href="#id2887471">Note about broadcast addresses</a></dt><dt><a href="#id2887488">Multiple interfaces</a></dt><dt><a href="#id2887517">Use of the Remote Announce parameter</a></dt><dt><a href="#id2887626">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2887687">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2887846">Setting up a WINS server</a></dt><dt><a href="#id2888045">WINS Replication</a></dt><dt><a href="#id2888070">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2888154">Helpful Hints</a></dt><dd><dl><dt><a href="#id2888167">Windows Networking Protocols</a></dt><dt><a href="#id2888234">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2888372">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2888419">Browsing support in Samba</a></dt><dt><a href="#id2888526">Problem resolution</a></dt><dt><a href="#id2888605">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2889225">Common Errors</a></dt><dd><dl><dt><a href="#id2889240">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2889269">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2892812">Features and Benefits</a></dt><dt><a href="#id2893140">Technical Information</a></dt><dd><dl><dt><a href="#id2893204">Important Notes About Security</a></dt><dt><a href="#id2893458">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2893513">Account Management Tools</a></dt><dd><dl><dt><a href="#id2893545">The smbpasswd Command</a></dt><dt><a href="#id2893811">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2893963">Password Backends</a></dt><dd><dl><dt><a href="#id2893999">Plain Text</a></dt><dt><a href="#id2894038">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2894145">tdbsam</a></dt><dt><a href="#id2894173">ldapsam</a></dt><dt><a href="#id2895689">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2896493">Common Errors</a></dt><dd><dl><dt><a href="#id2896501">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2896516">Users are being added to the wrong backend database</a></dt><dt><a href="#id2896576">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and Unix Groups</a></dt><dd><dl><dt><a href="#id2903953">Features and Benefits</a></dt><dt><a href="#id2904055">Discussion</a></dt><dd><dl><dt><a href="#id2904246">Example Configuration</a></dt></dl></dd><dt><a href="#id2904310">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2904325">Sample smb.conf add group script</a></dt><dt><a href="#id2904393">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2904485">Common Errors</a></dt><dd><dl><dt><a href="#id2904501">Adding Groups Fails</a></dt><dt><a href="#id2904562">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2902775">Features and Benefits</a></dt><dt><a href="#id2902812">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902830">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2903087">Managing Directories</a></dt><dt><a href="#id2903183">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2903398">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2904578">User and Group Based Controls</a></dt><dt><a href="#id2904850">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2905095">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905311">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905383">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905682">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905690">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905728">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905807">Viewing file ownership</a></dt><dt><a href="#id2905929">Viewing File or Directory Permissions</a></dt><dt><a href="#id2906157">Modifying file or directory permissions</a></dt><dt><a href="#id2906309">Interaction with the standard Samba create mask + parameters</a></dt><dt><a href="#id2906639">Interaction with the standard Samba file attribute + mapping</a></dt></dl></dd><dt><a href="#id2906714">Common Errors</a></dt><dd><dl><dt><a href="#id2906729">Users can not write to a public share</a></dt><dt><a href="#id2907109">I have set force user and Samba still makes root the owner of all the files + I touch!</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2910721">Features and Benefits</a></dt><dt><a href="#id2910776">Discussion</a></dt><dd><dl><dt><a href="#id2910908">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2911554">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2911664">Example Configuration</a></dt></dl></dd><dt><a href="#id2911924">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2912154">Workstation Service Entries</a></dt><dt><a href="#id2912180">Server Service Entries</a></dt></dl></dd><dt><a href="#id2912260">Persistent Data Corruption</a></dt><dt><a href="#id2912291">Common Errors</a></dt><dd><dl><dt><a href="#id2912365">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2912394">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2914448">Introduction</a></dt><dt><a href="#id2914481">Features and Benefits</a></dt><dt><a href="#id2914555">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2914574">Using host based protection</a></dt><dt><a href="#id2914645">User based protection</a></dt><dt><a href="#id2914697">Using interface protection</a></dt><dt><a href="#id2914749">Using a firewall</a></dt><dt><a href="#id2914805">Using a IPC$ share deny</a></dt><dt><a href="#id2914866">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2914907">Upgrading Samba</a></dt><dt><a href="#id2914932">Common Errors</a></dt><dd><dl><dt><a href="#id2914949">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2914974">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2915881">Features and Benefits</a></dt><dt><a href="#id2915909">Trust Relationship Background</a></dt><dt><a href="#id2915993">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2916006">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2916091">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2916127">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2916155">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2916295">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2916428">Common Errors</a></dt><dd><dl><dt><a href="#id2916443">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2915783">Features and Benefits</a></dt><dt><a href="#id2917436">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2917027">Features and Benefits</a></dt><dt><a href="#id2917095">Technical Introduction</a></dt><dd><dl><dt><a href="#id2917133">What happens if you send a Job from a Client</a></dt><dt><a href="#id2917203">Printing Related Configuration Parameters</a></dt><dt><a href="#id2918120">Parameters Recommended for Use</a></dt><dt><a href="#id2918450">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2918559">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2918652">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2918721">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2918810">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2919116">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2919220">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2919234">The [global] Section</a></dt><dt><a href="#id2919616">The [printers] Section</a></dt><dt><a href="#id2919945">Any [my_printer_name] Section</a></dt><dt><a href="#id2920166">Print Commands</a></dt><dt><a href="#id2920216">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2920741">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2921021">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2921186">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2921338">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2921450">Creating the [print$] Share</a></dt><dt><a href="#id2921521">Parameters in the [print$] Section</a></dt><dt><a href="#id2921752">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2921913">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2922008">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2922192">Setting Drivers for existing Printers with +rpcclient</a></dt></dl></dd><dt><a href="#id2923912">"The Proof of the Pudding lies in the Eating" (Client Driver Install +Procedure)</a></dt><dd><dl><dt><a href="#id2923933">The first Client Driver Installation</a></dt><dt><a href="#id2924131">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2924420">Further Client Driver Install Procedures</a></dt><dt><a href="#id2924516">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2924657">Other Gotchas</a></dt><dd><dl><dt><a href="#id2924690">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2925127">Supporting large Numbers of Printers</a></dt><dt><a href="#id2925430">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2925673">Weird Error Message Cannot connect under a +different Name</a></dt><dt><a href="#id2925771">Be careful when assembling Driver Files</a></dt><dt><a href="#id2926117">Samba and Printer Ports</a></dt><dt><a href="#id2926188">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2926210">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2926256">What is Imprints?</a></dt><dt><a href="#id2926297">Creating Printer Driver Packages</a></dt><dt><a href="#id2926316">The Imprints Server</a></dt><dt><a href="#id2926340">The Installation Client</a></dt></dl></dd><dt><a href="#id2926492">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2926822">The addprinter command</a></dt><dt><a href="#id2926867">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2927036">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2927051">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2927064">I give my root password but I don't get access</a></dt><dt><a href="#id2927097">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2936290">Introduction</a></dt><dd><dl><dt><a href="#id2936298">Features and Benefits</a></dt><dt><a href="#id2936350">Overview</a></dt></dl></dd><dt><a href="#id2936405">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2936484">Linking of smbd with libcups.so</a></dt><dt><a href="#id2936628">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2936710">More complex smb.conf Settings for +CUPS</a></dt></dl></dd><dt><a href="#id2936828">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2936848">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2936875">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2936912">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2936970">Explicitly enable "raw" printing for +application/octet-stream!</a></dt><dt><a href="#id2937131">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2937224">Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2937300">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2937344">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2937445">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2937533">PostScript and Ghostscript</a></dt><dt><a href="#id2937630">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2937742">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2937813">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2937902">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2937925">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2938065">MIME types and CUPS Filters</a></dt><dt><a href="#id2938252">MIME type Conversion Rules</a></dt><dt><a href="#id2938369">Filter Requirements</a></dt><dt><a href="#id2938539">Prefilters</a></dt><dt><a href="#id2938624">pstops</a></dt><dt><a href="#id2938727">pstoraster</a></dt><dt><a href="#id2938883">imagetops and imagetoraster</a></dt><dt><a href="#id2938940">rasterto [printers specific]</a></dt><dt><a href="#id2939024">CUPS Backends</a></dt><dt><a href="#id2939336">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2939448">The Complete Picture</a></dt><dt><a href="#id2939464">mime.convs</a></dt><dt><a href="#id2939517">"Raw" printing</a></dt><dt><a href="#id2939571">"application/octet-stream" printing</a></dt><dt><a href="#id2939786">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2940015">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a></dt><dt><a href="#id2940170">Examples for filtering Chains</a></dt><dt><a href="#id2940401">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2940530">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2940605">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2940620">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2940659">Driver Execution on the Client</a></dt><dt><a href="#id2940731">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2940794">Network Printing (Windows clients -- UNIX/Samba Print +Servers)</a></dt><dd><dl><dt><a href="#id2940814">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2940978">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2941054">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2941110">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2941150">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2941216">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2941233">Printer Drivers running in "Kernel Mode" cause many +Problems</a></dt><dt><a href="#id2941268">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2941289">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2941316">PostScript Drivers with no major problems -- even in Kernel +Mode</a></dt></dl></dd><dt><a href="#id2941369"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2941388">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2941480">Prepare your smb.conf for +cupsaddsmb</a></dt><dt><a href="#id2941526">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2941724">Recognize the different Driver Files</a></dt><dt><a href="#id2941782">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2941814">ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"</a></dt><dt><a href="#id2941864">Caveats to be considered</a></dt><dt><a href="#id2942086">What are the Benefits of using the "CUPS PostScript Driver for +Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2942268">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2942369">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2942596">Understanding cupsaddsmb</a></dt><dt><a href="#id2942690">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2942777">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2942812">cupsaddsmb Flowchart</a></dt><dt><a href="#id2942865">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2942978">Avoiding critical PostScript Driver Settings on the +Client</a></dt></dl></dd><dt><a href="#id2943112">Installing PostScript Driver Files manually (using +rpcclient)</a></dt><dd><dl><dt><a href="#id2943227">A Check of the rpcclient man Page</a></dt><dt><a href="#id2943340">Understanding the rpcclient man Page</a></dt><dt><a href="#id2943429">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2943519">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2943682">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2944334">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2944435">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2944537">Trivial DataBase Files</a></dt><dt><a href="#id2944608">Binary Format</a></dt><dt><a href="#id2944670">Losing *.tdb Files</a></dt><dt><a href="#id2944728">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2944795">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2944903">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2945532">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2945993">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2946024">Setting up Quotas</a></dt><dt><a href="#id2946056">Correct and incorrect Accounting</a></dt><dt><a href="#id2946097">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2946169">The page_log File Syntax</a></dt><dt><a href="#id2946270">Possible Shortcomings</a></dt><dt><a href="#id2946341">Future Developments</a></dt><dt><a href="#id2946390">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2946404">Additional Material</a></dt><dt><a href="#id2946598">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2946644">CUPS Configuration Settings explained</a></dt><dt><a href="#id2946726">Pre-conditions</a></dt><dt><a href="#id2946787">Manual Configuration</a></dt></dl></dd><dt><a href="#id2946805">When not to use Samba to print to +CUPS</a></dt><dt><a href="#id2946822">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2946857">Where to find Documentation</a></dt><dt><a href="#id2946870">How to ask for Help</a></dt><dt><a href="#id2946883">Where to find Help</a></dt></dl></dd><dt><a href="#id2946896">Appendix</a></dt><dd><dl><dt><a href="#id2946904">Printing from CUPS to Windows attached +Printers</a></dt><dt><a href="#id2947118">More CUPS filtering Chains</a></dt><dt><a href="#id2947424">Trouble Shooting Guidelines to fix typical Samba printing +Problems</a></dt><dt><a href="#id2948546">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2960717">Features and Benefits</a></dt><dt><a href="#id2960735">Discussion</a></dt><dt><a href="#id2960826">Included modules</a></dt><dd><dl><dt><a href="#id2960833">audit</a></dt><dt><a href="#id2960871">extd_audit</a></dt><dt><a href="#id2960995">fake_perms</a></dt><dt><a href="#id2961013">recycle</a></dt><dt><a href="#id2961151">netatalk</a></dt></dl></dd><dt><a href="#id2961195">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2961218">DatabaseFS</a></dt><dt><a href="#id2961273">vscan</a></dt></dl></dd><dt><a href="#id2961303">Common Errors</a></dt></dl></dd><dt>21. <a href="#winbind">Integrated Logon Support using Winbind</a></dt><dd><dl><dt><a href="#id2962201">Features and Benefits</a></dt><dt><a href="#id2962229">Introduction</a></dt><dt><a href="#id2962301">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2962361">Target Uses</a></dt></dl></dd><dt><a href="#id2962392">How Winbind Works</a></dt><dd><dl><dt><a href="#id2962420">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2962454">Microsoft Active Directory Services</a></dt><dt><a href="#id2962477">Name Service Switch</a></dt><dt><a href="#id2962613">Pluggable Authentication Modules</a></dt><dt><a href="#id2962685">User and Group ID Allocation</a></dt><dt><a href="#id2962720">Result Caching</a></dt></dl></dd><dt><a href="#id2962747">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2962776">Introduction</a></dt><dt><a href="#id2962851">Requirements</a></dt><dt><a href="#id2962944">Testing Things Out</a></dt></dl></dd><dt><a href="#id2964563">Conclusion</a></dt><dt><a href="#id2964582">Common Errors</a></dt></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2967075">Features and Benefits</a></dt><dt><a href="#id2967264">Remote Server Administration</a></dt><dt><a href="#id2967363">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2967381">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2967592">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2967788">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2967822">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2966885">Features and Benefits</a></dt><dt><a href="#id2966939">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2968722">Windows 9x/Me Policies</a></dt><dt><a href="#id2968817">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2968950">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2969202">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2969303">Samba Editreg Toolset</a></dt><dt><a href="#id2969324">Windows NT4/200x</a></dt><dt><a href="#id2969344">Samba PDC</a></dt></dl></dd><dt><a href="#id2969388">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2969535">Common Errors</a></dt><dd><dl><dt><a href="#id2969549">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2970756">Features and Benefits</a></dt><dt><a href="#id2970790">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2970831">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971236">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972407">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972472">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972737">Mandatory profiles</a></dt><dt><a href="#id2972795">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972841">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972861">MS Windows 9x/Me</a></dt><dt><a href="#id2973009">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973563">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2974067">Common Errors</a></dt><dd><dl><dt><a href="#id2974080">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974143">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974365">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2978309">Features and Benefits</a></dt><dt><a href="#id2978577">Technical Discussion</a></dt><dd><dl><dt><a href="#id2978595">PAM Configuration Syntax</a></dt><dt><a href="#id2979265">Example System Configurations</a></dt><dt><a href="#id2979567">smb.conf PAM Configuration</a></dt><dt><a href="#id2979625">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2979709">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2980075">Common Errors</a></dt><dd><dl><dt><a href="#id2980089">pam_winbind problem</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2982211">Features and Benefits</a></dt><dt><a href="#id2982236">Background Information</a></dt><dt><a href="#id2982281">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2982337">/etc/hosts</a></dt><dt><a href="#id2982462">/etc/resolv.conf</a></dt><dt><a href="#id2982506">/etc/host.conf</a></dt><dt><a href="#id2982548">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2982637">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2982784">The NetBIOS Name Cache</a></dt><dt><a href="#id2982829">The LMHOSTS file</a></dt><dt><a href="#id2983073">HOSTS file</a></dt><dt><a href="#id2983105">DNS Lookup</a></dt><dt><a href="#id2983130">WINS Lookup</a></dt></dl></dd><dt><a href="#id2983200">Common Errors</a></dt><dd><dl><dt><a href="#id2983216">My Boomerang Won't Come Back</a></dt><dt><a href="#id2983248">Very Slow Network Connections</a></dt><dt><a href="#id2983300">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2984418">Features and Benefits</a></dt><dt><a href="#id2984620">What are charsets and unicode?</a></dt><dt><a href="#id2984690">Samba and charsets</a></dt><dt><a href="#id2984790">Conversion from old names</a></dt><dt><a href="#id2984835">Japanese charsets</a></dt></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2984038">Note</a></dt><dt><a href="#id2984063">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2985605">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter 10. Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2886062">Features and Benefits</a></dt><dt><a href="#id2886141">What is Browsing?</a></dt><dt><a href="#id2886251">Discussion</a></dt><dd><dl><dt><a href="#id2886267">NetBIOS over TCP/IP</a></dt><dt><a href="#id2886430">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2886562">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2886698">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2886824">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2887045">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2887315">Making Samba the domain master</a></dt><dt><a href="#id2887471">Note about broadcast addresses</a></dt><dt><a href="#id2887488">Multiple interfaces</a></dt><dt><a href="#id2887517">Use of the Remote Announce parameter</a></dt><dt><a href="#id2887626">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2887687">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2887846">Setting up a WINS server</a></dt><dt><a href="#id2888045">WINS Replication</a></dt><dt><a href="#id2888070">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2888154">Helpful Hints</a></dt><dd><dl><dt><a href="#id2888167">Windows Networking Protocols</a></dt><dt><a href="#id2888234">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2888372">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2888419">Browsing support in Samba</a></dt><dt><a href="#id2888526">Problem resolution</a></dt><dt><a href="#id2888605">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2889225">Common Errors</a></dt><dd><dl><dt><a href="#id2889240">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2889269">My client reports "This server is not configured to list shared resources"</a></dt></dl></dd></dl></div><p> This document contains detailed information as well as a fast track guide to implementing browsing across subnets and / or across workgroups (or domains). -WINS is the best tool for resolution of NetBIOS names to IP addesses. WINS is +WINS is the best tool for resolution of NetBIOS names to IP addresses. WINS is NOT involved in browse list handling except by way of name to address resolution. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> MS Windows 2000 and later can be configured to operate with NO NetBIOS @@ -2258,15 +2272,15 @@ over TCP/IP. Samba-3 and later also supports this mode of operation. When the use of NetBIOS over TCP/IP has been disabled then the primary means for resolution of MS Windows machine names is via DNS and Active Directory. The following information assumes that your site is running NetBIOS over TCP/IP. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883706"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886062"></a>Features and Benefits</h2></div></div><div></div></div><p> Someone once referred to the past in terms of: <span class="emphasis"><em>They were the worst of times, they were the best of times. The more we look back, them more we long for what was and hope it never returns!</em></span>. </p><p> -For many MS Windows network administrators that statement sums up their feelings about -NetBIOS networking precisely. For those who mastered NetBIOS networking it's fickle -nature was just par for the course. For those who never quite managed to tame it's -lusty features NetBIOS is like Paterson's Curse. +For many MS Windows network administrators, that statement sums up their feelings about +NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle +nature was just par for the course. For those who never quite managed to tame its +lusty features, NetBIOS is like Paterson's Curse. </p><p> For those not familiar with botanical problems in Australia: Paterson's curse, Echium plantagineum, was introduced to Australia from Europe during the mid-nineteenth @@ -2276,7 +2290,7 @@ ability to germinate at any time of year, given the right conditions, are some o features which make it such a persistent weed. </p><p> In this chapter we explore vital aspects of SMB (Server Message Block) networking with -a particular focus on SMB as implmented through running NetBIOS (Network Basic +a particular focus on SMB as implemented through running NetBIOS (Network Basic Input / Output System) over TCP/IP. Since Samba does NOT implement SMB or NetBIOS over any other protocols we need to know how to configure our network environment and simply remember to use nothing but TCP/IP on all our MS Windows network clients. @@ -2291,7 +2305,7 @@ support for NetBIOS, in which case WINS is of no relevance. Samba-3 supports thi </p><p> For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) the use of DNS is necessary for host name resolution. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883784"></a>What is Browsing?</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886141"></a>What is Browsing?</h2></div></div><div></div></div><p> To most people browsing means that they can see the MS Windows and Samba servers in the Network Neighborhood, and when the computer icon for a particular server is clicked, it opens up and shows the shares and printers available on the target server. @@ -2299,7 +2313,7 @@ clicked, it opens up and shows the shares and printers available on the target s What seems so simple is in fact a very complex interaction of different technologies. The technologies (or methods) employed in making all of this work includes: </p><table class="simplelist" border="0" summary="Simple list"><tr><td>MS Windows machines register their presence to the network</td></tr><tr><td>Machines announce themselves to other machines on the network</td></tr><tr><td>One or more machine on the network collates the local announcements</td></tr><tr><td>The client machine finds the machine that has the collated list of machines</td></tr><tr><td>The client machine is able to resolve the machine names to IP addresses</td></tr><tr><td>The client machine is able to connect to a target machine</td></tr></table><p> -The samba application that controls/manages browse list management and name resolution is +The Samba application that controls browse list management and name resolution is called <tt class="filename">nmbd</tt>. The configuration parameters involved in nmbd's operation are: </p><pre class="programlisting"> @@ -2326,18 +2340,18 @@ called <tt class="filename">nmbd</tt>. The configuration parameters involved in * wins support wins hook </pre><p> -For Samba the WINS Server and WINS Support are mutually exclusive options. Those marked with +For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are the only options that commonly MAY need to be modified. Even if not one of these -parameters is set nmbd will still do it's job. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883967"></a>Discussion</h2></div></div><div></div></div><p> +parameters is set <tt class="filename">nmbd</tt> will still do it's job. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886251"></a>Discussion</h2></div></div><div></div></div><p> Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging. SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports -NetBIOS over TCP/IP for backwards compatibility. Microsoft are intent on phasing out NetBIOS +NetBIOS over TCP/IP for backwards compatibility. Microsoft is intent on phasing out NetBIOS support. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883983"></a>NetBIOS over TCP/IP</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886267"></a>NetBIOS over TCP/IP</h3></div></div><div></div></div><p> Samba implements NetBIOS, as does MS Windows NT / 200x / XP, by encapsulating it over TCP/IP. MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to -affect browse list management. When running NetBIOS over TCP/IP this uses UDP based messaging. +affect browse list management. When running NetBIOS over TCP/IP, this uses UDP based messaging. UDP messages can be broadcast or unicast. </p><p> Normally, only unicast UDP messaging can be forwarded by routers. The @@ -2346,7 +2360,7 @@ to remote network segments via unicast UDP. Similarly, the <b class="command">remote browse sync</b> parameter of <tt class="filename">smb.conf</tt> implements browse list collation using unicast UDP. </p><p> -Secondly, in those networks where Samba is the only SMB server technology +Secondly, in those networks where Samba is the only SMB server technology, wherever possible <tt class="filename">nmbd</tt> should be configured on one (1) machine as the WINS server. This makes it easy to manage the browsing environment. If each network segment is configured with it's own Samba WINS server, then the only way to @@ -2361,9 +2375,9 @@ the use of the <b class="command">remote announce</b> and the As of Samba 3 WINS replication is being worked on. The bulk of the code has been committed, but it still needs maturation. This is NOT a supported feature of the Samba-3.0.0 release. Hopefully, this will become a supported feature -of one of the samba-3 release series. +of one of the Samba-3 release series. </p><p> -Right now samba WINS does not support MS-WINS replication. This means that +Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server there must only be one <tt class="filename">nmbd</tt> configured as a WINS server on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used @@ -2378,7 +2392,7 @@ Lastly, take note that browse lists are a collection of unreliable broadcast messages that are repeated at intervals of not more than 15 minutes. This means that it will take time to establish a browse list and it can take up to 45 minutes to stabilise, particularly across network segments. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883290"></a>TCP/IP - without NetBIOS</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886430"></a>TCP/IP - without NetBIOS</h3></div></div><div></div></div><p> All TCP/IP using systems use various forms of host name resolution. The primary methods for TCP/IP hostname resolutions involves either a static file (<tt class="filename">/etc/hosts </tt>) or DNS (the Domain Name System). DNS is the technology that makes @@ -2407,14 +2421,14 @@ force register with a Dynamic DNS server in Windows 200x / XP using: <b class="command">ipconfig /registerdns</b> </p><p> With Active Directory (ADS), a correctly functioning DNS server is absolutely -essential. In the absence of a working DNS server that has been correctly configured +essential. In the absence of a working DNS server that has been correctly configured, MS Windows clients and servers will be totally unable to locate each other, consequently network services will be severely impaired. </p><p> The use of Dynamic DNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for it's ability to adequately support the SRV (service) records that are needed for Active Directory. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2883418"></a>DNS and Active Directory</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886562"></a>DNS and Active Directory</h3></div></div><div></div></div><p> Occasionally we hear from Unix network administrators who want to use a Unix based Dynamic DNS server in place of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible @@ -2434,9 +2448,9 @@ The following are some of the default service records that Active Directory requ Entry used by MS Windows clients to locate machines using the Global Unique Identifier. </p></li><li><p>_ldap._tcp.<span class="emphasis"><em>Site</em></span>.gc.ms-dcs.<span class="emphasis"><em>DomainTree</em></span></p><p> - Used by MS Windows clients to locate site configuration dependant + Used by MS Windows clients to locate site configuration dependent Global Catalog server. - </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2883554"></a>How Browsing Functions</h2></div></div><div></div></div><p> + </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886698"></a>How Browsing Functions</h2></div></div><div></div></div><p> MS Windows machines register their NetBIOS names (ie: the machine name for each service type in operation) on start up. The exact method by which this name registration @@ -2444,11 +2458,11 @@ takes place is determined by whether or not the MS Windows client/server has been given a WINS server address, whether or not LMHOSTS lookup is enabled, or if DNS for NetBIOS name resolution is enabled, etc. </p><p> -In the case where there is no WINS server all name registrations as +In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse +which the Samba server name may be forcibly injected into the browse list of a remote MS Windows network (using the <b class="command">remote announce</b> parameter). </p><p> @@ -2477,7 +2491,7 @@ Any configuration that breaks name resolution and/or browsing intrinsics will annoy users because they will have to put up with protracted inability to use the network services. </p><p> -Samba supports a feature that allows forced synchonisation +Samba supports a feature that allows forced synchronisation of browse lists across routed networks using the <b class="command">remote browse sync</b> parameter in the <tt class="filename">smb.conf</tt> file. This causes Samba to contact the local master browser on a remote network and @@ -2491,7 +2505,7 @@ words, for cross subnet browsing to function correctly it is essential that a name to address resolution mechanism be provided. This mechanism could be via DNS, <tt class="filename">/etc/hosts</tt>, and so on. -</p><div xmlns:ns14="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884860"></a>Setting up WORKGROUP Browsing</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886824"></a>Setting up WORKGROUP Browsing</h3></div></div><div></div></div><p> To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one Samba server to be the Domain Master Browser (note that this is *NOT* @@ -2501,7 +2515,7 @@ to collate the browse lists from local master browsers on all the subnets that have a machine participating in the workgroup. Without one machine configured as a domain master browser each subnet would be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes +subnet. It is the presence of a domain master browser that makes cross subnet browsing possible for a workgroup. </p><p> In an WORKGROUP environment the domain master browser must be a @@ -2509,22 +2523,22 @@ Samba server, and there must only be one domain master browser per workgroup name. To set up a Samba server as a domain master browser, set the following option in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : -</p><ns14:p> -</ns14:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = yes -</pre><ns14:p> -</ns14:p><p> +</pre><p> +</p><p> The domain master browser should also preferrably be the local master browser for its own subnet. In order to achieve this set the following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : -</p><ns14:p> -</ns14:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = yes local master = yes preferred master = yes os level = 65 -</pre><ns14:p> -</ns14:p><p> +</pre><p> +</p><p> The domain master browser may be the same machine as the WINS server, if you require. </p><p> @@ -2536,14 +2550,14 @@ tend to get rebooted more often, so it's not such a good idea to use these). To make a Samba server a local master browser set the following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : -</p><ns14:p> -</ns14:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = no local master = yes preferred master = yes os level = 65 -</pre><ns14:p> -</ns14:p><p> +</pre><p> +</p><p> Do not do this for more than one Samba server on each subnet, or they will war with each other over which is to be the local master browser. @@ -2558,18 +2572,18 @@ be the local master browser then you can disable Samba from becoming a local master browser by setting the following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : -</p><ns14:p> -</ns14:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = no local master = no preferred master = no os level = 0 -</pre><ns14:p> -</ns14:p></div><div xmlns:ns15="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885066"></a>Setting up DOMAIN Browsing</h3></div></div><div></div></div><p> +</pre><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887045"></a>Setting up DOMAIN Browsing</h3></div></div><div></div></div><p> If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many +By default, a Windows NT Primary Domain Controller for a domain +is also the Domain master browser for that domain, and many things will break if a Samba server registers the Domain master browser NetBIOS name (<i class="replaceable"><tt>DOMAIN</tt></i><1B>) with WINS instead of the PDC. @@ -2579,20 +2593,20 @@ you may set up Samba servers as local master browsers as described. To make a Samba server a local master browser set the following options in the <b class="command">[global]</b> section of the <tt class="filename">smb.conf</tt> file : -</p><ns15:p> -</ns15:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = no local master = yes preferred master = yes os level = 65 -</pre><ns15:p> -</ns15:p><p> +</pre><p> +</p><p> If you wish to have a Samba server fight the election with machines on the same subnet you may set the <i class="parameter"><tt>os level</tt></i> parameter to lower levels. By doing this you can tune the order of machines that will become local master browsers if they are running. For -more details on this see the section <a href="#browse-force-master" title="Forcing samba to be the master"> -Forcing samba to be the master browser</a> +more details on this see the section <a href="#browse-force-master" title="Forcing Samba to be the master"> +Forcing Samba to be the master browser</a> below. </p><p> If you have Windows NT machines that are members of the domain @@ -2601,14 +2615,14 @@ you can disable Samba from taking part in browser elections and ever becoming a local master browser by setting following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : -</p><ns15:p> -</ns15:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> domain master = no local master = no preferred master = no os level = 0 -</pre><ns15:p> -</ns15:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="browse-force-master"></a>Forcing samba to be the master</h3></div></div><div></div></div><p> +</pre><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="browse-force-master"></a>Forcing Samba to be the master</h3></div></div><div></div></div><p> Who becomes the <i class="parameter"><tt>master browser</tt></i> is determined by an election process using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the @@ -2623,48 +2637,48 @@ samba systems!) A <i class="parameter"><tt>os level</tt></i> of 2 would make it beat WfWg and Win95, but not MS Windows NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. </p><p>The maximum os level is 255</p><p> -If you want samba to force an election on startup, then set the +If you want Samba to force an election on startup, then set the <i class="parameter"><tt>preferred master</tt></i> global option in <tt class="filename">smb.conf</tt> to <tt class="constant">yes</tt>. Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with <i class="parameter"><tt>preferred master</tt></i> to +care, as if you have two hosts (whether they are Windows 95 or NT or +Samba) on the same local subnet both set with <i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, then periodically and continually they will force an election in order to become the local master browser. </p><p> - If you want samba to be a <i class="parameter"><tt>domain master browser</tt></i>, then it is +If you want Samba to be a <i class="parameter"><tt>domain master browser</tt></i>, then it is recommended that you also set <i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, because -samba will not become a domain master browser for the whole of your +Samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet. </p><p> -It is possible to configure two samba servers to attempt to become +It is possible to configure two Samba servers to attempt to become the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will +up will be the domain master browser. All other Samba servers will attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master +will find that another Samba server is already the domain master browser and will fail. This provides automatic redundancy, should the current domain master browser fail. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885332"></a>Making samba the domain master</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887315"></a>Making Samba the domain master</h3></div></div><div></div></div><p> The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting <i class="parameter"><tt>domain master = yes</tt></i> +make Samba act as the domain master by setting <i class="parameter"><tt>domain master = yes</tt></i> in <tt class="filename">smb.conf</tt>. By default it will not be a domain master. </p><p> Note that you should <span class="emphasis"><em>not</em></span> set Samba to be the domain master for a workgroup that has the same name as an NT Domain. </p><p> -When samba is the domain master and the master browser it will listen +When Samba is the domain master and the master browser, it will listen for master announcements (made roughly every twelve minutes) from local master browsers on other subnets and then contact them to synchronise browse lists. </p><p> -If you want samba to be the domain master then I suggest you also set +If you want Samba to be the domain master then I suggest you also set the <i class="parameter"><tt>os level</tt></i> high enough to make sure it wins elections, and set -<i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, to get samba to force an election on +<i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, to get Samba to force an election on startup. </p><p> -Note that all your servers (including samba) and clients should be +Note that all your servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your clients are only using broadcasting to resolve NetBIOS names, then two things will occur: </p><div class="orderedlist"><ol type="1"><li><p> @@ -2675,11 +2689,11 @@ using broadcasting to resolve NetBIOS names, then two things will occur: a user attempts to access a host in that list, it will be unable to resolve the NetBIOS name of that host. </p></li></ol></div><p> -If, however, both samba and your clients are using a WINS server, then: +If, however, both Samba and your clients are using a WINS server, then: </p><div class="orderedlist"><ol type="1"><li><p> your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address + Samba has registered that it is a domain master browser with the WINS + server, your local master browser will receive Samba's IP address as its domain master browser. </p></li><li><p> when a client receives a domain-wide browse list, and a user attempts @@ -2687,37 +2701,37 @@ If, however, both samba and your clients are using a WINS server, then: resolve the NetBIOS name of that host. as long as that host has registered its NetBIOS name with the same WINS server, the user will be able to see that host. - </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888727"></a>Note about broadcast addresses</h3></div></div><div></div></div><p> + </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887471"></a>Note about broadcast addresses</h3></div></div><div></div></div><p> If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups does not seem to support a 0's broadcast and you will probably find that browsing and name lookups won't work. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888744"></a>Multiple interfaces</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887488"></a>Multiple interfaces</h3></div></div><div></div></div><p> Samba now supports machines with multiple network interfaces. If you have multiple interfaces then you will need to use the <b class="command">interfaces</b> option in <tt class="filename">smb.conf</tt> to configure them. -</p></div><div xmlns:ns16="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888773"></a>Use of the Remote Announce parameter</h3></div></div><div></div></div><ns16:p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887517"></a>Use of the Remote Announce parameter</h3></div></div><div></div></div><p> The <i class="parameter"><tt>remote announce</tt></i> parameter of <tt class="filename">smb.conf</tt> can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. The syntax of the <i class="parameter"><tt>remote announce</tt></i> parameter is: -</ns16:p><pre class="programlisting"> +</p><pre class="programlisting"> remote announce = a.b.c.d [e.f.g.h] ... -</pre><ns16:p> -_or_ -</ns16:p><pre class="programlisting"> +</pre><p> +<span class="emphasis"><em>or</em></span> +</p><pre class="programlisting"> remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... -</pre><ns16:p> +</pre><p> where: -</ns16:p><div class="variablelist"><dl><dt><span class="term"><i class="replaceable"><tt>a.b.c.d</tt></i> and +</p><div class="variablelist"><dl><dt><span class="term"><i class="replaceable"><tt>a.b.c.d</tt></i> and <i class="replaceable"><tt>e.f.g.h</tt></i></span></dt><dd><p>is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. +or the broadcast address of the remote network. ie: the LMB is at 192.168.1.10, or the address could be given as 192.168.1.255 where the netmask is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast -address of the remote network every host will receive +address of the remote network, every host will receive our announcements. This is noisy and therefore undesirable but may be necessary if we do NOT know the IP address of the remote LMB.</p></dd><dt><span class="term"><i class="replaceable"><tt>WORKGROUP</tt></i></span></dt><dd><p>is optional and can be either our own workgroup @@ -2726,28 +2740,28 @@ workgroup name of the remote network then our NetBIOS machine names will end up looking like they belong to that workgroup, this may cause name resolution problems and should be avoided. -</p></dd></dl></div><ns16:p> -</ns16:p></div><div xmlns:ns17="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888877"></a>Use of the Remote Browse Sync parameter</h3></div></div><div></div></div><p> +</p></dd></dl></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887626"></a>Use of the Remote Browse Sync parameter</h3></div></div><div></div></div><p> The <i class="parameter"><tt>remote browse sync</tt></i> parameter of <tt class="filename">smb.conf</tt> is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our +another LMB that it must synchronise its NetBIOS name list with our Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment. -</p><ns17:p> +simultaneously the LMB on its network segment. +</p><p> The syntax of the <i class="parameter"><tt>remote browse sync</tt></i> parameter is: -</ns17:p><pre class="programlisting"> +</p><pre class="programlisting"> remote browse sync = <i class="replaceable"><tt>a.b.c.d</tt></i> -</pre><ns17:p> +</pre><p> where <i class="replaceable"><tt>a.b.c.d</tt></i> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. -</ns17:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888938"></a>WINS - The Windows Internetworking Name Server</h2></div></div><div></div></div><p> -Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2887687"></a>WINS - The Windows Internetworking Name Server</h2></div></div><div></div></div><p> +Use of WINS (either Samba WINS <span class="emphasis"><em>or</em></span> MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a -name_type value for each of of several types of service it has available. +name_type value for each of several types of service it has available. eg: It registers its name directly as a unique (the type 0x03) name. -It also registers its name if it is running the lanmanager compatible +It also registers its name if it is running the LanManager compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name. </p><p> @@ -2762,7 +2776,7 @@ that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured +information can only be provided via WINS <span class="emphasis"><em>or</em></span> via statically configured <tt class="filename">lmhosts</tt> files that must reside on all clients in the absence of WINS. </p><p> @@ -2793,16 +2807,16 @@ Never use both <i class="parameter"><tt>wins support = yes</tt></i> together with <i class="parameter"><tt>wins server = a.b.c.d</tt></i> particularly not using it's own IP address. Specifying both will cause <span class="application">nmbd</span> to refuse to start! -</p></div><div xmlns:ns18="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889089"></a>Setting up a WINS server</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887846"></a>Setting up a WINS server</h3></div></div><div></div></div><p> Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must add the following option to the <tt class="filename">smb.conf</tt> file on the selected machine : in the <i class="parameter"><tt>[globals]</tt></i> section add the line -</p><ns18:p> -</ns18:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> wins support = yes -</pre><ns18:p> -</ns18:p><p> +</pre><p> +</p><p> Versions of Samba prior to 1.9.17 had this parameter default to yes. If you have any older versions of Samba on your network it is strongly suggested you upgrade to a recent version, or at the very @@ -2811,7 +2825,7 @@ least set the parameter to 'no' on all these machines. Machines with <i class="parameter"><tt>wins support = yes</tt></i> will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names. </p><p> -You should set up only ONE wins server. Do NOT set the +You should set up only ONE WINS server. Do NOT set the <i class="parameter"><tt>wins support = yes</tt></i> option on more than one Samba server. </p><p> @@ -2819,7 +2833,7 @@ To set up a Windows NT Server as a WINS server you need to set up the WINS service - see your NT documentation for details. Note that Windows NT WINS Servers can replicate to each other, allowing more than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently +refuses to document these replication protocols, Samba cannot currently participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server @@ -2834,11 +2848,11 @@ the <span class="guilabel">Control Panel->Network->Protocols->TCP->W in Windows 95 or Windows NT. To tell a Samba server the IP address of the WINS server add the following line to the <i class="parameter"><tt>[global]</tt></i> section of all <tt class="filename">smb.conf</tt> files : -</p><ns18:p> -</ns18:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> wins server = <name or IP address> -</pre><ns18:p> -</ns18:p><p> +</pre><p> +</p><p> where <name or IP address> is either the DNS name of the WINS server machine or its IP address. </p><p> @@ -2853,22 +2867,45 @@ The first details setting up cross subnet browsing on a network containing Windows 95, Samba and Windows NT machines that are not configured as part of a Windows NT Domain. The second details setting up cross subnet browsing on networks that contain NT Domains. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889284"></a>WINS Replication</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888045"></a>WINS Replication</h3></div></div><div></div></div><p> Samba-3 permits WINS replication through the use of the <tt class="filename">wrepld</tt> utility. This tool is not currently capable of being used as it is still in active development. As soon as this tool becomes moderately functional we will prepare man pages and enhance this section of the documentation to provide usage and technical details. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889309"></a>Static WINS Entries</h3></div></div><div></div></div><p> -New to Samba-3 is a tool called <b class="command">winsedit</b> that may be used to add -static WINS entries to the WINS database. This tool can be used also to modify entries -existing in the WINS database. -</p><p> -The development of the winsedit tool was made necessary due to the migration -of the older style wins.dat file into a new tdb binary backend data store. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2889340"></a>Helpful Hints</h2></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888070"></a>Static WINS Entries</h3></div></div><div></div></div><p> +Adding static entries to your Samba-3 WINS server is actually fairly easy. +All you have to do is add a line to <tt class="filename">wins.dat</tt>, typically +located in <tt class="filename">/usr/local/samba/var/locks</tt>. +</p><p> +Entries in <tt class="filename">wins.dat</tt> take the form of + +</p><pre class="programlisting"> +"NAME#TYPE" TTL ADDRESS+ FLAGS +</pre><p> + +where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the +time-to-live as an absolute time in seconds, ADDRESS+ is one or more +addresses corresponding to the registration and FLAGS are the NetBIOS +flags for the registration. +</p><p> +A typical dynamic entry looks like: +</p><pre class="programlisting"> +"MADMAN#03" 1055298378 192.168.1.2 66R +</pre><p> + +To make it static, all that has to be done is set the TTL to 0: + +</p><pre class="programlisting"> +"MADMAN#03" 0 192.168.1.2 66R +</pre><p> +</p><p> +Though this method works with early Samba-3 versions, there's a +possibility that it may change in future versions if WINS replication +is added. +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888154"></a>Helpful Hints</h2></div></div><div></div></div><p> The following hints should be carefully considered as they are stumbling points for many new network administrators. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889353"></a>Windows Networking Protocols</h3></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888167"></a>Windows Networking Protocols</h3></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Do NOT use more than one (1) protocol on MS Windows machines </p></div><p> A very common cause of browsing problems results from installing more than @@ -2876,7 +2913,7 @@ one protocol on an MS Windows machine. </p><p> Every NetBIOS machine takes part in a process of electing the LMB (and DMB) every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or +of precedence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably win and thus retain it's role. </p><p> @@ -2898,29 +2935,32 @@ differently from MS Windows NT4. Generally, where a server does NOT support the newer or extended protocol, these will fall back to the NT4 protocols. </em></span></p><p> The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! -</p></div><div xmlns:ns19="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889420"></a>Name Resolution Order</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888234"></a>Name Resolution Order</h3></div></div><div></div></div><p> Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information -are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>WINS: the best tool!</td></tr><tr><td>LMHOSTS: is static and hard to maintain.</td></tr><tr><td>Broadcast: uses UDP and can not resolve names across remote segments.</td></tr></table><p> -Alternative means of name resolution includes:</p><table class="simplelist" border="0" summary="Simple list"><tr><td><tt class="filename">/etc/hosts</tt>: is static, hard to maintain, and lacks name_type info</td></tr><tr><td>DNS: is a good choice but lacks essential name_type info.</td></tr></table><ns19:p> +are: +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>WINS: the best tool!</td></tr><tr><td>LMHOSTS: is static and hard to maintain.</td></tr><tr><td>Broadcast: uses UDP and can not resolve names across remote segments.</td></tr></table><p> +Alternative means of name resolution includes: +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><tt class="filename">/etc/hosts</tt>: is static, hard to maintain, and lacks name_type info</td></tr><tr><td>DNS: is a good choice but lacks essential name_type info.</td></tr></table><p> Many sites want to restrict DNS lookups and want to avoid broadcast name -resolution traffic. The "name resolve order" parameter is of great help here. -The syntax of the "name resolve order" parameter is: -</ns19:p><pre class="programlisting"> +resolution traffic. The <i class="parameter"><tt>name resolve order</tt></i> parameter is +of great help here. The syntax of the <i class="parameter"><tt>name resolve order</tt></i> +parameter is: +</p><pre class="programlisting"> name resolve order = wins lmhosts bcast host -</pre><ns19:p> -_or_ -</ns19:p><pre class="programlisting"> +</pre><p> +<span class="emphasis"><em>or</em></span> +</p><pre class="programlisting"> name resolve order = wins lmhosts (eliminates bcast and host) -</pre><ns19:p> +</pre><p> The default is: -</ns19:p><pre class="programlisting"> -name resolve order = host lmhost wins bcast -</pre><ns19:p> +</p><pre class="programlisting"> +name resolve order = host lmhost wins bcast +</pre><p> where "host" refers the the native methods used by the Unix system to implement the gethostbyname() function call. This is normally controlled by <tt class="filename">/etc/host.conf</tt>, <tt class="filename">/etc/nsswitch.conf</tt> and <tt class="filename">/etc/resolv.conf</tt>. -</ns19:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2889541"></a>Technical Overview of browsing</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888372"></a>Technical Overview of browsing</h2></div></div><div></div></div><p> SMB networking provides a mechanism by which clients can access a list of machines in a network, a so-called <i class="parameter"><tt>browse list</tt></i>. This list contains machines that are ready to offer file and/or print services @@ -2931,7 +2971,7 @@ browsing has been problematic for some Samba users, hence this document. </p><p> MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way +configured to not use NetBIOS over TCP/IP. When configured this way, it is imperative that name resolution (using DNS/LDAP/ADS) be correctly configured and operative. Browsing will NOT work if name resolution from SMB machine names to IP addresses does not function correctly. @@ -2940,7 +2980,7 @@ Where NetBIOS over TCP/IP is enabled use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that can NOT be provided by any other means of name resolution. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889588"></a>Browsing support in samba</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888419"></a>Browsing support in Samba</h3></div></div><div></div></div><p> Samba facilitates browsing. The browsing is supported by <span class="application">nmbd</span> and is also controlled by options in the <tt class="filename">smb.conf</tt> file. Samba can act as a local browse master for a workgroup and the ability @@ -2950,7 +2990,7 @@ Samba can also act as a domain master browser for a workgroup. This means that it will collate lists from local browse masters into a wide area network server list. In order for browse clients to resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server. +both Samba and your clients use a WINS server. </p><p> Note that you should NOT set Samba to be the domain master for a workgroup that has the same name as an NT Domain: on each wide area @@ -2959,11 +2999,11 @@ regardless of whether it is NT, Samba or any other type of domain master that is providing this service. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows +necessary to specifically use Samba as your WINS server. MS Windows NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on +your WINS server. In a mixed NT/2000/2003 server and Samba environment on a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is +WINS server capabilities. In a Samba-only environment, it is recommended that you use one and only one Samba server as your WINS server. </p></div><p> To get browsing to work you need to run nmbd as usual, but will need @@ -2975,8 +3015,8 @@ browsing on another subnet. It is recommended that this option is only used for 'unusual' purposes: announcements over the internet, for example. See <i class="parameter"><tt>remote announce</tt></i> in the <tt class="filename">smb.conf</tt> man page. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889695"></a>Problem resolution</h3></div></div><div></div></div><p> -If something doesn't work then hopefully the log.nmb file will help +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888526"></a>Problem resolution</h3></div></div><div></div></div><p> +If something doesn't work then hopefully the log.nmbd file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored in text form in a file called <tt class="filename">browse.dat</tt>. @@ -3000,15 +3040,13 @@ server resources. The other big problem people have is that their broadcast address, netmask or IP address is wrong (specified with the "interfaces" option in <tt class="filename">smb.conf</tt>) -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889774"></a>Browsing across subnets</h3></div></div><div></div></div><p> -Since the release of Samba 1.9.17(alpha1) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings. +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888605"></a>Browsing across subnets</h3></div></div><div></div></div><p> +Since the release of Samba 1.9.17(alpha1), Samba has supported the +replication of browse lists across subnet boundaries. This section +describes how to set this feature up in different settings. </p><p> To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least +by routers that don't pass broadcast traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing NetBIOS name to IP address translation to be done by doing a direct query of the WINS server. This is done via a directed UDP packet on @@ -3023,16 +3061,16 @@ be they Windows 95, Windows NT, or Samba servers must have the IP address of a WINS server given to them by a DHCP server, or by manual configuration (for Win95 and WinNT, this is in the TCP/IP Properties, under Network settings) for Samba this is in the <tt class="filename">smb.conf</tt> file. -</p><div xmlns:ns20="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2889825"></a>How does cross subnet browsing work ?</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888654"></a>How does cross subnet browsing work ?</h4></div></div><div></div></div><p> Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. Samba is capable of cross subnet browsing when configured correctly. </p><p> Consider a network set up as follows : -</p><ns20:p> +</p><p> -</ns20:p><pre class="programlisting"> +</p><pre class="programlisting"> (DMB) N1_A N1_B N1_C N1_D N1_E | | | | | @@ -3047,8 +3085,8 @@ Consider a network set up as follows : | | | | | | | | N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D (WINS) -</pre><ns20:p> -</ns20:p><p> +</pre><p> +</p><p> Consisting of 3 subnets (1, 2, 3) connected by two routers (R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume @@ -3089,9 +3127,9 @@ called 'non-authoritative'. At this point the browse lists look as follows (these are the machines you would see in your network neighborhood if you looked in it on a particular network right now). -</p><ns20:p> -</ns20:p><div class="table"><a name="id2889940"></a><p class="title"><b>Table 10.1. Browse subnet example 1</b></p><table summary="Browse subnet example 1" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><ns20:p> -</ns20:p><p> +</p><p> +</p><div class="table"><a name="id2888772"></a><p class="title"><b>Table 10.1. Browse subnet example 1</b></p><table summary="Browse subnet example 1" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p> +</p><p> Note that at this point all the subnets are separate, no machine is seen across any of the subnets. </p><p> @@ -3111,11 +3149,11 @@ names it knows about. Once the domain master browser receives the MasterAnnouncement packet it schedules a synchronization request to the sender of that packet. After both synchronizations are done the browse lists look like : -</p><ns20:p> -</ns20:p><div class="table"><a name="id2890050"></a><p class="title"><b>Table 10.2. Browse subnet example 2</b></p><table summary="Browse subnet example 2" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><ns20:p> +</p><p> +</p><div class="table"><a name="id2888886"></a><p class="title"><b>Table 10.2. Browse subnet example 2</b></p><table summary="Browse subnet example 2" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. -</ns20:p><p> +</p><p> At this point users looking in their network neighborhood on subnets 1 or 2 will see all the servers on both, users on subnet 3 will still only see the servers on their own subnet. @@ -3126,24 +3164,24 @@ synchronizes browse lists with the domain master browser (N1_A) it gets both the server entries on subnet 1, and those on subnet 2. After N3_D has synchronized with N1_C and vica-versa the browse lists look like. -</p><ns20:p> -</ns20:p><div class="table"><a name="id2890149"></a><p class="title"><b>Table 10.3. Browse subnet example 3</b></p><table summary="Browse subnet example 3" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><ns20:p> +</p><p> +</p><div class="table"><a name="id2888985"></a><p class="title"><b>Table 10.3. Browse subnet example 3</b></p><table summary="Browse subnet example 3" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. -</ns20:p><p> +</p><p> At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on +subnets 1 or 3 will see all the servers on all subnets, users on subnet 2 will still only see the servers on subnets 1 and 2, but not 3. </p><p> Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing +with the domain master browser (N1_C) and will receive the missing server entries. Finally - and as a steady state (if no machines are removed or shut off) the browse lists will look like : -</p><ns20:p> -</ns20:p><div class="table"><a name="id2890249"></a><p class="title"><b>Table 10.4. Browse subnet example 4</b></p><table summary="Browse subnet example 4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><ns20:p> +</p><p> +</p><div class="table"><a name="id2889086"></a><p class="title"><b>Table 10.4. Browse subnet example 4</b></p><table summary="Browse subnet example 4" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. -</ns20:p><p> +</p><p> Synchronizations between the domain master browser and local master browsers will continue to occur, but this should be a steady state situation. @@ -3161,13 +3199,13 @@ If either router R1 or R2 fails the following will occur: be able to access servers on its local subnet, by using subnet-isolated broadcast NetBIOS name resolution. The effects are similar to that of losing access to a DNS server. - </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890391"></a>Common Errors</h2></div></div><div></div></div><p> -Many questions are sked on the mailing lists regarding browsing. The majority of browsing + </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="id2889225"></a>Common Errors</h2></div></div><div></div></div><p> +Many questions are asked on the mailing lists regarding browsing. The majority of browsing problems originate out of incorrect configuration of NetBIOS name resolution. Some are of particular note. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890406"></a>How can one flush the Samba NetBIOS name cache without restarting samba?</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889240"></a>How can one flush the Samba NetBIOS name cache without restarting Samba?</h3></div></div><div></div></div><p> Samba's nmbd process controls all browse list handling. Under normal circumstances it is -safe to restart nmbd. This will effectively flush the samba NetBIOS name cache and cause it +safe to restart nmbd. This will effectively flush the Samba NetBIOS name cache and cause it to be rebuilt. Note that this does NOT make certain that a rogue machine name will not re-appear in the browse list. When nmbd is taken out of service another machine on the network will become the browse master. This new list may still have the rogue entry in it. If you really @@ -3175,29 +3213,29 @@ want to clear a rogue machine from the list then every machine on the network wi shut down and restarted at after all machines are down. Failing a complete restart, the only other thing you can do is wait until the entry times out and is then flushed from the list. This may take a long time on some networks (months). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890435"></a>My client reports "This server is not configured to list shared resources"</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889269"></a>My client reports "This server is not configured to list shared resources"</h3></div></div><div></div></div><p> Your guest account is probably invalid for some reason. Samba uses the guest account for browsing in smbd. Check that your guest account is valid. -</p><p>See also <i class="parameter"><tt>guest account</tt></i> in the <tt class="filename">smb.conf</tt> man page.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="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="#id2890530">Features and Benefits</a></dt><dt><a href="#id2890854">Technical Information</a></dt><dd><dl><dt><a href="#id2890917">Important Notes About Security</a></dt><dt><a href="#id2891160">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2891216">Account Management Tools</a></dt><dd><dl><dt><a href="#id2891247">The smbpasswd Command</a></dt><dt><a href="#id2891513">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2891647">Password Backends</a></dt><dd><dl><dt><a href="#id2895859">Plain Text</a></dt><dt><a href="#id2895899">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2896006">tdbsam</a></dt><dt><a href="#id2896034">ldapsam</a></dt><dt><a href="#id2897524">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2898328">Common Errors</a></dt><dd><dl><dt><a href="#id2898335">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2898350">Users are being added to the wrong backend database</a></dt><dt><a href="#id2898409">auth methods does not work</a></dt></dl></dd></dl></div><p> -Samba-3 implements a new capability to work concurrently with mulitple account backends. +</p><p>See also <i class="parameter"><tt>guest account</tt></i> in the <tt class="filename">smb.conf</tt> man page.</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="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="#id2892812">Features and Benefits</a></dt><dt><a href="#id2893140">Technical Information</a></dt><dd><dl><dt><a href="#id2893204">Important Notes About Security</a></dt><dt><a href="#id2893458">Mapping User Identifiers between MS Windows and Unix</a></dt></dl></dd><dt><a href="#id2893513">Account Management Tools</a></dt><dd><dl><dt><a href="#id2893545">The smbpasswd Command</a></dt><dt><a href="#id2893811">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2893963">Password Backends</a></dt><dd><dl><dt><a href="#id2893999">Plain Text</a></dt><dt><a href="#id2894038">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2894145">tdbsam</a></dt><dt><a href="#id2894173">ldapsam</a></dt><dt><a href="#id2895689">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2896493">Common Errors</a></dt><dd><dl><dt><a href="#id2896501">Users can not logon - Users not in Samba SAM</a></dt><dt><a href="#id2896516">Users are being added to the wrong backend database</a></dt><dt><a href="#id2896576">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 +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 <span class="emphasis"><em>"passdb backend = tdbsam_nua, guest"</em></span> 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 +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.0.0 does NOT support Non-Unix Account (NUA) operation. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890530"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892812"></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="variablelist"><p class="title"><b>Backwards Compatibility Backends</b></p><dl><dt><span class="term">Plain Text:</span></dt><dd><p> @@ -3217,7 +3255,7 @@ as follows: </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 Compatibilty):</span></dt><dd><p> + </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 @@ -3247,11 +3285,11 @@ Samba-3 introduces the following new password backend capabilities: 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 + 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">~samba/examples/LDAP</tt> directory. + 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 @@ -3274,7 +3312,7 @@ Samba-3 introduces the following new password backend capabilities: </p></dd><dt><span class="term">nisplussam:</span></dt><dd><p> The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with Sun NIS+ servers. - </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890854"></a>Technical Information</h2></div></div><div></div></div><p> + </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893140"></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> @@ -3282,7 +3320,7 @@ Samba-3 introduces the following new password backend capabilities: 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 + 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> @@ -3292,7 +3330,7 @@ Samba-3 introduces the following new password backend capabilities: information using 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 <i class="parameter"><tt>passdb backend</tt></i> parameter. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890917"></a>Important Notes About Security</h3></div></div><div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893204"></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 @@ -3334,7 +3372,7 @@ Samba-3 introduces the following new password backend capabilities: (broken) only the cached (encrypted) password will be sent to the resource server to affect a auto-reconnect. If the resource server does not support encrypted passwords the auto-reconnect will fail. <span class="emphasis"><em>USE OF ENCRYPTED PASSWORDS IS STRONGLY ADVISED.</em></span> - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891070"></a>Advantages of Encrypted Passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not passed across + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893368"></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 @@ -3345,38 +3383,38 @@ Samba-3 introduces the following new password backend capabilities: only things you can do to stop this is to use SMB encryption. </p></li><li><p>Encrypted password support allows automatic share (resource) reconnects.</p></li><li><p>Encrypted passwords are essential for PDC/BDC - operation.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891124"></a>Advantages of non-encrypted passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not kept + operation.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2893422"></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="id2891160"></a>Mapping User Identifiers between MS Windows and Unix</h3></div></div><div></div></div><p> + isn't such a big deal.</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893458"></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 Management database) accounts require + 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-3 will call the <i class="parameter"><tt>add user script</tt></i> - interface to add the account to the Samba host OS. In essence all accounts in + information database, Samba-3 will call the <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><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891216"></a>Account Management Tools</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893513"></a>Account Management Tools</h2></div></div><div></div></div><p> Samba-3 provides two (2) tools for management of User and machine accounts. These tools are -called <tt class="filename">smbpasswd</tt> and <b class="command">pdbedit</b>. A third tool is under +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 samba-3.0.1 release timing. -</p><div xmlns:ns21="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891247"></a>The <span class="emphasis"><em>smbpasswd</em></span> Command</h3></div></div><div></div></div><p> +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="id2893545"></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 + 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 @@ -3386,18 +3424,18 @@ be announced in time for samba-3.0.1 release timing. <b class="command">smbpasswd</b> can be used to: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><span class="emphasis"><em>add</em></span> user or machine accounts</td></tr><tr><td><span class="emphasis"><em>delete</em></span> user or machine accounts</td></tr><tr><td><span class="emphasis"><em>enable</em></span> user or machine accounts</td></tr><tr><td><span class="emphasis"><em>disable</em></span> user or machine accounts</td></tr><tr><td><span class="emphasis"><em>set to NULL</em></span> user passwords</td></tr><tr><td><span class="emphasis"><em>manage interdomain trust accounts</em></span></td></tr></table><p> To run smbpasswd as a normal user just type: - </p><ns21:p> - </ns21:p><pre class="screen"> + </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><ns21:p> + </pre><p> For <i class="replaceable"><tt>secret</tt></i> type old value here - or hit return if there was no old password - </ns21:p><pre class="screen"> + </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><ns21:p> - </ns21:p><p> + </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> @@ -3416,7 +3454,7 @@ be announced in time for samba-3.0.1 release timing. </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="id2891513"></a>The <span class="emphasis"><em>pdbedit</em></span> Command</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893811"></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><table class="simplelist" border="0" summary="Simple list"><tr><td>add, remove or modify user accounts</td></tr><tr><td>listing user accounts</td></tr><tr><td>migrate user accounts</td></tr></table><p> @@ -3452,29 +3490,29 @@ be announced in time for samba-3.0.1 release timing. 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></div></div><div xmlns:ns22="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891647"></a>Password Backends</h2></div></div><div></div></div><p> + </pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893963"></a>Password Backends</h2></div></div><div></div></div><p> Samba-3 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><ns22:p> -</ns22:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> [globals] passdb backend = tdbsam:/etc/samba/passdb.tdb, \ tdbsam:/etc/samba/old-passdb.tdb, guest -</pre><ns22:p> -</ns22:p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895859"></a>Plain Text</h3></div></div><div></div></div><p> - Older versions of samba retrieved user information from the unix user database +</pre><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893999"></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 conduected via the way - that the samba host OS will access it's <tt class="filename">/etc/passwd</tt> database. + 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="id2895899"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p> - Traditionally, when configuring <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">"encrypt - passwords = yes"</a> in Samba's <tt class="filename">smb.conf</tt> file, user account + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894038"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p> + Traditionally, when configuring <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt + passwords = yes</a> in Samba's <tt class="filename">smb.conf</tt> file, user account information such as username, LM/NT password hashes, password change times, and account flags have been stored in the <tt class="filename">smbpasswd(5)</tt> file. There are several disadvantages to this approach for sites with very large numbers of users (counted @@ -3503,15 +3541,15 @@ backends of the same type. For example, to use two different tdbsam databases: Samba-3 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="id2896006"></a>tdbsam</h3></div></div><div></div></div><p>Samba can store user and machine account data in a "TDB" (Trivial Database). + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894145"></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 do NOT recommend using the tdbsam backend for sites + 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 implmentations 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="id2896034"></a>ldapsam</h3></div></div><div></div></div><p> + 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="id2894173"></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 @@ -3524,7 +3562,10 @@ backends of the same type. For example, to use two different tdbsam databases: 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><p> + </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 @@ -3536,25 +3577,25 @@ backends of the same type. For example, to use two different tdbsam databases: </p><div class="itemizedlist"><ul type="disc"><li><p>The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a> maintained by Ignacio Coupeau.</p></li><li><p>The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are geared to manage users and group in such a Samba-LDAP Domain Controller configuration. - </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896172"></a>Supported LDAP Servers</h4></div></div><div></div></div><p> + </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894325"></a>Supported LDAP Servers</h4></div></div><div></div></div><p> The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and client libraries. The same code should work with Netscape's Directory Server and client SDK. However, there are bound to be compile errors and bugs. These should not be hard to fix. Please submit fixes via <a href="#bugreport" title="Chapter 35. Reporting Bugs">Bug reporting facility</a>. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896197"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894351"></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 sambaAccount objectclass is given here: - </p><ns22:p> -</ns22:p><pre class="programlisting"> -objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' SUP top AUXILIARY - DESC 'Samba Auxilary Account' + <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.3 NAME 'sambaSamAccount' SUP top AUXILIARY + DESC 'Samba Auxiliary Account' MUST ( uid $ rid ) MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ description $ userWorkstations $ primaryGroupID $ domain )) -</pre><ns22:p> -</ns22:p><p> +</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 @@ -3562,55 +3603,55 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' SUP top AUXILIARY <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 sambaAccount object - meant to supplement the UNIX user account information. A sambaAccount is 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 sambaAccount and posixAccount objectclasses in + 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="id2896306"></a>OpenLDAP configuration</h4></div></div><div></div></div><p> - To include support for the sambaAccount object in an OpenLDAP directory + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894458"></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><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>cp samba.schema /etc/openldap/schema/</tt></b> -</pre><ns22:p> -</ns22:p><p> +</pre><p> +</p><p> Next, include the <tt class="filename">samba.schema</tt> file in <tt class="filename">slapd.conf</tt>. - The sambaAccount object contains two attributes which depend upon other schema + 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><ns22:p> -</ns22:p><pre class="programlisting"> + </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 sambaAccount +## 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><ns22:p> -</ns22:p><p> - It is recommended that you maintain some indices on some of the most usefull attributes, - like in the following example, to speed up searches made on sambaAccount objectclasses +</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><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> # Indices to maintain ## required by OpenLDAP index objectclass eq @@ -3632,25 +3673,25 @@ index sambaSID eq index sambaPrimaryGroupSID eq index sambaDomainName eq index default sub -</pre><ns22:p> -</ns22:p><p> +</pre><p> +</p><p> Create the new index by executing: - </p><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> ./sbin/slapindex -f slapd.conf -</pre><ns22:p> -</ns22:p><p> +</pre><p> +</p><p> Remember to restart slapd after making these changes: - </p><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>/etc/init.d/slapd restart</tt></b> -</pre><ns22:p> -</ns22:p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896493"></a>Initialise the LDAP database</h4></div></div><div></div></div><p> +</pre><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894646"></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><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> # Organization for Samba Base dn: dc=plainjoe,dc=org objectclass: dcObject @@ -3678,26 +3719,26 @@ objectclass: top objectclass: organizationalRole objectclass: simpleSecurityObject userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz -</pre><ns22:p> -</ns22:p><p> +</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><ns22:p> -</ns22:p><pre class="screen"> + </p><p> +</p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>slapadd -v -l initldap.dif</tt></b> -</pre><ns22:p> -</ns22:p><p> +</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><ns22:p> - Before Samba can access the LDAP server you need to stoe the LDAP 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: - </ns22:p><pre class="screen"> + </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><ns22:p> - </ns22:p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896622"></a>Configuring Samba</h4></div></div><div></div></div><p> + </pre><p> + </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894774"></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. @@ -3705,8 +3746,8 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 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><ns22:p> -</ns22:p><pre class="programlisting"> + </p><p> +</p><pre class="programlisting"> ## /usr/local/samba/lib/smb.conf [global] security = user @@ -3735,7 +3776,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz ldap delete dn = no # the machine and user suffix added to the base suffix - # wrote WITHOUT quotes. NULL siffixes by default + # wrote WITHOUT quotes. NULL suffixes by default ldap user suffix = ou=People ldap machine suffix = ou=Systems @@ -3747,27 +3788,27 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz ldap suffix = "ou=people,dc=samba,dc=org" # generally the default ldap search filter is ok - # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))" -</pre><ns22:p> -</ns22:p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896800"></a>Accounts and Groups management</h4></div></div><div></div></div><p> - As users accounts are managed thru the sambaAccount objectclass, you should - modify your existing administration tools to deal with sambaAccount attributes. + # ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))" +</pre><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2894972"></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 sambaAccount objectclass, just - like users accounts. However, it's up to you to store thoses accounts + 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=plainjoe,dc=org" to store groups and "ou=People,dc=plainjoe,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration file). </p><p> - In Samba release 3.0, the group management system is based on posix - groups. This means that Samba makes usage of the posixGroup objectclass. + 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="id2896837"></a>Security and sambaAccount</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2895009"></a>Security and sambaSamAccount</h4></div></div><div></div></div><p> There are two important points to remember when discussing the security - of sambaAccount entries in the directory. + 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> @@ -3776,7 +3817,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz on the details of LM/NT password hashes, refer to the <a href="#passdb" title="Chapter 11. Account Information Databases">Account Information Database</a> section of this chapter. </p><p> - To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults + To remedy the first security issue, the <i class="parameter"><tt>ldap ssl</tt></i> <tt class="filename">smb.conf</tt> parameter defaults to require an encrypted session (<i class="parameter"><tt>ldap ssl = on</tt></i>) using the default port of <tt class="constant">636</tt> when contacting the directory server. When using an OpenLDAP server, it @@ -3791,19 +3832,19 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 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><ns22:p> -</ns22:p><pre class="programlisting"> + </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=plainjoe,dc=org" write by * none -</pre><ns22:p> -</ns22:p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896958"></a>LDAP special attributes for sambaAccounts</h4></div></div><div></div></div><p> - The sambaAccount objectclass is composed of the following attributes: - </p><ns22:p> - </ns22:p><div class="table"><a name="id2896974"></a><p class="title"><b>Table 11.1. Attributes in the sambaAccount objectclass (LDAP)</b></p><table summary="Attributes in the sambaAccount objectclass (LDAP)" border="1"><colgroup><col><col></colgroup><tbody><tr><td align="left"><tt class="constant">lmPassword</tt></td><td align="left">the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.</td></tr><tr><td align="left"><tt class="constant">ntPassword</tt></td><td align="left">the NT password hash 16-byte stored as a character - representation of a hexidecimal string.</td></tr><tr><td align="left"><tt class="constant">pwdLastSet</tt></td><td align="left">The integer time in seconds since 1970 when the +</pre><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2895146"></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="id2895163"></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><col></colgroup><tbody><tr><td align="left"><tt class="constant">lmPassword</tt></td><td align="left">the LANMAN password 16-byte hash stored as a character + representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">ntPassword</tt></td><td align="left">the NT password hash 16-byte stored as a character + representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">pwdLastSet</tt></td><td align="left">The integer time in seconds since 1970 when the <tt class="constant">lmPassword</tt> and <tt class="constant">ntPassword</tt> attributes were last set. </td></tr><tr><td align="left"><tt class="constant">acctFlags</tt></td><td align="left">string of 11 characters surrounded by square brackets [] representing account flags such as U (user), W(workstation), X(no password expiration), @@ -3824,14 +3865,14 @@ access to attrs=lmPassword,ntPassword </td></tr><tr><td align="left"><tt class="constant">userWorkstation</tt></td><td align="left">character string value currently unused. </td></tr><tr><td align="left"><tt class="constant">rid</tt></td><td align="left">the integer representation of the user's relative identifier (RID).</td></tr><tr><td align="left"><tt class="constant">primaryGroupID</tt></td><td align="left">the relative identifier (RID) of the primary group - of the user.</td></tr><tr><td align="left"><tt class="constant">domain</tt></td><td align="left">domain the user is part of.</td></tr></tbody></table></div><ns22:p> - </ns22:p><p> + of the user.</td></tr><tr><td align="left"><tt class="constant">domain</tt></td><td align="left">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" 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 sambaAccount entry if the values are non-default values: + are only stored with the sambaSamAccount entry if the values are non-default values: </p><table class="simplelist" border="0" summary="Simple list"><tr><td>smbHome</td></tr><tr><td>scriptPath</td></tr><tr><td>logonPath</td></tr><tr><td>homeDrive</td></tr></table><p> - These attributes are only stored with the sambaAccount entry if + 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 <i class="parameter"><tt>logon home = \\%L\%u</tt></i> was defined in its <tt class="filename">smb.conf</tt> file. When a user named "becky" logons to the domain, @@ -3841,10 +3882,10 @@ access to attrs=lmPassword,ntPassword of the <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="id2897322"></a>Example LDIF Entries for a sambaAccount</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2895512"></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><ns22:p> - </ns22:p><pre class="programlisting"> + </p><p> + </p><pre class="programlisting"> dn: uid=guest2, ou=people,dc=plainjoe,dc=org ntPassword: 878D8014606CDA29677A44EFA1353FC7 pwdMustChange: 2147483647 @@ -3852,26 +3893,26 @@ access to attrs=lmPassword,ntPassword lmPassword: 552902031BEDE9EFAAD3B435B51404EE pwdLastSet: 1010179124 logonTime: 0 - objectClass: sambaAccount + objectClass: sambaSamAccount uid: guest2 kickoffTime: 2147483647 acctFlags: [UX ] logoffTime: 2147483647 rid: 19006 pwdCanChange: 0 - </pre><ns22:p> - </ns22:p><p> - The following is an LDIF entry for using both the sambaAccount and + </pre><p> + </p><p> + The following is an LDIF entry for using both the sambaSamAccount and posixAccount objectclasses: - </p><ns22:p> - </ns22:p><pre class="programlisting"> + </p><p> + </p><pre class="programlisting"> dn: uid=gcarter, ou=people,dc=plainjoe,dc=org logonTime: 0 displayName: Gerald Carter lmPassword: 552902031BEDE9EFAAD3B435B51404EE primaryGroupID: 1201 objectClass: posixAccount - objectClass: sambaAccount + objectClass: sambaSamAccount acctFlags: [UX ] userPassword: {crypt}BpM2ej8Rkzogo uid: gcarter @@ -3887,56 +3928,53 @@ access to attrs=lmPassword,ntPassword pwdCanChange: 0 pwdMustChange: 2147483647 ntPassword: 878D8014606CDA29677A44EFA1353FC7 -</pre><ns22:p> - </ns22:p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2897383"></a>Password synchronisation</h4></div></div><div></div></div><p> +</pre><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2895574"></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 <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 when - the LDAP library supports LDAP_EXOP_X_MODIFY_PASSWD. </p></dd></dl></div><p>More information can be found in the <a href="smb.conf.5.html#LDAPPASSWDSYNC" target="_top">smb.conf</a> manpage. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2897495"></a>ldap trust ids</h4></div></div><div></div></div><p> - LDAP Performance can be improved by using the <b class="command">ldap trust ids</b> parameter. - See the <a href="smb.conf.5.html#LDAPTRUSTIDS" target="_top">smb.conf</a> manpage for details. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897524"></a>MySQL</h3></div></div><div></div></div><p> + about the other fields. This option is only available when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD. </p></dd></dl></div><p>More information can be found in the <a href="smb.conf.5.html#LDAPPASSWDSYNC" target="_top">smb.conf</a> manpage. + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895689"></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="id2897546"></a>Creating the database</h4></div></div><div></div></div><ns22:p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2895709"></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 : - </ns22: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><ns22:p> - </ns22:p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2897609"></a>Configuring</h4></div></div><div></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><ns22:p>Add a the following to the <i class="parameter"><tt>passdb backend</tt></i> variable in your <tt class="filename">smb.conf</tt>: - </ns22:p><pre class="programlisting"> + </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="id2895772"></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 <i class="parameter"><tt>passdb backend</tt></i> variable in your <tt class="filename">smb.conf</tt>: + </p><pre class="programlisting"> passdb backend = [other-plugins] mysql:identifier [other-plugins] - </pre><ns22:p> - </ns22:p><p>The identifier can be any string you like, as long as it doesn't collide with + </pre><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 <i class="parameter"><tt>passdb backend</tt></i>, you also need to use different identifiers! </p><p> - Additional options can be given thru the <tt class="filename">smb.conf</tt> file in the <i class="parameter"><tt>[global]</tt></i> section. - </p><ns22:p> - </ns22:p><div class="table"><a name="id2897685"></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><col></colgroup><thead><tr><th align="left">Field</th><th align="left">Contents</th></tr></thead><tbody><tr><td align="left">identifier:mysql host</td><td align="left">host name, defaults to 'localhost'</td></tr><tr><td align="left">identifier:mysql password</td><td align="left"> </td></tr><tr><td align="left">identifier:mysql user</td><td align="left">defaults to 'samba'</td></tr><tr><td align="left">identifier:mysql database</td><td align="left">defaults to 'samba'</td></tr><tr><td align="left">identifier:mysql port</td><td align="left">defaults to 3306</td></tr><tr><td align="left">identifier:table</td><td align="left">Name of the table containing users</td></tr></tbody></table></div><ns22:p> - </ns22: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 + 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="id2895850"></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><col></colgroup><thead><tr><th align="left">Field</th><th align="left">Contents</th></tr></thead><tbody><tr><td align="left">identifier:mysql host</td><td align="left">host name, defaults to 'localhost'</td></tr><tr><td align="left">identifier:mysql password</td><td align="left"> </td></tr><tr><td align="left">identifier:mysql user</td><td align="left">defaults to 'samba'</td></tr><tr><td align="left">identifier:mysql database</td><td align="left">defaults to 'samba'</td></tr><tr><td align="left">identifier:mysql port</td><td align="left">defaults to 3306</td></tr><tr><td align="left">identifier:table</td><td align="left">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 the <tt class="filename">smb.conf</tt> file - readable only to the user that runs samba. This is considered a security + 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><ns22:p> - </ns22:p><div class="table"><a name="id2897810"></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><col><col></colgroup><thead><tr><th align="left">Field</th><th align="left">Type</th><th align="left">Contents</th></tr></thead><tbody><tr><td align="left">identifier:logon time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:logoff time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:kickoff time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass last set time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass can change time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass must change time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:username column</td><td align="left">varchar(255)</td><td align="left">unix username</td></tr><tr><td align="left">identifier:domain column</td><td align="left">varchar(255)</td><td align="left">NT domain user is part of</td></tr><tr><td align="left">identifier:nt username column</td><td align="left">varchar(255)</td><td align="left">NT username</td></tr><tr><td align="left">identifier:fullname column</td><td align="left">varchar(255)</td><td align="left">Full name of user</td></tr><tr><td align="left">identifier:home dir column</td><td align="left">varchar(255)</td><td align="left">Unix homedir path</td></tr><tr><td align="left">identifier:dir drive column</td><td align="left">varchar(2)</td><td align="left">Directory drive path (eg: 'H:')</td></tr><tr><td align="left">identifier:logon script column</td><td align="left">varchar(255)</td><td align="left">Batch file to run on client side when logging on</td></tr><tr><td align="left">identifier:profile path column</td><td align="left">varchar(255)</td><td align="left">Path of profile</td></tr><tr><td align="left">identifier:acct desc column</td><td align="left">varchar(255)</td><td align="left">Some ASCII NT user data</td></tr><tr><td align="left">identifier:workstations column</td><td align="left">varchar(255)</td><td align="left">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="left">identifier:unknown string column</td><td align="left">varchar(255)</td><td align="left">unknown string</td></tr><tr><td align="left">identifier:munged dial column</td><td align="left">varchar(255)</td><td align="left">?</td></tr><tr><td align="left">identifier:user sid column</td><td align="left">varchar(255)</td><td align="left">NT user SID</td></tr><tr><td align="left">identifier:group sid column</td><td align="left">varchar(255)</td><td align="left">NT group ID</td></tr><tr><td align="left">identifier:lanman pass column</td><td align="left">varchar(255)</td><td align="left">encrypted lanman password</td></tr><tr><td align="left">identifier:nt pass column</td><td align="left">varchar(255)</td><td align="left">encrypted nt passwd</td></tr><tr><td align="left">identifier:plain pass column</td><td align="left">varchar(255)</td><td align="left">plaintext password</td></tr><tr><td align="left">identifier:acct control column</td><td align="left">int(9)</td><td align="left">nt user data</td></tr><tr><td align="left">identifier:unknown 3 column</td><td align="left">int(9)</td><td align="left">unknown</td></tr><tr><td align="left">identifier:logon divs column</td><td align="left">int(9)</td><td align="left">?</td></tr><tr><td align="left">identifier:hours len column</td><td align="left">int(9)</td><td align="left">?</td></tr><tr><td align="left">identifier:unknown 5 column</td><td align="left">int(9)</td><td align="left">unknown</td></tr><tr><td align="left">identifier:unknown 6 column</td><td align="left">int(9)</td><td align="left">unknown</td></tr></tbody></table></div><ns22:p> - </ns22:p><p> + </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="id2895975"></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><col><col></colgroup><thead><tr><th align="left">Field</th><th align="left">Type</th><th align="left">Contents</th></tr></thead><tbody><tr><td align="left">identifier:logon time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:logoff time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:kickoff time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass last set time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass can change time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:pass must change time column</td><td align="left">int(9)</td><td align="left"> </td></tr><tr><td align="left">identifier:username column</td><td align="left">varchar(255)</td><td align="left">unix username</td></tr><tr><td align="left">identifier:domain column</td><td align="left">varchar(255)</td><td align="left">NT domain user is part of</td></tr><tr><td align="left">identifier:nt username column</td><td align="left">varchar(255)</td><td align="left">NT username</td></tr><tr><td align="left">identifier:fullname column</td><td align="left">varchar(255)</td><td align="left">Full name of user</td></tr><tr><td align="left">identifier:home dir column</td><td align="left">varchar(255)</td><td align="left">Unix homedir path</td></tr><tr><td align="left">identifier:dir drive column</td><td align="left">varchar(2)</td><td align="left">Directory drive path (eg: 'H:')</td></tr><tr><td align="left">identifier:logon script column</td><td align="left">varchar(255)</td><td align="left">Batch file to run on client side when logging on</td></tr><tr><td align="left">identifier:profile path column</td><td align="left">varchar(255)</td><td align="left">Path of profile</td></tr><tr><td align="left">identifier:acct desc column</td><td align="left">varchar(255)</td><td align="left">Some ASCII NT user data</td></tr><tr><td align="left">identifier:workstations column</td><td align="left">varchar(255)</td><td align="left">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="left">identifier:unknown string column</td><td align="left">varchar(255)</td><td align="left">unknown string</td></tr><tr><td align="left">identifier:munged dial column</td><td align="left">varchar(255)</td><td align="left">?</td></tr><tr><td align="left">identifier:user sid column</td><td align="left">varchar(255)</td><td align="left">NT user SID</td></tr><tr><td align="left">identifier:group sid column</td><td align="left">varchar(255)</td><td align="left">NT group ID</td></tr><tr><td align="left">identifier:lanman pass column</td><td align="left">varchar(255)</td><td align="left">encrypted lanman password</td></tr><tr><td align="left">identifier:nt pass column</td><td align="left">varchar(255)</td><td align="left">encrypted nt passwd</td></tr><tr><td align="left">identifier:plain pass column</td><td align="left">varchar(255)</td><td align="left">plaintext password</td></tr><tr><td align="left">identifier:acct control column</td><td align="left">int(9)</td><td align="left">nt user data</td></tr><tr><td align="left">identifier:unknown 3 column</td><td align="left">int(9)</td><td align="left">unknown</td></tr><tr><td align="left">identifier:logon divs column</td><td align="left">int(9)</td><td align="left">?</td></tr><tr><td align="left">identifier:hours len column</td><td align="left">int(9)</td><td align="left">?</td></tr><tr><td align="left">identifier:unknown 5 column</td><td align="left">int(9)</td><td align="left">unknown</td></tr><tr><td align="left">identifier:unknown 6 column</td><td align="left">int(9)</td><td align="left">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="id2898192"></a>Using plaintext passwords or encrypted password</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896354"></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 @@ -3946,7 +3984,7 @@ access to attrs=lmPassword,ntPassword </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="id2898222"></a>Getting non-column data from the table</h4></div></div><div></div></div><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2896385"></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 : @@ -3955,42 +3993,42 @@ access to attrs=lmPassword,ntPassword 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> + <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="id2898328"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898335"></a>Users can not logon - Users not in Samba SAM</h3></div></div><div></div></div><p> - People forget to put their users in their backend and then complain samba won't authorize them. - </p></div><div xmlns:ns23="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898350"></a>Users are being added to the wrong backend database</h3></div></div><div></div></div><p> - A few complaints have been recieved from users that just moved to samba-3. The following + <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="id2896493"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896501"></a>Users can not logon - Users not in Samba SAM</h3></div></div><div></div></div><p> + People forget to put their users in their backend and then complain Samba won't authorize them. + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896516"></a>Users are being added to the 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><ns23:p> - </ns23:p><pre class="programlisting"> + </p><p> + </p><pre class="programlisting"> [globals] ... passdb backend = smbpasswd, tdbsam, guest ... - </pre><ns23:p> - </ns23:p><p> + </pre><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><ns23:p> - </ns23:p><pre class="programlisting"> + </p><p> + </p><pre class="programlisting"> [globals] ... passdb backend = tdbsam, smbpasswd, guest ... - </pre><ns23:p> - </ns23:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898409"></a>auth methods does not work</h3></div></div><div></div></div><p> + </pre><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896576"></a>auth methods does not work</h3></div></div><div></div></div><p> If you explicitly set an 'auth methods' parameter, guest must be specified as the first entry on the line. Eg: <i class="parameter"><tt>auth methods = guest sam</tt></i>. </p><p> This is the exact opposite of the requirement for the <i class="parameter"><tt>passdb backed</tt></i> option, where it must be the <span class="emphasis"><em>LAST</em></span> parameter on the line. - </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter 12. Mapping MS Windows and Unix Groups</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jean François</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2898582">Features and Benefits</a></dt><dt><a href="#id2898682">Discussion</a></dt><dd><dl><dt><a href="#id2898871">Example Configuration</a></dt></dl></dd><dt><a href="#id2898936">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2898950">Sample smb.conf add group script</a></dt><dt><a href="#id2899017">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2899091">Common Errors</a></dt><dd><dl><dt><a href="#id2899107">Adding Groups Fails</a></dt><dt><a href="#id2899167">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="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="#id2903953">Features and Benefits</a></dt><dt><a href="#id2904055">Discussion</a></dt><dd><dl><dt><a href="#id2904246">Example Configuration</a></dt></dl></dd><dt><a href="#id2904310">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2904325">Sample smb.conf add group script</a></dt><dt><a href="#id2904393">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2904485">Common Errors</a></dt><dd><dl><dt><a href="#id2904501">Adding Groups Fails</a></dt><dt><a href="#id2904562">Adding MS Windows Groups to MS Windows Groups Fails</a></dt></dl></dd></dl></div><p> Starting with Samba-3, new group mapping functionality is available to create associations between Windows group SIDs and UNIX groups. The <i class="parameter"><tt>groupmap</tt></i> subcommand included with the <span class="application">net</span> tool can be used to manage these associations. @@ -4000,12 +4038,12 @@ access to attrs=lmPassword,ntPassword 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="id2898582"></a>Features and Benefits</h2></div></div><div></div></div><p> + </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2903953"></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><p> Group accounts can be managed using the MS Windows NT4 or MS Windows 200x MMC tools - so long as appropriate interface scripts have been provided to <tt class="filename">smb.conf</tt> + so long as appropriate interface scripts have been provided to <tt class="filename">smb.conf</tt>. </p><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>, @@ -4018,43 +4056,43 @@ access to attrs=lmPassword,ntPassword 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. + 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 xmlns:ns26="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2898682"></a>Discussion</h2></div></div><div></div></div><p> + </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904055"></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 to that group privileges necessary privilidges to perform essential system tasks. - eg: Ability to change the date and time or to kill any process (or close too) running on the + 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><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 Adminis" group of the + 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? + 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 xmlns:ns24=""><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 + </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><ns24:p> - </ns24:p></li><li xmlns:ns25=""><p> + </pre><p> + </p></li><li><p> Map this domadm group to the "Domain Admins" group by running the command: - </p><ns25:p> - </ns25:p><pre class="screen"> + </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><ns25:p> - </ns25:p><p> + </pre><p> + </p><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> @@ -4064,36 +4102,36 @@ access to attrs=lmPassword,ntPassword 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><ns26:p> - </ns26:p><pre class="screen"> + </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><ns26:p> - </ns26:p><p> - Be aware that the RID parmeter is a unsigned 32 bit integer that should + </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 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="id2898871"></a>Example Configuration</h3></div></div><div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904246"></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><ns26:p> - </ns26:p><pre class="screen"> + </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><ns26:p> - </ns26:p><p> + </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="id2898936"></a>Configuration Scripts</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904310"></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 xmlns:ns27="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898950"></a>Sample <tt class="filename">smb.conf</tt> add group script</h3></div></div><div></div></div><p> - A script to great complying group names for use by the samba group interfaces: - </p><ns27:p> -</ns27:p><div class="example"><a name="id2898973"></a><p class="title"><b>Example 12.1. smbgrpadd.sh</b></p><pre class="programlisting"> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904325"></a>Sample <tt class="filename">smb.conf</tt> add group script</h3></div></div><div></div></div><p> + A script to great complying group names for use by the Samba group interfaces: + </p><p> +</p><div class="example"><a name="id2904348"></a><p class="title"><b>Example 12.1. smbgrpadd.sh</b></p><pre class="programlisting"> #!/bin/bash @@ -4103,22 +4141,23 @@ 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 -cat /etc/group | sed s/smbtmpgrp00/$1/g > /etc/group +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><ns27:p> -</ns27:p><ns27:p> +</pre></div><p> +</p><p> The <tt class="filename">smb.conf</tt> entry for the above script would look like: - </ns27:p><pre class="programlisting"> + </p><pre class="programlisting"> add group script = /path_to_tool/smbgrpadd.sh %g - </pre><ns27:p> - </ns27:p></div><div xmlns:ns28="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899017"></a>Script to configure Group Mapping</h3></div></div><div></div></div><p> + </pre><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904393"></a>Script to configure Group Mapping</h3></div></div><div></div></div><p> In our example we have created a Unix/Linux group called <i class="parameter"><tt>ntadmin</tt></i>. Our script will create the additional groups <i class="parameter"><tt>Engineers, Marketoids, Gnomes</tt></i>: - </p><ns28:p> -</ns28:p><pre class="programlisting"> + </p><p> +</p><pre class="programlisting"> #!/bin/bash net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin @@ -4141,21 +4180,21 @@ net groupmap modify ntgroup="Power Users" unixgroup=sys #net groupmap add ntgroup="Engineers" unixgroup=Engineers type=d #net groupmap add ntgroup="Marketoids" unixgroup=Marketoids type=d #net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d -</pre><ns28:p> -</ns28:p><p> - Of course it is expected that the admininstrator will modify this to suit local needs. +</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="id2899091"></a>Common Errors</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2904485"></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="id2899107"></a>Adding Groups Fails</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904501"></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 <i class="parameter"><tt>add group script</tt></i> in + by the Samba interface script for the <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 acocunt + 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 @@ -4164,15 +4203,15 @@ manually before putting them into active service. third option is to manually create a Unix/Linux group account that can substitute for the MS Windows group name, then use the procedure listed above to map that group to the MS Windows group. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899167"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904562"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><p> Samba-3 does NOT support nested groups from the MS Windows control environment. - </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter 13. File, Directory and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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><p class="pubdate">May 10, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2902353">Features and Benefits</a></dt><dt><a href="#id2902478">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902496">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2899413">Managing Directories</a></dt><dt><a href="#id2899508">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2899915">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2899943">User and Group Based Controls</a></dt><dt><a href="#id2900215">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2900461">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905044">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905115">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905414">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905422">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905460">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905539">Viewing file ownership</a></dt><dt><a href="#id2905661">Viewing File or Directory Permissions</a></dt><dt><a href="#id2905889">Modifying file or directory permissions</a></dt><dt><a href="#id2906041">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2906370">Interaction with the standard Samba file attribute - mapping</a></dt></dl></dd><dt><a href="#id2906446">Common Errors</a></dt><dd><dl><dt><a href="#id2906460">Users can not write to a public share</a></dt><dt><a href="#id2906838">I have set force user and samba still makes root the owner of all the files + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter 13. File, Directory and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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><p class="pubdate">May 10, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2902775">Features and Benefits</a></dt><dt><a href="#id2902812">File System Access Controls</a></dt><dd><dl><dt><a href="#id2902830">MS Windows NTFS Comparison with Unix File Systems</a></dt><dt><a href="#id2903087">Managing Directories</a></dt><dt><a href="#id2903183">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2903398">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2904578">User and Group Based Controls</a></dt><dt><a href="#id2904850">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2905095">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2905311">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2905383">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2905682">MS Windows Access Control Lists and Unix Interoperability</a></dt><dd><dl><dt><a href="#id2905690">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2905728">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2905807">Viewing file ownership</a></dt><dt><a href="#id2905929">Viewing File or Directory Permissions</a></dt><dt><a href="#id2906157">Modifying file or directory permissions</a></dt><dt><a href="#id2906309">Interaction with the standard Samba create mask + parameters</a></dt><dt><a href="#id2906639">Interaction with the standard Samba file attribute + mapping</a></dt></dl></dd><dt><a href="#id2906714">Common Errors</a></dt><dd><dl><dt><a href="#id2906729">Users can not write to a public share</a></dt><dt><a href="#id2907109">I have set force user and Samba still makes root the owner of all the files I touch!</a></dt></dl></dd></dl></div><p> Advanced MS Windows users are frequently perplexed when file, directory and share manipulation of resources shared via Samba do not behave in the manner they might expect. MS Windows network -adminstrators are often confused regarding network access controls and what is the best way to +administrators are often confused regarding network access controls and what is the best way to provide users with the type of access they need while protecting resources from the consequences of untoward access capabilities. </p><p> @@ -4198,9 +4237,9 @@ This is an opportune point to mention that it should be borne in mind that Samba provide a means of interoperability and interchange of data between two operating environments that are quite different. It was never the intent to make Unix/Linux like MS Windows NT. Instead the purpose was an is to provide a sufficient level of exchange of data between the two environments. -What is available today extends well beyond early plans and expections, yet the gap continues to +What is available today extends well beyond early plans and expectations, yet the gap continues to shrink. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902353"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902775"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba offers a lot of flexibility in file system access management. These are the key access control facilities present in Samba today: </p><div class="itemizedlist"><p class="title"><b>Samba Access Control Facilities</b></p><ul type="disc"><li><p> @@ -4237,15 +4276,15 @@ shrink. operating system supports them. If not, then this option will not be available to you. Current Unix technology platforms have native support for POSIX ACLs. There are patches for the Linux kernel that provide - this also. Sadly, few Linux paltforms ship today with native ACLs and + this also. Sadly, few Linux platforms ship today with native ACLs and Extended Attributes enabled. This chapter has pertinent information for users of platforms that support them. - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902478"></a>File System Access Controls</h2></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902812"></a>File System Access Controls</h2></div></div><div></div></div><p> Perhaps the most important recognition to be made is the simple fact that MS Windows NT4 / 200x / XP implement a totally divergent file system technology from what is provided in the Unix operating system environment. Firstly we should consider what the most significant differences are, then we shall look at how Samba helps to bridge the differences. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902496"></a>MS Windows NTFS Comparison with Unix File Systems</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902830"></a>MS Windows NTFS Comparison with Unix File Systems</h3></div></div><div></div></div><p> Samba operates on top of the Unix file system. This means it is subject to Unix file system conventions and permissions. It also means that if the MS Windows networking environment requires file system behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating @@ -4253,7 +4292,7 @@ at how Samba helps to bridge the differences. </p><p> It is good news that Samba does this to a very large extent and on top of that provides a high degree of optional configuration to over-ride the default behaviour. We will look at some of these over-rides, - but for the greater part we will stay withing the bounds of default behaviour. Those wishing to explore + but for the greater part we will stay within the bounds of default behaviour. Those wishing to explore to depths of control ability should review the <tt class="filename">smb.conf</tt> man page. </p><div class="variablelist"><p class="title"><b>File System Feature Comparison</b></p><dl><dt><span class="term">Name Space</span></dt><dd><p> MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, Unix file names @@ -4304,24 +4343,24 @@ at how Samba helps to bridge the differences. Symbolic links are files in Unix that contain the actual location of the data (file OR directory). An operation (like read or write) will operate directly on the file referenced. Symbolic links are also referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows - one physical file to be known simulataneously by more than one file name. + one physical file to be known simultaneously by more than one file name. </p></dd></dl></div><p> There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort in the process of becoming familiar with Unix/Linux. These are best left for a text that is dedicated to the purpose of Unix/Linux training/education. - </p></div><div xmlns:ns29="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899413"></a>Managing Directories</h3></div></div><div></div></div><ns29:p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903087"></a>Managing Directories</h3></div></div><div></div></div><p> There are three basic operations for managing directories, <b class="command">create, delete, rename</b>. - </ns29:p><div class="table"><a name="id2899431"></a><p class="title"><b>Table 13.1. Managing directories with unix and windows</b></p><table summary="Managing directories with unix and windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">Unix Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div><ns29:p> - </ns29:p></div><div xmlns:ns30="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899508"></a>File and Directory Access Control</h3></div></div><div></div></div><p> + </p><div class="table"><a name="id2903107"></a><p class="title"><b>Table 13.1. Managing directories with unix and windows</b></p><table summary="Managing directories with unix and windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">Unix Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903183"></a>File and Directory Access Control</h3></div></div><div></div></div><p> The network administrator is strongly advised to read foundational training manuals and reference materials regarding file and directory permissions maintenance. Much can be achieved with the basic Unix permissions without having to resort to more complex facilities like POSIX Access Control Lists (ACLs) or Extended Attributes (EAs). - </p><ns30:p> - Unix/Linux file and directory access permissions invloves setting three (3) primary sets of data and one (1) control set. + </p><p> + Unix/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. A Unix file listing looks as follows:- - </ns30:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">jht@frodo:~/stuff> </tt><b class="userinput"><tt>ls -la</tt></b> total 632 drwxr-xr-x 13 jht users 816 2003-05-12 22:56 . @@ -4344,13 +4383,13 @@ at how Samba helps to bridge the differences. -rw-rw-rw- 1 jht users 41105 2003-05-12 22:32 mydata06.lst -rwxrwxrwx 1 jht users 19312 2003-05-12 22:32 mydata07.lst <tt class="prompt">jht@frodo:~/stuff></tt> - </pre><ns30:p> - </ns30:p><p> + </pre><p> + </p><p> The columns above represent (from left to right): permissions, no blocks used, owner, group, size (bytes), access date, access time, file name. - </p><ns30:p> + </p><p> The permissions field is made up of: - </ns30:p><pre class="programlisting"> + </p><pre class="programlisting"> <i><span class="comment"> JRV: Put this into a diagram of some sort</span></i> [ type ] [ users ] [ group ] [ others ] [File, Directory Permissions] [ d | l ] [ r w x ] [ r w x ] [ r w x ] @@ -4366,20 +4405,20 @@ at how Samba helps to bridge the differences. | | |-----------------------------> Can Read, Read files | |-----------------------------------> Is a symbolic Link |---------------------------------------> Is a directory - </pre><ns30:p> - </ns30:p><ns30:p> + </pre><p> + </p><p> Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character. - </ns30:p><div class="example"><a name="id2899836"></a><p class="title"><b>Example 13.1. Example File</b></p><pre class="programlisting"> + </p><div class="example"><a name="id2903320"></a><p class="title"><b>Example 13.1. Example File</b></p><pre class="programlisting"> -rwxr-x--- Means: The owner (user) can read, write, execute the group can read and execute everyone else can NOT do anything with it - </pre></div><ns30:p> + </pre></div><p> - </ns30:p><p> - Additional posibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = Unix Domain Socket. </p><p> - The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),r + Additional possibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = Unix Domain Socket. + </p><p> + The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x), execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), sticky (t). </p><p> @@ -4396,10 +4435,10 @@ at how Samba helps to bridge the differences. the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the directory but can NOT create new files. NOTE: If files in the directory are set to be readable and writable for the group, then group members will be able to write to (or delete) them. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2899915"></a>Share Definition Access Controls</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2903398"></a>Share Definition Access Controls</h2></div></div><div></div></div><p> The following parameters in the <tt class="filename">smb.conf</tt> file sections that define a share control or affect access controls. Before using any of the following options please refer to the man page for <tt class="filename">smb.conf</tt>. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899943"></a>User and Group Based Controls</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904578"></a>User and Group Based Controls</h3></div></div><div></div></div><p> User and group based controls can prove very useful. In some situations it is distinctly desirable to affect all file system operations as if a single user is doing this, the use of the <i class="parameter"><tt>force user</tt></i> and <i class="parameter"><tt>force group</tt></i> behaviour will achieve this. In other situations it may be necessary to affect a @@ -4411,7 +4450,7 @@ Before using any of the following options please refer to the man page for <tt c controlling access. Remember, that when you leave the scene someone else will need to provide assistance and if that person finds too great a mess, or if they do not understand what you have done then there is risk of Samba being removed and an alternative solution being adopted. - </p><div class="table"><a name="id2900001"></a><p class="title"><b>Table 13.2. User and Group Based Controls</b></p><table summary="User and Group Based Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>admin users</td><td><p> + </p><div class="table"><a name="id2904638"></a><p class="title"><b>Table 13.2. User and Group Based Controls</b></p><table summary="User and Group Based Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>admin users</td><td><p> List of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). Any user in this list will be able to do anything they like on the share, @@ -4438,12 +4477,12 @@ Before using any of the following options please refer to the man page for <tt c List of users that should be allowed to login to this service. </p></td></tr><tr><td>write list</td><td><p> List of users that are given read-write access to a service. - </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900215"></a>File and Directory Permissions Based Controls</h3></div></div><div></div></div><p> + </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904850"></a>File and Directory Permissions Based Controls</h3></div></div><div></div></div><p> The following file and directory permission based controls, if misused, can result in considerable difficulty to diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually - re-instroduce them in a controlled fashion. - </p><div class="table"><a name="id2900234"></a><p class="title"><b>Table 13.3. File and Directory Permission Based Controls</b></p><table summary="File and Directory Permission Based Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>create mask</td><td><p> + re-introduce them in a controlled fashion. + </p><div class="table"><a name="id2904871"></a><p class="title"><b>Table 13.3. File and Directory Permission Based Controls</b></p><table summary="File and Directory Permission Based Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>create mask</td><td><p> Refer to the <tt class="filename">smb.conf</tt> man page. </p></td></tr><tr><td>directory mask</td><td><p> The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories. @@ -4459,17 +4498,17 @@ Before using any of the following options please refer to the man page for <tt c </p></td></tr><tr><td>force security mode</td><td><p> Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions. </p></td></tr><tr><td>hide unreadable</td><td><p> - Prevents clients from seeing the existance of files that cannot be read. + Prevents clients from seeing the existence of files that cannot be read. </p></td></tr><tr><td>hide unwriteable files</td><td><p> - Prevents clients from seeing the existance of files that cannot be written to. Unwriteable directories are shown as usual. + Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. </p></td></tr><tr><td>nt acl support</td><td><p> This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists. </p></td></tr><tr><td>security mask</td><td><p> Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file. - </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900461"></a>Miscellaneous Controls</h3></div></div><div></div></div><p> + </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905095"></a>Miscellaneous Controls</h3></div></div><div></div></div><p> The following are documented because of the prevalence of administrators creating inadvertant barriers to file access by not understanding the full implications of <tt class="filename">smb.conf</tt> file settings. - </p><div class="table"><a name="id2900482"></a><p class="title"><b>Table 13.4. Other Controls</b></p><table summary="Other Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>case sensitive, default case, short preserve case</td><td><p> + </p><div class="table"><a name="id2905118"></a><p class="title"><b>Table 13.4. Other Controls</b></p><table summary="Other Controls" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td>case sensitive, default case, short preserve case</td><td><p> This means that all file name lookup will be done in a case sensitive manner. Files will be created with the precise filename Samba received from the MS Windows client. </p></td></tr><tr><td>csc policy</td><td><p> @@ -4490,9 +4529,9 @@ Before using any of the following options please refer to the man page for <tt c If this parameter is yes, then users of a service may not create or modify files in the service's directory. </p></td></tr><tr><td>veto files</td><td><p> List of files and directories that are neither visible nor accessible. - </p></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905044"></a>Access Controls on Shares</h2></div></div><div></div></div><p> + </p></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905311"></a>Access Controls on Shares</h2></div></div><div></div></div><p> This section deals with how to configure Samba per share access control restrictions. - By default samba sets no restrictions on the share itself. Restrictions on the share itself + By default, Samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can connect to a share. In the absence of specific restrictions the default setting is to allow the global user <tt class="constant">Everyone</tt> Full Control (ie: Full control, Change and Read). @@ -4504,12 +4543,12 @@ Before using any of the following options please refer to the man page for <tt c </p><p> Samba stores the per share access control settings in a file called <tt class="filename">share_info.tdb</tt>. The location of this file on your system will depend on how samba was compiled. The default location - for samba's tdb files is under <tt class="filename">/usr/local/samba/var</tt>. If the <tt class="filename">tdbdump</tt> - utility has been compiled and installed on your system then you can examine the contents of this file + for Samba's tdb files is under <tt class="filename">/usr/local/samba/var</tt>. If the <tt class="filename">tdbdump</tt> + utility has been compiled and installed on your system, then you can examine the contents of this file by: <b class="userinput"><tt>tdbdump share_info.tdb</tt></b>. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905115"></a>Share Permissions Management</h3></div></div><div></div></div><p> - The best tool for the task is platform dependant. Choose the best tool for your environmemt. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905128"></a>Windows NT4 Workstation/Server</h4></div></div><div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905383"></a>Share Permissions Management</h3></div></div><div></div></div><p> + The best tool for the task is platform dependant. Choose the best tool for your environment. + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905397"></a>Windows NT4 Workstation/Server</h4></div></div><div></div></div><p> The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below. @@ -4519,7 +4558,7 @@ Before using any of the following options please refer to the man page for <tt c </p></li><li><p> Now click on the share that you wish to manage, then click on the <span class="guilabel">Properties</span> tab, next click on the <span class="guilabel">Permissions</span> tab. Now you can add or change access control settings as you wish. - </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905210"></a>Windows 200x/XP</h4></div></div><div></div></div><p> + </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905479"></a>Windows 200x/XP</h4></div></div><div></div></div><p> On <span class="application">MS Windows NT4/200x/XP</span> system access control lists on the share itself are set using native tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, then select <span class="guimenuitem">Sharing</span>, then click on <span class="guilabel">Permissions</span>. The default @@ -4532,7 +4571,7 @@ Before using any of the following options please refer to the man page for <tt c After launching the MMC with the Computer Management snap-in, click on the menu item <span class="guimenuitem">Action</span>, select <span class="guilabel">Connect to another computer</span>. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered. + If you where already logged in with administrative privilege this step is not offered. </p></li><li><p> If the Samba server is not shown in the <span class="guilabel">Select Computer</span> box, then type in the name of the target Samba server in the field <span class="guilabel">Name:</span>. Now click on the <span class="guibutton">[+]</span> next to @@ -4548,7 +4587,7 @@ Before using any of the following options please refer to the man page for <tt c then effectively no user will be able to access the share. This is a result of what is known as ACL precedence. ie: Everyone with <span class="emphasis"><em>no access</em></span> means that MaryK who is part of the group <tt class="constant">Everyone</tt> will have no access even if this user is given explicit full control access. - </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905414"></a>MS Windows Access Control Lists and Unix Interoperability</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905422"></a>Managing UNIX permissions Using NT Security Dialogs</h3></div></div><div></div></div><p>Windows NT clients can use their native security settings + </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905682"></a>MS Windows Access Control Lists and Unix Interoperability</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905690"></a>Managing UNIX permissions Using NT Security Dialogs</h3></div></div><div></div></div><p>Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions.</p><p>Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba @@ -4559,7 +4598,7 @@ Before using any of the following options please refer to the man page for <tt c the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905460"></a>Viewing File Security on a Samba Share</h3></div></div><div></div></div><p>From an NT4/2000/XP client, single-click with the right + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905728"></a>Viewing File Security on a Samba Share</h3></div></div><div></div></div><p>From an NT4/2000/XP client, single-click with the right mouse button on any file or directory in a Samba mounted drive letter or UNC path. When the menu pops-up, click on the <span class="guilabel">Properties</span> entry at the bottom of @@ -4575,7 +4614,7 @@ Before using any of the following options please refer to the man page for <tt c user is logged on as the NT Administrator. This dialog is non-functional with a Samba share at this time, as the only useful button, the <span class="guibutton">Add</span> button will not currently - allow a list of users to be seen.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905539"></a>Viewing file ownership</h3></div></div><div></div></div><p>Clicking on the <span class="guibutton">Ownership</span> button + allow a list of users to be seen.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905807"></a>Viewing file ownership</h3></div></div><div></div></div><p>Clicking on the <span class="guibutton">Ownership</span> button brings up a dialog box telling you who owns the given file. The owner name will be of the form :</p><p><b class="command">"SERVER\user (Long name)"</b></p><p>Where <i class="replaceable"><tt>SERVER</tt></i> is the NetBIOS name of the Samba server, <i class="replaceable"><tt>user</tt></i> is the user name of @@ -4598,7 +4637,7 @@ Before using any of the following options please refer to the man page for <tt c files on both a local NTFS filesystem or remote mounted NTFS or Samba drive. This is available as part of the <span class="application">Seclib </span> NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905661"></a>Viewing File or Directory Permissions</h3></div></div><div></div></div><p>The third button is the <span class="guibutton">Permissions</span> + the Samba Team, available from the main Samba ftp site.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905929"></a>Viewing File or Directory Permissions</h3></div></div><div></div></div><p>The third button is the <span class="guibutton">Permissions</span> button. Clicking on this brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed in the form :</p><p><b class="command">"<i class="replaceable"><tt>SERVER</tt></i>\ @@ -4612,9 +4651,9 @@ Before using any of the following options please refer to the man page for <tt c be shown as the NT user <tt class="constant">"Everyone"</tt> and the permissions will be shown as NT "Full Control".</p><p>The permissions field is displayed differently for files and directories, so I'll describe the way file permissions - are displayed first.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905752"></a>File Permissions</h4></div></div><div></div></div><p>The standard UNIX user/group/world triple and + are displayed first.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2906021"></a>File Permissions</h4></div></div><div></div></div><p>The standard UNIX user/group/world triplet and the corresponding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL + triplets are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into the global NT group <tt class="constant">Everyone</tt>, followed @@ -4634,7 +4673,7 @@ Before using any of the following options please refer to the man page for <tt c no permissions as having the NT <b class="command">"O"</b> bit set. This was chosen of course to make it look like a zero, meaning zero permissions. More details on the decision behind this will - be given below.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2905844"></a>Directory Permissions</h4></div></div><div></div></div><p>Directories on an NT NTFS file system have two + be given below.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2906112"></a>Directory Permissions</h4></div></div><div></div></div><p>Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed in the first set of parentheses in the normal <tt class="constant">"RW"</tt> @@ -4645,7 +4684,7 @@ Before using any of the following options please refer to the man page for <tt c inherited</tt> permissions that any file created within this directory would inherit.</p><p>Samba synthesises these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905889"></a>Modifying file or directory permissions</h3></div></div><div></div></div><p>Modifying file and directory permissions is as simple + created by Samba on this share would receive.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906157"></a>Modifying file or directory permissions</h3></div></div><div></div></div><p>Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and clicking the <span class="guibutton">OK</span> button. However, there are limitations that a user needs to be aware of, and also interactions @@ -4659,14 +4698,14 @@ Before using any of the following options please refer to the man page for <tt c and did not execute</span>). This means that you can only manipulate the current user/group/world permissions listed in the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.</p><p>If a permission triple (either user, group, or world) + only permissions that UNIX actually has.</p><p>If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT dialog box, then when the <span class="guibutton">OK</span> button is pressed it will be applied as "no permissions" on the UNIX side. If you then view the permissions again the "no permissions" entry will appear as the NT <b class="command">"O"</b> flag, as described above. This allows you to add permissions back to a file or directory once - you have removed them from a triple component.</p><p>As UNIX supports only the "r", "w" and "x" bits of + you have removed them from a triplet component.</p><p>As UNIX supports only the "r", "w" and "x" bits of an NT ACL then if other NT security attributes such as "Delete access" are selected then they will be ignored when applied on the Samba server.</p><p>When setting permissions on a directory the second @@ -4679,16 +4718,16 @@ Before using any of the following options please refer to the man page for <tt c component and click the <span class="guibutton">Remove</span> button, or set the component to only have the special <tt class="constant">Take Ownership</tt> permission (displayed as <b class="command">"O" - </b>) highlighted.</p></div><div xmlns:ns31="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906041"></a>Interaction with the standard Samba create mask - parameters</h3></div></div><div></div></div><ns31:p>There are four parameters + </b>) highlighted.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906309"></a>Interaction with the standard Samba create mask + parameters</h3></div></div><div></div></div><p>There are four parameters to control interaction with the standard Samba create mask parameters. These are : - </ns31:p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode</tt></i></td></tr></table><ns31:p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode</tt></i></td></tr></table><p> - </ns31:p><p>Once a user clicks <span class="guibutton">OK</span> to apply the + </p><p>Once a user clicks <span class="guibutton">OK</span> to apply the permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a + r/w/x triplet set, and then will check the changed permissions for a file against the bits set in the <a href="smb.conf.5.html#SECURITYMASK" target="_top"> <i class="parameter"><tt>security mask</tt></i></a> parameter. Any bits that were changed that are not set to '1' in this parameter are left alone @@ -4726,7 +4765,7 @@ Before using any of the following options please refer to the man page for <tt c in modifying the permission bits on their files and directories and doesn't force any particular bits to be set 'on', then set the following parameters in the <tt class="filename">smb.conf</tt> file in that share specific section : - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode = 0</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode = 0</tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906370"></a>Interaction with the standard Samba file attribute + </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode = 0</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode = 0</tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906639"></a>Interaction with the standard Samba file attribute mapping</h3></div></div><div></div></div><p>Samba maps some of the DOS attribute bits (such as "read only") into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security @@ -4743,13 +4782,13 @@ Before using any of the following options please refer to the man page for <tt c permissions and clicking <span class="guibutton">OK</span> to get back to the attributes dialog you should always hit <span class="guibutton">Cancel</span> rather than <span class="guibutton">OK</span> to ensure that your changes - are not overridden.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2906446"></a>Common Errors</h2></div></div><div></div></div><p> + are not overridden.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2906714"></a>Common Errors</h2></div></div><div></div></div><p> File, Directory and Share access problems are very common on the mailing list. The following are examples taken from the mailing list in recent times. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906460"></a>Users can not write to a public share</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906729"></a>Users can not write to a public share</h3></div></div><div></div></div><p> “<span class="quote"> We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root), - and theres a public share, on which everyone needs to have permission to create / modify files, but only + and there's a public share, on which everyone needs to have permission to create / modify files, but only root can change the file, no one else can. We need to constantly go to server to <b class="userinput"><tt>chgrp -R users *</tt></b> and <b class="userinput"><tt>chown -R nobody *</tt></b> to allow others users to change the file. </span>” @@ -4757,78 +4796,78 @@ are examples taken from the mailing list in recent times. There are many ways to solve this problem, here are a few hints: </p><div class="procedure"><p class="title"><b>Procedure 13.3. Example Solution:</b></p><ol type="1"><li><p> Go to the top of the directory that is shared - </p></li><li xmlns:ns32=""><ns32:p> + </p></li><li><p> Set the ownership to what ever public owner and group you want - </ns32:p><pre class="programlisting"> + </p><pre class="programlisting"> find 'directory_name' -type d -exec chown user.group {}\; find 'directory_name' -type d -exec chmod 6775 'directory_name' find 'directory_name' -type f -exec chmod 0775 {} \; find 'directory_name' -type f -exec chown user.group {}\; - </pre><ns32:p> - </ns32:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </pre><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above will set the 'sticky bit' on all directories. Read your Unix/Linux man page on what that does. It causes the OS to assign to all files created in the directories the ownership of the directory. - </p></div></li><li xmlns:ns33=""><ns33:p> + </p></div></li><li><p> Directory is: <i class="replaceable"><tt>/foodbar</tt></i> - </ns33:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chown jack.engr /foodbar</tt></b> - </pre><ns33:p> - </ns33:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><ns33:p> - </ns33:p><p>This is the same as doing:</p><ns33:p> - </ns33:p><pre class="screen"> + </pre><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><p>This is the same as doing:</p><p> + </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chown jack /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>chgrp engr /foodbar</tt></b> - </pre><ns33:p> - </ns33:p></div></li><li xmlns:ns34=""><ns34:p>Now do: + </pre><p> + </p></div></li><li><p>Now do: - </ns34:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chmod 6775 /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>ls -al /foodbar/..</tt></b> - </pre><ns34:p> + </pre><p> - </ns34:p><ns34:p>You should see: - </ns34:p><pre class="screen"> + </p><p>You should see: + </p><pre class="screen"> drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar - </pre><ns34:p> - </ns34:p></li><li xmlns:ns35=""><ns35:p>Now do: - </ns35:p><pre class="screen"> + </pre><p> + </p></li><li><p>Now do: + </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>su - jill</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>cd /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>touch Afile</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>ls -al</tt></b> - </pre><ns35:p> - </ns35:p><ns35:p> + </pre><p> + </p><p> You should see that the file <tt class="filename">Afile</tt> created by Jill will have ownership and permissions of Jack, as follows: - </ns35:p><pre class="screen"> + </p><pre class="screen"> -rw-r--r-- 1 jack engr 0 2003-02-04 09:57 Afile - </pre><ns35:p> - </ns35:p></li><li xmlns:ns36=""><ns36:p> + </pre><p> + </p></li><li><p> Now in your <tt class="filename">smb.conf</tt> for the share add: - </ns36:p><pre class="programlisting"> + </p><pre class="programlisting"> force create mode = 0775 - force direcrtory mode = 6775 - </pre><ns36:p> - </ns36:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + force directory mode = 6775 + </pre><p> + </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above are only needed <span class="emphasis"><em>if</em></span> your users are <span class="emphasis"><em>not</em></span> members of the group you have used. ie: Within the OS do not have write permission on the directory. - </p></div><ns36:p> + </p></div><p> An alternative is to set in the <tt class="filename">smb.conf</tt> entry for the share: - </ns36:p><pre class="programlisting"> + </p><pre class="programlisting"> force user = jack force group = engr - </pre><ns36:p> - </ns36:p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906838"></a>I have set force user and samba still makes <span class="emphasis"><em>root</em></span> the owner of all the files + </pre><p> + </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907109"></a>I have set force user and Samba still makes <span class="emphasis"><em>root</em></span> the owner of all the files I touch!</h3></div></div><div></div></div><p> - When you have a user in 'admin users', samba will always do file operations for + When you have a user in 'admin users', Samba will always do file operations for this user as <span class="emphasis"><em>root</em></span>, even if <i class="parameter"><tt>force user</tt></i> has been set. - </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter 14. File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2908960">Features and Benefits</a></dt><dt><a href="#id2909016">Discussion</a></dt><dd><dl><dt><a href="#id2906890">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2907521">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2907630">Example Configuration</a></dt></dl></dd><dt><a href="#id2907890">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2910326">Workstation Service Entries</a></dt><dt><a href="#id2910353">Server Service Entries</a></dt></dl></dd><dt><a href="#id2910432">Persistent Data Corruption</a></dt><dt><a href="#id2910463">Common Errors</a></dt><dd><dl><dt><a href="#id2910536">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2910566">Additional Reading</a></dt></dl></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter 14. File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2910721">Features and Benefits</a></dt><dt><a href="#id2910776">Discussion</a></dt><dd><dl><dt><a href="#id2910908">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2911554">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2911664">Example Configuration</a></dt></dl></dd><dt><a href="#id2911924">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2912154">Workstation Service Entries</a></dt><dt><a href="#id2912180">Server Service Entries</a></dt></dl></dd><dt><a href="#id2912260">Persistent Data Corruption</a></dt><dt><a href="#id2912291">Common Errors</a></dt><dd><dl><dt><a href="#id2912365">locking.tdb error messages</a></dt></dl></dd><dt><a href="#id2912394">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="id2908960"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910721"></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> @@ -4850,7 +4889,7 @@ settings on the MS Windows client. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Sometimes it is necessary to disable locking control settings BOTH on the Samba server as well as on each MS Windows client! -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2909016"></a>Discussion</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910776"></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> @@ -4889,7 +4928,7 @@ access should be allowed simultaneously with its open. A client may ask for <tt class="constant">DENY_NONE</tt>, <tt class="constant">DENY_READ</tt>, <tt class="constant">DENY_WRITE</tt> or <tt class="constant">DENY_ALL</tt>. There are also special compatibility modes called <tt class="constant">DENY_FCB</tt> and <tt class="constant">DENY_DOS</tt>. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2906890"></a>Opportunistic Locking Overview</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910908"></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 @@ -4910,8 +4949,8 @@ other processes. 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/ex- - clusive access to the file. The client now performs + 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 @@ -5012,7 +5051,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907180"></a>Exclusively Accessed Shares</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911199"></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 @@ -5021,7 +5060,7 @@ mechanism will cause a delay. </p><p> Home directories are the most obvious examples of where the performance benefit of opportunistic locking can be safely realized. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907206"></a>Multiple-Accessed Shares or Files</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911224"></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 @@ -5033,7 +5072,7 @@ of the caching user. As each additional client attempts to access a file with oplocks set, the potential performance improvement is negated and eventually results in a performance bottleneck. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907234"></a>Unix or NFS Client Accessed Files</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911253"></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 @@ -5041,9 +5080,9 @@ 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 loca Unix +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="id2907261"></a>Slow and/or Unreliable Networks</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911279"></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. @@ -5058,7 +5097,7 @@ the most advantageous scenario to utilize opportunistic locking. If the network is slow, unreliable, or a WAN, then do not configure opportunistic locking if there is any chance of multiple users regularly opening the same file. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907294"></a>Multi-User Databases</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911312"></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 @@ -5066,7 +5105,7 @@ locking enabled will likely result in a locking management bottleneck on the Samba server. Whether the database application is developed in-house or a commercially available product, ensure that the share has opportunistic locking disabled. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907315"></a>PDM Data Shares</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911334"></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 @@ -5079,7 +5118,7 @@ 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="id2907342"></a>Beware of Force User</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911375"></a>Beware of Force User</h4></div></div><div></div></div><p> Samba includes an <tt class="filename">smb.conf</tt> parameter called <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 @@ -5097,7 +5136,7 @@ Avoid the combination of the following: 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="id2907419"></a>Advanced Samba Opportunistic Locking Parameters</h4></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911453"></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 @@ -5111,7 +5150,7 @@ 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="id2907462"></a>Mission Critical High Availability</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911496"></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 @@ -5141,7 +5180,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907521"></a>Samba Opportunistic Locking Control</h2></div></div><div></div></div><p> +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911554"></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 defacto locking feature. @@ -5165,7 +5204,7 @@ synchronising the contents of the entire file back to the server for a single ch </p><p> Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. </p><p> -Level2 Oplocks provids opportunistic locking for a file that will be treated as +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> @@ -5178,7 +5217,7 @@ Unless your system supports kernel oplocks, you should disable oplocks if you ar 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 noticable performance +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. @@ -5191,29 +5230,29 @@ of your client sending oplock breaks and will instead want to disable oplocks fo </p><p> Another factor to consider is the perceived performance of file access. If oplocks provide no measurable speed benefit on your network, it might not be worth the hassle of dealing with them. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2907630"></a>Example Configuration</h3></div></div><div></div></div><p> -In the following we examine two destinct aspects of samba locking controls. -</p><div xmlns:ns37="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907643"></a>Disabling Oplocks</h4></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911664"></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="id2911677"></a>Disabling Oplocks</h4></div></div><div></div></div><p> You can disable oplocks on a per-share basis with the following: -</p><ns37:p> -</ns37:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> [acctdata] oplocks = False level2 oplocks = False -</pre><ns37:p> -</ns37:p><p> +</pre><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><ns37:p> -</ns37:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/ -</pre><ns37:p> -</ns37:p><p> +</pre><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 xmlns:ns38="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2907706"></a>Disabling Kernel OpLocks</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2911740"></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 @@ -5225,13 +5264,13 @@ 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><ns38:p> -</ns38:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> [global] kernel oplocks = yes -</pre><ns38:p> +</pre><p> The default is "no". -</ns38:p><p> +</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 @@ -5243,26 +5282,26 @@ 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><ns38:p> -</ns38:p><pre class="programlisting"><font color="red"><title>Example Veto OpLock Settings</title></font> +</p><p> +</p><pre class="programlisting"><font color="red"><title>Example Veto OpLock Settings</title></font> [global] veto oplock files = /filename.htm/*.txt/ [share_name] veto oplock files = /*.exe/filename.ext/ -</pre><ns38:p> -</ns38:p><p> +</pre><p> +</p><p> <span class="emphasis"><em>Oplock break wait time</em></span> 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><ns38:p> -</ns38:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> [global] oplock break wait time = 0 (default) -</pre><ns38:p> -</ns38:p><p> +</pre><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 @@ -5270,15 +5309,15 @@ 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><ns38:p> -</ns38:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> [global] oplock break contention limit = 2 (default) [share_name] oplock break contention limit = 2 (default) -</pre><ns38:p> -</ns38:p></div></div></div><div xmlns:ns39="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2907890"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><div></div></div><p> +</pre><p> +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911924"></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 @@ -5315,20 +5354,20 @@ Windows 2000 will still respect the EnableOplocks registry value used to disable in earlier versions of Windows. </p></div><p> You can also deny the granting of opportunistic locks by changing the following registry entries: -</p><ns39:p> -</ns39:p><pre class="programlisting"> +</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><ns39:p> -</ns39:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</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><ns39:p> -</ns39:p><pre class="programlisting"> +</p></div><p> +</p><pre class="programlisting"> HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanServer\Parameters @@ -5337,8 +5376,8 @@ request opportunistic locks on a remote file. To disable oplocks, the value of EnableOpLockForceClose REG_DWORD 0 or 1 Default: 0 (Disabled by Default) -</pre><ns39:p> -</ns39:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</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> @@ -5370,7 +5409,7 @@ An illustration of how level II oplocks work: station holds any oplock on the file. Because the workstations can have no cached writes or locks at this point, they need not respond to the break-to-none advisory; all they need do is invalidate locally cashed read-ahead data. - </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910326"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting"> + </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912154"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting"> \HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanWorkstation\Parameters @@ -5379,7 +5418,7 @@ An illustration of how level II oplocks work: </pre><p> Indicates whether the redirector should use opportunistic-locking (oplock) performance enhancement. This parameter should be disabled only to isolate problems. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910353"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting"> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912180"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting"> \HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanServer\Parameters @@ -5408,7 +5447,7 @@ the server disables raw I/O and opportunistic locking for this connection. Specifies the time that the server waits for a client to respond to an oplock break request. Smaller values can allow detection of crashed clients more quickly but can potentially cause loss of cached data. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910432"></a>Persistent Data Corruption</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912260"></a>Persistent Data Corruption</h2></div></div><div></div></div><p> If you have applied all of the settings discussed in this paper but data corruption problems and other symptoms persist, here are some additional things to check out: </p><p> @@ -5419,10 +5458,10 @@ rebuild the data files in question. This involves creating a new data file with same definition as the file to be rebuilt and transferring the data from the old file to the new one. There are several known methods for doing this that can be found in our Knowledge Base. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910463"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912291"></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 exeception, when a locking -problem does surface it will cause embarassment and potential data corruption. +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 @@ -5449,18 +5488,18 @@ so far: report on https://bugzilla.samba.org without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow reproduction of the problem (an essential step in problem isolation and correction). - </p></li></ul></div><div xmlns:ns40="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910536"></a>locking.tdb error messages</h3></div></div><div></div></div><ns40:p> - </ns40:p><pre class="screen"> + </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912365"></a>locking.tdb error messages</h3></div></div><div></div></div><p> + </p><pre class="screen"> > We are seeing lots of errors in the samba logs like: > > tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic > 0x4d6f4b61 at offset=36116 > > What do these mean? - </pre><ns40:p> - </ns40:p><p> - Corrupted tdb. Stop all instancesd of smbd, delete locking.tdb, restart smbd. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910566"></a>Additional Reading</h2></div></div><div></div></div><p> + </pre><p> + </p><p> + Corrupted tdb. Stop all instances of smbd, delete locking.tdb, restart smbd. + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912394"></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. @@ -5480,7 +5519,7 @@ Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default </p><p> Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", Microsoft Corporation, April 1995, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</a>. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter 15. Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2911991">Introduction</a></dt><dt><a href="#id2912024">Features and Benefits</a></dt><dt><a href="#id2910684">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2910702">Using host based protection</a></dt><dt><a href="#id2910771">User based protection</a></dt><dt><a href="#id2910822">Using interface protection</a></dt><dt><a href="#id2910872">Using a firewall</a></dt><dt><a href="#id2910929">Using a IPC$ share deny</a></dt><dt><a href="#id2910994">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2911033">Upgrading Samba</a></dt><dt><a href="#id2911056">Common Errors</a></dt><dd><dl><dt><a href="#id2911075">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2911100">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="id2911991"></a>Introduction</h2></div></div><div></div></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter 15. Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2914448">Introduction</a></dt><dt><a href="#id2914481">Features and Benefits</a></dt><dt><a href="#id2914555">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2914574">Using host based protection</a></dt><dt><a href="#id2914645">User based protection</a></dt><dt><a href="#id2914697">Using interface protection</a></dt><dt><a href="#id2914749">Using a firewall</a></dt><dt><a href="#id2914805">Using a IPC$ share deny</a></dt><dt><a href="#id2914866">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2914907">Upgrading Samba</a></dt><dt><a href="#id2914932">Common Errors</a></dt><dd><dl><dt><a href="#id2914949">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2914974">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="id2914448"></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. @@ -5492,7 +5531,7 @@ on it!" Security concerns are just like that: You need to know a little about the subject to appreciate how obvious most of it really is. The challenge for most of us is to discover that first morsel of knowledge with which we may unlock the secrets of the masters. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912024"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914481"></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. @@ -5511,13 +5550,13 @@ TCP/IP connections. Another method by which Samba may be secured is by way of setting Access Control Entries in an Access Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access Control. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2910684"></a>Technical Discussion of Protective Measures and Issues</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914555"></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="id2910702"></a>Using host based protection</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914574"></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 @@ -5537,7 +5576,7 @@ before someone will find yet another vulnerability. 192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as a <span class="errorname">not listening on called name</span> error. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910771"></a>User based protection</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914645"></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>[globals]</tt></i> section put: </p><pre class="programlisting"> @@ -5545,7 +5584,7 @@ before someone will find yet another vulnerability. </pre><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="id2910822"></a>Using interface protection</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914697"></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 @@ -5567,7 +5606,7 @@ before someone will find yet another vulnerability. connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that interface to any samba process. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910872"></a>Using a firewall</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914749"></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 @@ -5580,7 +5619,7 @@ before someone will find yet another vulnerability. The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910929"></a>Using a IPC$ share deny</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914805"></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 @@ -5607,10 +5646,10 @@ before someone will find yet another vulnerability. </p><p> This is not recommended unless you cannot use one of the other methods listed above for some reason. - </p></div><div xmlns:ns41="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2910994"></a>NTLMv2 Security</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914866"></a>NTLMv2 Security</h3></div></div><div></div></div><p> To configure NTLMv2 authentication the following registry keys are worth knowing about: - </p><ns41:p> - </ns41:p><pre class="screen"> + </p><p> + </p><pre class="screen"> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "lmcompatibilitylevel"=dword:00000003 @@ -5624,25 +5663,25 @@ before someone will find yet another vulnerability. 0x80000 - NTLMv2 session security. If either NtlmMinClientSec or NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2 session security is not negotiated. - </pre><ns41:p> - </ns41:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911033"></a>Upgrading Samba</h2></div></div><div></div></div><p> + </pre><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914907"></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. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911056"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914932"></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 admininstrators who post what turns +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="id2911075"></a>Smbclient works on localhost, but the network is dead</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914949"></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 xmlns:ns42="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911100"></a>Why can users access home directories of other users?</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914974"></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 @@ -5652,7 +5691,7 @@ out to be a security problem request are totally convinced that the problem is w </span>” </p><p>“<span class="quote"> User xyzzy can map his home directory. Once mapped user xyzzy can also map - *anyone* elses home directory! + *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 @@ -5673,25 +5712,25 @@ out to be a security problem request are totally convinced that the problem is w Samba does allow the setup you require when you have set the <i class="parameter"><tt>only user = yes</tt></i> option on the share, is that you have not set the valid users list for the share. - </p><ns42:p> + </p><p> Note that only user works in conjunction with the users= list, so to get the behavior you require, add the line : - </ns42:p><pre class="programlisting"> + </p><pre class="programlisting"> users = %S - </pre><ns42:p> + </pre><p> this is equivalent to: - </ns42:p><pre class="programlisting"> + </p><pre class="programlisting"> valid users = %S - </pre><ns42:p> + </pre><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. - </ns42:p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter 16. Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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">Rafal</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:mimir@samba.org">mimir@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2911618">Features and Benefits</a></dt><dt><a href="#id2911646">Trust Relationship Background</a></dt><dt><a href="#id2911730">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2911742">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2913717">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2913754">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2913781">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2913908">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2911286">Common Errors</a></dt><dd><dl><dt><a href="#id2911301">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter 16. Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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">Rafal</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:mimir@samba.org">mimir@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2915881">Features and Benefits</a></dt><dt><a href="#id2915909">Trust Relationship Background</a></dt><dt><a href="#id2915993">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2916006">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2916091">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2916127">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2916155">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2916295">Samba-3 as the Trusted Domain</a></dt></dl></dd><dt><a href="#id2916428">Common Errors</a></dt><dd><dl><dt><a href="#id2916443">Tell me about Trust Relationships using Samba</a></dt></dl></dd></dl></div><p> Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911618"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915881"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4 style trust relationships. This imparts to Samba similar scalability as is possible with MS Windows NT4. @@ -5699,9 +5738,9 @@ MS Windows NT4. Given that Samba-3 has the capability to function with a scalable backend authentication database such as LDAP, and given it's ability to run in Primary as well as Backup Domain control modes, the administrator would be well advised to consider alternatives to the use of -Interdomain trusts simplt because by the very nature of how this works it is fragile. -That was after all a key reason for the development and adoption of Microsoft Active Directory. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911646"></a>Trust Relationship Background</h2></div></div><div></div></div><p> +Interdomain trusts simply because by the very nature of how this works it is fragile. +That was, after all, a key reason for the development and adoption of Microsoft Active Directory. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915909"></a>Trust Relationship Background</h2></div></div><div></div></div><p> MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking in large organisations is well known. Additionally, the flat-name space that results from @@ -5736,9 +5775,9 @@ domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 style Interdomain trusts and interoperates with MS Windows 200x ADS security domains in similar manner to MS Windows NT4 style domains. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911730"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915993"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><div></div></div><p> There are two steps to creating an interdomain trust relationship. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911742"></a>NT4 as the Trusting Domain (ie. creating the trusted account)</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916006"></a>NT4 as the Trusting Domain (ie. creating the trusted account)</h3></div></div><div></div></div><p> For MS Windows NT4, all domain trust relationships are configured using the <span class="application">Domain User Manager</span>. To affect a two way trust relationship it is necessary for each domain administrator to make available (for use by an external domain) it's @@ -5750,14 +5789,14 @@ button will open a panel in which needs to be entered the remote domain that wil user rights to your domain. In addition it is necessary to enter a password that is specific to this trust relationship. The password needs to be typed twice (for standard confirmation). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913717"></a>NT4 as the Trusted Domain (ie. creating trusted account's password)</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916091"></a>NT4 as the Trusted Domain (ie. creating trusted account's password)</h3></div></div><div></div></div><p> A trust relationship will work only when the other (trusting) domain makes the appropriate connections -with the trusted domain. To consumate the trust relationship the administrator will launch the +with the trusted domain. To consummate the trust relationship the administrator will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the <span class="guibutton">Add</span> button that is next to the box that is labelled <span class="guilabel">Trusted Domains</span>. A panel will open in which must be entered the name of the remote domain as well as the password assigned to that trust. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913754"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2916127"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><div></div></div><p> This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba is in its early stage, so lot of things don't work yet. @@ -5766,32 +5805,32 @@ Each of the procedures described below is treated as they were performed with Wi one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after reading this document, that combining Samba-specific parts of what's written below leads to trust between domains in purely Samba environment. -</p><div xmlns:ns43="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913781"></a>Samba-3 as the Trusting Domain</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916155"></a>Samba-3 as the Trusting Domain</h3></div></div><div></div></div><p> In order to set the Samba PDC to be the trusted party of the relationship first you need to create special account for the domain that will be the trusting party. To do that, you can use the 'smbpasswd' utility. Creating the trusted domain account is very -similiar to creating a trusted machine account. Suppose, your domain is +similar to creating a trusted machine account. Suppose, your domain is called SAMBA, and the remote domain is called RUMBA. The first step will be to issue this command from your favourite shell: -</p><ns43:p> -</ns43:p><pre class="screen"> +</p><p> +</p><pre class="screen"> <tt class="prompt">root# </tt> <b class="userinput"><tt>smbpasswd -a -i rumba</tt></b> New SMB password: XXXXXXXX Retype SMB password: XXXXXXXX Added user rumba$ -</pre><ns43:p> +</pre><p> where <tt class="option">-a</tt> means to add a new account into the passdb database and <tt class="option">-i</tt> means: ''create this account with the InterDomain trust flag'' -</ns43:p><p> +</p><p> The account name will be 'rumba$' (the name of the remote domain) </p><p> After issuing this command you'll be asked to enter the password for the account. You can use any password you want, but be aware that Windows NT will not change this password until 7 days following account creation. After the command returns successfully, you can look at the entry for the new account -(in the stardard way depending on your configuration) and see that account's name is +(in the standard way depending on your configuration) and see that account's name is really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm the trust by establishing it from Windows NT Server. </p><p> @@ -5804,7 +5843,7 @@ your domain name, and the password used at the time of account creation. Press OK and, if everything went without incident, you will see <tt class="computeroutput">Trusted domain relationship successfully established</tt> message. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913908"></a>Samba-3 as the Trusted Domain</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916295"></a>Samba-3 as the Trusted Domain</h3></div></div><div></div></div><p> This time activities are somewhat reversed. Again, we'll assume that your domain controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA. </p><p> @@ -5835,11 +5874,11 @@ Congratulations! Your trust relationship has just been established. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Note that you have to run this command as root because you must have write access to the <tt class="filename">secrets.tdb</tt> file. -</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911286"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2916428"></a>Common Errors</h2></div></div><div></div></div><p> Interdomain trust relationships should NOT be attempted on networks that are unstable or that suffer regular outages. Network stability and integrity are key concerns with distributed trusted domains. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2911301"></a>Tell me about Trust Relationships using Samba</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2916443"></a>Tell me about Trust Relationships using Samba</h3></div></div><div></div></div><p> Like many, I administer multiple LANs connected together using NT trust relationships. This was implemented about 4 years ago. I now have the occasion to consider performing this same task again, but this time, I @@ -5856,12 +5895,12 @@ distributed trusted domains. Please provide any helpful feedback that you may have. </p><p> These are almost complete in Samba 3.0 snapshots. The main catch - is getting winbindd to be able to allocate uid/gid's for trusted + is getting winbindd to be able to allocate UID/GIDs for trusted users/groups. See the updated Samba HOWTO collection for more details. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="msdfs"></a>Chapter 17. Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Shirish</span> <span class="surname">Kalele</span></h3><div class="affiliation"><span class="orgname">Samba Team & 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="#id2911399">Features and Benefits</a></dt><dt><a href="#id2912809">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2911399"></a>Features and Benefits</h2></div></div><div></div></div><p> + </p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2915783">Features and Benefits</a></dt><dt><a href="#id2917436">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915783"></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 @@ -5913,17 +5952,17 @@ distributed trusted domains. network shares you want, and start Samba.</p><p>Users on DFS-aware clients can now browse the DFS tree on the Samba server at \\samba\dfs. Accessing links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2912809"></a>Common Errors</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted + takes users directly to the appropriate shares on the network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2917436"></a>Common Errors</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted if a previously mounted non-dfs share is made a dfs root or vice versa. A better way is to introduce a new share and make it the dfs root.</p></li><li><p>Currently there's a restriction that msdfs symlink names should all be lowercase.</p></li><li><p>For security purposes, the directory acting as the root of the DFS tree should have ownership and permissions set so that only designated users can - modify the symbolic links in the directory.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter 18. Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email"><<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 32, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2914332">Features and Benefits</a></dt><dt><a href="#id2914396">Technical Introduction</a></dt><dd><dl><dt><a href="#id2914432">What happens if you send a Job from a Client</a></dt><dt><a href="#id2914502">Printing Related Configuration Parameters</a></dt><dt><a href="#id2917610">Parameters Recommended for Use</a></dt><dt><a href="#id2912970">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2913079">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2913172">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2915178">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2915261">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2915568">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2915660">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2915673">The [global] Section</a></dt><dt><a href="#id2925133">The [printers] Section</a></dt><dt><a href="#id2925462">Any [my_printer_name] Section</a></dt><dt><a href="#id2925683">Print Commands</a></dt><dt><a href="#id2925734">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2926260">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2926537">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2926691">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2926842">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2926955">Creating the [print$] Share</a></dt><dt><a href="#id2927026">Parameters in the [print$] Section</a></dt><dt><a href="#id2927247">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2927408">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2927502">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2927686">Setting Drivers for existing Printers with -rpcclient</a></dt></dl></dd><dt><a href="#id2929284">"The Proof of the Pudding lies in the Eating" (Client Driver Insta -Procedure)</a></dt><dd><dl><dt><a href="#id2929305">The first Client Driver Installation</a></dt><dt><a href="#id2929502">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2929792">Further Client Driver Install Procedures</a></dt><dt><a href="#id2929887">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2930029">Other Gotchas</a></dt><dd><dl><dt><a href="#id2930062">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2930496">Supporting large Numbers of Printers</a></dt><dt><a href="#id2930798">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2931042">Weird Error Message Cannot connect under a -different Name</a></dt><dt><a href="#id2931140">Be careful when assembling Driver Files</a></dt><dt><a href="#id2931411">Samba and Printer Ports</a></dt><dt><a href="#id2931481">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2931504">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2931549">What is Imprints?</a></dt><dt><a href="#id2931590">Creating Printer Driver Packages</a></dt><dt><a href="#id2931609">The Imprints Server</a></dt><dt><a href="#id2931634">The Installation Client</a></dt></dl></dd><dt><a href="#id2931786">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2932115">The addprinter command</a></dt><dt><a href="#id2932160">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2932329">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2932343">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2932356">I give my root password but I don't get access</a></dt><dt><a href="#id2932390">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="id2914332"></a>Features and Benefits</h2></div></div><div></div></div><p> + modify the symbolic links in the directory.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter 18. Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email"><<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 32, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2917027">Features and Benefits</a></dt><dt><a href="#id2917095">Technical Introduction</a></dt><dd><dl><dt><a href="#id2917133">What happens if you send a Job from a Client</a></dt><dt><a href="#id2917203">Printing Related Configuration Parameters</a></dt><dt><a href="#id2918120">Parameters Recommended for Use</a></dt><dt><a href="#id2918450">Parameters for Backwards Compatibility</a></dt><dt><a href="#id2918559">Parameters no longer in use</a></dt></dl></dd><dt><a href="#id2918652">A simple Configuration to Print with Samba-3</a></dt><dd><dl><dt><a href="#id2918721">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2918810">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2919116">Extended Sample Configuration to Print with Samba-3</a></dt><dt><a href="#id2919220">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2919234">The [global] Section</a></dt><dt><a href="#id2919616">The [printers] Section</a></dt><dt><a href="#id2919945">Any [my_printer_name] Section</a></dt><dt><a href="#id2920166">Print Commands</a></dt><dt><a href="#id2920216">Default Print Commands for various Unix Print Subsystems</a></dt><dt><a href="#id2920741">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2921021">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2921186">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2921338">The [printer$] Section is removed from Samba-3</a></dt><dt><a href="#id2921450">Creating the [print$] Share</a></dt><dt><a href="#id2921521">Parameters in the [print$] Section</a></dt><dt><a href="#id2921752">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2921913">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2922008">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2922192">Setting Drivers for existing Printers with +rpcclient</a></dt></dl></dd><dt><a href="#id2923912">"The Proof of the Pudding lies in the Eating" (Client Driver Install +Procedure)</a></dt><dd><dl><dt><a href="#id2923933">The first Client Driver Installation</a></dt><dt><a href="#id2924131">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2924420">Further Client Driver Install Procedures</a></dt><dt><a href="#id2924516">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2924657">Other Gotchas</a></dt><dd><dl><dt><a href="#id2924690">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2925127">Supporting large Numbers of Printers</a></dt><dt><a href="#id2925430">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2925673">Weird Error Message Cannot connect under a +different Name</a></dt><dt><a href="#id2925771">Be careful when assembling Driver Files</a></dt><dt><a href="#id2926117">Samba and Printer Ports</a></dt><dt><a href="#id2926188">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2926210">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2926256">What is Imprints?</a></dt><dt><a href="#id2926297">Creating Printer Driver Packages</a></dt><dt><a href="#id2926316">The Imprints Server</a></dt><dt><a href="#id2926340">The Installation Client</a></dt></dl></dd><dt><a href="#id2926492">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2926822">The addprinter command</a></dt><dt><a href="#id2926867">Migration of "Classical" printing to Samba-3</a></dt><dt><a href="#id2927036">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2927051">Common Errors and Problems</a></dt><dd><dl><dt><a href="#id2927064">I give my root password but I don't get access</a></dt><dt><a href="#id2927097">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="id2917027"></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. @@ -5940,7 +5979,7 @@ 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 commandline +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 @@ -5959,7 +5998,7 @@ Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 2000 clients are very similar, but may differ in details. Windows NT is somewhat different again. -</p></div></div><div xmlns:ns44="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914396"></a>Technical Introduction</h2></div></div><div></div></div><ns44:p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2917095"></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 @@ -5974,18 +6013,18 @@ the next chapter covers in great detail the more modern <span class="emphasis"><em>Common UNIX Printing System</em></span> (CUPS). -</ns44: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 +</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><ns44:p> -</ns44:p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2914432"></a>What happens if you send a Job from a Client</h3></div></div><div></div></div><p> +here!</p></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2917133"></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 printershare</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 explicitely 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="id2914502"></a>Printing Related Configuration Parameters</h3></div></div><div></div></div><p> +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="id2917203"></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 @@ -5999,20 +6038,20 @@ 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="id2917610"></a>Parameters Recommended for Use</h3></div></div><div></div></div><p>The following <tt class="filename">smb.conf</tt> parameters directly +this (if you run it) and tell you so.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918120"></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-3. See also the <tt class="filename">smb.conf</tt> man page for detailed explanations: -</p><ns44:p><b>List of printing related parameters in Samba-3. </b> -</ns44:p><div class="itemizedlist"><p class="title"><b>Global level parameters:</b></p><ul type="disc"><li><p><i class="parameter"><tt>addprinter command (G)</tt></i></p></li><li><p><i class="parameter"><tt>deleteprinter command (G)</tt></i></p></li><li><p><i class="parameter"><tt>disable spoolss (G)</tt></i></p></li><li><p><i class="parameter"><tt>enumports command (G)</tt></i></p></li><li><p><i class="parameter"><tt>load printers (G)</tt></i></p></li><li><p><i class="parameter"><tt>lpq cache time (G)</tt></i></p></li><li><p><i class="parameter"><tt>os2 driver map (G)</tt></i></p></li><li><p><i class="parameter"><tt>printcap name (G), printcap (G)</tt></i></p></li><li><p><i class="parameter"><tt>show add printer wizard (G)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (G)</tt></i></p></li><li><p><i class="parameter"><tt>use client driver (G)</tt></i></p></li></ul></div><ns44:p> +</p><p><b>List of printing related parameters in Samba-3. </b> +</p><div class="itemizedlist"><p class="title"><b>Global level parameters:</b></p><ul type="disc"><li><p><i class="parameter"><tt>addprinter command (G)</tt></i></p></li><li><p><i class="parameter"><tt>deleteprinter command (G)</tt></i></p></li><li><p><i class="parameter"><tt>disable spoolss (G)</tt></i></p></li><li><p><i class="parameter"><tt>enumports command (G)</tt></i></p></li><li><p><i class="parameter"><tt>load printers (G)</tt></i></p></li><li><p><i class="parameter"><tt>lpq cache time (G)</tt></i></p></li><li><p><i class="parameter"><tt>os2 driver map (G)</tt></i></p></li><li><p><i class="parameter"><tt>printcap name (G), printcap (G)</tt></i></p></li><li><p><i class="parameter"><tt>show add printer wizard (G)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (G)</tt></i></p></li><li><p><i class="parameter"><tt>use client driver (G)</tt></i></p></li></ul></div><p> -</ns44:p><div class="itemizedlist"><p class="title"><b>Service level parameters:</b></p><ul type="disc"><li><p><i class="parameter"><tt>hosts allow (S)</tt></i></p></li><li><p><i class="parameter"><tt>hosts deny (S)</tt></i></p></li><li><p><i class="parameter"><tt>lppause command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lpq command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lpresume command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lprm command (S)</tt></i></p></li><li><p><i class="parameter"><tt>max print jobs (S)</tt></i></p></li><li><p><i class="parameter"><tt>min print space (S)</tt></i></p></li><li><p><i class="parameter"><tt>print command (S)</tt></i></p></li><li><p><i class="parameter"><tt>printable (S), print ok (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer name (S), printer (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer admin (S)</tt></i></p></li><li><p><i class="parameter"><tt>printing = [cups|bsd|lprng...] (S)</tt></i></p></li><li><p><i class="parameter"><tt>queuepause command (S)</tt></i></p></li><li><p><i class="parameter"><tt>queueresume command (S)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (S)</tt></i></p></li></ul></div><ns44:p> -</ns44:p><p> +</p><div class="itemizedlist"><p class="title"><b>Service level parameters:</b></p><ul type="disc"><li><p><i class="parameter"><tt>hosts allow (S)</tt></i></p></li><li><p><i class="parameter"><tt>hosts deny (S)</tt></i></p></li><li><p><i class="parameter"><tt>lppause command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lpq command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lpresume command (S)</tt></i></p></li><li><p><i class="parameter"><tt>lprm command (S)</tt></i></p></li><li><p><i class="parameter"><tt>max print jobs (S)</tt></i></p></li><li><p><i class="parameter"><tt>min print space (S)</tt></i></p></li><li><p><i class="parameter"><tt>print command (S)</tt></i></p></li><li><p><i class="parameter"><tt>printable (S), print ok (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer name (S), printer (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer admin (S)</tt></i></p></li><li><p><i class="parameter"><tt>printing = [cups|bsd|lprng...] (S)</tt></i></p></li><li><p><i class="parameter"><tt>queuepause command (S)</tt></i></p></li><li><p><i class="parameter"><tt>queueresume command (S)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (S)</tt></i></p></li></ul></div><p> +</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 class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2912970"></a>Parameters for Backwards Compatibility</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918450"></a>Parameters for Backwards Compatibility</h3></div></div><div></div></div><p> Two new parameters that were added in Samba 2.2.2, are still present in Samba-3.0. Both of these options are described in the <tt class="filename">smb.conf</tt> man page and are disabled by @@ -6022,19 +6061,19 @@ provided for better support of Samba 2.0.x backwards capability. It will disable Samba's support for MS-RPC printing and yield identical printing behaviour to Samba 2.0.x.</p></dd><dt><span class="term"><i class="parameter"><tt>use client driver (G)</tt></i></span></dt><dd><p> was provided for using local printer drivers on Windows NT/2000 clients. It does -not apply to Windows 95/98/ME clients.</p></dd></dl></div><ns44:p><b>Parameters "for backward compatibility only", use with caution. </b> -</ns44:p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>disable spoolss (G)</tt></i></p></li><li><p><i class="parameter"><tt>use client driver (S)</tt></i></p></li></ul></div><ns44:p> -</ns44:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2913079"></a>Parameters no longer in use</h3></div></div><div></div></div><p> +not apply to Windows 95/98/ME clients.</p></dd></dl></div><p><b>Parameters "for backward compatibility only", use with caution. </b> +</p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>disable spoolss (G)</tt></i></p></li><li><p><i class="parameter"><tt>use client driver (S)</tt></i></p></li></ul></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918559"></a>Parameters no longer in use</h3></div></div><div></div></div><p> Samba users upgrading from 2.2.x to 3.0 need to be aware that some previously available settings are no longer supported (as was announced some time ago). Here is a list of them: -</p><ns44:p><b>"old" parameters, removed in Samba-3. </b> +</p><p><b>"old" parameters, removed in Samba-3. </b> The following <tt class="filename">smb.conf</tt> parameters have been deprecated already in Samba 2.2 and are now completely removed from Samba-3. You cannot use them in new 3.0 installations: -</ns44:p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>printer driver file (G)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (G)</tt></i></p></li><li><p><i class="parameter"><tt>postscript (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer driver (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer driver location (S)</tt></i></p></li></ul></div><ns44:p> -</ns44:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2913172"></a>A simple Configuration to Print with Samba-3</h2></div></div><div></div></div><p> +</p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>printer driver file (G)</tt></i></p></li><li><p><i class="parameter"><tt>total print jobs (G)</tt></i></p></li><li><p><i class="parameter"><tt>postscript (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer driver (S)</tt></i></p></li><li><p><i class="parameter"><tt>printer driver location (S)</tt></i></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="id2918652"></a>A simple Configuration to Print with Samba-3</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 @@ -6069,7 +6108,7 @@ reminder: It even tolerates some spelling errors (like "browsable" instead of "browseable"). Most spelling is case-insensitive. Also, you can use "Yes|No" or "True|False" for boolean settings. Lists of names may be separated by commas, spaces or tabs. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2915178"></a>Verification of "Settings in Use" with <b class="command">testparm</b></h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918721"></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", @@ -6123,7 +6162,7 @@ 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.0 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="id2915261"></a>A little Experiment to warn you</h3></div></div><div></div></div><p> +configuration used, add the "-v" parameter to testparm.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2918810"></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, @@ -6227,12 +6266,12 @@ Samba version(s). But the man page states: “<span class="quote">Internal w in a parameter value is retained verbatim.</span>” This means that a line consisting of, for example, </p><pre class="screen"> -printing =lprng #This defines LPRng as the printing system" +printing = lprng #This defines LPRng as the printing system" </pre><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="id2915568"></a>Extended Sample Configuration to Print with Samba-3</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2919116"></a>Extended Sample Configuration to Print with Samba-3</h2></div></div><div></div></div><p> Here we show a more verbose example configuration for print related settings in an . Below is a discussion and explanation of the various parameters. We chose to use BSD-style @@ -6290,9 +6329,9 @@ default, because these have been compiled in. To see all settings, let root use the <b class="command">testparm</b> utility. <b class="command">testparm</b> also gives warnings if you have mis-configured certain things.. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2915660"></a>Detailed Explanation of the Example's Settings</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2919220"></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="id2915673"></a>The [global] Section</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919234"></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 @@ -6366,7 +6405,7 @@ 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="id2925133"></a>The [printers] Section</h3></div></div><div></div></div><p> +</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919616"></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, @@ -6414,7 +6453,7 @@ yes</tt></i>. Since we have <i class="parameter"><tt>guest ok = yes</tt></i>, 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 -Sambe wins. The "winner" is shown by testparm. Testparm doesn't +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 @@ -6426,7 +6465,7 @@ 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"><i class="parameter"><tt>writeable = no</tt></i></span></dt><dd><p> synonym for <i class="parameter"><tt>read only = yes</tt></i> -</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925462"></a>Any [my_printer_name] Section</h3></div></div><div></div></div><p> +</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2919945"></a>Any [my_printer_name] Section</h3></div></div><div></div></div><p> If a section appears in the , which is tagged as <i class="parameter"><tt>printable = yes</tt></i>, Samba presents it as a printer share to its clients. Note, that Win95/98/ME clients may @@ -6461,7 +6500,7 @@ 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"><i class="parameter"><tt>guest ok = no</tt></i></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="id2925683"></a>Print Commands</h3></div></div><div></div></div><p> +</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920166"></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 @@ -6479,7 +6518,7 @@ 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="id2925734"></a>Default Print Commands for various Unix Print Subsystems</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920216"></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 @@ -6519,7 +6558,7 @@ 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="id2926260"></a>Setting up your own Print Commands</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2920741"></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 <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 @@ -6589,7 +6628,7 @@ for the <i class="parameter"><tt>print command</tt></i> parameter varies dependi the <i class="parameter"><tt>printing</tt></i> parameter. Another example is: </p><pre class="programlisting"> print command = /usr/local/samba/bin/myprintscript %p %s -</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926537"></a>Innovations in Samba Printing since 2.2</h2></div></div><div></div></div><p> +</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921021"></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 @@ -6621,7 +6660,7 @@ 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/2k/XPprof +. 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 @@ -6630,7 +6669,7 @@ default permissions assigned by Windows NT to a printer gives the "Print" permissions to the well-known <span class="emphasis"><em>Everyone</em></span> group. (The older clients of type Win9x can only print to "shared" printers). -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926691"></a>Client Drivers on Samba Server for <span class="emphasis"><em>Point'n'Print</em></span></h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921186"></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 @@ -6654,7 +6693,7 @@ connect to this printer share. The <span class="emphasis"><em>uploading</em></sp 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/2k/XPprof client (this doesn't work from 95/98/ME +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 @@ -6663,12 +6702,12 @@ 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 +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="id2926842"></a>The [printer$] Section is removed from Samba-3</h3></div></div><div></div></div><p><b> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921338"></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 @@ -6694,11 +6733,11 @@ 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="id2926955"></a>Creating the [print$] Share</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921450"></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 hardcoded in the MS +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. @@ -6728,7 +6767,7 @@ with appropriate values for your site): </pre><p> Of course, you also need to ensure that the directory named by the <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="id2927026"></a>Parameters in the [print$] Section</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921521"></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. @@ -6773,7 +6812,7 @@ 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 <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="id2927247"></a>Subdirectory Structure in [print$]</h3></div></div><div></div></div><p> +configuring file shares. </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2921752"></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 @@ -6812,12 +6851,12 @@ client workstation. Open <span class="guiicon">Network Neighbourhood</span> or Once you have located the server, navigate to its <span class="guiicon">Printers and Faxes</span> folder. You should see an initial listing of printers that matches the printer shares defined on your Samba host. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927408"></a>Installing Drivers into [print$]</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2921913"></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. Unfortunatly, it is not enough +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 @@ -6830,7 +6869,7 @@ Properties</em></span> and <span class="emphasis"><em>Add Printer Wizard</em></s from any Windows NT/2k/XP client workstation.</p></li></ul></div><p> The latter option is probably the easier one (even if the only entrance to this realm seems a little bit weird at first). -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927502"></a>Setting Drivers for existing Printers with a Client GUI</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922008"></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, in @@ -6856,13 +6895,13 @@ now?</span></p><p> 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 popup list of installed +</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 Wiindows (we assume here that you are +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 <i class="parameter"><tt>printer admin</tt></i> privileges (if in doubt, use @@ -6876,7 +6915,7 @@ Assuming you have connected with an administrative (or root) account 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="id2927686"></a>Setting Drivers for existing Printers with +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2922192"></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 @@ -6885,13 +6924,13 @@ done from the UNIX command line. This involves four distinct steps: 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">addriver</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="id2927794"></a>Identifying the Driver Files</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922300"></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 @@ -6987,14 +7026,14 @@ 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 Wndows XP are +</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="id2928122"></a>Collecting the Driver Files from a Windows Host's +</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922629"></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 @@ -7030,7 +7069,7 @@ files for these architectures are in the WIN40/0/ subdir. Once we are complete, we can run <b class="command">smbclient ... put</b> to store the collected files on the Samba server's <i class="parameter"><tt>[print$]</tt></i> share. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928275"></a>Depositing the Driver Files into [print$]</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2922781"></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 @@ -7091,7 +7130,7 @@ re-location will automatically be done by the don't forget to also put the files for the Win95/98/ME architecture into the <tt class="filename">WIN40/</tt> subdirectory should you need them). -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928478"></a>Check if the Driver Files are there (with smbclient)</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923017"></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): @@ -7144,7 +7183,7 @@ Point'n'Print. The reason is: Samba doesn't know yet that these files are something special, namely <span class="emphasis"><em>printer driver files</em></span> and it doesn't know yet to which print queue(s) these driver files belong. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928594"></a>Running <b class="command">rpcclient</b> with +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923178"></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 @@ -7171,7 +7210,7 @@ again, for readability: </pre><p> After this step the driver should be recognized by Samba on the print -server. You need to be very carefull when typing the command. Don't +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 @@ -7179,7 +7218,7 @@ files successfully, but render the driver unworkable. So take care! Hints about the syntax of the adddriver command are in the man page. The CUPS printing chapter of this HOWTO collection provides a more detailed description, if you should need it. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928693"></a>Check how Driver Files have been moved after +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923278"></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. @@ -7227,19 +7266,19 @@ subdirectory. You can check this again with </pre><p> Another verification is that the timestamp of the printing TDB files is now updated (and possibly their filesize has increased). -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2928817"></a>Check if the Driver is recognized by Samba</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923446"></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, -finde the Samba host and open the Samba <span class="guiicon">Printers and +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 carefull to not do this unwittingly.). You can use this +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 @@ -7271,7 +7310,7 @@ time. Our new driver only shows up for <span class="application">Windows NT 4.0 or 2000</span>. To have it present for <span class="application">Windows 95, 98 and ME</span> you'll have to repeat the whole procedure with the WIN40 architecture and subdirectory. -</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2929021"></a>A sidenote: you are not bound to specific driver names</h4></div></div><div></div></div><p> +</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923650"></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: @@ -7304,8 +7343,8 @@ 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 ... addriver</b>" command. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2929132"></a>La Grande Finale: Running <b class="command">rpcclient</b> with +<b class="command">rpcclient ... adddriver</b>" command. +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2923761"></a>La Grande Finale: 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 @@ -7321,7 +7360,7 @@ 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 - Succesfully set dm9110 to driver 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 @@ -7335,13 +7374,13 @@ 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="id2929284"></a>"The Proof of the Pudding lies in the Eating" (Client Driver Insta +<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="id2923912"></a>"The Proof of the Pudding lies in the Eating" (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="id2929305"></a>The first Client Driver Installation</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2923933"></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 @@ -7384,7 +7423,7 @@ Data" set is still incomplete. </p><p> You must now make sure that a valid "Device Mode" is set for the driver. Don't fear -- we will explain now what that means. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929502"></a>IMPORTANT! Setting Device Modes on new Printers</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924131"></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 @@ -7456,7 +7495,7 @@ properties. Others may crash the client's spooler service. So use this parameter with caution. It is always better to have the client generate a valid device mode for the printer and store it on the server for you. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929792"></a>Further Client Driver Install Procedures</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924420"></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 @@ -7476,7 +7515,7 @@ rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2 You can enter the commands either inside a <span class="guilabel">DOS box</span> window or in the <span class="guimenuitem">Run command...</span> field from the <span class="guimenu">Start</span> menu. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2929887"></a>Always make first Client Connection as root or "printer admin"</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924516"></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 @@ -7508,17 +7547,17 @@ 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="id2930029"></a>Other Gotchas</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2924657"></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 preceeding paragraphs? And your users +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 xmlns:ns48="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930062"></a>Setting Default Print Options for the Client Drivers</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2924690"></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 @@ -7528,7 +7567,7 @@ up when you right-click the printer name and select 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><ns48:p><b>“<span class="quote">I can't set and save default print options +</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 @@ -7539,34 +7578,34 @@ dialogs <span class="emphasis"><em>look</em></span> the same. Only one of them Administrator to do this for all users. Here is how I reproduce it in on XP Professional: -</ns48:p><div class="orderedlist"><ol type="A"><li xmlns:ns45=""><ns45:p>The first "wrong" way: +</p><div class="orderedlist"><ol type="A"><li><p>The first "wrong" way: -</ns45:p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guiicon">Printers</span> +</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><ns45:p> -</ns45:p></li><li xmlns:ns46=""><ns46:p>The second "wrong" way: +like.</p></li></ol></div><p> +</p></li><li><p>The second "wrong" way: -</ns46:p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guimenu">Printers</span> +</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><ns46:p> -</ns46:p></li><li xmlns:ns47=""><ns47:p>The third, the "correct" way: (should you do +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) -</ns47:p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="guilabel">Advanced</span> +</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><ns47:p> -</ns47:p></li></ol></div><ns48:p> +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 @@ -7576,8 +7615,8 @@ defaults, you need to conduct these steps as administrator (<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 +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 @@ -7593,7 +7632,7 @@ 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! -</ns48: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 +</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> @@ -7607,7 +7646,7 @@ to see the tab with the <span class="guilabel">Printing Preferences...</span> button (the one which doesn't set system-wide defaults). You can start the commands from inside a DOS box" or from the <span class="guimenu">Start</span> -- <span class="guimenuitem">Run...</span> menu. -</p></div></div><div xmlns:ns49="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930496"></a>Supporting large Numbers of Printers</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925127"></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 @@ -7644,9 +7683,9 @@ following is an example of how this could be accomplished: Driver Name: [myphantasydrivername] [....] -</pre><ns49:p> +</pre><p> -</ns49:p><pre class="screen"> +</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] @@ -7654,15 +7693,15 @@ following is an example of how this could be accomplished: description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart] comment:[110 ppm HiVolume DANKA Stuttgart] [....] -</pre><ns49:p> +</pre><p> -</ns49:p><pre class="screen"> +</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><ns49:p> +</pre><p> -</ns49:p><pre class="screen"> +</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] @@ -7670,15 +7709,15 @@ following is an example of how this could be accomplished: description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....] -</pre><ns49:p> +</pre><p> -</ns49:p><pre class="screen"> +</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><ns49:p> +</pre><p> -</ns49:p><pre class="screen"> +</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] @@ -7693,8 +7732,8 @@ 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">rpccclient</b>). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2930798"></a>Adding new Printers with the Windows NT APW</h3></div></div><div></div></div><p> +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="id2925430"></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 @@ -7740,7 +7779,7 @@ user, not necessarily a root account. A <i class="parameter"><tt>map to guest = user</tt></i> 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="id2931042"></a>Weird Error Message <span class="errorname">Cannot connect under a +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925673"></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 @@ -7770,7 +7809,7 @@ message. You close all Explorer Windows and start it again. You try to connect - and this times it works! Windows seems to cache connection info somewhere and doesn't keep it up to date (if you are unlucky you might need to reboot to get rid of the error message). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931140"></a>Be careful when assembling Driver Files</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2925771"></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 @@ -7911,7 +7950,7 @@ In my example were even more differences than shown here. Conclusion: you must be very careful to select the correct driver files for each driver version. Don't rely on the names alone. Don't interchange files belonging to different driver versions. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931411"></a>Samba and Printer Ports</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926117"></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 @@ -7932,14 +7971,14 @@ another (“<span class="quote">My users and my Boss should not know that th working with Samba</span>”), possesses 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="id2931481"></a>Avoiding the most common Misconfigurations of the Client Driver</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926188"></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="id2931504"></a>The Imprints Toolset</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926210"></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 @@ -7956,20 +7995,20 @@ coordinate your efforts on the samba-technical mailing list. The toolset is still in usable form; but only for a series of older printer models, where there are prepared packages to use. Packages for more up to date print devices are needed if Imprints should have a -future.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931549"></a>What is Imprints?</h3></div></div><div></div></div><p> +future.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926256"></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="id2931590"></a>Creating Printer Driver Packages</h3></div></div><div></div></div><p> +servers.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926297"></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="id2931609"></a>The Imprints Server</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926316"></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 @@ -7977,7 +8016,7 @@ package is digitally signed via GnuPG which can be used to verify that package downloaded is actually the one referred in the Imprints database. It is strongly recommended that this security check <span class="emphasis"><em>not</em></span> be disabled. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2931634"></a>The Installation Client</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2926340"></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. @@ -7992,10 +8031,10 @@ 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 xmlns:ns50=""><ns50:p> +</p><div class="itemizedlist"><ul type="disc"><li><p> foreach (supported architecture for a given driver) - </ns50: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><ns50:p> - </ns50:p></li><li><p>rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer</p></li></ul></div><p> + </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 @@ -8018,7 +8057,7 @@ if is has not already been installed? The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that NT driver is installed first. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2931786"></a>Add Network Printers at Logon without User Interaction</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926492"></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> @@ -8064,12 +8103,12 @@ 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 deside for a +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 printqueue -on "sambacupsserver", and if the printer drivers have sucessfully been +<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 @@ -8093,7 +8132,7 @@ at logon time will not really be noticeable. Printers can be centrally added, changed, and deleted at will on the server with no user intervention required on the clients (you just need to keep the logon scripts up to date). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932115"></a>The <b class="command">addprinter</b> command</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2926822"></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 @@ -8105,7 +8144,7 @@ on legacy systems, or execute the <b class="command">lpadmin</b> command on more modern systems) and create the associated share in , then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932160"></a>Migration of "Classical" printing to Samba-3</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="id2926867"></a>Migration of "Classical" printing to Samba-3</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 @@ -8120,7 +8159,7 @@ and driver support. Previously used parameters "<i class="parameter"><tt>pr 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 theWin9x/ME drivers to the new +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.0. In @@ -8142,12 +8181,12 @@ rpcclient. See the Imprints installation client at: <a href="http://imprints.sourceforge.net/" target="_top"><span class="emphasis"><em>http://imprints.sourceforge.net/</em></span></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="id2932329"></a>Publishing Printer Information in Active Directory or LDAP</h2></div></div><div></div></div><p> +"CUPS Printing" section.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2927036"></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="id2932343"></a>Common Errors and Problems</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="id2927051"></a>Common Errors and Problems</h2></div></div><div></div></div><p> Here are a few typical errors and problems people have encountered. You can avoid them. Read on. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932356"></a>I give my root password but I don't get access</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927064"></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 @@ -8155,28 +8194,28 @@ 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="id2932390"></a>My printjobs get spooled into the spooling directory, but then get lost</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2927097"></a>My printjobs get spooled into the spooling directory, but then get lost</h3></div></div><div></div></div><p> Don't use the existing Unix print system spool directory for the Samba spool directory. It may seem convenient and a saving of space, but it only leads to problems. The two <span class="emphasis"><em>must</em></span> be separate. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter 19. CUPS Printing Support in Samba 3.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email"><<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">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span><div class="affiliation"><div class="address"><p><tt class="email"><<a href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (3 June 2003) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2939414">Introduction</a></dt><dd><dl><dt><a href="#id2939421">Features and Benefits</a></dt><dt><a href="#id2939469">Overview</a></dt></dl></dd><dt><a href="#id2939521">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2939600">Linking of smbd with libcups.so</a></dt><dt><a href="#id2932509">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2932572">More complex smb.conf Settings for -CUPS</a></dt></dl></dd><dt><a href="#id2932671">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2932692">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2932719">CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2932755">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2932814">Explicitly enable "raw" printing for -application/octet-stream!</a></dt><dt><a href="#id2932975">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2933068">Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2933143">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2933188">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2933286">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2933358">PostScript and Ghostscript</a></dt><dt><a href="#id2933454">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2933550">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2946373">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2946462">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2946485">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2946623">MIME types and CUPS Filters</a></dt><dt><a href="#id2946811">MIME type Conversion Rules</a></dt><dt><a href="#id2946927">Filter Requirements</a></dt><dt><a href="#id2947096">Prefilters</a></dt><dt><a href="#id2947181">pstops</a></dt><dt><a href="#id2947284">pstoraster</a></dt><dt><a href="#id2947440">imagetops and imagetoraster</a></dt><dt><a href="#id2947495">rasterto [printerspecific]</a></dt><dt><a href="#id2947580">CUPS Backends</a></dt><dt><a href="#id2947894">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2947997">The Complete Picture</a></dt><dt><a href="#id2948012">mime.convs</a></dt><dt><a href="#id2948065">"Raw" printing</a></dt><dt><a href="#id2948120">"application/octet-stream" printing</a></dt><dt><a href="#id2948335">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2948562">Difference between cupsomatic/foomatic-rip and -native CUPS printing</a></dt><dt><a href="#id2948719">Examples for filtering Chains</a></dt><dt><a href="#id2948948">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2949073">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2949135">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2949151">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2949190">Driver Execution on the Client</a></dt><dt><a href="#id2949249">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2949312">Network Printing (Windows clients -- UNIX/Samba Print -Servers)</a></dt><dd><dl><dt><a href="#id2949333">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2949493">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2949571">Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2949626">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2949667">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2949732">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2949750">Printer Drivers running in "Kernel Mode" cause many -Problems</a></dt><dt><a href="#id2949784">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2949805">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2949832">PostScript Drivers with no major problems -- even in Kernel -Mode</a></dt></dl></dd><dt><a href="#id2949866"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2949885">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2949976">Prepare your smb.conf for -cupsaddsmb</a></dt><dt><a href="#id2950023">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2950220">Recognize the different Driver Files</a></dt><dt><a href="#id2950278">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2950311">ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"</a></dt><dt><a href="#id2950361">Caveats to be considered</a></dt><dt><a href="#id2950582">What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2950763">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2950864">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2951007">Understanding cupsaddsmb</a></dt><dt><a href="#id2951101">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2951188">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2951223">cupsaddsmb Flowchart</a></dt><dt><a href="#id2951274">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2951389">Avoiding critical PostScript Driver Settings on the -Client</a></dt></dl></dd><dt><a href="#id2951523">Installing PostScript Driver Files manually (using -rpcclient)</a></dt><dd><dl><dt><a href="#id2951638">A Check of the rpcclient man Page</a></dt><dt><a href="#id2951750">Understanding the rpcclient man Page</a></dt><dt><a href="#id2951829">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2951919">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2952081">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2952701">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2952803">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2952906">Trivial DataBase Files</a></dt><dt><a href="#id2952976">Binary Format</a></dt><dt><a href="#id2953038">Losing *.tdb Files</a></dt><dt><a href="#id2953097">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2953159">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2953265">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2953893">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2954351">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2954382">Setting up Quotas</a></dt><dt><a href="#id2954413">Correct and incorrect Accounting</a></dt><dt><a href="#id2954454">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2954526">The page_log File Syntax</a></dt><dt><a href="#id2954628">Possible Shortcomings</a></dt><dt><a href="#id2954699">Future Developments</a></dt><dt><a href="#id2954747">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2954762">Additional Material</a></dt><dt><a href="#id2954956">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2955001">CUPS Configuration Settings explained</a></dt><dt><a href="#id2955083">Pre-conditions</a></dt><dt><a href="#id2955144">Manual Configuration</a></dt></dl></dd><dt><a href="#id2955162">When not to use Samba to print to -CUPS</a></dt><dt><a href="#id2955180">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2955214">Where to find Documentation</a></dt><dt><a href="#id2955227">How to ask for Help</a></dt><dt><a href="#id2955240">Where to find Help</a></dt></dl></dd><dt><a href="#id2955254">Appendix</a></dt><dd><dl><dt><a href="#id2955261">Printing from CUPS to Windows attached -Printers</a></dt><dt><a href="#id2955455">More CUPS filtering Chains</a></dt><dt><a href="#id2955709">Trouble Shooting Guidelines to fix typical Samba printing -Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2939414"></a>Introduction</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939421"></a>Features and Benefits</h3></div></div><div></div></div><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter 19. CUPS Printing Support in Samba 3.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email"><<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">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span><div class="affiliation"><div class="address"><p><tt class="email"><<a href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (3 June 2003) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2936290">Introduction</a></dt><dd><dl><dt><a href="#id2936298">Features and Benefits</a></dt><dt><a href="#id2936350">Overview</a></dt></dl></dd><dt><a href="#id2936405">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2936484">Linking of smbd with libcups.so</a></dt><dt><a href="#id2936628">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2936710">More complex smb.conf Settings for +CUPS</a></dt></dl></dd><dt><a href="#id2936828">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2936848">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2936875">CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2936912">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2936970">Explicitly enable "raw" printing for +application/octet-stream!</a></dt><dt><a href="#id2937131">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2937224">Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download</a></dt><dd><dl><dt><a href="#id2937300">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="#id2937344">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2937445">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="#id2937533">PostScript and Ghostscript</a></dt><dt><a href="#id2937630">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2937742">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2937813">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2937902">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2937925">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2938065">MIME types and CUPS Filters</a></dt><dt><a href="#id2938252">MIME type Conversion Rules</a></dt><dt><a href="#id2938369">Filter Requirements</a></dt><dt><a href="#id2938539">Prefilters</a></dt><dt><a href="#id2938624">pstops</a></dt><dt><a href="#id2938727">pstoraster</a></dt><dt><a href="#id2938883">imagetops and imagetoraster</a></dt><dt><a href="#id2938940">rasterto [printers specific]</a></dt><dt><a href="#id2939024">CUPS Backends</a></dt><dt><a href="#id2939336">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2939448">The Complete Picture</a></dt><dt><a href="#id2939464">mime.convs</a></dt><dt><a href="#id2939517">"Raw" printing</a></dt><dt><a href="#id2939571">"application/octet-stream" printing</a></dt><dt><a href="#id2939786">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2940015">Difference between cupsomatic/foomatic-rip and +native CUPS printing</a></dt><dt><a href="#id2940170">Examples for filtering Chains</a></dt><dt><a href="#id2940401">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2940530">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2940605">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2940620">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2940659">Driver Execution on the Client</a></dt><dt><a href="#id2940731">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2940794">Network Printing (Windows clients -- UNIX/Samba Print +Servers)</a></dt><dd><dl><dt><a href="#id2940814">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2940978">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2941054">Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2941110">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2941150">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2941216">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2941233">Printer Drivers running in "Kernel Mode" cause many +Problems</a></dt><dt><a href="#id2941268">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2941289">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2941316">PostScript Drivers with no major problems -- even in Kernel +Mode</a></dt></dl></dd><dt><a href="#id2941369"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2941388">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2941480">Prepare your smb.conf for +cupsaddsmb</a></dt><dt><a href="#id2941526">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2941724">Recognize the different Driver Files</a></dt><dt><a href="#id2941782">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2941814">ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"</a></dt><dt><a href="#id2941864">Caveats to be considered</a></dt><dt><a href="#id2942086">What are the Benefits of using the "CUPS PostScript Driver for +Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="#id2942268">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2942369">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2942596">Understanding cupsaddsmb</a></dt><dt><a href="#id2942690">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="#id2942777">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2942812">cupsaddsmb Flowchart</a></dt><dt><a href="#id2942865">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2942978">Avoiding critical PostScript Driver Settings on the +Client</a></dt></dl></dd><dt><a href="#id2943112">Installing PostScript Driver Files manually (using +rpcclient)</a></dt><dd><dl><dt><a href="#id2943227">A Check of the rpcclient man Page</a></dt><dt><a href="#id2943340">Understanding the rpcclient man Page</a></dt><dt><a href="#id2943429">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2943519">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2943682">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="#id2944334">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2944435">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2944537">Trivial DataBase Files</a></dt><dt><a href="#id2944608">Binary Format</a></dt><dt><a href="#id2944670">Losing *.tdb Files</a></dt><dt><a href="#id2944728">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2944795">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2944903">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2945532">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2945993">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2946024">Setting up Quotas</a></dt><dt><a href="#id2946056">Correct and incorrect Accounting</a></dt><dt><a href="#id2946097">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2946169">The page_log File Syntax</a></dt><dt><a href="#id2946270">Possible Shortcomings</a></dt><dt><a href="#id2946341">Future Developments</a></dt><dt><a href="#id2946390">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2946404">Additional Material</a></dt><dt><a href="#id2946598">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2946644">CUPS Configuration Settings explained</a></dt><dt><a href="#id2946726">Pre-conditions</a></dt><dt><a href="#id2946787">Manual Configuration</a></dt></dl></dd><dt><a href="#id2946805">When not to use Samba to print to +CUPS</a></dt><dt><a href="#id2946822">In Case of Trouble.....</a></dt><dd><dl><dt><a href="#id2946857">Where to find Documentation</a></dt><dt><a href="#id2946870">How to ask for Help</a></dt><dt><a href="#id2946883">Where to find Help</a></dt></dl></dd><dt><a href="#id2946896">Appendix</a></dt><dd><dl><dt><a href="#id2946904">Printing from CUPS to Windows attached +Printers</a></dt><dt><a href="#id2947118">More CUPS filtering Chains</a></dt><dt><a href="#id2947424">Trouble Shooting Guidelines to fix typical Samba printing +Problems</a></dt><dt><a href="#id2948546">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936290"></a>Introduction</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936298"></a>Features and Benefits</h3></div></div><div></div></div><p> The Common Unix Print System (<a href="http://www.cups.org/" target="_top">CUPS</a>) has become very popular. All big Linux distributions now ship it as their default printing system. But to many it is still a very mystical tool. Normally it @@ -8201,7 +8240,7 @@ Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Proce contained. But lets start with the most basic things first. Maybe this is all you need for now. Then you can skip most of the other paragraphs. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939469"></a>Overview</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936350"></a>Overview</h3></div></div><div></div></div><p> CUPS is more than just a print spooling system. It is a complete printer management system that complies with the new IPP (<span class="emphasis"><em>Internet Printing Protocol</em></span>). IPP is an industry @@ -8221,7 +8260,7 @@ Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Proce argue that CUPS is better! In any case, let us now move on to explore how one may configure CUPS for interfacing with MS Windows print clients via Samba. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2939521"></a>Basic Configuration of CUPS support</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936405"></a>Basic Configuration of CUPS support</h2></div></div><div></div></div><p> Printing with CUPS in the most basic <tt class="filename">smb.conf</tt> setup in Samba 3.0 (as was true for 2.2.x) only needs two settings: <i class="parameter"><tt>printing = cups</tt></i> and <i class="parameter"><tt>printcap @@ -8237,7 +8276,7 @@ Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Proce details see <b class="command">man cupsd.conf</b> and other CUPS-related documentation, like the wealth of documents on your CUPS server itself: <a href="http://localhost:631/documentation.html" target="_top">http://localhost:631/documentation.html</a>. - </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939600"></a>Linking of smbd with <tt class="filename">libcups.so</tt></h3></div></div><div></div></div><p> + </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936484"></a>Linking of smbd with libcups.so</h3></div></div><div></div></div><p> Samba has a very special relationship to CUPS. The reason is: Samba can be compiled with CUPS library support. Most recent installations have this support enabled, and per default CUPS linking is compiled @@ -8274,9 +8313,9 @@ Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Proce <i class="parameter"><tt>print command</tt></i>; other commands are <i class="parameter"><tt>lppause command, lpresume command, lpq command, lprm command, queuepause command </tt></i> and <i class="parameter"><tt>queue resume - command</tt></i>).</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932509"></a>Simple <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p> + command</tt></i>).</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936628"></a>Simple <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p> To summarize, here is the simplest printing-related setup - for<tt class="filename">smb.conf</tt> to enable basic CUPS support: + for <tt class="filename">smb.conf</tt> to enable basic CUPS support: </p><pre class="screen"> [global] @@ -8309,10 +8348,10 @@ Problems</a></dt><dt><a href="#id2956815">An Overview of the CUPS Printing Proce printer is not a PostScript device, the print data stream is "binary", sensible only for the target printer. Read on to learn which problem this may cause and how to avoid it. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932572"></a>More complex <tt class="filename">smb.conf</tt> Settings for + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936710"></a>More complex <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p> Here is a slightly more complex printing-related setup -for<tt class="filename">smb.conf</tt>. It enables general CUPS printing +for <tt class="filename">smb.conf</tt>. It enables general CUPS printing support for all printers, but defines one printer share which is set up differently. </p><pre class="screen"> @@ -8350,7 +8389,7 @@ up differently. </pre><p> This special share is only there for my testing purposes. It doesn't -even write the printjob to a file. It just logs the job parameters +even write the print job to a file. It just logs the job parameters known to Samba into the <tt class="filename">/tmp/smbprn.log</tt> file and deletes the jobfile. Moreover, the <i class="parameter"><tt>printer admin</tt></i> of this share is "kurt" (not the "@ntadmins" group); @@ -8360,13 +8399,13 @@ allowing access from three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set <i class="parameter"><tt>printing = sysv</tt></i> and <i class="parameter"><tt>printcap = lpstat</tt></i>. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2932671"></a>Advanced Configuration</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2936828"></a>Advanced Configuration</h2></div></div><div></div></div><p> Before we dive into all the configuration options, let's clarify a few points. <span class="emphasis"><em>Network printing needs to be organized and setup correctly</em></span>. Often this is not done correctly. Legacy systems or small LANs in business environments often lack a clear design and good housekeeping. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932692"></a>Central spooling vs. "Peer-to-Peer" printing</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936848"></a>Central spooling vs. "Peer-to-Peer" printing</h3></div></div><div></div></div><p> Many small office or home networks, as well as badly organized larger environments, allow each client a direct access to available network printers. Generally, this is a bad idea. It often blocks one client's @@ -8378,13 +8417,13 @@ is the usage of a "print server": it routes all jobs through one central system, which responds immediately, takes jobs from multiple concurrent clients at the same time and in turn transfers them to the printer(s) in the correct order. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932719"></a>CUPS/Samba as a "spooling-only" Print Server; "raw" printing +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936875"></a>CUPS/Samba as a "spooling-only" Print Server; "raw" printing with Vendor Drivers on Windows Clients</h3></div></div><div></div></div><p> Most traditionally configured Unix print servers acting on behalf of Samba's Windows clients represented a really simple setup. Their only task was to manage the "raw" spooling of all jobs handed to them by Samba. This approach meant that the Windows clients were expected to -prepare the printjob file in such a way that it became fit to be fed to +prepare the print job file in such a way that it became fit to be fed to the printing device. Here a native (vendor-supplied) Windows printer driver for the target device needed to be installed on each and every client. @@ -8397,7 +8436,7 @@ sent in a format that is suitable for direct delivery to the printer. Clients need to run the vendor-provided drivers to do this. In this case CUPS will NOT do any print file format conversion work. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932755"></a>Driver Installation Methods on Windows Clients</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936912"></a>Driver Installation Methods on Windows Clients</h3></div></div><div></div></div><p> The printer drivers on the Windows clients may be installed in two functionally different ways: </p><div class="itemizedlist"><ul type="disc"><li><p>manually install the drivers locally on each client, @@ -8410,7 +8449,7 @@ first time they access the printer; with this method NT/2K/XP clients use the <span class="emphasis"><em>SPOOLSS/MS-RPC</em></span> type printing calls.</p></li></ul></div><p> The second method is recommended for use over the first. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932814"></a>Explicitly enable "raw" printing for +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2936970"></a>Explicitly enable "raw" printing for <span class="emphasis"><em>application/octet-stream</em></span>!</h3></div></div><div></div></div><p> If you use the first option (drivers are installed on the client side), there is one setting to take care of: CUPS needs to be told @@ -8459,7 +8498,7 @@ This is all you need to know to get the CUPS/Samba combo printing locally installed. If you are not interested in background information about more advanced CUPS/Samba printing, simply skip the remaining sections of this chapter. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2932975"></a>Three familiar Methods for driver upload plus a new one</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937131"></a>Three familiar Methods for driver upload plus a new one</h3></div></div><div></div></div><p> If you want to use the MS-RPC type printing, you must upload the drivers onto the Samba server first (<i class="parameter"><tt>[print$]</tt></i> share). For a discussion on how to deposit printer drivers on the @@ -8481,7 +8520,7 @@ utility.</p></li></ul></div><p> cupsaddsmb is discussed in much detail further below. But we will first explore the CUPS filtering system and compare the Windows and UNIX printing architectures. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2933068"></a>Using CUPS/Samba in an advanced Way -- intelligent printing +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2937224"></a>Using CUPS/Samba in an advanced Way -- intelligent printing with PostScript Driver Download</h2></div></div><div></div></div><p> Still reading on? Good. Let's go into more detail then. We now know how to set up a "dump" printserver, that is, a server which is spooling @@ -8506,7 +8545,7 @@ how CUPS works and how you can enable its features. What follows is the comparison of some fundamental concepts for Windows and Unix printing; then is the time for a description of the CUPS filtering system, how it works and how you can tweak it. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933143"></a>GDI on Windows -- PostScript on Unix</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937300"></a>GDI on Windows -- PostScript on Unix</h3></div></div><div></div></div><p> Network printing is one of the most complicated and error-prone day-to-day tasks any user or an administrator may encounter. This is true for all OS platforms. And there are reasons for this. @@ -8515,14 +8554,14 @@ You can't expect for most file formats to just throw them towards printers and they get printed. There needs to be a file format conversion in between. The problem is: there is no common standard for print file formats across all manufacturers and printer types. While -<span class="emphasis"><em>PostScript</em></span> (trademark held by Adobe), and to an -extend<span class="emphasis"><em>PCL</em></span> (trademark held by HP), have developed +<span class="emphasis"><em>PostScript</em></span> (trademark held by Adobe), and, to an +extent, <span class="emphasis"><em>PCL</em></span> (trademark held by HP), have developed into semi-official "standards", by being the most widely used PDLs (<span class="emphasis"><em>Page Description Languages</em></span>), there are still many manufacturers who "roll their own" (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, etc.). -</p></div><div xmlns:ns51="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933188"></a>Windows Drivers, GDI and EMF</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937344"></a>Windows Drivers, GDI and EMF</h3></div></div><div></div></div><p> In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all application programmers have at their disposal a built-in API, the GDI (<span class="emphasis"><em>Graphical Device @@ -8544,10 +8583,10 @@ put paper and screen output on a common foundation for their (BSD-Unix-based, did you know??) Mac OS X and Darwin Operating Systems.Their <span class="emphasis"><em>Core Graphic Engine</em></span> uses a <span class="emphasis"><em>PDF</em></span> derivate for all display work. -</p></div><ns51:p> +</p></div><p> -</ns51:p><div class="figure"><a name="id2933252"></a><p class="title"><b>Figure 19.1. Windows Printing to a local Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="Windows Printing to a local Printer"></div></div><ns51:p> -</ns51:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933286"></a>Unix Printfile Conversion and GUI Basics</h3></div></div><div></div></div><p> +</p><div class="figure"><a name="id2937409"></a><p class="title"><b>Figure 19.1. Windows Printing to a local Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="Windows Printing to a local Printer"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937445"></a>Unix Printfile Conversion and GUI Basics</h3></div></div><div></div></div><p> In Unix and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server. Every application is responsible for itself to create its print output. Fortunately, most @@ -8583,7 +8622,7 @@ form and you will be reading its PostScript code, the language instructions which need to be interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer program or on paper by a printer. -</p></div><div xmlns:ns52="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933358"></a>PostScript and Ghostscript</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937533"></a>PostScript and Ghostscript</h3></div></div><div></div></div><p> So, Unix is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable legacy for Unix, basic printing is fairly easy: if you have PostScript printers at your @@ -8602,9 +8641,9 @@ options a printer supports: duplexing, stapling, punching... Therefore Unix users for a long time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now there is CUPS.... ;-) -</p></div><ns52:p> -</ns52:p><div class="figure"><a name="id2933404"></a><p class="title"><b>Figure 19.2. Printing to a Postscript Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/2small.png" alt="Printing to a Postscript Printer"></div></div><ns52:p> -</ns52:p><p> +</p></div><p> +</p><div class="figure"><a name="id2937580"></a><p class="title"><b>Figure 19.2. Printing to a Postscript Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/2small.png" alt="Printing to a Postscript Printer"></div></div><p> +</p><p> However, there are other types of printers out there. These don't know how to print PostScript. They use their own <span class="emphasis"><em>Page Description Language</em></span> (PDL, often proprietary). To print to them is much @@ -8612,17 +8651,17 @@ more demanding. Since your Unix applications mostly produce PostScript, and since these devices don't understand PostScript, you need to convert the printfiles to a format suitable for your printer on the host, before you can send it away. -</p></div><div xmlns:ns53="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933454"></a>Ghostscript -- the Software RIP for non-PostScript Printers</h3></div></div><div></div></div><p> -Here is where<span class="emphasis"><em>Ghostscript</em></span> kicks in. Ghostscript is +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937630"></a>Ghostscript -- the Software RIP for non-PostScript Printers</h3></div></div><div></div></div><p> +Here is where <span class="emphasis"><em>Ghostscript</em></span> kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter used on Unix platforms. It is a RIP in software, capable to do a <span class="emphasis"><em>lot</em></span> of file format conversions, for a very broad spectrum of hardware devices as well as software file formats. Ghostscript technology and drivers is what enables PostScript printing to non-PostScript hardware. -</p><ns53:p> -</ns53:p><div class="figure"><a name="id2933484"></a><p class="title"><b>Figure 19.3. Ghostscript as a RIP for non-postscript printers</b></p><div class="mediaobject"><img src="projdoc/imagefiles/3small.png" alt="Ghostscript as a RIP for non-postscript printers"></div></div><ns53:p> -</ns53:p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> +</p><p> +</p><div class="figure"><a name="id2937660"></a><p class="title"><b>Figure 19.3. Ghostscript as a RIP for non-postscript printers</b></p><div class="mediaobject"><img src="projdoc/imagefiles/3small.png" alt="Ghostscript as a RIP for non-postscript printers"></div></div><p> +</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Use the "gs -h" command to check for all built-in "devices" of your Ghostscript version. If you specify e.g. a parameter of <i class="parameter"><tt>-sDEVICE=png256</tt></i> on your Ghostscript command @@ -8639,7 +8678,7 @@ enhancement over GNU Ghostscript, with lots of bug-fixes, additional devices and improvements. It is jointly maintained by developers from CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes the "cups" device (essential to print to non-PS printers from CUPS). -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2933550"></a>PostScript Printer Description (PPD) Specification</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937742"></a>PostScript Printer Description (PPD) Specification</h3></div></div><div></div></div><p> While PostScript in essence is a <span class="emphasis"><em>Page Description Language</em></span> (PDL) to represent the page layout in a <span class="emphasis"><em>device independent</em></span> way, real world print jobs are @@ -8670,7 +8709,7 @@ for achieving a certain print job output (e.g. duplexed, stapled and punched) on a specific target machine, may not print as expected, or may not be printable at all on other models; it also may not be fit for further processing by software (e.g. by a PDF distilling program). -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946373"></a>CUPS can use all Windows-formatted Vendor PPDs</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937813"></a>CUPS can use all Windows-formatted Vendor PPDs</h3></div></div><div></div></div><p> CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if a Unix/Linux-illiterate vendor might not have mentioned our favorite @@ -8697,7 +8736,7 @@ your LAN has the PostScript driver installed, just use access the Windows directory where all printer driver files are stored. First look in the <tt class="filename">W32X86/2</tt> subdir for the PPD you are seeking. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946462"></a>CUPS also uses PPDs for non-PostScript Printers</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2937902"></a>CUPS also uses PPDs for non-PostScript Printers</h3></div></div><div></div></div><p> CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available from the vendors (and no, you can't just take the PPD of a Postscript printer with the same @@ -8705,7 +8744,7 @@ model name and hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers we first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2946485"></a>The CUPS Filtering Architecture</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2937925"></a>The CUPS Filtering Architecture</h2></div></div><div></div></div><p> The core of the CUPS filtering system is based on <span class="emphasis"><em>Ghostscript</em></span>. In addition to Ghostscript, CUPS uses some other filters of its own. You (or your OS vendor) may have @@ -8747,7 +8786,7 @@ others. However, even for Foomatic/cupsomatic usage, best results and broadest printer model support is provided by ESP Ghostscript (more about cupsomatic/Foomatic, particularly the new version called now <span class="emphasis"><em>foomatic-rip</em></span>, follows below). -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946623"></a>MIME types and CUPS Filters</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938065"></a>MIME types and CUPS Filters</h3></div></div><div></div></div><p> CUPS reads the file <tt class="filename">/etc/cups/mime.types</tt> (and all other files carrying a <tt class="filename">*.types</tt> suffix in the same directory) upon startup. These files contain the MIME @@ -8800,7 +8839,7 @@ CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, PNM, PBM, SGI-RGB and some more) and their associated MIME types with its filters. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946811"></a>MIME type Conversion Rules</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938252"></a>MIME type Conversion Rules</h3></div></div><div></div></div><p> CUPS reads the file <tt class="filename">/etc/cups/mime.convs</tt> (and all other files named with a <tt class="filename">*.convs</tt> suffix in the same directory) upon startup. These files contain @@ -8841,7 +8880,7 @@ The last two examples name the <span class="emphasis"><em>texttops</em></span> f to work on "text/plain" as well as on "application/x-shell". (Hint: this differentiation is needed for the syntax highlighting feature of "texttops"). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946927"></a>Filter Requirements</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938369"></a>Filter Requirements</h3></div></div><div></div></div><p> There are many more combinations named in mime.convs. However, you are not limited to use the ones pre-defined there. You can plug in any filter you like into the CUPS framework. It must meet, or must be made @@ -8862,7 +8901,7 @@ attribute</p></dd><dt><span class="term">Printer</span></dt><dd><p>The string fr attribute</p></dd><dt><span class="term">Printer</span></dt><dd><p>The job options</p></dd><dt><span class="term">Printer</span></dt><dd><p>(Optionally) The print request file (if missing, filters expected data fed through <tt class="filename">stdin</tt>). In most cases it is very easy to write a simple wrapper script around existing -filters to make them work with CUPS.</p></dd></dl></div></div></div><div xmlns:ns54="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947096"></a>Prefilters</h3></div></div><div></div></div><p> +filters to make them work with CUPS.</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938539"></a>Prefilters</h3></div></div><div></div></div><p> As was said, PostScript is the central file format to any Unix based printing system. From PostScript, CUPS generates raster data to feed non-PostScript printers. @@ -8879,18 +8918,18 @@ the <span class="emphasis"><em>imagetops</em></span> filter. Its outcome is alwa MIME type <span class="emphasis"><em>application/vnd.cups-postscript</em></span> (<span class="emphasis"><em>not</em></span> application/postscript), meaning it has the print options already embedded into the file. -</p><ns54:p> -</ns54:p><div class="figure"><a name="id2947147"></a><p class="title"><b>Figure 19.4. Prefiltering in CUPS to form Postscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/4small.png" alt="Prefiltering in CUPS to form Postscript"></div></div><ns54:p> -</ns54:p></div><div xmlns:ns55="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947181"></a>pstops</h3></div></div><div></div></div><p> +</p><p> +</p><div class="figure"><a name="id2938589"></a><p class="title"><b>Figure 19.4. Prefiltering in CUPS to form Postscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/4small.png" alt="Prefiltering in CUPS to form Postscript"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938624"></a>pstops</h3></div></div><div></div></div><p> <span class="emphasis"><em>pstops</em></span>is the filter to convert <span class="emphasis"><em>application/postscript</em></span> to <span class="emphasis"><em>application/vnd.cups-postscript</em></span>. It was said above that this filter inserts all device-specific print options (commands to the printer to ask for the duplexing of output, or stapling an punching it, etc.) into the PostScript file. -</p><ns55:p> -</ns55:p><div class="figure"><a name="id2947212"></a><p class="title"><b>Figure 19.5. Adding Device-specific Print Options</b></p><div class="mediaobject"><img src="projdoc/imagefiles/5small.png" alt="Adding Device-specific Print Options"></div></div><ns55:p> -</ns55:p><p> +</p><p> +</p><div class="figure"><a name="id2938654"></a><p class="title"><b>Figure 19.5. Adding Device-specific Print Options</b></p><div class="mediaobject"><img src="projdoc/imagefiles/5small.png" alt="Adding Device-specific Print Options"></div></div><p> +</p><p> This is not all: other tasks performed by it are: </p><div class="itemizedlist"><ul type="disc"><li><p> selecting the range of pages to be printed (if you choose to @@ -8901,7 +8940,7 @@ putting 2 or more logical pages on one sheet of paper (the so-called "number-up" function) </p></li><li><p>counting the pages of the job to insert the accounting information into the <tt class="filename">/var/log/cups/page_log</tt> -</p></li></ul></div></div><div xmlns:ns56="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947284"></a>pstoraster</h3></div></div><div></div></div><p> +</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938727"></a>pstoraster</h3></div></div><div></div></div><p> <span class="emphasis"><em>pstoraster</em></span> is at the core of the CUPS filtering system. It is responsible for the first stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; @@ -8909,9 +8948,9 @@ its output is application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a general purpose input format for more specialized <span class="emphasis"><em>raster drivers</em></span>, that are able to generate device-specific printer data. -</p><ns56:p> -</ns56:p><div class="figure"><a name="id2947314"></a><p class="title"><b>Figure 19.6. Postscript to intermediate Raster format</b></p><div class="mediaobject"><img src="projdoc/imagefiles/6small.png" alt="Postscript to intermediate Raster format"></div></div><ns56:p> -</ns56:p><p> +</p><p> +</p><div class="figure"><a name="id2938756"></a><p class="title"><b>Figure 19.6. Postscript to intermediate Raster format</b></p><div class="mediaobject"><img src="projdoc/imagefiles/6small.png" alt="Postscript to intermediate Raster format"></div></div><p> +</p><p> CUPS raster is a generic raster format with powerful features. It is able to include per-page information, color profiles and more to be used by the following downstream raster drivers. Its MIME type is @@ -8922,9 +8961,9 @@ printer models, should they choose to do so. CUPS always takes care for the first stage of rasterization so these vendors don't need to care about Ghostscript complications (in fact, there is currently more than one vendor financing the development of CUPS raster drivers). -</p><ns56:p> -</ns56:p><div class="figure"><a name="id2947366"></a><p class="title"><b>Figure 19.7. CUPS-raster production using Ghostscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/7small.png" alt="CUPS-raster production using Ghostscript"></div></div><ns56:p> -</ns56:p><p> +</p><p> +</p><div class="figure"><a name="id2938809"></a><p class="title"><b>Figure 19.7. CUPS-raster production using Ghostscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/7small.png" alt="CUPS-raster production using Ghostscript"></div></div><p> +</p><p> CUPS versions before version 1.1.15 were shipping a binary (or source code) standalone filter, named "pstoraster". pstoraster was derived from GNU Ghostscript 5.50, and could be installed besides and in @@ -8937,16 +8976,16 @@ integrated back into Ghostscript (now based on GNU Ghostscript version parameter. If your Ghostscript doesn't show a success on asking for <b class="command">gs -h |grep cups</b>, you might not be able to print. Update your Ghostscript then! -</p></div><div xmlns:ns57="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947440"></a>imagetops and imagetoraster</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938883"></a>imagetops and imagetoraster</h3></div></div><div></div></div><p> Above in the section about prefilters, we mentioned the prefilter that generates PostScript from image formats. The imagetoraster filter is used to convert directly from image to raster, without the intermediate PostScript stage. It is used more often than the above mentioned prefilters. Here is a summarizing flowchart of image file filtering: -</p><ns57:p> -</ns57:p><div class="figure"><a name="id2947461"></a><p class="title"><b>Figure 19.8. Image format to CUPS-raster format conversion</b></p><div class="mediaobject"><img src="projdoc/imagefiles/8small.png" alt="Image format to CUPS-raster format conversion"></div></div><ns57:p> -</ns57:p></div><div xmlns:ns58="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947495"></a>rasterto [printerspecific]</h3></div></div><div></div></div><p> +</p><p> +</p><div class="figure"><a name="id2938904"></a><p class="title"><b>Figure 19.8. Image format to CUPS-raster format conversion</b></p><div class="mediaobject"><img src="projdoc/imagefiles/8small.png" alt="Image format to CUPS-raster format conversion"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2938940"></a>rasterto [printers specific]</h3></div></div><div></div></div><p> CUPS ships with quite some different raster drivers processing CUPS raster. On my system I find in /usr/lib/cups/filter/ these: <i class="parameter"><tt>rastertoalps, rastertobj, rastertoepson, rastertoescp, @@ -8958,9 +8997,9 @@ than this; some of these are installed by commercial add-ons to CUPS <i class="parameter"><tt>rastertoprinter</tt></i>) by 3rd party driver development projects (such as Gimp-Print) wanting to cooperate as closely as possible with CUPS. -</p><ns58:p> -</ns58:p><div class="figure"><a name="id2947546"></a><p class="title"><b>Figure 19.9. Raster to Printer Specific formats</b></p><div class="mediaobject"><img src="projdoc/imagefiles/9small.png" alt="Raster to Printer Specific formats"></div></div><ns58:p> -</ns58:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947580"></a>CUPS Backends</h3></div></div><div></div></div><p> +</p><p> +</p><div class="figure"><a name="id2938988"></a><p class="title"><b>Figure 19.9. Raster to Printer Specific formats</b></p><div class="mediaobject"><img src="projdoc/imagefiles/9small.png" alt="Raster to Printer Specific formats"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939024"></a>CUPS Backends</h3></div></div><div></div></div><p> The last part of any CUPS filtering chain is a "backend". Backends are special programs that send the print-ready file to the final device. There is a separate backend program for any transfer @@ -9034,8 +9073,8 @@ PDF (through a "pdfgen:/" backend) or dump them to "/dev/null&quo fact I have the system-wide default printer set up to be connected to a "devnull:/" backend: there are just too many people sending jobs without specifying a printer, or scripts and programs which don't name -a printer. The system-wided default deletes the job and sends a polite -mail back to the $USER asking him to alsways specify a correct +a printer. The system-wide default deletes the job and sends a polite +mail back to the $USER asking him to always specify a correct printername). </p><p> Not all of the mentioned backends may be present on your system or @@ -9047,7 +9086,7 @@ all available backends: lpinfo -v -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947894"></a>cupsomatic/Foomatic -- how do they fit into the Picture?</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939336"></a>cupsomatic/Foomatic -- how do they fit into the Picture?</h3></div></div><div></div></div><p> "cupsomatic" filters may be the most widely used on CUPS installations. You must be clear about the fact that these were not developed by the CUPS people. They are a "Third Party" add-on to @@ -9068,7 +9107,7 @@ You can recognize these PPDs from the line calling the This line you may find amongst the first 40 or so lines of the PPD file. If you have such a PPD installed, the printer shows up in the CUPS web interface with a <span class="emphasis"><em>foomatic</em></span> namepart for -the driver description. cupsomatic is a Perlscript that runs +the driver description. cupsomatic is a Perl script that runs Ghostscript, with all the complicated commandline options auto-constructed from the selected PPD and commandline options give to the printjob. @@ -9097,11 +9136,11 @@ print-options from page to page, in the middle of a job. And the best thing is: the new foomatic-rip now works seamlessly with all legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing for them access to use PPDs for their printing! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947997"></a>The Complete Picture</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939448"></a>The Complete Picture</h3></div></div><div></div></div><p> If you want to see an overview over all the filters and how they relate to each other, the complete picture of the puzzle is at the end of this document. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948012"></a><tt class="filename">mime.convs</tt></h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939464"></a><tt class="filename">mime.convs</tt></h3></div></div><div></div></div><p> CUPS auto-constructs all possible filtering chain paths for any given MIME type, and every printer installed. But how does it decide in favor or against a specific alternative? (There may often be cases, @@ -9118,7 +9157,7 @@ cost. This is a very efficient way to limit the load of any CUPS server by setting an appropriate "FilterLimit" value. A FilterLimit of 200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows approximately 5 jobs maximum at a time. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948065"></a>"Raw" printing</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939517"></a>"Raw" printing</h3></div></div><div></div></div><p> You can tell CUPS to print (nearly) any file "raw". "Raw" means it will not be filtered. CUPS will send the file to the printer "as is" without bothering if the printer is able to digest it. Users need to @@ -9141,7 +9180,7 @@ CUPS will automatically treat each job sent to a queue as a "raw" one, if it can't find a PPD associated with the queue. However, CUPS will only send known MIME types (as defined in its own mime.types file) and refuse others. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948120"></a>"application/octet-stream" printing</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939571"></a>"application/octet-stream" printing</h3></div></div><div></div></div><p> Any MIME type with no rule in the <tt class="filename">/etc/cups/mime.types</tt> file is regarded as unknown or <span class="emphasis"><em>application/octet-stream</em></span> and will not be @@ -9191,7 +9230,7 @@ does not by default allow one to send deliberate (possibly binary) data to printing devices. (This could be easily abused to launch a Denial of Service attack on your printer(s), causing at least the loss of a lot of paper and ink...) "Unknown" data are regarded by CUPS -as<span class="emphasis"><em>MIME type</em></span> +as <span class="emphasis"><em>MIME type</em></span> <span class="emphasis"><em>application/octet-stream</em></span>. While you <span class="emphasis"><em>can</em></span> send data "raw", the MIME type for these must be one that is known to CUPS and an allowed one. The file @@ -9199,7 +9238,7 @@ be one that is known to CUPS and an allowed one. The file recognizes MIME types. The file <tt class="filename">/etc/cups/mime.convs</tt> decides which file conversion filter(s) may be applied to which MIME types. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948335"></a>PostScript Printer Descriptions (PPDs) for non-PS Printers</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2939786"></a>PostScript Printer Descriptions (PPDs) for non-PS Printers</h3></div></div><div></div></div><p> Originally PPDs were meant to be used for PostScript printers only. Here, they help to send device-specific commands and settings to the RIP which processes the jobfile. CUPS has extended this @@ -9242,9 +9281,9 @@ specific model supports): </p></dd><dt><span class="term">stcolor2.ppd</span></dt><dd><p>newer Epson Stylus Color printers </p></dd><dt><span class="term">stphoto.ppd</span></dt><dd><p>older Epson Stylus Photo printers </p></dd><dt><span class="term">stphoto2.ppd</span></dt><dd><p>newer Epson Stylus Photo printers -</p></dd><dt><span class="term">laserjet.ppd</span></dt><dd><p>all PCL printersFurther below is a discussion +</p></dd><dt><span class="term">laserjet.ppd</span></dt><dd><p>all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable fur use with CUPS. -</p></dd></dl></div></div><div xmlns:ns59="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948562"></a>Difference between <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> and +</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940015"></a>Difference between <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> and <span class="emphasis"><em>native CUPS</em></span> printing</h3></div></div><div></div></div><p> Native CUPS rasterization works in two steps. </p><div class="itemizedlist"><ul type="disc"><li><p> @@ -9257,9 +9296,9 @@ quality filters for this step, some are Free Software, some are Shareware/Non-Free, some are proprietary.</p></li></ul></div><p> Often this produces better quality (and has several more advantages) than other methods. -</p><ns59:p> -</ns59:p><div class="figure"><a name="id2948613"></a><p class="title"><b>Figure 19.10. cupsomatic/foomatic processing versus Native CUPS</b></p><div class="mediaobject"><img src="projdoc/imagefiles/10small.png" alt="cupsomatic/foomatic processing versus Native CUPS"></div></div><ns59:p> -</ns59:p><p> +</p><p> +</p><div class="figure"><a name="id2940065"></a><p class="title"><b>Figure 19.10. cupsomatic/foomatic processing versus Native CUPS</b></p><div class="mediaobject"><img src="projdoc/imagefiles/10small.png" alt="cupsomatic/foomatic processing versus Native CUPS"></div></div><p> +</p><p> One other method is the <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> way. Note that cupsomatic is <span class="emphasis"><em>not</em></span> made by the CUPS developers. It is an independent contribution to printing development, @@ -9269,7 +9308,7 @@ supported. It has now been replaced by <span class="emphasis"><em>foomatic-rip</em></span>. foomatic-rip is a complete re-write of the old cupsomatic idea, but very much improved and generalized to other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly -adviced, especially if you are upgrading to a recent version of CUPS +advised, especially if you are upgrading to a recent version of CUPS too. </p><p> Both the cupsomatic (old) and the foomatic-rip (new) methods from @@ -9286,14 +9325,14 @@ which works best for you. </p><p> cupsomatic "kidnaps" the printfile after the <span class="emphasis"><em>application/vnd.cups-postscript</em></span> stage and -deviates it through the CUPS-external, systemwide Ghostscript +deviates it through the CUPS-external, system wide Ghostscript installation: Therefore the printfile bypasses the "pstoraster" filter (and thus also bypasses the CUPS-raster-drivers "rastertosomething"). After Ghostscript finished its rasterization, cupsomatic hands the rendered file directly to the CUPS backend. The flowchart above illustrates the difference between native CUPS rendering and the Foomatic/cupsomatic method. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948719"></a>Examples for filtering Chains</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940170"></a>Examples for filtering Chains</h3></div></div><div></div></div><p> Here are a few examples of commonly occurring filtering chains to illustrate the workings of CUPS. </p><p> @@ -9343,7 +9382,7 @@ which transfers the job to the printers.</p></li></ul></div><p> The resulting filter chain therefore is: </p><pre class="screen"> pdftops --> pstops --> pstoraster --> rastertoepson --> usb -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948948"></a>Sources of CUPS drivers / PPDs</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940401"></a>Sources of CUPS drivers / PPDs</h3></div></div><div></div></div><p> On the internet you can find now many thousand CUPS-PPD files (with their companion filters), in many national languages, supporting more than 1000 non-PostScript models. @@ -9364,7 +9403,7 @@ roughly the same amount of printers in excellent quality;</p></li><li><p><a href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">OMNI (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</a> (LPGL, Free) is a package made by IBM, now containing support for more -than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow +than 400 printers, stemming from the inheritance of IBM OS/2 Know-How ported over to Linux (CUPS support is in a Beta-stage at present);</p></li><li><p><a href="http://hpinkjet.sourceforge.net/" target="_top">HPIJS (http://hpinkjet.sourceforge.net/)</a> (BSD-style licenses, Free) @@ -9378,7 +9417,7 @@ HPIJS).</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-r The cupsomatic/Foomatic trick from Linuxprinting.org works differently from the other drivers. This is explained elsewhere in this document. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949073"></a>Printing with Interface Scripts</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940530"></a>Printing with Interface Scripts</h3></div></div><div></div></div><p> CUPS also supports the usage of "interface scripts" as known from System V AT&T printing systems. These are often used for PCL printers, from applications that generate PCL print jobs. Interface @@ -9400,12 +9439,12 @@ with CUPS they provide the most easy way to plug in your own custom-written filtering script or program into one specific print queue (some information about the traditional usage of interface scripts is to be found at <a href="http://playground.sun.com/printing/documentation/interface.html" target="_top">http://playground.sun.com/printing/documentation/interface.html</a>). -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2949135"></a>Network printing (purely Windows)</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940605"></a>Network printing (purely Windows)</h2></div></div><div></div></div><p> Network printing covers a lot of ground. To understand what exactly goes on with Samba when it is printing on behalf of its Windows clients, let's first look at a "purely Windows" setup: Windows clients with a Windows NT print server. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949151"></a>From Windows Clients to an NT Print Server</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940620"></a>From Windows Clients to an NT Print Server</h3></div></div><div></div></div><p> Windows clients printing to an NT-based print server have two options. They may </p><div class="itemizedlist"><ul type="disc"><li><p>execute the driver locally and render the GDI output @@ -9414,7 +9453,7 @@ or</p></li><li><p>send the GDI output (EMF) to the server, where the driver is executed to render the printer specific output.</p></li></ul></div><p> Both print paths are shown in the flowcharts below. -</p></div><div xmlns:ns60="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949190"></a>Driver Execution on the Client</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940659"></a>Driver Execution on the Client</h3></div></div><div></div></div><p> In the first case the print server must spool the file as "raw", meaning it shouldn't touch the jobfile and try to convert it in any way. This is what traditional Unix-based print server can do too; and @@ -9424,9 +9463,9 @@ advantage of this setup is that this "spooling-only" print server may be used even if no driver(s) for Unix are available it is sufficient to have the Windows client drivers available and installed on the clients. -</p><ns60:p> -</ns60:p><div class="figure"><a name="id2949215"></a><p class="title"><b>Figure 19.11. Print Driver execution on the Client</b></p><div class="mediaobject"><img src="projdoc/imagefiles/11small.png" alt="Print Driver execution on the Client"></div></div><ns60:p> -</ns60:p></div><div xmlns:ns61="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949249"></a>Driver Execution on the Server</h3></div></div><div></div></div><p> +</p><p> +</p><div class="figure"><a name="id2940695"></a><p class="title"><b>Figure 19.11. Print Driver execution on the Client</b></p><div class="mediaobject"><img src="projdoc/imagefiles/11small.png" alt="Print Driver execution on the Client"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940731"></a>Driver Execution on the Server</h3></div></div><div></div></div><p> The other path executes the printer driver on the server. The clients transfers print files in EMF format to the server. The server uses the PostScript, PCL, ESC/P or other driver to convert the EMF file into @@ -9434,18 +9473,18 @@ the printer-specific language. It is not possible for Unix to do the same. Currently there is no program or method to convert a Windows client's GDI output on a Unix server into something a printer could understand. -</p><ns61:p> -</ns61:p><div class="figure"><a name="id2949271"></a><p class="title"><b>Figure 19.12. Print Driver execution on the Server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/12small.png" alt="Print Driver execution on the Server"></div></div><ns61:p> -</ns61:p><p> +</p><p> +</p><div class="figure"><a name="id2940753"></a><p class="title"><b>Figure 19.12. Print Driver execution on the Server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/12small.png" alt="Print Driver execution on the Server"></div></div><p> +</p><p> However, there is something similar possible with CUPS. Read on... -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2949312"></a>Network Printing (Windows clients -- UNIX/Samba Print +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2940794"></a>Network Printing (Windows clients -- UNIX/Samba Print Servers)</h2></div></div><div></div></div><p> Since UNIX print servers <span class="emphasis"><em>cannot</em></span> execute the Win32 program code on their platform, the picture is somewhat different. However, this doesn't limit your options all that much. In the contrary, you may have a way here to implement printing features which are not possible otherwise. -</p><div xmlns:ns62="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949333"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940814"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div><div></div></div><p> Here is a simple recipe showing how you can take advantage of CUPS powerful features for the benefit of your Windows network printing clients: @@ -9472,10 +9511,10 @@ other print commands are set up, then printing will use the option automatically passing through (if you want your own defined print commands to work with a Samba that has CUPS support compiled in, simply use <i class="parameter"><tt>printing = sysv</tt></i>). -</p><ns62:p> -</ns62:p><div class="figure"><a name="id2949459"></a><p class="title"><b>Figure 19.13. Printing via CUPS/samba server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/13small.png" alt="Printing via CUPS/samba server"></div></div><ns62:p> -</ns62:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949493"></a>Samba receiving Jobfiles and passing them to CUPS</h3></div></div><div></div></div><p> -Samba<span class="emphasis"><em>must</em></span> use its own spool directory (it is set +</p><p> +</p><div class="figure"><a name="id2940943"></a><p class="title"><b>Figure 19.13. Printing via CUPS/samba server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/13small.png" alt="Printing via CUPS/samba server"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2940978"></a>Samba receiving Jobfiles and passing them to CUPS</h3></div></div><div></div></div><p> +Samba <span class="emphasis"><em>must</em></span> use its own spool directory (it is set by a line similar to <i class="parameter"><tt>path = /var/spool/samba</tt></i>, in the <i class="parameter"><tt>[printers]</tt></i> or <i class="parameter"><tt>[printername]</tt></i> section of @@ -9492,7 +9531,7 @@ A Windows user authenticates only to Samba (by whatever means is configured). If Samba runs on the same host as CUPS, you only need to allow "localhost" to print. If they run on different machines, you need to make sure the Samba host gets access to printing on CUPS. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2949571"></a>Network PostScript RIP: CUPS Filters on Server -- clients use +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941054"></a>Network PostScript RIP: CUPS Filters on Server -- clients use PostScript Driver with CUPS-PPDs</h2></div></div><div></div></div><p> PPDs can control all print device options. They are usually provided by the manufacturer; if you own a PostScript printer, that is. PPD @@ -9512,7 +9551,7 @@ or see if you have lphelp on your system). There are also some different GUI frontends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant to be evaluated by the PostScript RIP on the real PostScript printer. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949626"></a>PPDs for non-PS Printers on UNIX</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941110"></a>PPDs for non-PS Printers on UNIX</h3></div></div><div></div></div><p> CUPS doesn't limit itself to "real" PostScript printers in its usage of PPDs. The CUPS developers have extended the scope of the PPD concept, to also describe available device and driver options for @@ -9529,7 +9568,7 @@ the supplied PostScript. Thus CUPS lets all its printers appear as PostScript devices to its clients, because it can act as a PostScript RIP for those printers, processing the received PostScript code into a proper raster print format. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949667"></a>PPDs for non-PS Printers on Windows</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941150"></a>PPDs for non-PS Printers on Windows</h3></div></div><div></div></div><p> CUPS-PPDs can also be used on Windows-Clients, on top of a "core" PostScript driver (now recommended is the "CUPS PostScript Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with @@ -9545,13 +9584,13 @@ which always remain unfiltered per definition;</p></li><li><p>enable clients to driver, even for many different target printers.</p></li></ul></div><p> Using CUPS PPDs on Windows clients enables these to control all print job settings just as a UNIX client can do too. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2949732"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941216"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div><div></div></div><p> This setup may be of special interest to people experiencing major problems in WTS environments. WTS need often a multitude of non-PostScript drivers installed to run their clients' variety of different printer models. This often imposes the price of much increased instability. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949750"></a>Printer Drivers running in "Kernel Mode" cause many +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941233"></a>Printer Drivers running in "Kernel Mode" cause many Problems</h3></div></div><div></div></div><p> The reason is that in Win NT printer drivers run in "Kernel Mode", this introduces a high risk for the stability of the system @@ -9568,7 +9607,7 @@ might be because there have so far only been 2 different PostScript drivers the ones from Adobe and the one from Microsoft. Both are very well tested and are as stable as you ever can imagine on Windows. The CUPS driver is derived from the Microsoft one. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949784"></a>Workarounds impose Heavy Limitations</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941268"></a>Workarounds impose Heavy Limitations</h3></div></div><div></div></div><p> In many cases, in an attempt to work around this problem, site administrators have resorted to restrict the allowed drivers installed on their WTS to one generic PCL- and one PostScript driver. This @@ -9576,7 +9615,7 @@ however restricts the clients in the amount of printer options available for them; often they can't get out more than simplex prints from one standard paper tray, while their devices could do much better, if driven by a different driver! ) -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949805"></a>CUPS: a "Magical Stone"?</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941289"></a>CUPS: a "Magical Stone"?</h3></div></div><div></div></div><p> Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these shortcomings. There are, depending on the version of Windows OS you use, up to 3 different PostScript @@ -9588,7 +9627,7 @@ is a certain price for this too: a CUPS server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as a "raw spooling" device. Plus, this setup is not yet widely tested, although the first feedbacks look very promising. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949832"></a>PostScript Drivers with no major problems -- even in Kernel +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941316"></a>PostScript Drivers with no major problems -- even in Kernel Mode</h3></div></div><div></div></div><p> More recent printer drivers on W2K and XP don't run in Kernel mode (unlike Win NT) any more. However, both operating systems can still @@ -9605,14 +9644,14 @@ development efforts. This is what the CUPS people have done. The license doesn't allow them to publish the whole of the source code. However, they have released the "diff" under the GPL, and if you are owner of an "MS DDK for Win NT", you can check the driver yourself. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2949866"></a> Setting up CUPS for driver Download</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2941369"></a> Setting up CUPS for driver Download</h2></div></div><div></div></div><p> As we have said before: all previously known methods to prepare client printer drivers on the Samba server for download and "Point'n'Print" convenience of Windows workstations are working with CUPS too. These methods were described in the previous chapter. In reality, this is a pure Samba business, and only relates to the Samba/Win client relationship. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949885"></a><span class="emphasis"><em>cupsaddsmb</em></span>: the unknown Utility</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941388"></a><span class="emphasis"><em>cupsaddsmb</em></span>: the unknown Utility</h3></div></div><div></div></div><p> The cupsaddsmb utility (shipped with all current CUPS versions) is an alternative method to transfer printer drivers into the Samba <i class="parameter"><tt>[print$]</tt></i> share. Remember, this share is where @@ -9627,7 +9666,7 @@ named in its man page. </p><p> The CUPS printer driver is available from the CUPS download site. Its package name is <tt class="filename">cups-samba-[version].tar.gz</tt> . It -is prefered over the Adobe drivers since it has a number of +is preferred over the Adobe drivers since it has a number of advantages: </p><div class="itemizedlist"><ul type="disc"><li><p>it supports a much more accurate page accounting;</p></li><li><p>it supports banner pages, and page labels on all @@ -9637,7 +9676,7 @@ job-billing)</p></li></ul></div><p> However, currently only Windows NT, 2000, and XP are supported by the CUPS drivers. You will need to get the respective part of Adobe driver too if you need to support Windows 95, 98, and ME clients. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2949976"></a>Prepare your <tt class="filename">smb.conf</tt> for +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941480"></a>Prepare your <tt class="filename">smb.conf</tt> for cupsaddsmb</h3></div></div><div></div></div><p> Prior to running cupsaddsmb, you need the following settings in <tt class="filename">smb.conf</tt>: @@ -9666,7 +9705,7 @@ Prior to running cupsaddsmb, you need the following settings in read only = yes write list = root -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950023"></a>CUPS Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941526"></a>CUPS Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><p> CUPS users may get the exactly same packages from<a href="http://www.cups.org/software.html" target="_top"><span class="emphasis"><em>http://www.cups.org/software.html</em></span></a>. It is a separate package from the CUPS base software files, tagged as <span class="emphasis"><em>CUPS 1.1.x Windows NT/2k/XP Printer Driver for SAMBA @@ -9737,7 +9776,7 @@ Studio 6. Driver developers are not allowed to distribute the whole of the source code as Free Software. However, CUPS developers released the "diff" in source code under the GPL, so anybody with a license of Visual Studio and a DDK will be able to compile for him/herself. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950220"></a>Recognize the different Driver Files</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941724"></a>Recognize the different Driver Files</h3></div></div><div></div></div><p> The CUPS drivers don't support the "older" Windows 95/98/ME, but only the Windows NT/2000/XP client: </p><pre class="screen"> @@ -9772,7 +9811,7 @@ support of WinNT/2k/XP are present in , the Adobe ones will be ignored and the CUPS ones will be used. If you prefer -- for whatever reason -- to use Adobe-only drivers, move away the 3 CUPS driver files. The Win95/98/ME clients use the Adobe drivers in any case. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950278"></a>Acquiring the Adobe Driver Files</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941782"></a>Acquiring the Adobe Driver Files</h3></div></div><div></div></div><p> Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on the Adobe website as single files and the self-extracting and/or self-installing Windows-exe is @@ -9785,7 +9824,7 @@ Generic PostScript printer. After this, the client's where you can get them with smbclient from the CUPS host. A more detailed description about this is in the next (the CUPS printing) chapter. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950311"></a>ESP Print Pro Package of "PostScript Driver for +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941814"></a>ESP Print Pro Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><p> Users of the ESP Print Pro software are able to install their "Samba Drivers" package for this purpose with no problem. Retrieve the driver @@ -9801,7 +9840,7 @@ driver files; i.e. mainly setup the <i class="parameter"><tt>[print$]</tt></i> share, etc. The ESP Print Pro package includes the CUPS driver files as well as a (licensed) set of Adobe drivers for the Windows 95/98/ME client family. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950361"></a>Caveats to be considered</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2941864"></a>Caveats to be considered</h3></div></div><div></div></div><p> Once you have run the install script (and possibly manually moved the <tt class="filename">cups.hlp</tt> file to <tt class="filename">/usr/share/cups/drivers/</tt>), the driver is @@ -9821,8 +9860,8 @@ working in an environment where everything is configured for Once the driver files are in the <i class="parameter"><tt>[print$]</tt></i> share and are initialized, they are ready to be downloaded and installed by the Win NT/2k/XP clients. -</p><div xmlns:ns63="" class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><ns63:p> -</ns63:p><div class="orderedlist"><ol type="1"><li><p> +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</p><div class="orderedlist"><ol type="1"><li><p> Win 9x/ME clients won't work with the CUPS PostScript driver. For these you'd still need to use the <tt class="filename">ADOBE*.*</tt> drivers as previously. @@ -9857,8 +9896,8 @@ as described elsewhere in the "Samba HOWTO Collection": either change a driver for an existing printer by running the "Printer Properties" dialog, or use <b class="command">rpcclient</b> with the <b class="command">setdriver</b> sub-command. -</p></li></ol></div><ns63:p> -</ns63:p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950582"></a>What are the Benefits of using the "CUPS PostScript Driver for +</p></li></ol></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942086"></a>What are the Benefits of using the "CUPS PostScript Driver for Windows NT/2k/XP" as compared to the Adobe Driver?</h3></div></div><div></div></div><p> You are interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes these are the most important @@ -9878,9 +9917,9 @@ the more special MIME type <span class="emphasis"><em>application/cups.vnd-postscript</em></span>), which therefore also leads to the page accounting in <span class="emphasis"><em>/var/log/cups/page_log</em></span> not -receiving the exact mumber of pages; instead the dummy page number +receiving the exact number of pages; instead the dummy page number of "1" is logged in a standard setup)</p></li><li><p>the Adobe driver has more options to "mis-configure" the -PostScript generated by it (like setting it inadvertedly to +PostScript generated by it (like setting it inadvertently to <span class="emphasis"><em>Optimize for Speed</em></span>, instead of <span class="emphasis"><em>Optimize for Portability</em></span>, which could lead to CUPS being unable to process it)</p></li><li><p>the CUPS PostScript driver output sent by Windows @@ -9904,7 +9943,7 @@ not disturb any other applications as they will regard it as a comment and simply ignore it).</p></li><li><p>the CUPS PostScript driver will be the heart of the fully fledged CUPS IPP client for Windows NT/2K/XP to be released soon (probably alongside the first Beta release for CUPS -1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950763"></a>Run "cupsaddsmb" (quiet Mode)</h3></div></div><div></div></div><p> +1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942268"></a>Run "cupsaddsmb" (quiet Mode)</h3></div></div><div></div></div><p> The cupsaddsmb command copies the needed files into your <i class="parameter"><tt>[print$]</tt></i> share. Additionally, the PPD associated with this printer is copied from @@ -9930,11 +9969,11 @@ Here is an example of a successfully run cupsaddsmb command. Password for root required to access localhost via SAMBA: [type in password 'secret'] </pre><p> -To share<span class="emphasis"><em>all</em></span> printers and drivers, use the +To share <span class="emphasis"><em>all</em></span> printers and drivers, use the <i class="parameter"><tt>-a</tt></i> parameter instead of a printer name. Since cupsaddsmb "exports" the printer drivers to Samba, it should be obvious that it only works for queues with a CUPS driver associated. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2950864"></a>Run "cupsaddsmb" with verbose Output</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942369"></a>Run "cupsaddsmb" with verbose Output</h3></div></div><div></div></div><p> Probably you want to see what's going on. Use the <i class="parameter"><tt>-v</tt></i> parameter to get a more verbose output. The output below was edited for better readability: all "\" at the end of @@ -10010,7 +10049,7 @@ unencrypted! Running command: rpcclient localhost -N -U'root%secret' \ -c 'setdriver infotec_2105 infotec_2105' cmd = setdriver infotec_2105 infotec_2105 - Succesfully set infotec_2105 to driver infotec_2105. + Successfully set infotec_2105 to driver infotec_2105. </pre><p> If you look closely, you'll discover your root password was transfered @@ -10019,7 +10058,7 @@ you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because the directories WIN40 and W32X86 already existed in the <i class="parameter"><tt>[print$]</tt></i> driver download share (from a previous driver installation). They are harmless here. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951007"></a>Understanding cupsaddsmb</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942596"></a>Understanding cupsaddsmb</h3></div></div><div></div></div><p> What has happened? What did cupsaddsmb do? There are five stages of the procedure </p><div class="orderedlist"><ol type="1"><li><p>call the CUPS server via IPP and request the @@ -10042,7 +10081,7 @@ same host): # cupsaddsmb -H sambaserver -h cupsserver -v printername -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951101"></a>How to recognize if cupsaddsm completed successfully</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942690"></a>How to recognize if cupsaddsm completed successfully</h3></div></div><div></div></div><p> You <span class="emphasis"><em>must</em></span> always check if the utility completed successfully in all fields. You need as a minimum these 3 messages amongst the output: @@ -10050,7 +10089,7 @@ amongst the output: installed.</em></span> # (for the W32X86 == WinNT/2K/XP architecture...)</p></li><li><p><span class="emphasis"><em>Printer Driver infotec_2105 successfully installed.</em></span> # (for the WIN40 == Win9x/ME -architecture...)</p></li><li><p><span class="emphasis"><em>Succesfully set [printerXPZ] to driver +architecture...)</p></li><li><p><span class="emphasis"><em>Successfully set [printerXPZ] to driver [printerXYZ].</em></span></p></li></ol></div><p> These messages probably not easily recognized in the general output. If you run cupsaddsmb with the <i class="parameter"><tt>-a</tt></i> @@ -10063,7 +10102,7 @@ It is impossible to see any diagnostic output if you don't run cupsaddsmb in verbose mode. Therefore we strongly recommend to not use the default quiet mode. It will hide any problems from you which might occur. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951188"></a>cupsaddsmb with a Samba PDC</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942777"></a>cupsaddsmb with a Samba PDC</h3></div></div><div></div></div><p> You can't get the standard cupsaddsmb command to run on a Samba PDC? You are asked for the password credential all over again and again and the command just will not take off at all? Try one of these @@ -10077,13 +10116,13 @@ variations: </pre><p> (Note the two backslashes: the first one is required to "escape" the second one). -</p></div><div xmlns:ns64="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951223"></a>cupsaddsmb Flowchart</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942812"></a>cupsaddsmb Flowchart</h3></div></div><div></div></div><p> Here is a chart about the procedures, commandflows and dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is not intended to, and does not work with, "raw" queues! -</p><ns64:p> -</ns64:p><div class="figure"><a name="id2951240"></a><p class="title"><b>Figure 19.14. cupsaddsmb flowchart</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="cupsaddsmb flowchart"></div></div><ns64:p> -</ns64:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951274"></a>Installing the PostScript Driver on a Client</h3></div></div><div></div></div><p> +</p><p> +</p><div class="figure"><a name="id2942830"></a><p class="title"><b>Figure 19.14. cupsaddsmb flowchart</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="cupsaddsmb flowchart"></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942865"></a>Installing the PostScript Driver on a Client</h3></div></div><div></div></div><p> After cupsaddsmb completed, your driver is prepared for the clients to use. Here are the steps you must perform to download and install it via "Point'n'Print". From a Windows client, browse to the CUPS/Samba @@ -10119,7 +10158,7 @@ functions. (Note that user "ntadmin" needs to be a valid Samba user with the required privileges to access the printershare) This would set up the printer connection in the traditional <span class="emphasis"><em>LanMan</em></span> way (not using MS-RPC). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951389"></a>Avoiding critical PostScript Driver Settings on the +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2942978"></a>Avoiding critical PostScript Driver Settings on the Client</h3></div></div><div></div></div><p> Soooo: printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, @@ -10130,7 +10169,7 @@ your print device is not PostScript-enabled, you are treating your Ghostscript installation on your CUPS host with the output your client driver settings produce. Treat it well: </p><div class="itemizedlist"><ul type="disc"><li><p>Avoid the <span class="emphasis"><em>PostScript Output Option: Optimize -for Speed</em></span> settting. Rather use the <span class="emphasis"><em>Optimize for +for Speed</em></span> setting. Rather use the <span class="emphasis"><em>Optimize for Portability</em></span> instead (Adobe PostScript driver).</p></li><li><p>Don't use the <span class="emphasis"><em>Page Independence: NO</em></span> setting. Instead use <span class="emphasis"><em>Page Independence @@ -10144,8 +10183,8 @@ Font</em></span> (for exotic fonts you may need to change it back to get a printout at all) (Adobe)</p></li><li><p>Sometimes you can choose <span class="emphasis"><em>PostScript Language Level</em></span>: in case of problems try <span class="emphasis"><em>2</em></span> instead of <span class="emphasis"><em>3</em></span> (the latest ESP Ghostscript package -handels Level 3 PostScript very well) (Adobe).</p></li><li><p>Say <span class="emphasis"><em>Yes</em></span> to <span class="emphasis"><em>PostScript -Error Handler</em></span> (Adobe)</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2951523"></a>Installing PostScript Driver Files manually (using +handles Level 3 PostScript very well) (Adobe).</p></li><li><p>Say <span class="emphasis"><em>Yes</em></span> to <span class="emphasis"><em>PostScript +Error Handler</em></span> (Adobe)</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2943112"></a>Installing PostScript Driver Files manually (using rpcclient)</h2></div></div><div></div></div><p> Of course you can run all the commands which are embedded into the cupsaddsmb convenience utility yourself, one by one, and hereby upload @@ -10164,9 +10203,9 @@ sub-commands. <b class="command">enumprinters</b>, the most interesting ones. rpcclient implements an important part of the MS-RPC protocol. You can use it to query (and command) a Win NT (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other -things, to benefit from the "Point'n' Print" features. Samba can now +things, to benefit from the "Point'n'Print" features. Samba can now mimic this too. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951638"></a>A Check of the rpcclient man Page</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943227"></a>A Check of the rpcclient man Page</h3></div></div><div></div></div><p> First let's have a little check of the rpcclient man page. Here are two relevant passages: </p><p> @@ -10199,7 +10238,7 @@ printer driver associated with an installed printer. The printer driver must already be correctly installed on the print server. </p><p> See also the enumprinters and enumdrivers commands for obtaining a list of installed printers and drivers. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951750"></a>Understanding the rpcclient man Page</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943340"></a>Understanding the rpcclient man Page</h3></div></div><div></div></div><p> The <span class="emphasis"><em>exact</em></span> format isn't made too clear by the man page, since you have to deal with some parameters containing spaces. Here is a better description for it. We have line-broken the @@ -10235,7 +10274,7 @@ box now, and access it from a UNIX workstation. We will query it with <b class="command">rpcclient</b> to see what it tells us and try to understand the man page more clearly which we've read just now. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951829"></a>Producing an Example by querying a Windows Box</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943429"></a>Producing an Example by querying a Windows Box</h3></div></div><div></div></div><p> We could run <b class="command">rpcclient</b> with a <b class="command">getdriver</b> or a <b class="command">getprinter</b> subcommand (in level 3 verbosity) against it. Just sit down at UNIX or @@ -10280,9 +10319,9 @@ Some printer drivers list additional files under the label <span class="emphasis"><em>ListOfFiles,Comma-separated</em></span>. For the CUPS PostScript drivers we don't need any (nor would we for the Adobe PostScript driver): therefore the field will get a "NULL" entry. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2951919"></a>What is required for adddriver and setdriver to succeed</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943519"></a>What is required for adddriver and setdriver to succeed</h3></div></div><div></div></div><p> From the manpage (and from the quoted output -of<span class="emphasis"><em>cupsaddsmb</em></span>, above) it becomes clear that you +of <span class="emphasis"><em>cupsaddsmb</em></span>, above) it becomes clear that you need to have certain conditions in order to make the manual uploading and initializing of the driver files succeed. The two rpcclient subcommands (<b class="command">adddriver</b> and @@ -10311,12 +10350,12 @@ rpcclient. A long-standing bug prevented a proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember this in case you've created the CUPS printer just shortly ago and encounter problems: try restarting -Samba.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952081"></a>Manual Commandline Driver Installation in 15 little Steps</h3></div></div><div></div></div><p> +Samba.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2943682"></a>Manual Commandline Driver Installation in 15 little Steps</h3></div></div><div></div></div><p> We are going to install a printer driver now by manually executing all required commands. As this may seem a rather complicated process at first, we go through the procedure step by step, explaining every single action item as it comes up. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952098"></a>First Step: Install the Printer on CUPS</h4></div></div><div></div></div><pre class="screen"> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943698"></a>First Step: Install the Printer on CUPS</h4></div></div><div></div></div><pre class="screen"> # lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P /home/kurt/canonIR85.ppd @@ -10325,7 +10364,7 @@ This installs printer with the name <span class="emphasis"><em>mysmbtstprn</em>< to the CUPS system. The printer is accessed via a socket (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root for this step -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952128"></a>Second Step (optional): Check if the Printer is recognized by +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943729"></a>Second Step (optional): Check if the Printer is recognized by Samba</h4></div></div><div></div></div><pre class="screen"> # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn @@ -10346,7 +10385,7 @@ already. You need to know root's Samba password (as set by the following steps. Alternatively you can authenticate as one of the users from the "write list" as defined in <tt class="filename">smb.conf</tt> for <i class="parameter"><tt>[print$]</tt></i>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952191"></a>Third Step (optional): Check if Samba knows a Driver for the +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943792"></a>Third Step (optional): Check if Samba knows a Driver for the Printer</h4></div></div><div></div></div><pre class="screen"> # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver @@ -10372,7 +10411,7 @@ This step was done for the purpose of demonstrating this condition. An attempt to connect to the printer at this stage will prompt the message along the lines: "The server has not the required printer driver installed". -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952229"></a>Fourth Step: Put all required Driver Files into Samba's +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943830"></a>Fourth Step: Put all required Driver Files into Samba's [print$]</h4></div></div><div></div></div><pre class="screen"> # smbclient //localhost/print\$ -U 'root%xxxx' \ @@ -10391,7 +10430,7 @@ present in the <i class="parameter"><tt>[print$]</tt></i> share. However, client would still not be able to install them, because Samba does not yet treat them as driver files. A client asking for the driver would still be presented with a "not installed here" message. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952280"></a>Fifth Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen"> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943881"></a>Fifth Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen"> # ls -l /etc/samba/drivers/W32X86/ total 669 @@ -10405,7 +10444,7 @@ be presented with a "not installed here" message. </pre><p> The driver files now are in the W32X86 architecture "root" of <i class="parameter"><tt>[print$]</tt></i>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952318"></a>Sixth Step: Tell Samba that these are +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943920"></a>Sixth Step: Tell Samba that these are <span class="emphasis"><em>Driver</em></span> Files (<b class="command">adddriver</b>)</h4></div></div><div></div></div><pre class="screen"> @@ -10426,7 +10465,7 @@ driver. It is normally a good idea to use the same name as is used for the printername; however, in big installations you may use this driver for a number of printers which have obviously different names. So the name of the driver is not fixed. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952373"></a>Seventh Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen"> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2943974"></a>Seventh Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen"> # ls -l /etc/samba/drivers/W32X86/ total 1 @@ -10445,7 +10484,7 @@ name of the driver is not fixed. </pre><p> Notice how step 6 did also move the driver files to the appropriate subdirectory. Compare with the situation after step 5. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952406"></a>Eighth Step (optional): Verify if Samba now recognizes the +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944008"></a>Eighth Step (optional): Verify if Samba now recognizes the Driver</h4></div></div><div></div></div><pre class="screen"> # rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost | grep -B2 -A5 mydrivername @@ -10462,7 +10501,7 @@ Driver</h4></div></div><div></div></div><pre class="screen"> </pre><p> Remember, this command greps for the name you did choose for the driver in step Six. This command must succeed before you can proceed. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952439"></a>Ninth Step: Tell Samba which Printer should use these Driver +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944041"></a>Ninth Step: Tell Samba which Printer should use these Driver Files (<b class="command">setdriver</b>)</h4></div></div><div></div></div><pre class="screen"> # rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost @@ -10476,7 +10515,7 @@ driver. You don't need to repeat all the previous steps for the setdriver command to succeed. The only pre-conditions are: <b class="command">enumdrivers</b> must find the driver and <b class="command">enumprinters</b> must find the printer. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952490"></a>Tenth Step (optional): Verify if Samba has this Association +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944091"></a>Tenth Step (optional): Verify if Samba has this Association recognized</h4></div></div><div></div></div><pre class="screen"> # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver @@ -10518,7 +10557,7 @@ Compare these results with the ones from steps 2 and 3. Note that every single of these commands show the driver is installed. Even the <b class="command">enumprinters</b> command now lists the driver on the "description" line. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952546"></a>Eleventh Step (optional): Tickle the Driver into a correct +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944171"></a>Eleventh Step (optional): Tickle the Driver into a correct Device Mode</h4></div></div><div></div></div><p> You certainly know how to install the driver on the client. In case you are not particularly familiar with Windows, here is a short @@ -10543,7 +10582,7 @@ into the "DOS box" (type root's smbpassword when prompted): Change any printer setting once (like <span class="emphasis"><em>"portrait" --> "landscape"</em></span>), click "Apply"; change the setting back. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952607"></a>Twelveth Step: Install the Printer on a Client +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944235"></a>Twelfth Step: Install the Printer on a Client ("Point'n'Print")</h4></div></div><div></div></div><pre class="screen"> C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn" @@ -10551,24 +10590,24 @@ back. </pre><p> If it doesn't work it could be a permission problem with the <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="id2952638"></a>Thirteenth Step (optional): Print a Test Page</h4></div></div><div></div></div><pre class="screen"> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944268"></a>Thirteenth Step (optional): Print a Test Page</h4></div></div><div></div></div><pre class="screen"> C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn" </pre><p> Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again and march to the printer. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952663"></a>Fourteenth Step (recommended): Study the Test Page</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944295"></a>Fourteenth Step (recommended): Study the Test Page</h4></div></div><div></div></div><p> Hmmm.... just kidding! By now you know everything about printer installations and you don't need to read a word. Just put it in a frame and bolt it to the wall with the heading "MY FIRST RPCCLIENT-INSTALLED PRINTER" - why not just throw it away! -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2952681"></a>Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944313"></a>Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your Success</h4></div></div><div></div></div><pre class="screen"> # echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd -</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952701"></a>Troubleshooting revisited</h3></div></div><div></div></div><p> +</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944334"></a>Troubleshooting revisited</h3></div></div><div></div></div><p> The setdriver command will fail, if in Samba's mind the queue is not already there. You had promising messages about the: </p><pre class="screen"> @@ -10611,7 +10650,7 @@ An alternative command could be this: </pre><p> BTW, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too! -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2952803"></a>The printing <tt class="filename">*.tdb</tt> Files</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944435"></a>The printing <tt class="filename">*.tdb</tt> Files</h2></div></div><div></div></div><p> Some mystery is associated with the series of files with a tdb-suffix appearing in every Samba installation. They are <tt class="filename">connections.tdb</tt>, @@ -10626,7 +10665,7 @@ tdb-suffix appearing in every Samba installation. They are <tt class="filename">ntprinters.tdb</tt>, <tt class="filename">sessionid.tdb</tt> and <tt class="filename">secrets.tdb</tt>. What is their purpose? -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952906"></a>Trivial DataBase Files</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944537"></a>Trivial DataBase Files</h3></div></div><div></div></div><p> A Windows NT (Print) Server keeps track of all information needed to serve its duty toward its clients by storing entries in the Windows "Registry". Client queries are answered by reading from the registry, @@ -10639,7 +10678,7 @@ or <tt class="filename">/var/lock/samba/</tt> . The printing related files are <tt class="filename">ntprinters.tdb</tt>, <tt class="filename">printing.tdb</tt>,<tt class="filename">ntforms.tdb</tt> and <tt class="filename">ntdrivers.tdb</tt>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2952976"></a>Binary Format</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944608"></a>Binary Format</h3></div></div><div></div></div><p> <tt class="filename">*.tdb</tt> files are not human readable. They are written in a binary format. "Why not ASCII?", you may ask. "After all, ASCII configuration files are a good and proofed tradition on UNIX." @@ -10652,7 +10691,7 @@ same time</em></span>. The file format of Samba's <tt class="filename">*.tdb</tt> files allows for this provision. Many smbd processes may write to the same <tt class="filename">*.tdb</tt> file at the same time. This wouldn't be possible with pure ASCII files. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953038"></a>Losing <tt class="filename">*.tdb</tt> Files</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944670"></a>Losing <tt class="filename">*.tdb</tt> Files</h3></div></div><div></div></div><p> It is very important that all <tt class="filename">*.tdb</tt> files remain consistent over all write and read accesses. However, it may happen that these files <span class="emphasis"><em>do</em></span> get corrupted. (A @@ -10662,7 +10701,7 @@ etc.). In cases of trouble, a deletion of the old printing-related <tt class="filename">*.tdb</tt> files may be the only option. You need to re-create all print related setup after that. Or you have made a backup of the <tt class="filename">*.tdb</tt> files in time. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953097"></a>Using <span class="emphasis"><em>tdbbackup</em></span></h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944728"></a>Using <span class="emphasis"><em>tdbbackup</em></span></h3></div></div><div></div></div><p> Samba ships with a little utility which helps the root user of your system to back up your <tt class="filename">*.tdb</tt> files. If you run it with no argument, it prints a little usage message: @@ -10674,7 +10713,7 @@ with no argument, it prints a little usage message: Version:3.0a -h this help message -s suffix set the backup suffix - -v veryify mode (restore if corrupt) + -v verify mode (restore if corrupt) </pre><p> Here is how I backed up my printing.tdb file: @@ -10692,7 +10731,7 @@ Here is how I backed up my printing.tdb file: -rw------- 1 root root 40960 May 2 03:44 printing.tdb -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak -</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2953159"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div><div></div></div><p> +</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2944795"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div><div></div></div><p> CUPS ships with good support for HP LaserJet type printers. You can install the generic driver as follows: </p><pre class="screen"> @@ -10726,13 +10765,13 @@ not work with PPDs generated for the old cupsomatic. The new-style PPDs are 100% compliant to the Adobe PPD specification. They are intended to be used by Samba and the cupsaddsmb utility also, to provide the driver files for the Windows clients also! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953265"></a>foomatic-rip and Foomatic explained</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2944903"></a>foomatic-rip and Foomatic explained</h3></div></div><div></div></div><p> Nowadays most Linux distros rely on the utilities of Linuxprinting.org to create their printing related software (which, BTW, works on all UNIXes and on Mac OS X or Darwin too). It is not known as well as it should be, that it also has a very end-user friendly interface which allows for an easy update of drivers and PPDs, for all supported -models, all spoolers, all operatings systems and all package formats +models, all spoolers, all operating systems and all package formats (because there is none). Its history goes back a few years. </p><p> Recently Foomatic has achieved the astonishing milestone of <a href="http://www.linuxprinting.org/printer_list.cgi?make=Anyone" target="_top">1000 @@ -10743,7 +10782,7 @@ its <a href="http://www.linuxprinting.org/foomatic.html" target="_top">Foomatic< database. Currently there are <a href="http://www.linuxprinting.org/driver_list.cgi" target="_top">245 drivers</a> in the database: many drivers support various models, and many models may be driven by different drivers; it's your choice! -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953320"></a>690 "perfect" Printers</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944958"></a>690 "perfect" Printers</h4></div></div><div></div></div><p> At present there are 690 devices dubbed as working "perfectly", 181 "mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind that most of these are non-PostScript models (PostScript printers are @@ -10751,10 +10790,10 @@ automatically supported supported by CUPS to perfection, by using their own manufacturer-provided Windows-PPD...), and that a multifunctional device never qualifies as working "perfectly" if it doesn't also scan and copy and fax under GNU/Linux: then this is a -truely astonishing achievement. Three years ago the number was not +truly astonishing achievement. Three years ago the number was not more than 500, and Linux or UNIX "printing" at the time wasn't anywhere near the quality it is today! -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953345"></a>How the "Printing HOWTO" started it all</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2944982"></a>How the "Printing HOWTO" started it all</h4></div></div><div></div></div><p> A few years ago <a href="http://www2.picante.com:81/~gtaylor/" target="_top">Grant Taylor</a> started it all. The roots of today's Linuxprinting.org are in the first <a href="http://www.linuxprinting.org/foomatic2.9/howto/" target="_top">Linux Printing @@ -10768,7 +10807,7 @@ hardware and driver zoo that made up Linux printing of the time. This database became the core component of today's Foomatic collection of tools and data. In the meantime it has moved to an XML representation of the data. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953390"></a>Foomatic's strange Name</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945028"></a>Foomatic's strange Name</h4></div></div><div></div></div><p> "Why the funny name?", you ask. When it really took off, around spring 2000, CUPS was far less popular than today, and most systems used LPD, LPRng or even PDQ to print. CUPS shipped with a few generic "drivers" @@ -10791,7 +10830,7 @@ developments available for CUPS;</p></li><li><p>It made available a lot of addit to CUPS users (because often the "traditional" Ghostscript way of printing was the only one available);</p></li><li><p>It gave all the advanced CUPS options (web interface, GUI driver configurations) to users wanting (or needing) to use -Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953457"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div><div></div></div><p> +Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945095"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div><div></div></div><p> CUPS worked through a quickly-hacked up filter script named <a href="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&show=0" target="_top">cupsomatic</a>. cupsomatic ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed. It just @@ -10825,7 +10864,7 @@ Foomatic up to versions 2.0.x required (ugly) Perl data structures attached the Linuxprinting.org PPDs for CUPS. It had a different "*omatic" script for every spooler, as well as different printer configuration files.. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953589"></a>7.13.1.5.The <span class="emphasis"><em>Grand Unification</em></span> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945229"></a>7.13.1.5.The <span class="emphasis"><em>Grand Unification</em></span> achieved...</h4></div></div><div></div></div><p> This all has changed in Foomatic versions 2.9 (Beta) and released as "stable" 3.0. This has now achieved the convergence of all *omatic @@ -10861,7 +10900,7 @@ sizes for many printers; and it will support printing on media drawn from different paper trays within the same job (in both cases: even where there is no support for this from Windows-based vendor printer drivers). -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953677"></a>Driver Development outside</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945316"></a>Driver Development outside</h4></div></div><div></div></div><p> Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent maintainers. Linuxprinting.org just pools all the information, and stores it in its @@ -10884,7 +10923,7 @@ effort, started by Michael Sweet (also lead developer for CUPS), now directed by Robert Krawitz, which has achieved an amazing level of photo print quality (many Epson users swear that its quality is better than the vendor drivers provided by Epson for the Microsoft -platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953755"></a>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and +platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945397"></a>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and commercial Unix</h4></div></div><div></div></div><p> Linuxprinting.org today is the one-stop "shop" to download printer drivers. Look for printer information and <a href="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/" target="_top">tutorials</a> @@ -10905,7 +10944,7 @@ of the Foomatic project. Till Kamppeter from MandrakeSoft is doing an excellent job in his spare time to maintain Linuxprinting.org and Foomatic. So if you use it often, please send him a note showing your appreciation. -</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2953828"></a>Foomatic Database generated PPDs</h4></div></div><div></div></div><p> +</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2945467"></a>Foomatic Database generated PPDs</h4></div></div><div></div></div><p> The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver information, but it is organized in a way that it can generate "PPD" files "on the fly" from @@ -10930,7 +10969,7 @@ GUI tools (like KDE's marvellous <a href="http://printing.kde.org/overview/kprin or the GNOME <a href="http://gtklp.sourceforge.net/" target="_top">"gtklp"</a>, "xpp" and the CUPS web interface) read the PPD too and use this information to present the available settings to the user as an intuitive menu selection. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953893"></a>foomatic-rip and Foomatic-PPD Download and Installation</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2945532"></a>foomatic-rip and Foomatic-PPD Download and Installation</h3></div></div><div></div></div><p> Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus" compatible printer in CUPS (note that recent distributions of SuSE, UnitedLinux and Mandrake may ship with a complete package of @@ -11029,7 +11068,7 @@ the driver/model) contain support for a certain "device", representing the selected "driver" for your model (as shown by "gs -h")</p></li><li><p>foomatic-rip needs a new version of PPDs (PPD versions produced for cupsomatic don't work with -foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954351"></a>Page Accounting with CUPS</h2></div></div><div></div></div><p> +foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2945993"></a>Page Accounting with CUPS</h2></div></div><div></div></div><p> Often there are questions regarding "print quotas" wherein Samba users (that is, Windows clients) should not be able to print beyond a certain amount of pages or data volume per day, week or month. This @@ -11042,7 +11081,7 @@ Of course one could "hack" things with one's own scripts. But then there is CUPS. CUPS supports "quotas" which can be based on sizes of jobs or on the number of pages or both, and are spanning any time period you want. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954382"></a>Setting up Quotas</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946024"></a>Setting up Quotas</h3></div></div><div></div></div><p> This is an example command how root would set a print quota in CUPS, assuming an existing printer named "quotaprinter": </p><pre class="screen"> @@ -11053,7 +11092,7 @@ assuming an existing printer named "quotaprinter": This would limit every single user to print 100 pages or 1024 KB of data (whichever comes first) within the last 604,800 seconds ( = 1 week). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954413"></a>Correct and incorrect Accounting</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946056"></a>Correct and incorrect Accounting</h3></div></div><div></div></div><p> For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, otherwise it uses a "dummy" count of "1". Some printfiles don't pass it (eg: image files) but then those are mostly 1 @@ -11068,7 +11107,7 @@ printer is a non-PostScript model, you need to let CUPS do the job to convert the file to a print-ready format for the target printer. This will be working for currently about 1,000 different printer models, see <a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a>). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954454"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946097"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div><div></div></div><p> Before CUPS-1.1.16 your only option was to use the Adobe PostScript Driver on the Windows clients. The output of this driver was not always passed through the "pstops" filter on the CUPS/Samba side, and @@ -11088,7 +11127,7 @@ printfile</p></li></ul></div><p> You can read more about the setup of this combination in the manpage for "cupsaddsmb" (which is only present with CUPS installed, and only current from CUPS 1.1.16). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954526"></a>The page_log File Syntax</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946169"></a>The page_log File Syntax</h3></div></div><div></div></div><p> These are the items CUPS logs in the "page_log" for every single <span class="emphasis"><em>page</em></span> of a job: </p><div class="itemizedlist"><ul type="disc"><li><p>Printer name</p></li><li><p>User name</p></li><li><p>Job ID</p></li><li><p>Time of printing</p></li><li><p>the page number</p></li><li><p>the number of copies</p></li><li><p>a billing information string @@ -11110,7 +11149,7 @@ This was job ID "401", printed on "infotec_IS2027" by user & from IP address 10.160.50.13. The next job had ID "402", was sent by user "boss" from IP address 10.160.51.33,printed from one page 440 copies and is set to be billed to "finance-dep". -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954628"></a>Possible Shortcomings</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946270"></a>Possible Shortcomings</h3></div></div><div></div></div><p> What flaws or shortcomings are there with this quota system? </p><div class="itemizedlist"><ul type="disc"><li><p>the ones named above (wrongly logged job in case of printer hardware failure, etc.)</p></li><li><p>in reality, CUPS counts the job pages that are being @@ -11124,7 +11163,7 @@ groups</p></li><li><p>no means to read out the current balance or the "used-up" number of current quota</p></li><li><p>a user having used up 99 sheets of 100 quota will still be able to send and print a 1,000 sheet job</p></li><li><p>a user being denied a job because of a filled-up quota doesn't get a meaningful error message from CUPS other than -"client-error-not-possible".</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954699"></a>Future Developments</h3></div></div><div></div></div><p> +"client-error-not-possible".</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946341"></a>Future Developments</h3></div></div><div></div></div><p> This is the best system currently available, and there are huge improvements under development for CUPS 1.2: </p><div class="itemizedlist"><ul type="disc"><li><p>page counting will go into the "backends" (these talk @@ -11132,9 +11171,9 @@ directly to the printer and will increase the count in sync with the actual printing process: thus a jam at the 5th sheet will lead to a stop in the counting)</p></li><li><p>quotas will be handled more flexibly</p></li><li><p>probably there will be support for users to inquire their "accounts" in advance</p></li><li><p>probably there will be support for some other tools -around this topic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954747"></a>Other Accounting Tools</h3></div></div><div></div></div><p> +around this topic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946390"></a>Other Accounting Tools</h3></div></div><div></div></div><p> PrintAnalyzer, pyKota, printbill, LogReport. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954762"></a>Additional Material</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2946404"></a>Additional Material</h2></div></div><div></div></div><p> A printer queue with <span class="emphasis"><em>no</em></span> PPD associated to it is a "raw" printer and all files will go directly there as received by the spooler. The exceptions are file types "application/octet-stream" @@ -11212,7 +11251,7 @@ the jobs of hundreds of users on some big machine, where no user is allowed to have direct access (such as when the operators often need to load the proper paper type before running the 10,000 page job requested by marketing for the mailing, etc.). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954956"></a>Auto-Deletion or Preservation of CUPS Spool Files</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2946598"></a>Auto-Deletion or Preservation of CUPS Spool Files</h2></div></div><div></div></div><p> Samba print files pass through two "spool" directories. One is the incoming directory managed by Samba, (set in the <span class="emphasis"><em>path = /var/spool/samba</em></span> directive in the @@ -11221,7 +11260,7 @@ incoming directory managed by Samba, (set in the <span class="emphasis"><em>path your UNIX print subsystem. For CUPS it is normally <tt class="filename">/var/spool/cups/</tt>, as set by the cupsd.conf directive <tt class="filename">RequestRoot /var/spool/cups</tt>. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955001"></a>CUPS Configuration Settings explained</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946644"></a>CUPS Configuration Settings explained</h3></div></div><div></div></div><p> Some important parameter settings in the CUPS configuration file <tt class="filename">cupsd.conf</tt> are: </p><div class="variablelist"><dl><dt><span class="term">PreserveJobHistory Yes</span></dt><dd><p> @@ -11245,7 +11284,7 @@ maximum to 0 disables this functionality. The default setting is </p></dd></dl></div><p> (There are also additional settings for "MaxJobsPerUser" and "MaxJobsPerPrinter"...) -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955083"></a>Pre-conditions</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946726"></a>Pre-conditions</h3></div></div><div></div></div><p> For everything to work as announced, you need to have three things: </p><div class="itemizedlist"><ul type="disc"><li><p>a Samba-smbd which is compiled against "libcups" (Check @@ -11256,15 +11295,15 @@ In this case all other manually set printing-related commands (like "print command", "lpq command", "lprm command", "lppause command" or "lpresume command") are ignored and they should normally have no influence what-so-ever on your printing. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955144"></a>Manual Configuration</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946787"></a>Manual Configuration</h3></div></div><div></div></div><p> If you want to do things manually, replace the "printing = cups" by "printing = bsd". Then your manually set commands may work (haven't tested this), and a "print command = lp -d %P %s; rm %s" may do what you need. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2955162"></a>When <span class="emphasis"><em>not</em></span> to use Samba to print to +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2946805"></a>When <span class="emphasis"><em>not</em></span> to use Samba to print to CUPS</h2></div></div><div></div></div><p> [TO BE DONE] -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2955180"></a>In Case of Trouble.....</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="id2946822"></a>In Case of Trouble.....</h2></div></div><div></div></div><p> If you have more problems, post the output of these commands to the CUPS or Samba mailing lists (choose the one which seems more relevant to your problem): @@ -11280,13 +11319,13 @@ compact way. Don't forget to name the CUPS and Samba versions you are using! This saves bandwidth and makes for easier readability for experts (and you are expecting experts to read them, right? ;-) -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955214"></a>Where to find Documentation</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946857"></a>Where to find Documentation</h3></div></div><div></div></div><p> [TO BE DONE] -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955227"></a>How to ask for Help</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946870"></a>How to ask for Help</h3></div></div><div></div></div><p> [TO BE DONE] -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955240"></a>Where to find Help</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946883"></a>Where to find Help</h3></div></div><div></div></div><p> [TO BE DONE] -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2955254"></a>Appendix</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955261"></a>Printing <span class="emphasis"><em>from</em></span> CUPS to Windows attached +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2946896"></a>Appendix</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2946904"></a>Printing <span class="emphasis"><em>from</em></span> CUPS to Windows attached Printers</h3></div></div><div></div></div><p> From time to time the question arises, how you can print <span class="emphasis"><em>to</em></span> a Windows attached printer @@ -11374,7 +11413,7 @@ doesn't require a password! Printing will only work if you have a working netbios name resolution up and running. Note that this is a feature of CUPS and you don't necessarily need to have smbd running (but who wants that? :-). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955455"></a>More CUPS filtering Chains</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947118"></a>More CUPS filtering Chains</h3></div></div><div></div></div><p> The following diagrams reveal how CUPS handles print jobs. </p><pre class="screen"> ######################################################################### @@ -11665,7 +11704,7 @@ The following diagrams reveal how CUPS handles print jobs. # CUPS and ESP PrintPro plug-in where rastertosomething is noted. # ########################################################################## -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955709"></a>Trouble Shooting Guidelines to fix typical Samba printing +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2947424"></a>Trouble Shooting Guidelines to fix typical Samba printing Problems</h3></div></div><div></div></div><p> This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from @@ -11778,35 +11817,35 @@ three dialogs <span class="emphasis"><em>look</em></span> the same. Only one of <span class="emphasis"><em>does</em></span> what you intend. You need to be Administrator or Print Administrator to do this for all users. Here is how I do in on XP: -</p><div class="orderedlist"><ol type="A"><li xmlns:ns65=""><ns65:p>The first "wrong" way: +</p><div class="orderedlist"><ol type="A"><li><p>The first "wrong" way: -</ns65:p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></span> +</p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></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="emphasis"><em>Printing Preferences...</em></span></p></li><li><p>Look at this dialog closely and remember what it looks -like.</p></li></ol></div><ns65:p> -</ns65:p></li><li xmlns:ns66=""><ns66:p>The second "wrong" way: +like.</p></li></ol></div><p> +</p></li><li><p>The second "wrong" way: -</ns66:p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></span> +</p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></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="emphasis"><em>Properties</em></span></p></li><li><p>Click on the <span class="emphasis"><em>General</em></span> tab</p></li><li><p>Click on the button <span class="emphasis"><em>Printing Preferences...</em></span></p></li><li><p>A new dialog opens. Keep this dialog open and go back -to the parent dialog.</p></li></ol></div><ns66:p> -</ns66:p></li><li xmlns:ns67=""><ns67:p>The third, the "correct" way: (should you do +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) -</ns67:p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="emphasis"><em>Advanced</em></span> +</p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="emphasis"><em>Advanced</em></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="emphasis"><em>Printing Defaults...</em></span> button.</p></li><li><p>On any of the two new tabs, click on the <span class="emphasis"><em>Advanced...</em></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><ns67:p> -</ns67:p></li></ol></div><p> +identical looking one from "B.5" or A.3".</p></li></ol></div><p> +</p></li></ol></div><p> Do you see any difference? I don't either... However, only the last one, which you arrived at with steps "C.1.-6." will save any settings permanently and be the defaults for new users. If you want all clients @@ -11889,65 +11928,82 @@ Windows box with a shared PostScript printer: <b class="command">smbclient <tt class="filename">W32X86/2</tt> subdir to <b class="command">mget ADOBE*</b> and other files or to <tt class="filename">WIN40/0</tt> to do the same. -- Another option is to download the <tt class="filename">*.exe</tt> packaged -files from the Adobe website.</p></dd></dl></div></div><div xmlns:ns68="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956815"></a>An Overview of the CUPS Printing Processes</h3></div></div><div></div></div><ns68:p> -</ns68:p><div class="figure"><a name="id2956826"></a><p class="title"><b>Figure 19.15. CUPS Printing Overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/a_small.png" alt="CUPS Printing Overview"></div></div><ns68:p> -</ns68:p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter 20. Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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">Alexander</span> <span class="surname">Bokovoy</span></h3></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></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2958218">Features and Benefits</a></dt><dt><a href="#id2958235">Discussion</a></dt><dt><a href="#id2958286">Included modules</a></dt><dd><dl><dt><a href="#id2956883">audit</a></dt><dt><a href="#id2956922">extd_audit</a></dt><dt><a href="#id2957044">fake_perms</a></dt><dt><a href="#id2957063">recycle</a></dt><dt><a href="#id2957202">netatalk</a></dt></dl></dd><dt><a href="#id2957247">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2957269">DatabaseFS</a></dt><dt><a href="#id2957323">vscan</a></dt></dl></dd><dt><a href="#id2957352">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958218"></a>Features and Benefits</h2></div></div><div></div></div><p> +files from the Adobe website.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2948546"></a>An Overview of the CUPS Printing Processes</h3></div></div><div></div></div><p> +</p><div class="figure"><a name="id2948557"></a><p class="title"><b>Figure 19.15. CUPS Printing Overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/a_small.png" alt="CUPS Printing Overview"></div></div><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="VFS"></a>Chapter 20. Stackable VFS modules</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2960717">Features and Benefits</a></dt><dt><a href="#id2960735">Discussion</a></dt><dt><a href="#id2960826">Included modules</a></dt><dd><dl><dt><a href="#id2960833">audit</a></dt><dt><a href="#id2960871">extd_audit</a></dt><dt><a href="#id2960995">fake_perms</a></dt><dt><a href="#id2961013">recycle</a></dt><dt><a href="#id2961151">netatalk</a></dt></dl></dd><dt><a href="#id2961195">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2961218">DatabaseFS</a></dt><dt><a href="#id2961273">vscan</a></dt></dl></dd><dt><a href="#id2961303">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960717"></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 xmlns:ns69="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958235"></a>Discussion</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960735"></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><ns69:p> +</p><p> To use the VFS modules, create a share similar to the one below. The -important parameter is the <i class="parameter"><tt>vfs object</tt></i> parameter which must point to -the exact pathname of the shared library objects. For example, to log all access -to files and use a recycle bin: +important parameter is the <b class="command">vfs objects</b> 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: -</ns69:p><pre class="programlisting"> +</p><pre class="programlisting"> [audit] - comment = Audited /data directory - path = /data - vfs object = /path/to/audit.so /path/to/recycle.so - writeable = yes - browseable = yes -</pre><ns69:p> -</ns69:p><p> -The modules are used in the order they are specified. -</p><p> -Further documentation on writing VFS modules for Samba can be found in -the Samba Developers Guide. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958286"></a>Included modules</h2></div></div><div></div></div><div xmlns:ns70="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956883"></a>audit</h3></div></div><div></div></div><ns70:p> + comment = Audited /data directory + path = /data + vfs objects = audit recycle + writeable = yes + browseable = yes +</pre><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><pre class="programlisting"> +[test] + comment = VFS TEST + path = /data + writeable = yes + browseable = yes + vfs objects = example:example1 example example:test + example1: parameter = 1 + example: parameter = 5 + test: parameter = 7 +</pre><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2960826"></a>Included modules</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960833"></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: - </ns70:p><table class="simplelist" border="0" summary="Simple list"><tr><td>share</td></tr><tr><td>connect/disconnect</td></tr><tr><td>directory opens/create/remove</td></tr><tr><td>file open/close/rename/unlink/chmod</td></tr></table><ns70:p> - </ns70:p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956922"></a>extd_audit</h3></div></div><div></div></div><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td>share</td></tr><tr><td>connect/disconnect</td></tr><tr><td>directory opens/create/remove</td></tr><tr><td>file open/close/rename/unlink/chmod</td></tr></table><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960871"></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. + 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 <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="id2956961"></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="id2957044"></a>fake_perms</h3></div></div><div></div></div><p> + </p><div class="table"><a name="id2960912"></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="id2960995"></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 xmlns:ns71="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957063"></a>recycle</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961013"></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. - </p><ns71:p>Supported options: - </ns71:p><div class="variablelist"><dl><dt><span class="term">vfs_recycle_bin:repository</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:keeptree</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:versions</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:touch</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:maxsize</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:exclude</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:exclude_dir</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:noversions</span></dt><dd><p>FIXME</p></dd></dl></div><ns71:p> - </ns71:p></div><div xmlns:ns72="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957202"></a>netatalk</h3></div></div><div></div></div><p> + </p><p>Supported options: + </p><div class="variablelist"><dl><dt><span class="term">recycle:repository</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:keeptree</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:versions</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:touch</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:maxsize</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:exclude</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:exclude_dir</span></dt><dd><p>FIXME</p></dd><dt><span class="term">recycle:noversions</span></dt><dd><p>FIXME</p></dd></dl></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961151"></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><ns72:p>Advantages compared to the old netatalk module: - </ns72:p><table class="simplelist" border="0" summary="Simple list"><tr><td>it doesn't care about creating of .AppleDouble forks, just keeps them in sync</td></tr><tr><td>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</td></tr></table><ns72:p> - </ns72:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957247"></a>VFS modules available elsewhere</h2></div></div><div></div></div><p> + </p><p>Advantages compared to the old netatalk module: + </p><table class="simplelist" border="0" summary="Simple list"><tr><td>it doesn't care about creating of .AppleDouble forks, just keeps them in sync</td></tr><tr><td>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</td></tr></table><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2961195"></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 @@ -11955,7 +12011,7 @@ to have his or her own CVS tree). </p><p> No statements about the stability or functionality of any module should be implied due to its presence here. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957269"></a>DatabaseFS</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961218"></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 @@ -11970,15 +12026,15 @@ should be implied due to its presence here. Any feedback would be appreciated: comments, suggestions, patches, etc... If nothing else, hopefully it might prove useful for someone else who wishes to create a virtual filesystem. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957323"></a>vscan</h3></div></div><div></div></div><p>URL: <a href="http://www.openantivirus.org/" target="_top">http://www.openantivirus.org/</a></p><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961273"></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 couse, Samba has to be compiled with VFS support. + 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 class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957352"></a>Common Errors</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2961303"></a>Common Errors</h2></div></div><div></div></div><p> There must be some gotchas we should record here! Jelmer??? -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter 21. Integrated Logon Support using Winbind</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><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">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="#id2957847">Features and Benefits</a></dt><dt><a href="#id2957875">Introduction</a></dt><dt><a href="#id2959857">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2959916">Target Uses</a></dt></dl></dd><dt><a href="#id2959947">How Winbind Works</a></dt><dd><dl><dt><a href="#id2959975">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2960008">Microsoft Active Directory Services</a></dt><dt><a href="#id2960031">Name Service Switch</a></dt><dt><a href="#id2957393">Pluggable Authentication Modules</a></dt><dt><a href="#id2957465">User and Group ID Allocation</a></dt><dt><a href="#id2957499">Result Caching</a></dt></dl></dd><dt><a href="#id2957528">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2957555">Introduction</a></dt><dt><a href="#id2957630">Requirements</a></dt><dt><a href="#id2958907">Testing Things Out</a></dt></dl></dd><dt><a href="#id2963255">Conclusion</a></dt><dt><a href="#id2963274">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957847"></a>Features and Benefits</h2></div></div><div></div></div><p>Integration of UNIX and Microsoft Windows NT through +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter 21. Integrated Logon Support using Winbind</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><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">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="#id2962201">Features and Benefits</a></dt><dt><a href="#id2962229">Introduction</a></dt><dt><a href="#id2962301">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2962361">Target Uses</a></dt></dl></dd><dt><a href="#id2962392">How Winbind Works</a></dt><dd><dl><dt><a href="#id2962420">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2962454">Microsoft Active Directory Services</a></dt><dt><a href="#id2962477">Name Service Switch</a></dt><dt><a href="#id2962613">Pluggable Authentication Modules</a></dt><dt><a href="#id2962685">User and Group ID Allocation</a></dt><dt><a href="#id2962720">Result Caching</a></dt></dl></dd><dt><a href="#id2962747">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2962776">Introduction</a></dt><dt><a href="#id2962851">Requirements</a></dt><dt><a href="#id2962944">Testing Things Out</a></dt></dl></dd><dt><a href="#id2964563">Conclusion</a></dt><dt><a href="#id2964582">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962201"></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. We present <span class="emphasis"><em>winbind</em></span>, a component of the Samba suite @@ -11988,7 +12044,7 @@ There must be some gotchas we should record here! Jelmer??? Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind system, explaining the functionality it provides, how it is configured, - and how it works internally.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957875"></a>Introduction</h2></div></div><div></div></div><p>It is well known that UNIX and Microsoft Windows NT have + and how it works internally.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962229"></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 @@ -12009,7 +12065,7 @@ There must be some gotchas we should record here! Jelmer??? 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="id2959857"></a>What Winbind Provides</h2></div></div><div></div></div><p>Winbind unifies UNIX and Windows NT account management by + problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962301"></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 @@ -12033,7 +12089,7 @@ There must be some gotchas we should record here! Jelmer??? 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="id2959916"></a>Target Uses</h3></div></div><div></div></div><p>Winbind is targeted at organizations that have an + location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962361"></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 @@ -12043,12 +12099,12 @@ There must be some gotchas we should record here! Jelmer??? 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="id2959947"></a>How Winbind Works</h2></div></div><div></div></div><p>The winbind system is designed around a client/server + the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962392"></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="id2959975"></a>Microsoft Remote Procedure Calls</h3></div></div><div></div></div><p>Over the last few years, efforts have been underway + in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962420"></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 @@ -12061,7 +12117,7 @@ There must be some gotchas we should record here! Jelmer??? 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="id2960008"></a>Microsoft Active Directory Services</h3></div></div><div></div></div><p> + NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962454"></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. @@ -12070,7 +12126,7 @@ There must be some gotchas we should record here! Jelmer??? 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="id2960031"></a>Name Service Switch</h3></div></div><div></div></div><p>The Name Service Switch, or NSS, is a feature that is + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962477"></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 @@ -12107,7 +12163,7 @@ passwd: files example is to put <tt class="filename">libnss_winbind.so</tt> in <tt class="filename">/lib/</tt> then add "winbind" into <tt class="filename">/etc/nsswitch.conf</tt> at the appropriate place. The C library will then call Winbind to - resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957393"></a>Pluggable Authentication Modules</h3></div></div><div></div></div><p>Pluggable Authentication Modules, also known as PAM, + resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962613"></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 @@ -12132,7 +12188,7 @@ passwd: files example is copied to <tt class="filename">/lib/security/</tt> and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957465"></a>User and Group ID Allocation</h3></div></div><div></div></div><p>When a user or group is created under Windows NT + for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962685"></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 @@ -12145,7 +12201,7 @@ passwd: files example time, winbind will have mapped all Windows NT users and groups to UNIX user ids and group ids.</p><p>The results of this mapping are stored persistently in an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957499"></a>Result Caching</h3></div></div><div></div></div><p>An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962720"></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 @@ -12156,14 +12212,14 @@ passwd: files example the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information is discarded and up to date information is requested directly - from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2957528"></a>Installation and Configuration</h2></div></div><div></div></div><p> + from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962747"></a>Installation and Configuration</h2></div></div><div></div></div><p> Many thanks to John Trostel <a href="mailto:jtrostel@snapserver.com" target="_top">jtrostel@snapserver.com</a> for providing the HOWTO for this section. </p><p> This HOWTO describes how to get winbind services up and running to control access and authenticate users on your Linux box using the winbind services which come with SAMBA 3.0. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957555"></a>Introduction</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962776"></a>Introduction</h3></div></div><div></div></div><p> This section describes the procedures used to get winbind up and running on a RedHat 7.1 system. Winbind is capable of providing access and authentication control for Windows Domain users through an NT @@ -12188,15 +12244,15 @@ somewhat to fit the way your distribution works. 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="id2957630"></a>Requirements</h3></div></div><div></div></div><p> -If you have a samba configuration file that you are currently + </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962851"></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 yourmachine. That's why you want to be able to boot back +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. ;-) @@ -12215,7 +12271,7 @@ winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that means <tt class="filename">pam-0.74-22</tt>. For best results, it is helpful to also install the development packages in <tt class="filename">pam-devel-0.74-22</tt>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958907"></a>Testing Things Out</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962944"></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 @@ -12226,7 +12282,7 @@ services, several pam libraries, and the <tt class="filename">/usr/doc</tt> and <tt class="filename">/usr/man</tt> entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2958968"></a>Configure and compile SAMBA</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963006"></a>Configure and compile SAMBA</h4></div></div><div></div></div><p> The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon whether or not you have previously built the Samba binaries. @@ -12241,19 +12297,19 @@ whether or not you have previously built the Samba binaries. This will, by default, install SAMBA in <tt class="filename">/usr/local/samba</tt>. See the main SAMBA documentation if you want to install SAMBA somewhere else. It will also build the winbindd executable and libraries. -</p></div><div xmlns:ns73="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2959080"></a>Configure <tt class="filename">nsswitch.conf</tt> and the +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963118"></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><ns73:p> -</ns73:p><pre class="screen"> +</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><ns73:p> -</ns73:p><p> +</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"> +</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> @@ -12276,7 +12332,7 @@ is faster (and you don't need to reboot) if you do it manually: </p><p> This makes <tt class="filename">libnss_winbind</tt> available to winbindd and echos back a check to you. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2959288"></a>NSS Winbind on AIX</h4></div></div><div></div></div><p>(This section is only for those running AIX)</p><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963326"></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 @@ -12296,7 +12352,7 @@ Programming Concepts for AIX": <a href="http://publibn.boulder.ibm.com/doc_ 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="id2959359"></a>Configure smb.conf</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963405"></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 @@ -12309,16 +12365,16 @@ include the following entries in the [global] section: # separate domain and username with '+', like DOMAIN+username <a href="winbindd.8.html#WINBINDSEPARATOR" target="_top">winbind separator</a> = + # use uids from 10000 to 20000 for domain users - <a href="winbindd.8.html#WINBINDUID" target="_top">winbind uid</a> = 10000-20000 + <a href="winbindd.8.html#WINBINDUID" target="_top">idmap uid</a> = 10000-20000 # use gids from 10000 to 20000 for domain groups - <a href="winbindd.8.html#WINBINDGID" target="_top">winbind gid</a> = 10000-20000 + <a href="winbindd.8.html#WINBINDGID" target="_top">idmap gid</a> = 10000-20000 # allow enumeration of winbind users and groups <a href="winbindd.8.html#WINBINDENUMUSERS" target="_top">winbind enum users</a> = yes <a href="winbindd.8.html#WINBINDENUMGROUP" target="_top">winbind enum groups</a> = yes # give winbind users a real shell (only needed if they have telnet access) <a href="winbindd.8.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> = /home/winnt/%D/%U <a href="winbindd.8.html#TEMPLATESHELL" target="_top">template shell</a> = /bin/bash -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2959473"></a>Join the SAMBA server to the PDC domain</h4></div></div><div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963522"></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 @@ -12329,7 +12385,7 @@ a domain user who has administrative privileges in the domain. The proper response to the command should be: "Joined the domain <i class="replaceable"><tt>DOMAIN</tt></i>" where <i class="replaceable"><tt>DOMAIN</tt></i> is your DOMAIN name. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962315"></a>Start up the winbindd daemon and test it!</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963576"></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 @@ -12401,7 +12457,7 @@ directories and default shells. The same thing can be done for groups with the command </p><p> <tt class="prompt">root# </tt><b class="userinput"><tt>getent group</tt></b> -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962555"></a>Fix the init.d startup scripts</h4></div></div><div></div></div><div xmlns:ns74="" class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2962563"></a>Linux</h5></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2963817"></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="id2963825"></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. @@ -12432,18 +12488,18 @@ start() { touch /var/lock/subsys/smb || RETVAL=1 return $RETVAL } -</pre><ns74:p>If you would like to run winbindd in dual daemon mode, replace +</pre><p>If you would like to run winbindd in dual daemon mode, replace the line -</ns74:p><pre class="programlisting"> +</p><pre class="programlisting"> daemon /usr/local/samba/bin/winbindd -</pre><ns74:p> +</pre><p> in the example above with: -</ns74:p><pre class="programlisting"> +</p><pre class="programlisting"> daemon /usr/local/samba/bin/winbindd -B -</pre><ns74:p>. -</ns74:p><p> +</pre><p>. +</p><p> The 'stop' function has a corresponding entry to shut down the services and looks like this: </p><pre class="programlisting"> @@ -12467,7 +12523,7 @@ stop() { echo "" return $RETVAL } -</pre></div><div xmlns:ns75="" class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2962708"></a>Solaris</h5></div></div><div></div></div><p>Winbind doesn't work on solaris 9, see the <a href="#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><p>On solaris, you need to modify the +</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2963987"></a>Solaris</h5></div></div><div></div></div><p>Winbind doesn't work on Solaris 9, see the <a href="#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><p>On Solaris, you need to modify the <tt class="filename">/etc/init.d/samba.server</tt> startup script. It usually only starts smbd and nmbd but should now start winbindd too. If you have samba installed in <tt class="filename">/usr/local/samba/bin</tt>, @@ -12519,22 +12575,22 @@ the file could contains something like this: echo "Usage: /etc/init.d/samba.server { start | stop }" ;; esac -</pre><ns75:p> +</pre><p> Again, if you would like to run samba in dual daemon mode, replace -</ns75:p><pre class="programlisting"> +</p><pre class="programlisting"> /usr/local/samba/bin/winbindd -</pre><ns75:p> +</pre><p> in the script above with: -</ns75:p><pre class="programlisting"> +</p><pre class="programlisting"> /usr/local/samba/bin/winbindd -B -</pre><ns75:p> -</ns75:p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2962797"></a>Restarting</h5></div></div><div></div></div><p> +</pre><p> +</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2964105"></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="id2962833"></a>Configure Winbind and PAM</h4></div></div><div></div></div><p> +</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2964142"></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 @@ -12554,9 +12610,9 @@ your other pam security modules. On my RedHat system, this was the modules reside in <tt class="filename">/usr/lib/security</tt>. </p><p> <tt class="prompt">root# </tt><b class="userinput"><tt>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</tt></b> -</p><div xmlns:ns76="" class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2962940"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><div></div></div><p> +</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2964248"></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 fileas it was: +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 @@ -12610,14 +12666,14 @@ same way. It now looks like this: 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><ns76:p> -In this case, I added the </ns76:p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><ns76:p> -lines as before, but also added the </ns76:p><pre class="programlisting">required pam_securetty.so</pre><ns76:p> +</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 <b class="command">sufficient /lib/security/pam_unix.so use_first_pass</b> line after the <b class="command">winbind.so</b> line to get rid of annoying double prompts for passwords. -</ns76:p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2963163"></a>Solaris-specific configuration</h5></div></div><div></div></div><p> +</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2964472"></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 @@ -12689,12 +12745,12 @@ annoying double prompts for passwords. </p><p> Now restart your Samba and try connecting through your application that you configured in the pam.conf. -</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963255"></a>Conclusion</h2></div></div><div></div></div><p>The winbind system, through the use of the Name Service +</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964563"></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="id2963274"></a>Common Errors</h2></div></div><div></div></div><p>Winbind has a number of limitations in its current + cost of running a mixed UNIX and NT network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964582"></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 and IRIX operating systems, although ports to other operating @@ -12709,11 +12765,11 @@ configured in the pam.conf. containing this information is corrupted or destroyed.</p></li><li><p>Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter 22. Advanced Network Manangement</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">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2964647">Features and Benefits</a></dt><dt><a href="#id2964678">Remote Server Administration</a></dt><dt><a href="#id2963360">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2963377">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2963579">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2963774">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2963806">Common Errors</a></dt></dl></div><p> + instead up to the PDC to enforce.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter 22. Advanced Network Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2967075">Features and Benefits</a></dt><dt><a href="#id2967264">Remote Server Administration</a></dt><dt><a href="#id2967363">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2967381">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2967592">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2967788">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2967822">Common Errors</a></dt></dl></div><p> This section documents peripheral issues that are of great importance to network administrators who want to improve network resource access control, to automate the user environment, and to make their lives a little easier. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964647"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2967075"></a>Features and Benefits</h2></div></div><div></div></div><p> Often the difference between a working network environment and a well appreciated one can best be measured by the <span class="emphasis"><em>little things</em></span> that makes everything work more harmoniously. A key part of every network environment solution is the ability to remotely @@ -12723,7 +12779,7 @@ network operations. </p><p> This chapter presents information on each of these area. They are placed here, and not in other chapters, for ease of reference. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964678"></a>Remote Server Administration</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2967264"></a>Remote Server Administration</h2></div></div><div></div></div><p> <span class="emphasis"><em>How do I get 'User Manager' and 'Server Manager'?</em></span> </p><p> Since I don't need to buy an <span class="application">NT4 Server</span>, how do I get the 'User Manager for Domains', @@ -12737,30 +12793,30 @@ Click here to download the archived file <a href="ftp://ftp.microsoft.com/Softli The <span class="application">Windows NT 4.0</span> version of the 'User Manager for Domains' and 'Server Manager' are available from Microsoft via ftp from <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</a> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963360"></a>Remote Desktop Management</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2967363"></a>Remote Desktop Management</h2></div></div><div></div></div><p> There are a number of possible remote desktop management solutions that range from free through costly. Do not let that put you off. Sometimes the most costly solutions is the most cost effective. In any case, you will need to draw your own conclusions as to which is the best tool in your network environment. -</p><div xmlns:ns77="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963377"></a>Remote Management from NoMachines.Com</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2967381"></a>Remote Management from NoMachines.Com</h3></div></div><div></div></div><p> The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003. It is presented in slightly edited form (with author details omitted for privacy reasons). The entire answer is reproduced below with some comments removed. - </p><ns77:p> -</ns77:p><pre class="screen"> -> I have a wounderfull linux/samba server running as pdc for a network. -> Now I would like to add remote desktop capabilites so that + </p><p> +</p><pre class="screen"> +> I have a wonderful linux/samba server running as PDC for a network. +> Now I would like to add remote desktop capabilities so that > users outside could login to the system and get their desktop up from > home or another country.. > -> Is there a way to acomplish this? Do I need a windows terminal server? +> Is there a way to accomplish this? Do I need a windows terminal server? > Do I need to configure it so that it is a member of the domain or a > BDC,PDC? Are there any hacks for MS Windows XP to enable remote login > even if the computer is in a domain? > > Any ideas/experience would be appreciated :) -</pre><ns77:p> -</ns77:p><p> +</pre><p> +</p><p> Answer provided: Check out the new offer from NoMachine, "NX" software: <a href="http://www.nomachine.com/" target="_top">http://www.nomachine.com/</a>. </p><p> @@ -12772,7 +12828,7 @@ is the best tool in your network environment. a new way of compression and caching technologies which makes the thing fast enough to run even over slow modem/ISDN connections. </p><p> - I could testdrive their (public) RedHat machine in Italy, over a loaded + I could test drive their (public) RedHat machine in Italy, over a loaded internet connection, with enabled thumbnail previews in KDE konqueror which popped up immediately on "mouse-over". From inside that (remote X) session I started a rdesktop session on another, a Windows XP machine. @@ -12789,7 +12845,7 @@ is the best tool in your network environment. in Italy) to my Mozilla mailing agent... These guys are certainly doing something right! </p><p> - I recommend to testdrive NX to anybody with a only a remote interest + I recommend to test drive NX to anybody with a only a remote interest in remote computing <a href="http://www.nomachine.com/testdrive.php" target="_top">http://www.nomachine.com/testdrive.php</a>. </p><p> @@ -12808,7 +12864,7 @@ is the best tool in your network environment. </p><p> Now the best thing at the end: all the core compression and caching technologies are released under the GPL and available as source code - to anybody who wants to build on it! These technolgies are working, + to anybody who wants to build on it! These technologies are working, albeit started from the command line only (and very inconvenient to use in order to get a fully running remote X session up and running....) </p><p> @@ -12830,22 +12886,22 @@ is the best tool in your network environment. NoMachine are encouraging and offering help to OSS/Free Software implementations for such a frontend too, even if it means competition to them (they have written to this effect even to the LTSP, KDE and GNOME developer mailing lists) - </p></li></ul></div></div></div><div xmlns:ns78="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963579"></a>Network Logon Script Magic</h2></div></div><div></div></div><p> + </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2967592"></a>Network Logon Script Magic</h2></div></div><div></div></div><p> This section needs work. Volunteer contributions most welcome. Please send your patches or updates to <a href="mailto:jht@samba.org" target="_top">John Terpstra</a>. </p><p> There are several opportunities for creating a custom network startup configuration environment. -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>No Logon Script</td></tr><tr><td>Simple universal Logon Script that applies to all users</td></tr><tr><td>Use of a conditional Logon Script that applies per user or per group attirbutes</td></tr><tr><td>Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>No Logon Script</td></tr><tr><td>Simple universal Logon Script that applies to all users</td></tr><tr><td>Use of a conditional Logon Script that applies per user or per group attributes</td></tr><tr><td>Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create a custom Logon Script and then execute it.</td></tr><tr><td>User of a tool such as KixStart</td></tr></table><p> The Samba source code tree includes two logon script generation/execution tools. See <tt class="filename">examples</tt> directory <tt class="filename">genlogon</tt> and <tt class="filename">ntlogon</tt> subdirectories. </p><p> The following listings are from the genlogon directory. -</p><ns78:p> +</p><p> This is the <tt class="filename">genlogon.pl</tt> file: -</ns78:p><pre class="programlisting"> +</p><pre class="programlisting"> #!/usr/bin/perl # # genlogon.pl @@ -12917,29 +12973,29 @@ This is the <tt class="filename">genlogon.pl</tt> file: # All done! Close the output file. close LOGON; -</pre><ns78:p> -</ns78:p><p> +</pre><p> +</p><p> Those wishing to use more elaborate or capable logon processing system should check out the following sites: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></td></tr><tr><td><a href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></td></tr><tr><td><a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.asp?scid=kb;en-us;189105</a></td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963774"></a>Adding printers without user intervention</h3></div></div><div></div></div><ns78:p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a href="http://www.craigelachie.org/rhacer/ntlogon" target="_top">http://www.craigelachie.org/rhacer/ntlogon</a></td></tr><tr><td><a href="http://www.kixtart.org" target="_top">http://www.kixtart.org</a></td></tr><tr><td><a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.asp?scid=kb;en-us;189105</a></td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2967788"></a>Adding printers without user intervention</h3></div></div><div></div></div><p> Printers may be added automatically during logon script processing through the use of: -</ns78:p><pre class="programlisting"> +</p><pre class="programlisting"> rundll32 printui.dll,PrintUIEntry /? -</pre><ns78:p> +</pre><p> See the documentation in the <a href="http://support.microsoft.com/default.asp?scid=kb;en-us;189105" target="_top">Microsoft knowledgebase article no: 189105</a>. -</ns78:p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963806"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2967822"></a>Common Errors</h2></div></div><div></div></div><p> The information provided in this chapter has been reproduced from postings on the samba@samba.org mailing list. No implied endorsement or recommendation is offered. Administrators should conduct their own evaluation of alternatives and are encouraged to draw their own conclusions. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter 23. System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2964204">Features and Benefits</a></dt><dt><a href="#id2964256">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2964367">Windows 9x/Me Policies</a></dt><dt><a href="#id2963915">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2964048">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2965490">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2965591">Samba Editreg Toolset</a></dt><dt><a href="#id2965611">Windows NT4/200x</a></dt><dt><a href="#id2965631">Samba PDC</a></dt></dl></dd><dt><a href="#id2965676">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2965823">Common Errors</a></dt><dd><dl><dt><a href="#id2965837">Policy Does Not Work</a></dt></dl></dd></dl></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter 23. System and Account Policies</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2966885">Features and Benefits</a></dt><dt><a href="#id2966939">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2968722">Windows 9x/Me Policies</a></dt><dt><a href="#id2968817">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2968950">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2969202">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2969303">Samba Editreg Toolset</a></dt><dt><a href="#id2969324">Windows NT4/200x</a></dt><dt><a href="#id2969344">Samba PDC</a></dt></dl></dd><dt><a href="#id2969388">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2969535">Common Errors</a></dt><dd><dl><dt><a href="#id2969549">Policy Does Not Work</a></dt></dl></dd></dl></div><p> This chapter summarises the current state of knowledge derived from personal practice and knowledge from samba mailing list subscribers. Before reproduction of posted information effort has been made to validate the information provided. Where additional information was uncovered through this validation it is provided also. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964204"></a>Features and Benefits</h2></div></div><div></div></div><p> -When MS Windows NT3.5 was introduced the hot new topic was the ability to implmement +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2966885"></a>Features and Benefits</h2></div></div><div></div></div><p> +When MS Windows NT3.5 was introduced the hot new topic was the ability to implement Group Policies for users and group. Then along came MS Windows NT4 and a few sites started to adopt this capability. How do we know that? By way of the number of "booboos" (or mistakes) administrators made and then requested help to resolve. @@ -12959,7 +13015,7 @@ network client workstations. </p><p> A tool new to Samba-3 may become an important part of the future Samba Administrators' arsenal. The <b class="command">editreg</b> tool is described in this document. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964256"></a>Creating and Managing System Policies</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2966939"></a>Creating and Managing System Policies</h2></div></div><div></div></div><p> Under MS Windows platforms, particularly those following the release of MS Windows NT4 and MS Windows 95) it is possible to create a type of file that would be placed in the NETLOGON share of a domain controller. As the client logs onto the network @@ -12970,7 +13026,7 @@ affect users, groups of users, or machines. For MS Windows 9x/Me this file must be called <tt class="filename">Config.POL</tt> and may be generated using a tool called <tt class="filename">poledit.exe</tt>, better known as the Policy Editor. The policy editor was provided on the Windows 98 installation CD, but -dissappeared again with the introduction of MS Windows Me (Millenium Edition). From +disappeared again with the introduction of MS Windows Me (Millennium Edition). From comments from MS Windows network administrators it would appear that this tool became a part of the MS Windows Me Resource Kit. </p><p> @@ -12994,7 +13050,7 @@ be read and understood. Try searching on the Microsoft web site for "Group </p><p> What follows is a very brief discussion with some helpful notes. The information provided here is incomplete - you are warned. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964367"></a>Windows 9x/Me Policies</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2968722"></a>Windows 9x/Me Policies</h3></div></div><div></div></div><p> You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. It can be found on the Original full product Win98 installation CD under <tt class="filename">tools/reskit/netadmin/poledit</tt>. Install this using the @@ -13020,7 +13076,7 @@ here is incomplete - you are warned. <tt class="filename">grouppol.inf</tt>. Log off and on again a couple of times and see if Win98 picks up group policies. Unfortunately this needs to be done on every Win9x/Me machine that uses group policies. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963915"></a>Windows NT4 Style Policy Files</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2968817"></a>Windows NT4 Style Policy Files</h3></div></div><div></div></div><p> To create or edit <tt class="filename">ntconfig.pol</tt> you must use the NT Server Policy Editor, <b class="command">poledit.exe</b> which is included with NT4 Server but <span class="emphasis"><em>not NT Workstation</em></span>. There is a Policy Editor on a NT4 @@ -13041,14 +13097,14 @@ here is incomplete - you are warned. be extracted as well. It is also possible to downloaded the policy template files for Office97 and get a copy of the policy editor. Another possible location is with the Zero Administration Kit available for download from Microsoft. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2964024"></a>Registry Spoiling</h4></div></div><div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2968926"></a>Registry Spoiling</h4></div></div><div></div></div><p> With NT4 style registry based policy changes, a large number of settings are not automatically reversed as the user logs off. Since the settings that were in the NTConfig.POL file were applied to the client machine registry and that apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences down-stream and the administrator must be extremely careful not to lock out the ability to manage the machine at a later date. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964048"></a>MS Windows 200x / XP Professional Policies</h3></div></div><div></div></div><p> + </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2968950"></a>MS Windows 200x / XP Professional Policies</h3></div></div><div></div></div><p> Windows NT4 System policies allows setting of registry parameters specific to users, groups and computers (client workstations) that are members of the NT4 style domain. Such policy file will work with MS Windows 2000 / XP clients also. @@ -13082,10 +13138,10 @@ here is incomplete - you are warned. MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine startup (machine specific part) and when the user logs onto the network the user specific part is applied. In MS Windows 200x style policy management each machine and/or user may be subject - to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows + to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows the administrator to also set filters over the policy settings. No such equivalent capability exists with NT4 style policy files. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2964149"></a>Administration of Win2K / XP Policies</h4></div></div><div></div></div><p> + </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2969051"></a>Administration of Win2K / XP Policies</h4></div></div><div></div></div><p> Instead of using the tool called <span class="application">The System Policy Editor</span>, commonly called Poledit (from the executable name <b class="command">poledit.exe</b>), <span class="acronym">GPOs</span> are created and managed using a <span class="application">Microsoft Management Console</span> <span class="acronym">(MMC)</span> snap-in as follows:</p><div class="procedure"><ol type="1"><li><p> @@ -13102,16 +13158,16 @@ here is incomplete - you are warned. </p></li></ol></div><p> All policy configuration options are controlled through the use of policy administrative templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. - Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. + Beware however, since the .adm files are NOT interchangeable across NT4 and Windows 200x. The later introduces many new features as well as extended definition capabilities. It is well beyond the scope of this documentation to explain how to program .adm files, for that - the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular + the administrator is referred to the Microsoft Windows Resource Kit for your particular version of MS Windows. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you use this powerful tool. Please refer to the resource kit manuals for specific usage information. - </p></div></div></div></div><div xmlns:ns79="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2965490"></a>Managing Account/User Policies</h2></div></div><div></div></div><p> + </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969202"></a>Managing Account/User Policies</h2></div></div><div></div></div><p> Policies can define a specific user's settings or the settings for a group of users. The resulting policy file contains the registry settings for all users, groups, and computers that will be using the policy file. Separate policy files for each user, group, or computer are not not necessary. @@ -13130,48 +13186,48 @@ applied to the user's part of the registry. MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory itself. The key benefit of using AS GPOs is that they impose no registry <span class="emphasis"><em>spoiling</em></span> effect. -This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates. +This has considerable advantage compared with the use of NTConfig.POL (NT4) style policy updates. </p><p> In addition to user access controls that may be imposed or applied via system and/or group policies in a manner that works in conjunction with user profiles, the user management environment under MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. Common restrictions that are frequently used includes: -</p><ns79:p> -</ns79:p><table class="simplelist" border="0" summary="Simple list"><tr><td>Logon Hours</td></tr><tr><td>Password Aging</td></tr><tr><td>Permitted Logon from certain machines only</td></tr><tr><td>Account type (Local or Global)</td></tr><tr><td>User Rights</td></tr></table><ns79:p> -</ns79:p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2965591"></a>Samba Editreg Toolset</h3></div></div><div></div></div><p> +</p><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Logon Hours</td></tr><tr><td>Password Aging</td></tr><tr><td>Permitted Logon from certain machines only</td></tr><tr><td>Account type (Local or Global)</td></tr><tr><td>User Rights</td></tr></table><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969303"></a>Samba Editreg Toolset</h3></div></div><div></div></div><p> Describe in detail the benefits of <b class="command">editreg</b> and how to use it. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2965611"></a>Windows NT4/200x</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969324"></a>Windows NT4/200x</h3></div></div><div></div></div><p> The tools that may be used to configure these types of controls from the MS Windows environment are: The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). - Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate + Under MS Windows 200x/XP this is done using the Microsoft Management Console (MMC) with appropriate "snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2965631"></a>Samba PDC</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969344"></a>Samba PDC</h3></div></div><div></div></div><p> With a Samba Domain Controller, the new tools for managing of user account and policy information includes: <b class="command">smbpasswd</b>, <b class="command">pdbedit</b>, <b class="command">net</b>, <b class="command">rpcclient</b>. The administrator should read the man pages for these tools and become familiar with their use. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2965676"></a>System Startup and Logon Processing Overview</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969388"></a>System Startup and Logon Processing Overview</h2></div></div><div></div></div><p> The following attempts to document the order of processing of system and user policies following a system reboot and as part of the user logon: </p><div class="orderedlist"><ol type="1"><li><p> Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming Convention Provider (MUP) start - </p></li><li xmlns:ns80=""><ns80:p> + </p></li><li><p> Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded and applied. The list may include GPOs that: -</ns80:p><table class="simplelist" border="0" summary="Simple list"><tr><td>Apply to the location of machines in a Directory</td></tr><tr><td>Apply only when settings have changed</td></tr><tr><td>Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</td></tr></table><ns80:p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Apply to the location of machines in a Directory</td></tr><tr><td>Apply only when settings have changed</td></tr><tr><td>Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</td></tr></table><p> No desktop user interface is presented until the above have been processed. - </ns80:p></li><li><p> - Execution of start-up scripts (hidden and synchronous by defaut). + </p></li><li><p> + Execution of start-up scripts (hidden and synchronous by default). </p></li><li><p> A keyboard action to affect start of logon (Ctrl-Alt-Del). </p></li><li><p> User credentials are validated, User profile is loaded (depends on policy settings). - </p></li><li xmlns:ns81=""><ns81:p> - An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: + </p></li><li><p> + An ordered list of User GPOs is obtained. The list contents depends on what is configured in respect of: -</ns81:p><table class="simplelist" border="0" summary="Simple list"><tr><td>Is user a domain member, thus subject to particular policies</td></tr><tr><td>Loopback enablement, and the state of the loopback policy (Merge or Replace)</td></tr><tr><td>Location of the Active Directory itself</td></tr><tr><td>Has the list of GPOs changed. No processing is needed if not changed.</td></tr></table><ns81:p> - </ns81:p></li><li><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Is user a domain member, thus subject to particular policies</td></tr><tr><td>Loopback enablement, and the state of the loopback policy (Merge or Replace)</td></tr><tr><td>Location of the Active Directory itself</td></tr><tr><td>Has the list of GPOs changed. No processing is needed if not changed.</td></tr></table><p> + </p></li><li><p> User Policies are applied from Active Directory. Note: There are several types. </p></li><li><p> Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group @@ -13180,10 +13236,10 @@ reboot and as part of the user logon: </p></li><li><p> The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 Domain) machine (system) policies are applied at start-up, User policies are applied at logon. - </p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2965823"></a>Common Errors</h2></div></div><div></div></div><p> + </p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969535"></a>Common Errors</h2></div></div><div></div></div><p> Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following collection demonstrates only basic issues. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2965837"></a>Policy Does Not Work</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969549"></a>Policy Does Not Work</h3></div></div><div></div></div><p> Question: We have created the <tt class="filename">config.pol</tt> file and put it in the <span class="emphasis"><em>NETLOGON</em></span> share. It has made no difference to our Win XP Pro machines, they just don't see it. IT worked fine with Win 98 but does not work any longer since we upgraded to Win XP Pro. Any hints? @@ -13191,7 +13247,7 @@ work any longer since we upgraded to Win XP Pro. Any hints? <span class="emphasis"><em>ANSWER:</em></span> Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based platforms. You need to use the NT4 Group Policy Editor to create a file called <tt class="filename">NTConfig.POL</tt> so that it is in the correct format for your MS Windows XP Pro clients. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter 24. Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2965940">Features and Benefits</a></dt><dt><a href="#id2965973">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2966014">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971377">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972314">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972378">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972638">Mandatory profiles</a></dt><dt><a href="#id2972696">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972742">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972762">MS Windows 9x/Me</a></dt><dt><a href="#id2972910">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973464">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2973968">Common Errors</a></dt><dd><dl><dt><a href="#id2973980">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974043">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974262">Changing the default profile</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2965940"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter 24. Desktop Profile Management</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2970756">Features and Benefits</a></dt><dt><a href="#id2970790">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2970831">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2971236">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2972407">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2972472">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2972737">Mandatory profiles</a></dt><dt><a href="#id2972795">Creating/Managing Group Profiles</a></dt><dt><a href="#id2972841">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2972861">MS Windows 9x/Me</a></dt><dt><a href="#id2973009">MS Windows NT4 Workstation</a></dt><dt><a href="#id2973563">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2974067">Common Errors</a></dt><dd><dl><dt><a href="#id2974080">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="#id2974143">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2974365">Changing the default profile</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2970756"></a>Features and Benefits</h2></div></div><div></div></div><p> Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for some administrators. </p><p> @@ -13204,7 +13260,7 @@ problem to others. In particular, users of mobile computing tools, where often t be a sustained network connection, are often better served by purely Local Profiles. This chapter provides information to help the Samba administrator to deal with those situations also. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2965973"></a>Roaming Profiles</h2></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2970790"></a>Roaming Profiles</h2></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Roaming profiles support is different for Win9x / Me and Windows NT4/200x. </p></div><p> Before discussing how to configure roaming profiles, it is useful to see how @@ -13217,34 +13273,34 @@ profiles are restricted to being stored in the user's home directory. </p><p> Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, including a separate field for the location of the user's profiles. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2966014"></a>Samba Configuration for Profile Handling</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2970831"></a>Samba Configuration for Profile Handling</h3></div></div><div></div></div><p> This section documents how to configure Samba for MS Windows client profile support. -</p><div xmlns:ns82="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2966027"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p> -To support Windowns NT4/200x clients, in the [global] section of smb.conf set the +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2970844"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p> +To support Windows NT4/200x clients, in the [global] section of smb.conf set the following (for example): -</p><ns82:p> -</ns82:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath -</pre><ns82:p> +</pre><p> This is typically implemented like: -</ns82:p><pre class="programlisting"> +</p><pre class="programlisting"> logon path = \\%L\Profiles\%u -</pre><ns82:p> +</pre><p> where %L translates to the name of the Samba server and %u translates to the user name -</ns82:p><p> +</p><p> The default for this option is <tt class="filename">\\%N\%U\profile</tt>, namely <tt class="filename">\\sambaserver\username\profile</tt>. The <tt class="filename">\\N%\%U</tt> service is created automatically by the [homes] service. If you are using a samba server for the profiles, you _must_ make the share specified in the logon path browseable. Please refer to the man page for <tt class="filename">smb.conf</tt> in respect of the different -symantics of %L and %N, as well as %U and %u. +semantics of %L and %N, as well as %U and %u. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> MS Windows NT/2K clients at times do not disconnect a connection to a server between logons. It is recommended to NOT use the <i class="parameter"><tt>homes</tt></i> meta-service name as part of the profile share path. -</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2966116"></a>Windows 9x / Me User Profiles</h4></div></div><div></div></div><p> +</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2970937"></a>Windows 9x / Me User Profiles</h4></div></div><div></div></div><p> To support Windows 9x / Me clients, you must use the <i class="parameter"><tt>logon home</tt></i> parameter. Samba has now been fixed so that <b class="userinput"><tt>net use /home</tt></b> now works as well, and it, too, relies on the <b class="command">logon home</b> parameter. @@ -13262,28 +13318,28 @@ Not only that, but <b class="userinput"><tt>net use /home</tt></b> will also wor Windows 9x / Me. It removes any directory stuff off the end of the home directory area and only uses the server and share portion. That is, it looks like you specified <tt class="filename">\\%L\%U</tt> for <i class="parameter"><tt>logon home</tt></i>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971192"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971046"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p> You can support profiles for both Win9X and WinNT clients by setting both the <i class="parameter"><tt>logon home</tt></i> and <i class="parameter"><tt>logon path</tt></i> parameters. For example: </p><pre class="programlisting"> logon home = \\%L\%u\.profiles logon path = \\%L\profiles\%u -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971228"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971085"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p> A question often asked is “<span class="quote">How may I enforce use of local profiles?</span>” or “<span class="quote">How do I disable Roaming Profiles?</span>” </p><p> There are three ways of doing this: -</p><div class="variablelist"><dl><dt><span class="term">In <tt class="filename">smb.conf</tt></span></dt><dd xmlns:ns83=""><ns83:p> +</p><div class="variablelist"><dl><dt><span class="term">In <tt class="filename">smb.conf</tt></span></dt><dd><p> Affect the following settings and ALL clients will be forced to use a local profile: - </ns83:p><pre class="programlisting"> + </p><pre class="programlisting"> logon home = logon path = - </pre><ns83:p> - </ns83:p></dd><dt><span class="term">MS Windows Registry:</span></dt><dd xmlns:ns84=""><ns84:p> + </pre><p> + </p></dd><dt><span class="term">MS Windows Registry:</span></dt><dd><p> By using the Microsoft Management Console gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This of course modifies registry settings. The full path to the option is: - </ns84:p><pre class="programlisting"> + </p><pre class="programlisting"> Local Computer Policy\ Computer Configuration\ Administrative Templates\ @@ -13291,9 +13347,9 @@ There are three ways of doing this: User Profiles\ Disable: Only Allow Local User Profiles - Disable: Prevent Roaming Profile Change from Propogating to the Server - </pre><ns84:p> - </ns84:p></dd><dt><span class="term">Change of Profile Type:</span></dt><dd><p> + Disable: Prevent Roaming Profile Change from Propagating to the Server + </pre><p> + </p></dd><dt><span class="term">Change of Profile Type:</span></dt><dd><p> From the start menu right click on the My Computer icon, select <span class="guimenuitem">Properties</span>, click on the <span class="guilabel">User Profiles</span> tab, select the profile you wish to change from Roaming type to Local, click <span class="guibutton">Change Type</span>. @@ -13305,7 +13361,7 @@ profiles. The specifics of how to convert a local profile to a roaming profile, or a roaming profile to a local one vary according to the version of MS Windows you are running. Consult the Microsoft MS Windows Resource Kit for your version of Windows for specific information. -</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2971377"></a>Windows Client Profile Configuration Information</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971385"></a>Windows 9x / Me Profile Setup</h4></div></div><div></div></div><p> +</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2971236"></a>Windows Client Profile Configuration Information</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971244"></a>Windows 9x / Me Profile Setup</h4></div></div><div></div></div><p> When a user first logs in on Windows 9X, the file user.DAT is created, as are folders <tt class="filename">Start Menu</tt>, <tt class="filename">Desktop</tt>, <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt>. @@ -13411,7 +13467,7 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces provided with Windows NT4/200x server, and see what the differences are with the equivalent samba trace. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2967586"></a>Windows NT4 Workstation</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971738"></a>Windows NT4 Workstation</h4></div></div><div></div></div><p> When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified through the <i class="parameter"><tt>logon path</tt></i> parameter. @@ -13440,7 +13496,7 @@ turns a profile into a mandatory one. </p><p> The case of the profile is significant. The file must be called <tt class="filename">NTuser.DAT</tt> or, for a mandatory profile, <tt class="filename">NTuser.MAN</tt>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2967744"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2971896"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p> You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows: </p><div class="procedure"><ol type="1"><li><p> @@ -13468,10 +13524,10 @@ profile on the MS Windows workstation as follows: Now click on the <span class="guibutton">Ok</span> button to create the profile in the path you nominated. </p></li></ol></div><p> -Done. You now have a profile that can be editted using the samba-3.0.0 +Done. You now have a profile that can be edited using the samba-3.0.0 <b class="command">profiles</b> tool. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Under NT/2K the use of mandotory profiles forces the use of MS Exchange +Under NT/2K the use of mandatory profiles forces the use of MS Exchange storage of mail data. That keeps desktop profiles usable. </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><div class="procedure"><ol type="1"><li><p> This is a security check new to Windows XP (or maybe only @@ -13490,7 +13546,7 @@ On the XP workstation log in with an Administrator account. </p></li><li><p>Click: <span class="guimenu">Start</span>, <span class="guimenuitem">Run</span></p></li><li><p>Type: <b class="userinput"><tt>mmc</tt></b></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click: <span class="guimenu">File</span>, <span class="guimenuitem">Add/Remove Snap-in...</span>, <span class="guimenuitem">Add</span></p></li><li><p>Double-Click: <span class="guiicon">Group Policy</span></p></li><li><p>Click: <span class="guibutton">Finish</span>, <span class="guibutton">Close</span></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>In the "Console Root" window:</p></li><li><p>Expand: <span class="guiicon">Local Computer Policy</span>, <span class="guiicon">Computer Configuration</span>, <span class="guiicon">Administrative Templates</span>, <span class="guiicon">System</span>, <span class="guiicon">User Profiles</span></p></li><li><p>Double-Click: <span class="guilabel">Do not check for user ownership of Roaming Profile Folders</span></p></li><li><p>Select: <span class="guilabel">Enabled</span></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>Close the whole console. You do not need to save the settings (this refers to the console settings rather than the policies you have - changed).</p></li><li><p>Reboot</p></li></ol></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972314"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><div></div></div><p> + changed).</p></li><li><p>Reboot</p></li></ol></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972407"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><div></div></div><p> Sharing of desktop profiles between Windows versions is NOT recommended. Desktop profiles are an evolving phenomenon and profiles for later versions of MS Windows clients add features that may interfere with earlier versions @@ -13507,12 +13563,12 @@ that need to be common are <i class="parameter"><tt>logon path</tt></i> and </p><p> If you have this set up correctly, you will find separate <tt class="filename">user.DAT</tt> and <tt class="filename">NTuser.DAT</tt> files in the same profile directory. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972378"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972472"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><p> There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the profile be stored on a samba server, or any other SMB server, as long as that SMB server supports encrypted passwords. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972395"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972489"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><p> Unfortunately, the Resource Kit information is specific to the version of MS Windows NT4/200x. The correct resource kit is required for each platform. </p><p> @@ -13522,24 +13578,24 @@ On your NT4 Domain Controller, right click on <span class="guiicon">My Computer< select the tab labelled <span class="guilabel">User Profiles</span>. </p></li><li><p> Select a user profile you want to migrate and click on it. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term "migrate" lossely. You can copy a profile to +</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term "migrate" loosely. You can copy a profile to create a group profile. You can give the user 'Everyone' rights to the profile you copy this to. That is what you need to do, since your samba domain is not a member of a trust relationship with your NT4 PDC.</p></div></li><li><p>Click the <span class="guibutton">Copy To</span> button.</p></li><li><p>In the box labelled <span class="guilabel">Copy Profile to</span> add your new path, eg: <tt class="filename">c:\temp\foobar</tt></p></li><li><p>Click on the button <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li><p>Click on the group 'Everyone' and then click <span class="guibutton">OK</span>. This closes the 'choose user' box.</p></li><li><p>Now click <span class="guibutton">OK</span>.</p></li></ol></div><p> Follow the above for every profile you need to migrate. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972559"></a>Side bar Notes</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972658"></a>Side bar Notes</h4></div></div><div></div></div><p> You should obtain the SID of your NT4 domain. You can use smbpasswd to do this. Read the man page.</p><p> With Samba-3.0.0 alpha code you can import all you NT4 domain accounts using the net samsync method. This way you can retain your profile settings as well as all your users. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972580"></a>moveuser.exe</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972680"></a>moveuser.exe</h4></div></div><div></div></div><p> The W2K professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account domain to change, and/or the user name to change. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972597"></a>Get SID</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972696"></a>Get SID</h4></div></div><div></div></div><p> You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit. </p><p> @@ -13552,7 +13608,7 @@ users who have logged on to this computer. (To find the profile information for the user whose locally cached profile you want to move, find the SID for the user with the GetSID.exe utility.) Inside of the appropriate user's subkey, you will see a string value named ProfileImagePath. -</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972638"></a>Mandatory profiles</h2></div></div><div></div></div><p> +</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972737"></a>Mandatory profiles</h2></div></div><div></div></div><p> A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. During the user's session it may be possible to change the desktop environment, but as the user logs out all changes made will be lost. If it is desired to NOT allow the @@ -13568,8 +13624,8 @@ file in the copied profile and rename it to NTUser.MAN. </p><p> For MS Windows 9x / Me it is the <tt class="filename">User.DAT</tt> file that must be renamed to <tt class="filename">User.MAN</tt> to affect a mandatory profile. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972696"></a>Creating/Managing Group Profiles</h2></div></div><div></div></div><p> -Most organisations are arranged into departments. There is a nice benenfit in +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972795"></a>Creating/Managing Group Profiles</h2></div></div><div></div></div><p> +Most organisations are arranged into departments. There is a nice benefit in this fact since usually most users in a department will require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the use of Group Profiles. A Group Profile is a profile that is created firstly using @@ -13583,14 +13639,14 @@ the now modified profile. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Be careful with group profiles, if the user who is a member of a group also has a personal profile, then the result will be a fusion (merge) of the two. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972742"></a>Default Profile for Windows Users</h2></div></div><div></div></div><p> + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2972841"></a>Default Profile for Windows Users</h2></div></div><div></div></div><p> MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom a profile does not already exist. Armed with a knowledge of where the default profile is located on the Windows workstation, and knowing which registry keys affect the path from which the default profile is created, it is possible to modify the default profile to one that has been optimised for the site. This has significant administrative advantages. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972762"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972861"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p> To enable default per use profiles in Windows 9x / Me you can either use the <span class="application">Windows 98 System Policy Editor</span> or change the registry directly. </p><p> @@ -13602,7 +13658,7 @@ select <span class="guilabel">User Profiles</span>, click on the enable box. Do To modify the registry directly, launch the <span class="application">Registry Editor</span> (<b class="command">regedit.exe</b>), select the hive <tt class="filename">HKEY_LOCAL_MACHINE\Network\Logon</tt>. Now add a DWORD type key with the name "User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972859"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2972959"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><div></div></div><p> When a user logs on to a Windows 9x / Me machine, the local profile path, <tt class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked for an existing entry for that user: @@ -13618,7 +13674,7 @@ If a User Profile is not found in either location, the Default User Profile from machine is used and is copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user's local profile. If the user has a roaming profile, the changes are written to the user's profile on the server. -</p></div></div><div xmlns:ns85="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2972910"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2973009"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><p> On MS Windows NT4 the default user profile is obtained from the location <tt class="filename">%SystemRoot%\Profiles</tt> which in a default installation will translate to <tt class="filename">C:\WinNT\Profiles</tt>. Under this directory on a clean install there will be @@ -13653,21 +13709,21 @@ the following steps are followed in respect of profile handling: out to the location of the profile. The <tt class="filename">NTuser.DAT</tt> file is then re-created from the contents of the <tt class="filename">HKEY_CURRENT_USER</tt> contents. Thus, should there not exist in the NETLOGON share an <tt class="filename">NTConfig.POL</tt> at the - next logon, the effect of the provious <tt class="filename">NTConfig.POL</tt> will still be held + next logon, the effect of the previous <tt class="filename">NTConfig.POL</tt> will still be held in the profile. The effect of this is known as <span class="emphasis"><em>tatooing</em></span>. </p></li></ol></div><p> MS Windows NT4 profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>. A Local profile will stored in the <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt> location. A roaming profile will also remain stored in the same way, unless the following registry key is created: -</p><ns85:p> -</ns85:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ "DeleteRoamingCache"=dword:00000001 -</pre><ns85:p> +</pre><p> In which case, the local copy (in <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>) will be deleted on logout. -</ns85:p><p> +</p><p> Under MS Windows NT4 default locations for common resources (like <tt class="filename">My Documents</tt> may be redirected to a network share by modifying the following registry keys. These changes may be affected via use of the System Policy Editor (to do so may require that you create your owns template extension @@ -13680,17 +13736,17 @@ are controlled by entries on Windows NT4 is: <tt class="filename">HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\</tt> </p><p> The above hive key contains a list of automatically managed folders. The default entries are: -</p><ns85:p> -</ns85:p><div class="table"><a name="id2973257"></a><p class="title"><b>Table 24.1. User Shell Folder registry keys default values</b></p><table summary="User Shell Folder registry keys default values" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu </td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><ns85:p> -</ns85:p><p> +</p><p> +</p><div class="table"><a name="id2973359"></a><p class="title"><b>Table 24.1. User Shell Folder registry keys default values</b></p><table summary="User Shell Folder registry keys default values" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu </td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><p> +</p><p> The registry key that contains the location of the default profile settings is: </p><p> <tt class="filename">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders</tt> -</p><ns85:p> +</p><p> The default entries are: -</ns85:p><div class="table"><a name="id2973402"></a><p class="title"><b>Table 24.2. Defaults of profile settings registry keys</b></p><table summary="Defaults of profile settings registry keys" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Common Desktop</td><td>%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td>Common Programs</td><td>%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td>Common Start Menu</td><td>%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td>Common Startup</td><td>%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</td></tr></tbody></table></div><ns85:p> -</ns85:p></div><div xmlns:ns86="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2973464"></a>MS Windows 200x/XP</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</p><div class="table"><a name="id2973503"></a><p class="title"><b>Table 24.2. Defaults of profile settings registry keys</b></p><table summary="Defaults of profile settings registry keys" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Common Desktop</td><td>%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td>Common Programs</td><td>%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td>Common Start Menu</td><td>%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td>Common Startup</td><td>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2973563"></a>MS Windows 200x/XP</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> MS Windows XP Home Edition does use default per user profiles, but can not participate in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile only from itself. While there are benefits in doing this the beauty of those MS Windows @@ -13716,7 +13772,7 @@ login name of the user. If a default profile does not exist in this location then MS Windows 200x/XP will use the local default profile. </p><p> -On loging out, the users' desktop profile will be stored to the location specified in the registry +On logging out, the users' desktop profile will be stored to the location specified in the registry settings that pertain to the user. If no specific policies have been created, or passed to the client during the login process (as Samba does automatically), then the user's profile will be written to the local machine only under the path <tt class="filename">C:\Documents and Settings\%USERNAME%</tt>. @@ -13738,9 +13794,9 @@ are controlled by entries on Windows 200x/XP is: <tt class="filename">HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\</tt> </p><p> The above hive key contains a list of automatically managed folders. The default entries are: -</p><ns86:p> -</ns86:p><div class="table"><a name="id2973656"></a><p class="title"><b>Table 24.3. Defaults of default user profile paths registry keys</b></p><table summary="Defaults of default user profile paths registry keys" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Cache</td><td>%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td>Cookies</td><td>%USERPROFILE%\Cookies</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>History</td><td>%USERPROFILE%\Local Settings\History</td></tr><tr><td>Local AppData</td><td>%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td>Local Settings</td><td>%USERPROFILE%\Local Settings</td></tr><tr><td>My Pictures</td><td>%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>Personal</td><td>%USERPROFILE%\My Documents</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu</td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td>Templates</td><td>%USERPROFILE%\Templates</td></tr></tbody></table></div><ns86:p> -</ns86:p><p> +</p><p> +</p><div class="table"><a name="id2973759"></a><p class="title"><b>Table 24.3. Defaults of default user profile paths registry keys</b></p><table summary="Defaults of default user profile paths registry keys" border="1"><colgroup><col><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Cache</td><td>%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td>Cookies</td><td>%USERPROFILE%\Cookies</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>History</td><td>%USERPROFILE%\Local Settings\History</td></tr><tr><td>Local AppData</td><td>%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td>Local Settings</td><td>%USERPROFILE%\Local Settings</td></tr><tr><td>My Pictures</td><td>%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>Personal</td><td>%USERPROFILE%\My Documents</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu</td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td>Templates</td><td>%USERPROFILE%\Templates</td></tr></tbody></table></div><p> +</p><p> There is also an entry called "Default" that has no value set. The default entry is of type <tt class="constant">REG_SZ</tt>, all the others are of type <tt class="constant">REG_EXPAND_SZ</tt>. </p><p> @@ -13764,9 +13820,9 @@ MS Windows 200x/XP profiles may be <span class="emphasis"><em>Local</em></span> A roaming profile will be cached locally unless the following registry key is created: </p><p><tt class="filename">HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\"DeleteRoamingCache"=dword:00000001</tt></p><p> In which case, the local cache copy will be deleted on logout. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2973968"></a>Common Errors</h2></div></div><div></div></div><p> -THe following are some typical errors/problems/questions that have been asked. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2973980"></a>How does one set up roaming profiles for just one (or a few) user/s or group/s?</h3></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974067"></a>Common Errors</h2></div></div><div></div></div><p> +The following are some typical errors/problems/questions that have been asked. +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974080"></a>How does one set up roaming profiles for just one (or a few) user/s or group/s?</h3></div></div><div></div></div><p> With samba-2.2.x the choice you have is to enable or disable roaming profiles support. It is a global only setting. The default is to have roaming profiles and the default path will locate them in the user's home @@ -13784,43 +13840,43 @@ using the Domain User Manager (as with MS Windows NT4/ Win 2Kx). </p><p> In any case, you can configure only one profile per user. That profile can be either: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A profile unique to that user</td></tr><tr><td>A mandatory profile (one the user can not change)</td></tr><tr><td>A group profile (really should be mandatory ie:unchangable)</td></tr></table></div><div xmlns:ns88="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974043"></a>Can NOT use Roaming Profiles</h3></div></div><div></div></div><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A profile unique to that user</td></tr><tr><td>A mandatory profile (one the user can not change)</td></tr><tr><td>A group profile (really should be mandatory ie:unchangable)</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974143"></a>Can NOT use Roaming Profiles</h3></div></div><div></div></div><p> “<span class="quote"> I dont want Roaming profile to be implemented, I just want to give users local profiles only. ... Please help me I am totally lost with this error from past two days I tried everything and googled around quite a bit but of no help. Please help me. -</span>”</p><ns88:p> +</span>”</p><p> Your choices are: -</ns88:p><div class="variablelist"><dl><dt><span class="term">Local profiles</span></dt><dd><p> +</p><div class="variablelist"><dl><dt><span class="term">Local profiles</span></dt><dd><p> I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out - </p></dd><dt><span class="term">Roaming profiles</span></dt><dd xmlns:ns87=""><ns87:p> - </ns87:p><table class="simplelist" border="0" summary="Simple list"><tr><td>can use auto-delete on logout option</td></tr><tr><td>requires a registry key change on workstation</td></tr></table><ns87:p> + </p></dd><dt><span class="term">Roaming profiles</span></dt><dd><p> + </p><table class="simplelist" border="0" summary="Simple list"><tr><td>can use auto-delete on logout option</td></tr><tr><td>requires a registry key change on workstation</td></tr></table><p> Your choices are: - </ns87:p><div class="variablelist"><dl><dt><span class="term">Personal Roaming profiles</span></dt><dd><p> + </p><div class="variablelist"><dl><dt><span class="term">Personal Roaming profiles</span></dt><dd><p> - should be preserved on a central server - workstations 'cache' (store) a local copy - used in case the profile can not be downloaded at next logon - </p></dd><dt><span class="term">Group profiles</span></dt><dd><p>- loaded from a cetral place</p></dd><dt><span class="term">Mandatory profiles</span></dt><dd><p> + </p></dd><dt><span class="term">Group profiles</span></dt><dd><p>- loaded from a central place</p></dd><dt><span class="term">Mandatory profiles</span></dt><dd><p> - can be personal or group - can NOT be changed (except by an administrator - </p></dd></dl></div><ns87:p> - </ns87:p></dd></dl></div><ns88:p> + </p></dd></dl></div><p> + </p></dd></dl></div><p> -</ns88:p><p> +</p><p> A WinNT4/2K/XP profile can vary in size from 130KB to off the scale. Outlook PST files are most often part of the profile and can be many GB in -size. On average (in a well controlled environment) roaming profie size of +size. On average (in a well controlled environment) roaming profile size of 2MB is a good rule of thumb to use for planning purposes. In an undisciplined environment I have seen up to 2GB profiles. Users tend to complain when it take an hour to log onto a workstation but they harvest -the fuits of folly (and ignorance). +the fruits of folly (and ignorance). </p><p> The point of all the above is to show that roaming profiles and good controls of how they can be changed as well as good discipline make up for @@ -13828,19 +13884,19 @@ a problem free site. </p><p> Microsoft's answer to the PST problem is to store all email in an MS Exchange Server back-end. But this is another story ...! -</p><ns88:p> +</p><p> So, having LOCAL profiles means: -</ns88:p><table class="simplelist" border="0" summary="Simple list"><tr><td>If lots of users user each machine - lot's of local disk storage needed for local profiles</td></tr><tr><td>Every workstation the user logs into has it's own profile - can be very different from machine to machine</td></tr></table><ns88:p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>If lots of users user each machine - lot's of local disk storage needed for local profiles</td></tr><tr><td>Every workstation the user logs into has it's own profile - can be very different from machine to machine</td></tr></table><p> On the other hand, having roaming profiles means: -</ns88:p><table class="simplelist" border="0" summary="Simple list"><tr><td>The network administrator can control EVERY aspect of user profiles</td></tr><tr><td>With the use of mandatory profiles - a drastic reduction in network management overheads</td></tr><tr><td>User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably</td></tr></table><ns88:p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>The network administrator can control EVERY aspect of user profiles</td></tr><tr><td>With the use of mandatory profiles - a drastic reduction in network management overheads</td></tr><tr><td>User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably</td></tr></table><p> -</ns88:p><p> +</p><p> I have managed and installed MANY NT/2K networks and have NEVER found one where users who move from machine to machine are happy with local profiles. In the long run local profiles bite them. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974262"></a>Changing the default profile</h3></div></div><div></div></div><p>“<span class="quote"> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974365"></a>Changing the default profile</h3></div></div><div></div></div><p>“<span class="quote"> When the client tries to logon to the PDC it looks for a profile to download where do I put this default profile. </span>”</p><p> @@ -13870,18 +13926,18 @@ Secondly, for roaming profiles you need: logon drive = H: (Z: is the default) Plus you need a PROFILES share that is world writable. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter 25. PAM based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2975719">Features and Benefits</a></dt><dt><a href="#id2974574">Technical Discussion</a></dt><dd><dl><dt><a href="#id2974590">PAM Configuration Syntax</a></dt><dt><a href="#id2975256">Example System Configurations</a></dt><dt><a href="#id2977688">smb.conf PAM Configuration</a></dt><dt><a href="#id2977745">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2977829">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2978196">Common Errors</a></dt><dd><dl><dt><a href="#id2978209">pam_winbind problem</a></dt></dl></dd></dl></div><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter 25. PAM based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2978309">Features and Benefits</a></dt><dt><a href="#id2978577">Technical Discussion</a></dt><dd><dl><dt><a href="#id2978595">PAM Configuration Syntax</a></dt><dt><a href="#id2979265">Example System Configurations</a></dt><dt><a href="#id2979567">smb.conf PAM Configuration</a></dt><dt><a href="#id2979625">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2979709">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2980075">Common Errors</a></dt><dd><dl><dt><a href="#id2980089">pam_winbind problem</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 managment -possibilities and in particular how to deploy tools like pam_smbpass.so to your adavantage. +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" title="Chapter 21. Integrated Logon Support using Winbind">the Winbind chapter</a>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2975719"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2978309"></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 @@ -13939,12 +13995,12 @@ of distributed samba domain controllers that can provide wide are network bandwi efficient authentication services for PAM capable systems. In effect, this allows the deployment of centrally managed and maintained distributed authentication from a single user account database. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2974574"></a>Technical Discussion</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2978577"></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 xmlns:ns89="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2974590"></a>PAM Configuration Syntax</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978595"></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. @@ -13958,22 +14014,22 @@ 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><ns89:p> -</ns89:p><pre class="screen"> +</p><p> +</p><pre class="screen"> auth required /other_path/pam_strange_module.so -</pre><ns89:p> -</ns89:p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2974646"></a>Anatomy of <tt class="filename">/etc/pam.d</tt> Entries</h4></div></div><div></div></div><p> +</pre><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2978651"></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"> http://ftp.kernel.org/pub/linux/libs/pam</a> The Official Linux-PAM home page. </p><p> A general configuration line of the /etc/pam.conf file has the following form: -</p><ns89:p> -</ns89:p><pre class="screen"> +</p><p> +</p><pre class="screen"> service-name module-type control-flag module-path args -</pre><ns89:p> -</ns89:p><p> +</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. @@ -13999,8 +14055,8 @@ Once we have explained the meaning of the above tokens, we will describe this me 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 loggin - of information concerning the opening/closing of some data exchange with a user, mountin + 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 @@ -14048,19 +14104,19 @@ Once we have explained the meaning of the above tokens, we will describe this me 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 delimeted with square brackets and + 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="screen"> [value1=action1 value2=action2 ...] </pre><p> - Here, valueI is one of the following return values: success; open_err; symbol_err; service_err; + 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 actionI can be a positive integer or one of the following tokens: ignore; ok; done; bad; die; and reset. + 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 @@ -14090,8 +14146,8 @@ Once we have explained the meaning of the above tokens, we will describe this me </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><ns89:p> - </ns89:p><div class="itemizedlist"><ul type="disc"><li><p> + </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] @@ -14099,8 +14155,8 @@ Once we have explained the meaning of the above tokens, we will describe this me 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><ns89:p> - </ns89:p><p> + </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 @@ -14132,13 +14188,13 @@ squid auth required pam_mysql.so user=passwd_query passwd=mada \ Any line in (one of) the configuration file(s), that is not formatted correctly, will generally tend (erring on the side of caution) to make the authentication process fail. A corresponding error is written to the system log files with a call to syslog(3). - </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2975256"></a>Example System Configurations</h3></div></div><div></div></div><p> + </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2979265"></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="id2975286"></a>PAM: original login config</h4></div></div><div></div></div><pre class="screen"> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2979296"></a>PAM: original login config</h4></div></div><div></div></div><pre class="screen"> #%PAM-1.0 # The PAM configuration file for the `login' service # @@ -14153,10 +14209,10 @@ 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 xmlns:ns90="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2975313"></a>PAM: login using pam_smbpass</h4></div></div><div></div></div><p> -PAM allows use of replacable modules. Those available on a sample system include: -</p><ns90:p><tt class="prompt">$</tt><b class="userinput"><tt>/bin/ls /lib/security</tt></b> -</ns90:p><pre class="screen"> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2979322"></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="screen"> 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 @@ -14225,14 +14281,14 @@ password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf also possible to pass information obtained within one PAM module through to the next module in the PAM stack. Please refer to the documentation for your particular system implementation for details regarding the specific -capabilities of PAM in this environment. Some Linux implmentations also +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="id2977688"></a>smb.conf PAM Configuration</h3></div></div><div></div></div><p> +</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2979567"></a>smb.conf PAM Configuration</h3></div></div><div></div></div><p> There is an option in smb.conf called <a href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a>. The following is from the on-line help for this option in SWAT; </p><p> @@ -14247,8 +14303,8 @@ ignores PAM for authentication in the case of The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption. -</p><p>Default: <i class="parameter"><tt>obey pam restrictions = no</tt></i></p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2977745"></a>Remote CIFS Authentication using winbindd.so</h3></div></div><div></div></div><p> -All operating systems depend on the provision of users credentials accecptable to the platform. +</p><p>Default: <i class="parameter"><tt>obey pam restrictions = no</tt></i></p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2979625"></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>. @@ -14273,7 +14329,7 @@ Microsoft Active Directory Service (ADS) in so far as reduction of wide area net The rid to unix id database is the only location where the user and group mappings are stored by winbindd. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids. -</p></div></div><div xmlns:ns91="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2977829"></a>Password Synchronization using pam_smbpass.so</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2979709"></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 @@ -14284,21 +14340,21 @@ 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><ns91:p> +</p><p> Options recognized by this module are as follows: -</ns91:p><div class="table"><a name="id2977860"></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><col></colgroup><tbody><tr><td align="left">debug</td><td align="left">log more debugging info</td></tr><tr><td align="left">audit</td><td align="left">like debug, but also logs unknown usernames</td></tr><tr><td align="left">use_first_pass</td><td align="left">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="left">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="left">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="left">don't make passwords used by this module available to other modules.</td></tr><tr><td align="left">nodelay</td><td align="left">don't insert ~1 second delays on authentication failure.</td></tr><tr><td align="left">nullok</td><td align="left">null passwords are allowed.</td></tr><tr><td align="left">nonull</td><td align="left">null passwords are not allowed. Used to override the Samba configuration.</td></tr><tr><td align="left">migrate</td><td align="left">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="left">specify an alternate path to the <tt class="filename">smb.conf</tt> file.</td></tr></tbody></table></div><ns91:p> -</ns91:p><ns91:p> +</p><div class="table"><a name="id2979741"></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><col></colgroup><tbody><tr><td align="left">debug</td><td align="left">log more debugging info</td></tr><tr><td align="left">audit</td><td align="left">like debug, but also logs unknown usernames</td></tr><tr><td align="left">use_first_pass</td><td align="left">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="left">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="left">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="left">don't make passwords used by this module available to other modules.</td></tr><tr><td align="left">nodelay</td><td align="left">don't insert ~1 second delays on authentication failure.</td></tr><tr><td align="left">nullok</td><td align="left">null passwords are allowed.</td></tr><tr><td align="left">nonull</td><td align="left">null passwords are not allowed. Used to override the Samba configuration.</td></tr><tr><td align="left">migrate</td><td align="left">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="left">specify an alternate path to the <tt class="filename">smb.conf</tt> file.</td></tr></tbody></table></div><p> +</p><p> Thanks go to the following people: -</ns91:p><table class="simplelist" border="0" summary="Simple list"><tr><td><a href="mailto:morgan@transmeta.com" target="_top">Andrew Morgan</a>, for providing the Linux-PAM +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><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</td></tr><tr><td><a href="gafton@redhat.com" target="_top">Christian Gafton</a> and Andrew Morgan again, for the pam_pwdb module upon which pam_smbpass was originally based</td></tr><tr><td><a href="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 :)</td></tr></table><ns91:p>. -</ns91:p><p> + that keep me working on it :)</td></tr></table><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="id2978061"></a>Password Synchronisation Configuration</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2979941"></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 @@ -14314,7 +14370,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2978094"></a>Password Migration Configuration</h4></div></div><div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2979974"></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: @@ -14333,7 +14389,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password optional pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2978129"></a>Mature Password Configuration</h4></div></div><div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2980009"></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. @@ -14348,7 +14404,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so use_authtok use_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2978161"></a>Kerberos Password Integration Configuration</h4></div></div><div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2980041"></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. @@ -14364,13 +14420,13 @@ 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="id2978196"></a>Common Errors</h2></div></div><div></div></div><p> +</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2980075"></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 xmlns:ns92="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978209"></a>pam_winbind problem</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2980089"></a>pam_winbind problem</h3></div></div><div></div></div><p> I have the following PAM configuration: - </p><ns92:p> -</ns92:p><pre class="screen"> + </p><p> +</p><pre class="screen"> 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 @@ -14379,8 +14435,8 @@ 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><ns92:p> -</ns92:p><p> +</pre><p> +</p><p> 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. </p><p> @@ -14391,7 +14447,7 @@ password required /lib/security/pam_stack.so service=system-auth <tt class="filename">/etc/pam.d/system-auth</tt> and copy only what you need from it into your <tt class="filename">/etc/pam.d/login</tt> file. Alternatively, if you want all services to use winbind, you can put the winbind-specific stuff in <tt class="filename">/etc/pam.d/system-auth</tt>. - </p></div></div></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="#id2979952">Features and Benefits</a></dt><dt><a href="#id2979977">Background Information</a></dt><dt><a href="#id2980022">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2980073">/etc/hosts</a></dt><dt><a href="#id2980198">/etc/resolv.conf</a></dt><dt><a href="#id2978348">/etc/host.conf</a></dt><dt><a href="#id2978390">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2978479">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2978604">The NetBIOS Name Cache</a></dt><dt><a href="#id2978648">The LMHOSTS file</a></dt><dt><a href="#id2978762">HOSTS file</a></dt><dt><a href="#id2978795">DNS Lookup</a></dt><dt><a href="#id2978820">WINS Lookup</a></dt></dl></dd><dt><a href="#id2978890">Common Errors</a></dt><dd><dl><dt><a href="#id2978906">My Boomerang Won't Come Back</a></dt><dt><a href="#id2978938">Very Slow Network Connections</a></dt><dt><a href="#id2978989">Samba server name change problem</a></dt></dl></dd></dl></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="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="#id2982211">Features and Benefits</a></dt><dt><a href="#id2982236">Background Information</a></dt><dt><a href="#id2982281">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2982337">/etc/hosts</a></dt><dt><a href="#id2982462">/etc/resolv.conf</a></dt><dt><a href="#id2982506">/etc/host.conf</a></dt><dt><a href="#id2982548">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2982637">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2982784">The NetBIOS Name Cache</a></dt><dt><a href="#id2982829">The LMHOSTS file</a></dt><dt><a href="#id2983073">HOSTS file</a></dt><dt><a href="#id2983105">DNS Lookup</a></dt><dt><a href="#id2983130">WINS Lookup</a></dt></dl></dd><dt><a href="#id2983200">Common Errors</a></dt><dd><dl><dt><a href="#id2983216">My Boomerang Won't Come Back</a></dt><dt><a href="#id2983248">Very Slow Network Connections</a></dt><dt><a href="#id2983300">Samba server name change problem</a></dt></dl></dd></dl></div><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 @@ -14402,15 +14458,15 @@ NetBIOS over TCP/IP then this section may help you to resolve networking problem to NOT run NetBEUI at all. Note also that there is NO such thing as NetBEUI over TCP/IP - the existence of such a protocol is a complete and utter mis-apprehension. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2979952"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982211"></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 adminsitrators have not been exposed to the intricacies of MS Windows TCP/IP based +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="id2979977"></a>Background Information</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982236"></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 @@ -14426,9 +14482,9 @@ disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS req Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). Use of DHCP with ADS is recommended as a further means of maintaining central control over client workstation network configuration. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2980022"></a>Name Resolution in a pure Unix/Linux world</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982281"></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="id2980073"></a><tt class="filename">/etc/hosts</tt></h3></div></div><div></div></div><p> +</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="filename">/etc/hosts</tt></p></li><li><p><tt class="filename">/etc/resolv.conf</tt></p></li><li><p><tt class="filename">/etc/host.conf</tt></p></li><li><p><tt class="filename">/etc/nsswitch.conf</tt></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982337"></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="screen"> @@ -14452,7 +14508,7 @@ as two digit hexadecimal numbers separated by colons. eg: 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 arbitary or discretionary in nature. At the most basic level all +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 @@ -14479,13 +14535,13 @@ contain the MAC address and the primary IP address for each interface. </p><p> The <tt class="filename">/etc/hosts</tt> file is foundational to all -Unix/Linux TCP/IP installations and as a minumum will contain +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="id2980198"></a><tt class="filename">/etc/resolv.conf</tt></h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982462"></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 @@ -14495,18 +14551,18 @@ This file tells the name resolution libraries: </p></li><li><p>The name or IP address of available Domain Name Servers that may be asked to perform name to address translation lookups - </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978348"></a><tt class="filename">/etc/host.conf</tt></h3></div></div><div></div></div><p> + </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982506"></a><tt class="filename">/etc/host.conf</tt></h3></div></div><div></div></div><p> <tt class="filename">/etc/host.conf</tt> is the primary means by which the setting in /etc/resolv.conf may be affected. It is a critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is: +which name resolution may proceed. The typical structure is: </p><pre class="screen"> 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="id2978390"></a><tt class="filename">/etc/nsswitch.conf</tt></h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982548"></a><tt class="filename">/etc/nsswitch.conf</tt></h3></div></div><div></div></div><p> This file controls the actual name resolution targets. The file typically has resolver object specifications as follows: </p><pre class="screen"> @@ -14523,7 +14579,7 @@ file typically has resolver object specifications as follows: hosts: files nis dns # Alternative entries for host name resolution are: - # hosts: files dns nis nis+ hesoid db compat ldap wins + # hosts: files dns nis nis+ hesiod db compat ldap wins networks: nis files dns ethers: nis files @@ -14550,7 +14606,7 @@ the <tt class="filename">/etc/nsswitch.conf</tt> file. At this point it will be possible to ping any MS Windows machine by it's NetBIOS machine name, so long as that machine is within the workgroup to which both the samba machine and the MS Windows machine belong. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2978479"></a>Name resolution as used within MS Windows networking</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982637"></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", @@ -14621,7 +14677,7 @@ NBT or NetBT, the NetBIOS over TCP/IP. MS Windows machines use a complex array of name resolution mechanisms. Since we are primarily concerned with TCP/IP this demonstration is limited to this area. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978604"></a>The NetBIOS Name Cache</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982784"></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 @@ -14639,7 +14695,7 @@ frustrating for users - but it is a characteristic of the protocol. 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="id2978648"></a>The LMHOSTS file</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982829"></a>The LMHOSTS 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 machine name in matched pairs. The @@ -14656,7 +14712,7 @@ It typically looks like: # This file contains the mappings of IP addresses to NT computernames # (NetBIOS) names. Each entry should be kept on an individual line. # The IP address should be placed in the first column followed by the - # corresponding computername. The address and the comptername + # 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). @@ -14688,7 +14744,7 @@ It typically looks like: # centralized lmhosts file to be maintained on a server. # It is ALWAYS necessary to provide a mapping for the IP address of the # server prior to the #INCLUDE. This mapping must use the #PRE directive. - # In addtion the share "public" in the example below must be in the + # 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 @@ -14724,14 +14780,14 @@ It typically looks like: # so keeping the number of comments to a minimum will improve performance. # Therefore it is not advisable to simply add lmhosts file entries onto the # end of this file. -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978762"></a>HOSTS file</h3></div></div><div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983073"></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="id2978795"></a>DNS Lookup</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983105"></a>DNS Lookup</h3></div></div><div></div></div><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 what the NetBIOS @@ -14742,8 +14798,8 @@ 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="id2978820"></a>WINS Lookup</h3></div></div><div></div></div><p> -A WINS (Windows Internet Name Server) service is the equivaent of the +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983130"></a>WINS Lookup</h3></div></div><div></div></div><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. @@ -14761,23 +14817,23 @@ needed in the <tt class="filename">smb.conf</tt> file: </pre><p> where <i class="replaceable"><tt>xxx.xxx.xxx.xxx</tt></i> is the IP address of the WINS server. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2978890"></a>Common Errors</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983200"></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 keybaord mishaps, forgetfulness, simple mistakes, and -carelessness. Of course, noone is every deliberately careless! -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978906"></a>My Boomerang Won't Come Back</h3></div></div><div></div></div><p> +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="id2983216"></a>My Boomerang Won't Come Back</h3></div></div><div></div></div><p> Well, the real complaint said, "I can ping my samba server from Windows, but I can not ping my Windows machine from the samba server." </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 netmast 255.255.255.128. + 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="id2978938"></a>Very Slow Network Connections</h3></div></div><div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983248"></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 xmlns:ns93="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2978989"></a>Samba server name change problem</h3></div></div><div></div></div><p> + </p><div class="itemizedlist"><ul type="disc"><li><p>Client is configured to use DNS and DNS server is down</p></li><li><p>Client is configured to use remote DNS server, but remote connection is down</p></li><li><p>Client is configured to use a WINS server, but there is no WINS server</p></li><li><p>Client is NOT configured to use a WINS server, but there is a WINS server</p></li><li><p>Firewall is filtering our DNS or WINS traffic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983300"></a>Samba server name change problem</h3></div></div><div></div></div><p> 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? @@ -14786,8 +14842,8 @@ carelessness. Of course, noone is every deliberately careless! </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><ns93:p> - </ns93:p><pre class="screen"> + </p><p> + </p><pre class="screen"> C:\temp\>nbtstat -n NetBIOS Local Name Table @@ -14795,7 +14851,7 @@ carelessness. Of course, noone is every deliberately careless! Name Type Status ------------------------------------------------ SLACK <03> UNIQUE Registered - ADMININSTRATOR <03> UNIQUE Registered + ADMINISTRATOR <03> UNIQUE Registered SLACK <00> UNIQUE Registered SARDON <00> GROUP Registered SLACK <20> UNIQUE Registered @@ -14811,13 +14867,13 @@ carelessness. Of course, noone is every deliberately careless! FRODO <20> UNIQUE 192.168.1.1 240 C:\Temp\> - </pre><ns93:p> - </ns93:p><p> + </pre><p> + </p><p> In the above example, FRODO is the Samba server and SLACK is the MS Windows NT4 Workstation. The first listing shows the contents of the Local Name Table (ie: Identity information on the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache. The name cache contains the remote machines known to this workstation. - </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter 27. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2979144">Features and Benefits</a></dt><dt><a href="#id2979186">What are charsets and unicode?</a></dt><dt><a href="#id2979255">Samba and charsets</a></dt><dt><a href="#id2979355">Conversion from old names</a></dt><dt><a href="#id2979401">Japanese charsets</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2979144"></a>Features and Benefits</h2></div></div><div></div></div><p> + </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="unicode"></a>Chapter 27. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2984418">Features and Benefits</a></dt><dt><a href="#id2984620">What are charsets and unicode?</a></dt><dt><a href="#id2984690">Samba and charsets</a></dt><dt><a href="#id2984790">Conversion from old names</a></dt><dt><a href="#id2984835">Japanese charsets</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984418"></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 @@ -14830,9 +14886,9 @@ special mention. For more information about Openi18n please refer to: <a href="#">http://www.openi18n.org/</a>. </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 truely trans-global +<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="id2979186"></a>What are charsets and unicode?</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984620"></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) @@ -14855,11 +14911,11 @@ A big advantage of using a multibyte charset is that you only need one; no need to make sure two computers use the same charset when they are communicating. </p><p>Old windows clients used to use single-byte charsets, named -'codepages' by microsoft. However, there is no support for +'codepages' by Microsoft. However, there is no support for negotiating the charset to be used in the smb protocol. Thus, you have to make sure you are using the same charset when talking to an old client. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2979255"></a>Samba and charsets</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984690"></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"><i class="parameter"><tt>unix charset</tt></i></span></dt><dd><p> @@ -14873,14 +14929,14 @@ samba knows of three kinds of character sets: 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="id2979355"></a>Conversion from old names</h2></div></div><div></div></div><p>Because previous samba versions did not do any charset conversion, + </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984790"></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>The following script from Steve Langasek converts all filenames from CP850 to the iso8859-15 charset.</p><p> <tt class="prompt">#</tt><b class="userinput"><tt>find <i class="replaceable"><tt>/path/to/share</tt></i> -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; </tt></b> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2979401"></a>Japanese charsets</h2></div></div><div></div></div><p>Samba doesn't work correctly with Japanese charsets yet. Here are +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984835"></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 <i class="parameter"><tt>mangling method = hash</tt></i></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 @@ -14890,28 +14946,28 @@ Shift_JIS, SJIS...</p></li><li><p>Currently only <i class="parameter"><tt>unix c will work (but still has some problems...) because of iconv() issues. <i class="parameter"><tt>unix charset = EUC-JP</tt></i> doesn't work well because of iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <i class="parameter"><tt>unix charset -= UTF8-MAC/CAP/HEX/JIS*</tt></i></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><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter 28. Samba Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2981995">Note</a></dt><dt><a href="#id2982016">Features and Benefits</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2981995"></a>Note</h2></div></div><div></div></div><p> += UTF8-MAC/CAP/HEX/JIS*</tt></i></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><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Backup"></a>Chapter 28. Samba Backup Techniques</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2984038">Note</a></dt><dt><a href="#id2984063">Features and Benefits</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984038"></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. If you have something to contribute for this section please email it to <a href="#">jht@samba.org</a>/ -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982016"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984063"></a>Features and Benefits</h2></div></div><div></div></div><p> We need feedback from people who are backing up samba servers. We would like to know what software tools you are using to backup your samba server/s. </p><p> In particular, if you have any success and / or failure stories you could share with other users this would be appreciated. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter 29. High Availability Options</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2981826">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2981826"></a>Note</h2></div></div><div></div></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SambaHA"></a>Chapter 29. High Availability Options</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2985605">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2985605"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. -</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Migration and Updating</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2983161">Charsets</a></dt><dt><a href="#id2983184">Obsolete configuration options</a></dt><dt><a href="#id2983238">Password Backend</a></dt></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2982481">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2982505">Objectives</a></dt><dt><a href="#id2981433">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2983650">Migration Options</a></dt><dd><dl><dt><a href="#id2983731">Planning for Success</a></dt><dt><a href="#id2983972">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2984279">Features and Benefits</a></dt><dd><dl><dt><a href="#id2984129">Enabling SWAT for use</a></dt><dt><a href="#id2985018">Securing SWAT through SSL</a></dt><dt><a href="#id2985131">The SWAT Home Page</a></dt><dt><a href="#id2985194">Global Settings</a></dt><dt><a href="#id2985300">Share Settings</a></dt><dt><a href="#id2985365">Printers Settings</a></dt><dt><a href="#id2985429">The SWAT Wizard</a></dt><dt><a href="#id2985477">The Status Page</a></dt><dt><a href="#id2985529">The View Page</a></dt><dt><a href="#id2985552">The Password Change Page</a></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">25 October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2983161">Charsets</a></dt><dt><a href="#id2983184">Obsolete configuration options</a></dt><dt><a href="#id2983238">Password Backend</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983161"></a>Charsets</h2></div></div><div></div></div><p>You might experience problems with special characters +</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="migration"></a>Migration and Updating</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2984190">Charsets</a></dt><dt><a href="#id2984215">Obsolete configuration options</a></dt><dt><a href="#id2985825">Password Backend</a></dt></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2983845">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2983873">Objectives</a></dt><dt><a href="#id2986549">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2986887">Migration Options</a></dt><dd><dl><dt><a href="#id2986968">Planning for Success</a></dt><dt><a href="#id2987210">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2986434">Features and Benefits</a></dt><dd><dl><dt><a href="#id2986468">Enabling SWAT for use</a></dt><dt><a href="#id2988827">Securing SWAT through SSL</a></dt><dt><a href="#id2988941">The SWAT Home Page</a></dt><dt><a href="#id2989005">Global Settings</a></dt><dt><a href="#id2989110">Share Settings</a></dt><dt><a href="#id2989175">Printers Settings</a></dt><dt><a href="#id2989239">The SWAT Wizard</a></dt><dt><a href="#id2989287">The Status Page</a></dt><dt><a href="#id2989339">The View Page</a></dt><dt><a href="#id2989362">The Password Change Page</a></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">25 October 2002</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2984190">Charsets</a></dt><dt><a href="#id2984215">Obsolete configuration options</a></dt><dt><a href="#id2985825">Password Backend</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984190"></a>Charsets</h2></div></div><div></div></div><p>You might experience problems with special characters when communicating with old DOS clients. Codepage support has changed in samba 3.0. Read the chapter <a href="#unicode" title="Chapter 27. Unicode/Charsets">Unicode support</a> for details. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983184"></a>Obsolete configuration options</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984215"></a>Obsolete configuration options</h2></div></div><div></div></div><p> In 3.0, the following configuration options have been removed. -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>printer driver (replaced by new driver procedures) </td></tr><tr><td>printer driver file (replaced by new driver procedures)</td></tr><tr><td>printer driver location (replaced by new driver procedures)</td></tr><tr><td>use rhosts</td></tr><tr><td>postscript</td></tr><tr><td>client code page (replaced by dos charset)</td></tr><tr><td>vfs path</td></tr><tr><td>vfs options</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983238"></a>Password Backend</h2></div></div><div></div></div><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>printer driver (replaced by new driver procedures) </td></tr><tr><td>printer driver file (replaced by new driver procedures)</td></tr><tr><td>printer driver location (replaced by new driver procedures)</td></tr><tr><td>use rhosts</td></tr><tr><td>postscript</td></tr><tr><td>client code page (replaced by dos charset)</td></tr><tr><td>vfs path</td></tr><tr><td>vfs options</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2985825"></a>Password Backend</h2></div></div><div></div></div><p> Effective with the release of samba-3 it is now imperative that the password backend be correctly defined in smb.conf. </p><p> @@ -14923,18 +14979,18 @@ Those migrating from samba-2.x with encrypted password support should add to smb </p><p> LDAP using Samba-2.x systems can continue to operate with the following entry <span class="emphasis"><em>passdb backend = ldapsam_compat, guest</em></span>. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter 31. Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2982481">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2982505">Objectives</a></dt><dt><a href="#id2981433">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2983650">Migration Options</a></dt><dd><dl><dt><a href="#id2983731">Planning for Success</a></dt><dt><a href="#id2983972">Samba Implementation Choices</a></dt></dl></dd></dl></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter 31. Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2983845">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2983873">Objectives</a></dt><dt><a href="#id2986549">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2986887">Migration Options</a></dt><dd><dl><dt><a href="#id2986968">Planning for Success</a></dt><dt><a href="#id2987210">Samba Implementation Choices</a></dt></dl></dd></dl></div><p> This is a rough guide to assist those wishing to migrate from NT4 domain control to Samba-3 based domain control. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2982481"></a>Planning and Getting Started</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983845"></a>Planning and Getting Started</h2></div></div><div></div></div><p> In the IT world there is often a saying that all problems are encountered because of -poor planning. The corrollary to this saying is that not all problems can be anticpated -and planned for. Then again, good planning will anticpate most show stopper type situations. +poor planning. The corollary to this saying is that not all problems can be anticipated +and planned for. Then again, good planning will anticipate most show stopper type situations. </p><p> Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control environment would do well to develop a detailed migration plan. So here are a few pointers to help migration get under way. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2982505"></a>Objectives</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983873"></a>Objectives</h3></div></div><div></div></div><p> The key objective for most organisations will be to make the migration from MS Windows NT4 to Samba-3 domain control as painless as possible. One of the challenges you may experience in your migration process may well be one of convincing management that the new environment @@ -14953,15 +15009,15 @@ features that Microsoft has promoted as core values in migration from MS Windows MS Windows 2000 and beyond (with or without Active Directory services). </p><p> What are the features that Samba-3 can NOT provide? -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Active Directory Server</td></tr><tr><td>Group Policy Objects (in Active Direcrtory)</td></tr><tr><td>Machine Policy objects</td></tr><tr><td>Logon Scripts in Active Directorty</td></tr><tr><td>Software Application and Access Controls in Active Directory</td></tr></table><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Active Directory Server</td></tr><tr><td>Group Policy Objects (in Active Directory)</td></tr><tr><td>Machine Policy objects</td></tr><tr><td>Logon Scripts in Active Directory</td></tr><tr><td>Software Application and Access Controls in Active Directory</td></tr></table><p> The features that Samba-3 DOES provide and that may be of compelling interest to your site includes: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Lower Cost of Ownership</td></tr><tr><td>Global availability of support with no strings attached</td></tr><tr><td>Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)</td></tr><tr><td>Creation of on-the-fly logon scripts</td></tr><tr><td>Creation of on-the-fly Policy Files</td></tr><tr><td>Greater Stability, Reliability, Performance and Availability</td></tr><tr><td>Manageability via an ssh connection</td></tr><tr><td>Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)</td></tr><tr><td>Ability to implement a full single-signon architecture</td></tr><tr><td>Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand</td></tr></table><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Lower Cost of Ownership</td></tr><tr><td>Global availability of support with no strings attached</td></tr><tr><td>Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)</td></tr><tr><td>Creation of on-the-fly logon scripts</td></tr><tr><td>Creation of on-the-fly Policy Files</td></tr><tr><td>Greater Stability, Reliability, Performance and Availability</td></tr><tr><td>Manageability via an ssh connection</td></tr><tr><td>Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)</td></tr><tr><td>Ability to implement a full single-sign-on architecture</td></tr><tr><td>Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand</td></tr></table><p> Before migrating a network from MS Windows NT4 to Samba-3 it is vital that all necessary factors are considered. Users should be educated about changes they may experience so that the change will be a welcome one and not become an obstacle to the work they need to do. The following are some of the factors that will go into a successful migration: -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2981206"></a>Domain Layout</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2985388"></a>Domain Layout</h4></div></div><div></div></div><p> Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called a secondary controller), a domain member, or as a stand-alone server. The Windows network security domain context should be sized and scoped before implementation. Particular attention needs to be @@ -14978,11 +15034,11 @@ and network bandwidth. A physical network segment may house several domains, each of which may span multiple network segments. Where domains span routed network segments it is most advisable to consider and test the performance implications of the design and layout of a network. A Centrally located domain controller that is being -designed to serve mulitple routed network segments may result in severe performance problems if the +designed to serve multiple routed network segments may result in severe performance problems if the response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as the local authentication and access control server. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2981260"></a>Server Share and Directory Layout</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2985441"></a>Server Share and Directory Layout</h4></div></div><div></div></div><p> There are few cardinal rules to effective network design that can be broken with impunity. The most important rule of effective network management is that simplicity is king in every well controlled network. Every part of the infrastructure must be managed, the more complex @@ -15007,48 +15063,48 @@ complex mess that has been inherited. Remember, apparent job security through co and implementation may ultimately cause loss of operations and downtime to users as the new administrator learns to untangle your web. Keep access controls simple and effective and make sure that users will never be interrupted by the stupidity of complexity. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2981321"></a>Logon Scripts</h4></div></div><div></div></div><p> -Please refer to the section of this document on Advanced Network Adminsitration for information +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2985503"></a>Logon Scripts</h4></div></div><div></div></div><p> +Please refer to the section of this document on Advanced Network Administration for information regarding the network logon script options for Samba-3. Logon scripts can help to ensure that all users gain share and printer connections they need. </p><p> Logon scripts can be created on-the-fly so that all commands executed are specific to the -rights and privilidges granted to the user. The preferred controls should be affected through -group membership so that group information can be used to custom create a logong script using +rights and privileges granted to the user. The preferred controls should be affected through +group membership so that group information can be used to custom create a logon script using the <i class="parameter"><tt>root preexec</tt></i> parameters to the <tt class="filename">NETLOGON</tt> share. </p><p> Some sites prefer to use a tool such as <b class="command">kixstart</b> to establish a controlled user environment. In any case you may wish to do a google search for logon script process controls. In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that deals with how to add printers without user intervention via the logon script process. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2981379"></a>Profile Migration/Creation</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2985560"></a>Profile Migration/Creation</h4></div></div><div></div></div><p> User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile Management. </p><p> Profiles may also be managed using the Samba-3 tool <b class="command">profiles</b>. This tool allows the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file to be changed to the SID of the Samba-3 domain. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2981408"></a>User and Group Accounts</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2986523"></a>User and Group Accounts</h4></div></div><div></div></div><p> It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the groups that are present on the MS Windows NT4 domain <span class="emphasis"><em>AND</em></span> to connect these to suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes should migrate painlessly. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2981433"></a>Steps In Migration Process</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2986549"></a>Steps In Migration Process</h3></div></div><div></div></div><p> The approximate migration process is described below. </p><div class="itemizedlist"><ul type="disc"><li><p> You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated </p></li><li><p> Samba-3 set up as a DC with netlogon share, profile share, etc. -</p></li></ul></div><div class="procedure"><p class="title"><b>Procedure 31.1. The Account Migration Process</b></p><ol type="1"><li><p>Create a BDC account for the samba server using NT Server Manager</p><ol type="a"><li><p>Samba must NOT be running</p></li></ol></li><li><p><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>NT4PDC</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p><ol type="a"><li><p>lsaquery</p></li><li><p>Note the SID returned</p></li></ol></li><li><p><b class="userinput"><tt>net getsid -S <i class="replaceable"><tt>NT4PDC</tt></i> -w <i class="replaceable"><tt>DOMNAME</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p><ol type="a"><li><p>Note the SID</p></li></ol></li><li><p><b class="userinput"><tt>net getlocalsid</tt></b></p><ol type="a"><li><p>Note the SID, now check that all three SIDS reported are the same!</p></li></ol></li><li><p><b class="userinput"><tt>net rpc join -S <i class="replaceable"><tt>NT4PDC</tt></i> -w <i class="replaceable"><tt>DOMNAME</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>net rpc vampire -S <i class="replaceable"><tt>NT4PDC</tt></i> -U administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>pdbedit -L</tt></b></p><ol type="a"><li><p>Note - did the users migrate?</p></li></ol></li><li><p><b class="userinput"><tt>initGrps.sh <i class="replaceable"><tt>DOMNAME</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>net groupmap list</tt></b></p><ol type="a"><li><p>Now check that all groups are recognised</p></li></ol></li><li><p><b class="userinput"><tt>net rpc campire -S <i class="replaceable"><tt>NT4PDC</tt></i> -U administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>pdbedit -Lv</tt></b></p><ol type="a"><li><p>Note - check that all group membership has been migrated</p></li></ol></li></ol></div><p> +</p></li></ul></div><div class="procedure"><p class="title"><b>Procedure 31.1. The Account Migration Process</b></p><ol type="1"><li><p>Create a BDC account for the samba server using NT Server Manager</p><ol type="a"><li><p>Samba must NOT be running</p></li></ol></li><li><p><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>NT4PDC</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p><ol type="a"><li><p>lsaquery</p></li><li><p>Note the SID returned</p></li></ol></li><li><p><b class="userinput"><tt>net getsid -S <i class="replaceable"><tt>NT4PDC</tt></i> -w <i class="replaceable"><tt>DOMNAME</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p><ol type="a"><li><p>Note the SID</p></li></ol></li><li><p><b class="userinput"><tt>net getlocalsid</tt></b></p><ol type="a"><li><p>Note the SID, now check that all three SIDS reported are the same!</p></li></ol></li><li><p><b class="userinput"><tt>net rpc join -S <i class="replaceable"><tt>NT4PDC</tt></i> -w <i class="replaceable"><tt>DOMNAME</tt></i> -U Administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>net rpc vampire -S <i class="replaceable"><tt>NT4PDC</tt></i> -U administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>pdbedit -L</tt></b></p><ol type="a"><li><p>Note - did the users migrate?</p></li></ol></li><li><p><b class="userinput"><tt>initGrps.sh <i class="replaceable"><tt>DOMNAME</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>net groupmap list</tt></b></p><ol type="a"><li><p>Now check that all groups are recognised</p></li></ol></li><li><p><b class="userinput"><tt>net rpc vampire -S <i class="replaceable"><tt>NT4PDC</tt></i> -U administrator%<i class="replaceable"><tt>passwd</tt></i></tt></b></p></li><li><p><b class="userinput"><tt>pdbedit -Lv</tt></b></p><ol type="a"><li><p>Note - check that all group membership has been migrated</p></li></ol></li></ol></div><p> Now it is time to migrate all the profiles, then migrate all policy files. More later. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2983650"></a>Migration Options</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2986887"></a>Migration Options</h2></div></div><div></div></div><p> Based on feedback from many sites as well as from actual installation and maintenance experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba based solution fit into three basic categories. -</p><div class="table"><a name="id2983665"></a><p class="title"><b>Table 31.1. The 3 Major Site Types</b></p><table summary="The 3 Major Site Types" border="1"><colgroup><col><col></colgroup><thead><tr><th>Number of Users</th><th>Description</th></tr></thead><tbody><tr><td>< 50</td><td><p>Want simple conversion with NO pain</p></td></tr><tr><td>50 - 250</td><td><p>Want new features, can manage some in-house complexity</p></td></tr><tr><td>> 250</td><td><p>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</p></td></tr></tbody></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983731"></a>Planning for Success</h3></div></div><div></div></div><p> -There are three basic choices for sites that intend to migrate from MS Windwows NT4 +</p><div class="table"><a name="id2986904"></a><p class="title"><b>Table 31.1. The 3 Major Site Types</b></p><table summary="The 3 Major Site Types" border="1"><colgroup><col><col></colgroup><thead><tr><th>Number of Users</th><th>Description</th></tr></thead><tbody><tr><td>< 50</td><td><p>Want simple conversion with NO pain</p></td></tr><tr><td>50 - 250</td><td><p>Want new features, can manage some in-house complexity</p></td></tr><tr><td>> 250</td><td><p>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</p></td></tr></tbody></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2986968"></a>Planning for Success</h3></div></div><div></div></div><p> +There are three basic choices for sites that intend to migrate from MS Windows NT4 to Samba-3. </p><div class="itemizedlist"><ul type="disc"><li><p> Simple Conversion (total replacement) @@ -15066,20 +15122,20 @@ No matter what choice you make, the following rules will minimise down-stream pr Test ALL assumptions </p></li><li><p> Test full roll-out program, including workstation deployment - </p></li></ul></div><div class="table"><a name="id2983801"></a><p class="title"><b>Table 31.2. Nature of the Conversion Choices</b></p><table summary="Nature of the Conversion Choices" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Simple</th><th>Upgraded</th><th>Redesign</th></tr></thead><tbody><tr><td><p>Make use of minimal OS specific features</p></td><td><p>Translate NT4 features to new host OS features</p></td><td><p>Decide:</p></td></tr><tr><td><p>Suck all accounts from NT4 into Samba-3</p></td><td><p>Copy and improve:</p></td><td><p>Authentication Regime (database location and access)</p></td></tr><tr><td><p>Make least number of operational changes</p></td><td><p>Make progressive improvements</p></td><td><p>Desktop Management Methods</p></td></tr><tr><td><p>Take least amount of time to migrate</p></td><td><p>Minimise user impact</p></td><td><p>Better Control of Desktops / Users</p></td></tr><tr><td><p>Live versus Isolated Conversion</p></td><td><p>Maximise functionality</p></td><td><p>Identify Needs for: Manageability, Scalability, Security, Availability</p></td></tr><tr><td><p>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</p></td><td><p>Take advantage of lower maintenance opportunity</p></td><td><p></p></td></tr></tbody></table></div></div><div xmlns:ns94="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2983972"></a>Samba Implementation Choices</h3></div></div><div></div></div><pre class="programlisting"> + </p></li></ul></div><div class="table"><a name="id2987041"></a><p class="title"><b>Table 31.2. Nature of the Conversion Choices</b></p><table summary="Nature of the Conversion Choices" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Simple</th><th>Upgraded</th><th>Redesign</th></tr></thead><tbody><tr><td><p>Make use of minimal OS specific features</p></td><td><p>Translate NT4 features to new host OS features</p></td><td><p>Decide:</p></td></tr><tr><td><p>Suck all accounts from NT4 into Samba-3</p></td><td><p>Copy and improve:</p></td><td><p>Authentication Regime (database location and access)</p></td></tr><tr><td><p>Make least number of operational changes</p></td><td><p>Make progressive improvements</p></td><td><p>Desktop Management Methods</p></td></tr><tr><td><p>Take least amount of time to migrate</p></td><td><p>Minimise user impact</p></td><td><p>Better Control of Desktops / Users</p></td></tr><tr><td><p>Live versus Isolated Conversion</p></td><td><p>Maximise functionality</p></td><td><p>Identify Needs for: Manageability, Scalability, Security, Availability</p></td></tr><tr><td><p>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</p></td><td><p>Take advantage of lower maintenance opportunity</p></td><td><p></p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2987210"></a>Samba Implementation Choices</h3></div></div><div></div></div><pre class="programlisting"> Authentication database back end Winbind (external Samba or NT4/200x server) Can use pam_mkhomedir.so to auto-create home dirs External server could use Active Directory or NT4 Domain Database type - smbpasswd, tdbsam, ldapsam, MySQLsam + smbpasswd, tdbsam, ldapsam, mysqlsam Access Control Points On the Share itself (Use NT4 Server Manager) On the file system Unix permissions on files and directories - Posix ACLs enablement in file system? + Enable Posix ACLs in file system? Through Samba share parameters Not recommended - except as only resort @@ -15123,8 +15179,8 @@ Migration Tools Authentication New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam) -</pre><ns94:p> -</ns94:p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter 32. SWAT - The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2984279">Features and Benefits</a></dt><dd><dl><dt><a href="#id2984129">Enabling SWAT for use</a></dt><dt><a href="#id2985018">Securing SWAT through SSL</a></dt><dt><a href="#id2985131">The SWAT Home Page</a></dt><dt><a href="#id2985194">Global Settings</a></dt><dt><a href="#id2985300">Share Settings</a></dt><dt><a href="#id2985365">Printers Settings</a></dt><dt><a href="#id2985429">The SWAT Wizard</a></dt><dt><a href="#id2985477">The Status Page</a></dt><dt><a href="#id2985529">The View Page</a></dt><dt><a href="#id2985552">The Password Change Page</a></dt></dl></dd></dl></div><p> +</pre><p> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter 32. SWAT - The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2986434">Features and Benefits</a></dt><dd><dl><dt><a href="#id2986468">Enabling SWAT for use</a></dt><dt><a href="#id2988827">Securing SWAT through SSL</a></dt><dt><a href="#id2988941">The SWAT Home Page</a></dt><dt><a href="#id2989005">Global Settings</a></dt><dt><a href="#id2989110">Share Settings</a></dt><dt><a href="#id2989175">Printers Settings</a></dt><dt><a href="#id2989239">The SWAT Wizard</a></dt><dt><a href="#id2989287">The Status Page</a></dt><dt><a href="#id2989339">The View Page</a></dt><dt><a href="#id2989362">The Password Change Page</a></dt></dl></dd></dl></div><p> There are many and varied opinions regarding the usefulness or otherwise of SWAT. No matter how hard one tries to produce the perfect configuration tool it remains an object of personal taste. SWAT is a tool that will allow web based configuration @@ -15132,7 +15188,7 @@ of samba. It has a wizard that may help to get samba configured quickly, it has sensitive help on each smb.conf parameter, it provides for monitoring of current state of connection information, and it allows network wide MS Windows network password management. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2984279"></a>Features and Benefits</h2></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2986434"></a>Features and Benefits</h2></div></div><div></div></div><p> There are network administrators who believe that it is a good idea to write systems documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT does not store the configuration file in any intermediate form, rather, it stores only the @@ -15144,7 +15200,7 @@ internal ordering. So before using SWAT please be warned - SWAT will completely replace your smb.conf with a fully optimised file that has been stripped of all comments you might have placed there and only non-default settings will be written to the file. -</p></div><div xmlns:ns95="" class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2984129"></a>Enabling SWAT for use</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2986468"></a>Enabling SWAT for use</h3></div></div><div></div></div><p> SWAT should be installed to run via the network super daemon. Depending on which system your Unix/Linux system has you will have either an <b class="command">inetd</b> or <b class="command">xinetd</b> based system. @@ -15160,8 +15216,8 @@ The control entry for the older style file might be: swat stream tcp nowait.400 root /usr/sbin/swat swat </pre><p> A control file for the newer style xinetd could be: -</p><ns95:p> -</ns95:p><pre class="programlisting"> +</p><p> +</p><pre class="programlisting"> # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ @@ -15177,9 +15233,9 @@ A control file for the newer style xinetd could be: log_on_failure += USERID disable = yes } -</pre><ns95:p> +</pre><p> -</ns95:p><p> +</p><p> Both the above examples assume that the <b class="command">swat</b> binary has been located in the <tt class="filename">/usr/sbin</tt> directory. In addition to the above SWAT will use a directory access point from which it will load it's help files @@ -15198,48 +15254,48 @@ So long as you log onto SWAT as the user <span class="emphasis"><em>root</em></s full change and commit ability. The buttons that will be exposed includes: <span class="guibutton">HOME</span>, <span class="guibutton">GLOBALS</span>, <span class="guibutton">SHARES</span>, <span class="guibutton">PRINTERS</span>, <span class="guibutton">WIZARD</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, <span class="guibutton">PASSWORD</span>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985018"></a>Securing SWAT through SSL</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2988827"></a>Securing SWAT through SSL</h3></div></div><div></div></div><p> Lots of people have asked about how to setup SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger </p><p> Modifications to the swat setup are as following: </p><div class="procedure"><ol type="1"><li><p> install OpenSSL - </p></li><li xmlns:ns96=""><ns96:p> + </p></li><li><p> generate certificate and private key - </ns96:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>/usr/bin/openssl req -new -x509 -days 365 -nodes -config \ /usr/share/doc/packages/stunnel/stunnel.cnf \ -out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem</tt></b> </pre></li><li><p> remove swat-entry from [x]inetd - </p></li><li xmlns:ns97=""><ns97:p> + </p></li><li><p> start stunnel - </ns97:p><pre class="screen"> + </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>stunnel -p /etc/stunnel/stunnel.pem -d 901 \ -l /usr/local/samba/bin/swat swat </tt></b> </pre></li></ol></div><p> -afterwards simply contact to swat by using the URL <a href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate +afterwords simply contact to swat by using the URL <a href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate and the SSL connection is up. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985131"></a>The SWAT Home Page</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2988941"></a>The SWAT Home Page</h3></div></div><div></div></div><p> The SWAT title page provides access to the latest Samba documentation. The manual page for each samba component is accessible from this page as are the Samba-HOWTO-Collection (this document) as well as the O'Reilly book "Using Samba". </p><p> Administrators who wish to validate their samba configuration may obtain useful information -from the man pages for the diganostic utilities. These are available from the SWAT home page +from the man pages for the diagnostic utilities. These are available from the SWAT home page also. One diagnostic tool that is NOT mentioned on this page, but that is particularly useful is <b class="command">ethereal</b>, available from <a href="http://www.ethereal.com" target="_top"> http://www.ethereal.com</a>. </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> SWAT can be configured to run in <span class="emphasis"><em>demo</em></span> mode. This is NOT recommended as it runs SWAT without authentication and with full administrative ability. ie: Allows -changes to smb.conf as well as general operation with root privilidges. The option that +changes to smb.conf as well as general operation with root privileges. The option that creates this ability is the <tt class="option">-a</tt> flag to swat. <span class="emphasis"><em>Do not use this in any production environment.</em></span> -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985194"></a>Global Settings</h3></div></div><div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989005"></a>Global Settings</h3></div></div><div></div></div><p> The Globals button will expose a page that allows configuration of the global parameters in smb.conf. There are three levels of exposure of the parameters: </p><div class="itemizedlist"><ul type="disc"><li><p> @@ -15260,9 +15316,9 @@ After making any changes to configuration parameters make sure that you click on your changes will be immediately lost. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> SWAT has context sensitive help. To find out what each parameter is for simply click the -<span class="guibutton">Help</span> link to the left of the configurartion parameter. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985300"></a>Share Settings</h3></div></div><div></div></div><p> -To affect a currenly configured share, simply click on the pull down button between the +<span class="guibutton">Help</span> link to the left of the configuration parameter. +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989110"></a>Share Settings</h3></div></div><div></div></div><p> +To affect a currently configured share, simply click on the pull down button between the <span class="guibutton">Choose Share</span> and the <span class="guibutton">Delete Share</span> buttons, select the share you wish to operate on, then to edit the settings click on the <span class="guibutton">Choose Share</span> button, to delete the share simply press the @@ -15271,8 +15327,8 @@ select the share you wish to operate on, then to edit the settings click on the To create a new share, next to the button labelled <span class="guibutton">Create Share</span> enter into the text field the name of the share to be created, then click on the <span class="guibutton">Create Share</span> button. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985365"></a>Printers Settings</h3></div></div><div></div></div><p> -To affect a currenly configured printer, simply click on the pull down button between the +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989175"></a>Printers Settings</h3></div></div><div></div></div><p> +To affect a currently configured printer, simply click on the pull down button between the <span class="guibutton">Choose Printer</span> and the <span class="guibutton">Delete Printer</span> buttons, select the printer you wish to operate on, then to edit the settings click on the <span class="guibutton">Choose Printer</span> button, to delete the share simply press the @@ -15281,23 +15337,23 @@ select the printer you wish to operate on, then to edit the settings click on th To create a new printer, next to the button labelled <span class="guibutton">Create Printer</span> enter into the text field the name of the share to be created, then click on the <span class="guibutton">Create Printer</span> button. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985429"></a>The SWAT Wizard</h3></div></div><div></div></div><p> -The purpose if the SWAT Wizard is to help the Microsoft knowledgable network administrator +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989239"></a>The SWAT Wizard</h3></div></div><div></div></div><p> +The purpose if the SWAT Wizard is to help the Microsoft knowledgeable network administrator to configure Samba with a minimum of effort. </p><p> -The Wizard page provides a tool for rewiting the smb.conf file in fully optimised format. +The Wizard page provides a tool for rewriting the smb.conf file in fully optimised format. This will also happen if you press the commit button. The two differ in the the rewrite button ignores any changes that may have been made, while the Commit button causes all changes to be affected. </p><p> The <span class="guibutton">Edit</span> button permits the editing (setting) of the minimal set of -options that may be necessary to create a working samba server. +options that may be necessary to create a working Samba server. </p><p> -Finally, there are a limited set of options that will determine what type of server samba +Finally, there are a limited set of options that will determine what type of server Samba will be configured for, whether it will be a WINS server, participate as a WINS client, or -operate with no WINS support. By clicking on one button you can elect to epose (or not) user +operate with no WINS support. By clicking on one button you can elect to expose (or not) user home directories. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985477"></a>The Status Page</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989287"></a>The Status Page</h3></div></div><div></div></div><p> The status page serves a limited purpose. Firstly, it allows control of the samba daemons. The key daemons that create the samba server environment are: <span class="application">smbd</span>, <span class="application">nmbd</span>, <span class="application">winbindd</span>. </p><p> @@ -15308,11 +15364,11 @@ conditions with minimal effort. </p><p> Lastly, the Status page may be used to terminate specific smbd client connections in order to free files that may be locked. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985529"></a>The View Page</h3></div></div><div></div></div><p> -This page allows the administrator to view the optimised <tt class="filename">smb.conf</tt> file and if you are -particularly massochistic will permit you also to see all possible global configuration +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989339"></a>The View Page</h3></div></div><div></div></div><p> +This page allows the administrator to view the optimised <tt class="filename">smb.conf</tt> file and, if you are +particularly masochistic, will permit you also to see all possible global configuration parameters and their settings. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2985552"></a>The Password Change Page</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989362"></a>The Password Change Page</h3></div></div><div></div></div><p> The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation and reactivation of MS Windows networking users on the local machine. Alternatively, you can use this tool to change a local password for a user account. @@ -15323,7 +15379,7 @@ required. </p><p> One popular use for this tool is to change user passwords across a range of remote MS Windows servers. -</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>33. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2985673">Introduction</a></dt><dt><a href="#id2985707">Assumptions</a></dt><dt><a href="#id2985879">The tests</a></dt><dt><a href="#id2989430">Still having troubles?</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2990823">Diagnostics tools</a></dt><dt><a href="#id2989549">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2989832">Useful URL's</a></dt><dt><a href="#id2989876">Getting help from the mailing lists</a></dt><dt><a href="#id2990029">How to get off the mailinglists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2992343">Introduction</a></dt><dt><a href="#id2992402">General info</a></dt><dt><a href="#id2992438">Debug levels</a></dt><dt><a href="#id2990534">Internal errors</a></dt><dt><a href="#id2990642">Attaching to a running process</a></dt><dt><a href="#id2990144">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter 33. The samba checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2985673">Introduction</a></dt><dt><a href="#id2985707">Assumptions</a></dt><dt><a href="#id2985879">The tests</a></dt><dt><a href="#id2989430">Still having troubles?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2985673"></a>Introduction</h2></div></div><div></div></div><p> +</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2988578">Introduction</a></dt><dt><a href="#id2990437">Assumptions</a></dt><dt><a href="#id2990614">The tests</a></dt><dt><a href="#id2991790">Still having troubles?</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2993414">Diagnostics tools</a></dt><dt><a href="#id2993555">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2993839">Useful URLs</a></dt><dt><a href="#id2993884">Getting help from the mailing lists</a></dt><dt><a href="#id2994036">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2994775">Introduction</a></dt><dt><a href="#id2994997">General info</a></dt><dt><a href="#id2995034">Debug levels</a></dt><dt><a href="#id2995176">Internal errors</a></dt><dt><a href="#id2995284">Attaching to a running process</a></dt><dt><a href="#id2995331">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="diagnosis"></a>Chapter 33. The Samba checklist</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2988578">Introduction</a></dt><dt><a href="#id2990437">Assumptions</a></dt><dt><a href="#id2990614">The tests</a></dt><dt><a href="#id2991790">Still having troubles?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2988578"></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 @@ -15338,7 +15394,7 @@ to solve a problem. If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then you should not be surprised if your email is ignored. -</p></div><div xmlns:ns98="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2985707"></a>Assumptions</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990437"></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> @@ -15355,8 +15411,8 @@ following to <tt class="filename">smb.conf</tt>: path = /tmp read only = yes -</pre><ns98:p> -</ns98:p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +</pre><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> @@ -15379,7 +15435,7 @@ depending on how or if you specified logging in your <tt class="filename">smb.co </p><p> If you make changes to your <tt class="filename">smb.conf</tt> file while going through these test, don't forget to restart <span class="application">smbd</span> and <span class="application">nmbd</span>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2985879"></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><ol type="1"><li><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990614"></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><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. @@ -15447,7 +15503,7 @@ the following <tt class="filename">smb.conf</tt> file entries: bind interfaces only = Yes </pre><p> In the above, no allowance has been made for any session requests that -will automatically translate to the loopback adaptor address 127.0.0.1. +will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem change these lines to: </p><pre class="programlisting"> hosts deny = ALL @@ -15470,7 +15526,7 @@ to start <span class="application">smbd</span> as a daemon, it can avoid a lot o And yet another possible cause for failure of this test is when the subnet mask and / or broadcast address settings are incorrect. Please check that the network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the <tt class="filename">log.nmb</tt> file. +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. @@ -15495,7 +15551,7 @@ 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/TCPIP hosts on the network should respond, although Samba may +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. @@ -15530,7 +15586,7 @@ name</span> then the service <span class="emphasis"><em>"tmp"</em></sp </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 passords (or some other password system) but didn't + 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 <b class="command">valid users</b> configuration is incorrect @@ -15560,10 +15616,10 @@ to choose one of them): 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. + 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 + the TCP/IP setup </p></li><li><p> add BIGSERVER to your lmhosts file on the PC. </p></li></ol></div><p> @@ -15622,13 +15678,13 @@ capability and is in user level security mode. In this case either set <i class="parameter"><tt>password server = Windows_NT_Machine</tt></i> in your <tt class="filename">smb.conf</tt> file, or make sure <i class="parameter"><tt>encrypted passwords</tt></i> is set to "yes". -</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2989430"></a>Still having troubles?</h2></div></div><div></div></div><p>Read the chapter on +</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2991790"></a>Still having troubles?</h2></div></div><div></div></div><p>Read the chapter on <a href="#problems" title="Chapter 34. Analysing and solving samba problems">Analysing and Solving Problems</a>. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter 34. Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2990823">Diagnostics tools</a></dt><dt><a href="#id2989549">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2989832">Useful URL's</a></dt><dt><a href="#id2989876">Getting help from the mailing lists</a></dt><dt><a href="#id2990029">How to get off the mailinglists</a></dt></dl></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="problems"></a>Chapter 34. Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2993414">Diagnostics tools</a></dt><dt><a href="#id2993555">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2993839">Useful URLs</a></dt><dt><a href="#id2993884">Getting help from the mailing lists</a></dt><dt><a href="#id2994036">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="id2990823"></a>Diagnostics tools</h2></div></div><div></div></div><p> +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="id2993414"></a>Diagnostics tools</h2></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 <i class="parameter"><tt>debug level</tt></i> at which to run. See the man pages on smbd, nmbd and @@ -15650,7 +15706,7 @@ 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>testparam | more</tt></b> + <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><p> An SMB enabled version of tcpdump is available from @@ -15667,7 +15723,7 @@ The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon formatted files. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2989549"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</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="id2993555"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</h2></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 @@ -15706,11 +15762,11 @@ from the Windows 9x CD (<tt class="filename">\admin\nettools\netmon</tt>). Ther file located with the netmon driver files on the CD if you need information on how to do this. Copy the files from a working Netmon installation. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2989832"></a>Useful URL's</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>See how Scott Merrill simulates a BDC behavior at +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2993839"></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="id2989876"></a>Getting help from the mailing lists</h2></div></div><div></div></div><p> + ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2993884"></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>. @@ -15744,7 +15800,7 @@ error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( the pipe to the error ) you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email. Consider pasting the relevant parts into the body of the message. The samba mailing lists go to a huge number of people, do they all need a copy of your -smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990029"></a>How to get off the mailinglists</h2></div></div><div></div></div><p>To have your name removed from a samba mailing list, go to the +smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994036"></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>. Or perhaps see @@ -15752,7 +15808,7 @@ then click on <b class="command"> Samba related mailing lists</b>. Or perhaps se </p><p> Please don't post messages to the list asking to be removed, you will just be referred to the above address (unless that process failed in some way...) -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter 35. Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="surname">Someone; Tridge or Karl Auer perhaps?</span></h3></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="#id2992343">Introduction</a></dt><dt><a href="#id2992402">General info</a></dt><dt><a href="#id2992438">Debug levels</a></dt><dt><a href="#id2990534">Internal errors</a></dt><dt><a href="#id2990642">Attaching to a running process</a></dt><dt><a href="#id2990144">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2992343"></a>Introduction</h2></div></div><div></div></div><p>Please report bugs using +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter 35. Reporting Bugs</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="surname">Someone; Tridge or Karl Auer perhaps?</span></h3></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="#id2994775">Introduction</a></dt><dt><a href="#id2994997">General info</a></dt><dt><a href="#id2995034">Debug levels</a></dt><dt><a href="#id2995176">Internal errors</a></dt><dt><a href="#id2995284">Attaching to a running process</a></dt><dt><a href="#id2995331">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994775"></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 @@ -15774,23 +15830,23 @@ that list that may be able to help you. You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba web pages at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2992402"></a>General info</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994997"></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" title="Chapter 33. The samba checklist">diagnosis</a>? +Have you run through the <a href="#diagnosis" 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="id2992438"></a>Debug levels</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995034"></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 givesmore +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 <i class="parameter"><tt>log level</tt></i> in your @@ -15821,7 +15877,7 @@ 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="id2990534"></a>Internal errors</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995176"></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 @@ -15852,9 +15908,9 @@ If you know any assembly language then do a where the problem occurred (if its in a library routine then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you -don't know assembly then incuding this info in the bug report can be +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="id2990642"></a>Attaching to a running process</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995284"></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 @@ -15864,20 +15920,20 @@ to the running process using Then use <b class="command">c</b> to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990144"></a>Patches</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="id2995331"></a>Patches</h2></div></div><div></div></div><p> The best sort of bug report is one that includes a fix! If you send us patches please use <b class="userinput"><tt>diff -u</tt></b> format if your version of diff supports it, otherwise use <b class="userinput"><tt>diff -c4</tt></b>. Make sure you do the diff against a clean version of the source and let me know exactly what version you used. -</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>36. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2990261">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2990268">Introduction</a></dt><dt><a href="#id2990297">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2991766">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2991814">Verifying Samba's PGP signature</a></dt><dt><a href="#id2991949">Building the Binaries</a></dt><dd><dl><dt><a href="#id2992086">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2992982">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2993073">Starting from inetd.conf</a></dt><dt><a href="#id2993277">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2993372">Common Errors</a></dt></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2994651">HPUX</a></dt><dt><a href="#id2994736">SCO Unix</a></dt><dt><a href="#id2994764">DNIX</a></dt><dt><a href="#id2994934">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2994978">AIX</a></dt><dd><dl><dt><a href="#id2994984">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2995010">Solaris</a></dt><dd><dl><dt><a href="#id2995017">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2995794">Macintosh clients?</a></dt><dt><a href="#id2995866">OS2 Client</a></dt><dd><dl><dt><a href="#id2995873">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2995488">How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2995548">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2995645">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2995107">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2995197">Delete .pwl files after password change</a></dt><dt><a href="#id2995227">Configure WfW password handling</a></dt><dt><a href="#id2995273">Case handling of passwords</a></dt><dt><a href="#id2995303">Use TCP/IP as default protocol</a></dt><dt><a href="#id2995320">Speed improvement</a></dt></dl></dd><dt><a href="#id2995367">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2996396">Speed improvement</a></dt></dl></dd><dt><a href="#id2996420">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2996531">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2996649">Comparisons</a></dt><dt><a href="#id2996693">Socket options</a></dt><dt><a href="#id2996767">Read size</a></dt><dt><a href="#id2996811">Max xmit</a></dt><dt><a href="#id2996864">Log level</a></dt><dt><a href="#id2996886">Read raw</a></dt><dt><a href="#id2997829">Write raw</a></dt><dt><a href="#id2997871">Slow Logins</a></dt><dt><a href="#id2997892">LDAP</a></dt><dt><a href="#id2997917">Client tuning</a></dt><dt><a href="#id2997940">Samba performance problem due changing kernel</a></dt><dt><a href="#id2997973">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2998691">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2998110">Websites</a></dt><dt><a href="#id2998494">Related updates from microsoft</a></dt><dt><a href="#id2998561">Books</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 36. How to compile SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="surname">Someone; Jerry perhaps?</span></h3></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="#id2990261">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2990268">Introduction</a></dt><dt><a href="#id2990297">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2991766">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2991814">Verifying Samba's PGP signature</a></dt><dt><a href="#id2991949">Building the Binaries</a></dt><dd><dl><dt><a href="#id2992086">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2992982">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2993073">Starting from inetd.conf</a></dt><dt><a href="#id2993277">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2993372">Common Errors</a></dt></dl></div><p> +</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>36. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2994651">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2994658">Introduction</a></dt><dt><a href="#id2994688">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2996207">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2996256">Verifying Samba's PGP signature</a></dt><dt><a href="#id2996392">Building the Binaries</a></dt><dd><dl><dt><a href="#id2996529">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2996694">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2996786">Starting from inetd.conf</a></dt><dt><a href="#id2996990">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2997085">Common Errors</a></dt></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2995985">HPUX</a></dt><dt><a href="#id2998515">SCO Unix</a></dt><dt><a href="#id2998546">DNIX</a></dt><dt><a href="#id2998716">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2998760">AIX</a></dt><dd><dl><dt><a href="#id2998767">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2998793">Solaris</a></dt><dd><dl><dt><a href="#id2998800">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2998169">Macintosh clients?</a></dt><dt><a href="#id2999522">OS2 Client</a></dt><dd><dl><dt><a href="#id2999529">How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2999608">How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2999670">How do I get printer driver download working + for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2999766">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2999774">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2999864">Delete .pwl files after password change</a></dt><dt><a href="#id2999894">Configure WfW password handling</a></dt><dt><a href="#id2999940">Case handling of passwords</a></dt><dt><a href="#id2999970">Use TCP/IP as default protocol</a></dt><dt><a href="#id2999988">Speed improvement</a></dt></dl></dd><dt><a href="#id3000034">Windows '95/'98</a></dt><dd><dl><dt><a href="#id3000107">Speed improvement</a></dt></dl></dd><dt><a href="#id3000131">Windows 2000 Service Pack 2</a></dt><dt><a href="#id3000242">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id3001274">Comparisons</a></dt><dt><a href="#id3001319">Socket options</a></dt><dt><a href="#id3001394">Read size</a></dt><dt><a href="#id3001437">Max xmit</a></dt><dt><a href="#id3001490">Log level</a></dt><dt><a href="#id3001513">Read raw</a></dt><dt><a href="#id3001570">Write raw</a></dt><dt><a href="#id3001612">Slow Logins</a></dt><dt><a href="#id3001633">Client tuning</a></dt><dt><a href="#id3001658">Samba performance problem due changing kernel</a></dt><dt><a href="#id3001692">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id3001112">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id3001272">Websites</a></dt><dt><a href="#id3002922">Related updates from Microsoft</a></dt><dt><a href="#id3002990">Books</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 36. How to compile SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="surname">Someone; Jerry perhaps?</span></h3></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="#id2994651">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2994658">Introduction</a></dt><dt><a href="#id2994688">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2996207">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2996256">Verifying Samba's PGP signature</a></dt><dt><a href="#id2996392">Building the Binaries</a></dt><dd><dl><dt><a href="#id2996529">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2996694">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2996786">Starting from inetd.conf</a></dt><dt><a href="#id2996990">Alternative: starting it as a daemon</a></dt></dl></dd><dt><a href="#id2997085">Common Errors</a></dt></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="id2990261"></a>Access Samba source code via CVS</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2990268"></a>Introduction</h3></div></div><div></div></div><p> +</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994651"></a>Access Samba source code via CVS</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2994658"></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 @@ -15886,12 +15942,12 @@ detailed in this chapter. </p><p> This chapter is a modified version of the instructions found at <a href="http://samba.org/samba/cvs.html" target="_top">http://samba.org/samba/cvs.html</a> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2990297"></a>CVS Access to samba.org</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2994688"></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="id2990313"></a>Access via CVSweb</h4></div></div><div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2994705"></a>Access via CVSweb</h4></div></div><div></div></div><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 @@ -15899,7 +15955,7 @@ history and commit logs of individual files. You can also ask for a diff listing between any two versions on the repository. </p><p> Use the URL : <a href="http://samba.org/cgi-bin/cvsweb" target="_top">http://samba.org/cgi-bin/cvsweb</a> -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2990343"></a>Access via cvs</h4></div></div><div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2996017"></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 @@ -15941,7 +15997,7 @@ on this system just substitute the correct package name <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 userinput. + 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> @@ -15949,7 +16005,7 @@ on this system just substitute the correct package name the following command from within the samba directory: </p><p> <b class="userinput"><tt>cvs update -d -P</tt></b> - </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2991766"></a>Accessing the samba sources via rsync and ftp</h2></div></div><div></div></div><p> + </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2996207"></a>Accessing the samba sources via rsync and ftp</h2></div></div><div></div></div><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. @@ -15958,7 +16014,7 @@ on this system just substitute the correct package name The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2991814"></a>Verifying Samba's PGP signature</h2></div></div><div></div></div><p> + </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2996256"></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 @@ -15985,7 +16041,7 @@ 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><tt class="computeroutput"> gpg: BAD signature from "Samba Distribution Verification Key" -</tt></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2991949"></a>Building the Binaries</h2></div></div><div></div></div><p>To do this, first run the program <b class="userinput"><tt>./configure +</tt></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2996392"></a>Building the Binaries</h2></div></div><div></div></div><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><p><tt class="prompt">root# </tt><b class="userinput"><tt>./configure --help @@ -15998,10 +16054,10 @@ example of what you would not want to see would be: of Samba you might like to know that the old versions of the binaries will be renamed with a ".old" extension. You can go back to the previous version with</p><p><tt class="prompt">root# </tt><b class="userinput"><tt>make revert - </tt></b></p><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2992086"></a>Compiling samba with Active Directory support</h3></div></div><div></div></div><p>In order to compile samba with ADS support, you need to have installed + </tt></b></p><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2996529"></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 + 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 @@ -16010,13 +16066,13 @@ example of what you would not want to see would be: #define HAVE_LDAP 1 </pre><p>If it doesn't then configure did not find your krb5 libraries or your ldap libraries. Look in <tt class="filename">config.log</tt> to figure - out why and fix it.</p><div xmlns:ns99="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2992896"></a>Installing the required packages for Debian</h4></div></div><div></div></div><p>On Debian you need to install the following packages:</p><ns99:p> - </ns99:p><table class="simplelist" border="0" summary="Simple list"><tr><td>libkrb5-dev</td></tr><tr><td>krb5-user</td></tr></table><ns99:p> - </ns99:p></div><div xmlns:ns100="" class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2992929"></a>Installing the required packages for RedHat</h4></div></div><div></div></div><p>On RedHat this means you should have at least: </p><ns100:p> - </ns100:p><table class="simplelist" border="0" summary="Simple list"><tr><td>krb5-workstation (for kinit)</td></tr><tr><td>krb5-libs (for linking with)</td></tr><tr><td>krb5-devel (because you are compiling from source)</td></tr></table><ns100:p> - </ns100: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="id2992982"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><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 + out why and fix it.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2996610"></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><table class="simplelist" border="0" summary="Simple list"><tr><td>libkrb5-dev</td></tr><tr><td>krb5-user</td></tr></table><p> + </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2996642"></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><table class="simplelist" border="0" summary="Simple list"><tr><td>krb5-workstation (for kinit)</td></tr><tr><td>krb5-libs (for linking with)</td></tr><tr><td>krb5-devel (because you are compiling from source)</td></tr></table><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="id2996694"></a>Starting the <span class="application">smbd</span> and <span class="application">nmbd</span></h2></div></div><div></div></div><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 you can start them as @@ -16027,7 +16083,7 @@ example of what you would not want to see would be: Samba. In many cases you must be root.</p><p>The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method is that they will respond slightly more quickly to an initial connection - request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2993073"></a>Starting from inetd.conf</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if + request.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2996786"></a>Starting from inetd.conf</h3></div></div><div></div></div><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> @@ -16053,7 +16109,7 @@ example of what you would not want to see would be: 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. If you have installed an earlier version of <span class="application">nmbd</span> then - you may need to kill <span class="application">nmbd</span> as well.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2993277"></a>Alternative: starting it as a daemon</h3></div></div><div></div></div><p>To start the server as a daemon you should create + you may need to kill <span class="application">nmbd</span> as well.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2996990"></a>Alternative: starting it as a daemon</h3></div></div><div></div></div><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 @@ -16065,7 +16121,7 @@ example of what you would not want to see would be: </p><p>To kill it send a kill signal to the processes <span class="application">nmbd</span> and <span class="application">smbd</span>.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>If you use the SVR4 style init system then you may like to look at the <tt class="filename">examples/svr4-startup</tt> - script to make Samba fit into that system.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2993372"></a>Common Errors</h2></div></div><div></div></div><p>“<span class="quote"> + script to make Samba fit into that system.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2997085"></a>Common Errors</h2></div></div><div></div></div><p>“<span class="quote"> I'm using gcc 3 and I've compiled Samba-3 from the CVS and the binaries are very large files (40 Mb and 20 Mb). I've the same result with <tt class="option">--enable-shared</tt> ? @@ -16073,9 +16129,9 @@ binaries are very large files (40 Mb and 20 Mb). I've the same result with </p><p> The dwarf format used by GCC 3 for storing debugging symbols is very inefficient. Strip the binaries, don't compile with -g or compile with -gstabs. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter 37. Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2994651">HPUX</a></dt><dt><a href="#id2994736">SCO Unix</a></dt><dt><a href="#id2994764">DNIX</a></dt><dt><a href="#id2994934">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2994978">AIX</a></dt><dd><dl><dt><a href="#id2994984">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2995010">Solaris</a></dt><dd><dl><dt><a href="#id2995017">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></div><p>Samba works on a wide range of platforms but the interface all the +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Portability"></a>Chapter 37. Portability</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2995985">HPUX</a></dt><dt><a href="#id2998515">SCO Unix</a></dt><dt><a href="#id2998546">DNIX</a></dt><dt><a href="#id2998716">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2998760">AIX</a></dt><dd><dl><dt><a href="#id2998767">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2998793">Solaris</a></dt><dd><dl><dt><a href="#id2998800">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></div><p>Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994651"></a>HPUX</h2></div></div><div></div></div><p> +platform-specific information about compiling and using samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995985"></a>HPUX</h2></div></div><div></div></div><p> HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, <tt class="filename">/etc/group</tt> and <tt class="filename">/etc/logingroup</tt>; the system maps UIDs to numbers using the former, but @@ -16092,10 +16148,10 @@ to initgroups() be run as users not in any groups with GIDs outside the allowed range. </p><p>This is documented in the HP manual pages under setgroups(2) and passwd(4). </p><p> -On HPUX you must use gcc or the HP Ansi compiler. The free compiler -that comes with HP-UX is not Ansi compliant and cannot compile +On HPUX you must use gcc or the HP ANSI compiler. The free compiler +that comes with HP-UX is not ANSI compliant and cannot compile Samba. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994736"></a>SCO Unix</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998515"></a>SCO Unix</h2></div></div><div></div></div><p> If you run an old version of SCO Unix then you may need to get important TCP/IP patches for Samba to work correctly. Without the patch, you may encounter corrupt data transfers using samba. @@ -16103,7 +16159,7 @@ encounter corrupt data transfers using samba. The patch you need is UOD385 Connection Drivers SLS. It is available from SCO (<a href="ftp://ftp.sco.com/" target="_top">ftp.sco.com</a>, directory SLS, files uod385a.Z and uod385a.ltr.Z). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994764"></a>DNIX</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998546"></a>DNIX</h2></div></div><div></div></div><p> DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX C library for some reason. @@ -16162,13 +16218,13 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line: </p><pre class="programlisting"> #define NO_EID -</pre><p>from the DNIX section of <tt class="filename">includes.h</tt></p></div><div xmlns:ns101="" class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994934"></a>RedHat Linux Rembrandt-II</h2></div></div><div></div></div><ns101:p> +</pre><p>from the DNIX section of <tt class="filename">includes.h</tt></p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998716"></a>RedHat Linux Rembrandt-II</h2></div></div><div></div></div><p> By default RedHat Rembrandt-II during installation adds an entry to <tt class="filename">/etc/hosts</tt> as follows: -</ns101:p><pre class="programlisting"> +</p><pre class="programlisting"> 127.0.0.1 loopback "hostname"."domainname" -</pre><ns101:p> -</ns101:p><p> +</pre><p> +</p><p> This causes Samba to loop back onto the loopback interface. The result is that Samba fails to communicate correctly with the world and therefor may fail to correctly negotiate who @@ -16176,13 +16232,13 @@ is the master browse list holder and who is the master browser. </p><p> Corrective Action: Delete the entry after the word loopback in the line starting 127.0.0.1 -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2994978"></a>AIX</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2994984"></a>Sequential Read Ahead</h3></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998760"></a>AIX</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2998767"></a>Sequential Read Ahead</h3></div></div><div></div></div><p> Disabling Sequential Read Ahead using <b class="userinput"><tt>vmtune -r 0</tt></b> improves -samba performance significally. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995010"></a>Solaris</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995017"></a>Locking improvements</h3></div></div><div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl -when running samba on solaris. The built in file locking mechanism was +Samba performance significantly. +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998793"></a>Solaris</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2998800"></a>Locking improvements</h3></div></div><div></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl +when running Samba on Solaris. The built in file locking mechanism was not scalable. Performance would degrade to the point where processes would -get into loops of trying to lock a file. It woul try a lock, then fail, +get into loops of trying to lock a file. It would try a lock, then fail, then try again. The lock attempt was failing before the grant was occurring. So the visible manifestation of this would be a handful of processes stealing all of the CPU, and when they were trussed they would @@ -16200,11 +16256,11 @@ and rebuild samba. Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior is fixed by Sun in patch 113476-05 which as of March 2003 is not in any roll-up packages. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter 38. Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email"><<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</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">5 Mar 2001</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2995794">Macintosh clients?</a></dt><dt><a href="#id2995866">OS2 Client</a></dt><dd><dl><dt><a href="#id2995873">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2995488">How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2995548">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2995645">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2995107">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2995197">Delete .pwl files after password change</a></dt><dt><a href="#id2995227">Configure WfW password handling</a></dt><dt><a href="#id2995273">Case handling of passwords</a></dt><dt><a href="#id2995303">Use TCP/IP as default protocol</a></dt><dt><a href="#id2995320">Speed improvement</a></dt></dl></dd><dt><a href="#id2995367">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2996396">Speed improvement</a></dt></dl></dd><dt><a href="#id2996420">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2996531">Windows NT 3.1</a></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995794"></a>Macintosh clients?</h2></div></div><div></div></div><p> -Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> now have a CIFS Client / Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a> +</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Other-Clients"></a>Chapter 38. Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jim</span> <span class="surname">McDonough</span></h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt class="email"><<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</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">5 Mar 2001</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2998169">Macintosh clients?</a></dt><dt><a href="#id2999522">OS2 Client</a></dt><dd><dl><dt><a href="#id2999529">How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2999608">How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2999670">How do I get printer driver download working + for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2999766">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2999774">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2999864">Delete .pwl files after password change</a></dt><dt><a href="#id2999894">Configure WfW password handling</a></dt><dt><a href="#id2999940">Case handling of passwords</a></dt><dt><a href="#id2999970">Use TCP/IP as default protocol</a></dt><dt><a href="#id2999988">Speed improvement</a></dt></dl></dd><dt><a href="#id3000034">Windows '95/'98</a></dt><dd><dl><dt><a href="#id3000107">Speed improvement</a></dt></dl></dd><dt><a href="#id3000131">Windows 2000 Service Pack 2</a></dt><dt><a href="#id3000242">Windows NT 3.1</a></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998169"></a>Macintosh clients?</h2></div></div><div></div></div><p> +Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> now has a CIFS Client / Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a> </p><p> They test it against Windows 95, Windows NT and samba for compatibility issues. At the time of writing, DAVE was at version @@ -16213,17 +16269,17 @@ the Thursby web site (the speed of finder copies has been greatly enhanced, and there are bug-fixes included). </p><p> Alternatives - There are two free implementations of AppleTalk for -several kinds of UNIX machnes, and several more commercial ones. +several kinds of UNIX machines, and several more commercial ones. These products allow you to run file services and print services natively to Macintosh users, with no additional support required on -the Macintosh. The two free omplementations are +the Macintosh. The two free implementations are <a href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk</a>, and <a href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP</a>. What Samba offers MS Windows users, these packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems) see <a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html</a> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995866"></a>OS2 Client</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995873"></a>How can I configure OS/2 Warp Connect or +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2999522"></a>OS2 Client</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999529"></a>How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</h3></div></div><div></div></div><p>A more complete answer to this question can be found on <a href="http://carol.wins.uva.nl/~leeuw/samba/warp.html" target="_top"> http://carol.wins.uva.nl/~leeuw/samba/warp.html</a>.</p><p>Basically, you need three components:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>The File and Print Client ('IBM Peer')</td></tr><tr><td>TCP/IP ('Internet support') </td></tr><tr><td>The "NetBIOS over TCP/IP" driver ('TCPBEUI')</td></tr></table><p>Installing the first two together with the base operating @@ -16241,7 +16297,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see to the "Names List", or specify a WINS server ('NetBIOS Nameserver' in IBM and RFC terminology). For Warp Connect you may need to download an update for 'IBM Peer' to bring it on - the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995488"></a>How can I configure OS/2 Warp 3 (not Connect), + the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999608"></a>How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</h3></div></div><div></div></div><p>You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from <a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top"> @@ -16259,7 +16315,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see or NS2000 driver from <a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top"> ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995548"></a>How do I get printer driver download working + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999670"></a>How do I get printer driver download working for OS/2 clients?</h3></div></div><div></div></div><p>First, create a share called <i class="parameter"><tt>[PRINTDRV]</tt></i> that is world-readable. Copy your OS/2 driver files there. Note that the .EA_ files must still be separate, so you will need @@ -16276,8 +16332,8 @@ packages, Samba, and Linux (and other UNIX-based systems) see you the driver is not available. On the second attempt, it will work. This is fixed simply by adding the device name to the mapping, after which it will work on the first attempt. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995645"></a>Windows for Workgroups</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995107"></a>Use latest TCP/IP stack from Microsoft</h3></div></div><div></div></div><p>Use the latest TCP/IP stack from microsoft if you use Windows -for workgroups. + </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2999766"></a>Windows for Workgroups</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999774"></a>Use latest TCP/IP stack from Microsoft</h3></div></div><div></div></div><p>Use the latest TCP/IP stack from Microsoft if you use Windows +for Workgroups. </p><p>The early TCP/IP stacks had lots of bugs.</p><p> Microsoft has released an incremental upgrade to their TCP/IP 32-Bit VxD drivers. The latest release can be found on their ftp site at @@ -16291,7 +16347,7 @@ fixed. New files include <tt class="filename">WINSOCK.DLL</tt>, <tt class="filename">TRACERT.EXE</tt>, <tt class="filename">NETSTAT.EXE</tt>, and <tt class="filename">NBTSTAT.EXE</tt>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995197"></a>Delete .pwl files after password change</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999864"></a>Delete .pwl files after password change</h3></div></div><div></div></div><p> WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password. @@ -16300,7 +16356,7 @@ If you don't do this you may find that WfWg remembers and uses the old password, even if you told it a new one. </p><p> Often WfWg will totally ignore a password you give it in a dialog box. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995227"></a>Configure WfW password handling</h3></div></div><div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999894"></a>Configure WfW password handling</h3></div></div><div></div></div><p> There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it type <b class="userinput"><tt>EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE</tt></b>. @@ -16308,22 +16364,22 @@ Then add an icon for it via the <span class="application">Program Manager</span> <span class="guimenu">New</span> Menu. This program allows you to control how WFW handles passwords. ie disable Password Caching etc for use with <i class="parameter"><tt>security = user</tt></i> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995273"></a>Case handling of passwords</h3></div></div><div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> information on <i class="parameter"><tt>password level</tt></i> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995303"></a>Use TCP/IP as default protocol</h3></div></div><div></div></div><p>To support print queue reporting you may find +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999940"></a>Case handling of passwords</h3></div></div><div></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> information on <i class="parameter"><tt>password level</tt></i> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999970"></a>Use TCP/IP as default protocol</h3></div></div><div></div></div><p>To support print queue reporting you may find that you have to use TCP/IP as the default protocol under -WfWg. For some reason if you leave Netbeui as the default +WfWg. For some reason if you leave NetBEUI as the default it may break the print queue reporting on some systems. -It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2995320"></a>Speed improvement</h3></div></div><div></div></div><p> +It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2999988"></a>Speed improvement</h3></div></div><div></div></div><p> Note that some people have found that setting <i class="parameter"><tt>DefaultRcvWindow</tt></i> in the <i class="parameter"><tt>[MSTCP]</tt></i> section of the <tt class="filename">SYSTEM.INI</tt> file under WfWg to 3072 gives a big improvement. I don't know why. </p><p> -My own experience wth DefaultRcvWindow is that I get much better +My own experience with DefaultRcvWindow is that I get much better performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One +reported that anything over 3072 slows things down enormously. One person even reported a speed drop of a factor of 30 when he went from 3072 to 8192. I don't know why. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2995367"></a>Windows '95/'98</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3000034"></a>Windows '95/'98</h2></div></div><div></div></div><p> When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these updates have been installed. @@ -16332,16 +16388,16 @@ There are more updates than the ones mentioned here. You are referred to the Microsoft Web site for all currently available updates to your specific version of Windows 95. </p><table class="simplelist" border="0" summary="Simple list"><tr><td>Kernel Update: KRNLUPD.EXE</td></tr><tr><td>Ping Fix: PINGUPD.EXE</td></tr><tr><td>RPC Update: RPCRTUPD.EXE</td></tr><tr><td>TCP/IP Update: VIPUPD.EXE</td></tr><tr><td>Redirector Update: VRDRUPD.EXE</td></tr></table><p> -Also, if using <span class="application">MS OutLook</span> it is desirable to +Also, if using <span class="application">MS Outlook</span> it is desirable to install the <b class="command">OLEUPD.EXE</b> fix. This fix may stop your machine from hanging for an extended period when exiting -OutLook and you may also notice a significant speedup when accessing network +Outlook and you may also notice a significant speedup when accessing network neighborhood services. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2996396"></a>Speed improvement</h3></div></div><div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3000107"></a>Speed improvement</h3></div></div><div></div></div><p> Configure the win95 TCPIP registry settings to give better performance. I use a program called <b class="command">MTUSPEED.exe</b> which I got off the net. There are various other utilities of this type freely available. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2996420"></a>Windows 2000 Service Pack 2</h2></div></div><div></div></div><p> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3000131"></a>Windows 2000 Service Pack 2</h2></div></div><div></div></div><p> There are several annoyances with Windows 2000 SP2. One of which only appears when using a Samba server to host user profiles to Windows 2000 SP2 clients in a Windows domain. This assumes @@ -16382,10 +16438,10 @@ the Win2k client a response to the QuerySecurityDescriptor trans2 call which causes the client to set a default ACL for the profile. This default ACL includes </p><p><span class="emphasis"><em>DOMAIN\user "Full Control"</em></span>></p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2996531"></a>Windows NT 3.1</h2></div></div><div></div></div><p>If you have problems communicating across routers with Windows +create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3000242"></a>Windows NT 3.1</h2></div></div><div></div></div><p>If you have problems communicating across routers with Windows NT 3.1 workstations, read <a href="http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;Q103765" target="_top">this Microsoft Knowledge Base article</a>. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter 39. Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt class="email"><<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="#id2996649">Comparisons</a></dt><dt><a href="#id2996693">Socket options</a></dt><dt><a href="#id2996767">Read size</a></dt><dt><a href="#id2996811">Max xmit</a></dt><dt><a href="#id2996864">Log level</a></dt><dt><a href="#id2996886">Read raw</a></dt><dt><a href="#id2997829">Write raw</a></dt><dt><a href="#id2997871">Slow Logins</a></dt><dt><a href="#id2997892">LDAP</a></dt><dt><a href="#id2997917">Client tuning</a></dt><dt><a href="#id2997940">Samba performance problem due changing kernel</a></dt><dt><a href="#id2997973">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="id2996649"></a>Comparisons</h2></div></div><div></div></div><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="speed"></a>Chapter 39. Samba Performance Tuning</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Paul</span> <span class="surname">Cochrane</span></h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt class="email"><<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="#id3001274">Comparisons</a></dt><dt><a href="#id3001319">Socket options</a></dt><dt><a href="#id3001394">Read size</a></dt><dt><a href="#id3001437">Max xmit</a></dt><dt><a href="#id3001490">Log level</a></dt><dt><a href="#id3001513">Read raw</a></dt><dt><a href="#id3001570">Write raw</a></dt><dt><a href="#id3001612">Slow Logins</a></dt><dt><a href="#id3001633">Client tuning</a></dt><dt><a href="#id3001658">Samba performance problem due changing kernel</a></dt><dt><a href="#id3001692">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="id3001274"></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 @@ -16395,7 +16451,7 @@ SMB server. If you want to test against something like a NT or WfWg server then you will have to disable all but TCP on either the client or server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid. +(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, @@ -16407,7 +16463,7 @@ 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="id2996693"></a>Socket options</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001319"></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> @@ -16426,7 +16482,7 @@ biggest single difference for most networks. Many people report that adding <i class="parameter"><tt>socket options = TCP_NODELAY</tt></i> 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="id2996767"></a>Read size</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="id3001394"></a>Read size</h2></div></div><div></div></div><p> The option <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 @@ -16443,7 +16499,7 @@ 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="id2996811"></a>Max xmit</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001437"></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 <i class="parameter"><tt>max xmit = </tt></i> option @@ -16457,12 +16513,12 @@ 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="id2996864"></a>Log level</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="id3001490"></a>Log level</h2></div></div><div></div></div><p> If you set the log level (also known as <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="id2996886"></a>Read raw</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="id3001513"></a>Read raw</h2></div></div><div></div></div><p> The <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 <i class="parameter"><tt>read raw</tt></i> optional, with it @@ -16475,7 +16531,7 @@ read operations. So you might like to try <i class="parameter"><tt>read raw = no</tt></i> 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="id2997829"></a>Write raw</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="id3001570"></a>Write raw</h2></div></div><div></div></div><p> The <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 <i class="parameter"><tt>write raw</tt></i> optional, with it @@ -16483,54 +16539,51 @@ being enabled by default. </p><p> Some machines may find <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="id2997871"></a>Slow Logins</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001612"></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 <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="id2997892"></a>LDAP</h2></div></div><div></div></div><p> -LDAP can be vastly improved by using the -<a href="smb.conf.5.html#LDAPTRUSTIDS" target="_top"><i class="parameter"><tt>ldap trust ids</tt></i></a> parameter. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2997917"></a>Client tuning</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="id3001633"></a>Client tuning</h2></div></div><div></div></div><p> Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP performance. Check the sections on the various clients in <a href="#Other-Clients" title="Chapter 38. Samba and other CIFS clients">Samba and Other Clients</a>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2997940"></a>Samba performance problem due changing kernel</h2></div></div><div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001658"></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 ried +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 trerribly slow. +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="id2997973"></a>Corrupt tdb Files</h2></div></div><div></div></div><p> -Well today it happend, our first major problem using samba. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001692"></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 alot of searching I -decided to <b class="command">rm /var/locks/*.tbl</b>. Happy again. +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 *.tbl files in top condition or +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 stoping nmbd and before starting nmbd. +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 -alot lower then before the locks cleanup, any ideas on keeping it top notch? +a lot lower then before the locks cleanup, any ideas on keeping it top notch? </p><p> -A2) Yes! Samba answer as for Q1! -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter 40. DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id2998691">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998691"></a>Note</h2></div></div><div></div></div><p> +A2) Yes! Same answer as for Q1! +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="DNSDHCP"></a>Chapter 40. DNS and DHCP Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<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="#id3001112">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001112"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Further-Resources"></a>Chapter 41. Further Resources</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email"><<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>></tt></p></div></div></div></div><div><p class="pubdate">May 1, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2998110">Websites</a></dt><dt><a href="#id2998494">Related updates from microsoft</a></dt><dt><a href="#id2998561">Books</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998110"></a>Websites</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> +</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="Further-Resources"></a>Chapter 41. Further Resources</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<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">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email"><<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>></tt></p></div></div></div></div><div><p class="pubdate">May 1, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id3001272">Websites</a></dt><dt><a href="#id3002922">Related updates from Microsoft</a></dt><dt><a href="#id3002990">Books</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3001272"></a>Websites</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> <a href="http://hr.uoregon.edu/davidrl/cifs.txt" target="_top"> <span class="emphasis"><em>CIFS: Common Insecurities Fail Scrutiny</em></span> by "Hobbit"</a> </p></li><li><p> @@ -16617,7 +16670,7 @@ It is planned for the published release of this document. <span class="emphasis"><em>WFWG: Password Caching and How It Affects LAN Manager Security</em></span> at Microsoft Knowledge Base </a> - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998494"></a>Related updates from microsoft</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3002922"></a>Related updates from Microsoft</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> <a href="http://support.microsoft.com/support/kb/articles/q92/5/88.asp" target="_top"> <span class="emphasis"><em>Enhanced Encryption for Windows 95 Password Cache</em></span> </a> @@ -16629,4 +16682,4 @@ It is planned for the published release of this document. <a href="http://support.microsoft.com/support/kb/articles/q136/4/18.asp" target="_top"> <span class="emphasis"><em>Windows for Workgroups Sharing Updates</em></span> </a> - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2998561"></a>Books</h2></div></div><div></div></div></div></div></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id2998572"></a>Index</h2></div></div><div></div></div><div class="index"></div></div></div></body></html> + </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3002990"></a>Books</h2></div></div><div></div></div></div></div></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="id3001039"></a>Index</h2></div></div><div></div></div><div class="index"></div></div></div></body></html> |