diff options
Diffstat (limited to 'docs/htmldocs/Samba-HOWTO-Collection.html')
| -rw-r--r-- | docs/htmldocs/Samba-HOWTO-Collection.html | 9515 |
1 files changed, 0 insertions, 9515 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html deleted file mode 100644 index 8334ef82f3..0000000000 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ /dev/null @@ -1,9515 +0,0 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>SAMBA Project Documentation</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><meta name="description" content=" -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. -The most recent version of this document can be found at -http://www.samba.org/ -on the "Documentation" page. Please send updates to -Jelmer Venrooij, -John Terpstra or -Gerald (Jerry) Carter. - -The Samba-Team would like to express sincere thanks to the many people who have with -or without their knowledge contributed to this update. The size and scope of this -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 -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><h1 class="title"><a name="Samba-HOWTO-Collection"></a>SAMBA Project Documentation</h1></div><div><div class="author"><h3 class="author">SAMBA Team</h3><div class="affiliation"><div class="address"><p><tt><<a href="mailto:samba@samba.org">samba@samba.org</a>></tt></p></div></div></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></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. -The most recent version of this document can be found at -<a href="http://www.samba.org/" target="_top">http://www.samba.org/</a> -on the "Documentation" page. Please send updates to -<a href="mailto:jelmer@samba.org" target="_top">Jelmer Venrooij</a>, -<a href="mailto:jht@samba.org" target="_top">John Terpstra</a> or -<a href="mailto:jerry@samba.org" target="_top">Gerald (Jerry) Carter</a>. -</p><p> -The Samba-Team would like to express sincere thanks to the many people who have with -or without their knowledge contributed to this update. The size and scope of this -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 -application knowledge that is most to be desired by many Samba users and administrators. -</p></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="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your - server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>3. <a href="#ServerType">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="#securitylevels">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc"> -Samba as an NT4 or Win2k Primary Domain Controller -</a></dt><dd><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607"> -Background -</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">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="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc"> -Samba Backup Domain Controller to Samba Domain Control -</a></dt><dd><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#ADS">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><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="#id2862919">Notes</a></dt></dl></dd><dt>8. <a href="#domain-member">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>9. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</a></dt></dl></dd></dl></dd><dt>10. <a href="#passdb">User information database</a></dt><dd><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></dd><dt>11. <a href="#unix-permissions">UNIX Permission Bits and Windows NT Access Control Lists</a></dt><dd><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT - security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute - mapping</a></dt></dl></dd><dt>12. <a href="#groupmapping">Configuring Group Mapping</a></dt><dt>13. <a href="#printing">Printing Support</a></dt><dd><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></dd><dt>14. <a href="#CUPS-printing">CUPS Printing Support</a></dt><dd><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></dd><dt>15. <a href="#winbind">Unified Logons between Windows NT and UNIX using Winbind</a></dt><dd><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></dd><dt>16. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></dd><dt>17. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></dd><dt>18. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></dd><dt>19. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></dd><dt>20. <a href="#pam">PAM Configuration for Centrally Managed Authentication</a></dt><dd><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></dd><dt>21. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></dd><dt>22. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></dd><dt>23. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</a></dt></dl></dd></dl></dd><dt>24. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></dd><dt>25. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></dd><dt>26. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></dd></dl></dd><dt>IV. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>27. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></dd><dt>28. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</a></dt></dl></dd><dt>29. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></dd></dl></dd><dt>V. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>30. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>33. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">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="#id2891126">Are there any other issues when OS/2 (any version) - is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">Windows NT 3.1</a></dt></dl></dd><dt>34. <a href="#SWAT">SWAT - The Samba Web Admininistration Tool</a></dt><dd><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">The Password Change Page</a></dt></dl></dd></dl></dd><dt>35. <a href="#speed">Samba performance issues</a></dt><dd><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>21.1. <a href="#id2882333">Extended Auditing Log Information</a></dt><dt>31.1. <a href="#id2889997">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2890135">Nature of the Conversion Choices</a></dt></dl></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2789774"></a>Preparing Samba for Configuration</h1></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="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your - server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="IntroSMB"></a>Chapter 1. Introduction to Samba</h2></div><div><div class="author"><h3 class="author">David Lechnyr</h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></div><p><span class="emphasis"><em> -"If you understand what you're doing, you're not learning anything." --- Anonymous -</em></span></p><p> -Samba is a file and print server for Windows-based clients using TCP/IP as the underlying -transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big -strengths is that you can use it to blend your mix of Windows and Linux machines together -without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed -by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2794048"></a>Background</h2></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 -ran over UDP. When there was a need to run it over TCP so that it would be compatible -with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became -known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to -license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the -concept continued in the form of SMB (Server Message Block, or the "what") using the -NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can -run SMB (i.e., transport) over several different protocols; many different implementations -arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT -(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form -of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing -term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 -only. As of yet, direct-hosted TCP has yet to catch on. -</p><p> -Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS: -Common Insecurities Fail Scrutiny: -</p><p><span class="emphasis"><em> -Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba -stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have -been dutifully waded through during the information-gathering stages of this project, and there -are *still* many missing pieces... While often tedious, at least the way has been generously -littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they -thinking? -</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2794106"></a>Terminology</h2></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 - decided that SMB needed the word "Internet" in it, so they changed it to CIFS. - </p></li><li><p> - Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp - only using DNS for name resolution instead of WINS. - </p></li><li><p> - IPC: Acronym for "Inter-Process Communication". A method to communicate specific - information between programs. - </p></li><li><p> - Marshalling: - A method of serializing (i.e., sequential ordering of) variable data - suitable for transmission via a network connection or storing in a file. The source - data can be re-created using a similar process called unmarshalling. - </p></li><li><p> - NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; - it is a method of communication across an existing protocol. This is a standard which - was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, - it can help to think of this in comparison your computer's BIOS -- it controls the - essential functions of your input/output hardware -- whereas NetBIOS controls the - essential functions of your input/output traffic via the network. Again, this is a bit - of an exaggeration but it should help that paradigm shift. What is important to realize - is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically - brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second - thought; this will cause no end (and no doubt) of confusion. - </p></li><li><p> - NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI - is a protocol, not a standard. It is also not routable, so traffic on one side of a - router will be unable to communicate with the other side. Understanding NetBEUI is - not essential to deciphering SMB; however it helps to point out that it is not the - same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally - referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". - It is not often heard from these days. - </p></li><li><p> - NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use - of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made - to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. - This is how file and printer sharing are accomplished in Windows 95/98/ME. They - traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137, - NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service - (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, - and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 - (Detailed specifications). - </p></li><li><p> - W2K: Acronym for Windows 2000 Professional or Server - </p></li><li><p> - 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 -http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2795149"></a>Related Projects</h2></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> - SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol - that Microsoft Windows and OS/2 Lan Manager use to share files and printers - over local networks) and access them just like any other Unix directory. This is useful - if you just want to mount such filesystems without being a SMBFS server. - </p></li><li><p> - 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 - name space), secure per-user session establishment, safe distributed caching (oplock), - optional packet signing, Unicode and other internationalization improvements, and optional - Winbind (nsswitch) integration. - </p></li></ul></div><p> -Again, it's important to note that these are implementations for client filesystems, and have -nothing to do with acting as a file and print server for SMB/CIFS clients. -</p><p> -There are other Open Source CIFS client implementations, such as the jCIFS project -(jcifs.samba.org) which provides an SMB client toolkit written in Java. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845311"></a>SMB Methodology</h2></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 -packet sniffer will be amazed at the amount of traffic generated by just opening -up a single file. In general, SMB sessions are established in the following order: -</p><div class="itemizedlist"><ul type="disc"><li><p> - "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp - or 445/tcp. - </p></li><li><p> - "NetBIOS Session Request" - using the following "Calling Names": The local - machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS - name plus the 16th character 0x20 - </p></li><li><p> - "SMB Negotiate Protocol" - determine the protocol dialect to use, which will - be one of the following: PC Network Program 1.0 (Core) - share level security - mode only; Microsoft Networks 1.03 (Core Plus) - share level security - mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response - Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response - Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response - Authentication - </p></li><li><p> - SMB Session Startup. Passwords are encrypted (or not) according to one of - the following methods: Null (no encryption); Cleartext (no encryption); LM - and NTLM; NTLM; NTLMv2 - </p></li><li><p> - SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect - to a service type (e.g., IPC$ named pipe) - </p></li></ul></div><p> -A good way to examine this process in depth is to try out SecurityFriday's SWB program -at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to -walk through the establishment of a SMB/CIFS session step by step. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790901"></a>Additional Resources</h2></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> - <a href="http://afr.com/it/2002/10/01/FFXDF43AP6D.html" target="_top"> - <span class="emphasis"><em>Doing the Samba on Windows</em></span> by Financial Review - </a> - </p></li><li><p> - <a href="http://ubiqx.org/cifs/" target="_top"> - <span class="emphasis"><em>Implementing CIFS</em></span> by Christopher R. Hertel - </a> - </p></li><li><p> - <a href="http://samba.anu.edu.au/cifs/docs/what-is-smb.html" target="_top"> - <span class="emphasis"><em>Just What Is SMB?</em></span> by Richard Sharpe - </a> - </p></li><li><p> - <a href="http://www.linux-mag.com/1999-05/samba_01.html" target="_top"> - <span class="emphasis"><em>Opening Windows Everywhere</em></span> by Mike Warfield - </a> - </p></li><li><p> - <a href="http://www.tldp.org/HOWTO/SMB-HOWTO.html" target="_top"> - <span class="emphasis"><em>SMB HOWTO</em></span> by David Wood - </a> - </p></li><li><p> - <a href="http://www.phrack.org/phrack/60/p60-0x0b.txt" target="_top"> - <span class="emphasis"><em>SMB/CIFS by The Root</em></span> by "ledin" - </a> - </p></li><li><p> - <a href="http://www.linux-mag.com/1999-09/samba_01.html" target="_top"> - <span class="emphasis"><em>The Story of Samba</em></span> by Christopher R. Hertel - </a> - </p></li><li><p> - <a href="http://hr.uoregon.edu/davidrl/samba/" target="_top"> - <span class="emphasis"><em>The Unofficial Samba HOWTO</em></span> by David Lechnyr - </a> - </p></li><li><p> - <a href="http://www.linux-mag.com/2001-05/smb_01.html" target="_top"> - <span class="emphasis"><em>Understanding the Network Neighborhood</em></span> by Christopher R. Hertel - </a> - </p></li><li><p> - <a href="http://www.linux-mag.com/2002-02/samba_01.html" target="_top"> - <span class="emphasis"><em>Using Samba as a PDC</em></span> by Andrew Bartlett - </a> - </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2793926"></a>Epilogue</h2></div></div><p><span class="emphasis"><em> -"What's fundamentally wrong is that nobody ever had any taste when they -did it. Microsoft has been very much into making the user interface look good, -but internally it's just a complete mess. And even people who program for Microsoft -and who have had years of experience, just don't know how it works internally. -Worse, nobody dares change it. Nobody dares to fix bugs because it's such a -mess that fixing one bug might just break a hundred programs that depend on -that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested -in making money. They don't have anybody who takes pride in Windows 95 as an -operating system. -</em></span></p><p><span class="emphasis"><em> -People inside Microsoft know it's a bad operating system and they still -continue obviously working on it because they want to get the next version out -because they want to have all these new features to sell more copies of the -system. -</em></span></p><p><span class="emphasis"><em> -The problem with that is that over time, when you have this kind of approach, -and because nobody understands it, because nobody REALLY fixes bugs (other than -when they're really obvious), the end result is really messy. You can't trust -it because under certain circumstances it just spontaneously reboots or just -halts in the middle of something that shouldn't be strange. Normally it works -fine and then once in a blue moon for some completely unknown reason, it's dead, -and nobody knows why. Not Microsoft, not the experienced user and certainly -not the completely clueless user who probably sits there shivering thinking -"What did I do wrong?" when they didn't do anything wrong at all. -</em></span></p><p><span class="emphasis"><em> -That's what's really irritating to me." -</em></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><h2 class="title" style="clear: both"><a name="id2844986"></a>Miscellaneous</h2></div></div><p> -This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0, -in case anyone asks. -</p><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><h2 class="title"><a name="install"></a>Chapter 2. How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Karl Auer</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your - server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2844847"></a>Obtaining and installing samba</h2></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>. - </p><p>If you need to compile samba from source, check the - <a href="#compiling" title="Chapter 30. How to compile SAMBA">appropriate appendix chapter</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845201"></a>Configuring samba</h2></div></div><p>Samba's configuration is stored in the smb.conf file, - that usually resides in <tt>/etc/samba/smb.conf</tt> - or <tt>/usr/local/samba/lib/smb.conf</tt>. You can either - edit this file yourself or do it using one of the many graphical - tools that are available, such as the web-based interface swat, that - is included with samba.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2844744"></a>Editing the <tt>smb.conf</tt> file</h3></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><pre class="programlisting"> -[global] - workgroup = MYGROUP - -[homes] - guest ok = no - read only = no - </pre><p>which would allow connections by anyone with an - account on the server, using either their login name or - "<b>homes</b>" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)</p><p>Make sure you put the <tt>smb.conf</tt> file in the same place - you specified in the<tt>Makefile</tt> (the default is to - look for it in <tt>/usr/local/samba/lib/</tt>).</p><p>For more information about security settings for the - <b>[homes]</b> share please refer to the chapter - <a href="#securing-samba" title="Chapter 24. Securing Samba">Securing Samba</a>.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2858862"></a>Test your config file with - <b>testparm</b></h4></div></div><p>It's important that you test the validity of your - <tt>smb.conf</tt> file using the testparm program. - If testparm runs OK then it will list the loaded services. If - not it will give an error message.</p><p>Make sure it runs OK and that the services look - reasonable before proceeding. </p><p>Always run testparm again when you change - <tt>smb.conf</tt>!</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858916"></a>SWAT</h3></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 - on compiling, installing and configuring swat from source. - </p><p>To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace <i><tt>localhost</tt></i> with the name of the computer you are running samba on if you - are running samba on a different computer than your browser.</p><p>Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858954"></a>Try listing the shares available on your - server</h2></div></div><p><tt>$ </tt><b><tt>smbclient -L - <i><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. - Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).</p><p>If you choose user level security then you may find - that Samba requests a password before it will list the shares. - See the <b>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><h2 class="title" style="clear: both"><a name="id2859005"></a>Try connecting with the unix client</h2></div></div><p><tt>$ </tt><b><tt>smbclient <i><tt> - //yourhostname/aservice</tt></i></tt></b></p><p>Typically the <i><tt>yourhostname</tt></i> - would be the name of the host where you installed smbd. - The <i><tt>aservice</tt></i> is - any service you have defined in the <tt>smb.conf</tt> - file. Try your user name if you just have a <b>[homes]</b> - section - in <tt>smb.conf</tt>.</p><p>For example if your unix host is <i><tt>bambi</tt></i> - and your login name is <i><tt>fred</tt></i> you would type:</p><p><tt>$ </tt><b><tt>smbclient //<i><tt>bambi</tt></i>/<i><tt>fred</tt></i> - </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859108"></a>Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client</h2></div></div><p>Try mounting disks. eg:</p><p><tt>C:\WINDOWS\> </tt><b><tt>net use d: \\servername\service - </tt></b></p><p>Try printing. eg:</p><p><tt>C:\WINDOWS\> </tt><b><tt>net use lpt1: - \\servername\spoolservice</tt></b></p><p><tt>C:\WINDOWS\> </tt><b><tt>print filename - </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859169"></a>What If Things Don't Work?</h2></div></div><p>Then you might read the file chapter - <a href="#diagnosis" title="Chapter 27. The samba checklist">Diagnosis</a> and the - FAQ. If you are still stuck then try to follow - the <a href="#problems" title="Chapter 28. 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></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2845027"></a>First Steps in Server Configuration</h1></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>3. <a href="#ServerType">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="#securitylevels">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc"> -Samba as an NT4 or Win2k Primary Domain Controller -</a></dt><dd><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607"> -Background -</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">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="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc"> -Samba Backup Domain Controller to Samba Domain Control -</a></dt><dd><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#ADS">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><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="#id2862919">Notes</a></dt></dl></dd><dt>8. <a href="#domain-member">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ServerType"></a>Chapter 3. Nomenclature of Server Types</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></div><p>Adminstrators of Microsoft networks often refer to there being three -different type of servers:</p><div class="itemizedlist"><ul type="disc"><li><p>Stand Alone Server</p></li><li><p>Domain Member Server</p></li><li><p>Domain Controller</p><div class="itemizedlist"><ul type="circle"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div></li></ul></div><p>A network administrator who is familiar with these terms and who -wishes to migrate to or use Samba will want to know what these terms mean -within a Samba context.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845139"></a>Stand Alone Server</h2></div></div><p> -The term <span class="emphasis"><em>stand alone server</em></span> means that the server -will provide local authentication and access control for all resources -that are available from it. In general this means that there will be a -local user database. In more technical terms, it means that resources -on the machine will either be made available in either SHARE mode or in -USER mode. SHARE mode and USER mode security are documented under -discussions regarding "security mode". The smb.conf configuration parameters -that control security mode are: "security = user" and "security = share". -</p><p> -No special action is needed other than to create user accounts. Stand-alone -servers do NOT provide network logon services, meaning that machines that -use this server do NOT perform a domain logon but instead make use only of -the MS Windows logon which is local to the MS Windows workstation/server. -</p><p> -Samba tends to blur the distinction a little in respect of what is -a stand alone server. This is because the authentication database may be -local or on a remote server, even if from the samba protocol perspective -the samba server is NOT a member of a domain security context. -</p><p> -Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) 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 (/etc/passwd or /etc/shadow), may use a local smbpasswd -file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), 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><h2 class="title" style="clear: both"><a name="id2859402"></a>Domain Member Server</h2></div></div><p> -This mode of server operation involves the samba machine being made a member -of a domain security context. This means by definition that all user authentication -will be done from a centrally defined authentication regime. The authentication -regime may come from an NT3/4 style (old domain technology) server, or it may be -provided from an Active Directory server (ADS) running on MS Windows 2000 or later. -</p><p><span class="emphasis"><em> -Of course it should be clear that the authentication back end itself could be from any -distributed directory architecture server that is supported by Samba. This can be -LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc. -</em></span></p><p> -Please refer to the section on Howto configure Samba as a Primary Domain Controller -and for more information regarding how to create a domain machine account for a -domain member server as well as for information regarding how to enable the samba -domain member machine to join the domain and to be fully trusted by it. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859442"></a>Domain Controller</h2></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 what Domain Control -is the following types of controller are known: -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859458"></a>Domain Controller Types</h3></div></div><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><p> -The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in the MS -Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many -expect. The PDC seeds the Domain Control database (a part of the Windows registry) and -it plays a key part in synchronisation of the domain authentication database. -</p><p> -New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as -the NT4 style SAM (Security Account Manager) database (one of the registry files). -The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and -valid options include <span class="emphasis"><em> smbpasswd tdbsam ldapsam nisplussam plugin unixsam</em></span>. -The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix -Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux -system accounts, provided a uid range is defined from which SAM accounts can be created. -</p><p> -The <span class="emphasis"><em>Backup Domain Controller</em></span> or BDC plays a key role in servicing network -authentication requests. The BDC is biased to answer logon requests so that on a network segment -that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will -answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to -a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is -automatically demoted to a BDC. -</p><p> -At this time Samba is NOT capable of acting as an <span class="emphasis"><em>ADS Domain Controller</em></span>. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securitylevels"></a>Chapter 4. Samba as Stand-Alone Server</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></div><p> -In this section the function and purpose of Samba's <span class="emphasis"><em>security</em></span> -modes are described. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859216"></a>User and Share security level</h2></div></div><p> -A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859238"></a>User Level Security</h3></div></div><p> -I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after -the protocol negotiation. This contains a username and password. The -server can either accept or reject that username/password -combination. Note that at this stage the server has no idea what -share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than: -</p><div class="orderedlist"><ol type="1"><li><p>the username/password</p></li><li><p>the machine that the client is coming from</p></li></ol></div><p> -If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without -specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup". -</p><p> -It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use -as an authentication tag for that username/password. The client can -maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this) -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859720"></a>Share Level Security</h3></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 "tree connection" (share mount). It does not -explicitly send a username with this operation. The client is -expecting a password to be associated with each share, independent of -the user. This means that samba has to work out what username the -client probably wants to use. It is never explicitly sent the -username. Some commercial SMB servers such as NT actually associate -passwords directly with shares in share level security, but samba -always uses the unix authentication scheme where it is a -username/password that is authenticated, not a "share/password". -</p><p> -Many clients send a "session setup" even if the server is in share -level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds -to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the <b>user =</b> <tt>smb.conf</tt> -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859774"></a>Server Level Security</h3></div></div><p> -Finally "server level" security. In server level security the samba -server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba -server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same -username/password that it got from the client. If that server is in -user level security and accepts the password then samba accepts the -clients connection. This allows the samba server to use another SMB -server as the "password server". -</p><p> -You should also note that at the very start of all this, where the -server tells the client what security level it is in, it also tells -the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all -passwords in encrypted form. You have to compile samba with encryption -enabled to support this feature, and you have to maintain a separate -smbpasswd file with SMB style encrypted passwords. It is -cryptographically impossible to translate from unix style encryption -to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync. -</p><p> -"security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -<span class="emphasis"><em>Server</em></span> level security is incompatible with what is known -as <span class="emphasis"><em>schannel</em></span> or "sign and seal" protocols. This means that -if you want to use <span class="emphasis"><em>server</em></span> level security you must disable -the use of "sign and seal" on all machines on your network. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2859859"></a>Configuring Samba for Seemless Windows Network Integration</h4></div></div><p> -MS Windows clients may use encrypted passwords as part of a challenege/response -authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple -password based authentication. It should be realized that with the SMB protocol -the password is passed over the network either in plain text or encrypted, but -not both in the same authentication request. -</p><p> -When encrypted passwords are used a password that has been entered by the user -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 - 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 for the LanMan hash. - </p></li></ul></div><p> -MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 -pre-service pack 3 will use either mode of password authentication. All -versions of MS Windows that follow these versions no longer support plain -text passwords by default. -</p><p> -MS Windows clients have a habit of dropping network mappings that have been idle -for 10 minutes or longer. When the user attempts to use the mapped drive -connection that has been dropped, the client re-establishes the connection using -a cached copy of the password. -</p><p> -When Microsoft changed the default password mode, support was dropped for caching -of the plain text password. This means that when the registry parameter is changed -to re-enable use of plain text passwords it appears to work, but when a dropped -service connection mapping attempts to revalidate it will fail if the remote -authentication server does not support encrypted passwords. This means that it -is definitely not a good idea to re-enable plain text password support in such clients. -</p><p> -The following parameters can be used to work around the issue of Windows 9x client -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><tt>integer</tt></i> - <a href="smb.conf.5.html#USERNAMELEVEL" target="_top">username level</a> = <i><tt>integer</tt></i> -</pre><p> -By default Samba will lower case the username before attempting to lookup the user -in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the <i><tt>username level</tt></i> parameter -is rarely needed. -</p><p> -However, passwords on UNIX systems often make use of mixed case characters. -This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the <i><tt>password level</tt></i> -must be set to the maximum number of upper case letter which <span class="emphasis"><em>could</em></span> -appear is a password. Note that the server OS uses the traditional DES version -of crypt(), a <i><tt>password level</tt></i> of 8 will result in case -insensitive passwords as seen from Windows users. This will also result in longer -login times as Samba has to compute the permutations of the password string and -try them one by one until a match is located (or all combinations fail). -</p><p> -The best option to adopt is to enable support for encrypted passwords -where ever Samba is used. There are three configuration possibilities -for support of encrypted passwords: -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860034"></a>Use MS Windows NT as an authentication server</h4></div></div><p> -This method involves the additions of the following parameters in the <tt>smb.conf</tt> file: -</p><pre class="programlisting"> - encrypt passwords = Yes - security = server - password server = "NetBIOS_name_of_PDC" -</pre><p> -There are two ways of identifying whether or not a username and -password pair was valid or not. One uses the reply information provided -as part of the authentication messaging process, the other uses -just an error code. -</p><p> -The down-side of this mode of configuration is the fact that -for security reasons Samba will send the password server a bogus -username and a bogus password and if the remote server fails to -reject the username and password pair then an alternative mode -of identification of validation is used. Where a site uses password -lock out after a certain number of failed authentication attempts -this will result in user lockouts. -</p><p> -Use of this mode of authentication does require there to be -a standard Unix account for the user, this account can be blocked -to prevent logons by other than MS Windows clients. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860095"></a>Domain Level Security</h3></div></div><p> -When samba is operating in <span class="emphasis"><em>security = domain</em></span> mode this means that -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><h4 class="title"><a name="id2860115"></a>Samba as a member of an MS Windows NT security domain</h4></div></div><p> -This method involves addition of the following parameters in the <tt>smb.conf</tt> file: -</p><pre class="programlisting"> - encrypt passwords = Yes - security = domain - workgroup = "name of NT domain" - password server = * -</pre><p> -The use of the "*" argument to <b>password server</b> will cause samba to locate the -domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour. -</p><p> -In order for this method to work the Samba server needs to join the -MS Windows NT security domain. This is done as follows: -</p><div class="itemizedlist"><ul type="disc"><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 Linux system execute: - <b>smbpasswd -r PDC_NAME -j DOMAIN_NAME</b> (samba 2.x) - - <b>net join -U administrator%password</b> (samba-3) - </p></li></ul></div><p> -Use of this mode of authentication does require there to be a standard Unix account -for the 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 -MS Windows through things such as setting an invalid shell in the -<tt>/etc/passwd</tt> entry. -</p><p> -An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the <a href="#winbind" title="Chapter 15. Unified Logons between Windows NT and UNIX using Winbind">Winbind Overview</a> chapter -in this HOWTO collection. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860234"></a>ADS Level Security</h3></div></div><p> -For information about the configuration option please refer to the entire section entitled -<span class="emphasis"><em>Samba as an ADS Domain Member.</em></span> -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-pdc"></a>Chapter 5. -Samba as an NT4 or Win2k Primary Domain Controller -</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607"> -Background -</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">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="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not -exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859583"></a>Prerequisite Reading</h2></div></div><p> -Before you continue reading in this chapter, please make sure -that you are comfortable with configuring basic files services -in smb.conf and how to enable and administer password -encryption in Samba. Theses two topics are covered in the -<tt>smb.conf</tt> manpage. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859607"></a> -Background -</h2></div></div><p> -This article outlines the steps necessary for configuring Samba as a PDC. -It is necessary to have a working Samba server prior to implementing the -PDC functionality. -</p><div class="itemizedlist"><ul type="disc"><li><p> - Domain logons for Windows NT 4.0 / 200x / XP Professional clients. - </p></li><li><p> - Placing Windows 9x / Me clients in user level security - </p></li><li><p> - Retrieving a list of users and groups from a Samba PDC to - Windows 9x / Me / NT / 200x / XP Professional clients - </p></li><li><p> - Roaming Profiles - </p></li><li><p> - Network/System Policies - </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Roaming Profiles and System/Network policies are advanced network administration topics -that are covered separately in this document. -</p></div><p> -The following functionalities are new to the Samba 3.0 release: -</p><div class="itemizedlist"><ul type="disc"><li><p> - Windows NT 4 domain trusts - </p></li><li><p> - Adding users via the User Manager for Domains - </p></li></ul></div><p> -The following functionalities are NOT provided by Samba 3.0: -</p><div class="itemizedlist"><ul type="disc"><li><p> - SAM replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) - </p></li><li><p> - Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) - </p></li></ul></div><p> -Please note that Windows 9x / Me / XP Home clients are not true members of a domain -for reasons outlined in this article. Therefore the protocol for -support of Windows 9x-style domain logons is completely different -from NT4 / Win2k type domain logons and has been officially supported for some -time. -</p><p><span class="emphasis"><em> -MS Windows XP Home edition is NOT able to join a domain and does not permit -the use of domain logons.</em></span> -</p><p> -Implementing a Samba PDC can basically be divided into 3 broad -steps. -</p><div class="orderedlist"><ol type="1"><li><p> - Configuring the Samba PDC - </p></li><li><p> - Creating machine trust accounts and joining clients to the domain - </p></li><li><p> - Adding and managing domain user accounts - </p></li></ol></div><p> -There are other minor details such as user profiles, system -policies, etc... However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking -concepts. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860563"></a>Configuring the Samba Domain Controller</h2></div></div><p> -The first step in creating a working Samba PDC is to -understand the parameters necessary in smb.conf. Here we -attempt to explain the parameters that are covered in -the <tt>smb.conf</tt> man page. -</p><p> -Here is an example <tt>smb.conf</tt> for acting as a PDC: -</p><pre class="programlisting"> -[global] - ; Basic server settings - <a href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a> = <i><tt>POGO</tt></i> - <a href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> = <i><tt>NARNIA</tt></i> - - ; User and Machine Account Backends - ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ... - ; mysqlsam, xmlsam, guest - <a href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> = ldapsam, guest - - ; we should act as the domain and local master browser - <a href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> = 64 - <a href="smb.conf.5.html#PERFERREDMASTER" target="_top">preferred master</a> = yes - <a href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master</a> = yes - <a href="smb.conf.5.html#LOCALMASTER" target="_top">local master</a> = yes - - ; security settings (must user security = user) - <a href="smb.conf.5.html#SECURITYEQUALSUSER" target="_top">security</a> = user - - ; encrypted passwords are a requirement for a PDC - <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> = yes - - ; support domain logons - <a href="smb.conf.5.html#DOMAINLOGONS" target="_top">domain logons</a> = yes - - ; where to store user profiles? - <a href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> = \\%N\profiles\%u - - ; where is a user's home directory and where should it be mounted at? - <a href="smb.conf.5.html#LOGONDRIVE" target="_top">logon drive</a> = H: - <a href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> = \\homeserver\%u - - ; specify a generic logon script for all users - ; this is a relative **DOS** path to the [netlogon] share - <a href="smb.conf.5.html#LOGONSCRIPT" target="_top">logon script</a> = logon.cmd - -; necessary share for domain controller -[netlogon] - <a href="smb.conf.5.html#PATH" target="_top">path</a> = /usr/local/samba/lib/netlogon - <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = yes - <a href="smb.conf.5.html#WRITELIST" target="_top">write list</a> = <i><tt>ntadmin</tt></i> - -; share for storing user profiles -[profiles] - <a href="smb.conf.5.html#PATH" target="_top">path</a> = /export/smb/ntprofile - <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 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: - -</p><pre class="programlisting"> - workgroup = NARNIA - domain logons = Yes - security = User -</pre><p> - -The additional parameters shown in the longer listing above just makes for a -more complete environment. -</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 - to do this, refer to <a href="#passdb" title="Chapter 10. User information database">the User Database chapter</a>. - </p></li><li><p> - The server must support domain logons and a - <tt>[netlogon]</tt> share - </p></li><li><p> - The server must be the domain master browser in order for Windows - 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><p> -Samba 3.0 offers a complete implementation of group mapping -between Windows NT groups and Unix groups (this is really quite -complicated to explain in a short space). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860863"></a>Creating Machine Trust Accounts and Joining Clients to the Domain</h2></div></div><p> -A machine trust account is a Samba account that is used to -authenticate a client machine (rather than a user) to the Samba -server. In Windows terminology, this is known as a "Computer -Account."</p><p> -The password of a machine trust account acts as the shared secret for -secure communication with the Domain Controller. This is a security -feature to prevent an unauthorized machine with the same NetBIOS name -from joining the domain and gaining access to domain user/group -accounts. Windows NT, 200x, XP Professional clients use machine trust -accounts, but Windows 9x / Me / XP Home clients do not. Hence, a -Windows 9x / Me / XP Home client is never a true member of a domain -because it does not possess a machine trust account, and thus has no -shared secret with the domain controller. -</p><p>A Windows PDC stores each machine trust account in the Windows -Registry. A Samba-3 PDC also has to store 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 - 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> - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). - </p></li><li><p> - <span class="emphasis"><em>smbpasswd_nua</em></span> - This file is independant of the - system wide user accounts. The use of this back-end option requires - specification of the "non unix account range" option also. It is called - smbpasswd and will be located in the <tt>private</tt> directory. - </p></li><li><p> - <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>passwd.tdb</em></span>. The key benefit of this binary format - file is that it can store binary objects that can not be accomodated - in the traditional plain text smbpasswd file. - </p></li><li><p> - <span class="emphasis"><em>tdbsam_nua</em></span> like the smbpasswd_nua option above, this - file allows the creation of arbitrary user and machine accounts without - requiring that account to be added to the system (/etc/passwd) file. It - too requires the specification of the "non unix account range" option - in the [globals] section of the <tt>smb.conf</tt> file. - </p></li><li><p> - <span class="emphasis"><em>ldapsam</em></span> - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com - </p></li><li><p> - <span class="emphasis"><em>ldapsam_nua</em></span> - LDAP based back-end with no unix - account requirement, like smbpasswd_nua and tdbsam_nua above. - </p></li></ul></div><p>Read the chapter about the <a href="#passdb" title="Chapter 10. User information database">User Database</a> -for details.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -The new tdbsam and ldapsam account backends store vastly more information than -smbpasswd is capable of. The new backend database includes capacity to specify -per user settings for many parameters, over-riding global settings given in the -<tt>smb.conf</tt> file. eg: logon drive, logon home, logon path, etc. -</p></div><p> -A Samba PDC, however, stores each machine trust account in two parts, -as follows: - -</p><div class="itemizedlist"><ul type="disc"><li><p>A Samba account, stored in the same location as user - LanMan and NT password hashes (currently - <tt>smbpasswd</tt>). The Samba account - possesses and uses only the NT password hash.</p></li><li><p>A corresponding Unix account, typically stored in - <tt>/etc/passwd</tt>. (Future releases will alleviate the need to - create <tt>/etc/passwd</tt> entries.) </p></li></ul></div><p> -</p><p> -There are two ways to create machine trust accounts: -</p><div class="itemizedlist"><ul type="disc"><li><p> Manual creation. Both the Samba and corresponding - Unix account are created by hand.</p></li><li><p> "On-the-fly" creation. The Samba machine trust - account is automatically created by Samba at the time the client - is joined to the domain. (For security, this is the - recommended method.) The corresponding Unix account may be - created automatically or manually. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861132"></a>Manual Creation of Machine Trust Accounts</h3></div></div><p> -The first step in manually creating a machine trust account is to -manually create the corresponding Unix account in -<tt>/etc/passwd</tt>. This can be done using -<b>vipw</b> or other 'add user' command that is normally -used to create new Unix accounts. The following is an example for a -Linux based Samba server: -</p><p> - <tt>root# </tt><b>/usr/sbin/useradd -g 100 -d /dev/null -c <i><tt>"machine -nickname"</tt></i> -s /bin/false <i><tt>machine_name</tt></i>$ </b> -</p><p> -<tt>root# </tt><b>passwd -l <i><tt>machine_name</tt></i>$</b> -</p><p>On *BSD systems, this can be done using the 'chpass' utility:</p><p> -<tt>root# </tt><b>chpass -a "<i><tt>machine_name</tt></i>$:*:101:100::0:0:Workstation <i><tt>machine_name</tt></i>:/dev/null:/sbin/nologin"</b> -</p><p> -The <tt>/etc/passwd</tt> entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no -home directory. For example a machine named 'doppy' would have an -<tt>/etc/passwd</tt> entry like this: -</p><pre class="programlisting"> -doppy$:x:505:501:<i><tt>machine_nickname</tt></i>:/dev/null:/bin/false -</pre><p> -Above, <i><tt>machine_nickname</tt></i> can be any -descriptive name for the client, i.e., BasementComputer. -<i><tt>machine_name</tt></i> absolutely must be the NetBIOS -name of the client to be joined to the domain. The "$" must be -appended to the NetBIOS name of the client or Samba will not recognize -this as a machine trust account. -</p><p> -Now that the corresponding Unix account has been created, the next step is to create -the Samba account for the client containing the well-known initial -machine trust account password. This can be done using the <a href="smbpasswd.8.html" target="_top"><b>smbpasswd(8)</b></a> command -as shown here: -</p><p> -<tt>root# </tt><b><tt>smbpasswd -a -m <i><tt>machine_name</tt></i></tt></b> -</p><p> -where <i><tt>machine_name</tt></i> is the machine's NetBIOS -name. The RID of the new machine account is generated from the UID of -the corresponding Unix account. -</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p> - Manually creating a machine trust account using this method is the - equivalent of creating a machine trust account on a Windows NT PDC using - the "Server Manager". From the time at which the account is created - to the time which the client joins the domain and changes the password, - your domain is vulnerable to an intruder joining your domain using - a machine with the same NetBIOS name. A PDC inherently trusts - members of the domain and will serve out a large degree of user - information to such clients. You have been warned! - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861366"></a>"On-the-Fly" Creation of Machine Trust Accounts</h3></div></div><p> -The second (and recommended) way of creating machine trust accounts is -simply to allow the Samba server to create them as needed when the client -is joined to the domain. </p><p>Since each Samba machine trust account requires a corresponding -Unix account, a method for automatically creating the -Unix account is usually supplied; this requires configuration of the -<a href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a> -option in <tt>smb.conf</tt>. This -method is not required, however; corresponding Unix accounts may also -be created manually. -</p><p>Below is an example for a RedHat 6.2 Linux system. -</p><pre class="programlisting"> -[global] - # <...remainder of parameters...> - add user 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><h3 class="title"><a name="id2861423"></a>Joining the Client to the Domain</h3></div></div><p> -The procedure for joining a client to the domain varies with the -version of Windows. -</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Windows 2000</em></span></p><p> - When the user elects to join the client to a domain, Windows prompts for - an account and password that is privileged to join the domain. A Samba administrative - account (i.e., a Samba account that has root privileges on the Samba server) must be - entered here; the operation will fail if an ordinary user account is given. - The password for this account should be set to a different password than the associated - <tt>/etc/passwd</tt> entry, for security reasons. - </p><p> - The session key of the Samba administrative account acts as an - encryption key for setting the password of the machine trust - account. The machine trust account will be created on-the-fly, or - updated if it already exists. - </p></li><li><p><span class="emphasis"><em>Windows NT</em></span></p><p> If the machine trust account was created manually, on the - Identification Changes menu enter the domain name, but do not - check the box "Create a Computer Account in the Domain." In this case, - the existing machine trust account is used to join the machine to - the domain.</p><p> If the machine trust account is to be created - on-the-fly, on the Identification Changes menu enter the domain - name, and check the box "Create a Computer Account in the Domain." In - this case, joining the domain proceeds as above for Windows 2000 - (i.e., you must supply a Samba administrative account when - prompted).</p></li><li><p><span class="emphasis"><em>Samba</em></span></p><p>Joining a samba client to a domain is documented in - the <a href="#domain-member" title="Chapter 8. Samba as a NT4 or Win2k domain member">Domain Member</a> chapter. -</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2861529"></a>Common Problems and Errors</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861536"></a>I cannot include a '$' in a machine name</h3></div></div><p> -A 'machine name' in (typically) <tt>/etc/passwd</tt> -of the machine name with a '$' appended. FreeBSD (and other BSD -systems?) won't create a user with a '$' in their name. -</p><p> -The problem is only in the program used to make the entry. Once made, it works perfectly. -Create a user without the '$' using <b>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><h3 class="title"><a name="id2861574"></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><p> -This happens if you try to create a machine trust account from the -machine itself and already have a connection (e.g. mapped drive) -to a share (or IPC$) on the Samba PDC. The following command -will remove all network drive connections: -</p><p> -<tt>C:\WINNT\></tt> <b>net use * /d</b> -</p><p> -Further, if the machine is already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861621"></a>The system can not log you on (C000019B)....</h3></div></div><p>I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try again or consult your -system administrator" when attempting to logon. -</p><p> -This occurs when the domain SID stored in the secrets.tdb database -is changed. The most common cause of a change in domain SID is when -the domain name and/or the server name (netbios name) is changed. -The only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin. The domain -SID may be reset using either the net or rpcclient utilities. -</p><p> -The reset or change the domain SID you can use the net command as follows: - -</p><pre class="programlisting"> - net getlocalsid 'OLDNAME' - net setlocalsid 'SID' -</pre><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861672"></a>The machine trust account for this computer either does not -exist or is not accessible.</h3></div></div><p> -When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". What's -wrong? -</p><p> -This problem is caused by the PDC not having a suitable machine trust account. -If you are using the <i><tt>add user script</tt></i> method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working. -</p><p> -Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine trust account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine NetBIOS name -with a '$' appended to it ( i.e. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861721"></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><p> -At first be ensure to enable the useraccounts with <b>smbpasswd -e -%user%</b>, this is normally done, when you create an account. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2861746"></a>Domain Control for Windows 9x/ME</h2></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 -network. Also, different access rights can be granted to users if they -successfully authenticate against a domain logon server. Samba-3 does this -now in the same way that MS Windows NT/2K. -</p><p> -The SMB client logging on to a domain has an expectation that every other -server in the domain should accept the same authentication information. -Network browsing functionality of domains and workgroups is identical and -is explained in this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support. -</p><p> -Issues related to the single-logon network model are discussed in this -section. Samba supports domain logons, network logon scripts, and user -profiles for MS Windows for workgroups and MS Windows 9X/ME clients -which are the focus of this section. -</p><p> -When an SMB client in a domain wishes to logon it broadcast requests for a -logon server. The first one to reply gets the job, and validates its -password using whatever mechanism the Samba administrator has installed. -It is possible (but very stupid) to create a domain where the user -database is not shared between servers, i.e. they are effectively workgroup -servers advertising themselves as participating in a domain. This -demonstrates how authentication is quite different from but closely -involved with domains. -</p><p> -Using these features you can make your clients verify their logon via -the Samba server; make clients run a batch file when they logon to -the network and download their preferences, desktop and start menu. -</p><p> -Before launching into the configuration instructions, it is -worthwhile to look at how a Windows 9x/ME client performs a logon: -</p><div class="orderedlist"><ol type="1"><li><p> - The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the - NetBIOS layer. The client chooses the first response it receives, which - contains the NetBIOS name of the logon server to use in the format of - \\SERVER. - </p></li><li><p> - The client then connects to that server, logs on (does an SMBsessetupX) and - then connects to the IPC$ share (using an SMBtconX). - </p></li><li><p> - The client then does a NetWkstaUserLogon request, which retrieves the name - of the user's logon script. - </p></li><li><p> - The client then connects to the NetLogon share and searches for this - and if it is found and can be read, is retrieved and executed by the client. - After this, the client disconnects from the NetLogon share. - </p></li><li><p> - The client then sends a NetUserGetInfo request to the server, to retrieve - the user's home share, which is used to search for profiles. Since the - response to the NetUserGetInfo request does not contain much more then - the user's home share, profiles for Win9X clients MUST reside in the user - home directory. - </p></li><li><p> - The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the user's home share as - a sharename and path. For example, \\server\fred\.profile. - If the profiles are found, they are implemented. - </p></li><li><p> - The client then disconnects from the user's home share, and reconnects to - the NetLogon share and looks for CONFIG.POL, the policies file. If this is - found, it is read and implemented. - </p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861910"></a>Configuration Instructions: Network Logons</h3></div></div><p> -The main difference between a PDC and a Windows 9x logon -server configuration is that -</p><div class="itemizedlist"><ul type="disc"><li><p> -Password encryption is not required for a Windows 9x logon server. -</p></li><li><p> -Windows 9x/ME clients do not possess machine trust accounts. -</p></li></ul></div><p> -Therefore, a Samba PDC will also act as a Windows 9x logon -server. -</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">security mode and master browsers</h3><p> -There are a few comments to make in order to tie up some -loose ends. There has been much debate over the issue of whether -or not it is ok to configure Samba as a Domain Controller in security -modes other than <tt>USER</tt>. The only security mode -which will not work due to technical reasons is <tt>SHARE</tt> -mode security. <tt>DOMAIN</tt> and <tt>SERVER</tt> -mode security is really just a variation on SMB user level security. -</p><p> -Actually, this issue is also closely tied to the debate on whether -or not Samba must be the domain master browser for its workgroup -when operating as a DC. While it may technically be possible -to configure a server as such (after all, browsing and domain logons -are two distinctly different functions), it is not a good idea to do -so. You should remember that the DC must register the DOMAIN#1b NetBIOS -name. This is the name used by Windows clients to locate the DC. -Windows clients do not distinguish between the DC and the DMB. -For this reason, it is very wise to configure the Samba DC as the DMB. -</p><p> -Now back to the issue of configuring a Samba DC to use a mode other -than "security = user". If a Samba host is configured to use -another SMB server or DC in order to validate user connection -requests, then it is a fact that some other machine on the network -(the "password server") knows more about the user than the Samba host. -99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the "workgroup" parameter -must be set to the name of the Windows NT domain (which already -has a domain controller, right?) -</p><p> -Therefore configuring a Samba box as a DC for a domain that -already by definition has a PDC is asking for trouble. -Therefore, you should always configure the Samba DC to be the DMB -for its domain. -</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-bdc"></a>Chapter 6. -Samba Backup Domain Controller to Samba Domain Control -</h2></div><div><div class="author"><h3 class="author">Volker Lendecke</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>></tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845056"></a>Prerequisite Reading</h2></div></div><p> -Before you continue reading in this chapter, please make sure -that you are comfortable with configuring a Samba PDC -as described in the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860294"></a>Background</h2></div></div><p> -What is a Domain Controller? It is a machine that is able to answer -logon requests from workstations in a Windows NT Domain. Whenever a -user logs into a Windows NT Workstation, the workstation connects to a -Domain Controller and asks him whether the username and password the -user typed in is correct. The Domain Controller replies with a lot of -information about the user, for example the place where the users -profile is stored, the users full name of the user. All this -information is stored in the NT user database, the so-called SAM. -</p><p> -There are two kinds of Domain Controller in a NT 4 compatible Domain: -A Primary Domain Controller (PDC) and one or more Backup Domain -Controllers (BDC). The PDC contains the master copy of the -SAM. Whenever the SAM has to change, for example when a user changes -his password, this change has to be done on the PDC. A Backup Domain -Controller is a machine that maintains a read-only copy of the -SAM. This way it is able to reply to logon requests and authenticate -users in case the PDC is not available. During this time no changes to -the SAM are possible. Whenever changes to the SAM are done on the PDC, -all BDC receive the changes from the PDC. -</p><p> -Since version 2.2 Samba officially supports domain logons for all -current Windows Clients, including Windows 2000 and XP. This text -assumes the domain to be named SAMBA. To be able to act as a PDC, some -parameters in the [global]-section of the smb.conf have to be set: -</p><pre class="programlisting"> - workgroup = SAMBA - domain master = yes - domain logons = yes -</pre><p> -Several other things like a [homes] and a [netlogon] share also may be -set along with settings for the profile path, the users home drive and -others. This will not be covered in this document. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862166"></a>What qualifies a Domain Controller on the network?</h2></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 is -normally reserved for the domain master browser, a role that has -nothing to do with anything related to authentication, but the -Microsoft Domain implementation requires the domain master browser to -be on the same machine as the PDC. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862187"></a>How does a Workstation find its domain controller?</h3></div></div><p> -A NT workstation in the domain SAMBA that wants a local user to be -authenticated has to find the domain controller for SAMBA. It does -this by doing a NetBIOS name query for the group name SAMBA#1c. It -assumes that each of the machines it gets back from the queries is a -domain controller and can answer logon requests. To not open security -holes both the workstation and the selected (TODO: How is the DC -chosen) domain controller authenticate each other. After that the -workstation sends the user's credentials (his name and password) to -the domain controller, asking for approval. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862212"></a>When is the PDC needed?</h3></div></div><p> -Whenever a user wants to change his password, this has to be done on -the PDC. To find the PDC, the workstation does a NetBIOS name query -for SAMBA#1b, assuming this machine maintains the master copy of the -SAM. The workstation contacts the PDC, both mutually authenticate and -the password change is done. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862231"></a>Can Samba be a Backup Domain Controller to an NT PDC?</h2></div></div><p> -With version 2.2, no. The native NT SAM replication protocols have -not yet been fully implemented. The Samba Team is working on -understanding and implementing the protocols, but this work has not -been finished for version 2.2. -</p><p> -With version 3.0, the work on both the replication protocols and a -suitable storage mechanism has progressed, and some form of NT4 BDC -support is expected soon. -</p><p> -Can I get the benefits of a BDC with Samba? Yes. The main reason for -implementing a BDC is availability. If the PDC is a Samba machine, -a second Samba machine can be set up to -service logon requests whenever the PDC is down. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862264"></a>How do I set up a Samba BDC?</h2></div></div><p> -Several things have to be done: -</p><div class="itemizedlist"><ul type="disc"><li><p> -The domain SID has to be the same on the PDC and the BDC. This used to -be stored in the file private/MACHINE.SID. This file is not created -anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is -stored in the file private/secrets.tdb. Simply copying the secrets.tdb -from the PDC to the BDC does not work, as the BDC would -generate a new SID for itself and override the domain SID with this -new BDC SID.</p><p> -To retrieve the domain SID from the PDC or an existing BDC and store it in the -secrets.tdb, execute 'net rpc getsid' on the BDC. -</p></li><li><p> -The Unix user database has to be synchronized from the PDC to the -BDC. This means that both the /etc/passwd and /etc/group have to be -replicated from the PDC to the BDC. This can be done manually -whenever changes are made, or the PDC is set up as a NIS master -server and the BDC as a NIS slave server. To set up the BDC as a -mere NIS client would not be enough, as the BDC would not be able to -access its user database in case of a PDC failure. -</p></li><li><p> -The Samba password database in the file private/smbpasswd has to be -replicated from the PDC to the BDC. This is a bit tricky, see the -next section. -</p></li><li><p> -Any netlogon share has to be replicated from the PDC to the -BDC. This can be done manually whenever login scripts are changed, -or it can be done automatically together with the smbpasswd -synchronization. -</p></li></ul></div><p> -Finally, the BDC has to be found by the workstations. This can be done -by setting -</p><pre class="programlisting"> - workgroup = samba - domain master = no - domain logons = yes -</pre><p> -in the [global]-section of the smb.conf of the BDC. This makes the BDC -only register the name SAMBA#1c with the WINS server. This is no -problem as the name SAMBA#1c is a NetBIOS group name that is meant to -be registered by more than one machine. The parameter 'domain master = -no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS -name is reserved for the Primary Domain Controller. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862361"></a>How do I replicate the smbpasswd file?</h3></div></div><p> -Replication of the smbpasswd file is sensitive. It has to be done -whenever changes to the SAM are made. Every user's password change is -done in the smbpasswd file and has to be replicated to the BDC. So -replicating the smbpasswd file very often is necessary. -</p><p> -As the smbpasswd file contains plain text password equivalents, it -must not be sent unencrypted over the wire. The best way to set up -smbpasswd replication from the PDC to the BDC is to use the utility -rsync. rsync can use ssh as a transport. ssh itself can be set up to -accept *only* rsync transfer without requiring the user to type a -password. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862390"></a>Can I do this all with LDAP?</h3></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><h2 class="title"><a name="ADS"></a>Chapter 7. Samba as a ADS domain member</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">2002/2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><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="#id2862919">Notes</a></dt></dl></div><p> -This is a rough guide to setting up Samba 3.0 with kerberos authentication against a -Windows2000 KDC. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862021"></a>Setup your <tt>smb.conf</tt></h2></div></div><p>You must use at least the following 3 options in smb.conf:</p><pre class="programlisting"> - realm = YOUR.KERBEROS.REALM - security = ADS - encrypt passwords = yes -</pre><p> -In case samba can't figure out your ads server using your realm name, use the -<b>ads server</b> option in <tt>smb.conf</tt>: -</p><pre class="programlisting"> - ads server = your.kerberos.server -</pre><p> -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You do *not* need a smbpasswd file, and older clients will - be authenticated as if <b>security = domain</b>, - although it won't do any harm - and allows you to have local users not in the domain. - I expect that the above required options will change soon when we get better - active directory integration.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862571"></a>Setup your <tt>/etc/krb5.conf</tt></h2></div></div><p>Note: you will need the krb5 workstation, devel, and libs installed</p><p>The minimal configuration for <tt>krb5.conf</tt> is:</p><pre class="programlisting"> - [realms] - YOUR.KERBEROS.REALM = { - kdc = your.kerberos.server - } -</pre><p>Test your config by doing a <b><tt>kinit -<i><tt>USERNAME</tt></i>@<i><tt>REALM</tt></i></tt></b> and -making sure that your password is accepted by the Win2000 KDC. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The realm must be uppercase or you will get "Cannot find KDC for requested -realm while getting initial credentials" 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 -"kinit(v5): Clock skew too great while getting initial credentials" if the time -difference is more than five minutes. </p></div><p> -You also must ensure that you can do a reverse DNS lookup on the IP -address of your KDC. Also, the name that this reverse lookup maps to -must either be the netbios name of the KDC (ie. the hostname with no -domain attached) or it can alternatively be the netbios name -followed by the realm. -</p><p> -The easiest way to ensure you get this right is to add a -<tt>/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 -"local error" when you try to join the realm. -</p><p> -If all you want is kerberos support in smbclient then you can skip -straight to <a href="#ads-test-smbclient" title="Testing with smbclient">Test with smbclient</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 smbd and winbindd. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-create-machine-account"></a>Create the computer account</h2></div></div><p> -As a user that has write permission on the Samba private directory -(usually root) run: -</p><pre class="programlisting"> - <b><tt>net join -U Administrator%password</tt></b> -</pre><p> -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862765"></a>Possible errors</h3></div></div><p> -</p><div class="variablelist"><dl><dt><span class="term">"ADS support not compiled in"</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">net join prompts for user name</span></dt><dd><p>You need to login to the domain using <b><tt>kinit - <i><tt>USERNAME</tt></i>@<i><tt>REALM</tt></i></tt></b>. - <i><tt>USERNAME</tt></i> must be a user who has rights to add a machine - to the domain. </p></dd></dl></div><p> -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-test-server"></a>Test your server setup</h2></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><tt>net use * \\server\share</tt></b>. You should -be logged in with kerberos without needing to know a password. If -this fails then run <b><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="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-test-smbclient"></a>Testing with smbclient</h2></div></div><p> -On your Samba server try to login to a Win2000 server or your Samba -server using smbclient and kerberos. Use smbclient as usual, but -specify the <i><tt>-k</tt></i> option to choose kerberos authentication. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862919"></a>Notes</h2></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="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="domain-member"></a>Chapter 8. Samba as a NT4 or Win2k domain member</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">16 Apr 2001</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862413"></a>Joining an NT Domain with Samba 3.0</h2></div></div><p><span class="emphasis"><em>Assumptions:</em></span> - </p><pre class="programlisting"> - NetBIOS name: SERV1 - Win2K/NT domain name: DOM - Domain's PDC NetBIOS name: DOMPDC - Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2 - </pre><p> - </p><p>First, you must edit your <tt>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><tt>security =</tt></i></a> line in the [global] section - of your <tt>smb.conf</tt> to read:</p><p><b>security = domain</b></p><p>Next change the <a href="smb.conf.5.html#WORKGROUP" target="_top"><i><tt> - workgroup =</tt></i></a> line in the [global] section to read: </p><p><b>workgroup = DOM</b></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"> - <i><tt>encrypt passwords</tt></i></a> set to <tt>yes - </tt> in order for your users to authenticate to the NT PDC.</p><p>Finally, add (or modify) a <a href="smb.conf.5.html#PASSWORDSERVER" target="_top"> - <i><tt>password server =</tt></i></a> line in the [global] - section to read: </p><p><b>password server = DOMPDC DOMBDC1 DOMBDC2</b></p><p>These are the primary and backup domain controllers Samba - will attempt to contact in order to authenticate users. Samba will - try to contact each of these servers in order, so you may want to - rearrange this list in order to spread out the authentication load - among domain controllers.</p><p>Alternatively, if you want smbd to automatically determine - the list of Domain controllers to use for authentication, you may - set this line to be :</p><p><b>password server = *</b></p><p>This method, allows Samba to use exactly the same - mechanism that NT does. This - method either broadcasts or uses a WINS database in order to - find domain controllers to authenticate against.</p><p>In order to actually join the domain, you must run this - command:</p><p><tt>root# </tt><b><tt>net join -S DOMPDC - -U<i><tt>Administrator%password</tt></i></tt></b></p><p> - If the <b><tt>-S DOMPDC</tt></b> argument is not given then - the domain name will be obtained from smb.conf. - </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><tt>Administrator%password</tt></i> is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:</p><p><tt>Joined domain DOM.</tt> - or <tt>Joined 'SERV1' to realm 'MYREALM'</tt> - </p><p>in your terminal window. See the <a href="net.8.html" target="_top"> - net(8)</a> man page for more details.</p><p>This process joins the server to the domain - without having to create the machine trust account on the PDC - beforehand.</p><p>This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :</p><p><tt>/usr/local/samba/private/secrets.tdb</tt></p><p>This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.</p><p>Finally, restart your Samba daemons and get ready for - clients to begin using domain security!</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863318"></a>Why is this better than security = server?</h2></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>DOM\fred - </tt> attaches to your domain security Samba server, there needs - to be a local Unix user fred to represent that user in the Unix - filesystem. This is very similar to the older Samba security mode - <a href="smb.conf.5.html#SECURITYEQUALSSERVER" target="_top">security = server</a>, - 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 - assign UNIX uids and gids to Windows NT Domain users and groups. - </p><p>The advantage to domain-level security is that the - authentication in domain-level security is passed down the authenticated - RPC channel in exactly the same way that an NT server would do it. This - means Samba servers now participate in domain trust relationships in - exactly the same way NT servers do (i.e., you can add Samba servers into - a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC).</p><p>In addition, with <b>security = server</b> every Samba - daemon on a server has to keep a connection open to the - authenticating server for as long as that daemon lasts. This can drain - the connection resources on a Microsoft NT server and cause it to run - out of available connections. With <b>security = domain</b>, - however, the Samba daemons connect to the PDC/BDC only for as long - as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.</p><p>And finally, acting in the same manner as an NT server - authenticating to a PDC means that as part of the authentication - reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Much of the text of this document - was first published in the Web magazine <a href="http://www.linuxworld.com" target="_top"> - LinuxWorld</a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">Doing - the NIS/NT Samba</a>.</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2859626"></a>Valuable Nuts and Bolts Information</h1></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>9. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</a></dt></dl></dd></dl></dd><dt>10. <a href="#passdb">User information database</a></dt><dd><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></dd><dt>11. <a href="#unix-permissions">UNIX Permission Bits and Windows NT Access Control Lists</a></dt><dd><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT - security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute - mapping</a></dt></dl></dd><dt>12. <a href="#groupmapping">Configuring Group Mapping</a></dt><dt>13. <a href="#printing">Printing Support</a></dt><dd><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></dd><dt>14. <a href="#CUPS-printing">CUPS Printing Support</a></dt><dd><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></dd><dt>15. <a href="#winbind">Unified Logons between Windows NT and UNIX using Winbind</a></dt><dd><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></dd><dt>16. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></dd><dt>17. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></dd><dt>18. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></dd><dt>19. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></dd><dt>20. <a href="#pam">PAM Configuration for Centrally Managed Authentication</a></dt><dd><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></dd><dt>21. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></dd><dt>22. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></dd><dt>23. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</a></dt></dl></dd></dl></dd><dt>24. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></dd><dt>25. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></dd><dt>26. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter 9. Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</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 -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 -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><h2 class="title" style="clear: both"><a name="id2862996"></a>What is Browsing?</h2></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. -</p><p> -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 -called <tt>nmbd</tt>. The configuration parameters involved in nmbd's operation are: -</p><pre class="programlisting"> - Browsing options: - ----------------- - * os level - lm announce - lm interval - * preferred master - * local master - * domain master - browse list - enhanced browsing - - Name Resolution Method: - ----------------------- - * name resolve order - - WINS options: - ------------- - dns proxy - wins proxy - * wins server - * wins support - wins hook -</pre><p> -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><h2 class="title" style="clear: both"><a name="id2863646"></a>Discussion</h2></div></div><p> -Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. -MS Windows products can do likewise. NetBIOS based networking uses broadcast -messaging to affect browse list management. When running NetBIOS over -TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast. -</p><p> -Normally, only unicast UDP messaging can be forwarded by routers. The -<b>remote announce</b> -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -<b>remote browse sync</b> parameter of <tt>smb.conf</tt> -implements browse list collation using unicast UDP. -</p><p> -Secondly, in those networks where Samba is the only SMB server technology -wherever possible <tt>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 -get cross segment browsing to work is by using the -<b>remote announce</b> and the <b>remote browse sync</b> -parameters to your <tt>smb.conf</tt> file. -</p><p> -If only one WINS server is used for an entire multi-segment network then -the use of the <b>remote announce</b> and the -<b>remote browse sync</b> parameters should NOT be necessary. -</p><p> -As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation. -</p><p> -Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one <tt>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 -<b>remote browse sync</b> and <b>remote announce</b> -to affect browse list collation across all -segments. Note that this means clients will only resolve local names, -and must be configured to use DNS to resolve names on other subnets in -order to resolve the IP addresses of the servers they can see on other -subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario). -</p><p> -Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863809"></a>How Browsing Functions</h2></div></div><p> -As stated above, MS Windows machines register their NetBIOS names -(ie: the machine name for each service type in operation) on start -up. Also, as stated above, the exact method by which this name registration -takes place is determined by whether or not the MS Windows client/server -has been given a WINS server address, whether or not LMHOSTS lookup -is enabled, or if DNS for NetBIOS name resolution is enabled, etc. -</p><p> -In the case where there is no WINS server all name registrations as -well as name lookups are done by UDP broadcast. This isolates name -resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the -<b>remote announce</b> parameter). -</p><p> -Where a WINS server is used, the MS Windows client will use UDP -unicast to register with the WINS server. Such packets can be routed -and thus WINS allows name resolution to function across routed networks. -</p><p> -During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local -master browser (found by asking WINS or from LMHOSTS) and exchanging browse -list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election -is held to determine which machine will be the master browser. By the nature of -the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser. -</p><p> -Clients wishing to browse the network make use of this list, but also depend -on the availability of correct name resolution to the respective IP -address/addresses. -</p><p> -Any configuration that breaks name resolution and/or browsing intrinsics -will annoy users because they will have to put up with protracted -inability to use the network services. -</p><p> -Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the <b>remote -browse sync</b> parameter in the <tt>smb.conf</tt> file. -This causes Samba to contact the local master browser on a remote network and -to request browse list synchronisation. This effectively bridges -two networks that are separated by routers. The two remote -networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the <b>remote -browse sync</b> parameter provides browse list synchronisation - and -that is distinct from name to address resolution, in other -words, for cross subnet browsing to function correctly it is -essential that a name to address resolution mechanism be provided. -This mechanism could be via DNS, <tt>/etc/hosts</tt>, -and so on. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863936"></a>Setting up WORKGROUP Browsing</h3></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* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup. -</p><p> -In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the <tt>smb.conf</tt> file : -</p><p> -</p><pre class="programlisting"> - domain master = yes -</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 [global] section of the <tt>smb.conf</tt> file : -</p><p> -</p><pre class="programlisting"> - domain master = yes - local master = yes - preferred master = yes - os level = 65 -</pre><p> -</p><p> -The domain master browser may be the same machine as the WINS -server, if you require. -</p><p> -Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the -<tt>smb.conf</tt> file : -</p><p> -</p><pre class="programlisting"> - domain master = no - local master = yes - preferred master = yes - os level = 65 -</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. -</p><p> -The <b>local master</b> parameter allows Samba to act as a -local master browser. The <b>preferred master</b> causes nmbd -to force a browser election on startup and the <b>os level</b> -parameter sets Samba high enough so that it should win any browser elections. -</p><p> -If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the <b>[global]</b> section of the -<tt>smb.conf</tt> file : -</p><p> -</p><pre class="programlisting"> - domain master = no - local master = no - preferred master = no - os level = 0 -</pre><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864124"></a>Setting up DOMAIN Browsing</h3></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 -things will break if a Samba server registers the Domain master -browser NetBIOS name (<i><tt>DOMAIN</tt></i><1B>) -with WINS instead of the PDC. -</p><p> -For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the <b>[global]</b> section -of the <tt>smb.conf</tt> file : -</p><p> -</p><pre class="programlisting"> - domain master = no - local master = yes - preferred master = yes - os level = 65 -</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 <b>os level</b> parameter -to lower levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section <a href="#browse-force-master" 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 -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the <b>[global]</b> section of the <tt>smb.conf</tt> -file : -</p><p> -</p><pre class="programlisting"> - domain master = no - local master = no - preferred master = no - os level = 0 -</pre><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="browse-force-master"></a>Forcing samba to be the master</h3></div></div><p> -Who becomes the <b>master browser</b> is determined by an election -process using broadcasts. Each election packet contains a number of parameters -which determine what precedence (bias) a host should have in the -election. By default Samba uses a very low precedence and thus loses -elections to just about anyone else. -</p><p> -If you want Samba to win elections then just set the <b>os level</b> global -option in <tt>smb.conf</tt> to a higher number. It defaults to 0. Using 34 -would make it win all elections over every other system (except other -samba systems!) -</p><p> -A <b>os level</b> of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. -</p><p>The maximum os level is 255</p><p> -If you want samba to force an election on startup, then set the -<b>preferred master</b> global option in <tt>smb.conf</tt> to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with <b>preferred master</b> to -"yes", then periodically and continually they will force an election -in order to become the local master browser. -</p><p> -If you want samba to be a <b>domain master browser</b>, then it is -recommended that you also set <b>preferred master</b> to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet. -</p><p> -It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864390"></a>Making samba the domain master</h3></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 <b>domain master = yes</b> -in <tt>smb.conf</tt>. By default it will not be a domain master. -</p><p> -Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain. -</p><p> -When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists. -</p><p> -If you want samba to be the domain master then I suggest you also set -the <b>os level</b> high enough to make sure it wins elections, and set -<b>preferred master</b> to "yes", to get samba to force an election on -startup. -</p><p> -Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur: -</p><div class="orderedlist"><ol type="1"><li><p> - your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. - </p></li><li><p> - if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. - </p></li></ol></div><p> -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 - as its domain master browser. - </p></li><li><p> - when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. - </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864538"></a>Note about broadcast addresses</h3></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><h3 class="title"><a name="id2864555"></a>Multiple interfaces</h3></div></div><p> -Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the <b>interfaces</b> -option in <tt>smb.conf</tt> to configure them. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864584"></a>Use of the <b>Remote Announce</b> parameter</h3></div></div><p> -The <b>remote announce</b> parameter of -<tt>smb.conf</tt> can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the <b>remote announce</b> parameter is: -</p><pre class="programlisting"> - remote announce = a.b.c.d [e.f.g.h] ... -</pre><p> -_or_ -</p><pre class="programlisting"> - remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... -</pre><p> - -where: -</p><div class="variablelist"><dl><dt><span class="term"><i><tt>a.b.c.d</tt></i> and -<i><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. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.</p></dd><dt><span class="term"><i><tt>WORKGROUP</tt></i></span></dt><dd><p>is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided. -</p></dd></dl></div><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864695"></a>Use of the <b>Remote Browse Sync</b> parameter</h3></div></div><p> -The <b>remote browse sync</b> parameter of -<tt>smb.conf</tt> is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our -Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment. -</p><p> -The syntax of the <b>remote browse sync</b> parameter is: - -</p><pre class="programlisting"> -remote browse sync = <i><tt>a.b.c.d</tt></i> -</pre><p> - -where <i><tt>a.b.c.d</tt></i> is either the IP address of the -remote LMB or else is the network broadcast address of the remote segment. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2864763"></a>WINS - The Windows Internetworking Name Server</h2></div></div><p> -Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly -recommended. Every NetBIOS machine registers it's name together with a -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name. -</p><p> -All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information). -</p><p> -WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -<tt>lmhosts</tt> files that must reside on all clients in the -absence of WINS. -</p><p> -WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only. -</p><p> -Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors. -</p><p> -To configure Samba as a WINS server just add -<b>wins support = yes</b> to the <tt>smb.conf</tt> -file [globals] section. -</p><p> -To configure Samba to register with a WINS server just add -"wins server = a.b.c.d" to your smb.conf file [globals] section. -</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p> -Never use both <b>wins support = yes</b> together -with <b>wins server = a.b.c.d</b> -particularly not using it's own IP address. -Specifying both will cause nmbd to refuse to start! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863586"></a>Setting up a WINS server</h3></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>smb.conf</tt> file on the selected machine : -in the [globals] section add the line -</p><p> -</p><pre class="programlisting"> - wins support = yes -</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 -least set the parameter to 'no' on all these machines. -</p><p> -Machines with <b>wins support = yes</b> will keep a list of -all NetBIOS names registered with them, acting as a DNS for NetBIOS names. -</p><p> -You should set up only ONE wins server. Do NOT set the -<b>wins support = yes</b> option on more than one Samba -server. -</p><p> -To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the -<b>wins support = yes</b> parameter set. -</p><p> -After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all <tt>smb.conf</tt> files : -</p><p> -</p><pre class="programlisting"> - wins server = <name or IP address> -</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> -Note that this line MUST NOT BE SET in the <tt>smb.conf</tt> file of the Samba -server acting as the WINS server itself. If you set both the -<b>wins support = yes</b> option and the -<b>wins server = <name></b> option then -nmbd will fail to start. -</p><p> -There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865218"></a>WINS Replication</h3></div></div><p> -Samba-3 permits WINS replication through the use of the <tt>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><h3 class="title"><a name="id2865243"></a>Static WINS Entries</h3></div></div><p> -New to Samba-3 is a tool called <tt>winsedit</tt> that may be used to add -static WINS entries to the WINS database. This tool can be used also to modify entries -existing in the WINS database. -</p><p> -The development of the winsedit tool was made necessary due to the migration -of the older style wins.dat file into a new tdb binary backend data store. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865274"></a>Helpful Hints</h2></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><h3 class="title"><a name="id2865287"></a>Windows Networking Protocols</h3></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 -one protocol on an MS Windows machine. -</p><p> -Every NetBIOS machine takes part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role. -</p><p> -The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail. -</p><p><span class="emphasis"><em> -Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols. -</em></span></p><p> -The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865354"></a>Name Resolution Order</h3></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>/etc/hosts: is static, hard to maintain, and lacks name_type info</td></tr><tr><td>DNS: is a good choice but lacks essential name_type info.</td></tr></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: -</p><pre class="programlisting"> -name resolve order = wins lmhosts bcast host -</pre><p> -_or_ -</p><pre class="programlisting"> -name resolve order = wins lmhosts (eliminates bcast and host) -</pre><p> -The default is: -</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>/etc/host.conf</tt>, <tt>/etc/nsswitch.conf</tt> and <tt>/etc/resolv.conf</tt>. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865470"></a>Technical Overview of browsing</h2></div></div><p> -SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called <b>browse list</b>. This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document. -</p><p> -MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly. -</p><p> -Where NetBIOS over TCP/IP is enabled use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865517"></a>Browsing support in samba</h3></div></div><p> -Samba facilitates browsing. The browsing is supported by nmbd -and is also controlled by options in the <tt>smb.conf</tt> file. -Samba can act as a local browse master for a workgroup and the ability -to support domain logons and scripts is now available. -</p><p> -Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server. -</p><p> -Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service. -</p><div class="note" 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 -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server. -</p></div><p> -To get browsing to work you need to run nmbd as usual, but will need -to use the <b>workgroup</b> option in <tt>smb.conf</tt> -to control what workgroup Samba becomes a part of. -</p><p> -Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See <b>remote announce</b> in the -<tt>smb.conf</tt> man page. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865624"></a>Problem resolution</h3></div></div><p> -If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called <tt>browse.dat</tt>. -</p><p> -Note that if it doesn't work for you, then you should still be able to -type the server name as <tt>\\SERVER</tt> in filemanager then -hit enter and filemanager should display the list of available shares. -</p><p> -Some people find browsing fails because they don't have the global -<b>guest account</b> set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must -have a valid guest account. -</p><p><span class="emphasis"><em> -MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources. -</em></span></p><p> -The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in <tt>smb.conf</tt>) -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865703"></a>Browsing across subnets</h3></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><p> -To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server. -</p><p> -Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the <tt>smb.conf</tt> file. -</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865754"></a>How does cross subnet browsing work ?</h4></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><p> -</p><pre class="programlisting"> - (DMB) - N1_A N1_B N1_C N1_D N1_E - | | | | | - ------------------------------------------------------- - | subnet 1 | - +---+ +---+ - |R1 | Router 1 Router 2 |R2 | - +---+ +---+ - | | - | subnet 2 subnet 3 | - -------------------------- ------------------------------------ - | | | | | | | | - N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D - (WINS) -</pre><p> -</p><p> -Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it. -</p><p> -As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser. -</p><p> -On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list. -</p><p> -For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'. -</p><p> -At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now). -</p><p> -</p><pre class="programlisting"> -Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D -</pre><p> -</p><p> -Note that at this point all the subnets are separate, no -machine is seen across any of the subnets. -</p><p> -Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP<1B>. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted. -</p><p> -Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like : -</p><p> -</p><pre class="programlisting"> -Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - -Servers with a (*) after them are non-authoritative names. -</pre><p> -</p><p> -At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet. -</p><p> -The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like. -</p><p> -</p><pre class="programlisting"> -Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*), - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Servers with a (*) after them are non-authoritative names. -</pre><p> -</p><p> -At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on -subnet 2 will still only see the servers on subnets 1 and 2, but not 3. -</p><p> -Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing -server entries. Finally - and as a steady state (if no machines -are removed or shut off) the browse lists will look like : -</p><p> -</p><pre class="programlisting"> -Subnet Browse Master List ------- ------------- ---- -Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, - N2_A(*), N2_B(*), N2_C(*), N2_D(*), - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet2 N2_B N2_A, N2_B, N2_C, N2_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) - N3_A(*), N3_B(*), N3_C(*), N3_D(*) - -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Servers with a (*) after them are non-authoritative names. -</pre><p> -</p><p> -Synchronizations between the domain master browser and local -master browsers will continue to occur, but this should be a -steady state situation. -</p><p> -If either router R1 or R2 fails the following will occur: -</p><div class="orderedlist"><ol type="1"><li><p> - Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. - </p></li><li><p> - Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. - </p></li><li><p> - If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. - </p></li></ol></div></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="passdb"></a>Chapter 10. User information database</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Olivier (lem) Lemaire</h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><tt><<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></tt></p></div></div></div></div><div><p class="pubdate">February 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866099"></a>Introduction</h2></div></div><p>Old windows clients send plain text passwords over the wire. - Samba can check these passwords by crypting them and comparing them - to the hash stored in the unix user database. - </p><p> - Newer windows clients send encrypted passwords (so-called - Lanman and NT hashes) over - the wire, instead of plain text passwords. The newest clients - will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked. - </p><p>These passwords can't be converted to unix style encrypted - passwords. Because of that you can't use the standard unix - user database, and you have to store the Lanman and NT hashes - somewhere else. </p><p>Next to a differently encrypted passwords, - windows also stores certain data for each user - that is not stored in a unix user database, e.g. - workstations the user may logon from, the location where his/her - profile is stored, etc. - Samba retrieves and stores this information using a "passdb backend". - Commonly - available backends are LDAP, plain text file, MySQL and nisplus. - For more information, see the documentation about the - <b>passdb backend = </b> parameter. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866152"></a>Important Notes About Security</h2></div></div><p>The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - scheme typically sends clear text passwords over the network when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext password over the network but it does store the 16 byte - hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's - password from them, but they could potentially be used in a modified - client to gain access to a server. This would require considerable - technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the data stored in whatever - passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.</p><p>Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc). </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are <span class="emphasis"><em>never</em></span> sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.</p><p>Other Microsoft operating systems which also exhibit - this behavior includes</p><p> These versions of MS Windows do not support full domain - security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.</p><table class="simplelist" border="0" summary="Simple list"><tr><td>MS DOS Network client 3.0 with - the basic network redirector installed</td></tr><tr><td>Windows 95 with the network redirector - update installed</td></tr><tr><td>Windows 98 [se]</td></tr><tr><td>Windows Me</td></tr><tr><td>Windows XP Home</td></tr></table><p> The following versions of MS Windows fully support domain - security protocols.</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Windows NT 3.5x</td></tr><tr><td>Windows NT 4.0</td></tr><tr><td>Windows 2000 Professional</td></tr><tr><td>Windows 200x Server/Advanced Server</td></tr><tr><td>Windows XP Professional</td></tr></table></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.</p></div><p>MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. <span class="emphasis"><em>USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866314"></a>Advantages of SMB Encryption</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Plain text passwords are not passed across - the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.</td></tr><tr><td>WinNT doesn't like talking to a server - that does not support encrypted passwords. It will refuse - to browse the server if the server is also in user level - security mode. It will insist on prompting the user for the - password on each connection, which is very annoying. The - only things you can do to stop this is to use SMB encryption. - </td></tr><tr><td>Encrypted password support allows automatic share - (resource) reconnects.</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866353"></a>Advantages of non-encrypted passwords</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Plain text passwords are not kept - on disk, and are NOT cached in memory. </td></tr><tr><td>Uses same password file as other unix - services such as login and ftp</td></tr><tr><td>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.</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866388"></a>The smbpasswd Command</h2></div></div><p>The smbpasswd utility is a utility similar to the - <b>passwd</b> or <b>yppasswd</b> programs. - It maintains the two 32 byte password fields in the passdb backend. </p><p><b>smbpasswd</b> works in a client-server mode - where it contacts the local smbd to change the user's password on its - behalf. This has enormous benefits - as follows.</p><p><b>smbpasswd</b> has the capability - to change passwords on Windows NT servers (this only works when - the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).</p><p>To run smbpasswd as a normal user just type :</p><p><tt>$ </tt><b><tt>smbpasswd</tt></b></p><p><tt>Old SMB password: </tt><b><tt><type old value here - - or hit return if there was no old password></tt></b></p><p><tt>New SMB Password: </tt><b><tt><type new value> - </tt></b></p><p><tt>Repeat New SMB Password: </tt><b><tt><re-type new value - </tt></b></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>If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.</p><p>If run by the root user smbpasswd may take an optional - argument, specifying the user name whose SMB password you wish to - change. Note that when run as root smbpasswd does not prompt for - or check the old password value, thus allowing root to set passwords - for users who have forgotten their passwords.</p><p><b>smbpasswd</b> is designed to work in the same way - and be familiar to UNIX users who use the <b>passwd</b> or - <b>yppasswd</b> commands.</p><p>For more details on using <b>smbpasswd</b> refer - to the man page which will always be the definitive reference.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866568"></a>Plain text</h2></div></div><p> -Older versions of samba retrieved user information from the unix user database -and eventually some other fields from the file <tt>/etc/samba/smbpasswd</tt> -or <tt>/etc/smbpasswd</tt>. When password encryption is disabled, no -data is stored at all. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866597"></a>TDB</h2></div></div><p>Samba can also store the user data in a "TDB" (Trivial Database). Using this backend -doesn't require any additional configuration. This backend is recommended for new installations that -don not require LDAP. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866613"></a>LDAP</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866621"></a>Introduction</h3></div></div><p> -This document describes how to use an LDAP directory for storing Samba user -account information traditionally stored in the smbpasswd(5) file. It is -assumed that the reader already has a basic understanding of LDAP concepts -and has a working directory server already installed. For more information -on LDAP architectures and Directories, please refer to the following sites. -</p><div class="itemizedlist"><ul type="disc"><li><p>OpenLDAP - <a href="http://www.openldap.org/" target="_top">http://www.openldap.org/</a></p></li><li><p>iPlanet Directory Server - <a href="http://iplanet.netscape.com/directory" target="_top">http://iplanet.netscape.com/directory</a></p></li></ul></div><p> -Note that <a href="http://www.ora.com/" target="_top">O'Reilly Publishing</a> is working on -a guide to LDAP for System Administrators which has a planned release date of -early summer, 2002. -</p><p> -Two additional Samba resources which may prove to be helpful are -</p><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><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866721"></a>Encrypted Password Database</h3></div></div><p> -Traditionally, when configuring <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">"encrypt -passwords = yes"</a> in Samba's <tt>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>smbpasswd(5)</tt> file. There are several -disadvantages to this approach for sites with very large numbers of users (counted -in the thousands). -</p><div class="itemizedlist"><ul type="disc"><li><p> -The first is that all lookups must be performed sequentially. Given that -there are approximately two lookups per domain logon (one for a normal -session connection such as when mapping a network drive or printer), this -is a performance bottleneck for large sites. What is needed is an indexed approach -such as is used in databases. -</p></li><li><p> -The second problem is that administrators who desired to replicate a -smbpasswd file to more than one Samba server were left to use external -tools such as <b>rsync(1)</b> and <b>ssh(1)</b> -and wrote custom, in-house scripts. -</p></li><li><p> -And finally, the amount of information which is stored in an -smbpasswd entry leaves no room for additional attributes such as -a home directory, password expiration time, or even a Relative -Identified (RID). -</p></li></ul></div><p> -As a result of these defeciencies, a more robust means of storing user attributes -used by smbd was developed. The API which defines access to user accounts -is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). -</p><p> -There are a few points to stress about that the ldapsam -does not provide. The LDAP support referred to in the this documentation does not -include: -</p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from - an Windows 2000 Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p> -The second item can be accomplished by using LDAP NSS and PAM modules. LGPL -versions of these libraries can be obtained from PADL Software -(<a href="http://www.padl.com/" target="_top">http://www.padl.com/</a>). More -information about the configuration of these packages may be found at "LDAP, -System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866860"></a>Supported LDAP Servers</h3></div></div><p> -The LDAP samdb code in 2.2.3 (and later) has been developed and tested -using the OpenLDAP 2.0 server and client libraries. -The same code should be able to work with Netscape's Directory Server -and client SDK. However, due to lack of testing so far, there are bound -to be compile errors and bugs. These should not be hard to fix. -If you are so inclined, please be sure to forward all patches to -<a href="mailto:samba-patches@samba.org" target="_top">samba-patches@samba.org</a> and -<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866898"></a>Schema and Relationship to the RFC 2307 posixAccount</h3></div></div><p> -Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in -<tt>examples/LDAP/samba.schema</tt>. The sambaAccount objectclass is given here: -</p><pre class="programlisting"> -objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY - DESC 'Samba Account' - MUST ( uid $ rid ) - MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ - logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ - displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ - description $ userWorkstations $ primaryGroupID $ domain )) -</pre><p> -The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are -owned by the Samba Team and as such is legal to be openly published. -If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to <a href="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>/etc/passwd</tt> entry, so is the sambaAccount object -meant to supplement the UNIX user account information. A sambaAccount is a -<tt>STRUCTURAL</tt> objectclass so it can be stored individually -in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design. -</p><p> -In order to store all user account information (UNIX and Samba) in the directory, -it is necessary to use the sambaAccount and posixAccount objectclasses in -combination. However, smbd will still obtain the user's UNIX account -information via the standard C library calls (e.g. getpwnam(), et. al.). -This means that the Samba server must also have the LDAP NSS library installed -and functioning correctly. This division of information makes it possible to -store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867008"></a>Configuring Samba with LDAP</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867016"></a>OpenLDAP configuration</h4></div></div><p> -To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory. -</p><p> -<tt>root# </tt><b><tt>cp samba.schema /etc/openldap/schema/</tt></b> -</p><p> -Next, include the <tt>samba.schema</tt> file in <tt>slapd.conf</tt>. -The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in <tt>cosine.schema</tt> and -the 'displayName' attribute is defined in the <tt>inetorgperson.schema</tt> -file. Both of these must be included before the <tt>samba.schema</tt> file. -</p><pre class="programlisting"> -## /etc/openldap/slapd.conf - -## schema files (core.schema is required by default) -include /etc/openldap/schema/core.schema - -## needed for sambaAccount -include /etc/openldap/schema/cosine.schema -include /etc/openldap/schema/inetorgperson.schema -include /etc/openldap/schema/samba.schema -include /etc/openldap/schema/nis.schema - -.... -</pre><p> -It is recommended that you maintain some indices on some of the most usefull attributes, -like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well). -</p><pre class="programlisting"> -# Indices to maintain -## required by OpenLDAP 2.0 -index objectclass eq - -## support pb_getsampwnam() -index uid pres,eq -## support pdb_getsambapwrid() -index rid eq - -## uncomment these if you are storing posixAccount and -## posixGroup entries in the directory as well -##index uidNumber eq -##index gidNumber eq -##index cn eq -##index memberUid eq - -# (both fetched via ldapsearch): -index primaryGroupID eq -index displayName pres,eq - -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867134"></a>Configuring Samba</h4></div></div><p> -The following parameters are available in smb.conf only with <i><tt>--with-ldapsam</tt></i> -was included when compiling Samba. -</p><div class="itemizedlist"><ul type="disc"><li><p><a href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend [ldapsam|ldapsam_nua]:url</a></p></li><li><p><a href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a></p></li><li><p><a href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a></p></li><li><p><a href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPFILTER" target="_top">ldap filter</a></p></li><li><p><a href="smb.conf.5.html#LDAPPORT" target="_top">ldap port</a></p></li><li><p><a href="smb.conf.5.html#LDAPMACHINSUFFIX" target="_top">ldap machine suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPUSERSUFFIX" target="_top">ldap user suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPDELETEDN" target="_top">ldap delete dn</a></p></li></ul></div><p> -These are described in the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> man -page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as -</p><pre class="programlisting"> -## /usr/local/samba/lib/smb.conf -[global] - security = user - encrypt passwords = yes - - netbios name = TASHTEGO - workgroup = NARNIA - - # ldap related parameters - - # define the DN to use when binding to the directory servers - # The password for this DN is not stored in smb.conf. Rather it - # must be set by using 'smbpasswd -w <i><tt>secretpw</tt></i>' to store the - # passphrase in the secrets.tdb file. If the "ldap admin dn" values - # change, this password will need to be reset. - ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" - - # Define the SSL option when connecting to the directory - # ('off', 'start tls', or 'on' (default)) - ldap ssl = start tls - - passdb backend ldapsam:ldap://ahab.samba.org - - # smbpasswd -x delete the entire dn-entry - ldap delete dn = no - - # the machine and user suffix added to the base suffix - # wrote WITHOUT quotes. NULL siffixes by default - ldap user suffix = ou=People - ldap machine suffix = ou=Systems - - # define the port to use in the LDAP session (defaults to 636 when - # "ldap ssl = on") - ldap port = 389 - - # specify the base DN to use when searching the directory - ldap suffix = "ou=people,dc=samba,dc=org" - - # generally the default ldap search filter is ok - # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))" -</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867304"></a>Accounts and Groups management</h3></div></div><p> -As users accounts are managed thru the sambaAccount objectclass, you should -modify your existing administration tools to deal with sambaAccount attributes. -</p><p> -Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to store thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file). -</p><p> -In Samba release 3.0, the group management system is based on posix -groups. This means that Samba makes usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867341"></a>Security and sambaAccount</h3></div></div><p> -There are two important points to remember when discussing the security -of sambaAccount entries in the directory. -</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the lmPassword or - ntPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to - view the lmPassword or ntPassword attribute values.</p></li></ul></div><p> -These password hashes are clear text equivalents and can be used to impersonate -the user without deriving the original clear text strings. For more information -on the details of LM/NT password hashes, refer to the <a href="#passdb" title="Chapter 10. User information database">User Database</a> of the Samba-HOWTO-Collection. -</p><p> -To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults -to require an encrypted session (<b>ldap ssl = on</b>) using -the default port of 636 -when contacting the directory server. When using an OpenLDAP 2.0 server, it -is possible to use the use the StartTLS LDAP extended operation in the place of -LDAPS. In either case, you are strongly discouraged to disable this security -(<b>ldap ssl = off</b>). -</p><p> -Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS -extended operation. However, the OpenLDAP library still provides support for -the older method of securing communication between clients and servers. -</p><p> -The second security precaution is to prevent non-administrative users from -harvesting password hashes from the directory. This can be done using the -following ACL in <tt>slapd.conf</tt>: -</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></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867456"></a>LDAP specials attributes for sambaAccounts</h3></div></div><p> -The sambaAccount objectclass is composed of the following attributes: -</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmPassword</tt>: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.</p></li><li><p><tt>ntPassword</tt>: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.</p></li><li><p><tt>pwdLastSet</tt>: The integer time in seconds since 1970 when the - <tt>lmPassword</tt> and <tt>ntPassword</tt> attributes were last set. - </p></li><li><p><tt>acctFlags</tt>: string of 11 characters surrounded by square brackets [] - representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).</p></li><li><p><tt>logonTime</tt>: Integer value currently unused</p></li><li><p><tt>logoffTime</tt>: Integer value currently unused</p></li><li><p><tt>kickoffTime</tt>: Integer value currently unused</p></li><li><p><tt>pwdCanChange</tt>: Integer value currently unused</p></li><li><p><tt>pwdMustChange</tt>: Integer value currently unused</p></li><li><p><tt>homeDrive</tt>: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.</p></li><li><p><tt>scriptPath</tt>: The scriptPath property specifies the path of - the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.</p></li><li><p><tt>profilePath</tt>: specifies a path to the user's profile. - This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.</p></li><li><p><tt>smbHome</tt>: The homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. - </p></li><li><p><tt>userWorkstation</tt>: character string value currently unused. - </p></li><li><p><tt>rid</tt>: the integer representation of the user's relative identifier - (RID).</p></li><li><p><tt>primaryGroupID</tt>: the relative identifier (RID) of the primary group - of the user.</p></li></ul></div><p> -The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a> for details on -how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values: -</p><div class="itemizedlist"><ul type="disc"><li><p>smbHome</p></li><li><p>scriptPath</p></li><li><p>logonPath</p></li><li><p>homeDrive</p></li></ul></div><p> -These attributes are only stored with the sambaAccount entry if -the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that <b>logon home = \\%L\%u</b> was defined in -its <tt>smb.conf</tt> file. When a user named "becky" logons to the domain, -the <i><tt>logon home</tt></i> string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", -this value is used. However, if this attribute does not exist, then the value -of the <i><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. \\MOBY\becky). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867737"></a>Example LDIF Entries for a sambaAccount</h3></div></div><p> -The following is a working LDIF with the inclusion of the posixAccount objectclass: -</p><pre class="programlisting"> -dn: uid=guest2, ou=people,dc=plainjoe,dc=org -ntPassword: 878D8014606CDA29677A44EFA1353FC7 -pwdMustChange: 2147483647 -primaryGroupID: 1201 -lmPassword: 552902031BEDE9EFAAD3B435B51404EE -pwdLastSet: 1010179124 -logonTime: 0 -objectClass: sambaAccount -uid: guest2 -kickoffTime: 2147483647 -acctFlags: [UX ] -logoffTime: 2147483647 -rid: 19006 -pwdCanChange: 0 -</pre><p> -The following is an LDIF entry for using both the sambaAccount and -posixAccount objectclasses: -</p><pre class="programlisting"> -dn: uid=gcarter, ou=people,dc=plainjoe,dc=org -logonTime: 0 -displayName: Gerald Carter -lmPassword: 552902031BEDE9EFAAD3B435B51404EE -primaryGroupID: 1201 -objectClass: posixAccount -objectClass: sambaAccount -acctFlags: [UX ] -userPassword: {crypt}BpM2ej8Rkzogo -uid: gcarter -uidNumber: 9000 -cn: Gerald Carter -loginShell: /bin/bash -logoffTime: 2147483647 -gidNumber: 100 -kickoffTime: 2147483647 -pwdLastSet: 1010179230 -rid: 19000 -homeDirectory: /home/tashtego/gcarter -pwdCanChange: 0 -pwdMustChange: 2147483647 -ntPassword: 878D8014606CDA29677A44EFA1353FC7 -</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2867793"></a>MySQL</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867800"></a>Creating the database</h3></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>examples/pdb/mysql/mysql.dump</tt> -contains the correct queries to create the required tables. Use the command : - -<b>mysql -u<i><tt>username</tt></i> -h<i><tt>hostname</tt></i> -p<i><tt>password</tt></i> <i><tt>databasename</tt></i> > <tt>/path/to/samba/examples/pdb/mysql/mysql.dump</tt></b> - -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867854"></a>Configuring</h3></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><p>Add a the following to the <b>passdb backend</b> variable in your <tt>smb.conf</tt>: -</p><pre class="programlisting"> -passdb backend = [other-plugins] mysql:identifier [other-plugins] -</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 'passdb backend', you also need to -use different identifiers! -</p><p> -Additional options can be given thru the smb.conf file in the [global] section. -</p><pre class="programlisting"> -identifier:mysql host - host name, defaults to 'localhost' -identifier:mysql password -identifier:mysql user - defaults to 'samba' -identifier:mysql database - defaults to 'samba' -identifier:mysql port - defaults to 3306 -identifier:table - Name of the table containing users -</pre><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 -smb.conf file, you should make the the smb.conf file -readable only to the user that runs samba. This is considered a security -bug and will be fixed soon. -</p></div><p>Names of the columns in this table(I've added column types those columns should have first):</p><pre class="programlisting"> -identifier:logon time column - int(9) -identifier:logoff time column - int(9) -identifier:kickoff time column - int(9) -identifier:pass last set time column - int(9) -identifier:pass can change time column - int(9) -identifier:pass must change time column - int(9) -identifier:username column - varchar(255) - unix username -identifier:domain column - varchar(255) - NT domain user is part of -identifier:nt username column - varchar(255) - NT username -identifier:fullname column - varchar(255) - Full name of user -identifier:home dir column - varchar(255) - Unix homedir path -identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:') -identifier:logon script column - varchar(255) - - Batch file to run on client side when logging on -identifier:profile path column - varchar(255) - Path of profile -identifier:acct desc column - varchar(255) - Some ASCII NT user data -identifier:workstations column - varchar(255) - - Workstations user can logon to (or NULL for all) -identifier:unknown string column - varchar(255) - unknown string -identifier:munged dial column - varchar(255) - ? -identifier:user sid column - varchar(255) - NT user SID -identifier:group sid column - varchar(255) - NT group ID -identifier:lanman pass column - varchar(255) - encrypted lanman password -identifier:nt pass column - varchar(255) - encrypted nt passwd -identifier:plain pass column - varchar(255) - plaintext password -identifier:acct control column - int(9) - nt user data -identifier:unknown 3 column - int(9) - unknown -identifier:logon divs column - int(9) - ? -identifier:hours len column - int(9) - ? -identifier:unknown 5 column - int(9) - unknown -identifier:unknown 6 column - int(9) - unknown -</pre><p> -Eventually, you can put a colon (:) after the name of each column, which -should specify the column to update when updating the table. You can also -specify nothing behind the colon - then the data from the field will not be -updated. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867999"></a>Using plaintext passwords or encrypted password</h3></div></div><p> -I strongly discourage the use of plaintext passwords, however, you can use them: -</p><p> -If you would like to use plaintext passwords, set -'identifier:lanman pass column' and 'identifier:nt pass column' to -'NULL' (without the quotes) and 'identifier:plain pass column' to the -name of the column containing the plaintext passwords. -</p><p> -If you use encrypted passwords, set the 'identifier:plain pass -column' to 'NULL' (without the quotes). This is the default. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868029"></a>Getting non-column data from the table</h3></div></div><p> -It is possible to have not all data in the database and making some 'constant'. -</p><p> -For example, you can set 'identifier:fullname column' to : -<b>CONCAT(First_name,' ',Sur_name)</b> -</p><p> -Or, set 'identifier:workstations column' to : -<b>NULL</b></p><p>See the MySQL documentation for more language constructs.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868072"></a>XML</h2></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> - <b><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: -<b><tt>pdbedit -i xml:filename -e current-pdb</tt></b> -</p><p> -Where filename is the name to read the data from and current-pdb to put it in. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unix-permissions"></a>Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">12 Apr 1999</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT - security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask - parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute - mapping</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865054"></a>Viewing and changing UNIX permissions using the NT - security dialogs</h2></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 - administrator can set.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - the identity of the Windows user as it is presented by Samba at - the point of file access. This can best be determined from the - Samba log files. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2864937"></a>How to view file security on a Samba share</h2></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="emphasis"><em>Properties</em></span> entry at the bottom of - the menu. This brings up the file properties dialog - box. Click on the tab <span class="emphasis"><em>Security</em></span> and you - will see three buttons, <span class="emphasis"><em>Permissions</em></span>, - <span class="emphasis"><em>Auditing</em></span>, and <span class="emphasis"><em>Ownership</em></span>. - The <span class="emphasis"><em>Auditing</em></span> button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the <b>Add</b> button will not currently - allow a list of users to be seen.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868280"></a>Viewing file ownership</h2></div></div><p>Clicking on the <b>"Ownership"</b> button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :</p><p><b>"SERVER\user (Long name)"</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of - the Samba server, <i><tt>user</tt></i> is the user name of - the UNIX user who owns the file, and <i><tt>(Long name)</tt></i> - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the <b>Close - </b> button to remove this dialog.</p><p>If the parameter <i><tt>nt acl support</tt></i> - is set to <tt>false</tt> then the file owner will - be shown as the NT user <b>"Everyone"</b>.</p><p>The <b>Take Ownership</b> button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the <span class="emphasis"><em>root</em></span> - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.</p><p>There is an NT chown command that will work with Samba - and allow a user with Administrator privilege connected - to a Samba server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the <span class="emphasis"><em>Seclib - </em></span> NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868401"></a>Viewing file or directory permissions</h2></div></div><p>The third button is the <b>"Permissions"</b> - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :</p><p><b>"SERVER\user (Long name)"</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of - the Samba server, <i><tt>user</tt></i> is the user name of - the UNIX user who owns the file, and <i><tt>(Long name)</tt></i> - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).</p><p>If the parameter <i><tt>nt acl support</tt></i> - is set to <tt>false</tt> then the file owner will - be shown as the NT user <b>"Everyone"</b> and the - permissions will be shown as NT "Full Control".</p><p>The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868484"></a>File Permissions</h3></div></div><p>The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group <b>Everyone</b>, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - <b>user</b> icon and an NT <b>local - group</b> icon respectively followed by the list - of permissions allowed for the UNIX user and group.</p><p>As many UNIX permission sets don't map into common - NT names such as <b>"read"</b>, <b> - "change"</b> or <b>"full control"</b> then - usually the permissions will be prefixed by the words <b> - "Special Access"</b> in the NT display list.</p><p>But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT <b>"Take Ownership"</b> ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT <b>"O"</b> bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868587"></a>Directory Permissions</h3></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 <b>"RW"</b> - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.</p><p>The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the <b> - "inherited"</b> permissions that any file created within - this directory would inherit.</p><p>Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868637"></a>Modifying file or directory permissions</h2></div></div><p>Modifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the <b>OK</b> button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.</p><p>If the parameter <i><tt>nt acl support</tt></i> - is set to <tt>false</tt> then any attempt to set - security permissions will fail with an <b>"Access Denied" - </b> message.</p><p>The first thing to note is that the <b>"Add"</b> - button will not return a list of users in Samba (it will give - an error message of <b>"The remote procedure call failed - and did not execute"</b>). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.</p><p>If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the <b>"OK"</b> button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT <b>"O"</b> flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component.</p><p>As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.</p><p>When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the <b>"Replace - permissions on existing files"</b> checkbox in the NT - dialog before clicking <b>"OK"</b>.</p><p>If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the <b>"Remove"</b> button, - or set the component to only have the special <b>"Take - Ownership"</b> permission (displayed as <b>"O" - </b>) highlighted.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868797"></a>Interaction with the standard Samba create mask - parameters</h2></div></div><p>There are four parameters - to control interaction with the standard Samba create mask parameters. - These are :</p><p><i><tt>security mask</tt></i></p><p><i><tt>force security mode</tt></i></p><p><i><tt>directory security mask</tt></i></p><p><i><tt>force directory security mode</tt></i></p><p>Once a user clicks <b>"OK"</b> to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the <a href="smb.conf.5.html#SECURITYMASK" target="_top"> - <i><tt>security mask</tt></i></a> parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions.</p><p>Essentially, zero bits in the <i><tt>security mask</tt></i> - mask may be treated as a set of bits the user is <span class="emphasis"><em>not</em></span> - allowed to change, and one bits are those the user is allowed to change. - </p><p>If not set explicitly this parameter is set to the same value as - the <a href="smb.conf.5.html#CREATEMASK" target="_top"><i><tt>create mask - </tt></i></a> parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter - to 0777.</p><p>Next Samba checks the changed permissions for a file against - the bits set in the <a href="smb.conf.5.html#FORCESECURITYMODE" target="_top"> - <i><tt>force security mode</tt></i></a> parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.</p><p>Essentially, bits set in the <i><tt>force security mode - </tt></i> parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is set to the same value - as the <a href="smb.conf.5.html#FORCECREATEMODE" target="_top"><i><tt>force - create mode</tt></i></a> parameter. - To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.</p><p>The <i><tt>security mask</tt></i> and <i><tt>force - security mode</tt></i> parameters are applied to the change - request in that order.</p><p>For a directory Samba will perform the same operations as - described above for a file except using the parameter <i><tt> - directory security mask</tt></i> instead of <i><tt>security - mask</tt></i>, and <i><tt>force directory security mode - </tt></i> parameter instead of <i><tt>force security mode - </tt></i>.</p><p>The <i><tt>directory security mask</tt></i> parameter - by default is set to the same value as the <i><tt>directory mask - </tt></i> parameter and the <i><tt>force directory security - mode</tt></i> parameter by default is set to the same value as - the <i><tt>force directory mode</tt></i> parameter. </p><p>In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.</p><p>If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the <tt>smb.conf</tt> file in that share specific section :</p><p><i><tt>security mask = 0777</tt></i></p><p><i><tt>force security mode = 0</tt></i></p><p><i><tt>directory security mask = 0777</tt></i></p><p><i><tt>force directory security mode = 0</tt></i></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869113"></a>Interaction with the standard Samba file attribute - mapping</h2></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 - dialog and the permission bits set by the file attribute mapping. - </p><p>One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.</p><p>What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - <b>"OK"</b> to get back to the standard attributes tab - dialog, and then clicks <b>"OK"</b> on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking <b>"OK"</b> to get back to the - attributes dialog you should always hit <b>"Cancel"</b> - rather than <b>"OK"</b> to ensure that your changes - are not overridden.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="groupmapping"></a>Chapter 12. Configuring Group Mapping</h2></div><div><div class="author"><h3 class="author">Jean François Micouleau</h3></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div></div><p> -Starting with Samba 3.0 alpha 2, new group mapping functionality -is available to create associations between Windows SIDs and UNIX -groups. The <i><tt>groupmap</tt></i> subcommand included with -the <b>net</b> tool can be used to manage these associations. -</p><p> -The first immediate reason to use the group mapping on a Samba PDC, is that -the <i><tt>domain admin group</tt></i> <tt>smb.conf</tt> has been removed. -This parameter was used to give the listed users membership in the "Domain Admins" -Windows group which gave local admin rights on their workstations (in -default configurations). -</p><p> -When installing NT/W2K on a computer, the installer program creates some users -and groups. Notably the 'Administrators' group, and gives to that group some -privileges like the ability to change the date and time or to kill any process -(or close too) running on the local machine. The 'Administrator' user is a -member of the 'Administrators' group, and thus 'inherit' the 'Administrators' -group privileges. If a 'joe' user is created and become a member of the -'Administrator' group, 'joe' has exactly the same rights as 'Administrator'. -</p><p> -When a NT/W2K machine is joined to a domain, the "Domain Adminis" group of the -PDC is added to the local 'Administrators' group of the workstation. Every -member of the 'Domain Administrators' group 'inherit' the -rights of the local 'Administrators' group when logging on the workstation. -</p><p> -The following steps describe how to make samba PDC users members of the -'Domain Admins' group? -</p><div class="orderedlist"><ol type="1"><li><p>create a unix group (usually in <tt>/etc/group</tt>), - let's call it domadm</p></li><li><p>add to this group the users that must be Administrators. For example - if you want joe,john and mary, your entry in <tt>/etc/group</tt> will - look like:</p><pre class="programlisting"> - domadm:x:502:joe,john,mary - </pre></li><li><p>Map this domadm group to the "Domain Admins" group - by running the command:</p><p><tt>root# </tt><b><tt>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</tt></b></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>Now joe, john and mary are domain administrators!</p><p> -It is possible to map any arbitrary UNIX group to any Windows NT -group as well as making any UNIX group a Windows domain group. -For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a -local file or printer on a domain member machine, you would flag -that group as a domain group by running the following on the Samba PDC: -</p><p><tt>root# </tt><b><tt>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</tt></b></p><p>Be aware that the rid parmeter 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 in on you.</p><p>You can list the various groups in the mapping database by executing -<b>net groupmap list</b>. Here is an example:</p><pre class="programlisting"><tt>root# </tt>net groupmap list -System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin -Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin -Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser -Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest -</pre><p>For complete details on <b>net groupmap</b>, refer to the -net(8) man page.</p></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="printing"></a>Chapter 13. Printing Support</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Patrick Powell</h3><div class="affiliation"><div class="address"><p><tt><<a href="mailto:papowell@lprng.org">papowell@lprng.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (3 May 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869498"></a>Introduction</h2></div></div><p>Beginning with the 2.2.0 release, Samba supports -the native Windows NT printing mechanisms implemented via -MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of -Samba only supported LanMan printing calls.</p><p>The additional functionality provided by the new -SPOOLSS support includes:</p><div class="itemizedlist"><ul type="disc"><li><p>Support for downloading printer driver - files to Windows 95/98/NT/2000 clients upon demand. - </p></li><li><p>Uploading of printer drivers via the - Windows NT Add Printer Wizard (APW) or the - Imprints tool set (refer to <a href="http://imprints.sourceforge.net" target="_top">http://imprints.sourceforge.net</a>). - </p></li><li><p>Support for the native MS-RPC printing - calls such as StartDocPrinter, EnumJobs(), etc... (See - the MSDN documentation at <a href="http://msdn.microsoft.com/" target="_top">http://msdn.microsoft.com/</a> - for more information on the Win32 printing API) - </p></li><li><p>Support for NT Access Control Lists (ACL) - on printer objects</p></li><li><p>Improved support for printer queue manipulation - through the use of an internal databases for spooled job - information</p></li></ul></div><p> -There has been some initial confusion about what all this means -and whether or not it is a requirement for printer drivers to be -installed on a Samba host in order to support printing from Windows -clients. As a side note, Samba does not use these drivers in any way to process -spooled files. They are utilized entirely by the clients. -</p><p> -The following MS KB article, may be of some help if you are dealing with -Windows 2000 clients: <span class="emphasis"><em>How to Add Printers with No User -Interaction in Windows 2000</em></span> -</p><p> -<a href="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP" target="_top">http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</a> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869614"></a>Configuration</h2></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">[print$] vs. [printer$]</h3><p> -Previous versions of Samba recommended using a share named [printer$]. -This name was taken from the printer$ service created by Windows 9x -clients when a printer was shared. Windows 9x printer servers always have -a printer$ service which provides read-only access via no -password in order to support printer driver downloads. -</p><p> -However, the initial implementation allowed for a -parameter named <i><tt>printer driver location</tt></i> -to be used on a per share basis to specify the location of -the driver files associated with that printer. Another -parameter named <i><tt>printer driver</tt></i> provided -a means of defining the printer driver name to be sent to -the client. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869661"></a>Creating [print$]</h3></div></div><p> -In order to support the uploading of printer driver -files, you must first configure a file share named [print$]. -The name of this share is hard coded in Samba's internals so -the name is very important (print$ is the service used by -Windows NT print servers to provide support for printer driver -download). -</p><p>You should modify the server's smb.conf file to add the global -parameters and to create the -following file share (of course, some of the parameter values, -such as 'path' are arbitrary and should be replaced with -appropriate values for your site):</p><pre class="programlisting"> -[global] - ; members of the ntadmin group should be able - ; to add drivers and set printer properties - ; root is implicitly a 'printer admin' - printer admin = @ntadmin - -[print$] - path = /usr/local/samba/printers - guest ok = yes - browseable = yes - read only = yes - ; since this share is configured as read only, then we need - ; a 'write list'. Check the file system permissions to make - ; sure this account can copy files to the share. If this - ; is setup to a non-root account, then it should also exist - ; as a 'printer admin' - write list = @ntadmin,root -</pre><p>The <a href="smb.conf.5.html#WRITELIST" target="_top"><i><tt> -write list</tt></i></a> is used to allow administrative -level user accounts to have write access in order to update files -on the share. See the <a href="smb.conf.5.html" target="_top">smb.conf(5) -man page</a> for more information on configuring file shares.</p><p>The requirement for <a href="smb.conf.5.html#GUESTOK" target="_top"><b>guest -ok = yes</b></a> depends upon how your -site is configured. If users will be guaranteed to have -an account on the Samba host, then this is a non-issue.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Author's Note</h3><p> -The non-issue is that if all your Windows NT users are guaranteed to be -authenticated by the Samba server (such as a domain member server and the NT -user has already been validated by the Domain Controller in -order to logon to the Windows NT console), then guest access -is not necessary. Of course, in a workgroup environment where -you just want to be able to print without worrying about -silly accounts and security, then configure the share for -guest access. You'll probably want to add <a href="smb.conf.5.html#MAPTOGUEST" target="_top"><b>map to guest = Bad User -</b></a> in the [global] section as well. Make sure -you understand what this parameter does before using it -though. --jerry -</p></div><p>In order for a Windows NT print server to support -the downloading of driver files by multiple client architectures, -it must create subdirectories within the [print$] service -which correspond to each of the supported client architectures. -Samba follows this model as well.</p><p>Next create the directory tree below the [print$] share -for each architecture you wish to support.</p><p><tt> -[print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC" -</tt></p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">ATTENTION! REQUIRED PERMISSIONS</h3><p> -In order to currently add a new driver to you Samba host, -one of two conditions must hold true: -</p><div class="itemizedlist"><ul type="disc"><li><p>The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)</p></li><li><p>The account used to connect to the Samba host - must be a member of the <a href="smb.conf.5.html#PRINTERADMIN" target="_top"><i><tt>printer - admin</tt></i></a> list.</p></li></ul></div><p> -Of course, the connected account must still possess access -to add files to the subdirectories beneath [print$]. Remember -that all file shares are set to 'read only' by default. -</p></div><p> -Once you have created the required [print$] service and -associated subdirectories, simply log onto the Samba server using -a root (or <i><tt>printer admin</tt></i>) account -from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or -"My Network Places" and browse for the Samba host. Once you have located -the server, navigate to the "Printers..." folder. -You should see an initial listing of printers -that matches the printer shares defined on your Samba host. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869893"></a>Setting Drivers for Existing Printers</h3></div></div><p>The initial listing of printers in the Samba host's -Printers folder will have no real printer driver assigned -to them. This defaults to a NULL string to allow the use -of the local Add Printer Wizard on NT/2000 clients. -Attempting to view the printer properties for a printer -which has this default driver assigned will result in -the error message:</p><p> -<span class="emphasis"><em>Device settings cannot be displayed. The driver -for the specified printer is not installed, only spooler -properties will be displayed. Do you want to install the -driver now?</em></span> -</p><p> -Click "No" in the error dialog and you will be presented with -the printer properties window. The way to assign a driver to a -printer is to either -</p><div class="itemizedlist"><ul type="disc"><li><p>Use the "New Driver..." button to install - a new printer driver, or</p></li><li><p>Select a driver from the popup list of - installed drivers. Initially this list will be empty.</p></li></ul></div><p>If you wish to install printer drivers for client -operating systems other than "Windows NT x86", you will need -to use the "Sharing" tab of the printer properties dialog.</p><p>Assuming you have connected with a root account, you -will also be able modify other printer properties such as -ACLs and device settings using this dialog box.</p><p>A few closing comments for this section, it is possible -on a Windows NT print server to have printers -listed in the Printers folder which are not shared. Samba does -not make this distinction. By definition, the only printers of -which Samba is aware are those which are specified as shares in -<tt>smb.conf</tt>.</p><p>Another interesting side note is that Windows NT clients do -not use the SMB printer share, but rather can print directly -to any printer on another Windows NT host using MS-RPC. This -of course assumes that the printing client has the necessary -privileges on the remote host serving the printer. The default -permissions assigned by Windows NT to a printer gives the "Print" -permissions to the "Everyone" well-known group. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869992"></a>Support a large number of printers</h3></div></div><p>One issue that has arisen during the development -phase of Samba 2.2 is the need to support driver downloads for -100's of printers. Using the Windows NT APW is somewhat -awkward to say the list. If more than one printer are using the -same driver, the <a href="rpcclient.1.html" target="_top"><b>rpcclient's -setdriver command</b></a> can be used to set the driver -associated with an installed driver. The following is example -of how this could be accomplished:</p><p> -<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c "enumdrivers"</tt></b> -</p><pre class="programlisting"> -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] - -[Windows NT x86] -Printer Driver Info 1: - Driver Name: [HP LaserJet 4000 Series PS] - -Printer Driver Info 1: - Driver Name: [HP LaserJet 2100 Series PS] - -Printer Driver Info 1: - Driver Name: [HP LaserJet 4Si/4SiMX PS] -</pre><p> -<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c "enumprinters"</tt></b> -</p><pre class="programlisting"> -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] - flags:[0x800000] - name:[\\POGO\hp-print] - description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] - comment:[] - -</pre><p> -<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""</tt></b> -</p><pre class="programlisting"> -Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] -Successfully set hp-print to driver HP LaserJet 4000 Series PS. -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870099"></a>Adding New Printers via the Windows NT APW</h3></div></div><p> -By default, Samba offers all printer shares defined in <tt>smb.conf</tt> -in the "Printers..." folder. Also existing in this folder is the Windows NT -Add Printer Wizard icon. The APW will be show only if -</p><div class="itemizedlist"><ul type="disc"><li><p>The connected user is able to successfully - execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or <i><tt>printer admin</tt></i>). - </p></li><li><p><a href="smb.conf.5.html#SHOWADDPRINTERWIZARD" target="_top"><i><tt>show - add printer wizard = yes</tt></i></a> (the default). - </p></li></ul></div><p> -In order to be able to use the APW to successfully add a printer to a Samba -server, the <a href="smb.conf.5.html#ADDPRINTERCOMMAND" target="_top"><i><tt>add -printer command</tt></i></a> must have a defined value. The program -hook must successfully add the printer to the system (i.e. -<tt>/etc/printcap</tt> or appropriate files) and -<tt>smb.conf</tt> if necessary. -</p><p> -When using the APW from a client, if the named printer share does -not exist, <b>smbd</b> will execute the <i><tt>add printer -command</tt></i> and reparse to the <tt>smb.conf</tt> -to attempt to locate the new printer share. If the share is still not defined, -an error of "Access Denied" is returned to the client. Note that the -<i><tt>add printer program</tt></i> is executed under the context -of the connected user, not necessarily a root account. -</p><p> -There is a complementary <a href="smb.conf.5.html#DELETEPRINTERCOMMAND" target="_top"><i><tt>delete -printer command</tt></i></a> for removing entries from the "Printers..." -folder. -</p><p> -The following is an example <a href="smb.conf.5.html#ADDPRINTERCOMMAN" target="_top"><i><tt>add printer command</tt></i></a> script. It adds the appropriate entries to <tt>/etc/printcap.local</tt> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work. -</p><pre class="programlisting"> -#!/bin/sh - -# Script to insert a new printer entry into printcap.local -# -# $1, printer name, used as the descriptive name -# $2, share name, used as the printer name for Linux -# $3, port name -# $4, driver name -# $5, location, used for the device file of the printer -# $6, win9x location - -# -# Make sure we use the location that RedHat uses for local printer defs -PRINTCAP=/etc/printcap.local -DATE=`date +%Y%m%d-%H%M%S` -LP=lp -RESTART="service lpd restart" - -# Keep a copy -cp $PRINTCAP $PRINTCAP.$DATE -# Add the printer to $PRINTCAP -echo "" >> $PRINTCAP -echo "$2|$1:\\" >> $PRINTCAP -echo " :sd=/var/spool/lpd/$2:\\" >> $PRINTCAP -echo " :mx=0:ml=0:sh:\\" >> $PRINTCAP -echo " :lp=/usr/local/samba/var/print/$5.prn:" >> $PRINTCAP - -touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 -chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1 - -mkdir /var/spool/lpd/$2 -chmod 700 /var/spool/lpd/$2 -chown $LP /var/spool/lpd/$2 -#echo $1 >> "/usr/local/samba/var/print/$5.prn" -#echo $2 >> "/usr/local/samba/var/print/$5.prn" -#echo $3 >> "/usr/local/samba/var/print/$5.prn" -#echo $4 >> "/usr/local/samba/var/print/$5.prn" -#echo $5 >> "/usr/local/samba/var/print/$5.prn" -#echo $6 >> "/usr/local/samba/var/print/$5.prn" -$RESTART >> "/usr/local/samba/var/print/$5.prn" -# Not sure if this is needed -touch /usr/local/samba/lib/smb.conf -# -# You need to return a value, but I am not sure what it means. -# -echo "Done" -exit 0 -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870231"></a>Samba and Printer Ports</h3></div></div><p> -Windows NT/2000 print servers associate a port with each printer. These normally -take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the -concept of ports associated with a printer. By default, only one printer port, -named "Samba Printer Port", exists on a system. Samba does not really a port in -order to print, rather it is a requirement of Windows clients. -</p><p> -Note that Samba does not support the concept of "Printer Pooling" internally -either. This is when a logical printer is assigned to multiple ports as -a form of load balancing or fail over. -</p><p> -If you require that multiple ports be defined for some reason, -<tt>smb.conf</tt> possesses a <a href="smb.conf.5.html#ENUMPORTSCOMMAND" target="_top"><i><tt>enumports -command</tt></i></a> which can be used to define an external program -that generates a listing of ports on a system. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869233"></a>The Imprints Toolset</h2></div></div><p>The Imprints tool set provides a UNIX equivalent of the - Windows NT Add Printer Wizard. For complete information, please - refer to the Imprints web site at <a href="http://imprints.sourceforge.net/" target="_top"> - http://imprints.sourceforge.net/</a> as well as the documentation - included with the imprints source distribution. This section will - only provide a brief introduction to the features of Imprints.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869259"></a>What is Imprints?</h3></div></div><p>Imprints is a collection of tools for supporting the goals - of</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 and install printer drivers on remote Samba - and Windows NT 4 print servers.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870336"></a>Creating Printer Driver Packages</h3></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><h3 class="title"><a name="id2870355"></a>The Imprints server</h3></div></div><p>The Imprints server is really a database server that - may be queried via standard HTTP mechanisms. Each printer - entry in the database has an associated URL for the actual - downloading of the package. Each package is digitally signed - via GnuPG which can be used to verify that package downloaded - is actually the one referred in the Imprints database. It is - <span class="emphasis"><em>not</em></span> recommended that this security check - be disabled.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870379"></a>The Installation Client</h3></div></div><p>More information regarding the Imprints installation client - is available in the <tt>Imprints-Client-HOWTO.ps</tt> - file included with the imprints source package.</p><p>The Imprints installation client comes in two forms.</p><div class="itemizedlist"><ul type="disc"><li><p>a set of command line Perl scripts</p></li><li><p>a GTK+ based graphical interface to - the command line perl scripts</p></li></ul></div><p>The installation client (in both forms) provides a means - of querying the Imprints database server for a matching - list of known printer model names as well as a means to - download and install the drivers on remote Samba and Windows - NT print servers.</p><p>The basic installation process is in four steps and - perl code is wrapped around <b>smbclient</b> - and <b>rpcclient</b>.</p><pre class="programlisting"> -foreach (supported architecture for a given driver) -{ - 1. rpcclient: Get the appropriate upload directory - on the remote server - 2. smbclient: Upload the driver files - 3. rpcclient: Issues an AddPrinterDriver() MS-RPC -} - -4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually - create the printer -</pre><p>One of the problems encountered when implementing - the Imprints tool set was the name space issues between - various supported client architectures. For example, Windows - NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 calls its version of this driver "Apple - LaserWriter II NTX"</p><p>The problem is how to know what client drivers have - been uploaded for a printer. As astute reader will remember - that the Windows NT Printer Properties dialog only includes - space for one printer driver name. A quick look in the - Windows NT 4.0 system registry at</p><p><tt>HKLM\System\CurrentControlSet\Control\Print\Environment - </tt></p><p>will reveal that Windows NT always uses the NT driver - name. This is ok as Windows NT always requires that at least - the Windows NT version of the printer driver is present. - However, Samba does not have the requirement internally. - Therefore, how can you use the NT driver name if is has not - already been installed?</p><p>The way of sidestepping this limitation is to require - that all Imprints printer driver packages include both the Intel - Windows NT and 95/98 printer drivers and that NT driver is - installed first.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869340"></a>Diagnosis</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869347"></a>Introduction</h3></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 a SMB -client to a Samba server, not the other way around. For the reverse -see the examples/printing directory. -</p><p> -Ok, so you want to print to a Samba server from your PC. The first -thing you need to understand is that Samba does not actually do any -printing itself, it just acts as a middleman between your PC client -and your Unix printing subsystem. Samba receives the file from the PC -then passes the file to a external "print command". What print command -you use is up to you. -</p><p> -The whole things is controlled using options in smb.conf. The most -relevant options (which you should look up in the smb.conf man page) -are: -</p><pre class="programlisting"> - [global] - print command - send a file to a spooler - lpq command - get spool queue status - lprm command - remove a job - [printers] - path = /var/spool/lpd/samba -</pre><p> -The following are nice to know about: -</p><pre class="programlisting"> - queuepause command - stop a printer or print queue - queueresume command - start a printer or print queue -</pre><p> -Example: -</p><pre class="programlisting"> - print command = /usr/bin/lpr -r -P%p %s - lpq command = /usr/bin/lpq -P%p %s - lprm command = /usr/bin/lprm -P%p %j - queuepause command = /usr/sbin/lpc -P%p stop - queuepause command = /usr/sbin/lpc -P%p start -</pre><p> -Samba should set reasonable defaults for these depending on your -system type, but it isn't clairvoyant. It is not uncommon that you -have to tweak these for local conditions. The commands should -always have fully specified pathnames, as the smdb may not have -the correct PATH values. -</p><p> -When you send a job to Samba to be printed, it will make a temporary -copy of it in the directory specified in the [printers] section. -and it should be periodically cleaned out. The lpr -r option -requests that the temporary copy be removed after printing; If -printing fails then you might find leftover files in this directory, -and it should be periodically cleaned out. Samba used the lpq -command to determine the "job number" assigned to your print job -by the spooler. -</p><p> -The %>letter< are "macros" that get dynamically replaced with appropriate -values when they are used. The %s gets replaced with the name of the spool -file that Samba creates and the %p gets replaced with the name of the -printer. The %j gets replaced with the "job number" which comes from -the lpq output. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870552"></a>Debugging printer problems</h3></div></div><p> -One way to debug printing problems is to start by replacing these -command with shell scripts that record the arguments and the contents -of the print file. A simple example of this kind of things might -be: -</p><pre class="programlisting"> - print command = /tmp/saveprint %p %s - - #!/bin/saveprint - # we make sure that we are the right user - /usr/bin/id -p >/tmp/tmp.print - # we run the command and save the error messages - # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print -</pre><p> -Then you print a file and try removing it. You may find that the -print queue needs to be stopped in order to see the queue status -and remove the job: -</p><pre class="programlisting"> - -h4: {42} % echo hi >/tmp/hi -h4: {43} % smbclient //localhost/lw4 -added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0 -Password: -Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7] -smb: \> print /tmp/hi -putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s) -smb: \> queue -1049 3 hi-17534 -smb: \> cancel 1049 -Error cancelling job 1049 : code 0 -smb: \> cancel 1049 -Job 1049 cancelled -smb: \> queue -smb: \> exit -</pre><p> -The 'code 0' indicates that the job was removed. The comment -by the smbclient is a bit misleading on this. -You can observe the command output and then and look at the -/tmp/tmp.print file to see what the results are. You can quickly -find out if the problem is with your printing system. Often people -have problems with their /etc/printcap file or permissions on -various print queues. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870619"></a>What printers do I have?</h3></div></div><p> -You can use the 'testprns' program to check to see if the printer -name you are using is recognized by Samba. For example, you can -use: -</p><pre class="programlisting"> - testprns printer /etc/printcap -</pre><p> -Samba can get its printcap information from a file or from a program. -You can try the following to see the format of the extracted -information: -</p><pre class="programlisting"> - testprns -a printer /etc/printcap - - testprns -a printer '|/bin/cat printcap' -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870661"></a>Setting up printcap and print servers</h3></div></div><p> -You may need to set up some printcaps for your Samba system to use. -It is strongly recommended that you use the facilities provided by -the print spooler to set up queues and printcap information. -</p><p> -Samba requires either a printcap or program to deliver printcap -information. This printcap information has the format: -</p><pre class="programlisting"> - name|alias1|alias2...:option=value:... -</pre><p> -For almost all printing systems, the printer 'name' must be composed -only of alphanumeric or underscore '_' characters. Some systems also -allow hyphens ('-') as well. An alias is an alternative name for the -printer, and an alias with a space in it is used as a 'comment' -about the printer. The printcap format optionally uses a \ at the end of lines -to extend the printcap to multiple lines. -</p><p> -Here are some examples of printcap files: -</p><p> -</p><div class="orderedlist"><ol type="1"><li><p> -pr just printer name -</p></li><li><p> -pr|alias printer name and alias -</p></li><li><p> -pr|My Printer printer name, alias used as comment -</p></li><li><p> -pr:sh:\ Same as pr:sh:cm= testing - :cm= \ - testing -</p></li><li><p> -pr:sh Same as pr:sh:cm= testing - :cm= testing -</p></li></ol></div><p> -</p><p> -Samba reads the printcap information when first started. If you make -changes in the printcap information, then you must do the following: -</p><div class="orderedlist"><ol type="1"><li><p> -make sure that the print spooler is aware of these changes. -The LPRng system uses the 'lpc reread' command to do this. -</p></li><li><p> -make sure that the spool queues, etc., exist and have the -correct permissions. The LPRng system uses the 'checkpc -f' -command to do this. -</p></li><li><p> -You now should send a SIGHUP signal to the smbd server to have -it reread the printcap information. -</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870795"></a>Job sent, no output</h3></div></div><p> -This is the most frustrating part of printing. You may have sent the -job, verified that the job was forwarded, set up a wrapper around -the command to send the file, but there was no output from the printer. -</p><p> -First, check to make sure that the job REALLY is getting to the -right print queue. If you are using a BSD or LPRng print spooler, -you can temporarily stop the printing of jobs. Jobs can still be -submitted, but they will not be printed. Use: -</p><pre class="programlisting"> - lpc -Pprinter stop -</pre><p> -Now submit a print job and then use 'lpq -Pprinter' to see if the -job is in the print queue. If it is not in the print queue then -you will have to find out why it is not being accepted for printing. -</p><p> -Next, you may want to check to see what the format of the job really -was. With the assistance of the system administrator you can view -the submitted jobs files. You may be surprised to find that these -are not in what you would expect to call a printable format. -You can use the UNIX 'file' utitily to determine what the job -format actually is: -</p><pre class="programlisting"> - cd /var/spool/lpd/printer # spool directory of print jobs - ls # find job files - file dfA001myhost -</pre><p> -You should make sure that your printer supports this format OR that -your system administrator has installed a 'print filter' that will -convert the file to a format appropriate for your printer. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871344"></a>Job sent, strange output</h3></div></div><p> -Once you have the job printing, you can then start worrying about -making it print nicely. -</p><p> -The most common problem is extra pages of output: banner pages -OR blank pages at the end. -</p><p> -If you are getting banner pages, check and make sure that the -printcap option or printer option is configured for no banners. -If you have a printcap, this is the :sh (suppress header or banner -page) option. You should have the following in your printer. -</p><pre class="programlisting"> - printer: ... :sh -</pre><p> -If you have this option and are still getting banner pages, there -is a strong chance that your printer is generating them for you -automatically. You should make sure that banner printing is disabled -for the printer. This usually requires using the printer setup software -or procedures supplied by the printer manufacturer. -</p><p> -If you get an extra page of output, this could be due to problems -with your job format, or if you are generating PostScript jobs, -incorrect setting on your printer driver on the MicroSoft client. -For example, under Win95 there is a option: -</p><pre class="programlisting"> - Printers|Printer Name|(Right Click)Properties|Postscript|Advanced| -</pre><p> -that allows you to choose if a Ctrl-D is appended to all jobs. -This is a very bad thing to do, as most spooling systems will -automatically add a ^D to the end of the job if it is detected as -PostScript. The multiple ^D may cause an additional page of output. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871420"></a>Raw PostScript printed</h3></div></div><p> -This is a problem that is usually caused by either the print spooling -system putting information at the start of the print job that makes -the printer think the job is a text file, or your printer simply -does not support PostScript. You may need to enable 'Automatic -Format Detection' on your printer. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871438"></a>Advanced Printing</h3></div></div><p> -Note that you can do some pretty magic things by using your -imagination with the "print command" option and some shell scripts. -Doing print accounting is easy by passing the %U option to a print -command shell script. You could even make the print command detect -the type of output and its size and send it to an appropriate -printer. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871464"></a>Real debugging</h3></div></div><p> -If the above debug tips don't help, then maybe you need to bring in -the bug guns, system tracing. See Tracing.txt in this directory. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="CUPS-printing"></a>Chapter 14. CUPS Printing Support</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Kurt Pfeifle</h3><div class="affiliation"><div class="address"><p><tt><<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></tt></p></div></div></div></div><div><p class="pubdate"> (25 March 2003) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871008"></a>Introduction</h2></div></div><p> -The Common Unix Print System (CUPS) has become very popular, but to many it is -a very mystical tool. There is a great deal of uncertainty regarding CUPS and how -it works. The result is seen in a large number of posting on the samba mailing lists -expressing frustration when MS Windows printers appear not to work with a CUPS -backr-end. -</p><p> -This is a good time to point out how CUPS can be used and what it does. CUPS is more -than just a print spooling system - it is a complete printer management system that -complies with HTTP and IPP protocols. It can be managed remotely via a web browser -and it can print using http and ipp protocols. -</p><p> -CUPS allows to creation of RAW printers (ie: NO file format translation) as well as -SMART printers (ie: CUPS does file format conversion as required for the printer). In -many ways this gives CUPS similar capabilities to the MS Windows print monitoring -system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! -In any case, let us now move on to explore how one may configure CUPS for interfacing -with MS Windows print clients via Samba. -</p><p> -<a href="http://www.cups.org/" target="_top">CUPS</a> is a newcomer in the UNIX printing scene, -which has convinced many people upon first trial already. However, it has quite a few -new features, which make it different from other, more traditional printing systems. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871067"></a>Configuring <tt>smb.conf</tt> for CUPS</h2></div></div><p> -Printing with CUPS in the most basic <tt>smb.conf</tt> -setup in Samba-3 only needs two settings: <b>printing = cups</b> and -<b>printcap = cups</b>. While CUPS itself doesn't need a printcap -anymore, the <tt>cupsd.conf</tt> configuration file knows two directives -(example: <b>Printcap /etc/printcap</b> and <b>PrintcapFormat -BSD</b>), which control if such a file should be created for the -convenience of third party applications. Make sure it is set! For details see -<b>man cupsd.conf</b> and other CUPS-related documentation. -</p><p> -If SAMBA is compiled against libcups, then <b>printcap = cups</b> uses the -CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands -with an additional <i><tt>-oraw</tt></i> option for printing. On a Linux system, -you can use the <b>ldd</b> command to find out details (ldd may not be -present on other OS platforms, or its function may be embodied by a different command): -</p><p> -</p><pre class="programlisting">transmeta:/home/kurt # ldd `which smbd` - libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) - libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) - libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) - libdl.so.2 => /lib/libdl.so.2 (0x401e8000) - libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000) - libpam.so.0 => /lib/libpam.so.0 (0x40202000) - libc.so.6 => /lib/libc.so.6 (0x4020b000) - /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) -</pre><p> -The line "libcups.so.2 => /usr/lib/libcups.so.2 -(0x40123000)" shows there is CUPS support compiled into this version of -Samba. If this is the case, and <b>printing = cups</b> is set, then any -otherwise manually set print command in <tt>smb.conf</tt> is ignored. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871607"></a>CUPS - RAW Print Through Mode</h2></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -When used in raw print through mode is will be necessary to use the printer -vendor's drivers in each Windows client PC. -</p></div><p> -When CUPS printers are configured for RAW print-through mode operation it is the -responsibility of the Samba client to fully render the print job (file) in a format -that is suitable for direct delivery to the printer. In this case CUPS will NOT -do any print file format conversion work. -</p><p> -The CUPS files that need to be correctly set for RAW mode printers to work are: - -</p><div class="itemizedlist"><ul type="disc"><li><p><tt>/etc/cups/mime.types</tt></p></li><li><p><tt>/etc/cups/mime.convs</tt></p></li></ul></div><p> - -Both contain entries that must be uncommented to allow <span class="emphasis"><em>RAW</em></span> mode -operation. -</p><p> -Firstly, to enable CUPS based printing from Samba the following options must be -enabled in your <tt>smb.conf</tt> file [globals] section: - -</p><div class="itemizedlist"><ul type="disc"><li><p>printing = CUPS</p></li><li><p>printcap = CUPS</p></li></ul></div><p> - -When these parameters are specified the print directives in <tt>smb.conf</tt> (as well as in -samba itself) will be ignored because samba will directly interface with CUPS through -it's application program interface (API) - so long as Samba has been compiled with -CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the <span class="emphasis"><em>-oraw</em></span> -option automatically passing through. -</p><p> -Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) -on the Samba/CUPS server does *not* add any features if a file is really -printed "raw". However, if you have loaded the driver for the Windows client from -the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using -a "Foomatic" PPD, the PJL header in question is already added on the Windows client, -at the time when the driver initially generated the PostScript data and CUPS in true -"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its -printer communication backend. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.</p></div><p> -Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids -the process of determining proper treatment while in the print queue system. - -</p><div class="itemizedlist"><ul type="disc"><li><p> - Files generated by PCL drivers and directed at PCK printers get auto-typed as - <tt>application/octet-stream</tt>. Unknown file format types also - get auto-typed with this tag. - </p></li><li><p> - Files generated by a Postscript driver and directed at a Postscript printer - are auto-typed depending on the auto-detected most suitable MIME type as: - - </p><div class="itemizedlist"><ul type="circle"><li><p>* application/postscript</p></li><li><p>* application/vnd.cups-postscript</p></li></ul></div><p> - </p></li></ul></div><p> -</p><p> -"application/postscript" first goes thru the "pstops" filter (where the page counting -and accounting takes place). The outcome will be of MIME type -"application/vnd.cups-postscript". The pstopsfilter reads and uses information from -the PPD and inserts user-provided options into the PostScript file. As a consequence, -the filtered file could possibly have an unwanted PJL header. -</p><p> -"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or ">04<%". -</p><p> -"application/vnd.cups-postscript" will files which contain the string -"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the -first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS -or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced -with a "Generic PostScript driver" will just be tagged "application/postscript". -</p><p> -Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" -or "cupsomatic" will take over (depending on the printer configuration, as -determined by the PPD in use). -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -A printer queue with *no* PPD associated to it is a "raw" printer and all files -will go directly there as received by the spooler. The exeptions are file types -"application/octet-stream" which need "passthrough feature" enabled. -"Raw" queues don't do any filtering at all, they hand the file directly to the -CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, -parallel:/, serial:/, usb:/ etc.) -</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. -They are a Third Party add-on, developed at Linuxprinting.org. As such, they are -a brilliant hack to make all models (driven by Ghostscript drivers/filters in -traditional spoolers) also work via CUPS, with the same (good or bad!) quality -as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript -commandline at that stage in the CUPS filtering chain, where "normally" the native -CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" -the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, -because the associated CUPS-O-Matic-/Foomatic-PPD specifies: -</p><pre class="programlisting"> - *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic" -</pre><p> -This line persuades CUPS to hand the file to cupsomatic, once it has successfully -converted it to the MIME type "application/vnd.cups-postscript". This conversion will not -happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", -with the according changes in "/etc/cups/mime.types" in place. -</p></div><p> -CUPS is widely configurable and flexible, even regarding its filtering mechanism. -Another workaround in some situations would be to have -in "/etc/cups/mime.types" entries as follows: -</p><pre class="programlisting"> - application/postscript application/vnd.cups-raw 0 - - application/vnd.cups-postscript application/vnd.cups-raw 0 - -</pre><p> -This would prevent all Postscript files from being filtered (rather, they will go -thru the virtual "nullfilter" denoted with "-"). This could only be useful for -PS printers. If you want to print PS code on non-PS printers an entry as follows -could be useful: -</p><pre class="programlisting"> - */* application/vnd.cups-raw 0 - -</pre><p> -and would effectively send *all* files to the backend without further processing. -</p><p> -Lastly, you could have the following entry: -</p><pre class="programlisting"> - application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter -</pre><p> -You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that -parses the PostScript and removes the unwanted PJL. This would need to conform to -CUPS filter design (mainly, receive and pass the parameters printername, job-id, -username, jobtitle, copies, print options and possibly the filename). It would -be installed as world executable into "/usr/lib/cups/filters/" and will be called -by CUPS if it encounters a MIME type "application/vnd.cups-postscript". -</p><p> -CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue -"on hold". It will only be printed upon manual release by the printer operator. -This is a requirement in many "central reproduction departments", where a few -operators manage the jobs of hundreds of users on some big machine, where no -user is allowed to have direct access. (The operators often need to load the -proper paper type before running the 10.000 page job requested by marketing -for the mailing, etc.). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871091"></a>CUPS as a network PostScript RIP</h2></div></div><p> -This is the configuration where CUPS drivers are working on server, and where the -Adobe PostScript driver with CUPS-PPDs is downloaded to clients. -</p><p> -CUPS is perfectly able to use PPD files (PostScript -Printer Descriptions). PPDs can control all print device options. They -are usually provided by the manufacturer -- if you own a PostSript printer, -that is. PPD files are always a component of PostScript printer drivers on MS -Windows or Apple Mac OS systems. They are ASCII files containing -user-selectable print options, mapped to appropriate PostScript, PCL or PJL -commands for the target printer. Printer driver GUI dialogs translate these -options "on-the-fly" into buttons and drop-down lists for the user to -select. -</p><p> -CUPS can load, without any conversions, the PPD file from -any Windows (NT is recommended) PostScript driver and handle the options. -There is a web browser interface to the print options (select -http://localhost:631/printers/ and click on one "Configure Printer" button -to see it), a commandline interface (see <b>man lpoptions</b> or -try if you have <b>lphelp</b> on your system) plus some different GUI frontends on Linux -UNIX, which can present PPD options to the users. PPD options are normally -meant to become evaluated by the PostScript RIP on the real PostScript -printer. -</p><p> -CUPS doesn't stop at "real" PostScript printers in its -usage of PPDs. The CUPS developers have extended the PPD concept, to also -describe available device and driver options for non-PostScript printers -through CUPS-PPDs. -</p><p> -This is logical, as CUPS includes a fully featured -PostScript interpreter (RIP). This RIP is based on Ghostscript. It can -process all received PostScript (and additionally many other file formats) -from clients. All CUPS-PPDs geared to non-PostScript printers contain an -additional line, starting with the keyword <i><tt>*cupsFilter</tt></i>. -This line -tells the CUPS print system which printer-specific filter to use for the -interpretation of the accompanying PostScript. Thus CUPS lets all its -printers appear as PostScript devices to its clients, because it can act as a -PostScript RIP for those printers, processing the received PostScript code -into a proper raster print format. -</p><p> -CUPS-PPDs can also be used on Windows-Clients, on top of a -PostScript driver (recommended is the Adobe one). -</p><p> -This feature enables CUPS to do a few tricks no other -spooler can do: -</p><div class="itemizedlist"><ul type="disc"><li><p>act as a networked PostScript RIP (Raster Image Processor), handling - printfiles from all client platforms in a uniform way;</p></li><li><p>act as a central accounting and billing server, as all files are passed - through the <b>pstops</b> Filter and are therefor logged in - the CUPS <tt>page_log</tt>. - <span class="emphasis"><em>NOTE: </em></span>this - can not happen with "raw" print jobs, which always remain unfiltered - per definition;</p></li><li><p>enable clients to consolidate on a single PostScript driver, even for - many different target printers.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872272"></a>Windows Terminal Servers (WTS) as CUPS clients</h2></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. In many cases, in an attempt to overcome this problem, site -administrators have resorted to restrict the allowed drivers installed on -their WTS to one generic PCL- and one PostScript driver. This however -restricts the clients in the amount of printer options available for them -- -often they can't get out more then simplex prints from one standard paper -tray, while their devices could do much better, if driven by a different -driver! -</p><p> -Using an Adobe PostScript driver, enabled with a CUPS-PPD, -seems to be a very elegant way to overcome all these shortcomings. The -PostScript driver is not known to cause major stability problems on WTS (even -if used with many different PPDs). The clients will be able to (again) chose -paper trays, duplex printing and other settings. However, there is a certain -price for this too: a CUPS server acting as a PostScript RIP for its clients -requires more CPU and RAM than just to act as a "raw spooling" device. Plus, -this setup is not yet widely tested, although the first feedbacks look very -promising... -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872314"></a>Setting up CUPS for driver download</h2></div></div><p> -The <b>cupsadsmb</b> utility (shipped with all current -CUPS versions) makes the sharing of any (or all) installed CUPS printers very -easy. Prior to using it, you need the following settings in <tt>smb.conf</tt>: -</p><pre class="programlisting">[global] - load printers = yes - printing = cups - printcap name = cups - - [printers] - comment = All Printers - path = /var/spool/samba - browseable = no - public = yes - guest ok = yes - writable = no - printable = yes - printer admin = root - - [print$] - comment = Printer Drivers - path = /etc/samba/drivers - browseable = yes - guest ok = no - read only = yes - write list = root - </pre><p> -For licensing reasons the necessary files of the Adobe -Postscript driver can not be distributed with either Samba or CUPS. You need -to download them yourself from the Adobe website. Once extracted, create a -<tt>drivers</tt> directory in the CUPS data directory (usually -<tt>/usr/share/cups/</tt>). Copy the Adobe files using -UPPERCASE filenames, to this directory as follows: -</p><pre class="programlisting"> - ADFONTS.MFM - ADOBEPS4.DRV - ADOBEPS4.HLP - ADOBEPS5.DLL - ADOBEPSU.DLL - ADOBEPSU.HLP - DEFPRTR2.PPD - ICONLIB.DLL - </pre><p> -Users of the ESP Print Pro software are able to install -their "Samba Drivers" package for this purpose with no problem. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872401"></a>Sources of CUPS drivers / PPDs</h2></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 1.000 non-PostScript models. -</p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://wwwl.easysw.com/printpro/" target="_top">ESP PrintPro - (http://wwwl.easysw.com/printpro/)</a> - (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for - successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris, - SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it - is written by the CUPS developers themselves and its sales help finance - the further development of CUPS, as they feed their creators)</p></li><li><p>the <a href="http://gimp-print.sourceforge.net/" target="_top">Gimp-Print-Project - (http://gimp-print.sourceforge.net/)</a> - (GPL, Free Software) provides around 120 PPDs (supporting nearly 300 - printers, many driven to photo quality output), to be used alongside the - Gimp-Print CUPS filters;</p></li><li><p><a href="http://www.turboprint.com/" target="_top">TurboPrint - (http://www.turboprint.com/)</a> - (Shareware, non-Freee) supports roughly the same amount of printers in - excellent quality;</p></li><li><p><a href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">OMNI - (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</a> - (LPGL, Free) is a package made by IBM, now containing support for more - than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow - ported over to Linux (CUPS support is in a Beta-stage at present);</p></li><li><p><a href="http://hpinkjet.sourceforge.net/" target="_top">HPIJS - (http://hpinkjet.sourceforge.net/)</a> - (BSD-style licnes, Free) supports around 120 of HP's own printers and is - also providing excellent print quality now;</p></li><li><p><a href="http://www.linuxprinting.org/" target="_top">Foomatic/cupsomatic (http://www.linuxprinting.org/)</a> - (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every - Ghostscript filter known to the world, now usable with CUPS.</p></li></ul></div><p> -<span class="emphasis"><em>NOTE: </em></span>the cupsomatic trick from Linuxprinting.org is -working different from the other drivers. While the other drivers take the -generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as -their input, cupsomatic "kidnaps" the PostScript inside CUPS, before -RIP-ping, deviates it to an external Ghostscript installation (which now -becomes the RIP) and gives it back to a CUPS backend once Ghostscript is -finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster -PostScript RIP function again inside a system-wide Ghostscript -installation rather than in "their own" pstoraster filter. (This -CUPS-enabling Ghostscript version may be installed either as a -patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). -However, this will not change the cupsomatic approach of guiding the printjob -along a different path through the filtering system than the standard CUPS -way... -</p><p> -Once you installed a printer inside CUPS with one of the -recommended methods (the lpadmin command, the web browser interface or one of -the available GUI wizards), you can use <b>cupsaddsmb</b> to share the -printer via Samba. <b>cupsaddsmb</b> prepares the driver files for -comfortable client download and installation upon their first contact with -this printer share. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872566"></a><b>cupsaddsmb</b></h3></div></div><p> -The <b>cupsaddsmb</b> command copies the needed files -for convenient Windows client installations from the previously prepared CUPS -data directory to your [print$] share. Additionally, the PPD -associated with this printer is copied from <tt>/etc/cups/ppd/</tt> to -[print$]. -</p><pre class="programlisting"> -<tt>root# </tt> <b>cupsaddsmb -U root infotec_IS2027</b> -Password for root required to access localhost via -SAMBA: <b><tt>[type in password 'secret']</tt></b> -</pre><p> -To share all printers and drivers, use the <i><tt>-a</tt></i> -parameter instead of a printer name. -</p><p> -Probably you want to see what's going on. Use the -<i><tt>-v</tt></i> parameter to get a more verbose output: -</p><p> -Probably you want to see what's going on. Use the -<i><tt>-v</tt></i> parameter to get a more verbose output: -</p><pre class="programlisting"> -Note: The following line shave been wrapped so that information is not lost. - -<tt>root# </tt> cupsaddsmb -v -U root infotec_IS2027 - Password for root required to access localhost via SAMBA: - Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put - /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put - /usr/share/cups/drivers/ - ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr - W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP' - added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0 - added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0 - added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0 - Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs] - NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86 - putting file /var/spool/cups/tmp/3cd1cc66376c0 as - \W32X86/infotec_IS2027.PPD (17394.6 kb/s) (average 17395.2 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS5.DLL as - \W32X86/ADOBEPS5.DLL (10877.4 kb/s) (average 11343.0 kb/s) - putting file /usr/share/cups/drivers/ADOBEPSU.DLL as - \W32X86/ADOBEPSU.DLL (5095.2 kb/s) (average 9260.4 kb/s) - putting file /usr/share/cups/drivers/ADOBEPSU.HLP as - \W32X86/ADOBEPSU.HLP (8828.7 kb/s) (average 9247.1 kb/s) - - Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put - /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put - /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put - /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put - /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put - /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put - /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put - /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;' - added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0 - added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0 - added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0 - Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs] - NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40 - putting file /var/spool/cups/tmp/3cd1cc66376c0 as - \WIN40/infotec_IS2027.PPD (26091.5 kb/s) (average 26092.8 kb/s) - putting file /usr/share/cups/drivers/ADFONTS.MFM as - \WIN40/ADFONTS.MFM (11241.6 kb/s) (average 11812.9 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS4.DRV as - \WIN40/ADOBEPS4.DRV (16640.6 kb/s) (average 14679.3 kb/s) - putting file /usr/share/cups/drivers/ADOBEPS4.HLP as - \WIN40/ADOBEPS4.HLP (11285.6 kb/s) (average 14281.5 kb/s) - putting file /usr/share/cups/drivers/DEFPRTR2.PPD as - \WIN40/DEFPRTR2.PPD (823.5 kb/s) (average 12944.0 kb/s) - putting file /usr/share/cups/drivers/ICONLIB.DLL as - \WIN40/ICONLIB.DLL (19226.2 kb/s) (average 13169.7 kb/s) - putting file /usr/share/cups/drivers/PSMON.DLL as - \WIN40/PSMON.DLL (18666.1 kb/s) (average 13266.7 kb/s) - - Running command: rpcclient localhost -N -U'root%secret' - -c 'adddriver "Windows NT x86" - "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL: - ADOBEPSU.HLP:NULL:RAW:NULL"' - cmd = adddriver "Windows NT x86" - "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL: - ADOBEPSU.HLP:NULL:RAW:NULL" - Printer Driver infotec_IS2027 successfully installed. - - Running command: rpcclient localhost -N -U'root%secret' - -c 'adddriver "Windows 4.0" - "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL: - ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"' - cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV: - infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW: - ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL" - Printer Driver infotec_IS2027 successfully installed. - - Running command: rpcclient localhost -N -U'root%secret' - -c 'setdriver infotec_IS2027 infotec_IS2027' - cmd = setdriver infotec_IS2027 infotec_IS2027 - Succesfully set infotec_IS2027 to driver infotec_IS2027. - - <tt>root# </tt> -</pre><p> -If you look closely, you'll discover your root password was transfered unencrypted over -the wire, so beware! Also, if you look further her, you'll discover error messages like -<tt>NT_STATUS_OBJECT_NAME_COLLISION</tt> in between. They occur, because -the directories <tt>WIN40</tt> and <tt>W32X86</tt> already -existed in the [print$] driver download share (from a previous driver -installation). They are harmless here. -</p><p> -Now your printer is prepared for the clients to use. From -a client, browse to the CUPS/Samba server, open the "Printers" -share, right-click on this printer and select "Install..." or -"Connect..." (depending on the Windows version you use). Now their -should be a new printer in your client's local "Printers" folder, -named (in my case) "infotec_IS2027 on kdebitshop" -</p><p> -<span class="emphasis"><em>NOTE: </em></span> -<b>cupsaddsmb</b> will only reliably work i -with CUPS version 1.1.15 or higher -and Samba from 2.2.4. If it doesn't work, or if the automatic printer -driver download to the clients doesn't succeed, you can still manually -install the CUPS printer PPD on top of the Adobe PostScript driver on -clients and then point the client's printer queue to the Samba printer -share for connection, should you desire to use the CUPS networked -PostScript RIP functions. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872915"></a>The CUPS Filter Chains</h2></div></div><p> -The following diagrams reveal how CUPS handles print jobs. -</p><pre class="programlisting"> -######################################################################### -# -# CUPS in and of itself has this (general) filter chain (CAPITAL -# letters are FILE-FORMATS or MIME types, other are filters (this is -# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro): -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT -# | -# | -# V -# pstoraster # as shipped with CUPS, independent from any Ghostscipt -# | # installation on the system -# | (= "postscipt interpreter") -# | -# V -# APPLICATION/VND.CUPS-RASTER -# | -# | -# V -# rasterto<i><tt>something</tt></i> (f.e. Gimp-Print filters may be plugged in here) -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# -# ESP PrintPro has some enhanced "rasterto<i><tt>something</tt></i>" filters as compared to -# CUPS, and also a somewhat improved "pstoraster" filter. -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -######################################################################### -</pre><pre class="programlisting"> -######################################################################### -# -# This is how "cupsomatic" comes into play: -# ========================================= -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+ -# | | -# | V -# V cupsomatic -# pstoraster (constructs complicated -# | (= "postscipt interpreter") Ghostscript commandline -# | to let the file be -# V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<i><tt>s.th.</tt></i>" -# | call...) -# | | -# V | -# rasterto<i><tt>something</tt></i> V -# | (= "raster driver") +-------------------------+ -# | | Ghostscript at work.... | -# V | | -# SOMETHING-DEVICE-SPECIFIC *-------------------------+ -# | | -# | | -# V | -# backend >------------------------------------+ -# | -# | -# V -# THE PRINTER -# -# -# Note, that cupsomatic "kidnaps" the printfile after the -# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through -# the CUPS-external, systemwide Ghostscript installation, bypassing the -# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers -# "rasterto<i><tt>something</tt></i>", and hands the rasterized file directly to the CUPS -# backend... -# -# cupsomatic is not made by the CUPS developers. It is an independent -# contribution to printing development, made by people from -# Linuxprinting.org. (see also http://www.cups.org/cups-help.html) -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -######################################################################### -</pre><pre class="programlisting"> -######################################################################### -# -# And this is how it works for ESP PrintPro from 4.3: -# =================================================== -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT -# | -# | -# V -# gsrip -# | (= "postscipt interpreter") -# | -# V -# APPLICATION/VND.CUPS-RASTER -# | -# | -# V -# rasterto<i><tt>something</tt></i> (f.e. Gimp-Print filters may be plugged in here) -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -######################################################################### -</pre><pre class="programlisting"> -######################################################################### -# -# This is how "cupsomatic" would come into play with ESP PrintPro: -# ================================================================ -# -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+ -# | | -# | V -# V cupsomatic -# gsrip (constructs complicated -# | (= "postscipt interpreter") Ghostscript commandline -# | to let the file be -# V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<i><tt>s.th.</tt></i>" -# | call...) -# | | -# V | -# rasterto<i><tt>something</tt></i> V -# | (= "raster driver") +-------------------------+ -# | | Ghostscript at work.... | -# V | | -# SOMETHING-DEVICE-SPECIFIC *-------------------------+ -# | | -# | | -# V | -# backend >------------------------------------+ -# | -# | -# V -# THE PRINTER -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -######################################################################### -</pre><pre class="programlisting"> -######################################################################### -# -# And this is how it works for CUPS from 1.1.15: -# ============================================== -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT-----+ -# | -# +------------------v------------------------------+ -# | Ghostscript | -# | at work... | -# | (with | -# | "-sDEVICE=cups") | -# | | -# | (= "postscipt interpreter") | -# | | -# +------------------v------------------------------+ -# | -# | -# APPLICATION/VND.CUPS-RASTER >-------+ -# | -# | -# V -# rasterto<i><tt>something</tt></i> -# | (= "raster driver") -# | -# V -# SOMETHING-DEVICE-SPECIFIC -# | -# | -# V -# backend -# -# -# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to -# Ghostscript. GNU Ghostscript needs to be patched to handle the -# CUPS requirement; ESP Ghostscript has this builtin. In any case, -# "gs -h" needs to show up a "cups" device. pstoraster is now a -# calling an appropriate "gs -sDEVICE=cups..." commandline to do -# the job. It will output "application/vnd.cup-raster", which will -# be finally processed by a CUPS raster driver "rasterto<i><tt>something</tt></i>" -# Note the difference to "cupsomatic", which will *not* output -# CUPS-raster, but a final version of the printfile, ready to be -# sent to the printer. cupsomatic also doesn't use the "cups" -# devicemode in Ghostscript, but one of the classical devicemodes.... -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -######################################################################### -</pre><pre class="programlisting"> -######################################################################### -# -# And this is how it works for CUPS from 1.1.15, with cupsomatic included: -# ======================================================================== -# -# <i><tt>SOMETHNG</tt></i>-FILEFORMAT -# | -# | -# V -# <i><tt>something</tt></i>tops -# | -# | -# V -# APPLICATION/POSTSCRIPT -# | -# | -# V -# pstops -# | -# | -# V -# APPLICATION/VND.CUPS-POSTSCRIPT-----+ -# | -# +------------------v------------------------------+ -# | Ghostscript . Ghostscript at work.... | -# | at work... . (with "-sDEVICE= | -# | (with . <i><tt>s.th.</tt></i>" | -# | "-sDEVICE=cups") . | -# | . | -# | (CUPS standard) . (cupsomatic) | -# | . | -# | (= "postscript interpreter") | -# | . | -# +------------------v--------------v---------------+ -# | | -# | | -# APPLICATION/VND.CUPS-RASTER >-------+ | -# | | -# | | -# V | -# rasterto<i><tt>something</tt></i> | -# | (= "raster driver") | -# | | -# V | -# SOMETHING-DEVICE-SPECIFIC >------------------------+ -# | -# | -# V -# backend -# -# -# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted. -# -########################################################################## -</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2873302"></a>CUPS Print Drivers and Devices</h2></div></div><p> -CUPS ships with good support for HP LaserJet type printers. You can install -the driver as follows: - -</p><div class="itemizedlist"><ul type="disc"><li><p> - lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd - </p></li></ul></div><p> - -(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository -for not-yet-installed-PPDs, which CUPS typically stores in -<tt>/usr/share/cups/model</tt>. Alternatively, you may use -"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd"). -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2873339"></a>Further printing steps</h3></div></div><p> -Always also consult the database on linuxprinting.org for all recommendations -about which driver is best used for each printer: -</p><p><a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a></p><p> -There select your model and click on "Show". You'll arrive at a page listing -all drivers working with your model. There will always be *one* -<span class="emphasis"><em>recommended</em></span> one. Try this one first. In your case -("HP LaserJet 4 Plus"), you'll arrive here: -</p><p><a href="http://www.linuxprinting.org/show_printer.cgi?recnum=75104" target="_top">http://www.linuxprinting.org/show_printer.cgi?recnum=75104</a></p><p> -The recommended driver is "ljet4". It has a link to the page for the ljet4 -driver too: -</p><p><a href="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4" target="_top">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</a></p><p> -On the driver's page, you'll find important and detailed info about how to use -that driver within the various available spoolers. You can generate a PPD for -CUPS. The PPD contains all the info about how to use your model and the driver; -this is, once installed, working transparently for the user -- you'll only -need to choose resolution, paper size etc. from the web-based menu or from -the print dialog GUI or from the commandline... -</p><p> -On the driver's page, choose to use the "PPD-O-Matic" online PPD generator -program. Select your model and click "Generate PPD file". When you safe the -appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt -line endings and tabs), but use "Save as..." in your browser's menu. Save it -at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd" -</p><p> -Then install the printer: -</p><pre class="programlisting"> - "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \ - -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd" -</pre><p> -Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need -a special "CUPS filter" named "cupsomatic". Get the latest version of -"cupsomatic" from: -</p><p><a href="http://www.linuxprinting.org/cupsomatic" target="_top">http://www.linuxprinting.org/cupsomatic</a></p><p> -This needs to be copied to <tt>/usr/lib/cups/filter/cupsomatic</tt> -and be made world executable. This filter is needed to read and act upon the -specially encoded Foomatic comments, embedded in the printfile, which in turn -are used to construct (transparently for you, the user) the complicated -ghostscript command line needed for your printer/driver combo. -</p><p> -You can have a look at all the options for the Ghostscript commandline supported -by your printer and the ljet4 driver by going to the section "Execution details", -selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". -This will bring up this web page: -</p><p><a href="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show%2Bexecution%2Bdetails" target="_top">http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details</a></p><p> -The ingenious thing is that the database is kept current. If there -is a bug fix and an improvement somewhere in the database, you will -always get the most current and stable and feature-rich driver by following -the steps described above. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Till Kamppeter from MandrakeSoft is doing an excellent job here that too few -people are aware of. (So if you use it often, please send him a note showing -your appreciation).</p></div><p> -The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it. -</p><p> -"cupsomatic" is documented here: -</p><p><a href="http://www.linuxprinting.org/cups-doc.html" target="_top">http://www.linuxprinting.org/cups-doc.html</a></p><p> -More printing tutorial info may be found here: -</p><p><a href="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/" target="_top">http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</a></p><p> -Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now -approaching the "all-time high" number of 1.000 for the supported models) -are using a special filtering chain involving Ghostscript, as described -in this document. -</p><p> -Summary - You need: -</p><p> -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A "foomatic+<i><tt>something</tt></i>" PPD is not enough to print with CUPS (but it is *one* important component)</td></tr><tr><td>The "cupsomatic" filter script (Perl) in <tt>/usr/lib/cups/filters/</tt></td></tr><tr><td>Perl to make cupsomatic run</td></tr><tr><td>Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</td></tr><tr><td>Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</td></tr></table><p> -</p><p> -In the case of the "hpijs" driver, you need a Ghostscript version, which -has "ijs" amongst its supported devices in "gs -h". In the case of -"hpijs+foomatic", a valid ghostscript commandline would be reading like this: -</p><pre class="programlisting"> - gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \ - -sIjsServer=hpijs<i><tt>PageSize</tt></i> -dDuplex=<i><tt>Duplex</tt></i> <i><tt>Model</tt></i> \ - -r<i><tt>Resolution</tt></i>,PS:MediaPosition=<i><tt>InputSlot</tt></i> -dIjsUseOutputFD \ - -sOutputFile=- - -</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) -you don't need to remember this. You can choose the available print options -thru a GUI print command (like "glp" from ESP's commercially supported -PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent -"xpp") or the CUPS web interface via human-readable drop-down selection -menus. -</p></div><p> -If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software -Products, the makers of CUPS, downloadable from -<a href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>, -co-maintained by the developers of linuxprinting.org), you are guaranteed to -have in use the most uptodate, bug-fixed, enhanced and stable version of a Free -Ghostscript. It contains support for ~300 devices, whereas plain vanilla -GNU Ghostscript 7.05 only has ~200. -</p><p> -If you print only one CUPS test page, from the web interface and when you try to -print a windows test page, it acts like the job was never sent: - -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Can you print "standard" jobs from the CUPS machine?</td></tr><tr><td>Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</td></tr><tr><td><span class="emphasis"><em>Most important:</em></span> What kind of printer driver are you using on the Windows clients?</td></tr></table><p> - -You can try to get a more detailed debugging info by setting "LogLevel debug" in -<tt>/etc/cups/cupsd.conf</tt>, re-start cupsd and investigate <tt>/var/log/cups/error_log</tt> -for the whereabouts of your Windows-originating printjobs: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</td></tr><tr><td>are there "filter" available for this MIME type?</td></tr><tr><td>are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2873758"></a>Limiting the number of pages users can print</h2></div></div><p> -The feature you want is dependent on the real print subsystem you're using. -Samba's part is always to receive the job files from the clients (filtered -*or* unfiltered) and hand it over to this printing subsystem. -</p><p> -Of course one could "hack" things with one's own scripts. -</p><p> -But there is CUPS (Common Unix Printing System). CUPS supports "quotas". -Quotas can be based on sizes of jobs or on the number of pages or both, -and are spanning any time period you want. -</p><p> -This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter": -</p><pre class="programlisting"> - lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \ - -o job-page-limit=100 -</pre><p> -This would limit every single user to print 100 pages or 1024 KB of -data (whichever comes first) within the last 604.800 seconds ( = 1 week). -</p><p> -For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, -otherwise it uses a "dummy" count of "1". Some printfiles don't pass it -(eg: image files) but then those are mostly 1 page jobs anyway. This also means, -proprietary drivers for the target printer running on the client computers and -CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too! -</p><p> -You need to send PostScript from the clients (i.e. run a PostScript driver there) -for having the chance to get accounting done. If the printer is a non-PostScript model, -you need to let CUPS do the job to convert the file to a print-ready format for the -target printer. This will be working for currently ~1.000 different printer models, see -</p><pre class="programlisting"> - http://www.linuxprinting.org/printer_list.cgi -</pre><p> -Before CUPS-1.1.16 your only option was to use the Adobe PostScript -Driver on the Windows clients. The output of this driver was not always -passed thru the "pstops" filter on the CUPS/Samba side, and therefor was -not counted correctly (the reason is that it often --- depending on the -"PPD" being used --- did write a "PJL"-header in front of the real -PostScript which made CUPS to skip the pstops and go directy to -the "pstoraster" stage). -</p><p> -From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver -for Windows NT/2K/XP clients" (it is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). -It is *not* working for Win9x/ME clients. But it: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>it guarantees to not write an PJL-header</td></tr><tr><td>it guarantees to still read and support all PJL-options named in the driver PPD with its own means</td></tr><tr><td>it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</td></tr><tr><td>it guarantees to page-count correctly the printfile</td></tr></table><p> -You can read more about the setup of this combination in the -manpage for "cupsaddsmb" (only present with CUPS installed, only -current with CUPS 1.1.16). -</p><p> -These are the items CUPS logs in the "page_log" for every single *page* of a job: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Printer name</td></tr><tr><td>User name</td></tr><tr><td>Job ID</td></tr><tr><td>Time of printing</td></tr><tr><td>the page number</td></tr><tr><td>the number of copies</td></tr><tr><td>a billing info string (optional)</td></tr></table><p> -</p><p> -Here is an extract of my CUPS server's page_log file to illustrate -the format and included items: -</p><p><tt> - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing -</tt></p><p> -This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job -printed in 2 copies and billed to "#marketing"... -</p><p> -What flaws or shortcomings are there? -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>the ones named above</td></tr><tr><td> - CUPS really counts the job pages being *processsed in software* - (going thru the "RIP") rather than the physical sheets successfully - leaving the printing device -- if there is a jam while printing - the 5th sheet out of 1000 and the job is aborted by the printer, - the "page count" will still show the figure of 1000 for that job - </td></tr><tr><td> - all quotas are the same for all users (no flexibility to give the - boss a higher quota than the clerk) no support for groups - </td></tr><tr><td> - no means to read out the current balance or "used-up" number of current quota - </td></tr><tr><td> - a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job - </td></tr><tr><td> - a user being denied a job because of a filled-up quota doesn't get a meaningful - error message from CUPS other than "client-error-not-possible". - </td></tr></table><p> -But this is the best system out there currently. And there are -huge improvements under development: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>page counting will go into the "backends" (these talk - directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</td></tr><tr><td>quotas will be handled more flexibly</td></tr><tr><td>probably there will be support for users to inquire their "accounts" in advance</td></tr><tr><td>probably there will be support for some other tools around this topic</td></tr></table><p> -Other than the current stage of the CUPS development, I don't -know any other ready-to-use tool which you could consider. -</p><p> -You can download the driver files from -<a href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>. -It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 -Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to -download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal -the files: -</p><p> -<tt> - cups-samba.install - cups-samba.license - cups-samba.readme - cups-samba.remove - cups-samba.ss -</tt> -</p><p> -These have been packaged with the ESP meta packager software "EPM". The -*.install and *.remove files are simple shell script, which untars the -*.ss (which is nothing else than a tar-archive) and puts its contents -into <tt>/usr/share/cups/drivers/</tt>. Its contents are 3 files: -</p><p> -<tt> - cupsdrvr.dll - cupsui.dll - cups.hlp -</tt> -</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p> -Due to a bug one CUPS release puts the <tt>cups.hlp</tt> -into <tt>/usr/share/drivers/</tt> instead of -<tt>/usr/share/cups/drivers/</tt>. To work around this, copy/move -the file after running the "./cups-samba.install" script manually to the right place: -</p><p> -<b><tt> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ -</tt></b> - </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -This new CUPS PostScript driver is currently binary-only, but free -no source code is provided (yet). The reason is this: it has -been developed with the help of the Microsoft Driver Developer Kit (DDK) -and compiled with Microsoft Visual Studio 6. It is not clear to the driver -developers if they are allowed to distribute the whole of the source code -as Free Software. However, they will likely release the "diff" in source -code under the GPL, so anybody with a license of Visual Studio and a DDK -will be able to compile for him/herself. -</p><p> -Once you have run the install script (and possibly manually moved the -"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be -put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" -and contains a subdir tree with WIN40 and W32X86 branches), by running -"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to -put root into the smbpasswd file by running "smbpasswd" should you run -this whole procedure for the first time.] Once the driver files are in the -[print$] share, they are ready to be downloaded and installed by the -Win NT/2k/XP clients. -</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - Win 9x/ME clients won't work with this driver. For these you'd - still need to use the ADOBE*.* drivers as previously. - </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. - The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). - </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - Should your Win clients have had the old ADOBE*.* files and the - Adobe PostScript drivers installed, the download and installation - of the new CUPS PostScript driver for Windows NT/2k/XP will fail - at first. - </p><p> - It is not enough to "delete" the printer (as the driver files - will still be kept by the clients and re-used if you try to - re-install the printer). To really get rid of the Adobe driver - files on the clients, open the "Printers" folder (possibly via - "Start --> Settings --> Control Panel --> Printers"), right-click - onto the folder background and select "Server Properties". A - new dialog opens; select the "Drivers" tab; on the list select - the driver you want to delete and click on the "Delete" button. - (This will only work if there is no single printer left which - uses that particular driver -- you need to "delete" all printers - using this driver in the "Printers" folder first.) - </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - Once you have successfully downloaded the CUPS PostScript driver - to a client, you can easily switch all printers to this one - by proceeding as described elsewhere in the "Samba HOWTO - Collection" to change a driver for an existing printer. - </p></div><p> -What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" -as compared to the Adobe drivers? -</p><p> -</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p> - no hassle with the Adobe EULA - </p></td></tr><tr><td><p> - no hassle with the question "where do I get the ADOBE*.* driver files from?" - </p></td></tr><tr><td><p> - the Adobe drivers (depending on the printer PPD associated with them) - often put a PJL header in front of the core PostScript part of the print - file (thus the file starts with "<i><tt>1B</tt></i>%-12345X" - or "<i><tt>escape</tt></i>%-12345X" - instead of "%!PS"). This leads to the CUPS daemon autotyping the - arriving file as a print-ready file, not requiring a pass thru the - "pstops" filter (to speak more technical, it is not regarded as the - generic MIME type "application/postscript", but as the more special - MIME type "application/cups.vnd-postscript"), which therefore also - leads to the page accounting in "/var/log/cups/page_log" not receiving - the exact mumber of pages; instead the dummy page number of "1" is - logged in a standard setup) - </p></td></tr><tr><td><p> - the Adobe driver has more options to "mis-configure" the PostScript - generated by it (like setting it inadvertedly to "Optimize for Speed", - instead of "Optimize for Portability", which could lead to CUPS being - unable to process it) - </p></td></tr><tr><td><p> - the CUPS PostScript driver output sent by Windows clients to the CUPS - server will be guaranteed to be auto-typed as generic MIME type - "application/postscript", thusly passing thru the CUPS "pstops" filter - and logging the correct number of pages in the page_log for accounting - and quota purposes - </p></td></tr><tr><td><p> - the CUPS PostScript driver supports the sending of additional print - options by the Win NT/2k/XP clients, such as naming the CUPS standard - banner pages (or the custom ones, should they be installed at the time - of driver download), using the CUPS "page-label" option, setting a - job-priority and setting the scheduled time of printing (with the option - to support additional useful IPP job attributes in the future). - </p></td></tr><tr><td><p> - the CUPS PostScript driver supports the inclusion of the new - "*cupsJobTicket" comments at the beginnig of the PostScript file (which - could be used in the future for all sort of beneficial extensions on - the CUPS side, but which will not disturb any other application as those - will regard it as a comment and simply ignore it). - </p></td></tr><tr><td><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></td></tr></table><p> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874367"></a>Advanced Postscript Printing from MS Windows</h2></div></div><p> -Let the Windows Clients use a PostScript driver to deliver poistscript to -the samba print server (just like any Linux or Unix Client would also use -PostScript to send to the server) -</p><p> -Make the Unix printing subsystem to which Samba sends the job convert the -incoming PostScript files to the native print format of the target printers -(would be PCL if you have an HP printer) -</p><p> -Now if you are afraid that this would just mean using a *Generic* PostScript -driver for the clients that has no Simplex/Duplex selection, and no paper tray -choice, but you need them to be able to set up print jobs, with all the bells -and whistles of your printers:- -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Not possible with traditional spooling systems</td></tr><tr><td> - But perfectly supported by CUPS (which uses "PPD" files to - describe how to control the print options for PostScript and - non-PostScript devices alike... - </td></tr></table><p> -CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript -drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use -them to setup the job to their liking and CUPS will use the received job options -to make the (PCL-, ESC/P- or PostScript-) printer behave as required. -</p><p> -If you want to have the additional benefit of page count logging and accounting -then the CUPS PostScript driver is the best choice (better than the Adobe one). -</p><p> -If you want to make the drivers downloadable for the clients then "cupsaddsmb" is -your friend. It will setup the [print$] share on the Samba host to be ready to serve -the clients for a "point and print" driver installation. -</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>What strings are attached?</p></div><p> -There are some. But, given the sheer CPU power you can buy nowadays, -these can be overcome easily. The strings: -</p><p> -Well, if the CUPS/Samba side will have to print to many printers serving many users, -you probably will need to set up a second server (which can do automatic load balancing -with the first one, plus a degree of fail-over mechanism). Converting the incoming -PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work -of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM -than for the mere "raw spooling" task your current setup is solving. It all depends -on the avarage and peak printing load the server should be able to handle. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874473"></a>Auto-Deletion of CUPS spool files</h2></div></div><p> -Samba print files pass thru two "spool" directories. One the incoming directory -managed by Samba, (set eg: in the <b>path = /var/spool/samba</b> directive in the [printers] -section of <tt>smb.conf</tt>). Second is the spool directory of your UNIX print subsystem. -For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive -"RequestRoot /var/spool/cups". -</p><p> -I am not sure, which one of your directories keeps the files. From what you say, -it is most likely the Samba part. -</p><p> -For the CUPS part, you may want to consult: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>http://localhost:631/sam.html#PreserveJobFiles</td></tr><tr><td>http://localhost:631/sam.html#PreserveJobHistory</td></tr><tr><td>http://localhost:631/sam.html#MaxJobs</td></tr></table><p> -There are the settings described for your CUPS daemon, which could lead to completed -job files not being deleted. -</p><p> -"PreserveJobHistory Yes" -- keeps some details of jobs in -cupsd's mind (well it keeps the "c12345", "c12346" etc. files -in the CUPS spool directory, which do a similar job as the -old-fashioned BSD-LPD control files). This is set to "Yes" -as a default. -</p><p> -"PreserveJobFiles Yes" -- keeps the job files themselves in -cupsd's mind (well it keeps the "d12345", "d12346" etc. files -in the CUPS spool directory...). This is set to "No" as the -CUPS default. -</p><p> -"MaxJobs 500" -- this directive controls the maximum number -of jobs that are kept in memory. Once the number of jobs -reaches the limit, the oldest completed job is automatically -purged from the system to make room for the new one. If all -of the known jobs are still pending or active then the new -job will be rejected. Setting the maximum to 0 disables this -functionality. The default setting is 0. -</p><p> -(There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...) -</p><p> -For everything to work as announced, you need to have three things: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td> - a Samba-smbd which is compiled against "libcups" (Check on Linux by running <b><tt>ldd `which smbd`</tt></b>) - </td></tr><tr><td> - a Samba-<tt>smb.conf</tt> setting of <b>printing = cups</b> - </td></tr><tr><td> - another Samba-<tt>smb.conf</tt> setting of <b>printcap = cups</b> - </td></tr></table><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Note, that in this case all other manually set printing-related -commands (like "print command", "lpq command", "lprm command", -"lppause command" or "lpresume command") are ignored and they -should normally have no influence what-so-ever on your printing. -</p></div><p> -If you want to do things manually, replace the "printing = cups" -by "printing = bsd". Then your manually set commands may work -(haven't tested this), and a "print command = lp -d %P %s; rm %s" -may do what you need. -</p><p> -You forgot to mention the CUPS version you're using. If you did -set things up as described in the man pages, then the Samba -spool files should be deleted. Otherwise it may be a bug. On -the CUPS side, you can control the behaviour as described -above. -</p><p> -If you have more problems, post the output of these commands: -</p><p> -<b><tt> - grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ - grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;" -</tt></b> -</p><p> -(adapt paths as needed). These commands sanitize the files -and cut out the empty lines and lines with comments, providing -the "naked settings" in a compact way. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="winbind"></a>Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author">Tim Potter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>></tt></p></div></div></div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div><div class="author"><h3 class="author">Naag Mummaneni</h3><div class="affiliation"><div class="address"><p><tt><<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>></tt></p></div></div></div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div><p class="pubdate">27 June 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874714"></a>Abstract</h2></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 - of programs as a solution to the unified logon problem. Winbind - uses a UNIX implementation - of Microsoft RPC calls, Pluggable Authentication Modules, and the Name - Service Switch to allow Windows NT domain users to appear and operate - as UNIX users on a UNIX machine. This paper describes the winbind - system, explaining the functionality it provides, how it is configured, - and how it works internally.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874743"></a>Introduction</h2></div></div><p>It is well known that UNIX and Microsoft Windows NT have - different models for representing user and group information and - use different technologies for implementing them. This fact has - made it difficult to integrate the two systems in a satisfactory - manner.</p><p>One common solution in use today has been to create - identically named user accounts on both the UNIX and Windows systems - and use the Samba suite of programs to provide file and print services - between the two. This solution is far from perfect however, as - adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which - can lead to synchronization problems between the UNIX and Windows - systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into - three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information - </p></li><li><p>Authenticating Windows NT users - </p></li><li><p>Password changing for Windows NT users - </p></li></ul></div><p>Ideally, a prospective solution to the unified logon problem - would satisfy all the above components without duplication of - information on the UNIX machines and without creating additional - tasks for the system administrator when maintaining users and - groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unified logon - problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874814"></a>What Winbind Provides</h2></div></div><p>Winbind unifies UNIX and Windows NT account management by - allowing a UNIX box to become a full member of a NT domain. Once - this is done the UNIX box will see NT users and groups as if - they were native UNIX users and groups, allowing the NT domain - to be used in much the same manner that NIS+ is used within - UNIX-only environments.</p><p>The end result is that whenever any - program on the UNIX machine asks the operating system to lookup - a user or group name, the query will be resolved by asking the - NT domain controller for the specified domain to do the lookup. - Because Winbind hooks into the operating system at a low level - (via the NSS name resolution modules in the C library) this - redirection to the NT domain controller is completely - transparent.</p><p>Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files - so that they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user.</p><p>The only obvious indication that Winbind is being used is - that user and group names take the form DOMAIN\user and - DOMAIN\group. This is necessary as it allows Winbind to determine - that redirection to a domain controller is wanted for a particular - lookup and which trusted domain is being referenced.</p><p>Additionally, Winbind provides an authentication service - that hooks into the Pluggable Authentication Modules (PAM) system - to provide authentication via a NT domain to any PAM enabled - applications. This capability solves the problem of synchronizing - passwords between systems since all passwords are stored in a single - location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872076"></a>Target Uses</h3></div></div><p>Winbind is targeted at organizations that have an - existing NT based domain infrastructure into which they wish - to put UNIX workstations or servers. Winbind will allow these - organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly - simplifies the administrative overhead of deploying UNIX - workstations into a NT based organization.</p><p>Another interesting way in which we expect Winbind to - be used is as a central part of UNIX based appliances. Appliances - that provide file and print services to Microsoft based networks - will be able to use Winbind to provide seamless integration of - the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872107"></a>How Winbind Works</h2></div></div><p>The winbind system is designed around a client/server - architecture. A long running <b>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><h3 class="title"><a name="id2872135"></a>Microsoft Remote Procedure Calls</h3></div></div><p>Over the last few years, efforts have been underway - by various Samba Team members to decode various aspects of - the Microsoft Remote Procedure Call (MSRPC) system. This - system is used for most network related operations between - Windows NT machines including remote management, user authentication - and print spooling. Although initially this work was done - to aid the implementation of Primary Domain Controller (PDC) - functionality in Samba, it has also yielded a body of code which - can be used for other purposes.</p><p>Winbind uses various MSRPC calls to enumerate domain users - and groups and to obtain detailed information about individual - users or groups. Other MSRPC calls can be used to authenticate - NT domain users and to change user passwords. By directly querying - a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872170"></a>Microsoft Active Directory Services</h3></div></div><p> - Since late 2001, Samba has gained the ability to - interact with Microsoft Windows 2000 using its 'Native - Mode' protocols, rather than the NT4 RPC services. - Using LDAP and Kerberos, a domain member running - winbind can enumerate users and groups in exactly the - same way as a Win2k client would, and in so doing - provide a much more efficient and - effective winbind implementation. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872192"></a>Name Service Switch</h3></div></div><p>The Name Service Switch, or NSS, is a feature that is - present in many UNIX operating systems. It allows system - information such as hostnames, mail aliases and user information - to be resolved from different sources. For example, a standalone - UNIX workstation may resolve system information from a series of - flat files stored on the local filesystem. A networked workstation - may first attempt to resolve system information from local files, - and then consult a NIS database for user information or a DNS server - for hostname information.</p><p>The NSS application programming interface allows winbind - to present itself as a source of system information when - resolving UNIX usernames and groups. Winbind uses this interface, - and information obtained from a Windows NT server using MSRPC - calls to provide a new source of account enumeration. Using standard - UNIX library calls, one can enumerate the users and groups on - a UNIX machine running winbind and see all users and groups in - a NT domain plus any trusted domain as though they were local - users and groups.</p><p>The primary control file for NSS is - <tt>/etc/nsswitch.conf</tt>. - When a UNIX application makes a request to do a lookup - the C library looks in <tt>/etc/nsswitch.conf</tt> - for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names - are looked up. This config line species which implementations - of that service should be tried and in what order. If the passwd - config line is:</p><p><b>passwd: files example</b></p><p>then the C library will first load a module called - <tt>/lib/libnss_files.so</tt> followed by - the module <tt>/lib/libnss_example.so</tt>. The - C library will dynamically load each of these modules in turn - and call resolver functions within the modules to try to resolve - the request. Once the request is resolved the C library returns the - result to the application.</p><p>This NSS interface provides a very easy way for Winbind - to hook into the operating system. All that needs to be done - is to put <tt>libnss_winbind.so</tt> in <tt>/lib/</tt> - then add "winbind" into <tt>/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><h3 class="title"><a name="id2875280"></a>Pluggable Authentication Modules</h3></div></div><p>Pluggable Authentication Modules, also known as PAM, - is a system for abstracting authentication and authorization - technologies. With a PAM module it is possible to specify different - authentication methods for different system applications without - having to recompile these applications. PAM is also useful - for implementing a particular policy for authorization. For example, - a system administrator may only allow console logins from users - stored in the local password file but only allow users resolved from - a NIS database to log in over the network.</p><p>Winbind uses the authentication management and password - management PAM interface to integrate Windows NT users into a - UNIX system. This allows Windows NT users to log in to a UNIX - machine and be authenticated against a suitable Primary Domain - Controller. These users can also change their passwords and have - this change take effect directly on the Primary Domain Controller. - </p><p>PAM is configured by providing control files in the directory - <tt>/etc/pam.d/</tt> for each of the services that - require authentication. When an authentication request is made - by an application the PAM code in the C library looks up this - control file to determine what modules to load to do the - authentication check and in what order. This interface makes adding - a new authentication service for Winbind very easy, all that needs - to be done is that the <tt>pam_winbind.so</tt> module - is copied to <tt>/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><h3 class="title"><a name="id2875352"></a>User and Group ID Allocation</h3></div></div><p>When a user or group is created under Windows NT - is it allocated a numerical relative identifier (RID). This is - slightly different to UNIX which has a range of numbers that are - used to identify users, and the same range in which to identify - groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is configured it is given part of the UNIX - user id space and a part of the UNIX group id space in which to - store Windows NT users and groups. If a Windows NT user is - resolved for the first time, it is allocated the next UNIX id from - the range. The same process applies for Windows NT groups. Over - time, winbind will have mapped all Windows NT users and groups - to UNIX user ids and group ids.</p><p>The results of this mapping are stored persistently in - an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875387"></a>Result Caching</h3></div></div><p>An active system can generate a lot of user and group - name lookups. To reduce the network cost of these lookups winbind - uses a caching scheme based on the SAM sequence number supplied - by NT domain controllers. User or group information returned - by a PDC is cached by winbind along with a sequence number also - returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modified. If - a cached entry has expired, the sequence number is requested from - the PDC and compared against the sequence number of the cached entry. - If the sequence numbers do not match, then the cached information - is discarded and up to date information is requested directly - from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875414"></a>Installation and Configuration</h2></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><h3 class="title"><a name="id2875442"></a>Introduction</h3></div></div><p> -This HOWTO describes the procedures used to get winbind up and -running on my RedHat 7.1 system. Winbind is capable of providing access -and authentication control for Windows Domain users through an NT -or Win2K PDC for 'regular' services, such as telnet a nd ftp, as -well for SAMBA services. -</p><p> -This HOWTO has been written from a 'RedHat-centric' perspective, so if -you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works. -</p><div class="itemizedlist"><ul type="disc"><li><p> - <span class="emphasis"><em>Why should I to this?</em></span> - </p><p>This allows the SAMBA administrator to rely on the - authentication mechanisms on the NT/Win2K PDC for the authentication - of domain members. NT/Win2K users no longer need to have separate - accounts on the SAMBA server. - </p></li><li><p> - <span class="emphasis"><em>Who should be reading this document?</em></span> - </p><p> - This HOWTO is designed for system administrators. If you are - implementing SAMBA on a file server and wish to (fairly easily) - integrate existing NT/Win2K users from your PDC onto the - SAMBA server, this HOWTO is for you. That said, I am no NT or PAM - expert, so you may find a better or easier way to accomplish - these tasks. - </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875518"></a>Requirements</h3></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>/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 -into your machine in single user mode and restore your -<tt>/etc/pam.d</tt> back to the original state they were in if -you get frustrated with the way things are going. ;-) -</p><p> -The latest version of SAMBA (version 3.0 as of this writing), now -includes a functioning winbindd daemon. Please refer to the -<a href="http://samba.org/" target="_top">main SAMBA web page</a> or, -better yet, your closest SAMBA mirror site for instructions on -downloading the source code. -</p><p> -To allow Domain users the ability to access SAMBA shares and -files, as well as potentially other services provided by your -SAMBA machine, PAM (pluggable authentication modules) must -be setup properly on your machine. In order to compile the -winbind modules, you should have at least the pam libraries resident -on your system. For recent RedHat systems (7.1, for instance), that -means <tt>pam-0.74-22</tt>. For best results, it is helpful to also -install the development packages in <tt>pam-devel-0.74-22</tt>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875611"></a>Testing Things Out</h3></div></div><p> -Before starting, it is probably best to kill off all the SAMBA -related daemons running on your server. Kill off all <b>smbd</b>, -<b>nmbd</b>, and <b>winbindd</b> processes that may -be running. To use PAM, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the <tt>/etc/pam.d</tt> -directory structure, including the pam modules are used by pam-aware -services, several pam libraries, and the <tt>/usr/doc</tt> -and <tt>/usr/man</tt> entries for pam. Winbind built better -in SAMBA if the pam-devel package was also installed. This package includes -the header files needed to compile pam-aware applications. For instance, -my RedHat system has both <tt>pam-0.74-22</tt> and -<tt>pam-devel-0.74-22</tt> RPMs installed. -</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875688"></a>Configure and compile SAMBA</h4></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. -</p><pre class="programlisting"> -<tt>root#</tt> <b>autoconf</b> -<tt>root#</tt> <b>make clean</b> -<tt>root#</tt> <b>rm config.cache</b> -<tt>root#</tt> <b>./configure</b> -<tt>root#</tt> <b>make</b> -<tt>root#</tt> <b>make install</b> -</pre><p> -This will, by default, install SAMBA in <tt>/usr/local/samba</tt>. -See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875809"></a>Configure <tt>nsswitch.conf</tt> and the -winbind libraries on Linux and Solaris</h4></div></div><p> -The libraries needed to run the <b>winbindd</b> daemon -through nsswitch need to be copied to their proper locations, so -</p><p> -<tt>root#</tt> <b>cp ../samba/source/nsswitch/libnss_winbind.so /lib</b> -</p><p> -I also found it necessary to make the following symbolic link: -</p><p> -<tt>root#</tt> <b>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</b> -</p><p>And, in the case of Sun solaris:</p><p> -<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</tt></b> -<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</tt></b> -<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</tt></b> -</p><p> -Now, as root you need to edit <tt>/etc/nsswitch.conf</tt> to -allow user and group entries to be visible from the <b>winbindd</b> -daemon. My <tt>/etc/nsswitch.conf</tt> file look like -this after editing: -</p><pre class="programlisting"> - passwd: files winbind - shadow: files - group: files winbind -</pre><p> -The libraries needed by the winbind daemon will be automatically -entered into the <b>ldconfig</b> cache the next time -your system reboots, but it -is faster (and you don't need to reboot) if you do it manually: -</p><p> -<tt>root#</tt> <b>/sbin/ldconfig -v | grep winbind</b> -</p><p> -This makes <tt>libnss_winbind</tt> available to winbindd -and echos back a check to you. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876014"></a>NSS Winbind on AIX</h4></div></div><p>(This section is only for those running AIX)</p><p> -The winbind AIX identification module gets built as libnss_winbind.so in the -nsswitch directory of the samba source. This file can be copied to -/usr/lib/security, and the AIX naming convention would indicate that it -should be named WINBIND. A stanza like the following: -</p><pre class="programlisting"> -WINBIND: - program = /usr/lib/security/WINBIND - options = authonly -</pre><p>can then be added to -<tt>/usr/lib/security/methods.cfg</tt>. This module only -supports identification, but there have been success reports using the -standard winbind pam module for authentication. Use caution configuring -loadable authentication modules as it is possible to make it impossible -to logon to the system. More information about the AIX authentication -module API can be found at "Kernel Extensions and Device Support -Programming Concepts for AIX": <a href="#"> -Chapter 18. Loadable Authentication Module Programming Interface</a> -and more information on administering the modules at <a href="#"> -"System Management Guide: Operating System and Devices"</a>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876087"></a>Configure smb.conf</h4></div></div><p> -Several parameters are needed in the smb.conf file to control -the behavior of <b>winbindd</b>. Configure -<tt>smb.conf</tt> These are described in more detail in -the <a href="winbindd.8.html">winbindd(8)</a> man page. My -<tt>smb.conf</tt> file was modified to -include the following entries in the [global] section: -</p><pre class="programlisting"> -[global] - <...> - # separate domain and username with '+', like DOMAIN+username - <a href="winbindd.8.html#WINBINDSEPARATOR" target="_top">winbind separator</a> = + - # use uids from 10000 to 20000 for domain users - <a href="winbindd.8.html#WINBINDUID" target="_top">winbind uid</a> = 10000-20000 - # use gids from 10000 to 20000 for domain groups - <a href="winbindd.8.html#WINBINDGID" target="_top">winbind gid</a> = 10000-20000 - # allow enumeration of winbind users and groups - <a href="winbindd.8.html#WINBINDENUMUSERS" target="_top">winbind enum users</a> = yes - <a href="winbindd.8.html#WINBINDENUMGROUP" target="_top">winbind enum groups</a> = yes - # give winbind users a real shell (only needed if they have telnet access) - <a href="winbindd.8.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> = /home/winnt/%D/%U - <a href="winbindd.8.html#TEMPLATESHELL" target="_top">template shell</a> = /bin/bash -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876202"></a>Join the SAMBA server to the PDC domain</h4></div></div><p> -Enter the following command to make the SAMBA server join the -PDC domain, where <i><tt>DOMAIN</tt></i> is the name of -your Windows domain and <i><tt>Administrator</tt></i> is -a domain user who has administrative privileges in the domain. -</p><p> -<tt>root#</tt> <b>/usr/local/samba/bin/net join -S PDC -U Administrator</b> -</p><p> -The proper response to the command should be: "Joined the domain -<i><tt>DOMAIN</tt></i>" where <i><tt>DOMAIN</tt></i> -is your DOMAIN name. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876259"></a>Start up the winbindd daemon and test it!</h4></div></div><p> -Eventually, you will want to modify your smb startup script to -automatically invoke the winbindd daemon when the other parts of -SAMBA start, but it is possible to test out just the winbind -portion first. To start up winbind services, enter the following -command as root: -</p><p> -<tt>root#</tt> <b>/usr/local/samba/bin/winbindd</b> -</p><p> -Winbindd can now also run in 'dual daemon mode'. This will make it -run as 2 processes. The first will answer all requests from the cache, -thus making responses to clients faster. The other will -update the cache for the query that the first has just responded. -Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline: -</p><p> -<tt>root#</tt> <b>/usr/local/samba/bin/winbindd -B</b> -</p><p> -I'm always paranoid and like to make sure the daemon -is really running... -</p><p> -<tt>root#</tt> <b>ps -ae | grep winbindd</b> -</p><p> -This command should produce output like this, if the daemon is running -</p><p> -3025 ? 00:00:00 winbindd -</p><p> -Now... for the real test, try to get some information about the -users on your PDC -</p><p> -<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -u</b> -</p><p> -This should echo back a list of users on your Windows users on -your PDC. For example, I get the following response: -</p><pre class="programlisting"> - CEO+Administrator - CEO+burdell - CEO+Guest - CEO+jt-ad - CEO+krbtgt - CEO+TsInternetUser -</pre><p> -Obviously, I have named my domain 'CEO' and my <i><tt>winbind -separator</tt></i> is '+'. -</p><p> -You can do the same sort of thing to get group information from -the PDC: -</p><pre class="programlisting"> -<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -g</b> - CEO+Domain Admins - CEO+Domain Users - CEO+Domain Guests - CEO+Domain Computers - CEO+Domain Controllers - CEO+Cert Publishers - CEO+Schema Admins - CEO+Enterprise Admins - CEO+Group Policy Creator Owners -</pre><p> -The function 'getent' can now be used to get unified -lists of both local and PDC users and groups. -Try the following command: -</p><p> -<tt>root#</tt> <b>getent passwd</b> -</p><p> -You should get a list that looks like your <tt>/etc/passwd</tt> -list followed by the domain users with their new uids, gids, home -directories and default shells. -</p><p> -The same thing can be done for groups with the command -</p><p> -<tt>root#</tt> <b>getent group</b> -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876504"></a>Fix the init.d startup scripts</h4></div></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876511"></a>Linux</h5></div></div><p> -The <b>winbindd</b> daemon needs to start up after the -<b>smbd</b> and <b>nmbd</b> daemons are running. -To accomplish this task, you need to modify the startup scripts of your system. -They are located at <tt>/etc/init.d/smb</tt> in RedHat and -<tt>/etc/init.d/samba</tt> in Debian. -script to add commands to invoke this daemon in the proper sequence. My -startup script starts up <b>smbd</b>, -<b>nmbd</b>, and <b>winbindd</b> from the -<tt>/usr/local/samba/bin</tt> directory directly. The 'start' -function in the script looks like this: -</p><pre class="programlisting"> -start() { - KIND="SMB" - echo -n $"Starting $KIND services: " - daemon /usr/local/samba/bin/smbd $SMBDOPTIONS - RETVAL=$? - echo - KIND="NMB" - echo -n $"Starting $KIND services: " - daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS - RETVAL2=$? - echo - KIND="Winbind" - echo -n $"Starting $KIND services: " - daemon /usr/local/samba/bin/winbindd - RETVAL3=$? - echo - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \ - touch /var/lock/subsys/smb || RETVAL=1 - return $RETVAL -} -</pre><p>If you would like to run winbindd in dual daemon mode, replace -the line -</p><pre class="programlisting"> - daemon /usr/local/samba/bin/winbindd -</pre><p> - -in the example above with: - -</p><pre class="programlisting"> - daemon /usr/local/samba/bin/winbindd -B -</pre><p>. -</p><p> -The 'stop' function has a corresponding entry to shut down the -services and looks like this: -</p><pre class="programlisting"> -stop() { - KIND="SMB" - echo -n $"Shutting down $KIND services: " - killproc smbd - RETVAL=$? - echo - KIND="NMB" - echo -n $"Shutting down $KIND services: " - killproc nmbd - RETVAL2=$? - echo - KIND="Winbind" - echo -n $"Shutting down $KIND services: " - killproc winbindd - RETVAL3=$? - [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \ - rm -f /var/lock/subsys/smb - echo "" - return $RETVAL -} -</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876648"></a>Solaris</h5></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>/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>/usr/local/samba/bin</tt>, -the file could contains something like this: -</p><pre class="programlisting"> - ## - ## samba.server - ## - - if [ ! -d /usr/bin ] - then # /usr not mounted - exit - fi - - killproc() { # kill the named process(es) - pid=`/usr/bin/ps -e | - /usr/bin/grep -w $1 | - /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid - } - - # Start/stop processes required for samba server - - case "$1" in - - 'start') - # - # Edit these lines to suit your installation (paths, workgroup, host) - # - echo Starting SMBD - /usr/local/samba/bin/smbd -D -s \ - /usr/local/samba/smb.conf - - echo Starting NMBD - /usr/local/samba/bin/nmbd -D -l \ - /usr/local/samba/var/log -s /usr/local/samba/smb.conf - - echo Starting Winbind Daemon - /usr/local/samba/bin/winbindd - ;; - - 'stop') - killproc nmbd - killproc smbd - killproc winbindd - ;; - - *) - echo "Usage: /etc/init.d/samba.server { start | stop }" - ;; - esac -</pre><p> -Again, if you would like to run samba in dual daemon mode, replace -</p><pre class="programlisting"> - /usr/local/samba/bin/winbindd -</pre><p> - -in the script above with: - -</p><pre class="programlisting"> - /usr/local/samba/bin/winbindd -B -</pre><p> -</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876749"></a>Restarting</h5></div></div><p> -If you restart the <b>smbd</b>, <b>nmbd</b>, -and <b>winbindd</b> daemons at this point, you -should be able to connect to the samba server as a domain member just as -if you were a local user. -</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876785"></a>Configure Winbind and PAM</h4></div></div><p> -If you have made it this far, you know that winbindd and samba are working -together. If you want to use winbind to provide authentication for other -services, keep reading. The pam configuration files need to be altered in -this step. (Did you remember to make backups of your original -<tt>/etc/pam.d</tt> files? If not, do it now.) -</p><p> -You will need a pam module to use winbindd with these other services. This -module will be compiled in the <tt>../source/nsswitch</tt> directory -by invoking the command -</p><p> -<tt>root#</tt> <b>make nsswitch/pam_winbind.so</b> -</p><p> -from the <tt>../source</tt> directory. The -<tt>pam_winbind.so</tt> file should be copied to the location of -your other pam security modules. On my RedHat system, this was the -<tt>/lib/security</tt> directory. On Solaris, the pam security -modules reside in <tt>/usr/lib/security</tt>. -</p><p> -<tt>root#</tt> <b>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</b> -</p><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876895"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><p> -The <tt>/etc/pam.d/samba</tt> file does not need to be changed. I -just left this fileas it was: -</p><pre class="programlisting"> - auth required /lib/security/pam_stack.so service=system-auth - account required /lib/security/pam_stack.so service=system-auth -</pre><p> -The other services that I modified to allow the use of winbind -as an authentication service were the normal login on the console (or a terminal -session), telnet logins, and ftp service. In order to enable these -services, you may first need to change the entries in -<tt>/etc/xinetd.d</tt> (or <tt>/etc/inetd.conf</tt>). -RedHat 7.1 uses the new xinetd.d structure, in this case you need -to change the lines in <tt>/etc/xinetd.d/telnet</tt> -and <tt>/etc/xinetd.d/wu-ftp</tt> from -</p><pre class="programlisting"> - enable = no -</pre><p> -to -</p><pre class="programlisting"> - enable = yes -</pre><p> -For ftp services to work properly, you will also need to either -have individual directories for the domain users already present on -the server, or change the home directory template to a general -directory for all domain users. These can be easily set using -the <tt>smb.conf</tt> global entry -<b>template homedir</b>. -</p><p> -The <tt>/etc/pam.d/ftp</tt> file can be changed -to allow winbind ftp access in a manner similar to the -samba file. My <tt>/etc/pam.d/ftp</tt> file was -changed to look like this: -</p><pre class="programlisting"> - auth required /lib/security/pam_listfile.so item=user sense=deny \ - file=/etc/ftpusers onerr=succeed - auth sufficient /lib/security/pam_winbind.so - auth required /lib/security/pam_stack.so service=system-auth - auth required /lib/security/pam_shells.so - account sufficient /lib/security/pam_winbind.so - account required /lib/security/pam_stack.so service=system-auth - session required /lib/security/pam_stack.so service=system-auth -</pre><p> -The <tt>/etc/pam.d/login</tt> file can be changed nearly the -same way. It now looks like this: -</p><pre class="programlisting"> - auth required /lib/security/pam_securetty.so - auth sufficient /lib/security/pam_winbind.so - auth sufficient /lib/security/pam_unix.so use_first_pass - auth required /lib/security/pam_stack.so service=system-auth - auth required /lib/security/pam_nologin.so - account sufficient /lib/security/pam_winbind.so - account required /lib/security/pam_stack.so service=system-auth - password required /lib/security/pam_stack.so service=system-auth - session required /lib/security/pam_stack.so service=system-auth - session optional /lib/security/pam_console.so -</pre><p> -In this case, I added the <b>auth sufficient /lib/security/pam_winbind.so</b> -lines as before, but also added the <b>required pam_securetty.so</b> -above it, to disallow root logins over the network. I also added a -<b>sufficient /lib/security/pam_unix.so use_first_pass</b> -line after the <b>winbind.so</b> line to get rid of annoying -double prompts for passwords. -</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2877118"></a>Solaris-specific configuration</h5></div></div><p> -The /etc/pam.conf needs to be changed. I changed this file so that my Domain -users can logon both locally as well as telnet.The following are the changes -that I made.You can customize the pam.conf file as per your requirements,but -be sure of those changes because in the worst case it will leave your system -nearly impossible to boot. -</p><pre class="programlisting"> - # - #ident "@(#)pam.conf 1.14 99/09/16 SMI" - # - # Copyright (c) 1996-1999, Sun Microsystems, Inc. - # All Rights Reserved. - # - # PAM configuration - # - # Authentication management - # - login auth required /usr/lib/security/pam_winbind.so - login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass - login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass - # - rlogin auth sufficient /usr/lib/security/pam_winbind.so - rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1 - rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass - # - dtlogin auth sufficient /usr/lib/security/pam_winbind.so - dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass - # - rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1 - other auth sufficient /usr/lib/security/pam_winbind.so - other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass - # - # Account management - # - login account sufficient /usr/lib/security/pam_winbind.so - login account requisite /usr/lib/security/$ISA/pam_roles.so.1 - login account required /usr/lib/security/$ISA/pam_unix.so.1 - # - dtlogin account sufficient /usr/lib/security/pam_winbind.so - dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1 - dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1 - # - other account sufficient /usr/lib/security/pam_winbind.so - other account requisite /usr/lib/security/$ISA/pam_roles.so.1 - other account required /usr/lib/security/$ISA/pam_unix.so.1 - # - # Session management - # - other session required /usr/lib/security/$ISA/pam_unix.so.1 - # - # Password management - # - #other password sufficient /usr/lib/security/pam_winbind.so - other password required /usr/lib/security/$ISA/pam_unix.so.1 - dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1 - # - # Support for Kerberos V5 authentication (uncomment to use Kerberos) - # - #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass - #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass - #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass - #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass - #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1 - #other account optional /usr/lib/security/$ISA/pam_krb5.so.1 - #other session optional /usr/lib/security/$ISA/pam_krb5.so.1 - #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass -</pre><p> -I also added a try_first_pass line after the winbind.so line to get rid of -annoying double prompts for passwords. -</p><p> -Now restart your Samba and try connecting through your application that you -configured in the pam.conf. -</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877210"></a>Limitations</h2></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 - systems are certainly possible. For such ports to be feasible, - we require the C library of the target operating system to - support the Name Service Switch and Pluggable Authentication - Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.</p></li><li><p>The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.</p></li><li><p>Currently the winbind PAM module does not take - into account possible workstation and logon time restrictions - that may be been set for Windows NT users, this is - instead up to the PDC to enforce.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877264"></a>Conclusion</h2></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><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter 16. Advanced Network Manangement</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></div><p> -This section attempts to document peripheral issues that are of great importance to network -administrators who want to improve network resource access control, to automate the user -environment, and to make their lives a little easier. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875143"></a>Configuring Samba Share Access Controls</h2></div></div><p> -This section deals with how to configure Samba per share access control restrictions. -By default samba sets no restrictions on the share itself. Restrictions on the share itself -can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can -connect to a share. In the absence of specific restrictions the default setting is to allow -the global user <span class="emphasis"><em>Everyone</em></span> Full Control (ie: Full control, Change and Read). -</p><p> -At this time Samba does NOT provide a tool for configuring access control setting on the Share -itself. Samba does have the capacity to store and act on access control settings, but the only -way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for -Computer Management. -</p><p> -Samba stores the per share access control settings in a file called <tt>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>/usr/local/samba/var</tt>. If the <tt>tdbdump</tt> -utility has been compiled and installed on your system then you can examine the contents of this file -by: <b><tt>tdbdump share_info.tdb</tt></b>. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874905"></a>Share Permissions Management</h3></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><h4 class="title"><a name="id2874919"></a>Windows NT4 Workstation/Server</h4></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. -</p><div class="procedure"><p class="title"><b>Procedure 16.1. Instructions</b></p><ol type="1"><li><p> -Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu -select Computer, then click on the Shared Directories entry. -</p></li><li><p> - Now click on the share that you wish to manage, then click on the Properties tab, next click on - the Permissions tab. Now you can Add or change access control settings as you wish. -</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877329"></a>Windows 200x/XP</h4></div></div><p> -On MS Windows NT4/200x/XP system access control lists on the share itself are set using native -tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, -then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows -<span class="emphasis"><em>Everyone</em></span> Full Control on the Share. -</p><p> -MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the -Microsoft Management Console (MMC). This tool is located by clicking on <tt>Control Panel -> -Administrative Tools -> Computer Management</tt>. -</p><div class="procedure"><p class="title"><b>Procedure 16.2. Instructions</b></p><ol type="1"><li><p> - After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', - select 'Connect to another computer'. If you are not logged onto a domain you will be prompted - to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered. -</p></li><li><p> -If the Samba server is not shown in the Select Computer box, then type in the name of the target -Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] -next to 'Shared Folders' in the left panel. -</p></li><li><p> -Now in the right panel, double-click on the share you wish to set access control permissions on. -Then click on the tab 'Share Permissions'. It is now possible to add access control entities -to the shared folder. Do NOT forget to set what type of access (full control, change, read) you -wish to assign for each entry. -</p></li></ol></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> -Be careful. If you take away all permissions from the Everyone user without removing this user -then effectively no user will be able to access the share. This is a result of what is known as -ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone -will have no access even if this user is given explicit full control access. -</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874974"></a>Remote Server Administration</h2></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 NT4 Server, how do I get the 'User Manager for Domains', -the 'Server Manager'? -</p><p> -Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me -systems. The tools set includes: -</p><div class="itemizedlist"><ul type="disc"><li><p>Server Manager</p></li><li><p>User Manager for Domains</p></li><li><p>Event Viewer</p></li></ul></div><p> -Click here to download the archived file <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" target="_top">ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</a> -</p><p> -The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</a> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875057"></a>Network Logon Script Magic</h2></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 - 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>examples</tt> directory <tt>genlogon</tt> and <tt>ntlogon</tt> subdirectories. -</p><p> -The following listings are from the genlogon directory. -</p><p> -This is the genlogon.pl file: - -</p><pre class="programlisting"> - #!/usr/bin/perl - # - # genlogon.pl - # - # Perl script to generate user logon scripts on the fly, when users - # connect from a Windows client. This script should be called from smb.conf - # with the %U, %G and %L parameters. I.e: - # - # root preexec = genlogon.pl %U %G %L - # - # The script generated will perform - # the following: - # - # 1. Log the user connection to /var/log/samba/netlogon.log - # 2. Set the PC's time to the Linux server time (which is maintained - # daily to the National Institute of Standard's Atomic clock on the - # internet. - # 3. Connect the user's home drive to H: (H for Home). - # 4. Connect common drives that everyone uses. - # 5. Connect group-specific drives for certain user groups. - # 6. Connect user-specific drives for certain users. - # 7. Connect network printers. - - # Log client connection - #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); - ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); - open LOG, ">>/var/log/samba/netlogon.log"; - print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; - close LOG; - - # Start generating logon script - open LOGON, ">/shared/netlogon/$ARGV[0].bat"; - print LOGON "\@ECHO OFF\r\n"; - - # Connect shares just use by Software Development group - if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") - { - print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; - } - - # Connect shares just use by Technical Support staff - if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support") - { - print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n"; - } - - # Connect shares just used by Administration staff - If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin") - { - print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n"; - print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n"; - } - - # Now connect Printers. We handle just two or three users a little - # differently, because they are the exceptions that have desktop - # printers on LPT1: - all other user's go to the LaserJet on the - # server. - if ($ARGV[0] eq 'jim' - || $ARGV[0] eq 'yvonne') - { - print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; - } - else - { - print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; - } - - # All done! Close the output file. - close LOGON; -</pre><p> -</p><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>http://www.craigelachie.org/rhacer/ntlogon</td></tr><tr><td>http://www.kixtart.org</td></tr><tr><td>http://support.microsoft.com/default.asp?scid=kb;en-us;189105</td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877889"></a>Adding printers without user intervention</h3></div></div><p> -Printers may be added automatically during logon script processing through the use of: - -</p><pre class="programlisting"> - rundll32 printui.dll,PrintUIEntry /? -</pre><p> - -See the documentation in the Microsoft knowledgebase article no: 189105 referred to above. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter 17. System and Account Policies</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877672"></a>Creating and Managing System Policies</h2></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 -this file is read and the contents initiate changes to the registry of the client -machine. This file allows changes to be made to those parts of the registry that -affect users, groups of users, or machines. -</p><p> -For MS Windows 9x/Me this file must be called <tt>Config.POL</tt> and may -be generated using a tool called <tt>poledit.exe</tt>, better known as the -Policy Editor. The policy editor was provided on the Windows 98 installation CD, but -dissappeared again with the introduction of MS Windows Me (Millenium Edition). From -comments from MS Windows network administrators it would appear that this tool became -a part of the MS Windows Me Resource Kit. -</p><p> -MS Windows NT4 Server products include the <span class="emphasis"><em>System Policy Editor</em></span> -under the <tt>Start -> Programs -> Administrative Tools</tt> menu item. -For MS Windows NT4 and later clients this file must be called <tt>NTConfig.POL</tt>. -</p><p> -New with the introduction of MS Windows 2000 was the Microsoft Management Console -or MMC. This tool is the new wave in the ever changing landscape of Microsoft -methods for management of network access and security. Every new Microsoft product -or technology seems to obsolete the old rules and to introduce newer and more -complex tools and methods. To Microsoft's credit though, the MMC does appear to -be a step forward, but improved functionality comes at a great price. -</p><p> -Before embarking on the configuration of network and system policies it is highly -advisable to read the documentation available from Microsoft's web site regarding -<a href="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp" target="_top"> -Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</a> available from Microsoft. -There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies". -</p><p> -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><h3 class="title"><a name="id2877925"></a>Windows 9x/Me Policies</h3></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>tools/reskit/netadmin/poledit</tt>. Install this using the -Add/Remove Programs facility and then click on the 'Have Disk' tab. -</p><p> -Use the Group Policy Editor to create a policy file that specifies the location of -user profiles and/or the <tt>My Documents</tt> etc. stuff. Then -save these settings in a file called <tt>Config.POL</tt> that needs to -be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto -the Samba Domain, it will automatically read this file and update the Win9x/Me registry -of the machine as it logs on. -</p><p> -Further details are covered in the Win98 Resource Kit documentation. -</p><p> -If you do not take the right steps, then every so often Win9x/Me will check the -integrity of the registry and will restore it's settings from the back-up -copy of the registry it stores on each Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings. -</p><p> -Install the group policy handler for Win9x to pick up group policies. Look on the -Win98 CD in <tt>\tools\reskit\netadmin\poledit</tt>. -Install group policies on a Win9x client by double-clicking -<tt>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><h3 class="title"><a name="id2878014"></a>Windows NT4 Style Policy Files</h3></div></div><p> -To create or edit <tt>ntconfig.pol</tt> you must use the NT Server -Policy Editor, <b>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 -Workstation but it is not suitable for creating <span class="emphasis"><em>Domain Policies</em></span>. -Further, although the Windows 95 Policy Editor can be installed on an NT4 -Workstation/Server, it will not work with NT clients. However, the files from -the NT Server will run happily enough on an NT4 Workstation. -</p><p> -You need <tt>poledit.exe, common.adm</tt> and <tt>winnt.adm</tt>. -It is convenient to put the two *.adm files in the <tt>c:\winnt\inf</tt> -directory which is where the binary will look for them unless told otherwise. Note also that that -directory is normally 'hidden'. -</p><p> -The Windows NT policy editor is also included with the Service Pack 3 (and -later) for Windows NT 4.0. Extract the files using <b>servicepackname /x</b>, -i.e. that's <b>Nt4sp6ai.exe /x</b> for service pack 6a. The policy editor, -<b>poledit.exe</b> and the associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft. -</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878116"></a>Registry Tattoos</h4></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><h3 class="title"><a name="id2878140"></a>MS Windows 200x / XP Professional Policies</h3></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. -</p><p> -New to MS Windows 2000 Microsoft introduced a new style of group policy that confers -a superset of capabilities compared with NT4 style policies. Obviously, the tool used -to create them is different, and the mechanism for implementing them is much changed. -</p><p> -The older NT4 style registry based policies are known as <span class="emphasis"><em>Administrative Templates</em></span> -in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security -configurations, enforce Internet Explorer browser settings, change and redirect aspects of the -users' desktop (including: the location of <span class="emphasis"><em>My Documents</em></span> files (directory), as -well as intrinsics of where menu items will appear in the Start menu). An additional new -feature is the ability to make available particular software Windows applications to particular -users and/or groups. -</p><p> -Remember: NT4 policy files are named <tt>NTConfig.POL</tt> and are stored in the root -of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password -and selects the domain name to which the logon will attempt to take place. During the logon -process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating -server, modifies the local registry values according to the settings in this file. -</p><p> -Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of -a Windows 200x policy file is stored in the Active Directory itself and the other part is stored -in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active -Directory domain controllers. The part that is stored in the Active Directory itself is called the -group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is -known as the group policy template (GPT). -</p><p> -With NT4 clients the policy file is read and executed upon only as each user logs onto the network. -MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine -startup (machine specific part) and when the user logs onto the network the user specific part -is applied. In MS Windows 200x style policy management each machine and/or user may be subject -to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows -the administrator to also set filters over the policy settings. No such equivalent capability -exists with NT4 style policy files. -</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878237"></a>Administration of Win2K / XP Policies</h4></div><div><h4 class="title"><a name="id2878237"></a>Administration of Win2K / XP Policies</h4></div></div><p> -Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the -executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows:</p><div class="procedure"><ol type="1"><li><p> -Go to the Windows 200x / XP menu <tt>Start->Programs->Administrative Tools</tt> - and select the MMC snap-in called "Active Directory Users and Computers" -</p></li><li><p> -Select the domain or organizational unit (OU) that you wish to manage, then right click -to open the context menu for that object, select the properties item. -</p></li><li><p> -Now left click on the Group Policy tab, then left click on the New tab. Type a name -for the new policy you will create. -</p></li><li><p> -Now left click on the Edit tab to commence the steps needed to create the GPO. -</p></li></ol></div><p> -All policy configuration options are controlled through the use of policy administrative -templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. -Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. -The later introduces many new features as well as extended definition capabilities. It is -well beyond the scope of this documentation to explain how to program .adm files, for that -the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular -version of MS Windows. -</p><div class="note" 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 class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878344"></a>Managing Account/User Policies</h2></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. -</p><p> -If you create a policy that will be automatically downloaded from validating domain controllers, -you should name the file NTconfig.POL. As system administrator, you have the option of renaming the -policy file and, by modifying the Windows NT-based workstation, directing the computer to update -the policy from a manual path. You can do this by either manually changing the registry or by using -the System Policy Editor. This path can even be a local path such that each machine has its own policy file, -but if a change is necessary to all machines, this change must be made individually to each workstation. -</p><p> -When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain -controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then -applied to the user's part of the registry. -</p><p> -MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, -acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory -itself. The key benefit of using AS GPOs is that they impose no registry <span class="emphasis"><em>tatooing</em></span> effect. -This has considerable advanage 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><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><h3 class="title"><a name="id2878457"></a>With Windows NT4/200x</h3></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 -"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><h3 class="title"><a name="id2878478"></a>With a Samba PDC</h3></div></div><p> -With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -<tt>smbpasswd, pdbedit, net, rpcclient.</tt>. The administrator should read the -man pages for these tools and become familiar with their use. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878502"></a>System Startup and Logon Processing Overview</h2></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><p> - Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded - and applied. The list may include GPOs that: -</p><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. - </p></li><li><p> - Execution of start-up scripts (hidden and synchronous by defaut). - </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><p> - An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: - -</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 - Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal - window. - </p></li><li><p> - The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 - Domain) machine (system) policies are applied at start-up, User policies are applied at logon. - </p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter 18. Desktop Profile Management</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877599"></a>Roaming Profiles</h2></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 -Windows 9x / Me and Windows NT4/200x clients implement these features. -</p><p> -Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's -profiles location. However, the response does not have room for a separate -profiles location field, only the user's home share. This means that Win9X/Me -profiles are restricted to being stored in the user's home directory. -</p><p> -Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877483"></a>Samba Configuration for Profile Handling</h3></div></div><p> -This section documents how to configure Samba for MS Windows client profile support. -</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877497"></a>NT4/200x User Profiles</h4></div></div><p> -To support Windowns NT4/200x clients, in the [global] section of smb.conf set the -following (for example): -</p><p> -</p><pre class="programlisting"> - logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath -</pre><p> - - This is typically implemented like: - -</p><pre class="programlisting"> - logon path = \\%L\Profiles\%u -</pre><p> -where %L translates to the name of the Samba server and %u translates to the user name -</p><p> -The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. -The \\N%\%U service is created automatically by the [homes] service. If you are using -a samba server for the profiles, you _must_ make the share specified in the logon path -browseable. Please refer to the man page for smb.conf in respect of the different -symantics of %L and %N, as well as %U and %u. -</p><div class="note" 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 <b>homes</b> -meta-service name as part of the profile share path. -</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878824"></a>Windows 9x / Me User Profiles</h4></div></div><p> -To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has -now been fixed so that <b><tt>net use /home</tt></b> now works as well, and it, too, relies -on the <b>logon home</b> parameter. -</p><p> -By using the logon home parameter, you are restricted to putting Win9x / Me -profiles in the user's home directory. But wait! There is a trick you -can use. If you set the following in the <b>[global]</b> section of your <tt>smb.conf</tt> file: -</p><pre class="programlisting"> - logon home = \\%L\%U\.profiles -</pre><p> -then your Windows 9x / Me clients will dutifully put their clients in a subdirectory -of your home directory called <tt>.profiles</tt> (thus making them hidden). -</p><p> -Not only that, but <b><tt>net use /home</tt></b> will also work, because of a feature in -Windows 9x / Me. It removes any directory stuff off the end of the home directory area -and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for <b>logon home</b>. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878920"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><p> -You can support profiles for both Win9X and WinNT clients by setting both the -<b>logon home</b> and <b>logon path</b> 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><h4 class="title"><a name="id2878959"></a>Disabling Roaming Profile Support</h4></div></div><p> -A question often asked is "How may I enforce use of local profiles?" or -"How do I disable Roaming Profiles?" -</p><p> -There are three ways of doing this: -</p><div class="itemizedlist"><ul type="disc"><li><p> - <b>In smb.conf:</b> affect the following settings and ALL clients - will be forced to use a local profile: - </p><pre class="programlisting"> - logon home = - logon path = - </pre></li><li><p> - <b>MS Windows Registry:</b> 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: - </p><pre class="programlisting"> - Local Computer Policy\ - Computer Configuration\ - Administrative Templates\ - System\ - User Profiles\ - - Disable: Only Allow Local User Profiles - Disable: Prevent Roaming Profile Change from Propogating to the Server - </pre><p> - </p></li><li><p> - <b>Change of Profile Type:</b> From the start menu right click on the - MY Computer icon, select <span class="emphasis"><em>Properties</em></span>, click on the "<span class="emphasis"><em>User Profiles</em></span> - tab, select the profile you wish to change from Roaming type to Local, click <span class="emphasis"><em>Change Type</em></span>. - </p></li></ul></div><p> -Consult the MS Windows registry guide for your particular MS Windows version for more -information about which registry keys to change to enforce use of only local user -profiles. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -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><h3 class="title"><a name="id2879080"></a>Windows Client Profile Configuration Information</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879088"></a>Windows 9x / Me Profile Setup</h4></div></div><p> -When a user first logs in on Windows 9X, the file user.DAT is created, -as are folders "Start Menu", "Desktop", "Programs" and "Nethood". -These directories and their contents will be merged with the local -versions stored in c:\windows\profiles\username on subsequent logins, -taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short preserve case = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders. -</p><p> -The user.DAT file contains all the user's preferences. If you wish to -enforce a set of preferences, rename their user.DAT file to user.MAN, -and deny them write access to this file. -</p><div class="orderedlist"><ol type="1"><li><p> - On the Windows 9x / Me machine, go to Control Panel -> Passwords and - select the User Profiles tab. Select the required level of - roaming preferences. Press OK, but do _not_ allow the computer - to reboot. - </p></li><li><p> - On the Windows 9x / Me machine, go to Control Panel -> Network -> - Client for Microsoft Networks -> Preferences. Select 'Log on to - NT Domain'. Then, ensure that the Primary Logon is 'Client for - Microsoft Networks'. Press OK, and this time allow the computer - to reboot. - </p></li></ol></div><p> -Under Windows 9x / Me Profiles are downloaded from the Primary Logon. -If you have the Primary Logon as 'Client for Novell Networks', then -the profiles and logon script will be downloaded from your Novell -Server. If you have the Primary Logon as 'Windows Logon', then the -profiles will be loaded from the local machine - a bit against the -concept of roaming profiles, it would seem! -</p><p> -You will now find that the Microsoft Networks Login box contains -[user, password, domain] instead of just [user, password]. Type in -the samba server's domain name (or any other domain known to exist, -but bear in mind that the user will be authenticated against this -domain and profiles downloaded from it, if that domain logon server -supports it), user name and user's password. -</p><p> -Once the user has been successfully validated, the Windows 9x / Me machine -will inform you that 'The user has not logged on before' and asks you -if you wish to save the user's preferences? Select 'yes'. -</p><p> -Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the "logon path" -on the samba server and verify that the "Desktop", "Start Menu", -"Programs" and "Nethood" folders have been created. -</p><p> -These folders will be cached locally on the client, and updated when -the user logs off (if you haven't made them read-only by then). -You will find that if the user creates further folders or short-cuts, -that the client will merge the profile contents downloaded with the -contents of the profile directory already on the local client, taking -the newest folders and short-cuts from each set. -</p><p> -If you have made the folders / files read-only on the samba server, -then you will get errors from the Windows 9x / Me machine on logon and logout, as -it attempts to merge the local and the remote profile. Basically, if -you have any errors reported by the Windows 9x / Me machine, check the Unix file -permissions and ownership rights on the profile directory contents, -on the samba server. -</p><p> -If you have problems creating user profiles, you can reset the user's -local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time". -</p><div class="orderedlist"><ol type="1"><li><p> - instead of logging in under the [user, password, domain] dialog, - press escape. - </p></li><li><p> - run the regedit.exe program, and look in: - </p><p> - HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList - </p><p> - you will find an entry, for each user, of ProfilePath. Note the - contents of this key (likely to be c:\windows\profiles\username), - then delete the key ProfilePath for the required user. - - [Exit the registry editor]. - - </p></li><li><p> - <span class="emphasis"><em>WARNING</em></span> - before deleting the contents of the - directory listed in the ProfilePath (this is likely to be - <tt>c:\windows\profiles\username)</tt>, ask them if they - have any important files stored on their desktop or in their start menu. - Delete the contents of the directory ProfilePath (making a backup if any - of the files are needed). - </p><p> - This will have the effect of removing the local (read-only hidden - system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. - </p></li><li><p> - search for the user's .PWL password-caching file in the c:\windows - directory, and delete it. - </p></li><li><p> - log off the windows 9x / Me client. - </p></li><li><p> - check the contents of the profile path (see "logon path" described - above), and delete the user.DAT or user.MAN file for the user, - making a backup if required. - </p></li></ol></div><p> -If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as ethereal or netmon.exe, and -look for error messages. -</p><p> -If you have access to an Windows NT4/200x server, then first set up roaming profiles -and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine -the example packet traces provided with Windows NT4/200x server, and see what the -differences are with the equivalent samba trace. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879358"></a>Windows NT4 Workstation</h4></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 "logon path" parameter. -</p><p> -There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to <tt>H:</tt> or any other drive, and -should be used in conjunction with the new "logon home" parameter. -</p><p> -The entry for the NT4 profile is a _directory_ not a file. The NT -help on profiles mentions that a directory is also created with a .PDS -extension. The user, while logging in, must have write permission to -create the full profile path (and the folder with the .PDS extension -for those situations where it might be created.) -</p><p> -In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -It creates "Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file -NTuser.DAT. Nothing appears to be stored in the .PDS directory, and -its purpose is currently unknown. -</p><p> -You can use the System Control Panel to copy a local profile onto -a samba server (see NT Help on profiles: it is also capable of firing -up the correct location in the System Control Panel for you). The -NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN -turns a profile into a mandatory one. -</p><p> -The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879426"></a>Windows 2000/XP Professional</h4></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="itemizedlist"><ul type="disc"><li><p> - Log on as the LOCAL workstation administrator. - </p></li><li><p> - Right click on the 'My Computer' Icon, select 'Properties' - </p></li><li><p> - Click on the 'User Profiles' tab - </p></li><li><p> - Select the profile you wish to convert (click on it once) - </p></li><li><p> - Click on the button 'Copy To' - </p></li><li><p> - In the "Permitted to use" box, click on the 'Change' button. - </p></li><li><p> - Click on the 'Look in" area that lists the machine name, when you click - here it will open up a selection box. Click on the domain to which the - profile must be accessible. - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.</p></div></li><li><p> - To make the profile capable of being used by anyone select 'Everyone' - </p></li><li><p> - Click OK. The Selection box will close. - </p></li><li><p> - Now click on the 'Ok' button to create the profile in the path you - nominated. - </p></li></ul></div><p> -Done. You now have a profile that can be editted using the samba-3.0.0 -<tt>profiles</tt> 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 -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="itemizedlist"><ul type="disc"><li><p> -This is a security check new to Windows XP (or maybe only -Windows XP service pack 1). It can be disabled via a group policy in -Active Directory. The policy is:</p><p>"Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders"</p><p>...and it should be set to "Enabled". -Does the new version of samba have an Active Directory analogue? If so, -then you may be able to set the policy through this. -</p><p> -If you cannot set group policies in samba, then you may be able to set -the policy locally on each machine. If you want to try this, then do -the following (N.B. I don't know for sure that this will work in the -same way as a domain group policy): -</p></li><li><p> -On the XP workstation log in with an Administrator account. -</p></li><li><p>Click: "Start", "Run"</p></li><li><p>Type: "mmc"</p></li><li><p>Click: "OK"</p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click: File, "Add/Remove Snap-in...", "Add"</p></li><li><p>Double-Click: "Group Policy"</p></li><li><p>Click: "Finish", "Close"</p></li><li><p>Click: "OK"</p></li><li><p>In the "Console Root" window:</p></li><li><p>Expand: "Local Computer Policy", "Computer Configuration",</p></li><li><p>"Administrative Templates", "System", "User Profiles"</p></li><li><p>Double-Click: "Do not check for user ownership of Roaming Profile</p></li><li><p>Folders"</p></li><li><p>Select: "Enabled"</p></li><li><p>Click: OK"</p></li><li><p>Close the whole console. You do not need to save the settings (this - refers to the console settings rather than the policies you have - changed).</p></li><li><p>Reboot</p></li></ul></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879695"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></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 -of MS Windows clients. Probably the more salient reason to NOT mix profiles -is that when logging off an earlier version of MS Windows the older format -of profile contents may overwrite information that belongs to the newer -version resulting in loss of profile information content when that user logs -on again with the newer version of MS Windows. -</p><p> -If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are <span class="emphasis"><em>logon path</em></span> and -<span class="emphasis"><em>logon home</em></span>. -</p><p> -If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879742"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></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><h4 class="title"><a name="id2879759"></a>Windows NT4 Profile Management Tools</h4></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> -Here is a quick guide: -</p><div class="itemizedlist"><ul type="disc"><li><p> -On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'. -</p></li><li><p> -Select a user profile you want to migrate and click on it. -</p><div class="note" 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 -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 'Copy To' button.</p></li><li><p>In the box labelled 'Copy Profile to' add your new path, eg: - <tt>c:\temp\foobar</tt></p></li><li><p>Click on the button labelled 'Change' in the "Permitted to use" box.</p></li><li><p>Click on the group 'Everyone' and then click OK. This closes the - 'chose user' box.</p></li><li><p>Now click OK.</p></li></ul></div><p> -Follow the above for every profile you need to migrate. -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879852"></a>Side bar Notes</h4></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><h4 class="title"><a name="id2879874"></a>moveuser.exe</h4></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><h4 class="title"><a name="id2879890"></a>Get SID</h4></div></div><p> -You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 -Resource Kit. -</p><p> -Windows NT 4.0 stores the local profile information in the registry under -the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList -</p><p> -Under the ProfileList key, there will be subkeys named with the SIDs of the -users who have logged on to this computer. (To find the profile information -for the user whose locally cached profile you want to move, find the SID for -the user with the GetSID.exe utility.) Inside of the appropriate user's -subkey, you will see a string value named ProfileImagePath. -</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879925"></a>Mandatory profiles</h2></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 -user any ability to change the desktop environment then this must be done through -policy settings. See previous chapter. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Under NO circumstances should the profile directory (or it's contents) be made read-only -as this may render the profile un-usable. -</p></div><p> -For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles -also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT -file in the copied profile and rename it to NTUser.MAN. -</p><p> -For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to -affect a mandatory profile. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879970"></a>Creating/Managing Group Profiles</h2></div></div><p> -Most organisations are arranged into departments. There is a nice benenfit in -this fact since usually most users in a department will require the same desktop -applications and the same desktop layout. MS Windows NT4/200x/XP will allow the -use of Group Profiles. A Group Profile is a profile that is created firstly using -a template (example) user. Then using the profile migration tool (see above) the -profile is assigned access rights for the user group that needs to be given access -to the group profile. -</p><p> -The next step is rather important. PLEASE NOTE: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned -the now modified profile. -</p><div class="note" 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><h2 class="title" style="clear: both"><a name="id2880011"></a>Default Profile for Windows Users</h2></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><h3 class="title"><a name="id2880040"></a>MS Windows 9x/Me</h3></div></div><p> -To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly. -</p><p> -To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes. -</p><p> -To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive -<tt>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><h4 class="title"><a name="id2880080"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><p> -When a user logs on to a Windows 9x / Me machine, the local profile path, -<tt>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked -for an existing entry for that user: -</p><p> -If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached -version of the user profile. Windows 9x / Me also checks the user's home directory (or other -specified directory if the location has been modified) on the server for the User Profile. -If a profile exists in both locations, the newer of the two is used. If the User Profile exists -on the server, but does not exist on the local machine, the profile on the server is downloaded -and used. If the User Profile only exists on the local machine, that copy is used. -</p><p> -If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me -machine is used and is copied to a newly created folder for the logged on user. At log off, any -changes that the user made are written to the user's local profile. If the user has a roaming -profile, the changes are written to the user's profile on the server. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2880129"></a>MS Windows NT4 Workstation</h3></div></div><p> -On MS Windows NT4 the default user profile is obtained from the location -<tt>%SystemRoot%\Profiles</tt> which in a default installation will translate to -<tt>C:\WinNT\Profiles</tt>. Under this directory on a clean install there will be -three (3) directories: <tt>Administrator, All Users, Default User</tt>. -</p><p> -The <tt>All Users</tt> directory contains menu settings that are common across all -system users. The <tt>Default User</tt> directory contains menu entries that are -customisable per user depending on the profile settings chosen/created. -</p><p> -When a new user first logs onto an MS Windows NT4 machine a new profile is created from: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td>All Users settings</td></tr><tr><td>Default User settings (contains the default NTUser.DAT file)</td></tr></table><p> -When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain -the following steps are followed in respect of profile handling: -</p><div class="orderedlist"><ol type="1"><li><p> - The users' account information which is obtained during the logon process contains - the location of the users' desktop profile. The profile path may be local to the - machine or it may be located on a network share. If there exists a profile at the location - of the path from the user account, then this profile is copied to the location - <tt>%SystemRoot%\Profiles\%USERNAME%</tt>. This profile then inherits the - settings in the <tt>All Users</tt> profile in the <tt>%SystemRoot%\Profiles</tt> - location. - </p></li><li><p> - If the user account has a profile path, but at it's location a profile does not exist, - then a new profile is created in the <tt>%SystemRoot%\Profiles\%USERNAME%</tt> - directory from reading the <tt>Default User</tt> profile. - </p></li><li><p> - If the NETLOGON share on the authenticating server (logon server) contains a policy file - (<tt>NTConfig.POL</tt>) then it's contents are applied to the <tt>NTUser.DAT</tt> - which is applied to the <tt>HKEY_CURRENT_USER</tt> part of the registry. - </p></li><li><p> - When the user logs out, if the profile is set to be a roaming profile it will be written - out to the location of the profile. The <tt>NTuser.DAT</tt> file is then - re-created from the contents of the <tt>HKEY_CURRENT_USER</tt> contents. - Thus, should there not exist in the NETLOGON share an <tt>NTConfig.POL</tt> at the - next logon, the effect of the provious <tt>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>%SystemRoot%\Profiles\%USERNAME%</tt> location. A roaming profile will -also remain stored in the same way, unless the following registry key is created: -</p><p> -</p><pre class="programlisting"> - HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ - "DeleteRoamingCache"=dword:00000001 -</pre><p> - -In which case, the local copy (in <tt>%SystemRoot%\Profiles\%USERNAME%</tt>) will be -deleted on logout. -</p><p> -Under MS Windows NT4 default locations for common resources (like <tt>My Documents</tt> -may be redirected to a network share by modifying the following registry keys. These changes may be affected -via use of the System Policy Editor (to do so may require that you create your owns template extension -for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first -creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings. -</p><p> -The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows NT4 is: -</p><p> -</p><pre class="programlisting"> - HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\ -</pre><p> -</p><p> -The above hive key contains a list of automatically managed folders. The default entries are: -</p><p> - </p><pre class="programlisting"> - Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - NetHood %USERPROFILE%\NetHood - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - </pre><p> - </p><p> -The registry key that contains the location of the default profile settings is: - -</p><pre class="programlisting"> - HKEY_LOCAL_MACHINE - \SOFTWARE - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders -</pre><p> - -The default entries are: - -</p><pre class="programlisting"> - Common Desktop %SystemRoot%\Profiles\All Users\Desktop - Common Programs %SystemRoot%\Profiles\All Users\Programs - Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu - Common Startup %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup -</pre><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2880513"></a>MS Windows 200x/XP</h3></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 - clients that CAN participate in domain logon processes allows the administrator to create - a global default profile and to enforce it through the use of Group Policy Objects (GPOs). - </p></div><p> -When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from -<tt>C:\Documents and Settings\Default User</tt>. The administrator can modify (or change -the contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum -arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client -workstation. -</p><p> -When MS Windows 200x/XP participate in a domain security context, and if the default user -profile is not found, then the client will search for a default profile in the NETLOGON share -of the authenticating server. ie: In MS Windows parlance: -<tt>%LOGONSERVER%\NETLOGON\Default User</tt> and if one exits there it will copy this -to the workstation to the <tt>C:\Documents and Settings\</tt> under the Windows -login name of the user. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory - should be created at the root of this share and must be called <tt>Default Profile</tt>. - </p></div><p> -If a default profile does not exist in this location then MS Windows 200x/XP will use the local -default profile. -</p><p> -On loging out, the users' desktop profile will be stored to the location specified in the registry -settings that pertain to the user. If no specific policies have been created, or passed to the client -during the login process (as Samba does automatically), then the user's profile will be written to -the local machine only under the path <tt>C:\Documents and Settings\%USERNAME%</tt>. -</p><p> -Those wishing to modify the default behaviour can do so through three methods: -</p><div class="itemizedlist"><ul type="disc"><li><p> - Modify the registry keys on the local machine manually and place the new default profile in the - NETLOGON share root - NOT recommended as it is maintenance intensive. - </p></li><li><p> - Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file - in the root of the NETLOGON share along with the new default profile. - </p></li><li><p> - Create a GPO that enforces this through Active Directory, and place the new default profile - in the NETLOGON share. - </p></li></ul></div><p> -The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows 200x/XP is: -</p><p> -</p><pre class="programlisting"> - HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\ -</pre><p> -</p><p> -The above hive key contains a list of automatically managed folders. The default entries are: -</p><p> - </p><pre class="programlisting"> - Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Cache %USERPROFILE%\Local Settings\Temporary Internet Files - Cookies %USERPROFILE%\Cookies - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - History %USERPROFILE%\Local Settings\History - Local AppData %USERPROFILE%\Local Settings\Application Data - Local Settings %USERPROFILE%\Local Settings - My Pictures %USERPROFILE%\My Documents\My Pictures - NetHood %USERPROFILE%\NetHood - Personal %USERPROFILE%\My Documents - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - Templates %USERPROFILE%\Templates - </pre><p> - </p><p> -There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ. -</p><p> -It makes a huge difference to the speed of handling roaming user profiles if all the folders are -stored on a dedicated location on a network server. This means that it will NOT be necessary to -write the Outlook PST file over the network for every login and logout. -</p><p> -To set this to a network location you could use the following examples: - -</p><pre class="programlisting"> - %LOGONSERVER%\%USERNAME%\Default Folders -</pre><p> - -This would store the folders in the user's home directory under a directory called "Default Folders" - -You could also use: - -</p><pre class="programlisting"> - \\SambaServer\FolderShare\%USERNAME% -</pre><p> - -in which case the default folders will be stored in the server named <span class="emphasis"><em>SambaServer</em></span> -in the share called <span class="emphasis"><em>FolderShare</em></span> under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system. -</p><p> -Please note that once you have created a default profile share, you MUST migrate a user's profile -(default or custom) to it. -</p><p> -MS Windows 200x/XP profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>. -A roaming profile will be cached locally unless the following registry key is created: -</p><p> -</p><pre class="programlisting"> - HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ - "DeleteRoamingCache"=dword:00000001 -</pre><p> - -In which case, the local cache copy will be deleted on logout. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter 19. Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Rafal Szczesniak</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</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><h2 class="title" style="clear: both"><a name="id2878684"></a>Trust Relationship Background</h2></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 -this design significantly impacts the delegation of administrative responsibilities in -large and diverse organisations. -</p><p> -Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means -of circumventing the limitations of the older technologies. Not every organisation is ready -or willing to embrace ADS. For small companies the older NT4 style domain security paradigm -is quite adequate, there thus remains an entrenched user base for whom there is no direct -desire to go through a disruptive change to adopt ADS. -</p><p> -Microsoft introduced with MS Windows NT the ability to allow differing security domains -to affect a mechanism so that users from one domain may be given access rights and privileges -in another domain. The language that describes this capability is couched in terms of -<span class="emphasis"><em>Trusts</em></span>. Specifically, one domain will <span class="emphasis"><em>trust</em></span> the users -from another domain. The domain from which users are available to another security domain is -said to be a trusted domain. The domain in which those users have assigned rights and privileges -is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, -thus if users in both domains are to have privileges and rights in each others' domain, then it is -necessary to establish two (2) relationships, one in each direction. -</p><p> -In an NT4 style MS security domain, all trusts are non-transitive. This means that if there -are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust -relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no -implied trust between the RED and BLUE domains. ie: Relationships are explicit and not -transitive. -</p><p> -New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way -by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE -domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is -an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 -style Interdomain trusts and interoperates with MS Windows 200x ADS -security domains in similar manner to MS Windows NT4 style domains. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881006"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><p> -There are two steps to creating an interdomain trust relationship. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881019"></a>NT4 as the Trusting Domain (ie. creating the trusted account)</h3></div></div><p> -For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. -To affect a two way trust relationship it is necessary for each domain administrator to make -available (for use by an external domain) it's security resources. This is done from the Domain -User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and -"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that -will be able to assign user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password needs to be -typed twice (for standard confirmation). -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881063"></a>NT4 as the Trusted Domain (ie. creating trusted account's password)</h3></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 -Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the -"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in -which must be entered the name of the remote domain as well as the password assigned to that trust. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881087"></a>Configuring Samba NT-style Domain Trusts</h2></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. -</p><p> -Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after -reading this document, that combining Samba-specific parts of what's written below leads to trust -between domains in purely Samba environment. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881114"></a>Samba-3 as the Trusting Domain</h3></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 -called SAMBA, and the remote domain is called RUMBA. The first step -will be to issue this command from your favourite shell: -</p><p> -</p><pre class="screen"> -<tt>deity#</tt> <b><tt>smbpasswd -a -i rumba</tt></b> - New SMB password: XXXXXXXX - Retype SMB password: XXXXXXXX - Added user rumba$ -</pre><p> - -where <i><tt>-a</tt></i> means to add a new account into the -passdb database and <i><tt>-i</tt></i> means: ''create this -account with the InterDomain trust flag'' -</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 -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm -the trust by establishing it from Windows NT Server. -</p><p> -Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. -Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for -the trusted domain name and the relationship password. Type in SAMBA, as this is -your domain name, and the password used at the time of account creation. -Press OK and, if everything went without incident, you will see 'Trusted domain relationship -successfully established' message. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881210"></a>Samba-3 as the Trusted Domain</h3></div></div><p> -This time activities are somewhat reversed. Again, we'll assume that your domain -controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA. -</p><p> -The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC. -</p><p> -Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. -Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted -domain (SAMBA) and password securing the relationship. -</p><p> -The password can be arbitrarily chosen. It is easy to change the password -from the Samba server whenever you want. After confirming the password your account is -ready for use. Now it's Samba's turn. -</p><p> -Using your favourite shell while being logged in as root, issue this command: -</p><p> -<tt>deity# </tt><b><tt>net rpc trustdom establish rumba</tt></b> -</p><p> -You will be prompted for the password you just typed on your Windows NT4 Server box. -Do not worry if you see an error message that mentions a returned code of -NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the -password you gave is correct and the NT4 Server says the account is -ready for interdomain connection and not for ordinary -connection. After that, be patient it can take a while (especially -in large networks), you should see the 'Success' message. Congratulations! Your trust -relationship has just been established. -</p><div class="note" 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>secrets.tdb</tt> file. -</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="pam"></a>Chapter 20. PAM Configuration for Centrally Managed Authentication</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (Jun 21 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2880956"></a>Samba and PAM</h2></div></div><p> -A number of Unix systems (eg: Sun Solaris), as well as the -xxxxBSD family and Linux, now utilize the Pluggable Authentication -Modules (PAM) facility to provide all authentication, -authorization and resource control services. Prior to the -introduction of PAM, a decision to use an alternative to -the system password database (<tt>/etc/passwd</tt>) -would require the provision of alternatives for all programs that provide -security services. Such a choice would involve provision of -alternatives to such programs as: <b>login</b>, -<b>passwd</b>, <b>chown</b>, etc. -</p><p> -PAM provides a mechanism that disconnects these security programs -from the underlying authentication/authorization infrastructure. -PAM is configured either through one file <tt>/etc/pam.conf</tt> (Solaris), -or by editing individual files that are located in <tt>/etc/pam.d</tt>. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - If the PAM authentication module (loadable link library file) is located in the - default location then it is not necessary to specify the path. In the case of - Linux, the default location is <tt>/lib/security</tt>. If the module - is located outside the default then the path must be specified as: - - </p><pre class="programlisting"> - auth required /other_path/pam_strange_module.so - </pre><p> - </p></div><p> -The following is an example <tt>/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>pam_pwdb.so</tt>. -</p><pre class="programlisting"> - #%PAM-1.0 - # The PAM configuration file for the `login' service - # - auth required pam_securetty.so - auth required pam_nologin.so - # auth required pam_dialup.so - # auth optional pam_mail.so - auth required pam_pwdb.so shadow md5 - # account requisite pam_time.so - account required pam_pwdb.so - session required pam_pwdb.so - # session optional pam_lastlog.so - # password required pam_cracklib.so retry=3 - password required pam_pwdb.so shadow md5 -</pre><p> -PAM allows use of replacable modules. Those available on a -sample system include: -</p><p><tt>$</tt><b><tt>/bin/ls /lib/security</tt></b> -</p><pre class="programlisting"> - pam_access.so pam_ftp.so pam_limits.so - pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so - pam_cracklib.so pam_group.so pam_listfile.so - pam_nologin.so pam_rootok.so pam_tally.so - pam_deny.so pam_issue.so pam_mail.so - pam_permit.so pam_securetty.so pam_time.so - pam_dialup.so pam_lastlog.so pam_mkhomedir.so - pam_pwdb.so pam_shells.so pam_unix.so - pam_env.so pam_ldap.so pam_motd.so - pam_radius.so pam_smbpass.so pam_unix_acct.so - pam_wheel.so pam_unix_auth.so pam_unix_passwd.so - pam_userdb.so pam_warn.so pam_unix_session.so -</pre><p> -The following example for the login program replaces the use of -the <tt>pam_pwdb.so</tt> module which uses the system -password database (<tt>/etc/passwd</tt>, -<tt>/etc/shadow</tt>, <tt>/etc/group</tt>) with -the module <tt>pam_smbpass.so</tt> which uses the Samba -database which contains the Microsoft MD4 encrypted password -hashes. This database is stored in either -<tt>/usr/local/samba/private/smbpasswd</tt>, -<tt>/etc/samba/smbpasswd</tt>, or in -<tt>/etc/samba.d/smbpasswd</tt>, depending on the -Samba implementation for your Unix/Linux system. The -<tt>pam_smbpass.so</tt> module is provided by -Samba version 2.2.1 or later. It can be compiled by specifying the -<b>--with-pam_smbpass</b> options when running Samba's -<tt>configure</tt> script. For more information -on the <tt>pam_smbpass</tt> module, see the documentation -in the <tt>source/pam_smbpass</tt> directory of the Samba -source distribution. -</p><pre class="programlisting"> - #%PAM-1.0 - # The PAM configuration file for the `login' service - # - auth required pam_smbpass.so nodelay - account required pam_smbpass.so nodelay - session required pam_smbpass.so nodelay - password required pam_smbpass.so nodelay -</pre><p> -The following is the PAM configuration file for a particular -Linux system. The default condition uses <tt>pam_pwdb.so</tt>. -</p><pre class="programlisting"> - #%PAM-1.0 - # The PAM configuration file for the `samba' service - # - auth required pam_pwdb.so nullok nodelay shadow audit - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required pam_pwdb.so shadow md5 -</pre><p> -In the following example the decision has been made to use the -smbpasswd database even for basic samba authentication. Such a -decision could also be made for the passwd program and would -thus allow the smbpasswd passwords to be changed using the passwd -program. -</p><pre class="programlisting"> - #%PAM-1.0 - # The PAM configuration file for the `samba' service - # - auth required pam_smbpass.so nodelay - account required pam_pwdb.so audit nodelay - session required pam_pwdb.so nodelay - password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf -</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>PAM allows stacking of authentication mechanisms. It is -also possible to pass information obtained within one PAM module through -to the next module in the PAM stack. Please refer to the documentation for -your particular system implementation for details regarding the specific -capabilities of PAM in this environment. Some Linux implmentations also -provide the <tt>pam_stack.so</tt> module that allows all -authentication to be configured in a single central file. The -<tt>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 class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881738"></a>PAM Configuration in smb.conf</h3></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> -When Samba is configured to enable PAM support (i.e. -<tt>--with-pam</tt>), this parameter will -control whether or not Samba should obey PAM's account -and session management directives. The default behavior -is to use PAM for clear text authentication only and to -ignore any account or session management. Note that Samba always -ignores PAM for authentication in the case of -<a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>. -The reason is that PAM modules cannot support the challenge/response -authentication mechanism needed in the presence of SMB -password encryption. -</p><p>Default: <b>obey pam restrictions = no</b></p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881795"></a>Password Synchronisation using pam_smbpass.so</h3></div></div><p> -pam_smbpass is a PAM module which can be used on conforming systems to -keep the smbpasswd (Samba password) database in sync with the unix -password file. PAM (Pluggable Authentication Modules) is an API supported -under some Unices, such as Solaris, HPUX and Linux, that provides a -generic interface to authentication mechanisms. -</p><p> -For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/ -</p><p> -This module authenticates a local smbpasswd user database. If you require -support for authenticating against a remote SMB server, or if you're -concerned about the presence of suid root binaries on your system, it is -recommended that you use pam_winbind instead. -</p><pre class="programlisting"> -Options recognized by this module are as follows: - - debug - log more debugging info - audit - like debug, but also logs unknown usernames - use_first_pass - don't prompt the user for passwords; - take them from PAM_ items instead - try_first_pass - try to get the password from a previous - PAM module, fall back to prompting the user - use_authtok - like try_first_pass, but *fail* if the new - PAM_AUTHTOK has not been previously set. - (intended for stacking password modules only) - not_set_pass - don't make passwords used by this module - available to other modules. - nodelay - don't insert ~1 second delays on authentication - failure. - nullok - null passwords are allowed. - nonull - null passwords are not allowed. Used to - override the Samba configuration. - migrate - only meaningful in an "auth" context; - used to update smbpasswd file with a - password used for successful authentication. - smbconf=< file > - specify an alternate path to the smb.conf - file. -</pre><pre class="programlisting"> -Thanks go to the following people: - - * Andrew Morgan < morgan@transmeta.com >, for providing the Linux-PAM - framework, without which none of this would have happened - - * Christian Gafton < gafton@redhat.com > and Andrew Morgan again, for the - pam_pwdb module upon which pam_smbpass was originally based - - * Luke Leighton < lkcl@switchboard.net > for being receptive to the idea, - and for the occasional good-natured complaint about the project's status - that keep me working on it :) - - * and of course, all the other members of the Samba team - <http://www.samba.org/samba/team.html>, for creating a great product - and for giving this project a purpose - - --------------------- - Stephen Langasek < vorlon@netexpress.net > -</pre><p> -The following are examples of the use of pam_smbpass.so in the format of Linux -<tt>/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><h4 class="title"><a name="id2881907"></a>Password Synchonisation Configuration</h4></div></div><p> -A sample PAM configuration that shows the use of pam_smbpass to make -sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow) -is changed. Useful when an expired password might be changed by an -application (such as ssh). -</p><pre class="programlisting"> - #%PAM-1.0 - # password-sync - # - auth requisite pam_nologin.so - auth required pam_unix.so - account required pam_unix.so - password requisite pam_cracklib.so retry=3 - password requisite pam_unix.so shadow md5 use_authtok try_first_pass - password required pam_smbpass.so nullok use_authtok try_first_pass - session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2881941"></a>Password Migration Configuration</h4></div></div><p> -A sample PAM configuration that shows the use of pam_smbpass to migrate -from plaintext to encrypted passwords for Samba. Unlike other methods, -this can be used for users who have never connected to Samba shares: -password migration takes place when users ftp in, login using ssh, pop -their mail, etc. -</p><pre class="programlisting"> - #%PAM-1.0 - # password-migration - # - auth requisite pam_nologin.so - # pam_smbpass is called IFF pam_unix succeeds. - auth requisite pam_unix.so - auth optional pam_smbpass.so migrate - account required pam_unix.so - password requisite pam_cracklib.so retry=3 - password requisite pam_unix.so shadow md5 use_authtok try_first_pass - password optional pam_smbpass.so nullok use_authtok try_first_pass - session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2881978"></a>Mature Password Configuration</h4></div></div><p> -A sample PAM configuration for a 'mature' smbpasswd installation. -private/smbpasswd is fully populated, and we consider it an error if -the smbpasswd doesn't exist or doesn't match the Unix password. -</p><pre class="programlisting"> - #%PAM-1.0 - # password-mature - # - auth requisite pam_nologin.so - auth required pam_unix.so - account required pam_unix.so - password requisite pam_cracklib.so retry=3 - password requisite pam_unix.so shadow md5 use_authtok try_first_pass - password required pam_smbpass.so use_authtok use_first_pass - session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2882011"></a>Kerberos Password Integration Configuration</h4></div></div><p> -A sample PAM configuration that shows pam_smbpass used together with -pam_krb5. This could be useful on a Samba PDC that is also a member of -a Kerberos realm. -</p><pre class="programlisting"> - #%PAM-1.0 - # kdc-pdc - # - auth requisite pam_nologin.so - auth requisite pam_krb5.so - auth optional pam_smbpass.so migrate - account required pam_krb5.so - password requisite pam_cracklib.so retry=3 - password optional pam_smbpass.so nullok use_authtok try_first_pass - password required pam_krb5.so use_authtok try_first_pass - session required pam_krb5.so -</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882047"></a>Distributed Authentication</h2></div></div><p> -The astute administrator will realize from this that the -combination of <tt>pam_smbpass.so</tt>, -<b>winbindd</b>, and a distributed -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed -user/password database that can also be used by all -PAM (eg: Linux) aware programs and applications. This arrangement -can have particularly potent advantages compared with the -use of Microsoft Active Directory Service (ADS) in so far as -reduction of wide area network authentication traffic. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="VFS"></a>Chapter 21. Stackable VFS modules</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Alexander Bokovoy</h3></div></div><div><div class="author"><h3 class="author">Tim Potter</h3></div></div><div><div class="author"><h3 class="author">Simo Sorce</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881331"></a>Introduction and configuration</h2></div></div><p> -Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. -Samba passes each request to access the unix file system thru the loaded VFS modules. -This chapter covers all the modules that come with the samba source and references to -some external modules. -</p><p> -You may have problems to compile these modules, as shared libraries are -compiled and linked in different ways on different systems. -They currently have been tested against GNU/linux and IRIX. -</p><p> -To use the VFS modules, create a share similar to the one below. The -important parameter is the <b>vfs object</b> parameter which must point to -the exact pathname of the shared library objects. For example, to log all access -to files and use a recycle bin: - -</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><p> -</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><h2 class="title" style="clear: both"><a name="id2882249"></a>Included modules</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882256"></a>audit</h3></div></div><p>A simple module to audit file access to the syslog -facility. The following operations are logged: -</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><h3 class="title"><a name="id2882295"></a>extd_audit</h3></div></div><p> -This module is identical with the <span class="emphasis"><em>audit</em></span> module above except -that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. -</p><p> -The logging information that will be written to the smbd log file is controlled by -the <span class="emphasis"><em>log level</em></span> parameter in <tt>smb.conf</tt>. The -following information will be recorded: -</p><div class="table"><a name="id2882333"></a><p class="title"><b>Table 21.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><h3 class="title"><a name="id2882416"></a>recycle</h3></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><p>Supported options: -</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><p> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882554"></a>netatalk</h3></div></div><p> -A netatalk module, that will ease co-existence of samba and -netatalk file sharing services. -</p><p>Advantages compared to the old netatalk module: -</p><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 share in smb.conf 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><h2 class="title" style="clear: both"><a name="id2882592"></a>VFS modules available elsewhere</h2></div></div><p> -This section contains a listing of various other VFS modules that -have been posted but don't currently reside in the Samba CVS -tree for one reason or another (e.g. it is easy for the maintainer -to have his or her own CVS tree). -</p><p> -No statemets 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><h3 class="title"><a name="id2882614"></a>DatabaseFS</h3></div></div><p> -URL: <a href="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" target="_top">http://www.css.tayloru.edu/~elorimer/databasefs/index.php</a> -</p><p>By <a href="mailto:elorimer@css.tayloru.edu" target="_top">Eric Lorimer</a>.</p><p> -I have created a VFS module which implements a fairly complete read-only -filesystem. It presents information from a database as a filesystem in -a modular and generic way to allow different databases to be used -(originally designed for organizing MP3s under directories such as -"Artists," "Song Keywords," etc... I have since applied it to a student -roster database very easily). The directory structure is stored in the -database itself and the module makes no assumptions about the database -structure beyond the table it requires to run. -</p><p> -Any feedback would be appreciated: comments, suggestions, patches, -etc... If nothing else, hopefully it might prove useful for someone -else who wishes to create a virtual filesystem. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882669"></a>vscan</h3></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. -samba-vscan supports various virus scanners and is maintained -by Rainer Link. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="msdfs"></a>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author">Shirish Kalele</h3><div class="affiliation"><span class="orgname">Samba Team & Veritas Software<br></span><div class="address"><p><br> - <tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882214"></a>Instructions</h2></div></div><p>The Distributed File System (or Dfs) provides a means of - separating the logical view of files and directories that users - see from the actual physical locations of these resources on the - network. It allows for higher availability, smoother storage expansion, - load balancing etc. For more information about Dfs, refer to <a href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top"> - Microsoft documentation</a>. </p><p>This document explains how to host a Dfs tree on a Unix - machine (for Dfs-aware clients to browse) using Samba.</p><p>To enable SMB-based DFS for Samba, configure it with the - <i><tt>--with-msdfs</tt></i> option. Once built, a - Samba server can be made a Dfs server by setting the global - boolean <a href="smb.conf.5.html#HOSTMSDFS" target="_top"><i><tt> - host msdfs</tt></i></a> parameter in the <tt>smb.conf - </tt> file. You designate a share as a Dfs root using the share - level boolean <a href="smb.conf.5.html#MSDFSROOT" target="_top"><i><tt> - msdfs root</tt></i></a> parameter. A Dfs root directory on - Samba hosts Dfs links in the form of symbolic links that point - to other servers. For example, a symbolic link - <tt>junction->msdfs:storage1\share1</tt> in - the share directory acts as the Dfs junction. When Dfs-aware - clients attempt to access the junction link, they are redirected - to the storage location (in this case, \\storage1\share1).</p><p>Dfs trees on Samba work with all Dfs-aware clients ranging - from Windows 95 to 2000.</p><p>Here's an example of setting up a Dfs tree on a Samba - server.</p><pre class="programlisting"> -# The smb.conf file: -[global] - netbios name = SAMBA - host msdfs = yes - -[dfs] - path = /export/dfsroot - msdfs root = yes - </pre><p>In the /export/dfsroot directory we set up our dfs links to - other servers on the network.</p><p><tt>root# </tt><b><tt>cd /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chown root /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chmod 755 /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:storageA\\shareA linka</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b></p><p>You should set up the permissions and ownership of - the directory acting as the Dfs root such that only designated - users can create, delete or modify the msdfs links. Also note - that symlink names should be all lowercase. This limitation exists - to have Samba avoid trying all the case combinations to get at - the link name. Finally set up the symbolic links to point to the - network shares you want, and start Samba.</p><p>Users on Dfs-aware clients can now browse the Dfs tree - on the Samba server at \\samba\dfs. Accessing - links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882961"></a>Notes</h3></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><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter 23. Integrating MS Windows networks with Samba</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</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 -NetBIOS over TCP/IP then this section may help you to resolve networking problems. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> - NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS - over Logical Link Control (LLC). On modern networks it is highly advised - to NOT run NetBEUI at all. Note also that there is NO such thing as - NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension. -</p></div><p> -Since the introduction of MS Windows 2000 it is possible to run MS Windows networking -without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS -name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over -TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then -the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic). -</p></div><p> -When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that -disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires -Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). -Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882745"></a>Name Resolution in a pure Unix/Linux world</h2></div></div><p> -The key configuration files covered in this section are: -</p><div class="itemizedlist"><ul type="disc"><li><p><tt>/etc/hosts</tt></p></li><li><p><tt>/etc/resolv.conf</tt></p></li><li><p><tt>/etc/host.conf</tt></p></li><li><p><tt>/etc/nsswitch.conf</tt></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883178"></a><tt>/etc/hosts</tt></h3></div></div><p> -Contains a static list of IP Addresses and names. -eg: -</p><pre class="programlisting"> - 127.0.0.1 localhost localhost.localdomain - 192.168.1.1 bigbox.caldera.com bigbox alias4box -</pre><p> -The purpose of <tt>/etc/hosts</tt> is to provide a -name resolution mechanism so that uses do not need to remember -IP addresses. -</p><p> -Network packets that are sent over the physical network transport -layer communicate not via IP addresses but rather using the Media -Access Control address, or MAC address. IP Addresses are currently -32 bits in length and are typically presented as four (4) decimal -numbers that are separated by a dot (or period). eg: 168.192.1.1 -</p><p> -MAC Addresses use 48 bits (or 6 bytes) and are typically represented -as two digit hexadecimal numbers separated by colons. eg: -40:8e:0a:12:34:56 -</p><p> -Every network interfrace must have an MAC address. Associated with -a MAC address there may be one or more IP addresses. There is NO -relationship between an IP address and a MAC address, all such assignments -are arbitary or discretionary in nature. At the most basic level all -network communications takes place using MAC addressing. Since MAC -addresses must be globally unique, and generally remains fixed for -any particular interface, the assignment of an IP address makes sense -from a network management perspective. More than one IP address can -be assigned per MAC address. One address must be the primary IP address, -this is the address that will be returned in the ARP reply. -</p><p> -When a user or a process wants to communicate with another machine -the protocol implementation ensures that the "machine name" or "host -name" is resolved to an IP address in a manner that is controlled -by the TCP/IP configuration control files. The file -<tt>/etc/hosts</tt> is one such file. -</p><p> -When the IP address of the destination interface has been -determined a protocol called ARP/RARP is used to identify -the MAC address of the target interface. ARP stands for Address -Resolution Protocol, and is a broadcast oriented method that -uses UDP (User Datagram Protocol) to send a request to all -interfaces on the local network segment using the all 1's MAC -address. Network interfaces are programmed to respond to two -MAC addresses only; their own unique address and the address -ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will -contain the MAC address and the primary IP address for each -interface. -</p><p> -The <tt>/etc/hosts</tt> file is foundational to all -Unix/Linux TCP/IP installations and as a minumum will contain -the localhost and local network interface IP addresses and the -primary names by which they are known within the local machine. -This file helps to prime the pump so that a basic level of name -resolution can exist before any other method of name resolution -becomes available. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883316"></a><tt>/etc/resolv.conf</tt></h3></div></div><p> -This file tells the name resolution libraries: -</p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine - belongs - </p></li><li><p>The name(s) of any domains that should be - automatically searched when trying to resolve unqualified - host names to their IP address - </p></li><li><p>The name or IP address of available Domain - Name Servers that may be asked to perform name to address - translation lookups - </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883360"></a><tt>/etc/host.conf</tt></h3></div></div><p> -<tt>/etc/host.conf</tt> is the primary means by -which the setting in /etc/resolv.conf may be affected. It is a -critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is: -</p><pre class="programlisting"> - order hosts,bind - multi on -</pre><p> -then both addresses should be returned. Please refer to the -man page for host.conf for further details. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883403"></a><tt>/etc/nsswitch.conf</tt></h3></div></div><p> -This file controls the actual name resolution targets. The -file typically has resolver object specifications as follows: -</p><pre class="programlisting"> - # /etc/nsswitch.conf - # - # Name Service Switch configuration file. - # - - passwd: compat - # Alternative entries for password authentication are: - # passwd: compat files nis ldap winbind - shadow: compat - group: compat - - hosts: files nis dns - # Alternative entries for host name resolution are: - # hosts: files dns nis nis+ hesoid db compat ldap wins - networks: nis files dns - - ethers: nis files - protocols: nis files - rpc: nis files - services: nis files -</pre><p> -Of course, each of these mechanisms requires that the appropriate -facilities and/or services are correctly configured. -</p><p> -It should be noted that unless a network request/message must be -sent, TCP/IP networks are silent. All TCP/IP communications assumes a -principal of speaking only when necessary. -</p><p> -Starting with version 2.2.0 samba has Linux support for extensions to -the name service switch infrastructure so that linux clients will -be able to obtain resolution of MS Windows NetBIOS names to IP -Addresses. To gain this functionality Samba needs to be compiled -with appropriate arguments to the make command (ie: <b>make -nsswitch/libnss_wins.so</b>). The resulting library should -then be installed in the <tt>/lib</tt> directory and -the "wins" parameter needs to be added to the "hosts:" line in -the <tt>/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><h2 class="title" style="clear: both"><a name="id2883498"></a>Name resolution as used within MS Windows networking</h2></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", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names -are exactly 16 characters in length. The 16th character is reserved. -It is used to store a one byte value that indicates service level -information for the NetBIOS name that is registered. A NetBIOS machine -name is therefore registered for each service type that is provided by -the client/server. -</p><p> -The following are typical NetBIOS name/service type registrations: -</p><pre class="programlisting"> - Unique NetBIOS Names: - MACHINENAME<00> = Server Service is running on MACHINENAME - MACHINENAME<03> = Generic Machine Name (NetBIOS name) - MACHINENAME<20> = LanMan Server service is running on MACHINENAME - WORKGROUP<1b> = Domain Master Browser - - Group Names: - WORKGROUP<03> = Generic Name registered by all members of WORKGROUP - WORKGROUP<1c> = Domain Controllers / Netlogon Servers - WORKGROUP<1d> = Local Master Browsers - WORKGROUP<1e> = Internet Name Resolvers -</pre><p> -It should be noted that all NetBIOS machines register their own -names as per the above. This is in vast contrast to TCP/IP -installations where traditionally the system administrator will -determine in the /etc/hosts or in the DNS database what names -are associated with each IP address. -</p><p> -One further point of clarification should be noted, the <tt>/etc/hosts</tt> -file and the DNS records do not provide the NetBIOS name type information -that MS Windows clients depend on to locate the type of service that may -be needed. An example of this is what happens when an MS Windows client -wants to locate a domain logon server. It finds this service and the IP -address of a server that provides it by performing a lookup (via a -NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each -IP address that is returned in the enumerated list of IP addresses. Which -ever machine first replies then ends up providing the logon services. -</p><p> -The name "workgroup" or "domain" really can be confusing since these -have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates -that the primary nature of the network environment is that of a -peer-to-peer design. In a WORKGROUP all machines are responsible for -their own security, and generally such security is limited to use of -just a password (known as SHARE MODE security). In most situations -with peer-to-peer networking the users who control their own machines -will simply opt to have no security at all. It is possible to have -USER MODE security in a WORKGROUP environment, thus requiring use -of a user name and a matching password. -</p><p> -MS Windows networking is thus predetermined to use machine names -for all local and remote machine message passing. The protocol used is -called Server Message Block (SMB) and this is implemented using -the NetBIOS protocol (Network Basic Input Output System). NetBIOS can -be encapsulated using LLC (Logical Link Control) protocol - in which case -the resulting protocol is called NetBEUI (Network Basic Extended User -Interface). NetBIOS can also be run over IPX (Internetworking Packet -Exchange) protocol as used by Novell NetWare, and it can be run -over TCP/IP protocols - in which case the resulting protocol is called -NBT or NetBT, the NetBIOS over TCP/IP. -</p><p> -MS Windows machines use a complex array of name resolution mechanisms. -Since we are primarily concerned with TCP/IP this demonstration is -limited to this area. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883030"></a>The NetBIOS Name Cache</h3></div></div><p> -All MS Windows machines employ an in memory buffer in which is -stored the NetBIOS names and IP addresses for all external -machines that that machine has communicated with over the -past 10-15 minutes. It is more efficient to obtain an IP address -for a machine from the local cache than it is to go through all the -configured name resolution mechanisms. -</p><p> -If a machine whose name is in the local name cache has been shut -down before the name had been expired and flushed from the cache, then -an attempt to exchange a message with that machine will be subject -to time-out delays. i.e.: Its name is in the cache, so a name resolution -lookup will succeed, but the machine can not respond. This can be -frustrating for users - but it is a characteristic of the protocol. -</p><p> -The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this -is called "nmblookup". -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883069"></a>The LMHOSTS file</h3></div></div><p> -This file is usually located in MS Windows NT 4.0 or -2000 in <tt>C:\WINNT\SYSTEM32\DRIVERS\ETC</tt> and contains -the IP Address and the machine name in matched pairs. The -<tt>LMHOSTS</tt> file performs NetBIOS name -to IP address mapping. -</p><p> -It typically looks like: -</p><pre class="programlisting"> - # Copyright (c) 1998 Microsoft Corp. - # - # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS - # over TCP/IP) stack for Windows98 - # - # This file contains the mappings of IP addresses to NT computernames - # (NetBIOS) names. Each entry should be kept on an individual line. - # The IP address should be placed in the first column followed by the - # corresponding computername. The address and the comptername - # should be separated by at least one space or tab. The "#" character - # is generally used to denote the start of a comment (see the exceptions - # below). - # - # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts - # files and offers the following extensions: - # - # #PRE - # #DOM:<domain> - # #INCLUDE <filename> - # #BEGIN_ALTERNATE - # #END_ALTERNATE - # \0xnn (non-printing character support) - # - # Following any entry in the file with the characters "#PRE" will cause - # the entry to be preloaded into the name cache. By default, entries are - # not preloaded, but are parsed only after dynamic name resolution fails. - # - # Following an entry with the "#DOM:<domain>" tag will associate the - # entry with the domain specified by <domain>. This affects how the - # browser and logon services behave in TCP/IP environments. To preload - # the host name associated with #DOM entry, it is necessary to also add a - # #PRE to the line. The <domain> is always preloaded although it will not - # be shown when the name cache is viewed. - # - # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) - # software to seek the specified <filename> and parse it as if it were - # local. <filename> is generally a UNC-based name, allowing a - # centralized lmhosts file to be maintained on a server. - # It is ALWAYS necessary to provide a mapping for the IP address of the - # server prior to the #INCLUDE. This mapping must use the #PRE directive. - # In addtion the share "public" in the example below must be in the - # LanManServer list of "NullSessionShares" in order for client machines to - # be able to read the lmhosts file successfully. This key is under - # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares - # in the registry. Simply add "public" to the list found there. - # - # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE - # statements to be grouped together. Any single successful include - # will cause the group to succeed. - # - # Finally, non-printing characters can be embedded in mappings by - # first surrounding the NetBIOS name in quotations, then using the - # \0xnn notation to specify a hex value for a non-printing character. - # - # The following example illustrates all of these extensions: - # - # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC - # 102.54.94.102 "appname \0x14" #special app server - # 102.54.94.123 popular #PRE #source server - # 102.54.94.117 localsrv #PRE #needed for the include - # - # #BEGIN_ALTERNATE - # #INCLUDE \\localsrv\public\lmhosts - # #INCLUDE \\rhino\public\lmhosts - # #END_ALTERNATE - # - # In the above example, the "appname" server contains a special - # character in its name, the "popular" and "localsrv" server names are - # preloaded, and the "rhino" server name is specified so it can be used - # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" - # system is unavailable. - # - # Note that the whole file is parsed including comments on each lookup, - # so keeping the number of comments to a minimum will improve performance. - # Therefore it is not advisable to simply add lmhosts file entries onto the - # end of this file. -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883112"></a>HOSTS file</h3></div></div><p> -This file is usually located in MS Windows NT 4.0 or 2000 in -<tt>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>/etc/hosts</tt> file. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883144"></a>DNS Lookup</h3></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 -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name -that is the subject of a name lookup is not found in the NetBIOS name -cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to -Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the -WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast -lookup is used. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883156"></a>WINS Lookup</h3></div></div><p> -A WINS (Windows Internet Name Server) service is the equivaent of the -rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores -the names and IP addresses that are registered by a Windows client -if the TCP/IP setup has been given at least one WINS Server IP Address. -</p><p> -To configure Samba to be a WINS server the following parameter needs -to be added to the <tt>smb.conf</tt> file: -</p><pre class="programlisting"> - wins support = Yes -</pre><p> -To configure Samba to use a WINS server the following parameters are -needed in the <tt>smb.conf</tt> file: -</p><pre class="programlisting"> - wins support = No - wins server = xxx.xxx.xxx.xxx -</pre><p> -where <i><tt>xxx.xxx.xxx.xxx</tt></i> is the IP address -of the WINS server. -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securing-samba"></a>Chapter 24. Securing Samba</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">17 March 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883603"></a>Introduction</h2></div></div><p> -This note was attached to the Samba 2.2.8 release notes as it contained an -important security fix. The information contained here applies to Samba -installations in general. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883619"></a>Using host based protection</h2></div></div><p> -In many installations of Samba the greatest threat comes for outside -your immediate network. By default Samba will accept connections from -any host, which means that if you run an insecure version of Samba on -a host that is directly connected to the Internet you can be -especially vulnerable. -</p><p> -One of the simplest fixes in this case is to use the <b>hosts allow</b> and -<b>hosts deny</b> options in the Samba <tt>smb.conf</tt> configuration file to only -allow access to your server from a specific range of hosts. An example -might be: -</p><pre class="programlisting"> - hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 - hosts deny = 0.0.0.0/0 -</pre><p> -The above will only allow SMB connections from 'localhost' (your own -computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused as soon -as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884070"></a>Using interface protection</h2></div></div><p> -By default Samba will accept connections on any network interface that -it finds on your system. That means if you have a ISDN line or a PPP -connection to the Internet then Samba will accept connections on those -links. This may not be what you want. -</p><p> -You can change this behaviour using options like the following: -</p><pre class="programlisting"> - interfaces = eth* lo - bind interfaces only = yes -</pre><p> -This tells Samba to only listen for connections on interfaces with a -name starting with 'eth' such as eth0, eth1, plus on the loopback -interface called 'lo'. The name you will need to use depends on what -OS you are using, in the above I used the common name for Ethernet -adapters on Linux. -</p><p> -If you use the above and someone tries to make a SMB connection to -your host over a PPP interface called 'ppp0' then they will get a TCP -connection refused reply. In that case no Samba code is run at all as -the operating system has been told not to pass connections from that -interface to any samba process. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884122"></a>Using a firewall</h2></div></div><p> -Many people use a firewall to deny access to services that they don't -want exposed outside their network. This can be a very good idea, -although I would recommend using it in conjunction with the above -methods so that you are protected even if your firewall is not active -for some reason. -</p><p> -If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following: -</p><pre class="programlisting"> - UDP/137 - used by nmbd - UDP/138 - used by nmbd - TCP/139 - used by smbd - TCP/445 - used by smbd -</pre><p> -The last one is important as many older firewall setups may not be -aware of it, given that this port was only added to the protocol in -recent years. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884164"></a>Using a IPC$ share deny</h2></div></div><p> -If the above methods are not suitable, then you could also place a -more specific deny on the IPC$ share that is used in the recently -discovered security hole. This allows you to offer access to other -shares while denying access to IPC$ from potentially untrustworthy -hosts. -</p><p> -To do that you could use: -</p><pre class="programlisting"> - [ipc$] - hosts allow = 192.168.115.0/24 127.0.0.1 - hosts deny = 0.0.0.0/0 -</pre><p> -this would tell Samba that IPC$ connections are not allowed from -anywhere but the two listed places (localhost and a local -subnet). Connections to other shares would still be allowed. As the -IPC$ share is the only share that is always accessible anonymously -this provides some level of protection against attackers that do not -know a username/password for your host. -</p><p> -If you use this method then clients will be given a 'access denied' -reply when they try to access the IPC$ share. That means that those -clients will not be able to browse shares, and may also be unable to -access some other resources. -</p><p> -This is not recommended unless you cannot use one of the other -methods listed above for some reason. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883724"></a>NTLMv2 Security</h2></div></div><p> -To configure NTLMv2 authentication the following registry keys are worth knowing about: -</p><p> -</p><pre class="programlisting"> - [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] - "lmcompatibilitylevel"=dword:00000003 - - 0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication, - use NTLMv2 session security if the server supports it. Domain - controllers accept LM, NTLM and NTLMv2 authentication. - - [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] - "NtlmMinClientSec"=dword:00080000 - - 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><p> -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883760"></a>Upgrading Samba</h2></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><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unicode"></a>Chapter 25. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">TAKAHASHI Motonobu</h3><div class="affiliation"><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884358"></a>What are charsets and unicode?</h2></div></div><p> -Computers communicate in numbers. In texts, each number will be -translated to a corresponding letter. The meaning that will be assigned -to a certain number depends on the <span class="emphasis"><em>character set(charset) -</em></span> that is used. -A charset can be seen as a table that is used to translate numbers to -letters. Not all computers use the same charset (there are charsets -with German umlauts, Japanese characters, etc). Usually a charset contains -256 characters, which means that storing a character with it takes -exactly one byte. </p><p> -There are also charsets that support even more characters, -but those need twice(or even more) as much storage space. These -charsets can contain <b>256 * 256 = 65536</b> characters, which -is more then all possible characters one could think of. They are called -multibyte charsets (because they use more then one byte to -store one character). -</p><p> -A standardised multibyte charset is unicode, info is available at -<a href="http://www.unicode.org/" target="_top">www.unicode.org</a>. -A big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are -communicating. -</p><p>Old windows clients used to use single-byte charsets, named -'codepages' by microsoft. However, there is no support for -negotiating the charset to be used in the smb protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. -Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884428"></a>Samba and charsets</h2></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">unix charset</span></dt><dd><p> - This is the charset used internally by your operating system. - The default is <tt>ASCII</tt>, which is fine for most - systems. - </p></dd><dt><span class="term">display charset</span></dt><dd><p>This is the charset samba will use to print messages - on your screen. It should generally be the same as the <b>unix charset</b>. - </p></dd><dt><span class="term">dos charset</span></dt><dd><p>This is the charset samba uses when communicating with - DOS and Windows 9x clients. It will talk unicode to all newer clients. - The default depends on the charsets you have installed on your system. - Run <b>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><h2 class="title" style="clear: both"><a name="id2884517"></a>Conversion from old names</h2></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>#</tt><b><tt>find <i><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><h2 class="title" style="clear: both"><a name="id2884562"></a>Japanese charsets</h2></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 <b>mangling method = -hash</b></p></li><li><p>There are various iconv() implementations around and not -all of them work equally well. glibc2's iconv() has a critical problem -in CP932. libiconv-1.8 works with CP932 but still has some problems and -does not work with EUC-JP.</p></li><li><p>You should set <b>dos charset = CP932</b>, not -Shift_JIS, SJIS...</p></li><li><p>Currently only <b>unix charset = CP932</b> -will work (but still has some problems...) because of iconv() issues. -<b>unix charset = EUC-JP</b> doesn't work well because of -iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <b>unix charset -= UTF8-MAC/CAP/HEX/JIS*</b></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><h2 class="title"><a name="locking"></a>Chapter 26. File and Record Locking</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884210"></a>Discussion</h2></div></div><p> -One area which sometimes causes trouble is locking. -</p><p> -There are two types of locking which need to be performed by a SMB server. -The first is <span class="emphasis"><em>record locking</em></span> which allows a client to lock -a range of bytes in a open file. The second is the <span class="emphasis"><em>deny modes</em></span> -that are specified when a file is open. -</p><p> -Record locking semantics under Unix is very different from record locking under -Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix -system call to implement proper record locking between different Samba clients. -This can not be fully correct due to several reasons. The simplest is the fact -that a Windows client is allowed to lock a byte range up to 2^32 or 2^64, -depending on the client OS. The unix locking only supports byte ranges up to 2^31. -So it is not possible to correctly satisfy a lock request above 2^31. There are -many more differences, too many to be listed here. -</p><p> -Samba 2.2 and above implements record locking completely independent of the -underlying unix system. If a byte range lock that the client requests happens -to fall into the range 0-2^31, Samba hands this request down to the Unix system. -All other locks can not be seen by unix anyway. -</p><p> -Strictly a SMB server should check for locks before every read and write call on -a file. Unfortunately with the way fcntl() works this can be slow and may overstress -the rpc.lockd. It is also almost always unnecessary as clients are supposed to -independently make locking calls before reads and writes anyway if locking is -important to them. By default Samba only makes locking calls when explicitly asked -to by a client, but if you set <span class="emphasis"><em>strict locking = yes</em></span> then it -will make lock checking calls on every read and write. -</p><p> -You can also disable by range locking completely using <span class="emphasis"><em>locking = no</em></span>. -This is useful for those shares that don't support locking or don't need it -(such as cdroms). In this case Samba fakes the return codes of locking calls to -tell clients that everything is OK. -</p><p> -The second class of locking is the <span class="emphasis"><em>deny modes</em></span>. These -are set by an application when it opens a file to determine what types of -access should be allowed simultaneously with its open. A client may ask for -DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatibility -modes called DENY_FCB and DENY_DOS. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884872"></a>Samba Opportunistic Locking Control</h2></div></div><p> -Opportunistic locking essentially means that the client is allowed to download and cache -a file on their hard drive while making changes; if a second client wants to access the -file, the first client receives a break and must synchronise the file back to the server. -This can give significant performance gains in some cases; some programs insist on -synchronising the contents of the entire file back to the server for a single change. -</p><p> -Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. -</p><p> -Level2 Oplocks provids opportunistic locking for a file that will be treated as -<span class="emphasis"><em>read only</em></span>. Typically this is used on files that are read-only or -on files that the client has no initial intention to write to at time of opening the file. -</p><p> -Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with -Samba's oplocked files, although this has provided better integration of MS Windows network -file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are -oplock aware at this time. -</p><p> -Unless your system supports kernel oplocks, you should disable oplocks if you are -accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should -always be disabled if you are sharing a database file (e.g., Microsoft Access) between -multiple clients, as any break the first client receives will affect synchronisation of -the entire file (not just the single record), which will result in a noticable performance -impairment and, more likely, problems accessing the database in the first place. Notably, -Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt, -disable oplocks and tune your system from that point. -</p><p> -If client-side caching is desirable and reliable on your network, you will benefit from -turning on oplocks. If your network is slow and/or unreliable, or you are sharing your -files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people -will be accessing the same files frequently, you probably will not benefit from the overhead -of your client sending oplock breaks and will instead want to disable oplocks for the share. -</p><p> -Another factor to consider is the perceived performance of file access. If oplocks provide no -measurable speed benefit on your network, it might not be worth the hassle of dealing with them. -</p><p> -You can disable oplocks on a per-share basis with the following: - -</p><pre class="programlisting"> - oplocks = False - level2 oplocks = False -</pre><p> - -Alternately, you could disable oplocks on a per-file basis within the share: - -</p><pre class="programlisting"> - veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/ -</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 class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884987"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><p> -There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP -workstation computer that can affect any application attempting to access shared database files -across a network. This is a result of a default setting configured in the Windows 2000/XP -operating system known as <span class="emphasis"><em>Opportunistic Locking</em></span>. When a workstation -attempts to access shared data files located on another Windows 2000/XP computer, -the Windows 2000/XP operating system will attempt to increase performance by locking the -files and caching information locally. When this occurs, the application is unable to -properly function, which results in an <span class="emphasis"><em>Access Denied</em></span> - error message being displayed during network operations. -</p><p> -All Windows operating systems in the NT family that act as database servers for data files -(meaning that data files are stored there and accessed by other Windows PCs) may need to -have opportunistic locking disabled in order to minimize the risk of data file corruption. -This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP. -</p><p> -If you are using a Windows NT family workstation in place of a server, you must also -disable opportunistic locking (oplocks) on that workstation. For example, if you use a -PC with the Windows NT Workstation operating system instead of Windows NT Server, and you -have data files located on it that are accessed from other Windows PCs, you may need to -disable oplocks on that system. -</p><p> -The major difference is the location in the Windows registry where the values for disabling -oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location -may be used. -</p><p> -You can verify (or change or add, if necessary) this Registry value using the Windows -Registry Editor. When you change this registry value, you will have to reboot the PC -to ensure that the new setting goes into effect. -</p><p> -The location of the client registry entry for opportunistic locking has changed in -Windows 2000 from the earlier location in Microsoft Windows NT. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks -in earlier versions of Windows. -</p></div><p> -You can also deny the granting of opportunistic locks by changing the following registry entries: -</p><p> -</p><pre class="programlisting"> - HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\ - - OplocksDisabled REG_DWORD 0 or 1 - Default: 0 (not disabled) -</pre><p> -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -The OplocksDisabled registry value configures Windows clients to either request or not -request opportunistic locks on a remote file. To disable oplocks, the value of - OplocksDisabled must be set to 1. -</p></div><p> -</p><pre class="programlisting"> - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters - - EnableOplocks REG_DWORD 0 or 1 - Default: 1 (Enabled by Default) - - EnableOpLockForceClose REG_DWORD 0 or 1 - Default: 0 (Disabled by Default) -</pre><p> -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -The EnableOplocks value configures Windows-based servers (including Workstations sharing -files) to allow or deny opportunistic locks on local files. -</p></div><p> -To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1. -</p><p> -An illustration of how level II oplocks work: -</p><div class="itemizedlist"><ul type="disc"><li><p> - Station 1 opens the file, requesting oplock. - </p></li><li><p> - Since no other station has the file open, the server grants station 1 exclusive oplock. - </p></li><li><p> - Station 2 opens the file, requesting oplock. - </p></li><li><p> - Since station 1 has not yet written to the file, the server asks station 1 to Break - to Level II Oplock. - </p></li><li><p> - Station 1 complies by flushing locally buffered lock information to the server. - </p></li><li><p> - Station 1 informs the server that it has Broken to Level II Oplock (alternatively, - station 1 could have closed the file). - </p></li><li><p> - The server responds to station 2's open request, granting it level II oplock. - Other stations can likewise open the file and obtain level II oplock. - </p></li><li><p> - Station 2 (or any station that has the file open) sends a write request SMB. - The server returns the write response. - </p></li><li><p> - The server asks all stations that have the file open to Break to None, meaning no - station holds any oplock on the file. Because the workstations can have no cached - writes or locks at this point, they need not respond to the break-to-none advisory; - all they need do is invalidate locally cashed read-ahead data. - </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885212"></a>Workstation Service Entries</h3></div></div><pre class="programlisting"> - \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters - - UseOpportunisticLocking REG_DWORD 0 or 1 - Default: 1 (true) -</pre><p> -Indicates whether the redirector should use opportunistic-locking (oplock) performance -enhancement. This parameter should be disabled only to isolate problems. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885239"></a>Server Service Entries</h3></div></div><pre class="programlisting"> - \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters - - EnableOplocks REG_DWORD 0 or 1 - Default: 1 (true) -</pre><p> -Specifies whether the server allows clients to use oplocks on files. Oplocks are a -significant performance enhancement, but have the potential to cause lost cached -data on some networks, particularly wide-area networks. -</p><pre class="programlisting"> - MinLinkThroughput REG_DWORD 0 to infinite bytes per second - Default: 0 -</pre><p> -Specifies the minimum link throughput allowed by the server before it disables -raw and opportunistic locks for this connection. -</p><pre class="programlisting"> - MaxLinkDelay REG_DWORD 0 to 100,000 seconds - Default: 60 -</pre><p> -Specifies the maximum time allowed for a link delay. If delays exceed this number, -the server disables raw I/O and opportunistic locking for this connection. -</p><pre class="programlisting"> - OplockBreakWait REG_DWORD 10 to 180 seconds - Default: 35 -</pre><p> -Specifies the time that the server waits for a client to respond to an oplock break -request. Smaller values can allow detection of crashed clients more quickly but can -potentially cause loss of cached data. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885320"></a>Persistent Data Corruption</h2></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> -We have credible reports from developers that faulty network hardware, such as a single -faulty network card, can cause symptoms similar to read caching and data corruption. -If you see persistent data corruption even after repeated reindexing, you may have to -rebuild the data files in question. This involves creating a new data file with the -same definition as the file to be rebuilt and transferring the data from the old file -to the new one. There are several known methods for doing this that can be found in -our Knowledge Base. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885350"></a>Additional Reading</h2></div></div><p> -You may want to check for an updated version of this white paper on our Web site from -time to time. Many of our white papers are updated as information changes. For those papers, -the Last Edited date is always at the top of the paper. -</p><p> -Section of the Microsoft MSDN Library on opportunistic locking: -</p><p> -Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development > -Windows Base Services > Files and I/O > SDK Documentation > File Storage > File Systems -> About File Systems > Opportunistic Locks, Microsoft Corporation. -<a href="http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp" target="_top">http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp</a> -</p><p> -Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", -Microsoft Corporation, April 1999, <a href="=http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992</a>. -</p><p> -Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", -Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264</a>. -</p><p> -Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", - Microsoft Corporation, April 1995, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</a>. -</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>27. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></dd><dt>28. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</a></dt></dl></dd><dt>29. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="diagnosis"></a>Chapter 27. The samba checklist</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884776"></a>Introduction</h2></div></div><p> -This file contains a list of tests you can perform to validate your -Samba server. It also tells you what the likely cause of the problem -is if it fails any one of these steps. If it passes all these tests -then it is probably working fine. -</p><p> -You should do ALL the tests, in the order shown. We have tried to -carefully choose them so later tests only use capabilities verified in -the earlier tests. However, do not stop at the first error as there -have been some instances when continuing with the tests has helped -to solve a problem. -</p><p> -If you send one of the samba mailing lists an email saying "it doesn't work" -and you have not followed this test procedure then you should not be surprised -if your email is ignored. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884810"></a>Assumptions</h2></div></div><p> -In all of the tests it is assumed you have a Samba server called -BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP. -</p><p> -The procedure is similar for other types of clients. -</p><p> -It is also assumed you know the name of an available share in your -<tt>smb.conf</tt>. I will assume this share is called <i><tt>tmp</tt></i>. -You can add a <i><tt>tmp</tt></i> share like this by adding the -following to <tt>smb.conf</tt>: -</p><pre class="programlisting"> - -[tmp] - comment = temporary files - path = /tmp - read only = yes - -</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> -Please pay attention to the error messages you receive. If any error message -reports that your server is being unfriendly you should first check that your -IP name resolution is correctly set up. eg: Make sure your <tt>/etc/resolv.conf</tt> -file points to name servers that really do exist. -</p><p> -Also, if you do not have DNS server access for name resolution please check -that the settings for your <tt>smb.conf</tt> file results in <b>dns proxy = no</b>. The -best way to check this is with <b><tt>testparm smb.conf</tt></b>. -</p><p> -It is helpful to monitor the log files during testing by using the -<b>tail -F <i><tt>log_file_name</tt></i></b> in a separate -terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). -Relevant log files can be found (for default installations) in -<tt>/usr/local/samba/var</tt>. Also, connection logs from -machines can be found here or possibly in <tt>/var/log/samba</tt> -depending on how or if you specified logging in your <tt>smb.conf</tt> file. -</p><p> -If you make changes to your <tt>smb.conf</tt> file while going through these test, -don't forget to restart smbd and nmbd. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2793401"></a>The tests</h2></div></div><div class="procedure"><p class="title"><b>Procedure 27.1. Diagnosing your samba server</b></p><ol type="1"><li><p> -In the directory in which you store your <tt>smb.conf</tt> file, run the command -<b><tt>testparm smb.conf</tt></b>. If it reports any errors then your <tt>smb.conf</tt> -configuration file is faulty. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Your <tt>smb.conf</tt> file may be located in: <tt>/etc/samba</tt> -Or in: <tt>/usr/local/samba/lib</tt> -</p></div></li><li><p> -Run the command <b><tt>ping BIGSERVER</tt></b> from the PC and -<b><tt>ping ACLIENT</tt></b> from -the unix box. If you don't get a valid response then your TCP/IP -software is not correctly installed. -</p><p> -Note that you will need to start a "dos prompt" window on the PC to -run ping. -</p><p> -If you get a message saying "host not found" or similar then your DNS -software or <tt>/etc/hosts</tt> file is not correctly setup. -It is possible to -run samba without DNS entries for the server and client, but I assume -you do have correct entries for the remainder of these tests. -</p><p> -Another reason why ping might fail is if your host is running firewall -software. You will need to relax the rules to let in the workstation -in question, perhaps by allowing access from another subnet (on Linux -this is done via the ipfwadm program.) -</p><p> -Note: Modern Linux distributions install ipchains/iptables by default. -This is a common problem that is often overlooked. -</p></li><li><p> -Run the command <b><tt>smbclient -L BIGSERVER</tt></b> on the unix box. You -should get a list of available shares back. -</p><p> -If you get a error message containing the string "Bad password" then -you probably have either an incorrect <b>hosts allow</b>, -<b>hosts deny</b> or <b>valid users</b> line in your -<tt>smb.conf</tt>, or your guest account is not -valid. Check what your guest account is using testparm and -temporarily remove any <b>hosts allow</b>, <b>hosts deny</b>, <b>valid users</b> or <b>invalid users</b> lines. -</p><p> -If you get a "connection refused" response then the smbd server may -not be running. If you installed it in inetd.conf then you probably edited -that file incorrectly. If you installed it as a daemon then check that -it is running, and check that the netbios-ssn port is in a LISTEN -state using <b><tt>netstat -a</tt></b>. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -Some Unix / Linux systems use <b>xinetd</b> in place of -<b>inetd</b>. Check your system documentation for the location -of the control file/s for your particular system implementation of -this network super daemon. -</p></div><p> -If you get a "session request failed" then the server refused the -connection. If it says "Your server software is being unfriendly" then -its probably because you have invalid command line parameters to smbd, -or a similar fatal problem with the initial startup of smbd. Also -check your config file (<tt>smb.conf</tt>) for syntax errors with testparm -and that the various directories where samba keeps its log and lock -files exist. -</p><p> -There are a number of reasons for which smbd may refuse or decline -a session request. The most common of these involve one or more of -the following <tt>smb.conf</tt> file entries: -</p><pre class="programlisting"> - hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy - 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. -To solve this problem change these lines to: -</p><pre class="programlisting"> - hosts deny = ALL - hosts allow = xxx.xxx.xxx.xxx/yy 127. -</pre><p> -Do NOT use the <b>bind interfaces only</b> parameter where you -may wish to -use the samba password change facility, or where smbclient may need to -access a local service for name resolution or for local resource -connections. (Note: the <b>bind interfaces only</b> parameter deficiency -where it will not allow connections to the loopback address will be -fixed soon). -</p><p> -Another common cause of these two errors is having something already running -on port 139, such as Samba (ie: smbd is running from inetd already) or -something like Digital's Pathworks. Check your <tt>inetd.conf</tt> file before trying -to start smbd as a daemon, it can avoid a lot of frustration! -</p><p> -And yet another possible cause for failure of this test is when the subnet mask -and / or broadcast address settings are incorrect. Please check that the -network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the <tt>log.nmb</tt> file. -</p></li><li><p> -Run the command <b><tt>nmblookup -B BIGSERVER __SAMBA__</tt></b>. You should get the -IP address of your Samba server back. -</p><p> -If you don't then nmbd is incorrectly installed. Check your <tt>inetd.conf</tt> -if you run it from there, or that the daemon is running and listening -to udp port 137. -</p><p> -One common problem is that many inetd implementations can't take many -parameters on the command line. If this is the case then create a -one-line script that contains the right parameters and run that from -inetd. -</p></li><li><p>run the command <b><tt>nmblookup -B ACLIENT '*'</tt></b></p><p> -You should get the PCs IP address back. If you don't then the client -software on the PC isn't installed correctly, or isn't started, or you -got the name of the PC wrong. -</p><p> -If ACLIENT doesn't resolve via DNS then use the IP address of the -client in the above test. -</p></li><li><p> -Run the command <b><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 -not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts. -</p><p> -If this doesn't give a similar result to the previous test then -nmblookup isn't correctly getting your broadcast address through its -automatic mechanism. In this case you should experiment with the -<b>interfaces</b> option in <tt>smb.conf</tt> to manually configure your IP -address, broadcast and netmask. -</p><p> -If your PC and server aren't on the same subnet then you will need to -use the <i><tt>-B</tt></i> option to set the broadcast address to that of the PCs -subnet. -</p><p> -This test will probably fail if your subnet mask and broadcast address are -not correct. (Refer to TEST 3 notes above). -</p></li><li><p> -Run the command <b><tt>smbclient //BIGSERVER/TMP</tt></b>. You should -then be prompted for a password. You should use the password of the account -you are logged into the unix box with. If you want to test with -another account then add the <i><tt>-U <i><tt>accountname</tt></i></tt></i> option to the end of -the command line. eg: -<b><tt>smbclient //bigserver/tmp -Ujohndoe</tt></b> -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -It is possible to specify the password along with the username -as follows: -<b><tt>smbclient //bigserver/tmp -Ujohndoe%secret</tt></b> -</p></div><p> -Once you enter the password you should get the <tt>smb></tt> prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your <tt>smb.conf</tt>. -</p><p> -If it says "bad password" 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 - compile in support for them in smbd - </p></li><li><p> - your <b>valid users</b> configuration is incorrect - </p></li><li><p> - you have a mixed case password and you haven't enabled the <b>password - level</b> option at a high enough level - </p></li><li><p> - the <b>path =</b> line in <tt>smb.conf</tt> is incorrect. Check it with testparm - </p></li><li><p> - you enabled password encryption but didn't create the SMB encrypted - password file - </p></li></ol></div><p> -Once connected you should be able to use the commands -<b>dir</b> <b>get</b> <b>put</b> etc. -Type <b>help <i><tt>command</tt></i></b> for instructions. You should -especially check that the amount of free disk space shown is correct -when you type <b>dir</b>. -</p></li><li><p> -On the PC, type the command <b><tt>net view \\BIGSERVER</tt></b>. You will -need to do this from within a "dos prompt" window. You should get back a -list of available shares on the server. -</p><p> -If you get a "network name not found" or similar error then netbios -name resolution is not working. This is usually caused by a problem in -nmbd. To overcome it you could do one of the following (you only need -to choose one of them): -</p><div class="orderedlist"><ol type="1"><li><p> - fixup the nmbd installation -</p></li><li><p> - add the IP address of BIGSERVER to the <b>wins server</b> box in the - advanced tcp/ip setup on the PC. -</p></li><li><p> - enable windows name resolution via DNS in the advanced section of - the tcp/ip setup -</p></li><li><p> - add BIGSERVER to your lmhosts file on the PC. -</p></li></ol></div><p> -If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the <b><tt>smbclient -L</tt></b> test above. In -particular, make sure your <b>hosts allow</b> line is correct (see the man -pages) -</p><p> -Also, do not overlook that fact that when the workstation requests the -connection to the samba server it will attempt to connect using the -name with which you logged onto your Windows machine. You need to make -sure that an account exists on your Samba server with that exact same -name and password. -</p><p> -If you get "specified computer is not receiving requests" or similar -it probably means that the host is not contactable via tcp services. -Check to see if the host is running tcp wrappers, and if so add an entry in -the <tt>hosts.allow</tt> file for your client (or subnet, etc.) -</p></li><li><p> -Run the command <b><tt>net use x: \\BIGSERVER\TMP</tt></b>. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly -installed or your smb.conf is incorrect. make sure your <b>hosts allow</b> -and other config lines in <tt>smb.conf</tt> are correct. -</p><p> -It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line <b>user = -<i><tt>username</tt></i></b> to the <b>[tmp]</b> section of -<tt>smb.conf</tt> where <i><tt>username</tt></i> is the -username corresponding to the password you typed. If you find this -fixes things you may need the username mapping option. -</p><p> -It might also be the case that your client only sends encrypted passwords -and you have <b>encrypt passwords = no</b> in <tt>smb.conf</tt> -Turn it back on to fix. -</p></li><li><p> -Run the command <b><tt>nmblookup -M <i><tt>testgroup</tt></i></tt></b> where -<i><tt>testgroup</tt></i> is the name of the workgroup that your Samba server and -Windows PCs belong to. You should get back the IP address of the -master browser for that workgroup. -</p><p> -If you don't then the election process has failed. Wait a minute to -see if it is just being slow then try again. If it still fails after -that then look at the browsing options you have set in <tt>smb.conf</tt>. Make -sure you have <b>preferred master = yes</b> to ensure that -an election is held at startup. -</p></li><li><p> ->From file manager try to browse the server. Your samba server should -appear in the browse list of your local workgroup (or the one you -specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it -is refusing to browse a server that has no encrypted password -capability and is in user level security mode. In this case either set -<b>security = server</b> AND -<b>password server = Windows_NT_Machine</b> in your -<tt>smb.conf</tt> file, or make sure <b>encrypted passwords</b> is -set to "yes". -</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886854"></a>Still having troubles?</h2></div></div><p>Read the chapter on -<a href="#problems" title="Chapter 28. Analysing and solving samba problems">Analysing and Solving Problems</a>. -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="problems"></a>Chapter 28. Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</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><h2 class="title" style="clear: both"><a name="id2790687"></a>Diagnostics tools</h2></div></div><p> -One of the best diagnostic tools for debugging problems is Samba itself. -You can use the -d option for both smbd and nmbd to specify what -'debug level' at which to run. See the man pages on smbd, nmbd and -smb.conf for more information on debugging options. The debug -level can range from 1 (the default) to 10 (100 for debugging passwords). -</p><p> -Another helpful method of debugging is to compile samba using the -<b>gcc -g </b> flag. This will include debug -information in the binaries and allow you to attach gdb to the -running smbd / nmbd process. In order to attach gdb to an smbd -process for an NT workstation, first get the workstation to make the -connection. Pressing ctrl-alt-delete and going down to the domain box -is sufficient (at least, on the first time you join the domain) to -generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation -maintains an open connection, and therefore there will be an smbd -process running (assuming that you haven't set a really short smbd -idle timeout) So, in between pressing ctrl alt delete, and actually -typing in your password, you can attach gdb and continue. -</p><p> -Some useful samba commands worth investigating: -</p><div class="itemizedlist"><ul type="disc"><li><p>testparam | more</p></li><li><p>smbclient -L //{netbios name of server}</p></li></ul></div><p> -An SMB enabled version of tcpdump is available from -<a href="http://www.tcpdump.org/" target="_top">http://www.tcpdup.org/</a>. -Ethereal, another good packet sniffer for Unix and Win32 -hosts, can be downloaded from <a href="http://www.ethereal.com/" target="_top">http://www.ethereal.com</a>. -</p><p> -For tracing things on the Microsoft Windows NT, Network Monitor -(aka. netmon) is available on the Microsoft Developer Network CD's, -the Windows NT Server install CD and the SMS CD's. The version of -netmon that ships with SMS allows for dumping packets between any two -computers (i.e. placing the network interface in promiscuous mode). -The version on the NT Server install CD will only allow monitoring -of network traffic directed to the local NT box and broadcasts on the -local subnet. Be aware that Ethereal can read and write netmon -formatted files. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887096"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</h2></div></div><p> -Installing netmon on an NT workstation requires a couple -of steps. The following are for installing Netmon V4.00.349, which comes -with Microsoft Windows NT Server 4.0, on Microsoft Windows NT -Workstation 4.0. The process should be similar for other versions of -Windows NT / Netmon. You will need both the Microsoft Windows -NT Server 4.0 Install CD and the Workstation 4.0 Install CD. -</p><p> -Initially you will need to install 'Network Monitor Tools and Agent' -on the NT Server. To do this -</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel - - Network - Services - Add </p></li><li><p>Select the 'Network Monitor Tools and Agent' and - click on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel. - </p></li><li><p>Insert the Windows NT Server 4.0 install CD - when prompted.</p></li></ul></div><p> -At this point the Netmon files should exist in -<tt>%SYSTEMROOT%\System32\netmon\*.*</tt>. -Two subdirectories exist as well, <tt>parsers\</tt> -which contains the necessary DLL's for parsing the netmon packet -dump, and <tt>captures\</tt>. -</p><p> -In order to install the Netmon tools on an NT Workstation, you will -first need to install the 'Network Monitor Agent' from the Workstation -install CD. -</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel - - Network - Services - Add</p></li><li><p>Select the 'Network Monitor Agent' and click - on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel. - </p></li><li><p>Insert the Windows NT Workstation 4.0 install - CD when prompted.</p></li></ul></div><p> -Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* -to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set -permissions as you deem appropriate for your site. You will need -administrative rights on the NT box to run netmon. -</p><p> -To install Netmon on a Windows 9x box install the network monitor agent -from the Windows 9x CD (\admin\nettools\netmon). There is a readme -file located with the netmon driver files on the CD if you need -information on how to do this. Copy the files from a working -Netmon installation. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887237"></a>Useful URL's</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>Home of Samba site <a href="http://samba.org" target="_top"> - http://samba.org</a>. We have a mirror near you !</p></li><li><p> The <span class="emphasis"><em>Development</em></span> document -on the Samba mirrors might mention your problem. If so, -it might mean that the developers are working on it.</p></li><li><p>See how Scott Merrill simulates a BDC behavior at - <a href="http://www.skippy.net/linux/smb-howto.html" target="_top"> - http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>Although 2.0.7 has almost had its day as a PDC, David Bannon will - keep the 2.0.7 PDC pages at <a href="http://bioserve.latrobe.edu.au/samba" target="_top"> - http://bioserve.latrobe.edu.au/samba</a> going for a while yet.</p></li><li><p>Misc links to CIFS information - <a href="http://samba.org/cifs/" target="_top">http://samba.org/cifs/</a></p></li><li><p>NT Domains for Unix <a href="http://mailhost.cb1.com/~lkcl/ntdom/" target="_top"> - http://mailhost.cb1.com/~lkcl/ntdom/</a></p></li><li><p>FTP site for older SMB specs: - <a href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top"> - ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887343"></a>Getting help from the mailing lists</h2></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>Support</b> and then click on <b> -Samba related mailing lists</b>. -</p><p> -For questions relating to Samba TNG go to -<a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a> -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.</p><p> -If you post a message to one of the lists please observe the following guide lines : -</p><div class="itemizedlist"><ul type="disc"><li><p> Always remember that the developers are volunteers, they are -not paid and they never guarantee to produce a particular feature at -a particular time. Any time lines are 'best guess' and nothing more. -</p></li><li><p> Always mention what version of samba you are using and what -operating system its running under. You should probably list the -relevant sections of your <tt>smb.conf</tt> file, at least the options -in [global] that affect PDC support.</p></li><li><p>In addition to the version, if you obtained Samba via -CVS mention the date when you last checked it out.</p></li><li><p> Try and make your question clear and brief, lots of long, -convoluted questions get deleted before they are completely read ! -Don't post html encoded messages (if you can select colour or font -size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when -you are away, make sure its configured to not answer mailing lists. -</p></li><li><p> Don't cross post. Work out which is the best list to post to -and see what happens, i.e. don't post to both samba-ntdom and samba-technical. -Many people active on the lists subscribe to more -than one list and get annoyed to see the same message two or more times. -Often someone will see a message and thinking it would be better dealt -with on another, will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span> -log files written at a debug level set to as much as 20. -Please don't send the entire log but enough to give the context of the -error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( from the opening of -the pipe to the error ) you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email. -Consider pasting the relevant parts into the body of the message. The samba -mailing lists go to a huge number of people, do they all need a copy of your -smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887497"></a>How to get off the mailinglists</h2></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>Support</b> and -then click on <b> Samba related mailing lists</b>. Or perhaps see -<a href="http://lists.samba.org/mailman/roster/samba-ntdom" target="_top">here</a> -</p><p> -Please don't post messages to the list asking to be removed, you will just -be referred to the above address (unless that process failed in some way...) -</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="bugreport"></a>Chapter 29. Reporting Bugs</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887016"></a>Introduction</h2></div></div><p>Please report bugs using <a href="https://bugzilla.samba.org/" target="_top">bugzilla</a>.</p><p> -Please take the time to read this file before you submit a bug -report. Also, please see if it has changed between releases, as we -may be changing the bug reporting mechanism at some time. -</p><p> -Please also do as much as you can yourself to help track down the -bug. Samba is maintained by a dedicated group of people who volunteer -their time, skills and efforts. We receive far more mail about it than -we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets -us fix it fast. -</p><p> -Do not assume that if you post the bug to the comp.protocols.smb -newsgroup or the mailing list that we will read it. If you suspect that your -problem is not a bug but a configuration problem then it is better to send -it to the Samba mailing list, as there are (at last count) 5000 other users on -that list that may be able to help you. -</p><p> -You may also like to look though the recent mailing list archives, -which are conveniently accessible on the Samba web pages -at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886937"></a>General info</h2></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 27. 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><h2 class="title" style="clear: both"><a name="id2887713"></a>Debug levels</h2></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 -detail, but may use too much disk space. -</p><p> -To set the debug level use <b>log level =</b> in your -<tt>smb.conf</tt>. You may also find it useful to set the log -level higher for just one machine and keep separate logs for each machine. -To do this use: -</p><pre class="programlisting"> -log level = 10 -log file = /usr/local/samba/lib/log.%m -include = /usr/local/samba/lib/smb.conf.%m -</pre><p> -then create a file -<tt>/usr/local/samba/lib/smb.conf.<i><tt>machine</tt></i></tt> where -<i><tt>machine</tt></i> is the name of the client you wish to debug. In that file -put any <tt>smb.conf</tt> commands you want, for example -<b>log level=</b> may be useful. This also allows you to -experiment with different security systems, protocol levels etc on just -one machine. -</p><p> -The <tt>smb.conf</tt> entry <b>log level =</b> -is synonymous with the entry <b>debuglevel =</b> that has been -used in older versions of Samba and is being retained for backwards -compatibility of <tt>smb.conf</tt> files. -</p><p> -As the <b>log level =</b> value is increased you will record -a significantly increasing level of debugging information. For most -debugging operations you may not need a setting higher than 3. Nearly -all bugs can be tracked at a setting of 10, but be prepared for a VERY -large volume of log data. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887849"></a>Internal errors</h2></div></div><p> -If you get a "INTERNAL ERROR" message in your log files it means that -Samba got an unexpected signal while running. It is probably a -segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software). -</p><p> -If the message came from smbd then it will probably be accompanied by -a message which details the last SMB message received by smbd. This -info is often very useful in tracking down the problem so please -include it in your bug report. -</p><p> -You should also detail how to reproduce the problem, if -possible. Please make this reasonably detailed. -</p><p> -You may also find that a core file appeared in a <tt>corefiles</tt> -subdirectory of the directory where you keep your samba log -files. This file is the most useful tool for tracking down the bug. To -use it you do this: -</p><p><b>gdb smbd core</b></p><p> -adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try <b><tt>dbx</tt></b>. Then within the debugger use the -command <b><tt>where</tt></b> to give a stack trace of where the problem -occurred. Include this in your mail. -</p><p> -If you know any assembly language then do a <b><tt>disass</tt></b> of the routine -where the problem occurred (if its in a library routine then -disassemble the routine that called it) and try to work out exactly -where the problem is by looking at the surrounding code. Even if you -don't know assembly then incuding this info in the bug report can be -useful. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887942"></a>Attaching to a running process</h2></div></div><p> -Unfortunately some unixes (in particular some recent linux kernels) -refuse to dump a core file if the task has changed uid (which smbd -does often). To debug with this sort of system you could try to attach -to the running process using <b><tt>gdb smbd <i><tt>PID</tt></i></tt></b> where you get <i><tt>PID</tt></i> from -smbstatus. Then use <b><tt>c</tt></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><h2 class="title" style="clear: both"><a name="id2887989"></a>Patches</h2></div></div><p> -The best sort of bug report is one that includes a fix! If you send us -patches please use <b><tt>diff -u</tt></b> format if your version of -diff supports it, otherwise use <b><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><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>33. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">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="#id2891126">Are there any other issues when OS/2 (any version) - is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">Windows NT 3.1</a></dt></dl></dd><dt>34. <a href="#SWAT">SWAT - The Samba Web Admininistration Tool</a></dt><dd><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">The Password Change Page</a></dt></dl></dd></dl></dd><dt>35. <a href="#speed">Samba performance issues</a></dt><dd><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="compiling"></a>Chapter 30. How to compile SAMBA</h2></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (22 May 2001) </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></div><p> -You can obtain the samba source from the <a href="http://samba.org/" target="_top">samba website</a>. To obtain a development version, -you can download samba from CVS or using rsync. -</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887580"></a>Access Samba source code via CVS</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887587"></a>Introduction</h3></div></div><p> -Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can -be accessed via anonymous CVS using the instructions -detailed in this chapter. -</p><p> -This chapter is a modified version of the instructions found at -<a href="http://samba.org/samba/cvs.html" target="_top">http://samba.org/samba/cvs.html</a> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887620"></a>CVS Access to samba.org</h3></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 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><h4 class="title"><a name="id2887636"></a>Access via CVSweb</h4></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 -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><h4 class="title"><a name="id2888200"></a>Access via cvs</h4></div></div><p> -You can also access the source code via a -normal cvs client. This gives you much more control over what you can -do with the repository and allows you to checkout whole source trees -and keep them up to date via normal cvs commands. This is the -preferred method of access if you are a developer and not -just a casual browser. -</p><p> -To download the latest cvs source code, point your -browser at the URL : <a href="http://www.cyclic.com/" target="_top">http://www.cyclic.com/</a>. -and click on the 'How to get cvs' link. CVS is free software under -the GNU GPL (as is Samba). Note that there are several graphical CVS clients -which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com. -</p><p> -To gain access via anonymous cvs use the following steps. -For this example it is assumed that you want a copy of the -samba source code. For the other source code repositories -on this system just substitute the correct package name -</p><div class="orderedlist"><ol type="1"><li><p> - Install a recent copy of cvs. All you really need is a - copy of the cvs client binary. - </p></li><li><p> - Run the command - </p><p> - <b><tt>cvs -d :pserver:cvs@samba.org:/cvsroot login</tt></b> - </p><p> - When it asks you for a password type <b><tt>cvs</tt></b>. - </p></li><li><p> - Run the command - </p><p> - <b><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</tt></b> - </p><p> - This will create a directory called samba containing the - latest samba source code (i.e. the HEAD tagged cvs branch). This - currently corresponds to the 3.0 development tree. - </p><p> - CVS branches other then HEAD can be obtained by using the <i><tt>-r</tt></i> - and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the - latest 2.2 release code. This could be done by using the following userinput. - </p><p> - <b><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</tt></b> - </p></li><li><p> - Whenever you want to merge in the latest code changes use - the following command from within the samba directory: - </p><p> - <b><tt>cvs update -d -P</tt></b> - </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888377"></a>Accessing the samba sources via rsync and ftp</h2></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 rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See <a href="http://rsync.samba.org/" target="_top">the rsync homepage</a> for more info on rsync. - </p><p> - The disadvantage of the unpacked trees - is that they do not support automatic - merging of local changes like CVS does. - rsync access is most convenient for an - initial install. - </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888418"></a>Verifying Samba's PGP signature</h2></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. According to Jerry Carter of the Samba Team, only about 22% of -all Samba downloads have had a corresponding PGP signature download (a very low percentage, which -should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP -signatures should be a standard reflex. -</p><p> -With that said, go ahead and download the following files: -</p><pre class="programlisting"> - $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc - $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc -</pre><p> -The first file is the PGP signature for the Samba source file; the other is the Samba public -PGP key itself. Import the public PGP key with: -</p><pre class="programlisting"> - $ gpg --import samba-pubkey.asc -</pre><p> -And verify the Samba source code integrity with: -</p><pre class="programlisting"> - $ gzip -d samba-2.2.8a.tar.gz - $ gpg --verify samba-2.2.8a.tar.asc -</pre><p> -If you receive a message like, "Good signature from Samba Distribution Verification Key..." -then all is well. The warnings about trust relationships can be ignored. An example of what -you would not want to see would be: -</p><pre class="programlisting"> - gpg: BAD signature from "Samba Distribution Verification Key" -</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888501"></a>Building the Binaries</h2></div></div><p>To do this, first run the program <b><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>root# </tt><b><tt>./configure --help - </tt></b></p><p>first to see what special options you can enable. - Then executing</p><p><tt>root# </tt><b><tt>make</tt></b></p><p>will create the binaries. Once it's successfully - compiled you can use </p><p><tt>root# </tt><b><tt>make install</tt></b></p><p>to install the binaries and manual pages. You can - separately install the binaries and/or man pages using</p><p><tt>root# </tt><b><tt>make installbin - </tt></b></p><p>and</p><p><tt>root# </tt><b><tt>make installman - </tt></b></p><p>Note that if you are upgrading for a previous version - of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with</p><p><tt>root# </tt><b><tt>make revert - </tt></b></p><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888639"></a>Compiling samba with Active Directory support</h3></div></div><p>In order to compile samba with ADS support, you need to have installed - on your system:</p><div class="itemizedlist"><ul type="disc"><li><p>the MIT kerberos development libraries - (either install from the sources or use a package). The - heimdal libraries will not work.</p></li><li><p>the OpenLDAP development libraries.</p></li></ul></div><p>If your kerberos libraries are in a non-standard location then - remember to add the configure option --with-krb5=DIR.</p><p>After you run configure make sure that <tt>include/config.h</tt> it generates contains lines like this:</p><pre class="programlisting"> -#define HAVE_KRB5 1 -#define HAVE_LDAP 1 -</pre><p>If it doesn't then configure did not find your krb5 libraries or - your ldap libraries. Look in config.log to figure out why and fix - it.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2888706"></a>Installing the required packages for Debian</h4></div></div><p>On Debian you need to install the following packages:</p><p> - </p><div class="itemizedlist"><ul type="disc"><li>libkrb5-dev</li><li>krb5-user</li></ul></div><p> - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2888736"></a>Installing the required packages for RedHat</h4></div></div><p>On RedHat this means you should have at least: </p><p> - </p><div class="itemizedlist"><ul type="disc"><li>krb5-workstation (for kinit)</li><li>krb5-libs (for linking with)</li><li>krb5-devel (because you are compiling from source)</li></ul></div><p> - </p><p>in addition to the standard development environment.</p><p>Note that these are not standard on a RedHat install, and you may need - to get them off CD2.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888786"></a>Starting the smbd and nmbd</h2></div></div><p>You must choose to start smbd and nmbd either - as daemons or from inetdDon't try - to do both! Either you can put them in <tt> - inetd.conf</tt> and have them started on demand - by inetd, or you can start them as - daemons either from the command line or in <tt> - /etc/rc.local</tt>. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start - Samba. In many cases you must be root.</p><p>The main advantage of starting smbd - and nmbd 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><h3 class="title"><a name="id2888853"></a>Starting from inetd.conf</h3></div></div><p>NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute services maps.</p><p>Look at your <tt>/etc/services</tt>. - What is defined at port 139/tcp. If nothing is defined - then add a line like this:</p><p><b><tt>netbios-ssn 139/tcp</tt></b></p><p>similarly for 137/udp you should have an entry like:</p><p><b><tt>netbios-ns 137/udp</tt></b></p><p>Next edit your <tt>/etc/inetd.conf</tt> - and add two lines something like this:</p><pre class="programlisting"> - netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd - netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd - </pre><p>The exact syntax of <tt>/etc/inetd.conf</tt> - varies between unixes. Look at the other entries in inetd.conf - for a guide.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some unixes already have entries like netbios_ns - (note the underscore) in <tt>/etc/services</tt>. - You must either edit <tt>/etc/services</tt> or - <tt>/etc/inetd.conf</tt> to make them consistent.</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On many systems you may need to use the - <b>interfaces</b> option in <tt>smb.conf</tt> to specify the IP address - and netmask of your interfaces. Run ifconfig - as root if you don't know what the broadcast is for your - net. nmbd tries to determine it at run - time, but fails on some unixes. - </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Many unixes only accept around 5 - parameters on the command line in <tt>inetd.conf</tt>. - This means you shouldn't use spaces between the options and - arguments, or you should use a script, and start the script - from <b>inetd</b>.</p></div><p>Restart <b>inetd</b>, perhaps just send - it a HUP. If you have installed an earlier version of - nmbd then you may need to kill nmbd as well.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889045"></a>Alternative: starting it as a daemon</h3></div></div><p>To start the server as a daemon you should create - a script something like this one, perhaps calling - it <tt>startsmb</tt>.</p><pre class="programlisting"> - #!/bin/sh - /usr/local/samba/bin/smbd -D - /usr/local/samba/bin/nmbd -D - </pre><p>then make it executable with <b>chmod - +x startsmb</b></p><p>You can then run <b>startsmb</b> by - hand or execute it from <tt>/etc/rc.local</tt> - </p><p>To kill it send a kill signal to the processes - <b>nmbd</b> and <b>smbd</b>.</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>examples/svr4-startup</tt> - script to make Samba fit into that system.</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><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">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">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><h2 class="title" style="clear: both"><a name="id2888159"></a>Planning and Getting Started</h2></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. -</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><h3 class="title"><a name="id2888028"></a>Objectives</h3></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 -should remain in place. Many who have introduced open source technologies have experienced -pressure to return to a Microsoft based platform solution at the first sign of trouble. -</p><p> -It is strongly advised that before attempting a migration to a Samba-3 controlled network -that every possible effort be made to gain all-round commitment to the change. Firstly, you -should know precisely <span class="emphasis"><em>why</em></span> the change is important for the organisation. -Possible motivations to make a change include: -</p><div class="itemizedlist"><ul type="disc"><li><p>Improve network manageability</p></li><li><p>Obtain better user level functionality</p></li><li><p>Reduce network operating costs</p></li><li><p>Reduce exposure caused by Microsoft withdrawal of NT4 support</p></li><li><p>Avoid MS License 6 implications</p></li><li><p>Reduce organisation's dependency on Microsoft</p></li></ul></div><p> -It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers -an alternative solution that is both different from MS Windows NT4 and that offers some -advantages compared with it. It should also be recognised that Samba-3 lacks many of the -features that Microsoft has promoted as core values in migration from MS Windows NT4 to -MS Windows 2000 and beyond (with or without Active Directory services). -</p><p> -What are the features that Samba-3 can NOT provide? -</p><div class="itemizedlist"><ul type="disc"><li><p>Active Directory Server</p></li><li><p>Group Policy Objects (in Active Direcrtory)</p></li><li><p>Machine Policy objects</p></li><li><p>Logon Scripts in Active Directorty</p></li><li><p>Software Application and Access Controls in Active Directory</p></li></ul></div><p> -The features that Samba-3 DOES provide and that may be of compelling interest to your site -includes: -</p><div class="itemizedlist"><ul type="disc"><li><p>Lower Cost of Ownership</p></li><li><p>Global availability of support with no strings attached</p></li><li><p>Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)</p></li><li><p>Creation of on-the-fly logon scripts</p></li><li><p>Creation of on-the-fly Policy Files</p></li><li><p>Greater Stability, Reliability, Performance and Availability</p></li><li><p>Manageability via an ssh connection</p></li><li><p>Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)</p></li><li><p>Ability to implement a full single-signon architecture</p></li><li><p>Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand</p></li></ul></div><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><h4 class="title"><a name="id2889498"></a>Domain Layout</h4></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 -paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs). -It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one -chooses to use an LDAP authentication backend then the same database can be used by several different -domains. This means that in a complex organisation there can be a single LDAP database, that itself -can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed). -</p><p> -It is recommended that from a design perspective, the number of users per server, as well as the number -of servers, per domain should be scaled according to needs and should also consider server capacity -and network bandwidth. -</p><p> -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 -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><h4 class="title"><a name="id2889551"></a>Server Share and Directory Layout</h4></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 -it is, the greater will be the demand of keeping systems secure and functional. -</p><p> -The nature of the data that must be stored needs to be born in mind when deciding how many -shares must be created. The physical disk space layout should also be taken into account -when designing where share points will be created. Keep in mind that all data needs to be -backed up, thus the simpler the disk layout the easier it will be to keep track of what must -be backed up to tape or other off-line storage medium. Always plan and implement for minimum -maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance: -Backup and test, validate every backup, create a disaster recovery plan and prove that it works. -</p><p> -Users should be grouped according to data access control needs. File and directory access -is best controlled via group permissions and the use of the "sticky bit" on group controlled -directories may substantially avoid file access complaints from samba share users. -</p><p> -Many network administrators who are new to the game will attempt to use elaborate techniques -to set access controls, on files, directories, shares, as well as in share definitions. -There is the ever present danger that that administrator's successor will not understand the -complex mess that has been inherited. Remember, apparent job security through complex design -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><h4 class="title"><a name="id2889612"></a>Logon Scripts</h4></div></div><p> -Please refer to the section of this document on Advanced Network Adminsitration 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 -the <tt>root preexec</tt> parameters to the <tt>NETLOGON</tt> share. -</p><p> -Some sites prefer to use a tool such as <tt>kixstart</tt> 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><h4 class="title"><a name="id2889670"></a>Profile Migration/Creation</h4></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 <tt>profiles</tt>. 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><h4 class="title"><a name="id2889700"></a>User and Group Accounts</h4></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><h3 class="title"><a name="id2889725"></a>Steps In Migration Process</h3></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>rpcclient NT4PDC -U Administrator%passwd</p><ol type="a"><li><p>lsaquery</p></li><li><p>Note the SID returned</p></li></ol></li><li><p>net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd</p><ol type="a"><li><p>Note the SID</p></li></ol></li><li><p>net getlocalsid</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>net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd</p></li><li><p>net rpc vampire -S NT4PDC -U administrator%passwd</p></li><li><p>pdbedit -l</p><ol type="a"><li><p>Note - did the users migrate?</p></li></ol></li><li><p>initGrps.sh DOMNAME</p></li><li><p>net groupmap list</p><ol type="a"><li><p>Now check that all groups are recognised</p></li></ol></li><li><p>net rpc campire -S NT4PDC -U administrator%passwd</p></li><li><p>pdbedit -lv</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><h2 class="title" style="clear: both"><a name="id2889980"></a>Migration Options</h2></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="id2889997"></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><h3 class="title"><a name="id2890062"></a>Planning for Success</h3></div></div><p> -There are three basic choices for sites that intend to migrate from MS Windwows NT4 -to Samba-3. -</p><div class="itemizedlist"><ul type="disc"><li><p> - Simple Conversion (total replacement) - </p></li><li><p> - Upgraded Conversion (could be one of integration) - </p></li><li><p> - Complete Redesign (completely new solution) - </p></li></ul></div><p> -No matter what choice you make, the following rules will minimise down-stream problems: -</p><div class="itemizedlist"><ul type="disc"><li><p> - Take sufficient time - </p></li><li><p> - Avoid Panic - </p></li><li><p> - Test ALL assumptions - </p></li><li><p> - Test full roll-out program, including workstation deployment - </p></li></ul></div><div class="table"><a name="id2890135"></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><h3 class="title"><a name="id2890304"></a>Samba Implementation Choices</h3></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 - -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? - Through Samba share parameters - Not recommended - except as only resort - -Policies (migrate or create new ones) - Group Policy Editor (NT4) - Watch out for Tattoo effect - -User and Group Profiles - Platform specific so use platform tool to change from a Local - to a Roaming profile Can use new profiles tool to change SIDs - (NTUser.DAT) - -Logon Scripts (Know how they work) - -User and Group mapping to Unix/Linux - username map facility may be needed - Use 'net groupmap' to connect NT4 groups to Unix groups - Use pdbedit to set/change user configuration -NOTE: -If migrating to LDAP back end it may be easier to dump initial LDAP database -to LDIF, then edit, then reload into LDAP - - OS specific scripts / programs may be needed - Add / delete Users - Note OS limits on size of name (Linux 8 chars) - NT4 up to 254 chars - Add / delete machines - Applied only to domain members (note up to 16 chars) - Add / delete Groups - Note OS limits on size and nature - Linux limit is 16 char, - no spaces and no upper case chars (groupadd) - -Migration Tools - Domain Control (NT4 Style) - Profiles, Policies, Access Controls, Security - -Migration Tools - Samba: net, rpcclient, smbpasswd, pdbedit, profiles - Windows: NT4 Domain User Manager, Server Manager (NEXUS) - -Authentication - New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam) -</pre><p> -</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="Portability"></a>Chapter 32. Portability</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">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><h2 class="title" style="clear: both"><a name="id2889273"></a>HPUX</h2></div></div><p> -HP's implementation of supplementary groups is, er, non-standard (for -hysterical reasons). There are two group files, /etc/group and -/etc/logingroup; the system maps UIDs to numbers using the former, but -initgroups() reads the latter. Most system admins who know the ropes -symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons -too stupid to go into here). initgroups() will complain if one of the -groups you're in in /etc/logingroup has what it considers to be an invalid -ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think) -60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody' -GIDs. -</p><p> -If you encounter this problem, make sure that the programs that are failing -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 -Samba. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889171"></a>SCO Unix</h2></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. -</p><p> -The patch you need is UOD385 Connection Drivers SLS. It is available from -SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889194"></a>DNIX</h2></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. -</p><p> -For this reason Samba by default defines the macro NO_EID in the DNIX -section of includes.h. This works around the problem in a limited way, -but it is far from ideal, some things still won't work right. -</p><p> -To fix the problem properly you need to assemble the following two -functions and then either add them to your C library or link them into -Samba. -</p><p> -put this in the file <tt>setegid.s</tt>: -</p><pre class="programlisting"> - .globl _setegid -_setegid: - moveq #47,d0 - movl #100,a0 - moveq #1,d1 - movl 4(sp),a1 - trap #9 - bccs 1$ - jmp cerror -1$: - clrl d0 - rts -</pre><p> -put this in the file <tt>seteuid.s</tt>: -</p><pre class="programlisting"> - .globl _seteuid -_seteuid: - moveq #47,d0 - movl #100,a0 - moveq #0,d1 - movl 4(sp),a1 - trap #9 - bccs 1$ - jmp cerror -1$: - clrl d0 - rts -</pre><p> -after creating the above files you then assemble them using -</p><p><b>as seteuid.s</b></p><p><b>as setegid.s</b></p><p> -that should produce the files <tt>seteuid.o</tt> and -<tt>setegid.o</tt> -</p><p> -then you need to add these to the LIBSM line in the DNIX section of -the Samba Makefile. Your LIBSM line will then look something like this: -</p><pre class="programlisting"> -LIBSM = setegid.o seteuid.o -ln -</pre><p> -You should then remove the line: -</p><pre class="programlisting"> -#define NO_EID -</pre><p>from the DNIX section of <tt>includes.h</tt></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890671"></a>RedHat Linux Rembrandt-II</h2></div></div><p> -By default RedHat Rembrandt-II during installation adds an -entry to /etc/hosts as follows: -</p><pre class="programlisting"> - 127.0.0.1 loopback "hostname"."domainname" -</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 -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><h2 class="title" style="clear: both"><a name="id2890709"></a>AIX</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890716"></a>Sequential Read Ahead</h3></div></div><p> -Disabling Sequential Read Ahead using <b><tt>vmtune -r 0</tt></b> improves -samba performance significally. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890741"></a>Solaris</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890748"></a>Locking improvements</h3></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, -then try again. The lock attempt was failing before the grant was -occurring. So the visible manifestation of this would be a handful of -processes stealing all of the CPU, and when they were trussed they would -be stuck if F_SETLKW64 loops. -</p><p> -Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 -has not been released yet. -</p><p> -The patch revision for 2.6 is 105181-34 -for 8 is 108528-19 -and for 9 is 112233-04 -</p><p> -After the install of these patches it is recommended to reconfigure -and rebuild samba. -</p><p>Thanks to Joe Meslovich for reporting</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="winbind-solaris9"></a>Winbind on Solaris 9</h3></div></div><p> -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><h2 class="title"><a name="Other-Clients"></a>Chapter 33. Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author">Jim McDonough</h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt><<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">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">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="#id2891126">Are there any other issues when OS/2 (any version) - is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working - for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">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><h2 class="title" style="clear: both"><a name="id2890402"></a>Macintosh clients?</h2></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><p> -They test it against Windows 95, Windows NT and samba for -compatibility issues. At the time of writing, DAVE was at version -1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from -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. -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 -<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><h2 class="title" style="clear: both"><a name="id2890976"></a>OS2 Client</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890983"></a>How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?</h3></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><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client ('IBM Peer') - </p></li><li><p>TCP/IP ('Internet support') - </p></li><li><p>The "NetBIOS over TCP/IP" driver ('TCPBEUI') - </p></li></ul></div><p>Installing the first two together with the base operating - system on a blank system is explained in the Warp manual. If Warp - has already been installed, but you now want to install the - networking support, use the "Selective Install for Networking" - object in the "System Setup" folder.</p><p>Adding the "NetBIOS over TCP/IP" driver is not described - in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line - is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this - configuration.</p><p>If the Samba server(s) is not on your local subnet, you - can optionally add IP names and addresses of these servers - 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><h3 class="title"><a name="id2891066"></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><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"> - ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>. - See <a href="http://carol.wins.uva.nl/~leeuw/lanman.html" target="_top"> - http://carol.wins.uva.nl/~leeuw/lanman.html</a> for - more information on how to install and use this client. In - a nutshell, edit the file \OS2VER in the root directory of - the OS/2 boot partition and add the lines:</p><pre class="programlisting"> - 20=setup.exe - 20=netwksta.sys - 20=netvdd.sys - </pre><p>before you install the client. Also, don't use the - included NE2000 driver because it is buggy. Try the NE2000 - 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><h3 class="title"><a name="id2891126"></a>Are there any other issues when OS/2 (any version) - is used as a client?</h3></div></div><p>When you do a NET VIEW or use the "File and Print - Client Resource Browser", no Samba servers show up. This can - be fixed by a patch from <a href="http://carol.wins.uva.nl/~leeuw/samba/fix.html" target="_top"> - http://carol.wins.uva.nl/~leeuw/samba/fix.html</a>. - The patch will be included in a later version of Samba. It also - fixes a couple of other problems, such as preserving long - filenames when objects are dragged from the Workplace Shell - to the Samba server. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891155"></a>How do I get printer driver download working - for OS/2 clients?</h3></div></div><p>First, create a share called [PRINTDRV] that is - world-readable. Copy your OS/2 driver files there. Note - that the .EA_ files must still be separate, so you will need - to use the original install files, and not copy an installed - driver from an OS/2 system.</p><p>Install the NT driver first for that printer. Then, - add to your smb.conf a parameter, os2 driver map = - <i><tt>filename</tt></i>". Then, in the file - specified by <i><tt>filename</tt></i>, map the - name of the NT driver name to the OS/2 driver name as - follows:</p><p><b>nt driver name = os2 "driver - name"."device name"</b>, e.g.: - HP LaserJet 5L = LASERJET.HP LaserJet 5L</p><p>You can have multiple drivers mapped in this file.</p><p>If you only specify the OS/2 driver name, and not the - device name, the first attempt to download the driver will - actually download the files, but the OS/2 client will tell - 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><h2 class="title" style="clear: both"><a name="id2891218"></a>Windows for Workgroups</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891226"></a>Use latest TCP/IP stack from Microsoft</h3></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 -ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe. -There is an update.txt file there that describes the problems that were -fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386, -WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891257"></a>Delete .pwl files after password change</h3></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. -</p><p> -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><h3 class="title"><a name="id2891287"></a>Configure WfW password handling</h3></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 EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon -for it via the "Progam Manager" "New" Menu. This program allows you -to control how WFW handles passwords. ie disable Password Caching etc -for use with <b>security = user</b> -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891313"></a>Case handling of passwords</h3></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 <b>password level</b> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891344"></a>Use TCP/IP as default protocol</h3></div></div><p>To support print queue reporting you may find -that you have to use TCP/IP as the default protocol under -WfWg. For some reason if you leave Netbeui as the default -it may break the print queue reporting on some systems. -It is presumably a WfWg bug.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891361"></a>Speed improvement</h3></div></div><p> -Note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why. -</p><p> -My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891388"></a>Windows '95/'98</h2></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. -</p><p> -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><div class="orderedlist"><ol type="1"><li><p>Kernel Update: KRNLUPD.EXE</p></li><li><p>Ping Fix: PINGUPD.EXE</p></li><li><p>RPC Update: RPCRTUPD.EXE</p></li><li><p>TCP/IP Update: VIPUPD.EXE</p></li><li><p>Redirector Update: VRDRUPD.EXE</p></li></ol></div><p> -Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This -fix may stop your machine from hanging for an extended period when exiting -OutLook and you may also notice a significant speedup when accessing network -neighborhood services. -</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891458"></a>Speed improvement</h3></div></div><p> -Configure the win95 TCPIP registry settings to give better -performance. I use a program called MTUSPEED.exe 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><h2 class="title" style="clear: both"><a name="id2891475"></a>Windows 2000 Service Pack 2</h2></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 -that Samba is a member of the domain, but the problem will -likely occur if it is not. -</p><p> -In order to server profiles successfully to Windows 2000 SP2 -clients (when not operating as a PDC), Samba must have -<b>nt acl support = no</b> -added to the file share which houses the roaming profiles. -If this is not done, then the Windows 2000 SP2 client will -complain about not being able to access the profile (Access -Denied) and create multiple copies of it on disk (DOMAIN.user.001, -DOMAIN.user.002, etc...). See the -<a href="smb.conf.5.html" target="_top">smb.conf(5)</a> man page -for more details on this option. Also note that the -<b>nt acl support</b> parameter was formally a global parameter in -releases prior to Samba 2.2.2. -</p><p> -The following is a minimal profile share: -</p><pre class="programlisting"> - [profile] - path = /export/profile - create mask = 0600 - directory mask = 0700 - nt acl support = no - read only = no -</pre><p> -The reason for this bug is that the Win2k SP2 client copies -the security descriptor for the profile which contains -the Samba server's SID, and not the domain SID. The client -compares the SID for SAMBA\user and realizes it is -different that the one assigned to DOMAIN\user. Hence the reason -for the "access denied" message. -</p><p> -By disabling the <b>nt acl support</b> parameter, Samba will send -the Win2k client a response to the QuerySecurityDescriptor -trans2 call which causes the client to set a default ACL -for the profile. This default ACL includes -</p><p><b>DOMAIN\user "Full Control"</b></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><h2 class="title" style="clear: both"><a name="id2891585"></a>Windows NT 3.1</h2></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><h2 class="title"><a name="SWAT"></a>Chapter 34. SWAT - The Samba Web Admininistration Tool</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<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 class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">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 -of samba. It has a wizard that may help to get samba configured quickly, it has context -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><h2 class="title" style="clear: both"><a name="id2890961"></a>SWAT Features and Benefits</h2></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 -parameter settings, so when SWAT writes the smb.conf file to disk it will write only -those parameters that are at other than the default settings. The result is that all comments -will be lost from the smb.conf file. Additionally, the parameters will be written back in -internal ordering. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -So before using SWAT please be warned - SWAT will completely replace your smb.conf with -a fully optimised file that has been stripped of all comments you might have placed there -and only non-default settings will be written to the file. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890837"></a>Enabling SWAT for use</h3></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 <tt>inetd</tt> or -<tt>xinetd</tt> based system. -</p><p> -The nature and location of the network super-daemon varies with the operating system -implementation. The control file (or files) can be located in the file -<tt>/etc/inetd.conf</tt> or in the directory <tt>/etc/[x]inet.d</tt> -or similar. -</p><p> -The control entry for the older style file might be: -</p><pre class="programlisting"> - # swat is the Samba Web Administration Tool - swat stream tcp nowait.400 root /usr/sbin/swat swat -</pre><p> -A control file for the newer style xinetd could be: -</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, \ - # connect to port 901 with your favorite web browser. - service swat - { - port = 901 - socket_type = stream - wait = no - only_from = localhost - user = root - server = /usr/sbin/swat - log_on_failure += USERID - disable = yes - } -</pre><p> - -</p><p> -Both the above examples assume that the <tt>swat</tt> binary has been -located in the <tt>/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 -as well as other control information. The default location for this on most Linux -systems is in the directory <tt>/usr/share/samba/swat</tt>. The default -location using samba defaults will be <tt>/usr/local/samba/swat</tt>. -</p><p> -Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user -the only permission allowed is to view certain aspects of configuration as well as -access to the password change facility. The buttons that will be exposed to the non-root -user are: <span class="emphasis"><em>HOME, STATUS, VIEW, PASSWORD</em></span>. The only page that allows -change capability in this case is <span class="emphasis"><em>PASSWORD</em></span>. -</p><p> -So long as you log onto SWAT as the user <b>root</b> you should obtain -full change and commit ability. The buttons that will be exposed includes: -<span class="emphasis"><em>HOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD</em></span>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891873"></a>Securing SWAT through SSL</h3></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="itemizedlist"><ul type="disc"><li><p> - install OpenSSL - </p></li><li><p> - generate certificate and private key - - </p><pre class="programlisting"> - root# /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 - </pre></li><li><p> - remove swat-entry from [x]inetd - </p></li><li><p> - start stunnel - - </p><pre class="programlisting"> - root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \ - -l /usr/local/samba/bin/swat swat - </pre></li></ul></div><p> -afterwards simply contact to swat by using the URL "https://myhost:901", accept the certificate -and the SSL connection is up. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891946"></a>The SWAT Home Page</h3></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 -also. One diagnostic tool that is NOT mentioned on this page, but that is particularly -useful is <b>ethereal</b>, available from <a href="http://www.ethereal.com" target="_top"> -http://www.ethereal.com</a>. -</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</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 -creates this ability is the <b>-a</b> flag to swat. DO NOT USE THIS IN ANY -PRODUCTION ENVIRONMENT - you have been warned! -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892010"></a>Global Settings</h3></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> - <b>Basic</b> - exposes common configuration options. - </p></li><li><p> - <b>Advanced</b> - exposes configuration options needed in more - complex environments. - </p></li><li><p> - <b>Developer</b> - exposes configuration options that only the brave - will want to tamper with. - </p></li></ul></div><p> -To switch to other than <span class="emphasis"><em>Basic</em></span> editing ability click on either the -<span class="emphasis"><em>Advanced</em></span> or the <span class="emphasis"><em>Developer</em></span> dial, then click the -<span class="emphasis"><em>Commit Changes</em></span> button. -</p><p> -After making any changes to configuration parameters make sure that you click on the -<span class="emphasis"><em>Commit Changes</em></span> button before moving to another area otherwise -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 -<b>Help</b> link to the left of the configurartion parameter. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892118"></a>Share Settings</h3></div></div><p> -To affect a currenly configured share, simply click on the pull down button between the -<span class="emphasis"><em>Choose Share</em></span> and the <span class="emphasis"><em>Delete Share</em></span> buttons, -select the share you wish to operate on, then to edit the settings click on the -<span class="emphasis"><em>Choose Share</em></span> button, to delete the share simply press the -<span class="emphasis"><em>Delete Share</em></span> button. -</p><p> -To create a new share, next to the button labelled <span class="emphasis"><em>Create Share</em></span> enter -into the text field the name of the share to be created, then click on the -<span class="emphasis"><em>Create Share</em></span> button. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892167"></a>Printers Settings</h3></div></div><p> -To affect a currenly configured printer, simply click on the pull down button between the -<span class="emphasis"><em>Choose Printer</em></span> and the <span class="emphasis"><em>Delete Printer</em></span> buttons, -select the printer you wish to operate on, then to edit the settings click on the -<span class="emphasis"><em>Choose Printer</em></span> button, to delete the share simply press the -<span class="emphasis"><em>Delete Printer</em></span> button. -</p><p> -To create a new printer, next to the button labelled <span class="emphasis"><em>Create Printer</em></span> enter -into the text field the name of the share to be created, then click on the -<span class="emphasis"><em>Create Printer</em></span> button. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892216"></a>The SWAT Wizard</h3></div></div><p> -The purpose if the SWAT Wizard is to help the Microsoft knowledgable 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. -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="emphasis"><em>Edit</em></span> button permits the editing (setting) of the minimal set of -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 -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 -home directories. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892261"></a>The Status Page</h3></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: <b> smbd, nmbd, winbindd</b>. -</p><p> -The daemons may be controlled individually or as a total group. Additionally, you may set -an automatic screen refresh timing. As MS Windows clients interact with Samba new smbd processes -will be continually spawned. The auto-refresh facility will allow you to track the changing -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><h3 class="title"><a name="id2892300"></a>The View Page</h3></div></div><p> -This page allows the administrator to view the optimised smb.conf file and if you are -particularly massochistic 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><h3 class="title"><a name="id2892316"></a>The Password Change Page</h3></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. -</p><p> -When logged in as a non-root account the user will have to provide the old password as well as -the new password (twice). When logged in as <b>root</b> only the new password is -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 class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="speed"></a>Chapter 35. Samba performance issues</h2></div><div><div class="author"><h3 class="author">Paul Cochrane</h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt><<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">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891608"></a>Comparisons</h2></div></div><p> -The Samba server uses TCP to talk to the client. Thus if you are -trying to see if it performs well you should really compare it to -programs that use the same protocol. The most readily available -programs for file transfer that use TCP are ftp or another TCP based -SMB server. -</p><p> -If you want to test against something like a NT or WfWg server then -you will have to disable all but TCP on either the client or -server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid. -</p><p> -Generally you should find that Samba performs similarly to ftp at raw -transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system. -</p><p> -Several people have done comparisons between Samba and Novell, NFS or -WinNT. In some cases Samba performed the best, in others the worst. I -suspect the biggest factor is not Samba vs some other system but the -hardware and drivers used on the various systems. Given similar -hardware Samba should certainly be competitive in speed with other -systems. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891653"></a>Socket options</h2></div></div><p> -There are a number of socket options that can greatly affect the -performance of a TCP based server like Samba. -</p><p> -The socket options that Samba uses are settable both on the command -line with the -O option, or in the smb.conf file. -</p><p> -The <b>socket options</b> section of the <tt>smb.conf</tt> manual page describes how -to set these and gives recommendations. -</p><p> -Getting the socket options right can make a big difference to your -performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network. -</p><p> -The socket option TCP_NODELAY is the one that seems to make the -biggest single difference for most networks. Many people report that -adding <b>socket options = TCP_NODELAY</b> 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><h2 class="title" style="clear: both"><a name="id2892541"></a>Read size</h2></div></div><p> -The option <b>read size</b> affects the overlap of disk -reads/writes with network reads/writes. If the amount of data being -transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and -SMBreadbraw) is larger than this value then the server begins writing -the data before it has received the whole packet from the network, or -in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk. -</p><p> -This overlapping works best when the speeds of disk and network access -are similar, having very little effect when the speed of one is much -greater than the other. -</p><p> -The default value is 16384, but very little experimentation has been -done yet to determine the optimal value, and it is likely that the best -value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892584"></a>Max xmit</h2></div></div><p> -At startup the client and server negotiate a <b>maximum transmit</b> size, -which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the <b>max xmit = </b> option -in <tt>smb.conf</tt>. Note that this is the maximum size of SMB requests that -Samba will accept, but not the maximum size that the *client* will accept. -The client maximum receive size is sent to Samba by the client and Samba -honours this limit. -</p><p> -It defaults to 65536 bytes (the maximum), but it is possible that some -clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems. -</p><p> -In most cases the default is the best option. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892637"></a>Log level</h2></div></div><p> -If you set the log level (also known as <b>debug level</b>) 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><h2 class="title" style="clear: both"><a name="id2892660"></a>Read raw</h2></div></div><p> -The <b>read raw</b> 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 <b>read raw</b> optional, with it -being enabled by default. -</p><p> -In some cases clients don't handle <b>read raw</b> very well and actually -get lower performance using it than they get using the conventional -read operations. -</p><p> -So you might like to try <b>read raw = no</b> 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><h2 class="title" style="clear: both"><a name="id2892717"></a>Write raw</h2></div></div><p> -The <b>write raw</b> 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 <b>write raw</b> optional, with it -being enabled by default. -</p><p> -Some machines may find <b>write raw</b> 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><h2 class="title" style="clear: both"><a name="id2892759"></a>Slow Logins</h2></div></div><p> -Slow logins are almost always due to the password checking time. Using -the lowest practical <b>password level</b> will improve things. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892781"></a>Client tuning</h2></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 33. Samba and other CIFS clients">Samba and Other Clients</a>. -</p></div></div></div></div></body></html> |