samba.git - Unnamed repository; edit this file 'description' to name the repository.

diff options

author	Günther Deschner <gd@samba.org>	2011-01-12 22:53:52 +0100
committer	Andreas Schneider <asn@samba.org>	2011-01-13 14:16:39 +0100
commit	166504adb711e0bf582d71c38f5b08beb2806978 (patch)
tree	9bf100cd0cfb41ded0fc6c4e4c634df0114053b7 /source3/lib/util.c
parent	da433458e5ba82e9cf94aed04ecfcda89b287331 (diff)
download	samba-166504adb711e0bf582d71c38f5b08beb2806978.tar.gz samba-166504adb711e0bf582d71c38f5b08beb2806978.tar.xz samba-166504adb711e0bf582d71c38f5b08beb2806978.zip

s3-net_registry: prefer dcerpc_winreg_X functions.

Guenther Signed-off-by: Andreas Schneider <asn@samba.org>

Diffstat (limited to 'source3/lib/util.c')

0 files changed, 0 insertions, 0 deletions

<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.60.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 Vernooij, John H. 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 HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. "></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>SAMBA Project Documentation</h1></div><div><div class="authorgroup"><h4 class="editedby">Edited by</h4><h3 class="editor"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><h3 class="editor"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><h3 class="editor"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3></div></div><div><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 Vernooij</a>, <a href="mailto:jht@samba.org" target="_top">John H. 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 HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. </p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2852328">Legal Notice</a></dt><dt><a href="#id2852352">Attributions</a></dt><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2800382">Background</a></dt><dt><a href="#id2800440">Terminology</a></dt><dt><a href="#id2800631">Related Projects</a></dt><dt><a href="#id2800699">SMB Methodology</a></dt><dt><a href="#id2800808">Epilogue</a></dt><dt><a href="#id2800892">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2866386">Obtaining and installing samba</a></dt><dt><a href="#id2866430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2866468">Example Configuration</a></dt><dt><a href="#id2866661">SWAT</a></dt></dl></dd><dt><a href="#id2866706">Try listing the shares available on your server</a></dt><dt><a href="#id2866764">Try connecting with the unix client</a></dt><dt><a href="#id2866881">Try connecting from another SMB client</a></dt><dt><a href="#id2866964">What If Things Don't Work?</a></dt><dt><a href="#id2866997">Common Errors</a></dt><dd><dl><dt><a href="#id2867010">Large number of smbd processes</a></dt><dt><a href="#id2867109">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2867129">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2867256">Note</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2867445">Features and Benefits</a></dt><dt><a href="#id2867540">Server Types</a></dt><dt><a href="#id2867626">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867745">User Level Security</a></dt><dt><a href="#id2867883">Share Level Security</a></dt><dt><a href="#id2868020">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2868278">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2868379">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868660">Password checking</a></dt><dt><a href="#id2868855">Common Errors</a></dt><dd><dl><dt><a href="#id2868882">What makes Samba a SERVER?</a></dt><dt><a href="#id2868923">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868959">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868998">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2869330">Features and Benefits</a></dt><dt><a href="#id2869545">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869560">Domain Controller Types</a></dt><dt><a href="#id2869805">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2870187">Domain Control - Example Configuration</a></dt><dt><a href="#id2870675">Samba ADS Domain Control</a></dt><dt><a href="#id2870727">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870742">Domain Network Logon Service</a></dt><dt><a href="#id2871174">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2871320">Common Errors</a></dt><dd><dl><dt><a href="#id2871328">'$' cannot be included in machine name</a></dt><dt><a href="#id2871386">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2871445">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871529">The machine trust account not accessible</a></dt><dt><a href="#id2871602">Account disabled</a></dt><dt><a href="#id2871634">Domain Controller Unavailable</a></dt><dt><a href="#id2871658">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2871817">Features And Benefits</a></dt><dt><a href="#id2872006">Essential Background Information</a></dt><dd><dl><dt><a href="#id2872035">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2872286">Active Directory Domain Control</a></dt><dt><a href="#id2872307">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2872332">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2872346">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2872480">Example Configuration</a></dt></dl></dd><dt><a href="#id2872638">Common Errors</a></dt><dd><dl><dt><a href="#id2872650">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872682">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872708">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872753">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2872960">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2873290">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873596">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873811">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873884">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2874094">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2874530">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874715">Setup your smb.conf</a></dt><dt><a href="#id2874844">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2875221">Notes</a></dt></dl></dd><dt><a href="#id2875243">Common Errors</a></dt><dd><dl><dt><a href="#id2875286">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2875318">Adding Machine to Domain Fails</a></dt><dt><a href="#id2875462">I can't join a Windows 2003 PDC</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2875549">Features and Benefits</a></dt><dt><a href="#id2875587">Background</a></dt><dt><a href="#id2875661">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2876184">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2876248">Note</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2876401">Features and Benefits</a></dt><dt><a href="#id2876490">What is Browsing?</a></dt><dt><a href="#id2876803">Discussion</a></dt><dd><dl><dt><a href="#id2876818">NetBIOS over TCP/IP</a></dt><dt><a href="#id2877054">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2877219">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2877367">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877916">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2878314">Making Samba the domain master</a></dt><dt><a href="#id2878491">Note about broadcast addresses</a></dt><dt><a href="#id2878515">Multiple interfaces</a></dt><dt><a href="#id2878551">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878708">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878786">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878975">Setting up a WINS server</a></dt><dt><a href="#id2879231">WINS Replication</a></dt><dt><a href="#id2879256">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2879345">Helpful Hints</a></dt><dd><dl><dt><a href="#id2879358">Windows Networking Protocols</a></dt><dt><a href="#id2879437">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2879603">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879656">Browsing support in Samba</a></dt><dt><a href="#id2879778">Problem resolution</a></dt><dt><a href="#id2879866">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2880547">Common Errors</a></dt><dd><dl><dt><a href="#id2880562">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2880591">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880635">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2880915">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880929">Backwards Compatibility Backends</a></dt><dt><a href="#id2881032">New Backends</a></dt></dl></dd><dt><a href="#id2881219">Technical Information</a></dt><dd><dl><dt><a href="#id2881344">Important Notes About Security</a></dt><dt><a href="#id2881634">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881821">The smbpasswd Command</a></dt><dt><a href="#id2882092">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2882329">Password Backends</a></dt><dd><dl><dt><a href="#id2882371">Plain Text</a></dt><dt><a href="#id2882412">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2882525">tdbsam</a></dt><dt><a href="#id2882559">ldapsam</a></dt><dt><a href="#id2884412">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2885260">Common Errors</a></dt><dd><dl><dt><a href="#id2885267">Users can not logon</a></dt><dt><a href="#id2885312">Users being added to wrong backend database</a></dt><dt><a href="#id2885422">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2885652">Features and Benefits</a></dt><dt><a href="#id2885887">Discussion</a></dt><dd><dl><dt><a href="#id2886122">Example Configuration</a></dt></dl></dd><dt><a href="#id2886189">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2886202">Sample smb.conf add group script</a></dt><dt><a href="#id2886288">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2886372">Common Errors</a></dt><dd><dl><dt><a href="#id2886386">Adding Groups Fails</a></dt><dt><a href="#id2886455">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2886481">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2886736">Features and Benefits</a></dt><dt><a href="#id2886866">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886902">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2887207">Managing Directories</a></dt><dt><a href="#id2887301">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2887513">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2887541">User and Group Based Controls</a></dt><dt><a href="#id2887963">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2888342">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888722">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888794">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2889094">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2889102">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2889146">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2889226">Viewing file ownership</a></dt><dt><a href="#id2889358">Viewing File or Directory Permissions</a></dt><dt><a href="#id2889603">Modifying file or directory permissions</a></dt><dt><a href="#id2889768">Interaction with the standard Samba create mask parameters</a></dt><dt><a href="#id2890164">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2890260">Common Errors</a></dt><dd><dl><dt><a href="#id2890274">Users can not write to a public share</a></dt><dt><a href="#id2890703">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890755">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2891003">Features and Benefits</a></dt><dt><a href="#id2891060">Discussion</a></dt><dd><dl><dt><a href="#id2891204">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891921">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2892041">Example Configuration</a></dt></dl></dd><dt><a href="#id2892456">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2892680">Workstation Service Entries</a></dt><dt><a href="#id2892709">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892788">Persistent Data Corruption</a></dt><dt><a href="#id2892817">Common Errors</a></dt><dd><dl><dt><a href="#id2892891">locking.tdb error messages</a></dt><dt><a href="#id2892930">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892952">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892983">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2893158">Introduction</a></dt><dt><a href="#id2893195">Features and Benefits</a></dt><dt><a href="#id2893269">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2893288">Using host based protection</a></dt><dt><a href="#id2893387">User based protection</a></dt><dt><a href="#id2893447">Using interface protection</a></dt><dt><a href="#id2893515">Using a firewall</a></dt><dt><a href="#id2893572">Using a IPC$ share deny</a></dt><dt><a href="#id2893660">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2893719">Upgrading Samba</a></dt><dt><a href="#id2893743">Common Errors</a></dt><dd><dl><dt><a href="#id2893761">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2893786">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2894077">Features and Benefits</a></dt><dt><a href="#id2894106">Trust Relationship Background</a></dt><dt><a href="#id2894193">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2894221">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2894294">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2894341">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2894518">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2894704">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894842">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894948">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2895017">Features and Benefits</a></dt><dt><a href="#id2895292">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2895411">Features and Benefits</a></dt><dt><a href="#id2895517">Technical Introduction</a></dt><dd><dl><dt><a href="#id2895555">What happens if you send a Job from a Client</a></dt><dt><a href="#id2895627">Printing Related Configuration Parameters</a></dt><dt><a href="#id2895722">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2896188">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2896354">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2896481">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2896843">Extended Sample Configuration to Print</a></dt><dt><a href="#id2897173">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2897186">The [global] Section</a></dt><dt><a href="#id2897717">The [printers] Section</a></dt><dt><a href="#id2898177">Any [my_printer_name] Section</a></dt><dt><a href="#id2898498">Print Commands</a></dt><dt><a href="#id2898580">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2899263">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2899603">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2899763">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2899925">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2900037">Creating the [print$] Share</a></dt><dt><a href="#id2900227">Parameters in the [print$] Section</a></dt><dt><a href="#id2900537">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2900710">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2900805">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2901002">Setting Drivers for existing Printers with rpcclient</a></dt></dl></dd><dt><a href="#id2902712">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2902731">The first Client Driver Installation</a></dt><dt><a href="#id2902934">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2903234">Further Client Driver Install Procedures</a></dt><dt><a href="#id2903328">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2903500">Other Gotchas</a></dt><dd><dl><dt><a href="#id2903534">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2904001">Supporting large Numbers of Printers</a></dt><dt><a href="#id2904312">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2904606">Weird Error Message Cannot connect under a different Name</a></dt><dt><a href="#id2904706">Be careful when assembling Driver Files</a></dt><dt><a href="#id2905065">Samba and Printer Ports</a></dt><dt><a href="#id2905158">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2905183">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2905239">What is Imprints?</a></dt><dt><a href="#id2905280">Creating Printer Driver Packages</a></dt><dt><a href="#id2905299">The Imprints Server</a></dt><dt><a href="#id2905323">The Installation Client</a></dt></dl></dd><dt><a href="#id2905478">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2905813">The addprinter command</a></dt><dt><a href="#id2905859">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2906032">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2906044">Common Errors</a></dt><dd><dl><dt><a href="#id2906050">I give my root password but I don't get access</a></dt><dt><a href="#id2906085">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2906220">Introduction</a></dt><dd><dl><dt><a href="#id2906227">Features and Benefits</a></dt><dt><a href="#id2906281">Overview</a></dt></dl></dd><dt><a href="#id2906348">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2906443">Linking of smbd with libcups.so</a></dt><dt><a href="#id2906684">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2906866">More complex smb.conf Settings for CUPS</a></dt></dl></dd><dt><a href="#id2907221">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2907241">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2907296">CUPS/Samba as a "spooling-only" Print Server; "raw" printing with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2907365">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2907441">Explicitly enable "raw" printing for application/octet-stream!</a></dt><dt><a href="#id2907647">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2907785">Using CUPS/Samba in an advanced Way -- intelligent printing with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2907968">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2908120">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2908420">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2908563">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2908649">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2908755">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2908777">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2908970">MIME types and CUPS Filters</a></dt><dt><a href="#id2909178">MIME type Conversion Rules</a></dt><dt><a href="#id2909333">Filter Requirements</a></dt><dt><a href="#id2909513">Prefilters</a></dt><dt><a href="#id2909624">pstops</a></dt><dt><a href="#id2909734">pstoraster</a></dt><dt><a href="#id2909928">imagetops and imagetoraster</a></dt><dt><a href="#id2909993">rasterto [printers specific]</a></dt><dt><a href="#id2910145">CUPS Backends</a></dt><dt><a href="#id2910493">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2910637">The Complete Picture</a></dt><dt><a href="#id2910653">mime.convs</a></dt><dt><a href="#id2910716">"Raw" printing</a></dt><dt><a href="#id2910805">"application/octet-stream" printing</a></dt><dt><a href="#id2911052">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2911319">Difference between cupsomatic/foomatic-rip and native CUPS printing</a></dt><dt><a href="#id2911554">Examples for filtering Chains</a></dt><dt><a href="#id2911891">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2912041">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2912139">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2912150">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2912212">Driver Execution on the Client</a></dt><dt><a href="#id2912287">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2912407">Network Printing (Windows clients -- UNIX/Samba Print Servers)</a></dt><dd><dl><dt><a href="#id2912426">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2912640">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2912726">Network PostScript RIP: CUPS Filters on Server -- clients use PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2912815">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2912871">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2912948">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2912964">Printer Drivers running in "Kernel Mode" cause many Problems</a></dt><dt><a href="#id2913011">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2913032">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2913085">PostScript Drivers with no major problems -- even in Kernel Mode</a></dt></dl></dd><dt><a href="#id2913108">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2913163">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2913282">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2913502">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2913789">Recognize the different Driver Files</a></dt><dt><a href="#id2913932">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2913965">ESP Print Pro Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2914035">Caveats to be considered</a></dt><dt><a href="#id2914308">Benefits of using "CUPS PostScript Driver for Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2914525">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2914652">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2914873">Understanding cupsaddsmb</a></dt><dt><a href="#id2915022">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2915105">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2915185">cupsaddsmb Flowchart</a></dt><dt><a href="#id2915261">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2915425">Avoiding critical PostScript Driver Settings on the Client</a></dt></dl></dd><dt><a href="#id2915559">Installing PostScript Driver Files manually (using rpcclient)</a></dt><dd><dl><dt><a href="#id2915762">A Check of the rpcclient man Page</a></dt><dt><a href="#id2915876">Understanding the rpcclient man page</a></dt><dt><a href="#id2915981">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2916147">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2916361">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2917432">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2917593">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2917838">Trivial DataBase Files</a></dt><dt><a href="#id2917930">Binary Format</a></dt><dt><a href="#id2917994">Losing *.tdb Files</a></dt><dt><a href="#id2918053">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2918189">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2918345">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2919115">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2919616">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2919667">Setting up Quotas</a></dt><dt><a href="#id2919734">Correct and incorrect Accounting</a></dt><dt><a href="#id2919778">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2919874">The page_log File Syntax</a></dt><dt><a href="#id2919991">Possible Shortcomings</a></dt><dt><a href="#id2920067">Future Developments</a></dt><dt><a href="#id2920123">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2920136">Additional Material</a></dt><dt><a href="#id2920387">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2920450">CUPS Configuration Settings explained</a></dt><dt><a href="#id2920543">Pre-conditions</a></dt><dt><a href="#id2920702">Manual Configuration</a></dt></dl></dd><dt><a href="#id2920760">In Case of Trouble.....</a></dt><dt><a href="#id2920832">Printing from CUPS to Windows attached Printers</a></dt><dt><a href="#id2921130">More CUPS filtering Chains</a></dt><dt><a href="#id2921233">Common Errors</a></dt><dd><dl><dt><a href="#id2921241">Win9x client can't install driver</a></dt><dt><a href="#id2921263">"cupsaddsmb" keeps asking for root password in neverending loop</a></dt><dt><a href="#id2921311">"cupsaddsmb" gives "No PPD file for printer..." message while PPD file is present</a></dt><dt><a href="#id2921368">Client can't connect to Samba printer</a></dt><dt><a href="#id2921397">Can't reconnect to Samba under new account from Win2K/XP</a></dt><dt><a href="#id2921624">Avoid being connected to the Samba server as the "wrong" user</a></dt><dt><a href="#id2921678">Upgrading to CUPS drivers from Adobe drivers on NT/2K/XP clients gives problems</a></dt><dt><a href="#id2921695">Can't use "cupsaddsmb" on Samba server which is a PDC</a></dt><dt><a href="#id2921726">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2921734">Win2K/XP "Local Security Policies"</a></dt><dt><a href="#id2921774">WinXP clients: "Administrator can not install printers for all local users"</a></dt><dt><a href="#id2921808">"Print Change Notify" functions on NT-clients</a></dt><dt><a href="#id2921830">WinXP-SP1</a></dt><dt><a href="#id2921875">Print options for all users can't be set on Win2K/XP</a></dt><dt><a href="#id2922164">Most common blunders in driver settings on Windows clients</a></dt><dt><a href="#id2922210">cupsaddsmb does not work with newly installed printer</a></dt><dt><a href="#id2922272">Permissions on /var/spool/samba/ get reset after each reboot</a></dt><dt><a href="#id2922380">Printer named "lp" intermittently swallows jobs and spits out completely different ones</a></dt><dt><a href="#id2922428">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2922484">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2922653">Features and Benefits</a></dt><dt><a href="#id2922671">Discussion</a></dt><dt><a href="#id2922900">Included modules</a></dt><dd><dl><dt><a href="#id2922907">audit</a></dt><dt><a href="#id2922950">extd_audit</a></dt><dt><a href="#id2923080">fake_perms</a></dt><dt><a href="#id2923099">recycle</a></dt><dt><a href="#id2923274">netatalk</a></dt></dl></dd><dt><a href="#id2923320">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2923342">DatabaseFS</a></dt><dt><a href="#id2923396">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2923626">Features and Benefits</a></dt><dt><a href="#id2923721">Introduction</a></dt><dt><a href="#id2923799">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2923876">Target Uses</a></dt></dl></dd><dt><a href="#id2923906">How Winbind Works</a></dt><dd><dl><dt><a href="#id2923935">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2923968">Microsoft Active Directory Services</a></dt><dt><a href="#id2923991">Name Service Switch</a></dt><dt><a href="#id2924127">Pluggable Authentication Modules</a></dt><dt><a href="#id2924199">User and Group ID Allocation</a></dt><dt><a href="#id2924232">Result Caching</a></dt></dl></dd><dt><a href="#id2924260">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2924268">Introduction</a></dt><dt><a href="#id2924335">Requirements</a></dt><dt><a href="#id2924429">Testing Things Out</a></dt></dl></dd><dt><a href="#id2926036">Conclusion</a></dt><dt><a href="#id2926054">Common Errors</a></dt><dd><dl><dt><a href="#id2926108">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2926216">Features and Benefits</a></dt><dt><a href="#id2926247">Remote Server Administration</a></dt><dt><a href="#id2926346">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2926363">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2926605">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2926843">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2926877">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2926955">Features and Benefits</a></dt><dt><a href="#id2927014">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2927128">Windows 9x/Me Policies</a></dt><dt><a href="#id2927223">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2927356">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2927608">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2927714">Samba Editreg Toolset</a></dt><dt><a href="#id2927753">Windows NT4/200x</a></dt><dt><a href="#id2927776">Samba PDC</a></dt></dl></dd><dt><a href="#id2927822">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2927973">Common Errors</a></dt><dd><dl><dt><a href="#id2927986">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2928087">Features and Benefits</a></dt><dt><a href="#id2928120">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2928161">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2928652">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2929902">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2929987">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2930246">Mandatory profiles</a></dt><dt><a href="#id2930304">Creating/Managing Group Profiles</a></dt><dt><a href="#id2930349">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2930369">MS Windows 9x/Me</a></dt><dt><a href="#id2930521">MS Windows NT4 Workstation</a></dt><dt><a href="#id2931076">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2931594">Common Errors</a></dt><dd><dl><dt><a href="#id2931607">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2931676">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2931889">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2932170">Features and Benefits</a></dt><dt><a href="#id2932418">Technical Discussion</a></dt><dd><dl><dt><a href="#id2932435">PAM Configuration Syntax</a></dt><dt><a href="#id2933099">Example System Configurations</a></dt><dt><a href="#id2933403">smb.conf PAM Configuration</a></dt><dt><a href="#id2933482">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2933565">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2933949">Common Errors</a></dt><dd><dl><dt><a href="#id2933962">pam_winbind problem</a></dt><dt><a href="#id2934050">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2934288">Features and Benefits</a></dt><dt><a href="#id2934312">Background Information</a></dt><dt><a href="#id2934378">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2934434">/etc/hosts</a></dt><dt><a href="#id2934584">/etc/resolv.conf</a></dt><dt><a href="#id2934626">/etc/host.conf</a></dt><dt><a href="#id2934679">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2934793">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2935103">The NetBIOS Name Cache</a></dt><dt><a href="#id2935167">The LMHOSTS file</a></dt><dt><a href="#id2935329">HOSTS file</a></dt><dt><a href="#id2935361">DNS Lookup</a></dt><dt><a href="#id2935393">WINS Lookup</a></dt></dl></dd><dt><a href="#id2935511">Common Errors</a></dt><dd><dl><dt><a href="#id2935527">Pinging works only in one way</a></dt><dt><a href="#id2935562">Very Slow Network Connections</a></dt><dt><a href="#id2935612">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2935816">Features and Benefits</a></dt><dt><a href="#id2935861">What are charsets and unicode?</a></dt><dt><a href="#id2935930">Samba and charsets</a></dt><dt><a href="#id2936058">Conversion from old names</a></dt><dt><a href="#id2936088">Japanese charsets</a></dt><dt><a href="#id2936225">Common errors</a></dt><dd><dl><dt><a href="#id2936232">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2936346">Note</a></dt><dt><a href="#id2936359">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2936430">Note</a></dt></dl></dd></dl></dd><dt>IV. <a href="#migration">Migration and Updating</a></dt><dd><dl><dt>30. <a href="#upgrading-to-3.0">Upgrading from Samba-2.x to Samba-3.0.0</a></dt><dd><dl><dt><a href="#id2936568">New Features in Samba-3</a></dt><dt><a href="#id2936703">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="#id2936719">Removed Parameters</a></dt><dt><a href="#id2936845">New Parameters</a></dt><dt><a href="#id2937241">Modified Parameters (changes in behavior):</a></dt></dl></dd><dt><a href="#id2937316">New Functionality</a></dt><dd><dl><dt><a href="#id2937323">Databases</a></dt><dt><a href="#id2937557">Changes in Behavior</a></dt><dt><a href="#id2937607">Charsets</a></dt><dt><a href="#id2937630">Passdb Backends and Authentication</a></dt><dt><a href="#id2937749">Charsets</a></dt><dt><a href="#id2937773">LDAP</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2938118">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2938143">Objectives</a></dt><dt><a href="#id2938581">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2938798">Migration Options</a></dt><dd><dl><dt><a href="#id2938888">Planning for Success</a></dt><dt><a href="#id2939144">Samba-3 Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#SWAT">SWAT - The Samba Web Administration Tool</a></dt><dd><dl><dt><a href="#id2939504">Features and Benefits</a></dt><dd><dl><dt><a href="#id2939553">Enabling SWAT for use</a></dt><dt><a href="#id2939790">Securing SWAT through SSL</a></dt><dt><a href="#id2939902">The SWAT Home Page</a></dt><dt><a href="#id2939968">Global Settings</a></dt><dt><a href="#id2940074">Share Settings</a></dt><dt><a href="#id2940138">Printers Settings</a></dt><dt><a href="#id2940203">The SWAT Wizard</a></dt><dt><a href="#id2940250">The Status Page</a></dt><dt><a href="#id2940302">The View Page</a></dt><dt><a href="#id2940326">The Password Change Page</a></dt></dl></dd></dl></dd></dl></dd><dt>V. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>33. <a href="#diagnosis">The Samba checklist</a></dt><dd><dl><dt><a href="#id2940455">Introduction</a></dt><dt><a href="#id2940496">Assumptions</a></dt><dt><a href="#id2940722">The tests</a></dt></dl></dd><dt>34. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2942220">Diagnostics tools</a></dt><dd><dl><dt><a href="#id2942241">Debugging with Samba itself</a></dt><dt><a href="#id2942367">Tcpdump</a></dt><dt><a href="#id2942389">Ethereal</a></dt><dt><a href="#id2942441">The Windows Network Monitor</a></dt></dl></dd><dt><a href="#id2942759">Useful URLs</a></dt><dt><a href="#id2942799">Getting help from the mailing lists</a></dt><dt><a href="#id2942958">How to get off the mailing lists</a></dt></dl></dd><dt>35. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2943087">Introduction</a></dt><dt><a href="#id2943154">General info</a></dt><dt><a href="#id2943191">Debug levels</a></dt><dt><a href="#id2943400">Internal errors</a></dt><dt><a href="#id2943534">Attaching to a running process</a></dt><dt><a href="#id2943580">Patches</a></dt></dl></dd></dl></dd><dt>VI. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>36. <a href="#compiling">How to compile Samba</a></dt><dd><dl><dt><a href="#id2943739">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2943756">Introduction</a></dt><dt><a href="#id2943794">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2944055">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2944120">Verifying Samba's PGP signature</a></dt><dt><a href="#id2944272">Building the Binaries</a></dt><dd><dl><dt><a href="#id2944452">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2944619">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2944727">Starting from inetd.conf</a></dt><dt><a href="#id2944974">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>37. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2945137">HPUX</a></dt><dt><a href="#id2945225">SCO UNIX</a></dt><dt><a href="#id2945255">DNIX</a></dt><dt><a href="#id2945428">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2945472">AIX</a></dt><dd><dl><dt><a href="#id2945479">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2945504">Solaris</a></dt><dd><dl><dt><a href="#id2945511">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>38. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2945664">Macintosh clients?</a></dt><dt><a href="#id2945743">OS2 Client</a></dt><dd><dl><dt><a href="#id2945750">Configuring OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba</a></dt><dt><a href="#id2945834">Configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba</a></dt><dt><a href="#id2945887">Printer driver download for for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2945987">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2945995">Latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2946085">Delete .pwl files after password change</a></dt><dt><a href="#id2946115">Configuring WfW password handling</a></dt><dt><a href="#id2946168">Case handling of passwords</a></dt><dt><a href="#id2946205">Use TCP/IP as default protocol</a></dt><dt><a href="#id2946222">Speed improvement</a></dt></dl></dd><dt><a href="#id2946269">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2946343">Speed improvement</a></dt></dl></dd><dt><a href="#id2946367">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2946555">Windows NT 3.1</a></dt></dl></dd><dt>39. <a href="#speed">Samba Performance Tuning</a></dt><dd><dl><dt><a href="#id2946684">Comparisons</a></dt><dt><a href="#id2946728">Socket options</a></dt><dt><a href="#id2946819">Read size</a></dt><dt><a href="#id2946869">Max xmit</a></dt><dt><a href="#id2946928">Log level</a></dt><dt><a href="#id2946959">Read raw</a></dt><dt><a href="#id2947043">Write raw</a></dt><dt><a href="#id2947106">Slow Logins</a></dt><dt><a href="#id2947135">Client tuning</a></dt><dt><a href="#id2947160">Samba performance problem due changing kernel</a></dt><dt><a href="#id2947192">Corrupt tdb Files</a></dt></dl></dd><dt>40. <a href="#DNSDHCP">DNS and DHCP Configuration Guide</a></dt><dd><dl><dt><a href="#id2947297">Note</a></dt></dl></dd><dt>41. <a href="#Further-Resources">Further Resources</a></dt><dd><dl><dt><a href="#id2947365">Websites</a></dt><dt><a href="#id2947755">Related updates from Microsoft</a></dt></dl></dd></dl></dd><dt><a href="#id2947825">Index</a></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>5.1. <a href="#domain-example">An Example Domain</a></dt><dt>10.1. <a href="#browsing1">Cross subnet browsing example</a></dt><dt>11.1. <a href="#idmap-diag">IDMAP</a></dt><dt>12.1. <a href="#idmap-group-diag">IDMAP groups</a></dt><dt>13.1. <a href="#access1">Overview of unix permissions field</a></dt><dt>16.1. <a href="#trusts1">Trusts overview</a></dt><dt>19.1. <a href="#small1">Windows Printing to a local Printer</a></dt><dt>19.2. <a href="#small2">Printing to a Postscript Printer</a></dt><dt>19.3. <a href="#small3">Ghostscript as a RIP for non-postscript printers</a></dt><dt>19.4. <a href="#small4">Prefiltering in CUPS to form Postscript</a></dt><dt>19.5. <a href="#small5">Adding Device-specific Print Options</a></dt><dt>19.6. <a href="#small6">Postscript to intermediate Raster format</a></dt><dt>19.7. <a href="#small7">CUPS-raster production using Ghostscript</a></dt><dt>19.8. <a href="#small8">Image format to CUPS-raster format conversion</a></dt><dt>19.9. <a href="#small9">Raster to Printer Specific formats</a></dt><dt>19.10. <a href="#small10">cupsomatic/foomatic processing versus Native CUPS</a></dt><dt>19.11. <a href="#pdftosocket">PDF to socket chain</a></dt><dt>19.12. <a href="#pdftoepsonusb">PDF to USB chain</a></dt><dt>19.13. <a href="#small11">Print Driver execution on the Client</a></dt><dt>19.14. <a href="#small12">Print Driver execution on the Server</a></dt><dt>19.15. <a href="#small13">Printing via CUPS/samba server</a></dt><dt>19.16. <a href="#small14">cupsaddsmb flowchart</a></dt><dt>19.17. <a href="#cups1">Filtering chain 1</a></dt><dt>19.18. <a href="#cups2">Filtering chain with cupsomatic</a></dt><dt>19.19. <a href="#a_small">CUPS Printing Overview</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id2874105">Assumptions</a></dt><dt>10.1. <a href="#id2880049">Browse subnet example 1</a></dt><dt>10.2. <a href="#id2880162">Browse subnet example 2</a></dt><dt>10.3. <a href="#id2880274">Browse subnet example 3</a></dt><dt>10.4. <a href="#id2880391">Browse subnet example 4</a></dt><dt>11.1. <a href="#id2883788">Attributes in the sambaSamAccount objectclass (LDAP)</a></dt><dt>11.2. <a href="#id2884599">Basic smb.conf options for MySQL passdb backend</a></dt><dt>11.3. <a href="#id2884730">MySQL field names for MySQL passdb backend</a></dt><dt>13.1. <a href="#id2887226">Managing directories with unix and windows</a></dt><dt>13.2. <a href="#id2887628">User and Group Based Controls</a></dt><dt>13.3. <a href="#id2887984">File and Directory Permission Based Controls</a></dt><dt>13.4. <a href="#id2888364">Other Controls</a></dt><dt>19.1. <a href="#id2911136">PPD's shipped with CUPS</a></dt><dt>20.1. <a href="#id2922997">Extended Auditing Log Information</a></dt><dt>24.1. <a href="#id2930872">User Shell Folder registry keys default values</a></dt><dt>24.2. <a href="#id2931016">Defaults of profile settings registry keys</a></dt><dt>24.3. <a href="#id2931278">Defaults of default user profile paths registry keys</a></dt><dt>25.1. <a href="#id2933597">Options recognized by pam_smbpass</a></dt><dt>26.1. <a href="#id2934846">Unique NetBIOS names</a></dt><dt>26.2. <a href="#id2934916">Group Names</a></dt><dt>30.1. <a href="#id2937342">TDB File Descriptions</a></dt><dt>31.1. <a href="#id2938813">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2938959">Nature of the Conversion Choices</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>2.1. <a href="#id2866491">Simplest possible smb.conf file</a></dt><dt>5.1. <a href="#pdc-example">smb.conf for being a PDC</a></dt><dt>5.2. <a href="#id2870798">smb.conf for being a PDC</a></dt><dt>6.1. <a href="#id2872218">Minimal smb.conf for being a PDC</a></dt><dt>6.2. <a href="#id2872495">Minimal setup for being a BDC</a></dt><dt>8.1. <a href="#id2875707">smb.conf for Reference Documentation Server</a></dt><dt>8.2. <a href="#id2876026">smb.conf for anonymous printing</a></dt><dt>10.1. <a href="#id2877630">Domain master browser smb.conf</a></dt><dt>10.2. <a href="#id2877721">Local master browser smb.conf</a></dt><dt>10.3. <a href="#id2877859">smb.conf for not being a master browser</a></dt><dt>10.4. <a href="#id2877965">Local master browser smb.conf</a></dt><dt>10.5. <a href="#id2878082">smb.conf for not being a master browser</a></dt><dt>11.1. <a href="#idmapbackendexample"></a></dt><dt>11.2. <a href="#id2883349">Configuration with LDAP</a></dt><dt>12.1. <a href="#id2886226">smbgrpadd.sh</a></dt><dt>13.1. <a href="#id2887436">Example File</a></dt><dt>14.1. <a href="#id2892244">Share with some files oplocked</a></dt><dt>14.2. <a href="#id2892403"></a></dt><dt>17.1. <a href="#id2895128">smb.conf with DFS configured</a></dt><dt>18.1. <a href="#id2896217">Simple configuration with BSD printing</a></dt><dt>18.2. <a href="#extbsdpr">Extended configuration with BSD printing</a></dt><dt>18.3. <a href="#id2900085">[print\$] example</a></dt><dt>19.1. <a href="#id2906712">Simplest printing-related smb.conf</a></dt><dt>19.2. <a href="#id2906897">Overriding global CUPS settings for one printer</a></dt><dt>19.3. <a href="#id2913310">smb.conf for cupsaddsmb usage</a></dt><dt>20.1. <a href="#id2922709">smb.conf with VFS modules</a></dt><dt>20.2. <a href="#id2922809">smb.conf with multiple VFS modules</a></dt><dt>21.1. <a href="#id2924824">smb.conf for winbind set-up</a></dt><dt>33.1. <a href="#id2940544">smb.conf with [tmp] share</a></dt><dt>38.1. <a href="#id2946439">Minimal profile share</a></dt></dl></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2852328"></a>Legal Notice</h2></div></div><div></div></div><p> This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a> </p></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2852352"></a>Attributions</h2></div></div><div></div></div><p><a href="#IntroSMB" title="Chapter�1.�Introduction to Samba">Introduction to Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>David Lechnyr <<a href="mailto:david@lechnyr.com" target="_top">david@lechnyr.com</a>></p></li></ul></div><p><a href="#install" title="Chapter�2.�How to Install and Test SAMBA">How to Install and Test SAMBA</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Karl Auer</p></li></ul></div><p><a href="#FastStart" title="Chapter�3.�Fast Start for the Impatient">Fast Start for the Impatient</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#ServerType" title="Chapter�4.�Server Types and Security Modes">Server Types and Security Modes</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#samba-pdc" title="Chapter�5.�Domain Control">Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div><p><a href="#samba-bdc" title="Chapter�6.�Backup Domain Control">Backup Domain Control</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Volker Lendecke <<a href="mailto:Volker.Lendecke@SerNet.DE" target="_top">Volker.Lendecke@SerNet.DE</a>></p></li></ul></div><p><a href="#domain-member" title="Chapter�7.�Domain Membership">Domain Membership</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div><p><a href="#StandAloneServer" title="Chapter�8.�Stand-Alone Servers">Stand-Alone Servers</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#ClientConfig" title="Chapter�9.�MS Windows Network Configuration Guide">MS Windows Network Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Samba / MS Windows Network Browsing Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div><p><a href="#passdb" title="Chapter�11.�Account Information Databases">Account Information Databases</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Olivier (lem) Lemaire <<a href="mailto:olem@IDEALX.org" target="_top">olem@IDEALX.org</a>></p></li></ul></div><p><a href="#groupmapping" title="Chapter�12.�Mapping MS Windows and UNIX Groups">Mapping MS Windows and UNIX Groups</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jean Fran�ois Micouleau</p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#AccessControls" title="Chapter�13.�File, Directory and Share Access Controls">File, Directory and Share Access Controls</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>> (drawing) </p></li></ul></div><p><a href="#locking" title="Chapter�14.�File and Record Locking">File and Record Locking</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jeremy Allison <<a href="mailto:jra@samba.org" target="_top">jra@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Eric Roseme <<a href="mailto:eric.roseme@hp.com" target="_top">eric.roseme@hp.com</a>></p></li></ul></div><p><a href="#securing-samba" title="Chapter�15.�Securing Samba">Securing Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#InterdomainTrusts" title="Chapter�16.�Interdomain Trust Relationships">Interdomain Trust Relationships</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Rafal Szczesniak <<a href="mailto:mimir@samba.org" target="_top">mimir@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>> (drawing) </p></li><li><p>Stephen Langasek <<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>></p></li></ul></div><p><a href="#msdfs" title="Chapter�17.�Hosting a Microsoft Distributed File System tree on Samba">Hosting a Microsoft Distributed File System tree on Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Shirish Kalele <<a href="mailto:samba@samba.org" target="_top">samba@samba.org</a>></p></li></ul></div><p><a href="#printing" title="Chapter�18.�Classical Printing Support">Classical Printing Support</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li></ul></div><p><a href="#CUPS-printing" title="Chapter�19.�CUPS Printing Support in Samba 3.0">CUPS Printing Support in Samba 3.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Kurt Pfeifle <<a href="mailto:kpfeifle@danka.de" target="_top">kpfeifle@danka.de</a>></p></li><li><p>Ciprian Vizitiu <<a href="mailto:CVizitiu@gbif.org" target="_top">CVizitiu@gbif.org</a>> (drawings) </p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>> (drawings) </p></li></ul></div><p><a href="#VFS" title="Chapter�20.�Stackable VFS modules">Stackable VFS modules</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Tim Potter</p></li><li><p>Simo Sorce (original vfs_skel README) </p></li><li><p>Alexander Bokovoy (original vfs_netatalk docs) </p></li><li><p>Stefan Metzmacher (Update for multiple modules) </p></li></ul></div><p><a href="#AdvancedNetworkManagement" title="Chapter�22.�Advanced Network Management">Advanced Network Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#PolicyMgmt" title="Chapter�23.�System and Account Policies">System and Account Policies</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#ProfileMgmt" title="Chapter�24.�Desktop Profile Management">Desktop Profile Management</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#pam" title="Chapter�25.�PAM based Distributed Authentication">PAM based Distributed Authentication</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Stephen Langasek <<a href="mailto:vorlon@netexpress.net" target="_top">vorlon@netexpress.net</a>></p></li></ul></div><p><a href="#integrate-ms-networks" title="Chapter�26.�Integrating MS Windows networks with Samba">Integrating MS Windows networks with Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#unicode" title="Chapter�27.�Unicode/Charsets">Unicode/Charsets</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>TAKAHASHI Motonobu <<a href="mailto:monyo@home.monyo.com" target="_top">monyo@home.monyo.com</a>></p></li></ul></div><p><a href="#Backup" title="Chapter�28.�Samba Backup Techniques">Samba Backup Techniques</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#SambaHA" title="Chapter�29.�High Availability Options">High Availability Options</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#upgrading-to-3.0" title="Chapter�30.�Upgrading from Samba-2.x to Samba-3.0.0">Upgrading from Samba-2.x to Samba-3.0.0</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li></ul></div><p><a href="#NT4Migration" title="Chapter�31.�Migration from NT4 PDC to Samba-3 PDC">Migration from NT4 PDC to Samba-3 PDC</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#SWAT" title="Chapter�32.�SWAT - The Samba Web Administration Tool">SWAT - The Samba Web Administration Tool</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#diagnosis" title="Chapter�33.�The Samba checklist">The Samba checklist</a></p><div class="itemizedlist"><ul type="disc"><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div><p><a href="#problems" title="Chapter�34.�Analysing and solving samba problems">Analysing and solving samba problems</a></p><div class="itemizedlist"><ul type="disc"><li><p>Gerald (Jerry) Carter <<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>David Bannon <<a href="mailto:dbannon@samba.org" target="_top">dbannon@samba.org</a>></p></li></ul></div><p><a href="#bugreport" title="Chapter�35.�Reporting Bugs">Reporting Bugs</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li></ul></div><p><a href="#compiling" title="Chapter�36.�How to compile Samba">How to compile Samba</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Andrew Tridgell <<a href="mailto:tridge@samba.org" target="_top">tridge@samba.org</a>></p></li></ul></div><p><a href="#Portability" title="Chapter�37.�Portability">Portability</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div><p><a href="#Other-Clients" title="Chapter�38.�Samba and other CIFS clients">Samba and other CIFS clients</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>Jim McDonough <<a href="mailto:jmcd@us.ibm.com" target="_top">jmcd@us.ibm.com</a>> (OS/2) </p></li></ul></div><p><a href="#speed" title="Chapter�39.�Samba Performance Tuning">Samba Performance Tuning</a></p><div class="itemizedlist"><ul type="disc"><li><p>Paul Cochrane <<a href="mailto:paulc@dth.scot.nhs.uk" target="_top">paulc@dth.scot.nhs.uk</a>></p></li><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#DNSDHCP" title="Chapter�40.�DNS and DHCP Configuration Guide">DNS and DHCP Configuration Guide</a></p><div class="itemizedlist"><ul type="disc"><li><p>John H. Terpstra <<a href="mailto:jht@samba.org" target="_top">jht@samba.org</a>></p></li></ul></div><p><a href="#Further-Resources" title="Chapter�41.�Further Resources">Further Resources</a></p><div class="itemizedlist"><ul type="disc"><li><p>Jelmer R. Vernooij <<a href="mailto:jelmer@samba.org" target="_top">jelmer@samba.org</a>></p></li></ul></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2800298"></a>Preparing Samba for Configuration</h1></div></div><div></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba and how to configure the parts of samba you will most likely need. PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2800382">Background</a></dt><dt><a href="#id2800440">Terminology</a></dt><dt><a href="#id2800631">Related Projects</a></dt><dt><a href="#id2800699">SMB Methodology</a></dt><dt><a href="#id2800808">Epilogue</a></dt><dt><a href="#id2800892">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2866386">Obtaining and installing samba</a></dt><dt><a href="#id2866430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2866468">Example Configuration</a></dt><dt><a href="#id2866661">SWAT</a></dt></dl></dd><dt><a href="#id2866706">Try listing the shares available on your server</a></dt><dt><a href="#id2866764">Try connecting with the unix client</a></dt><dt><a href="#id2866881">Try connecting from another SMB client</a></dt><dt><a href="#id2866964">What If Things Don't Work?</a></dt><dt><a href="#id2866997">Common Errors</a></dt><dd><dl><dt><a href="#id2867010">Large number of smbd processes</a></dt><dt><a href="#id2867109">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2867129">"The network name cannot be found"</a></dt></dl></dd></dl></dd><dt>3. <a href="#FastStart">Fast Start for the Impatient</a></dt><dd><dl><dt><a href="#id2867256">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="IntroSMB"></a>Chapter�1.�Introduction to Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Lechnyr</span></h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt class="email"><<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>></tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2800382">Background</a></dt><dt><a href="#id2800440">Terminology</a></dt><dt><a href="#id2800631">Related Projects</a></dt><dt><a href="#id2800699">SMB Methodology</a></dt><dt><a href="#id2800808">Epilogue</a></dt><dt><a href="#id2800892">Miscellaneous</a></dt></dl></div><p>“<span class="quote"> "If you understand what you're doing, you're not learning anything." -- Anonymous </span>”</p><p> 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><div><h2 class="title" style="clear: both"><a name="id2800382"></a>Background</h2></div></div><div></div></div><p> Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only 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><div><h2 class="title" style="clear: both"><a name="id2800440"></a>Terminology</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p> SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. </p></li><li><p> CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently 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 <a href="http://www.samba.org/" target="_top">http://www.samba.org</a>). </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800631"></a>Related Projects</h2></div></div><div></div></div><p> There are currently two network filesystem client projects for Linux that are directly related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself. </p><div class="itemizedlist"><ul type="disc"><li><p> 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 (hierarchical name space), secure per-user session establishment, safe distributed caching (oplock), optional packet signing, Unicode and other internationalization improvements, and optional Winbind (nsswitch) integration. </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 <a href="http://jcifs.samba.org/" target="_top">jCIFS project</a> which provides an SMB client toolkit written in Java. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800699"></a>SMB Methodology</h2></div></div><div></div></div><p> Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good 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 <a href="http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html" target="_top">SecurityFriday's SWB program</a>. It allows you to walk through the establishment of a SMB/CIFS session step by step. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800808"></a>Epilogue</h2></div></div><div></div></div><p>“<span class="quote"> What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft 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. </span>”</p><p>“<span class="quote"> 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. </span>”</p><p>“<span class="quote"> 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. </span>”</p><p>“<span class="quote"> That's what's really irritating to me." </span>”</p><p>-- <a href="http://hr.uoregon.edu/davidrl/boot.txt" target="_top">Linus Torvalds, from an interview with BOOT Magazine, Sept 1998</a> </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2800892"></a>Miscellaneous</h2></div></div><div></div></div><p> This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="install"></a>Chapter�2.�How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Karl</span> <span class="surname">Auer</span></h3></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866386">Obtaining and installing samba</a></dt><dt><a href="#id2866430">Configuring samba (smb.conf)</a></dt><dd><dl><dt><a href="#id2866468">Example Configuration</a></dt><dt><a href="#id2866661">SWAT</a></dt></dl></dd><dt><a href="#id2866706">Try listing the shares available on your server</a></dt><dt><a href="#id2866764">Try connecting with the unix client</a></dt><dt><a href="#id2866881">Try connecting from another SMB client</a></dt><dt><a href="#id2866964">What If Things Don't Work?</a></dt><dt><a href="#id2866997">Common Errors</a></dt><dd><dl><dt><a href="#id2867010">Large number of smbd processes</a></dt><dt><a href="#id2867109">"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</a></dt><dt><a href="#id2867129">"The network name cannot be found"</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866386"></a>Obtaining and installing samba</h2></div></div><div></div></div><p> Binary packages of samba are included in almost any Linux or UNIX distribution. There are also some packages available at <a href="http://samba.org/" target="_top">the samba homepage</a>. </p><p>If you need to compile samba from source, check <a href="#compiling" title="Chapter�36.�How to compile Samba">the chapter about compiling samba from scratch</a>.</p><p>If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow for information about updating samba.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866430"></a>Configuring samba (smb.conf)</h2></div></div><div></div></div><p> Samba's configuration is stored in the <tt class="filename">smb.conf</tt> file, that usually resides in <tt class="filename">/etc/samba/smb.conf</tt> or <tt class="filename">/usr/local/samba/lib/smb.conf</tt>. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the web-based interface swat, that is included with samba. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866468"></a>Example Configuration</h3></div></div><div></div></div><p> There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options. </p><p> The simplest useful configuration file would be something like this: </p><p> </p><div class="example"><a name="id2866491"></a><p class="title"><b>Example�2.1.�Simplest possible smb.conf file</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[homes]</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr></table></div><p> </p><p> This will allow connections by anyone with an account on the server, using either their login name or <i class="parameter"><tt>homes</tt></i>" as the service name. (Note that the workgroup that Samba must also be set.) </p><p> Make sure you put the <tt class="filename">smb.conf</tt> file in the correct place (usually in <tt class="filename">/etc/samba</tt>). </p><p> For more information about security settings for the <i class="parameter"><tt>[homes]</tt></i> share please refer to <a href="#securing-samba" title="Chapter�15.�Securing Samba">"Securing Samba"</a>. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2866608"></a>Test your config file with <b class="command">testparm</b></h4></div></div><div></div></div><p> It's important that you test the validity of your <tt class="filename">smb.conf</tt> file using the <span class="application">testparm</span> program. If testparm runs OK then it will list the loaded services. If not it will give an error message. </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 class="filename">smb.conf</tt>! </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2866661"></a>SWAT</h3></div></div><div></div></div><p> SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage on compiling, installing and configuring swat from source. </p><p> To launch SWAT just run your favorite web browser and point it at <a href="http://localhost:901/" target="_top">http://localhost:901/</a>. Replace <i class="replaceable"><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><div><h2 class="title" style="clear: both"><a name="id2866706"></a>Try listing the shares available on your server</h2></div></div><div></div></div><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient -L <i class="replaceable"><tt>yourhostname</tt></i></tt></b> </pre><p>You should get back a list of shares available on 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 class="command">smbclient</b> man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866764"></a>Try connecting with the unix client</h2></div></div><div></div></div><p> </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient <i class="replaceable"><tt> //yourhostname/aservice</tt></i></tt></b> </pre><p>Typically the <i class="replaceable"><tt>yourhostname</tt></i> would be the name of the host where you installed <span class="application">smbd</span>. The <i class="replaceable"><tt>aservice</tt></i> is any service you have defined in the <tt class="filename">smb.conf</tt> file. Try your user name if you just have a <i class="parameter"><tt>[homes]</tt></i> section in <tt class="filename">smb.conf</tt>.</p><p>For example if your unix host is <i class="replaceable"><tt>bambi</tt></i> and your login name is <i class="replaceable"><tt>fred</tt></i> you would type:</p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>smbclient //<i class="replaceable"><tt>bambi</tt></i>/<i class="replaceable"><tt>fred</tt></i></tt></b> </pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866881"></a>Try connecting from another SMB client</h2></div></div><div></div></div><p>Try mounting disks. from a DOS, Windows or OS/2 client, eg:</p><pre class="screen"> <tt class="prompt">C:\> </tt><b class="userinput"><tt>net use d: \\servername\service</tt></b> </pre><p>Try printing. eg:</p><p> </p><pre class="screen"> <tt class="prompt">C:\> </tt><b class="userinput"><tt>net use lpt1: \\servername\spoolservice</tt></b> </pre><p> </p><pre class="screen"><tt class="prompt">C:\> </tt><b class="userinput"><tt>print filename</tt></b> </pre></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866964"></a>What If Things Don't Work?</h2></div></div><div></div></div><p>Then you might read the file chapter <a href="#diagnosis" title="Chapter�33.�The Samba checklist">diagnosis</a> and the FAQ. If you are still stuck then refer to <a href="#problems" title="Chapter�34.�Analysing and solving samba problems">"Analysing and solving problems"</a>. Samba has been successfully installed at thousands of sites worldwide, so maybe someone else has hit your problem and has overcome it.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2866997"></a>Common Errors</h2></div></div><div></div></div><p> The following questions and issues get raised on the samba mailing list over and over again. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867010"></a>Large number of smbd processes</h3></div></div><div></div></div><p> Samba consists on three core programs: <span class="application">nmbd</span>, <span class="application">smbd</span>, <span class="application">winbindd</span>. <span class="application">nmbd</span> is the name server message daemon, <span class="application">smbd</span> is the server message daemon, <span class="application">winbindd</span> is the daemon that handles communication with Domain Controllers. </p><p> If your system is NOT running as a WINS server, then there will be one (1) single instance of <span class="application">nmbd</span> running on your system. If it is running as a WINS server then there will be two (2) instances - one to handle the WINS requests. </p><p> <span class="application">smbd</span> handles ALL connection requests and then spawns a new process for each client connection made. That is why you are seeing so many of them, one (1) per client connection. </p><p> <span class="application">winbindd</span> will run as one or two daemons, depending on whether or not it is being run in "split mode" (in which case there will be two instances). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867109"></a>"open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"</h3></div></div><div></div></div><p>Your loopback device isn't working correctly. Make sure it's configured properly. The loopback device is an internal (virtual) network device with the ip address 127.0.0.1. Read your OS documentation for details on how to configure the loopback on your system.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867129"></a>"<span class="errorname">The network name cannot be found</span>"</h3></div></div><div></div></div><p> This error can be caused by one of these misconfigurations: </p><div class="itemizedlist"><ul type="disc"><li><p>You specified an nonexisting <a class="indexterm" name="id2867155"></a><i class="parameter"><tt>path</tt></i> for the share in <tt class="filename">smb.conf</tt> </p></li><li><p>The user you are trying to access the share with does not have sufficient permissions to access the <a class="indexterm" name="id2867184"></a><i class="parameter"><tt>path</tt></i> for the share. Both read (r) and access (x) should be possible.</p></li><li><p>The share you are trying to access does not exist.</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="FastStart"></a>Chapter�3.�Fast Start for the Impatient</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867256">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867256"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. </p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2867283"></a>First Steps in Server Configuration</h1></div></div><div></div></div><p> Samba can operate in various modes within SMB networks. This HOWTO section contains information on configuring samba to function as the type of server your network requires. Please read this section carefully. </p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>4. <a href="#ServerType">Server Types and Security Modes</a></dt><dd><dl><dt><a href="#id2867445">Features and Benefits</a></dt><dt><a href="#id2867540">Server Types</a></dt><dt><a href="#id2867626">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867745">User Level Security</a></dt><dt><a href="#id2867883">Share Level Security</a></dt><dt><a href="#id2868020">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2868278">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2868379">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868660">Password checking</a></dt><dt><a href="#id2868855">Common Errors</a></dt><dd><dl><dt><a href="#id2868882">What makes Samba a SERVER?</a></dt><dt><a href="#id2868923">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868959">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868998">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">Domain Control</a></dt><dd><dl><dt><a href="#id2869330">Features and Benefits</a></dt><dt><a href="#id2869545">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869560">Domain Controller Types</a></dt><dt><a href="#id2869805">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2870187">Domain Control - Example Configuration</a></dt><dt><a href="#id2870675">Samba ADS Domain Control</a></dt><dt><a href="#id2870727">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870742">Domain Network Logon Service</a></dt><dt><a href="#id2871174">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2871320">Common Errors</a></dt><dd><dl><dt><a href="#id2871328">'$' cannot be included in machine name</a></dt><dt><a href="#id2871386">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2871445">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871529">The machine trust account not accessible</a></dt><dt><a href="#id2871602">Account disabled</a></dt><dt><a href="#id2871634">Domain Controller Unavailable</a></dt><dt><a href="#id2871658">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">Backup Domain Control</a></dt><dd><dl><dt><a href="#id2871817">Features And Benefits</a></dt><dt><a href="#id2872006">Essential Background Information</a></dt><dd><dl><dt><a href="#id2872035">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2872286">Active Directory Domain Control</a></dt><dt><a href="#id2872307">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2872332">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2872346">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2872480">Example Configuration</a></dt></dl></dd><dt><a href="#id2872638">Common Errors</a></dt><dd><dl><dt><a href="#id2872650">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872682">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872708">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872753">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#domain-member">Domain Membership</a></dt><dd><dl><dt><a href="#id2872960">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2873290">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873596">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873811">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873884">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2874094">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2874530">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874715">Setup your smb.conf</a></dt><dt><a href="#id2874844">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2875221">Notes</a></dt></dl></dd><dt><a href="#id2875243">Common Errors</a></dt><dd><dl><dt><a href="#id2875286">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2875318">Adding Machine to Domain Fails</a></dt><dt><a href="#id2875462">I can't join a Windows 2003 PDC</a></dt></dl></dd></dl></dd><dt>8. <a href="#StandAloneServer">Stand-Alone Servers</a></dt><dd><dl><dt><a href="#id2875549">Features and Benefits</a></dt><dt><a href="#id2875587">Background</a></dt><dt><a href="#id2875661">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2876184">Common Errors</a></dt></dl></dd><dt>9. <a href="#ClientConfig">MS Windows Network Configuration Guide</a></dt><dd><dl><dt><a href="#id2876248">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ServerType"></a>Chapter�4.�Server Types and Security Modes</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2867445">Features and Benefits</a></dt><dt><a href="#id2867540">Server Types</a></dt><dt><a href="#id2867626">Samba Security Modes</a></dt><dd><dl><dt><a href="#id2867745">User Level Security</a></dt><dt><a href="#id2867883">Share Level Security</a></dt><dt><a href="#id2868020">Domain Security Mode (User Level Security)</a></dt><dt><a href="#id2868278">ADS Security Mode (User Level Security)</a></dt><dt><a href="#id2868379">Server Security (User Level Security)</a></dt></dl></dd><dt><a href="#id2868660">Password checking</a></dt><dt><a href="#id2868855">Common Errors</a></dt><dd><dl><dt><a href="#id2868882">What makes Samba a SERVER?</a></dt><dt><a href="#id2868923">What makes Samba a Domain Controller?</a></dt><dt><a href="#id2868959">What makes Samba a Domain Member?</a></dt><dt><a href="#id2868998">Constantly Losing Connections to Password Server</a></dt></dl></dd></dl></div><p> This chapter provides information regarding the types of server that Samba may be configured to be. A Microsoft network administrator who wishes to migrate to or to use Samba will want to know what, within a Samba context, terms familiar to MS Windows administrator mean. This means that it is essential also to define how critical security modes function BEFORE we get into the details of how to configure the server itself. </p><p> The chapter provides an overview of the security modes of which Samba is capable and how these relate to MS Windows servers and clients. </p><p> A question often asked is, "Why would I want to use Samba?" Most chapters contain a section that highlights features and benefits. We hope that the information provided will help to answer this question. Be warned though, we want to be fair and reasonable, so not all features are positive towards Samba so the benefit may be on the side of our competition. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867445"></a>Features and Benefits</h2></div></div><div></div></div><p> Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion and fury fitting his anguish. The other looked at the stone and said, that is a garnet - I can turn that into a precious gem and some day it will make a princess very happy! </p><p> The moral of this tale: Two men, two very different perspectives regarding the same stone. Like it or not, Samba is like that stone. Treat it the right way and it can bring great pleasure, but if you are forced upon it and have no time for its secrets then it can be a source of discomfort. </p><p> Samba started out as a project that sought to provide interoperability for MS Windows 3.x clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides features and functionality fit for large scale deployment. It also has some warts. In sections like this one we will tell of both. </p><p> So now, what are the benefits of features mentioned in this chapter? </p><div class="itemizedlist"><ul type="disc"><li><p> Samba-3 can replace an MS Windows NT4 Domain Controller </p></li><li><p> Samba-3 offers excellent interoperability with MS Windows NT4 style domains as well as natively with Microsoft Active Directory domains. </p></li><li><p> Samba-3 permits full NT4 style Interdomain Trusts </p></li><li><p> Samba has security modes that permit more flexible authentication than is possible with MS Windows NT4 Domain Controllers. </p></li><li><p> Samba-3 permits use of multiple account database backends </p></li><li><p> The account (password) database backends can be distributed and replicated using multiple methods. This gives Samba-3 greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867540"></a>Server Types</h2></div></div><div></div></div><p>Administrators of Microsoft networks often refer to three different type of servers:</p><div class="itemizedlist"><ul type="disc"><li><p>Domain Controller</p><div class="itemizedlist"><ul type="circle"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div></li><li><p>Domain Member Server</p><div class="itemizedlist"><ul type="circle"><li><p>Active Directory Domain Server</p></li><li><p>NT4 Style Domain Domain Server</p></li></ul></div></li><li><p>Stand Alone Server</p></li></ul></div><p> The chapters covering Domain Control, Backup Domain Control and Domain Membership provide pertinent information regarding Samba configuration for each of these server roles. The reader is strongly encouraged to become intimately familiar with the information presented. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2867626"></a>Samba Security Modes</h2></div></div><div></div></div><p> In this section the function and purpose of Samba's <a class="indexterm" name="id2867637"></a><i class="parameter"><tt>security</tt></i> modes are described. An accurate understanding of how Samba implements each security mode as well as how to configure MS Windows clients for each mode will significantly reduce user complaints and administrator heartache. </p><p> In the SMB/CIFS networking world, there are only two types of security: <span class="emphasis"><em>USER Level</em></span> and <span class="emphasis"><em>SHARE Level</em></span>. We refer to these collectively as <span class="emphasis"><em>security levels</em></span>. In implementing these two <span class="emphasis"><em>security levels</em></span> Samba provides flexibilities that are not available with Microsoft Windows NT4 / 200x servers. Samba knows of five (5) ways that allow the security levels to be implemented. In actual fact, Samba implements <span class="emphasis"><em>SHARE Level</em></span> security only one way, but has four ways of implementing <span class="emphasis"><em>USER Level</em></span> security. Collectively, we call the Samba implementations <span class="emphasis"><em>Security Modes</em></span>. These are: <span class="emphasis"><em>SHARE</em></span>, <span class="emphasis"><em>USER</em></span>, <span class="emphasis"><em>DOMAIN</em></span>, <span class="emphasis"><em>ADS</em></span>, and <span class="emphasis"><em>SERVER</em></span> modes. They are documented in this chapter. </p><p> A SMB server tells the client at startup what <span class="emphasis"><em>security level</em></span> it is running. There are two options: <span class="emphasis"><em>share level</em></span> and <span class="emphasis"><em>user level</em></span>. 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. This may sound 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><div><h3 class="title"><a name="id2867745"></a>User Level Security</h3></div></div><div></div></div><p> We will describe <span class="emphasis"><em>user level</em></span> security first, as it's simpler. In <span class="emphasis"><em>user level</em></span> security, the client will send a <span class="emphasis"><em>session setup</em></span> command directly after the protocol negotiation. 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 <span class="emphasis"><em>accept/reject</em></span> on anything other than: </p><div class="orderedlist"><ol type="1"><li><p>The username/password</p></li><li><p>The name of the client machine</p></li></ol></div><p> If the server accepts the username/password then the client expects to be able to mount shares (using a <span class="emphasis"><em>tree connection</em></span>) without specifying a password. It expects that all access rights will be as the username/password specified in the <span class="emphasis"><em>session setup</em></span>. </p><p> It is also possible for a client to send multiple <span class="emphasis"><em>session setup</em></span> requests. When the server responds, it gives the client a <span class="emphasis"><em>uid</em></span> to use as an authentication tag for that username/password. The client can maintain multiple authentication contexts in this way (WinDD is an example of an application that does this). </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867837"></a>Example Configuration</h4></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>User Level Security</em></span> is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr></table><p> This is the default setting since samba-2.2.x. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2867883"></a>Share Level Security</h3></div></div><div></div></div><p> Ok, now for share level security. In share level security, the client authenticates itself separately for each share. It will send a password along with each <span class="emphasis"><em>tree connection</em></span> (share mount). It does not explicitly send a username with this operation. The client expects 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 pair that is authenticated, not a share/password pair. </p><p> To gain understanding of the MS Windows networking parallels to this, one should think in terms of MS Windows 9x/Me where one can create a shared folder that provides read-only or full access, with or without a password. </p><p> Many clients send a <span class="emphasis"><em>session setup</em></span> 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 <span class="emphasis"><em>possible usernames</em></span>. When the client then does a <span class="emphasis"><em>tree connection</em></span> it also adds to this list the name of the share they try to connect to (useful for home directories) and any users listed in the <a class="indexterm" name="id2867942"></a><i class="parameter"><tt>user</tt></i> <tt class="filename">smb.conf</tt> line. The password is then checked in turn against these <span class="emphasis"><em>possible usernames</em></span>. If a match is found then the client is authenticated as that user. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2867971"></a>Example Configuration</h4></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter that sets <span class="emphasis"><em>Share Level Security</em></span> is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = share</tt></i></td></tr></table><p> Please note that there are reports that recent MS Windows clients do not like to work with share mode security servers. You are strongly discouraged from using share level security. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868020"></a>Domain Security Mode (User Level Security)</h3></div></div><div></div></div><p> When Samba is operating in <a class="indexterm" name="id2868031"></a><i class="parameter"><tt>security</tt></i> = domain mode, the Samba server has a domain security trust account (a machine account) and will cause all authentication requests to be passed through to the domain controllers. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868051"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> Samba as a Domain Member Server </em></span></p><p> This method involves addition of the following parameters in the <tt class="filename">smb.conf</tt> file: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = domain</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr></table><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="procedure"><ol type="1"><li><p>On the MS Windows NT domain controller, using the Server Manager, add a machine account for the Samba server. </p></li><li><p>Next, on the UNIX/Linux system execute:</p><pre class="screen"><tt class="prompt">root# </tt><b class="userinput"><tt>net rpc join -U administrator%password</tt></b></pre></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Samba-2.2.4 and later can auto-join a Windows NT4 style Domain just by executing: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -j <i class="replaceable"><tt>DOMAIN_NAME</tt></i> -r <i class="replaceable"><tt>PDC_NAME</tt></i> \ -U Administrator%<i class="replaceable"><tt>password</tt></i></tt></b> </pre><p> Samba-3 can do the same by executing: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net rpc join -U Administrator%<i class="replaceable"><tt>password</tt></i></tt></b> </pre><p> It is not necessary with Samba-3 to specify the <i class="replaceable"><tt>DOMAIN_NAME</tt></i> or the <i class="replaceable"><tt>PDC_NAME</tt></i> as it figures this out from the <tt class="filename">smb.conf</tt> file settings. </p></div><p> Use of this mode of authentication does require there to be a standard UNIX account for each user in order to assign a UID once the account has been authenticated by the remote Windows DC. This account can be blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in the <tt class="filename">/etc/passwd</tt> entry. </p><p> An alternative to assigning UIDs to Windows users on a Samba member server is presented in <a href="#winbind" title="Chapter�21.�Winbind: Use of Domain Accounts">the chapter about winbind</a>. </p><p> For more information of being a domain member, see <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter about domain membership</a>. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868278"></a>ADS Security Mode (User Level Security)</h3></div></div><div></div></div><p> Both Samba 2.2 and 3.0 can join an Active Directory domain. This is possible if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style domain members. This is contrary to popular belief. The only thing that Active Directory in native mode prohibits is Backup Domain Controllers running NT4. </p><p> If you are using Active Directory, starting with Samba-3 you can join as a native AD member. Why would you want to do that? Your security policy might prohibit the use of NT-compatible authentication protocols. All your machines are running Windows 2000 and above and all use Kerberos. In this case Samba as a NT4-style domain would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos tickets. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868307"></a>Example Configuration</h4></div></div><div></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>realm = your.kerberos.REALM</tt></i></td></tr><tr><td><i class="parameter"><tt>security = ADS</tt></i></td></tr></table><p> The following parameter may be required: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>ads server = your.kerberos.server</tt></i></td></tr></table><p> Please refer to <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter on domain membership</a> for more information regarding this configuration option. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868379"></a>Server Security (User Level Security)</h3></div></div><div></div></div><p> Server security mode is a left over from the time when Samba was not capable of acting as a domain member server. It is highly recommended NOT to use this feature. Server security mode has many draw backs. The draw backs include: </p><div class="itemizedlist"><ul type="disc"><li><p>Potential Account Lockout on MS Windows NT4/200x password servers</p></li><li><p>Lack of assurance that the password server is the one specified</p></li><li><p>Does not work with Winbind, particularly needed when storing profiles remotely</p></li><li><p>This mode may open connections to the password server, and keep them open for extended periods.</p></li><li><p>Security on the Samba server breaks badly when the remote password server suddenly shuts down</p></li><li><p>With this mode there is NO security account in the domain that the password server belongs to for the Samba server.</p></li></ul></div><p> In server security mode the Samba server reports to the client that it is in user level security. The client then does a <span class="emphasis"><em>session setup</em></span> as described earlier. The Samba server takes the username/password that the client sends and attempts to login to the <a class="indexterm" name="id2868451"></a><i class="parameter"><tt>password server</tt></i> by sending exactly the same username/password that it got from the client. If that server is in user level security and accepts the password, then Samba accepts the clients connection. This allows the Samba server to use another SMB server as the <a class="indexterm" name="id2868471"></a><i class="parameter"><tt>password server</tt></i>. </p><p> You should also note that at the very start of all this, where the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does then it supplies the client with a random cryptkey. The client will then send all passwords in encrypted form. Samba supports this type of encryption by default. </p><p> The parameter <a class="indexterm" name="id2868500"></a><i class="parameter"><tt>security</tt></i> = server means that Samba reports to clients that it is running in <span class="emphasis"><em>user mode</em></span> but actually passes off all authentication requests to another <span class="emphasis"><em>user mode</em></span> server. This requires an additional parameter <a class="indexterm" name="id2868525"></a><i class="parameter"><tt>password server</tt></i> that points to the real authentication server. That real authentication server can be another Samba server or can be a Windows NT server, the later natively capable of encrypted password support. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> When Samba is running in <span class="emphasis"><em>server security mode</em></span> it is essential that the parameter <span class="emphasis"><em>password server</em></span> is set to the precise NetBIOS machine name of the target authentication server. Samba can NOT determine this from NetBIOS name lookups because the choice of the target authentication server is arbitrary and can not be determined from a domain name. In essence, a Samba server that is in <span class="emphasis"><em>server security mode</em></span> is operating in what used to be known as workgroup mode. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2868569"></a>Example Configuration</h4></div></div><div></div></div><p><span class="emphasis"><em> Using MS Windows NT as an authentication server </em></span></p><p> This method involves the additions of the following parameters in the <tt class="filename">smb.conf</tt> file: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>encrypt passwords = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>security = server</tt></i></td></tr><tr><td><i class="parameter"><tt>password server = "NetBIOS_name_of_a_DC"</tt></i></td></tr></table><p> There are two ways of identifying whether or not a username and password pair was valid. 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, though this account can be blocked to prevent logons by non-SMB/CIFS clients. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868660"></a>Password checking</h2></div></div><div></div></div><p> MS Windows clients may use encrypted passwords as part of a challenge/response authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear text strings for simple password based authentication. It should be realized that with the SMB protocol, 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 truncated to 14 bytes. This string is then appended with 5 bytes of NULL characters and split to form two 56 bit DES keys to encrypt a "magic" 8 byte value. The resulting 16 bytes form the LanMan hash. </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 clients upper casing usernames and password before transmitting them to the SMB server when using clear text authentication. </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password level = integer</tt></i></td></tr><tr><td><i class="parameter"><tt>username level = integer</tt></i></td></tr></table><p> By default Samba will lower case the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally only contain lower-case character, the <a class="indexterm" name="id2868781"></a><i class="parameter"><tt>username level</tt></i> parameter is rarely needed. </p><p> However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a user on a Windows 9x client to connect to a Samba server using clear text authentication, the <a class="indexterm" name="id2868805"></a><i class="parameter"><tt>password level</tt></i> must be set to the maximum number of upper case letters which <span class="emphasis"><em>could</em></span> appear in a password. Note that if the server OS uses the traditional DES version of crypt(), a <a class="indexterm" name="id2868826"></a><i class="parameter"><tt>password level</tt></i> of 8 will result in case insensitive passwords as seen from Windows users. This will also result in longer login times as Samba has to compute the permutations of the password string and try them one by one until a match is located (or all combinations fail). </p><p> The best option to adopt is to enable support for encrypted passwords wherever Samba is used. Most attempts to apply the registry change to re-enable plain text passwords will eventually lead to user complaints and unhappiness. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2868855"></a>Common Errors</h2></div></div><div></div></div><p> We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake made in a developmental test lab is expected. </p><p> Here we look at common mistakes and misapprehensions that have been the subject of discussions on the Samba mailing lists. Many of these are avoidable by doing you homework before attempting a Samba implementation. Some are the result of misunderstanding of the English language. The English language has many turns of phrase that are potentially vague and may be highly confusing to those for whom English is not their native tongue. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868882"></a>What makes Samba a SERVER?</h3></div></div><div></div></div><p> To some the nature of the Samba <span class="emphasis"><em>security</em></span> mode is very obvious, but entirely wrong all the same. It is assumed that <a class="indexterm" name="id2868899"></a><i class="parameter"><tt>security</tt></i> = server means that Samba will act as a server. Not so! See above - this setting means that Samba will <span class="emphasis"><em>try</em></span> to use another SMB server as its source of user authentication alone. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868923"></a>What makes Samba a Domain Controller?</h3></div></div><div></div></div><p> The <tt class="filename">smb.conf</tt> parameter <a class="indexterm" name="id2868941"></a><i class="parameter"><tt>security</tt></i> = domain does NOT really make Samba behave as a Domain Controller! This setting means we want Samba to be a domain member! </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868959"></a>What makes Samba a Domain Member?</h3></div></div><div></div></div><p> Guess! So many others do. But whatever you do, do NOT think that <a class="indexterm" name="id2868971"></a><i class="parameter"><tt>security</tt></i> = user makes Samba act as a domain member. Read the manufacturers manual before the warranty expires! See <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter about domain membership</a> for more information. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2868998"></a>Constantly Losing Connections to Password Server</h3></div></div><div></div></div><p> “<span class="quote"> Why does server_validate() simply give up rather than re-establishing its connection to the password server? Though I am not fluent in the SMB protocol, perhaps the cluster server process passes along to its client workstation the session key it receives from the password server, which means the password hashes submitted by the client would not work on a subsequent connection, whose session key would be different. So server_validate() must give up.</span>” </p><p> Indeed. That's why <a class="indexterm" name="id2869025"></a><i class="parameter"><tt>security</tt></i> = server is at best a nasty hack. Please use <a class="indexterm" name="id2869041"></a><i class="parameter"><tt>security</tt></i> = domain. <a class="indexterm" name="id2869054"></a><i class="parameter"><tt>security</tt></i> = server mode is also known as pass-through authentication. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter�5.�Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869330">Features and Benefits</a></dt><dt><a href="#id2869545">Basics of Domain Control</a></dt><dd><dl><dt><a href="#id2869560">Domain Controller Types</a></dt><dt><a href="#id2869805">Preparing for Domain Control</a></dt></dl></dd><dt><a href="#id2870187">Domain Control - Example Configuration</a></dt><dt><a href="#id2870675">Samba ADS Domain Control</a></dt><dt><a href="#id2870727">Domain and Network Logon Configuration</a></dt><dd><dl><dt><a href="#id2870742">Domain Network Logon Service</a></dt><dt><a href="#id2871174">Security Mode and Master Browsers</a></dt></dl></dd><dt><a href="#id2871320">Common Errors</a></dt><dd><dl><dt><a href="#id2871328">'$' cannot be included in machine name</a></dt><dt><a href="#id2871386">Joining domain fails because of existing machine account</a></dt><dt><a href="#id2871445">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2871529">The machine trust account not accessible</a></dt><dt><a href="#id2871602">Account disabled</a></dt><dt><a href="#id2871634">Domain Controller Unavailable</a></dt><dt><a href="#id2871658">Can not log onto domain member workstation after joining domain</a></dt></dl></dd></dl></div><p><b><span class="emphasis"><em>The Essence of Learning:</em></span>�</b> There are many who approach MS Windows networking with incredible misconceptions. That's OK, because it gives the rest of us plenty of opportunity to be of assistance. Those who really want help would be well advised to become familiar with information that is already available. </p><p> The reader is advised NOT to tackle this section without having first understood and mastered some basics. MS Windows networking is not particularly forgiving of misconfiguration. Users of MS Windows networking are likely to complain of persistent niggles that may be caused by a broken network configuration. To a great many people however, MS Windows networking starts with a domain controller that in some magical way is expected to solve all ills. </p><div class="figure"><a name="domain-example"></a><p class="title"><b>Figure�5.1.�An Example Domain</b></p><div class="mediaobject"><img src="projdoc/imagefiles/domain.png" width="270" alt="An Example Domain"></div></div><p> From the Samba mailing list one can readily identify many common networking issues. If you are not clear on the following subjects, then it will do much good to read the sections of this HOWTO that deal with it. These are the most common causes of MS Windows networking problems: </p><div class="itemizedlist"><ul type="disc"><li><p>Basic TCP/IP configuration</p></li><li><p>NetBIOS name resolution</p></li><li><p>Authentication configuration</p></li><li><p>User and Group configuration</p></li><li><p>Basic File and Directory Permission Control in UNIX/Linux</p></li><li><p>Understanding of how MS Windows clients interoperate in a network environment</p></li></ul></div><p> Do not be put off; on the surface of it MS Windows networking seems so simple that anyone can do it. In fact, it is not a good idea to set up an MS Windows network with inadequate training and preparation. But let's get our first indelible principle out of the way: <span class="emphasis"><em>It is perfectly OK to make mistakes!</em></span> In the right place and at the right time, mistakes are the essence of learning. It is <span class="emphasis"><em>very much</em></span> not ok to make mistakes that cause loss of productivity and impose an avoidable financial burden on an organisation. </p><p> Where is the right place to make mistakes? Only out of harm's way! If you are going to make mistakes, then please do this on a test network, away from users and in such a way as to not inflict pain on others. Do your learning on a test network. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869330"></a>Features and Benefits</h2></div></div><div></div></div><p> <span class="emphasis"><em>What is the key benefit of Microsoft Domain security?</em></span> </p><p> In a word, <span class="emphasis"><em>Single Sign On</em></span>, or SSO for short. To many, this is the holy grail of MS Windows NT and beyond networking. SSO allows users in a well designed network to log onto any workstation that is a member of the domain that their user account is in (or in a domain that has an appropriate trust relationship with the domain they are visiting) and they will be able to log onto the network and access resources (shares, files, and printers) as if they are sitting at their home (personal) workstation. This is a feature of the Domain security protocols. </p><p> The benefits of Domain security are available to those sites that deploy a Samba PDC. A Domain provides a unique network security identifier (SID). Domain user and group security identifiers are comprised of the network SID plus a relative identifier (RID) that is unique to the account. User and Group SIDs (the network SID plus the RID) can be used to create Access Control Lists (ACLs) attached to network resources to provide organizational access control. UNIX systems know only of local security identifiers. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Network clients of an MS Windows Domain security environment must be Domain members to be able to gain access to the advanced features provided. Domain membership involves more than just setting the workgroup name to the Domain name. It requires the creation of a Domain trust account for the workstation (called a machine account). Please refer to the chapter on <a href="#domain-member" title="Chapter�7.�Domain Membership">setting up samba as a domain member</a> for more information. </p></div><p> The following functionalities are new to the Samba-3 release: </p><div class="itemizedlist"><ul type="disc"><li><p> Windows NT4 domain trusts </p></li><li><p> Adding users via the User Manager for Domains. This can be done on any MS Windows client using the Nexus toolkit that is available from Microsoft's web site. Samba-3 supports the use of the Microsoft Management Console for user management. </p></li><li><p> Introduces replaceable and multiple user account (authentication) back ends. In the case where the back end is placed in an LDAP database, Samba-3 confers the benefits of a back end that can be distributed, replicated, and is highly scalable. </p></li><li><p> Implements full Unicode support. This simplifies cross locale internationalisation support. It also opens up the use of protocols that Samba-2.2.x had but could not use due to the need to fully support Unicode. </p></li></ul></div><p> The following functionalities are NOT provided by Samba-3: </p><div class="itemizedlist"><ul type="disc"><li><p> SAM replication with Windows NT4 Domain Controllers (i.e. a Samba PDC and a Windows NT BDC or vice versa). This means samba cannot operate as a BDC when the PDC is Microsoft-based or replicate account data to Windows-BDC's. </p></li><li><p> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and Active Directory) - In point of fact, Samba-3 DOES have some Active Directory Domain Control ability that is at this time purely experimental <span class="emphasis"><em>AND</em></span> that is certain to change as it becomes a fully supported feature some time during the Samba-3 (or later) life cycle. However, Active Directory is more then just SMB - it's also LDAP, Kerberos, DHCP and other protocols (with proprietary extensions, of course). </p></li></ul></div><p> Windows 9x / Me / XP Home clients are not true members of a domain for reasons outlined in this chapter. The protocol for support of Windows 9x / Me style network (domain) logons is completely different from NT4 / Win2k type domain logons and has been officially supported for some time. These clients use the old LanMan Network Logon facilities that are supported in Samba since approximately the Samba-1.9.15 series. </p><p> Samba-3 has an implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space). This is discussed more fully in <a href="#groupmapping" title="Chapter�12.�Mapping MS Windows and UNIX Groups">the chapter on group mapping</a>. </p><p> Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and machine trust account information in a suitable backend data store. Refer <a href="#machine-trust-accounts" title="MS Windows Workstation/Server Machine Trust Accounts">to the section on machine trust accounts</a>. With Samba-3 there can be multiple back-ends for this. A complete discussion of account database backends can be found in <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on Account Information Databases</a>. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2869545"></a>Basics of Domain Control</h2></div></div><div></div></div><p> Over the years, public perceptions of what Domain Control really is has taken on an almost mystical nature. Before we branch into a brief overview of Domain Control, there are three basic types of domain controllers: </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869560"></a>Domain Controller Types</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p> The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in the MS Windows NT4. In Windows 200x Domain Control architecture this role is held by domain controllers. There is folk lore that dictates that because of it's role in the MS Windows network, the domain controllers should be the most powerful and most capable machine in the network. As strange as it may seem to say this here, good over all network performance dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-Alone (or Domain Member) servers than in the domain controllers. </p><p> In the case of MS Windows NT4 style domains, it is the PDC that initiates a new Domain Control database. This forms a part of the Windows registry called the SAM (Security Account Manager). It plays a key part in NT4 type domain user authentication and in synchronisation of the domain authentication database with Backup Domain Controllers. </p><p> With MS Windows 200x Server based Active Directory domains, one domain controller initiates a potential hierarchy of domain controllers, each with their own area of delegated control. The master domain controller has the ability to override any down-stream controller, but a down-line controller has control only over it's down-line. With Samba-3 this functionality can be implemented using an LDAP based user and machine account back end. </p><p> New to Samba-3 is the ability to use a back-end database that holds the same type of data as the NT4 style SAM (Security Account Manager) database (one of the registry files). <sup>[<a name="id2869637" href="#ftn.id2869637">1</a>]</sup> </p><p> The <span class="emphasis"><em>Backup Domain Controller</em></span> or BDC plays a key role in servicing network authentication requests. The BDC is biased to answer logon requests in preference to the PDC. On a network segment that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to a PDC. If the PDC is on line at the time that a BDC is promoted to PDC, the previous PDC is automatically demoted to a BDC. With Samba-3 this is NOT an automatic operation; the PDC and BDC must be manually configured and changes need to be made likewise. </p><p> With MS Windows NT4, it is an install time decision what type of machine the server will be. It is possible to change the promote a BDC to a PDC and vice versa only, but the only way to convert a domain controller to a domain member server or a stand-alone server is to reinstall it. The install time choices offered are: </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Primary Domain Controller</em></span> - The one that seeds the domain SAM</p></li><li><p><span class="emphasis"><em>Backup Domain Controller</em></span> - One that obtains a copy of the domain SAM</p></li><li><p><span class="emphasis"><em>Domain Member Server</em></span> - One that has NO copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.</p></li><li><p><span class="emphasis"><em>Stand-Alone Server</em></span> - One that plays NO part is SAM synchronisation, has it's own authentication database and plays no role in Domain security.</p></li></ul></div><p> With MS Windows 2000 the configuration of domain control is done after the server has been installed. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active Directory domain. </p><p> New to Samba-3 is the ability to function fully as an MS Windows NT4 style Domain Controller, excluding the SAM replication components. However, please be aware that Samba-3 support the MS Windows 200x domain control protocols also. </p><p> At this time any appearance that Samba-3 is capable of acting as an <span class="emphasis"><em>Domain Controller</em></span> in native ADS mode is limited and experimental in nature. This functionality should not be used until the Samba-Team offers formal support for it. At such a time, the documentation will be revised to duly reflect all configuration and management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP environment. However, there are certain compromises: </p><div class="itemizedlist"><ul type="disc"><li><p>No machine policy files</p></li><li><p>No Group Policy Objects</p></li><li><p>No synchronously executed AD logon scripts</p></li><li><p>Can't use ANY Active Directory management tools to manage users and machines</p></li><li><p>Registry changes tattoo the main registry, while with AD they do NOT. ie: Leave permanent changes in effect</p></li><li><p>Without AD you can not peprform the function of exporting specific applications to specific users or groups</p></li></ul></div><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2869805"></a>Preparing for Domain Control</h3></div></div><div></div></div><p> There are two ways that MS Windows machines may interact with each other, with other servers, and with Domain Controllers: Either as <span class="emphasis"><em>Stand-Alone</em></span> systems, more commonly called <span class="emphasis"><em>Workgroup</em></span> members, or as full participants in a security system, more commonly called <span class="emphasis"><em>Domain</em></span> members. </p><p> It should be noted that <span class="emphasis"><em>Workgroup</em></span> membership involve no special configuration other than the machine being configured so that the network configuration has a commonly used name for it's workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this mode of configuration there are NO machine trust accounts and any concept of membership as such is limited to the fact that all machines appear in the network neighbourhood to be logically grouped together. Again, just to be clear: <span class="emphasis"><em>workgroup mode does not involve any security machine accounts</em></span>. </p><p> Domain member machines have a machine account in the Domain accounts database. A special procedure must be followed on each machine to affect Domain membership. This procedure, which can be done only by the local machine Administrator account, will create the Domain machine account (if if does not exist), and then initializes that account. When the client first logs onto the Domain it triggers a machine password change. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to <a href="#domain-member" title="Chapter�7.�Domain Membership">the chapter on domain membership</a> for information regarding HOW to make your MS Windows clients Domain members. </p></div><p> The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows NT4 / 200x / XP clients. </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2869911"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Consistent configuration of Name Resolution (See chapter on <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">Network Browsing</a> and on <a href="#integrate-ms-networks" title="Chapter�26.�Integrating MS Windows networks with Samba">Integrating Unix into Windows networks</a>)</p></li><li><p>Domain logons for Windows NT4 / 200x / XP Professional clients</p></li><li><p>Configuration of Roaming Profiles or explicit configuration to force local profile usage</p></li><li><p>Configuration of Network/System Policies</p></li><li><p>Adding and managing domain user accounts</p></li><li><p>Configuring MS Windows client machines to become domain members</p></li></ul></div><p> The following provisions are required to serve MS Windows 9x / Me Clients: </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows Networking</p></li><li><p>Correct designation of the Server Role (<a class="indexterm" name="id2870004"></a><i class="parameter"><tt>security</tt></i> = user)</p></li><li><p>Network Logon Configuration (Since Windows 9x / XP Home are not technically domain members, they do not really participate in the security aspects of Domain logons as such)</p></li><li><p>Roaming Profile Configuration</p></li><li><p>Configuration of System Policy handling</p></li><li><p>Installation of the Network driver "Client for MS Windows Networks" and configuration to log onto the domain</p></li><li><p>Placing Windows 9x / Me clients in user level security - if it is desired to allow all client share access to be controlled according to domain user / group identities.</p></li><li><p>Adding and managing domain user accounts</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Roaming Profiles and System/Network policies are advanced network administration topics that are covered in the <a href="#ProfileMgmt" title="Chapter�24.�Desktop Profile Management">Profile Management</a> and <a href="#PolicyMgmt" title="Chapter�23.�System and Account Policies">Policy Management</a> chapters of this document. However, these are not necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts. </p></div><p> A Domain Controller is an SMB/CIFS server that: </p><div class="itemizedlist"><ul type="disc"><li><p> Registers and advertises itself as a Domain Controller (through NetBIOS broadcasts as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast, to a WINS server over UDP unicast, or via DNS and Active Directory) </p></li><li><p> Provides the NETLOGON service (actually a collection of services that runs over a number of protocols. These include the LanMan Logon service, the Netlogon service, the Local Security Account service, and variations of them) </p></li><li><p> Provides a share called NETLOGON </p></li></ul></div><p> For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide the NETLOGON service which Samba calls the <a class="indexterm" name="id2870136"></a><i class="parameter"><tt>domain logons</tt></i> functionality (after the name of the parameter in the <tt class="filename">smb.conf</tt> file). Additionally, one (1) server in a Samba-3 Domain must advertise itself as the domain master browser<sup>[<a name="id2870160" href="#ftn.id2870160">2</a>]</sup>. This causes the Primary Domain Controller to claim domain specific NetBIOS name that identifies it as a domain master browser for its given domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870187"></a>Domain Control - Example Configuration</h2></div></div><div></div></div><p> The first step in creating a working Samba PDC is to understand the parameters necessary in <tt class="filename">smb.conf</tt>. An example <tt class="filename">smb.conf</tt> for acting as a PDC can be found in the example <a href="#pdc-example" title="Example�5.1.�smb.conf for being a PDC">for being a PDC</a>. </p><p> </p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example�5.1.�smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = BELERIAND</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = ldapsam, guest</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 33</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>logon path = \\%N\profiles\%u</tt></i></td></tr><tr><td><i class="parameter"><tt>logon drive = H:</tt></i></td></tr><tr><td><i class="parameter"><tt>logon home = \\homeserver\%u\winprofile</tt></i></td></tr><tr><td><i class="parameter"><tt>logon script = logon.cmd</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[netlogon]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/netlogon</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = ntadmin</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[profiles]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/profiles</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = no</tt></i></td></tr><tr><td><i class="parameter"><tt>create mask = 0600</tt></i></td></tr><tr><td><i class="parameter"><tt>directory mask = 0700</tt></i></td></tr></table></div><p> </p><p> The basic options shown above are explained as follows: </p><div class="variablelist"><dl><dt><span class="term">passdb backend</span></dt><dd><p> This contains all the user and group account information. Acceptable values for a PDC are: <span class="emphasis"><em>smbpasswd, tdbsam, ldapsam</em></span>. The 'guest' entry provides needed default accounts.</p><p> Where is is intended to use backup domain controllers (BDCs) the only logical choice is to use LDAP so that the passdb backend can be distributed. The tdbsam and smbpasswd files can not effectively be distributed and therefore should not be used. </p></dd><dt><span class="term">Domain Control Parameters</span></dt><dd><p> The parameters <span class="emphasis"><em>os level, preferred master, domain master, security, encrypt passwords, domain logons</em></span> play a central role in assuring domain control and network logon support.</p><p> The <span class="emphasis"><em>os level</em></span> must be set at or above a value of 32. A domain controller must be the domain master browser, must be set in <span class="emphasis"><em>user</em></span> mode security, must support Microsoft compatible encrypted passwords, and must provide the network logon service (domain logons). Encrypted passwords must be enabled, for more details on how to do this, refer to <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on account information databases</a>. </p></dd><dt><span class="term">Environment Parameters</span></dt><dd><p> The parameters <span class="emphasis"><em>logon path, logon home, logon drive, logon script</em></span> are environment support settings that help to facilitate client logon operations and that help to provide automated control facilities to ease network management overheads. Please refer to the man page information for these parameters. </p></dd><dt><span class="term">NETLOGON Share</span></dt><dd><p> The NETLOGON share plays a central role in domain logon and domain membership support. This share is provided on all Microsoft domain controllers. It is used to provide logon scripts, to store Group Policy files (NTConfig.POL), as well as to locate other common tools that may be needed for logon processing. This is an essential share on a domain controller. </p></dd><dt><span class="term">PROFILE Share</span></dt><dd><p> This share is used to store user desktop profiles. Eash user must have a directory at the root of this share. This directory must be write enabled for the user and must be globally read enabled. Samba-3 has a VFS module called 'fake_permissions' that may be installed on this share. This will allow a Samba administrator to make the directory read only to everyone. Of course this is useful only after the profile has been properly created. </p></dd></dl></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above parameters make for a full set of parameters that may define the server's mode of operation. The following <tt class="filename">smb.conf</tt> parameters are the essentials alone: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>netbios name = BELERIAND</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>security = User</tt></i></td></tr></table><p> </p><p> The additional parameters shown in the longer listing above just makes for more complete explanation. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870675"></a>Samba ADS Domain Control</h2></div></div><div></div></div><p> Samba-3 is not, and can not act as, an Active Directory Server. It can not truly function as an Active Directory Primary Domain Controller. The protocols for some of the functionality the Active Directory Domain Controllers has been partially implemented on an experimental only basis. Please do NOT expect Samba-3 to support these protocols. Do not depend on any such functionality either now or in the future. The Samba-Team may remove these experimental features or may change their behaviour. This is mentioned for the benefit of those who have discovered secret capabilities in samba-3 and who have asked when this functionality will be completed. The answer is: Maybe or maybe never! </p><p> To be sure: Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4 style domain controllers have. Samba-3 does NOT have all the capabilities of Windows NT4, but it does have a number of features that Windows NT4 domain contollers do not have. In short, Samba-3 is not NT4 and it is not Windows Server 200x and it is not an Active Directory server. We hope this is plain and simple enough for all to understand. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2870727"></a>Domain and Network Logon Configuration</h2></div></div><div></div></div><p> The subject of Network or Domain Logons is discussed here because it forms an integral part of the essential functionality that is provided by a Domain Controller. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2870742"></a>Domain Network Logon Service</h3></div></div><div></div></div><p> All Domain Controllers must run the netlogon service (<span class="emphasis"><em>domain logons</em></span> in Samba). One Domain Controller must be configured with <a class="indexterm" name="id2870759"></a><i class="parameter"><tt>domain master</tt></i> = Yes (the Primary Domain Controller); on ALL Backup Domain Controllers <a class="indexterm" name="id2870775"></a><i class="parameter"><tt>domain master</tt></i> = No must be set. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870791"></a>Example Configuration</h4></div></div><div></div></div><div class="example"><a name="id2870798"></a><p class="title"><b>Example�5.2.�smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = (Yes on PDC, No on BDCs)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[netlogon]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Network Logon Service</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/lib/samba/netlogon</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870882"></a>The Special Case of MS Windows XP Home Edition</h4></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> MS Windows XP Home Edition does not have the ability to join any type of Domain security facility. Unlike, MS Windows 9x / Me, MS Windows XP Home Edition also completely lacks the ability to log onto a network. </p></div><p> To be completely clear: If you want MS Windows XP Home Edition to integrate with your MS Windows NT4 or Active Directory Domain security understand - IT CAN NOT BE DONE. Your only choice is to buy the upgrade pack from MS Windows XP Home Edition to MS Windows XP Professional. </p><p> Now that this has been said, please do NOT ask the mailing list, or email any of the Samba-Team members with your questions asking how to make this work. It can't be done. If it can be done, then to do so would violate your software license agreement with Microsoft, and we recommend that you do not do that. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2870920"></a>The Special Case of Windows 9x / Me</h4></div></div><div></div></div><p> A domain and a workgroup are exactly the same in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a network. Also, different access rights can be granted to users if they successfully authenticate against a domain logon server. Samba-3 does this now in the same way that MS Windows NT/2K. </p><p> The SMB client logging on to a domain has an expectation that every other server in the domain should accept the same authentication information. Network browsing functionality of domains and workgroups is identical and is explained in this documentation under the browsing discussions. It should be noted, that browsing is totally orthogonal to logon support. </p><p> Issues related to the single-logon network model are discussed in this section. Samba supports domain logons, network logon scripts, and user profiles for MS Windows for workgroups and MS Windows 9X/ME clients which are the focus of this section. </p><p> When an SMB client in a domain wishes to logon, it broadcasts requests for a logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but ill advised ) to create a domain where the user database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely involved with domains. </p><p> Using these features you can make your clients verify their logon via the Samba server; make clients run a batch file when they logon to the network and download their preferences, desktop and start menu. </p><p><span class="emphasis"><em> MS Windows XP Home edition is NOT able to join a domain and does not permit the use of domain logons. </em></span></p><p> Before launching into the configuration instructions, it is worthwhile to look at how a Windows 9x/ME client performs a logon: </p><div class="orderedlist"><ol type="1"><li><p> The client broadcasts (to the IP broadcast address of the subnet it is in) a NetLogon request. This is sent to the NetBIOS name DOMAIN<#1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of <tt class="filename">\\SERVER</tt>. </p></li><li><p> The client then connects to that server, logs on (does an SMBsessetupX) and then connects to the IPC$ share (using an SMBtconX). </p></li><li><p> The client then does a NetWkstaUserLogon request, which retrieves the name of the user's logon script. </p></li><li><p> The client then connects to the NetLogon share and searches for said script and if it is found and can be read, is retrieved and executed by the client. After this, the client disconnects from the NetLogon share. </p></li><li><p> The client then sends a NetUserGetInfo request to the server, to retrieve the user's home share, which is used to search for profiles. Since the response to the NetUserGetInfo request does not contain much more than the user's home share, profiles for Win9X clients MUST reside in the user home directory. </p></li><li><p> The client then connects to the user's home share and searches for the user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, <tt class="filename">\\server\fred\.winprofile</tt>. If the profiles are found, they are implemented. </p></li><li><p> The client then disconnects from the user's home share, and reconnects to the NetLogon share and looks for <tt class="filename">CONFIG.POL</tt>, the policies file. If this is found, it is read and implemented. </p></li></ol></div><p> The main difference between a PDC and a Windows 9x logon server configuration is that </p><div class="itemizedlist"><ul type="disc"><li><p> Password encryption is not required for a Windows 9x logon server. But note that beginning with MS Windows 98 the default setting is that plain-text password support is disabled. It can be re-enabled with the registry changes that are documented in the chapter on Policies. </p></li><li><p> Windows 9x/ME clients do not require and do not use machine trust accounts. </p></li></ul></div><p> A Samba PDC will act as a Windows 9x logon server; after all, it does provide the network logon services that MS Windows 9x / Me expect to find. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Use of plain-text passwords is strongly discouraged. Where used they are easily detected using a sniffer tool to examine network traffic. </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871174"></a>Security Mode and Master Browsers</h3></div></div><div></div></div><p> There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue of whether or not it is ok to configure Samba as a Domain Controller in security modes other than <tt class="constant">USER</tt>. The only security mode which will not work due to technical reasons is <tt class="constant">SHARE</tt> mode security. <tt class="constant">DOMAIN</tt> and <tt class="constant">SERVER</tt> mode security are really just a variation on SMB user level security. </p><p> Actually, this issue is also closely tied to the debate on whether or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons are two distinctly different functions), it is not a good idea to do so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. A DMB is a Domain Master Browser - see <a href="#DMB" title="Setting up WORKGROUP Browsing">Domain Master Browser</a>. For this reason, it is very wise to configure the Samba DC as the DMB. </p><p> Now back to the issue of configuring a Samba DC to use a mode other than <a class="indexterm" name="id2871243"></a><i class="parameter"><tt>security</tt></i> = user. If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network (the <a class="indexterm" name="id2871260"></a><i class="parameter"><tt>password server</tt></i>) knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now in order to operate in domain mode security, the <a class="indexterm" name="id2871278"></a><i class="parameter"><tt>workgroup</tt></i> parameter must be set to the name of the Windows NT domain (which already has a domain controller). If the domain does NOT already have a Domain Controller then you do not yet have a Domain! </p><p> Configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC to be the DMB for its domain and set <a class="indexterm" name="id2871302"></a><i class="parameter"><tt>security</tt></i> = user. This is the only officially supported mode of operation. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871320"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871328"></a>'$' cannot be included in machine name</h3></div></div><div></div></div><p> A 'machine account', (typically) stored in <tt class="filename">/etc/passwd</tt>, takes the form of the machine name with a '$' appended. FreeBSD (and other BSD systems?) won't create a user with a '$' in their name. </p><p> The problem is only in the program used to make the entry. Once made, it works perfectly. Create a user without the '$'. Then use <b class="command">vipw</b> to edit the entry, adding the '$'. Or create the whole entry with vipw if you like; make sure you use a unique User ID! </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The UNIX tool <b class="command">vipw</b> is a common tool for directly editting the <tt class="filename">/etc/passwd</tt> file. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871386"></a>Joining domain fails because of existing machine account</h3></div></div><div></div></div><p>“<span class="quote">I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an existing set.." when creating a machine trust account.</span>”</p><p> This happens if you try to create a machine trust account from the machine itself and already have a connection (e.g. mapped drive) to a share (or IPC$) on the Samba PDC. The following command will remove all network drive connections: </p><pre class="screen"> <tt class="prompt">C:\> </tt><b class="userinput"><tt>net use * /d</tt></b> </pre><p> Further, if the machine is already a 'member of a workgroup' that is the same name as the domain you are joining (bad idea) you will get this message. Change the workgroup name to something else, it does not matter what, reboot, and try again. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871445"></a>The system can not log you on (C000019B)....</h3></div></div><div></div></div><p>“<span class="quote">I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, <span class="errorname">The system can not log you on (C000019B), Please try again or consult your system administrator</span> when attempting to logon.</span>” </p><p> This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a change in domain SID is when the domain name and/or the server name (NetBIOS name) is changed. The only way to correct the problem is to restore the original domain SID or remove the domain client from the domain and rejoin. The domain SID may be reset using either the net or rpcclient utilities. </p><p> The reset or change the domain SID you can use the net command as follows: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net getlocalsid 'OLDNAME'</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>net setlocalsid 'SID'</tt></b> </pre><p> </p><p> Workstation machine trust accounts work only with the Domain (or network) SID. If this SID changes then domain members (workstations) will not be able to log onto the domain. The original Domain SID can be recovered from the secrets.tdb file. The alternative is to visit each workstation to re-join it to the domain. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871529"></a>The machine trust account not accessible</h3></div></div><div></div></div><p> “<span class="quote">When I try to join the domain I get the message <span class="errorname">The machine account for this computer either does not exist or is not accessible</span>. What's wrong?</span>” </p><p> This problem is caused by the PDC not having a suitable machine trust account. If you are using the <a class="indexterm" name="id2871555"></a><i class="parameter"><tt>add machine script</tt></i> method to create accounts then this would indicate that it has not worked. Ensure the domain admin user system is working. </p><p> Alternatively if you are creating account entries manually then they have not been created correctly. Make sure that you have the entry correct for the machine trust account in <tt class="filename">smbpasswd</tt> file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd utility, make sure that the account name is the machine NetBIOS name with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. </p><p> Some people have also reported that inconsistent subnet masks between the Samba server and the NT client can cause this problem. Make sure that these are consistent for both client and server. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871602"></a>Account disabled</h3></div></div><div></div></div><p>“<span class="quote">When I attempt to login to a Samba Domain from a NT4/W2K workstation, I get a message about my account being disabled.</span>”</p><p> Enable the user accounts with <b class="userinput"><tt>smbpasswd -e <i class="replaceable"><tt>username</tt></i> </tt></b>, this is normally done as an account is created. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871634"></a>Domain Controller Unavailable</h3></div></div><div></div></div><p>“<span class="quote">Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"</span>”</p><p> A domain controller has to announce on the network who it is. This usually takes a while. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2871658"></a>Can not log onto domain member workstation after joining domain</h3></div></div><div></div></div><p>After successfully joining the domain user logons fail with one of two messages:</p><p>One to the effect that the domain controller can not be found, the other claiming that the account does not exist in the domain or that the password is incorrect.</p><p>This may be due to incompatible settings between the Windows client and the Samba-3 server for <span class="emphasis"><em>schannel</em></span> (secure channel) settings or <span class="emphasis"><em>smb signing</em></span> settings. Check your samba settings for <span class="emphasis"><em> client schannel, server schannel, client signing, server signing</em></span> by executing: <b class="command">testparm -v | more</b> and looking for the value of these parameters. </p><p> Also use the Microsoft Management Console - Local Security Settings. This tool is available from the Control Panel. The Policy settings are found in the Local Policies / Securty Options area and are prefixed by <span class="emphasis"><em>Secure Channel: ..., and Digitally sign ...</em></span>. </p><p> It is important that these be set consistently with the Samba-3 server settings. </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2869637" href="#id2869637">1</a>] </sup>See also <a href="#passdb" title="Chapter�11.�Account Information Databases">the chapter on Account Information Databases</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id2870160" href="#id2870160">2</a>] </sup>See also <a href="#NetworkBrowsing" title="Chapter�10.�Samba / MS Windows Network Browsing Guide">the chapter about network browsing</a></p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-bdc"></a>Chapter�6.�Backup Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Volker</span> <span class="surname">Lendecke</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2871817">Features And Benefits</a></dt><dt><a href="#id2872006">Essential Background Information</a></dt><dd><dl><dt><a href="#id2872035">MS Windows NT4 Style Domain Control</a></dt><dt><a href="#id2872286">Active Directory Domain Control</a></dt><dt><a href="#id2872307">What qualifies a Domain Controller on the network?</a></dt><dt><a href="#id2872332">How does a Workstation find its domain controller?</a></dt></dl></dd><dt><a href="#id2872346">Backup Domain Controller Configuration</a></dt><dd><dl><dt><a href="#id2872480">Example Configuration</a></dt></dl></dd><dt><a href="#id2872638">Common Errors</a></dt><dd><dl><dt><a href="#id2872650">Machine Accounts keep expiring, what can I do?</a></dt><dt><a href="#id2872682">Can Samba be a Backup Domain Controller to an NT4 PDC?</a></dt><dt><a href="#id2872708">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2872753">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><p> Before you continue reading in this section, please make sure that you are comfortable with configuring a Samba Domain Controller as described in <a href="#samba-pdc" title="Chapter�5.�Domain Control">chapter on setting up Samba as a PDC</a>. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2871817"></a>Features And Benefits</h2></div></div><div></div></div><p> This is one of the most difficult chapters to summarise. It does not matter what we say here for someone will still draw conclusions and / or approach the Samba-Team with expectations that are either not yet capable of being delivered, or that can be achieved far more effectively using a totally different approach. In the event that you should have a persistent concern that is not addressed in this book then please email <a href="mailto:jht@samba.org" target="_top">John H Terpstra</a> clearly setting out your requirements and / or question and we will do our best to provide a solution. </p><p> Samba-3 is capable of acting as a Backup Domain Controller to another Samba Primary Domain Controller. A Samba-3 PDC can operate with an LDAP Account backend. The LDAP backend can be either a common master LDAP server, or a slave server. The use of a slave LDAP server has the benefit that when the master is down clients may still be able to log onto the network. This effectively gives samba a high degree of scalability iand is a very sweet (nice) solution for large organisations. </p><p> While it is possible to run a Samba-3 BDC with non-LDAP backend, the administrator will need to figure out precisely what is the best way to replicate (copy / distribute) the user and machine Accounts backend. </p><p> The use of a non-LDAP backend SAM database is particularly problematic because Domain member servers and workstations periodically change the machine trust account password. The new password is then stored only locally. This means that in the absence of a centrally stored accounts database (such as that provided with an LDAP based solution) if Samba-3 is running as a BDC, the BDC instance of the Domain member trust account password will not reach the PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs this results in overwriting of the SAM that contains the updated (changed) trust account password with resulting breakage of the domain trust. </p><p> Considering the number of comments and questions raised concerning how to configure a BDC lets consider each possible option and look at the pro's and con's for each theoretical solution: </p><div class="itemizedlist"><p class="title"><b>Backup Domain Backend Account Distribution Options</b></p><ul type="disc"><li><p> Solution: Passwd Backend is LDAP based, BDCs use a slave LDAP server </p><p> Arguments For: This is a neat and manageable solution. The LDAP based SAM (ldapsam) is constantly kept up to date. </p><p> Arguments Against: Complexity </p></li><li><p> Passdb Backend is tdbsam based, BDCs use cron based <span class="emphasis"><em>net rpc vampire</em></span> to obtain the Accounts database from the PDC and place them into the Samba SAM. <span class="emphasis"><em>net rpc vampire</em></span> is a Samba function of the "net" command. </p><p> Arguments For: It would be a nice solution </p><p> Arguments Against: It does not work because Samba-3 does not support the required protocols. This may become a later feature but is not available today. </p></li><li><p> Make use of rsync to replicate (pull down) copies of the essential account files </p><p> Arguments For: It is a simple solution, easy to set up as a scheduled job </p><p> Arguments Against: This will over-write the locally changed machine trust account passwords. This is a broken and flawed solution. Do NOT do this. </p></li><li><p> Operate with an entirely local accounts database (not recommended) </p><p> Arguments For: Simple, easy to maintain </p><p> Arguments Against: All machine trust accounts and user accounts will be locally maintained. Domain users will NOT be able to roam from office to office. This is a broken and flawed solution. Do NOT do this. </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872006"></a>Essential Background Information</h2></div></div><div></div></div><p> A Domain Controller is a machine that is able to answer logon requests from network workstations. Microsoft LanManager and IBM LanServer were two early products that provided this capability. The technology has become known as the LanMan Netlogon service. </p><p> When MS Windows NT3.10 was first released, it supported an new style of Domain Control and with it a new form of the network logon service that has extended functionality. This service became known as the NT NetLogon Service. The nature of this service has changed with the evolution of MS Windows NT and today provides a very complex array of services that are implemented over a complex spectrum of technologies. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872035"></a>MS Windows NT4 Style Domain Control</h3></div></div><div></div></div><p> Whenever a user logs into a Windows NT4 / 200x / XP Professional Workstation, the workstation connects to a Domain Controller (authentication server) to validate the username and password that the user entered are valid. If the information entered does not validate against the account information that has been stored in the Domain Control database (the SAM, or Security Account Manager database) then a set of error codes is returned to the workstation that has made the authentication request. </p><p> When the username / password pair has been validated, the Domain Controller (authentication server) will respond with full enumeration of the account information that has been stored regarding that user in the User and Machine Accounts database for that Domain. This information contains a complete network access profile for the user but excludes any information that is particular to the user's desktop profile, or for that matter it excludes all desktop profiles for groups that the user may belong to. It does include password time limits, password uniqueness controls, network access time limits, account validity information, machine names from which the user may access the network, and much more. All this information was stored in the SAM in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0). </p><p> The account information (user and machine) on Domain Controllers is stored in two files, one containing the Security information and the other the SAM. These are stored in files by the same name in the <tt class="filename">C:\WinNT\System32\config</tt> directory. These are the files that are involved in replication of the SAM database where Backup Domain Controllers are present on the network. </p><p> There are two situations in which it is desirable to install Backup Domain Controllers: </p><div class="itemizedlist"><ul type="disc"><li><p> On the local network that the Primary Domain Controller is on, if there are many workstations and/or where the PDC is generally very busy. In this case the BDCs will pick up network logon requests and help to add robustness to network services. </p></li><li><p> At each remote site, to reduce wide area network traffic and to add stability to remote network operations. The design of the network, the strategic placement of Backup Domain Controllers, together with an implementation that localises as much of network to client interchange as possible will help to minimise wide area network bandwidth needs (and thus costs). </p></li></ul></div><p> The PDC contains the master copy of the SAM. In the event that an administrator makes a change to the user account database while physically present on the local network that has the PDC, the change will likely be made directly to the PDC instance of the master copy of the SAM. In the event that this update may be performed in a branch office the change will likely be stored in a delta file on the local BDC. The BDC will then send a trigger to the PDC to commence the process of SAM synchronisation. The PDC will then request the delta from the BDC and apply it to the master SAM. The PDC will then contact all the BDCs in the Domain and trigger them to obtain the update and then apply that to their own copy of the SAM. </p><p> Thus the BDC is said to hold a <span class="emphasis"><em>read-only</em></span> of the SAM from which it is able to process network logon requests and to authenticate users. The BDC can continue to provide this service, particularly while, for example, the wide area network link to the PDC is down. Thus a BDC plays a very important role in both maintenance of Domain security as well as in network integrity. </p><p> In the event that the PDC should need to be taken out of service, or if it dies, then one of the BDCs can be promoted to a PDC. If this happens while the original PDC is on line then it is automatically demoted to a BDC. This is an important aspect of Domain Controller management. The tool that is used to affect a promotion or a demotion is the Server Manager for Domains. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2872186"></a>Example PDC Configuration</h4></div></div><div></div></div><p> Since version 2.2 Samba officially supports domain logons for all current Windows Clients, including Windows NT4, 2003 and XP Professional. For samba to be enabled as a PDC some parameters in the <i class="parameter"><tt>[global]</tt></i>-section of the <tt class="filename">smb.conf</tt> have to be set: </p><div class="example"><a name="id2872218"></a><p class="title"><b>Example�6.1.�Minimal smb.conf for being a PDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr></table></div><p> Several other things like a <i class="parameter"><tt>[homes]</tt></i> and a <i class="parameter"><tt>[netlogon]</tt></i> share also need to be set along with settings for the profile path, the users home drive, etc.. This will not be covered in this chapter, for more information please refer to <a href="#samba-pdc" title="Chapter�5.�Domain Control">the chapter about samba as a PDC</a>. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872286"></a>Active Directory Domain Control</h3></div></div><div></div></div><p> As of the release of MS Windows 2000 and Active Directory, this information is now stored in a directory that can be replicated and for which partial or full administrative control can be delegated. Samba-3 is NOT able to be a Domain Controller within an Active Directory tree, and it can not be an Active Directory server. This means that Samba-3 also can NOT act as a Backup Domain Controller to an Active Directory Domain Controller. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872307"></a>What qualifies a Domain Controller on the network?</h3></div></div><div></div></div><p> Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA<#1c> with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA<#1b> with the WINS server. The name type <#1b> name is normally reserved for the Domain Master Browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to be on the same machine as the PDC. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872332"></a>How does a Workstation find its domain controller?</h3></div></div><div></div></div><p> An MS Windows NT4 / 200x / XP Professional workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA<#1c>. It assumes that each of the machines it gets back from the queries is a domain controller and can answer logon requests. To not open security holes both the workstation and the selected domain controller authenticate each other. After that the workstation sends the user's credentials (name and password) to the local Domain Controller, for validation. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872346"></a>Backup Domain Controller Configuration</h2></div></div><div></div></div><p> Several things have to be done: </p><div class="itemizedlist"><ul type="disc"><li><p> The domain SID has to be the same on the PDC and the BDC. This used to be stored in the file private/MACHINE.SID. This file is not created since Samba 2.2.5. Nowadays the domain SID is stored in the file private/secrets.tdb. Simply copying the secrets.tdb from the PDC to the BDC does not work, as the BDC would generate a new SID for itself and override the domain SID with this new BDC SID.</p><p> To retrieve the domain SID from the PDC or an existing BDC and store it in the secrets.tdb, execute: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net rpc getsid</tt></b> </pre></li><li><p> The UNIX user database has to be synchronized from the PDC to the BDC. This means that both the /etc/passwd and /etc/group have to be replicated from the PDC to the BDC. This can be done manually whenever changes are made, or the PDC is set up as a NIS master server and the BDC as a NIS slave server. To set up the BDC as a mere NIS client would not be enough, as the BDC would not be able to access its user database in case of a PDC failure. NIS is by no means the only method to synchronize passwords. An LDAP solution would work as well. </p></li><li><p> The Samba password database has to be replicated from the PDC to the BDC. As said above, though possible to synchronise the <tt class="filename">smbpasswd</tt> file with rsync and ssh, this method is broken and flawed, and is therefore not recommended. A better solution is to set up slave LDAP servers for each BDC and a master LDAP server for the PDC. </p></li><li><p> Any netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd synchronization. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872480"></a>Example Configuration</h3></div></div><div></div></div><p> Finally, the BDC has to be found by the workstations. This can be done by setting: </p><div class="example"><a name="id2872495"></a><p class="title"><b>Example�6.2.�Minimal setup for being a BDC</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap backend = ldapsam://slave-ldap.quenya.org</tt></i></td></tr></table></div><p> In the <i class="parameter"><tt>[global]</tt></i>-section of the <tt class="filename">smb.conf</tt> of the BDC. This makes the BDC only register the name SAMBA<#1c> with the WINS server. This is no problem as the name SAMBA<#1c> is a NetBIOS group name that is meant to be registered by more than one machine. The parameter <a class="indexterm" name="id2872563"></a><i class="parameter"><tt>domain master</tt></i> = no forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS name is reserved for the Primary Domain Controller. </p><p> The <i class="parameter"><tt>idmap backend</tt></i> will redirect the <b class="command">winbindd</b> utility to use the LDAP database to resolve all UIDs and GIDs for UNIX accounts. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Samba-3 has introduced a new ID mapping facility. One of the features of this facility is that it allows greater flexibility in how user and group IDs are handled in respect of NT Domain User and Group SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Linux UID and GID values will be consistent on the PDC, all BDCs and all Domain Member servers. The parameter that controls this is called <i class="parameter"><tt>idmap backend</tt></i>. Please refer to the man page for <tt class="filename">smb.conf</tt> for more information regarding it's behaviour. Do NOT set this parameter except where an LDAP backend (ldapsam) is in use. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872638"></a>Common Errors</h2></div></div><div></div></div><p> As this is a rather new area for Samba there are not many examples that we may refer to. Keep watching for updates to this section. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872650"></a>Machine Accounts keep expiring, what can I do?</h3></div></div><div></div></div><p> This problem will occur when occur when the passdb (SAM) files are copied from a central server but the local Backup Domain Controllers. Local machine trust account password updates are not copied back to the central server. The newer machine account password is then over written when the SAM is copied from the PDC. The result is that the Domain member machine on start up will find that it's passwords does not match the one now in the database and since the startup security check will now fail, this machine will not allow logon attempts to proceed and the account expiry error will be reported. </p><p> The solution: use a more robust passdb backend, such as the ldapsam backend, setting up an slave LDAP server for each BDC, and a master LDAP server for the PDC. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872682"></a>Can Samba be a Backup Domain Controller to an NT4 PDC?</h3></div></div><div></div></div><p> With version 2.2, no. The native NT4 SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for Samba-3. </p><p> Can I get the benefits of a BDC with Samba? Yes, but only to a Samba PDC. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to service logon requests whenever the PDC is down. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872708"></a>How do I replicate the smbpasswd file?</h3></div></div><div></div></div><p> Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is done in the smbpasswd file and has to be replicated to the BDC. So replicating the smbpasswd file very often is necessary. </p><p> As the smbpasswd file contains plain text password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. Ssh itself can be set up to accept <span class="emphasis"><em>only</em></span> rsync transfer without requiring the user to type a password. </p><p> As said a few times before, use of this method is broken and flawed. Machine trust accounts will go out of sync, resulting in a very broken domain. This method is <span class="emphasis"><em>not</em></span> recommended. Try using LDAP instead. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2872753"></a>Can I do this all with LDAP?</h3></div></div><div></div></div><p> The simple answer is YES. Samba's pdb_ldap code supports binding to a replica LDAP server, and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read only, so this will not occur often). </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter�7.�Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2872960">Features and Benefits</a></dt><dt><a href="#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></dt><dd><dl><dt><a href="#id2873290">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873596">Using NT4 Server Manager to Add Machine Accounts to the Domain</a></dt><dt><a href="#id2873811">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="#id2873884">Making an MS Windows Workstation or Server a Domain Member</a></dt></dl></dd><dt><a href="#domain-member-server">Domain Member Server</a></dt><dd><dl><dt><a href="#id2874094">Joining an NT4 type Domain with Samba-3</a></dt><dt><a href="#id2874530">Why is this better than security = server?</a></dt></dl></dd><dt><a href="#ads-member">Samba ADS Domain Membership</a></dt><dd><dl><dt><a href="#id2874715">Setup your smb.conf</a></dt><dt><a href="#id2874844">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2875221">Notes</a></dt></dl></dd><dt><a href="#id2875243">Common Errors</a></dt><dd><dl><dt><a href="#id2875286">Can Not Add Machine Back to Domain</a></dt><dt><a href="#id2875318">Adding Machine to Domain Fails</a></dt><dt><a href="#id2875462">I can't join a Windows 2003 PDC</a></dt></dl></dd></dl></div><p> Domain Membership is a subject of vital concern, Samba must be able to participate as a member server in a Microsoft Domain security context, and Samba must be capable of providing Domain machine member trust accounts, otherwise it would not be capable of offering a viable option for many users. </p><p> This chapter covers background information pertaining to domain membership, Samba configuration for it, and MS Windows client procedures for joining a domain. Why is this necessary? Because both are areas in which there exists within the current MS Windows networking world and particularly in the UNIX/Linux networking and administration world, a considerable level of mis-information, incorrect understanding, and a lack of knowledge. Hopefully this chapter will fill the voids. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2872960"></a>Features and Benefits</h2></div></div><div></div></div><p> MS Windows workstations and servers that want to participate in domain security need to be made Domain members. Participating in Domain security is often called <span class="emphasis"><em>Single Sign On</em></span> or <span class="acronym">SSO</span> for short. This chapter describes the process that must be followed to make a workstation (or another server - be it an <span class="application">MS Windows NT4 / 200x</span> server) or a Samba server a member of an MS Windows Domain security context. </p><p> Samba-3 can join an MS Windows NT4 style domain as a native member server, an MS Windows Active Directory Domain as a native member server, or a Samba Domain Control network. </p><p> Domain membership has many advantages: </p><div class="itemizedlist"><ul type="disc"><li><p> MS Windows workstation users get the benefit of SSO </p></li><li><p> Domain user access rights and file ownership / access controls can be set from the single Domain SAM (Security Account Manager) database (works with Domain member servers as well as with MS Windows workstations that are domain members) </p></li><li><p> Only <span class="application">MS Windows NT4 / 200x / XP Professional</span> workstations that are Domain members can use network logon facilities </p></li><li><p> Domain Member workstations can be better controlled through the use of Policy files (<tt class="filename">NTConfig.POL</tt>) and Desktop Profiles. </p></li><li><p> Through the use of logon scripts, users can be given transparent access to network applications that run off application servers </p></li><li><p> Network administrators gain better application and user access management abilities because there is no need to maintain user accounts on any network client or server, other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an LDAP directory, or via an Active Directory infrastructure) </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="machine-trust-accounts"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div><div></div></div><a class="indexterm" name="id2873091"></a><p> A machine trust account is an account that is used to authenticate a client machine (rather than a user) to the Domain Controller server. In Windows terminology, this is known as a "Computer Account." </p><p> The password of a machine trust account acts as the shared secret for secure communication with the Domain Controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group accounts. Windows NT, 200x, XP Professional clients use machine trust accounts, but Windows 9x / Me / XP Home clients do not. Hence, a Windows 9x / Me / XP Home client is never a true member of a domain because it does not possess a machine trust account, and thus has no shared secret with the domain controller. </p><p> A Windows NT4 PDC stores each machine trust account in the Windows Registry. The introduction of MS Windows 2000 saw the introduction of Active Directory, the new repository for machine trust accounts. </p><p> A Samba PDC, however, stores each machine trust account in two parts, as follows: </p><div class="itemizedlist"><ul type="disc"><li><p> A Domain Security Account (stored in the <a class="indexterm" name="id2873145"></a><i class="parameter"><tt>passdb backend</tt></i> that has been configured in the <tt class="filename">smb.conf</tt> file. The precise nature of the account information that is stored depends on the type of backend database that has been chosen. </p><p> The older format of this data is the <tt class="filename">smbpasswd</tt> database which contains the UNIX login ID, the UNIX user identifier (UID), and the LanMan and NT encrypted passwords. There is also some other information in this file that we do not need to concern ourselves with here. </p><p> The two newer database types are called <span class="emphasis"><em>ldapsam</em></span>, <span class="emphasis"><em>tdbsam</em></span>. Both store considerably more data than the older <tt class="filename">smbpasswd</tt> file did. The extra information enables new user account controls to be used. </p></li><li><p> A corresponding UNIX account, typically stored in <tt class="filename">/etc/passwd</tt>. Work is in progress to allow a simplified mode of operation that does not require UNIX user accounts, but this may not be a feature of the early releases of Samba-3. </p></li></ul></div><p> </p><a class="indexterm" name="id2873227"></a><p> There are three ways to create machine trust accounts: </p><div class="itemizedlist"><ul type="disc"><li><p> Manual creation from the UNIX/Linux command line. Here, both the Samba and corresponding UNIX account are created by hand. </p></li><li><p> <a class="indexterm" name="id2873260"></a> Using the MS Windows NT4 Server Manager (either from an NT4 Domain member server, or using the Nexus toolkit available from the Microsoft web site. This tool can be run from any MS Windows machine so long as the user is logged on as the administrator account. </p></li><li><p> "On-the-fly" creation. The Samba machine trust account is automatically created by Samba at the time the client is joined to the domain. (For security, this is the recommended method.) The corresponding UNIX account may be created automatically or manually. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873290"></a>Manual Creation of Machine Trust Accounts</h3></div></div><div></div></div><p> The first step in manually creating a machine trust account is to manually create the corresponding UNIX account in <tt class="filename">/etc/passwd</tt>. This can be done using <b class="command">vipw</b> or another 'add user' command that is normally used to create new UNIX accounts. The following is an example for a Linux based Samba server: <a class="indexterm" name="id2873321"></a> <a class="indexterm" name="id2873329"></a> </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>/usr/sbin/useradd -g 100 -d /dev/null -c <i class="replaceable"><tt>"machine nickname"</tt></i> \ -s /bin/false <i class="replaceable"><tt>machine_name</tt></i>$ </tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>passwd -l <i class="replaceable"><tt>machine_name</tt></i>$</tt></b> </pre><p> </p><p> <a class="indexterm" name="id2873391"></a> On *BSD systems, this can be done using the <b class="command">chpass</b> utility: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>chpass -a \ "<i class="replaceable"><tt>machine_name</tt></i>$:*:101:100::0:0:Workstation <i class="replaceable"><tt>machine_name</tt></i>:/dev/null:/sbin/nologin"</tt></b> </pre><p> </p><p> The <tt class="filename">/etc/passwd</tt> entry will list the machine name with a "$" appended, won't have a password, will have a null shell and no home directory. For example a machine named 'doppy' would have an <tt class="filename">/etc/passwd</tt> entry like this: </p><pre class="programlisting"> doppy$:x:505:100:<i class="replaceable"><tt>machine_nickname</tt></i>:/dev/null:/bin/false </pre><p> Above, <i class="replaceable"><tt>machine_nickname</tt></i> can be any descriptive name for the client, i.e., BasementComputer. <i class="replaceable"><tt>machine_name</tt></i> absolutely must be the NetBIOS name of the client to be joined to the domain. The "$" must be appended to the NetBIOS name of the client or Samba will not recognize this as a machine trust account. </p><p> Now that the corresponding UNIX account has been created, the next step is to create the Samba account for the client containing the well-known initial machine trust account password. This can be done using the <b class="command">smbpasswd</b> command as shown here: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -a -m <i class="replaceable"><tt>machine_name</tt></i></tt></b> </pre><p> </p><p> where <i class="replaceable"><tt>machine_name</tt></i> is the machine's NetBIOS name. The RID of the new machine account is generated from the UID of the corresponding UNIX account. </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p> Manually creating a machine trust account using this method is the equivalent of creating a machine trust account on a Windows NT PDC using <a class="indexterm" name="id2873570"></a> the <span class="application">Server Manager</span>. From the time at which the account is created to the time which the client joins the domain and changes the password, your domain is vulnerable to an intruder joining your domain using a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873596"></a>Using NT4 Server Manager to Add Machine Accounts to the Domain</h3></div></div><div></div></div><p> If the machine from which you are trying to manage the domain is an <span class="application">MS Windows NT4 workstation or MS Windows 200x / XP Professional</span> then the tool of choice is the package called <b class="command">SRVTOOLS.EXE</b>. When executed in the target directory this will unpack <b class="command">SrvMge.exe</b> and <b class="command">UsrMgr.exe</b> (both are domain management tools for MS Windows NT4 workstation). </p><p> If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product you should download the <b class="command">Nexus.exe</b> package from the Microsoft web site. When executed from the target directory this will unpack the same tools but for use on this platform. </p><p> Further information about these tools may be obtained from the following locations: <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;173673</a> <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;172540</a> </p><p> Launch the <b class="command">srvmgr.exe</b> (Server Manager for Domains) and follow these steps: </p><div class="procedure"><p class="title"><b>Procedure�7.1.�Server Manager Account Machine Account Management</b></p><ol type="1"><li><p> From the menu select <span class="guimenu">Computer</span> </p></li><li><p> Click on <span class="guimenuitem">Select Domain</span> </p></li><li><p> Click on the name of the domain you wish to administer in the <span class="guilabel">Select Domain</span> panel and then click <span class="guibutton">OK</span>. </p></li><li><p> Again from the menu select <span class="guimenu">Computer</span> </p></li><li><p> Select <span class="guimenuitem">Add to Domain</span> </p></li><li><p> In the dialog box, click on the radio button to <span class="guilabel">Add NT Workstation of Server</span>, then enter the machine name in the field provided, then click the <span class="guibutton">Add</span> button. </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873811"></a>"On-the-Fly" Creation of Machine Trust Accounts</h3></div></div><div></div></div><p> The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client is joined to the domain. </p><p>Since each Samba machine trust account requires a corresponding UNIX account, a method for automatically creating the UNIX account is usually supplied; this requires configuration of the add machine script option in <tt class="filename">smb.conf</tt>. This method is not required, however; corresponding UNIX accounts may also be created manually. </p><p> Below is an example for a RedHat Linux system. </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># <...remainder of parameters...></td></tr><tr><td><i class="parameter"><tt>add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2873884"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div><div></div></div><p> The procedure for making an MS Windows workstation of server a member of the domain varies with the version of Windows: </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873896"></a>Windows 200x XP Professional</h4></div></div><div></div></div><p> When the user elects to make the client a domain member, Windows 200x prompts for an account and password that has privileges to create machine accounts in the domain. A Samba administrative account (i.e., a Samba account that has root privileges on the Samba server) must be entered here; the operation will fail if an ordinary user account is given. </p><p> Note: For security reasons the password for this administrative account should be set to a password that is other than that used for the root user in the <tt class="filename">/etc/passwd</tt>. </p><p> The name of the account that is used to create domain member machine accounts can be anything the network administrator may choose. If it is other than <span class="emphasis"><em>root</em></span> then this is easily mapped to root using the file pointed to be the <tt class="filename">smb.conf</tt> parameter <a class="indexterm" name="id2873948"></a><i class="parameter"><tt>username map</tt></i> = /etc/samba/smbusers. </p><p> The session key of the Samba administrative account acts as an encryption key for setting the password of the machine trust account. The machine trust account will be created on-the-fly, or updated if it already exists. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2873973"></a>Windows NT4</h4></div></div><div></div></div><p> If the machine trust account was created manually, on the Identification Changes menu enter the domain name, but do not check the box <span class="guilabel">Create a Computer Account in the Domain</span>. In this case, the existing machine trust account is used to join the machine to the domain. </p><p> If the machine trust account is to be created on-the-fly, on the Identification Changes menu enter the domain name, and check the box <span class="guilabel">Create a Computer Account in the Domain</span>. In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when prompted). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2874013"></a>Samba</h4></div></div><div></div></div><p>Joining a Samba client to a domain is documented in <a href="#domain-member-server" title="Domain Member Server">the domain member chapter</a>. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domain-member-server"></a>Domain Member Server</h2></div></div><div></div></div><p> This mode of server operation involves the Samba machine being made a member of a domain security context. This means by definition that all user authentication will be done from a centrally defined authentication regime. The authentication regime may come from an NT3/4 style (old domain technology) server, or it may be provided from an Active Directory server (ADS) running on MS Windows 2000 or later. </p><p> <span class="emphasis"><em> Of course it should be clear that the authentication back end itself could be from any distributed directory architecture server that is supported by Samba. This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc. </em></span> </p><p> Please refer to <a href="#samba-pdc" title="Chapter�5.�Domain Control">the chapter on setting up a PDC</a> for more information regarding how to create a domain machine account for a domain member server as well as for information regarding how to enable the Samba domain member machine to join the domain and to be fully trusted by it. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874094"></a>Joining an NT4 type Domain with Samba-3</h3></div></div><div></div></div><p> </p><div class="table"><a name="id2874105"></a><p class="title"><b>Table�7.1.�Assumptions</b></p><table summary="Assumptions" border="1"><colgroup><col><col></colgroup><tbody><tr><td align="left">NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="left">Win2K/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="left">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="left">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div><p> </p><p> First, you must edit your <tt class="filename">smb.conf</tt> file to tell Samba it should now use domain security. </p><p> Change (or add) your <a class="indexterm" name="id2874178"></a><i class="parameter"><tt>security</tt></i> line in the [global] section of your <tt class="filename">smb.conf</tt> to read: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = domain</tt></i></td></tr></table><p> </p><p> Next change the <a class="indexterm" name="id2874222"></a><i class="parameter"><tt>workgroup</tt></i> line in the <i class="parameter"><tt>[global]</tt></i> section to read: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr></table><p> </p><p> as this is the name of the domain we are joining. </p><p> You must also have the parameter <a class="indexterm" name="id2874272"></a><i class="parameter"><tt>encrypt passwords</tt></i> set to <tt class="constant">yes </tt> in order for your users to authenticate to the NT PDC. </p><p> Finally, add (or modify) a <a class="indexterm" name="id2874295"></a><i class="parameter"><tt>password server</tt></i> line in the [global] section to read: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password server = DOMPDC DOMBDC1 DOMBDC2</tt></i></td></tr></table><p> </p><p> These are the primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load among domain controllers. </p><p> Alternatively, if you want smbd to automatically determine the list of Domain controllers to use for authentication, you may set this line to be: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>password server = *</tt></i></td></tr></table><p> </p><p> This method allows Samba to use exactly the same mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against. </p><p> In order to actually join the domain, you must run this command: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net rpc join -S DOMPDC -U<i class="replaceable"><tt>Administrator%password</tt></i></tt></b> </pre><p> </p><p> If the <tt class="option">-S DOMPDC</tt> argument is not given then the domain name will be obtained from <tt class="filename">smb.conf</tt>. </p><p> As we are joining the domain DOM and the PDC for that domain (the only machine that has write access to the domain SAM database) is DOMPDC, we use it for the <tt class="option">-S</tt> option. The <i class="replaceable"><tt>Administrator%password</tt></i> is the login name and password for an account which has the necessary privilege to add machines to the domain. If this is successful you will see the message: </p><p> <tt class="computeroutput">Joined domain DOM.</tt> or <tt class="computeroutput">Joined 'SERV1' to realm 'MYREALM'</tt> </p><p> in your terminal window. See the <b class="command">net</b> man page for more details. </p><p> This process joins the server to the domain without having to create the machine trust account on the PDC beforehand. </p><p> This command goes through the machine account password change protocol, then writes the new (random) machine account password for this Samba server into a file in the same directory in which an smbpasswd file would be stored - normally: </p><p> <tt class="filename">/usr/local/samba/private/secrets.tdb</tt> </p><p> This file is created and owned by root and is not readable by any other user. It is the key to the domain-level security for your system, and should be treated as carefully as a shadow password file. </p><p> Finally, restart your Samba daemons and get ready for clients to begin using domain security! The way you can restart your samba daemons depends on your distribution, but in most cases running </p><pre class="screen"> <tt class="prompt">root# </tt>/etc/init.d/samba restart </pre><p> does the job. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874530"></a>Why is this better than security = server?</h3></div></div><div></div></div><p> Currently, domain security in Samba doesn't free you from having to create local UNIX users to represent the users attaching to your server. This means that if domain user <tt class="constant">DOM\fred </tt> attaches to your domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX filesystem. This is very similar to the older Samba security mode security = server, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would. </p><p> Please refer to <a href="#winbind" title="Chapter�21.�Winbind: Use of Domain Accounts">the chapter on winbind</a> for information on a system to automatically assign UNIX uids and gids to Windows NT Domain users and groups. </p><p> The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource domain PDC to an account domain PDC). </p><p> In addition, with <a class="indexterm" name="id2874587"></a><i class="parameter"><tt>security</tt></i> = server every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run out of available connections. With <a class="indexterm" name="id2874605"></a><i class="parameter"><tt>security</tt></i> = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. </p><p> And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such as the user SID, the list of NT groups the user belongs to, etc. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Much of the text of this document was first published in the Web magazine <a href="http://www.linuxworld.com" target="_top">LinuxWorld</a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">Doing the NIS/NT Samba</a>. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ads-member"></a>Samba ADS Domain Membership</h2></div></div><div></div></div><a class="indexterm" name="id2874673"></a><a class="indexterm" name="id2874648"></a><a class="indexterm" name="id2874692"></a><a class="indexterm" name="id2874700"></a><p> This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a Windows2000 KDC. A familiarity with Kerberos is assumed. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874715"></a>Setup your <tt class="filename">smb.conf</tt></h3></div></div><div></div></div><p> You must use at least the following 3 options in <tt class="filename">smb.conf</tt>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>realm = your.kerberos.REALM</tt></i></td></tr><tr><td><i class="parameter"><tt>security = ADS</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr></table><p> In case samba can't figure out your ads server using your realm name, use the <a class="indexterm" name="id2874775"></a><i class="parameter"><tt>ads server</tt></i> option in <tt class="filename">smb.conf</tt>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>ads server = your.kerberos.server</tt></i></td></tr></table><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> You do <span class="emphasis"><em>not</em></span> need a smbpasswd file, and older clients will be authenticated as if <a class="indexterm" name="id2874822"></a><i class="parameter"><tt>security</tt></i> = domain, although it won't do any harm and allows you to have local users not in the domain. It is expected that the above required options will change soon when active directory integration will get better. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2874844"></a>Setup your <tt class="filename">/etc/krb5.conf</tt></h3></div></div><div></div></div><p> The minimal configuration for <tt class="filename">krb5.conf</tt> is: </p><pre class="programlisting"> [libdefaults] default_realm = YOUR.KERBEROS.REALM [realms] YOUR.KERBEROS.REALM = { kdc = your.kerberos.server } </pre><a class="indexterm" name="id2874880"></a><p> Test your config by doing a <b class="userinput"><tt>kinit <i class="replaceable"><tt>USERNAME</tt></i>@<i class="replaceable"><tt>REALM</tt></i></tt></b> and making sure that your password is accepted by the Win2000 KDC. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The realm must be uppercase or you will get <span class="errorname">Cannot find KDC for requested realm while getting initial credentials</span> error (Kerberos is case-sensitive!). </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Time between the two servers must be synchronized. You will get a <span class="errorname">kinit(v5): Clock skew too great while getting initial credentials</span> if the time difference is more than five minutes. </p></div><p> You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that this reverse lookup maps to must either be the NetBIOS name of the KDC (ie. the hostname with no domain attached) or it can alternatively be the NetBIOS name followed by the realm. </p><p> The easiest way to ensure you get this right is to add a <tt class="filename">/etc/hosts</tt> entry mapping the IP address of your KDC to its NetBIOS name. If you don't get this right then you will get a <span class="errorname">local error</span> when you try to join the realm. </p><p> If all you want is Kerberos support in <span class="application">smbclient</span> then you can skip straight to <a href="#ads-test-smbclient" title="Testing with smbclient">Test with <span class="application">smbclient</span></a> now. <a href="#ads-create-machine-account" title="Create the computer account">Creating a computer account</a> and <a href="#ads-test-server" title="Test your server setup">testing your servers</a> is only needed if you want Kerberos support for <span class="application">smbd</span> and <span class="application">winbindd</span>. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-create-machine-account"></a>Create the computer account</h3></div></div><div></div></div><p> As a user that has write permission on the Samba private directory (usually root) run: </p><pre class="screen"> <tt class="prompt">root# </tt> <b class="userinput"><tt>net ads join -U Administrator%password</tt></b> </pre><p> </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2875062"></a>Possible errors</h4></div></div><div></div></div><p> </p><div class="variablelist"><dl><dt><span class="term"><span class="errorname">ADS support not compiled in</span></span></dt><dd><p>Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the Kerberos libs and headers are installed. </p></dd><dt><span class="term"><span class="errorname">net ads join prompts for user name</span></span></dt><dd><p>You need to login to the domain using <b class="userinput"><tt>kinit <i class="replaceable"><tt>USERNAME</tt></i>@<i class="replaceable"><tt>REALM</tt></i></tt></b>. <i class="replaceable"><tt>USERNAME</tt></i> must be a user who has rights to add a machine to the domain. </p></dd></dl></div><p> </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-server"></a>Test your server setup</h3></div></div><div></div></div><p> If the join was successful, you will see a new computer account with the NetBIOS name of your Samba server in Active Directory (in the "Computers" folder under Users and Computers. </p><p> On a Windows 2000 client try <b class="userinput"><tt>net use * \\server\share</tt></b>. You should be logged in with Kerberos without needing to know a password. If this fails then run <b class="userinput"><tt>klist tickets</tt></b>. Did you get a ticket for the server? Does it have an encoding type of DES-CBC-MD5 ? </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-smbclient"></a>Testing with <span class="application">smbclient</span></h3></div></div><div></div></div><a class="indexterm" name="id2875189"></a><p> On your Samba server try to login to a Win2000 server or your Samba server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but specify the <tt class="option">-k</tt> option to choose Kerberos authentication. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875221"></a>Notes</h3></div></div><div></div></div><p> You must change administrator password at least once after DC install, to create the right encoding types </p><p> W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in their defaults DNS setup. Maybe this will be fixed later in service packs. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875243"></a>Common Errors</h2></div></div><div></div></div><p> In the process of adding / deleting / re-adding domain member machine accounts there are many traps for the unwary player and there are many “<span class="quote">little</span>” things that can go wrong. It is particularly interesting how often subscribers on the samba mailing list have concluded after repeated failed attempts to add a machine account that it is necessary to "re-install" MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type of problem. The real solution is often very simple, and with understanding of how MS Windows networking functions easy to overcome. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875286"></a>Can Not Add Machine Back to Domain</h3></div></div><div></div></div><p> “<span class="quote"> A Windows workstation was reinstalled. The original domain machine account was deleted and added immediately. The workstation will not join the domain if I use the same machine name. Attempts to add the machine fail with a message that the machine already exists on the network - I know it doesn't. Why is this failing?</span>” </p><p> The original name is still in the NetBIOS name cache and must expire after machine account deletion BEFORE adding that same name as a domain member again. The best advice is to delete the old account and then to add the machine with a new name. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875318"></a>Adding Machine to Domain Fails</h3></div></div><div></div></div><p> “<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a message that, <span class="errorname">The machine could not be added at this time, there is a network problem. Please try again later.</span> Why?</span>” </p><p> You should check that there is an <a class="indexterm" name="id2875345"></a><i class="parameter"><tt>add machine script</tt></i> in your <tt class="filename">smb.conf</tt> file. If there is not, please add one that is appropriate for your OS platform. If a script has been defined you will need to debug it's operation. Increase the <a class="indexterm" name="id2875370"></a><i class="parameter"><tt>log level</tt></i> in the <tt class="filename">smb.conf</tt> file to level 10, then try to rejoin the domain. Check the logs to see which operation is failing. </p><p> Possible causes include: </p><div class="itemizedlist"><ul type="disc"><li><p> The script does not actually exist, or could not be located in the path specified. </p><p> <span class="emphasis"><em>Corrective Action:</em></span> Fix it. Make sure that when run manually that the script will add both the UNIX system account _and_ the Samba SAM account. </p></li><li><p> The machine could not be added to the UNIX system accounts file <tt class="filename">/etc/passwd</tt> </p><p> <span class="emphasis"><em>Corrective Action:</em></span> Check that the machine name is a legal UNIX system account name. ie: If the UNIX utility <b class="command">useradd</b> is called then make sure that the machine name you are trying to add can be added using this tool. <b class="command">Useradd</b> on some systems will not allow any upper case characters nor will it allow spaces in the name. </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2875462"></a>I can't join a Windows 2003 PDC</h3></div></div><div></div></div><p>Windows 2003 requires SMB signing. Client side SMB signing has only been implemented partially in Samba 3.0. Set <a class="indexterm" name="id2875474"></a><i class="parameter"><tt>client use spnego</tt></i> = no when communicating with a windows 2003 server. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="StandAloneServer"></a>Chapter�8.�Stand-Alone Servers</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2875549">Features and Benefits</a></dt><dt><a href="#id2875587">Background</a></dt><dt><a href="#id2875661">Example Configuration</a></dt><dd><dl><dt><a href="#RefDocServer">Reference Documentation Server</a></dt><dt><a href="#SimplePrintServer">Central Print Serving</a></dt></dl></dd><dt><a href="#id2876184">Common Errors</a></dt></dl></div><p> Stand-Alone servers are independent of Domain Controllers on the network. They are NOT domain members and function more like workgroup servers. In many cases a stand-alone server is configured with a minimum of security control with the intent that all data served will be readily accessible to all users. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875549"></a>Features and Benefits</h2></div></div><div></div></div><p> Stand-Alone servers can be as secure or as insecure as needs dictate. They can have simple or complex configurations. Above all, despite the hoopla about Domain security they remain a very common installation. </p><p> If all that is needed is a server for read-only files, or for printers alone, it may not make sense to affect a complex installation. For example: A drafting office needs to store old drawings and reference standards. No-one can write files to the server as it is legislatively important that all documents remain unaltered. A share mode read-only stand-alone server is an ideal solution. </p><p> Another situation that warrants simplicity is an office that has many printers that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to affect any access controls and no files will be served from the print server. Again a share mode stand-alone server makes a great solution. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875587"></a>Background</h2></div></div><div></div></div><p> The term <span class="emphasis"><em>stand-alone server</em></span> means that the server will provide local authentication and access control for all resources that are available from it. In general this means that there will be a local user database. In more technical terms, it means that resources on the machine will be made available in either SHARE mode or in USER mode. </p><p> No special action is needed other than to create user accounts. Stand-alone servers do NOT provide network logon services. This means that machines that use this server do NOT perform a domain logon to it. Whatever logon facility the workstations are subject to is independent of this machine. It is however necessary to accommodate any network user so that the logon name they use will be translated (mapped) locally on the stand-alone server to a locally known user name. There are several ways this can be done. </p><p> Samba tends to blur the distinction a little in respect of what is a stand-alone server. This is because the authentication database may be local or on a remote server, even if from the Samba protocol perspective the Samba server is NOT a member of a domain security context. </p><p> Through the use of PAM (Pluggable Authentication Modules) and nsswitch (the name service switcher, which maintains the unix user database) the source of authentication may reside on another server. We would be inclined to call this the authentication server. This means that the Samba server may use the local UNIX/Linux system password database (<tt class="filename">/etc/passwd</tt> or <tt class="filename">/etc/shadow</tt>), may use a local smbpasswd file, or may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB server for authentication. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2875661"></a>Example Configuration</h2></div></div><div></div></div><p> The following examples are designed to inspire simplicity. It is too easy to attempt a high level of creativity and to introduce too much complexity in server and network design. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="RefDocServer"></a>Reference Documentation Server</h3></div></div><div></div></div><p> Configuration of a read-only data server that EVERYONE can access is very simple. Here is the smb.conf file that will do this. Assume that all the reference documents are stored in the directory /export, that the documents are owned by a user other than nobody. No home directories are shared, that are no users in the <tt class="filename">/etc/passwd</tt> UNIX system database. This is a very simple system to administer. </p><div class="example"><a name="id2875707"></a><p class="title"><b>Example�8.1.�smb.conf for Reference Documentation Server</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = 192.168.1.1</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[data]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Data</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export</tt></i></td></tr><tr><td><i class="parameter"><tt>guest only = Yes</tt></i></td></tr></table></div><p> In the above example the machine name is set to REFDOCS, the workgroup is set to the name of the local workgroup so that the machine will appear in with systems users are familiar with. The only password backend required is the "guest" backend so as to allow default unprivileged account names to be used. Given that there is a WINS server on this network we do use it. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="SimplePrintServer"></a>Central Print Serving</h3></div></div><div></div></div><p> Configuration of a simple print server is very simple if you have all the right tools on your system. </p><div class="orderedlist"><p class="title"><b> Assumptions:</b></p><ol type="1"><li><p> The print server must require no administration </p></li><li><p> The print spooling and processing system on our print server will be CUPS. (Please refer to <a href="#CUPS-printing" title="Chapter�19.�CUPS Printing Support in Samba 3.0">the chapter about CUPS</a> for more information). </p></li><li><p> All printers that the print server will service will be network printers. They will be correctly configured, by the administrator, in the CUPS environment. </p></li><li><p> All workstations will be installed using postscript drivers. The printer of choice is the Apple Color LaserWriter. </p></li></ol></div><p> In this example our print server will spool all incoming print jobs to <tt class="filename">/var/spool/samba</tt> until the job is ready to be submitted by Samba to the CUPS print processor. Since all incoming connections will be as the anonymous (guest) user, two things will be required: </p><div class="itemizedlist"><p class="title"><b>Enabling Anonymous Printing</b></p><ul type="disc"><li><p> The UNIX/Linux system must have a <b class="command">guest</b> account. The default for this is usually the account <b class="command">nobody</b>. To find the correct name to use for your version of Samba do the following: </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>testparm -s -v | grep "guest account"</tt></b> </pre><p> Then make sure that this account exists in your system password database (<tt class="filename">/etc/passwd</tt>). </p></li><li><p> The directory into which Samba will spool the file must have write access for the guest account. The following commands will ensure that this directory is available for use: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>mkdir /var/spool/samba</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>chown nobody.nobody /var/spool/samba</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>chmod a+rwt /var/spool/samba</tt></b> </pre><p> </p></li></ul></div><p> </p><div class="example"><a name="id2876026"></a><p class="title"><b>Example�8.2.�smb.conf for anonymous printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = MIDEARTH</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>security = SHARE</tt></i></td></tr><tr><td><i class="parameter"><tt>passdb backend = guest</tt></i></td></tr><tr><td><i class="parameter"><tt>wins server = noldor</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = cups</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = cups</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = root</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>use client driver = Yes</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = No</tt></i></td></tr></table></div><p> </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876184"></a>Common Errors</h2></div></div><div></div></div><p> The greatest mistake so often made is to make a network configuration too complex. It pays to use the simplest solution that will meet the needs of the moment. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ClientConfig"></a>Chapter�9.�MS Windows Network Configuration Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2876248">Note</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876248"></a>Note</h2></div></div><div></div></div><p> This chapter did not make it into this release. It is planned for the published release of this document. </p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div></div></div><div class="partintro" lang="en"><div><div><div><h1 class="title"><a name="id2876276"></a>Valuable Nuts and Bolts Information</h1></div></div><div></div></div><p> Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. </p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>10. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2876401">Features and Benefits</a></dt><dt><a href="#id2876490">What is Browsing?</a></dt><dt><a href="#id2876803">Discussion</a></dt><dd><dl><dt><a href="#id2876818">NetBIOS over TCP/IP</a></dt><dt><a href="#id2877054">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2877219">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2877367">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877916">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2878314">Making Samba the domain master</a></dt><dt><a href="#id2878491">Note about broadcast addresses</a></dt><dt><a href="#id2878515">Multiple interfaces</a></dt><dt><a href="#id2878551">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878708">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878786">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878975">Setting up a WINS server</a></dt><dt><a href="#id2879231">WINS Replication</a></dt><dt><a href="#id2879256">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2879345">Helpful Hints</a></dt><dd><dl><dt><a href="#id2879358">Windows Networking Protocols</a></dt><dt><a href="#id2879437">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2879603">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879656">Browsing support in Samba</a></dt><dt><a href="#id2879778">Problem resolution</a></dt><dt><a href="#id2879866">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2880547">Common Errors</a></dt><dd><dl><dt><a href="#id2880562">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2880591">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880635">I get an Unable to browse the network error</a></dt></dl></dd></dl></dd><dt>11. <a href="#passdb">Account Information Databases</a></dt><dd><dl><dt><a href="#id2880915">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880929">Backwards Compatibility Backends</a></dt><dt><a href="#id2881032">New Backends</a></dt></dl></dd><dt><a href="#id2881219">Technical Information</a></dt><dd><dl><dt><a href="#id2881344">Important Notes About Security</a></dt><dt><a href="#id2881634">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881821">The smbpasswd Command</a></dt><dt><a href="#id2882092">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2882329">Password Backends</a></dt><dd><dl><dt><a href="#id2882371">Plain Text</a></dt><dt><a href="#id2882412">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2882525">tdbsam</a></dt><dt><a href="#id2882559">ldapsam</a></dt><dt><a href="#id2884412">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2885260">Common Errors</a></dt><dd><dl><dt><a href="#id2885267">Users can not logon</a></dt><dt><a href="#id2885312">Users being added to wrong backend database</a></dt><dt><a href="#id2885422">auth methods does not work</a></dt></dl></dd></dl></dd><dt>12. <a href="#groupmapping">Mapping MS Windows and UNIX Groups</a></dt><dd><dl><dt><a href="#id2885652">Features and Benefits</a></dt><dt><a href="#id2885887">Discussion</a></dt><dd><dl><dt><a href="#id2886122">Example Configuration</a></dt></dl></dd><dt><a href="#id2886189">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2886202">Sample smb.conf add group script</a></dt><dt><a href="#id2886288">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2886372">Common Errors</a></dt><dd><dl><dt><a href="#id2886386">Adding Groups Fails</a></dt><dt><a href="#id2886455">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2886481">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></dd><dt>13. <a href="#AccessControls">File, Directory and Share Access Controls</a></dt><dd><dl><dt><a href="#id2886736">Features and Benefits</a></dt><dt><a href="#id2886866">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886902">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2887207">Managing Directories</a></dt><dt><a href="#id2887301">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2887513">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2887541">User and Group Based Controls</a></dt><dt><a href="#id2887963">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2888342">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888722">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888794">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2889094">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2889102">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2889146">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2889226">Viewing file ownership</a></dt><dt><a href="#id2889358">Viewing File or Directory Permissions</a></dt><dt><a href="#id2889603">Modifying file or directory permissions</a></dt><dt><a href="#id2889768">Interaction with the standard Samba create mask parameters</a></dt><dt><a href="#id2890164">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2890260">Common Errors</a></dt><dd><dl><dt><a href="#id2890274">Users can not write to a public share</a></dt><dt><a href="#id2890703">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890755">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></dd><dt>14. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2891003">Features and Benefits</a></dt><dt><a href="#id2891060">Discussion</a></dt><dd><dl><dt><a href="#id2891204">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891921">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2892041">Example Configuration</a></dt></dl></dd><dt><a href="#id2892456">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2892680">Workstation Service Entries</a></dt><dt><a href="#id2892709">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892788">Persistent Data Corruption</a></dt><dt><a href="#id2892817">Common Errors</a></dt><dd><dl><dt><a href="#id2892891">locking.tdb error messages</a></dt><dt><a href="#id2892930">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892952">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892983">Additional Reading</a></dt></dl></dd><dt>15. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2893158">Introduction</a></dt><dt><a href="#id2893195">Features and Benefits</a></dt><dt><a href="#id2893269">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2893288">Using host based protection</a></dt><dt><a href="#id2893387">User based protection</a></dt><dt><a href="#id2893447">Using interface protection</a></dt><dt><a href="#id2893515">Using a firewall</a></dt><dt><a href="#id2893572">Using a IPC$ share deny</a></dt><dt><a href="#id2893660">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2893719">Upgrading Samba</a></dt><dt><a href="#id2893743">Common Errors</a></dt><dd><dl><dt><a href="#id2893761">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2893786">Why can users access home directories of other users?</a></dt></dl></dd></dl></dd><dt>16. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2894077">Features and Benefits</a></dt><dt><a href="#id2894106">Trust Relationship Background</a></dt><dt><a href="#id2894193">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2894221">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2894294">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2894341">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2894518">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2894704">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894842">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894948">Common Errors</a></dt></dl></dd><dt>17. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2895017">Features and Benefits</a></dt><dt><a href="#id2895292">Common Errors</a></dt></dl></dd><dt>18. <a href="#printing">Classical Printing Support</a></dt><dd><dl><dt><a href="#id2895411">Features and Benefits</a></dt><dt><a href="#id2895517">Technical Introduction</a></dt><dd><dl><dt><a href="#id2895555">What happens if you send a Job from a Client</a></dt><dt><a href="#id2895627">Printing Related Configuration Parameters</a></dt><dt><a href="#id2895722">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2896188">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2896354">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2896481">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2896843">Extended Sample Configuration to Print</a></dt><dt><a href="#id2897173">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2897186">The [global] Section</a></dt><dt><a href="#id2897717">The [printers] Section</a></dt><dt><a href="#id2898177">Any [my_printer_name] Section</a></dt><dt><a href="#id2898498">Print Commands</a></dt><dt><a href="#id2898580">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2899263">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2899603">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2899763">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2899925">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2900037">Creating the [print$] Share</a></dt><dt><a href="#id2900227">Parameters in the [print$] Section</a></dt><dt><a href="#id2900537">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2900710">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2900805">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2901002">Setting Drivers for existing Printers with rpcclient</a></dt></dl></dd><dt><a href="#id2902712">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2902731">The first Client Driver Installation</a></dt><dt><a href="#id2902934">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2903234">Further Client Driver Install Procedures</a></dt><dt><a href="#id2903328">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2903500">Other Gotchas</a></dt><dd><dl><dt><a href="#id2903534">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2904001">Supporting large Numbers of Printers</a></dt><dt><a href="#id2904312">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2904606">Weird Error Message Cannot connect under a different Name</a></dt><dt><a href="#id2904706">Be careful when assembling Driver Files</a></dt><dt><a href="#id2905065">Samba and Printer Ports</a></dt><dt><a href="#id2905158">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2905183">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2905239">What is Imprints?</a></dt><dt><a href="#id2905280">Creating Printer Driver Packages</a></dt><dt><a href="#id2905299">The Imprints Server</a></dt><dt><a href="#id2905323">The Installation Client</a></dt></dl></dd><dt><a href="#id2905478">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2905813">The addprinter command</a></dt><dt><a href="#id2905859">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2906032">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2906044">Common Errors</a></dt><dd><dl><dt><a href="#id2906050">I give my root password but I don't get access</a></dt><dt><a href="#id2906085">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></dd><dt>19. <a href="#CUPS-printing">CUPS Printing Support in Samba 3.0</a></dt><dd><dl><dt><a href="#id2906220">Introduction</a></dt><dd><dl><dt><a href="#id2906227">Features and Benefits</a></dt><dt><a href="#id2906281">Overview</a></dt></dl></dd><dt><a href="#id2906348">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="#id2906443">Linking of smbd with libcups.so</a></dt><dt><a href="#id2906684">Simple smb.conf Settings for CUPS</a></dt><dt><a href="#id2906866">More complex smb.conf Settings for CUPS</a></dt></dl></dd><dt><a href="#id2907221">Advanced Configuration</a></dt><dd><dl><dt><a href="#id2907241">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="#id2907296">CUPS/Samba as a "spooling-only" Print Server; "raw" printing with Vendor Drivers on Windows Clients</a></dt><dt><a href="#id2907365">Driver Installation Methods on Windows Clients</a></dt><dt><a href="#id2907441">Explicitly enable "raw" printing for application/octet-stream!</a></dt><dt><a href="#id2907647">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="#id2907785">Using CUPS/Samba in an advanced Way -- intelligent printing with PostScript Driver Download</a></dt><dd><dl><dt><a href="#gdipost">GDI on Windows -- PostScript on UNIX</a></dt><dt><a href="#id2907968">Windows Drivers, GDI and EMF</a></dt><dt><a href="#id2908120">UNIX Printfile Conversion and GUI Basics</a></dt><dt><a href="#post-and-ghost">PostScript and Ghostscript</a></dt><dt><a href="#id2908420">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="#id2908563">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="#id2908649">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="#id2908755">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="#id2908777">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="#id2908970">MIME types and CUPS Filters</a></dt><dt><a href="#id2909178">MIME type Conversion Rules</a></dt><dt><a href="#id2909333">Filter Requirements</a></dt><dt><a href="#id2909513">Prefilters</a></dt><dt><a href="#id2909624">pstops</a></dt><dt><a href="#id2909734">pstoraster</a></dt><dt><a href="#id2909928">imagetops and imagetoraster</a></dt><dt><a href="#id2909993">rasterto [printers specific]</a></dt><dt><a href="#id2910145">CUPS Backends</a></dt><dt><a href="#id2910493">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="#id2910637">The Complete Picture</a></dt><dt><a href="#id2910653">mime.convs</a></dt><dt><a href="#id2910716">"Raw" printing</a></dt><dt><a href="#id2910805">"application/octet-stream" printing</a></dt><dt><a href="#id2911052">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="#id2911319">Difference between cupsomatic/foomatic-rip and native CUPS printing</a></dt><dt><a href="#id2911554">Examples for filtering Chains</a></dt><dt><a href="#id2911891">Sources of CUPS drivers / PPDs</a></dt><dt><a href="#id2912041">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="#id2912139">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="#id2912150">From Windows Clients to an NT Print Server</a></dt><dt><a href="#id2912212">Driver Execution on the Client</a></dt><dt><a href="#id2912287">Driver Execution on the Server</a></dt></dl></dd><dt><a href="#id2912407">Network Printing (Windows clients -- UNIX/Samba Print Servers)</a></dt><dd><dl><dt><a href="#id2912426">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="#id2912640">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="#id2912726">Network PostScript RIP: CUPS Filters on Server -- clients use PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="#id2912815">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="#id2912871">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="#id2912948">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="#id2912964">Printer Drivers running in "Kernel Mode" cause many Problems</a></dt><dt><a href="#id2913011">Workarounds impose Heavy Limitations</a></dt><dt><a href="#id2913032">CUPS: a "Magical Stone"?</a></dt><dt><a href="#id2913085">PostScript Drivers with no major problems -- even in Kernel Mode</a></dt></dl></dd><dt><a href="#id2913108">Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="#id2913163">cupsaddsmb: the unknown Utility</a></dt><dt><a href="#id2913282">Prepare your smb.conf for cupsaddsmb</a></dt><dt><a href="#id2913502">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2913789">Recognize the different Driver Files</a></dt><dt><a href="#id2913932">Acquiring the Adobe Driver Files</a></dt><dt><a href="#id2913965">ESP Print Pro Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="#id2914035">Caveats to be considered</a></dt><dt><a href="#id2914308">Benefits of using "CUPS PostScript Driver for Windows NT/2k/XP" instead of Adobe Driver</a></dt><dt><a href="#id2914525">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="#id2914652">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="#id2914873">Understanding cupsaddsmb</a></dt><dt><a href="#id2915022">How to recognize if cupsaddsmb completed successfully</a></dt><dt><a href="#id2915105">cupsaddsmb with a Samba PDC</a></dt><dt><a href="#id2915185">cupsaddsmb Flowchart</a></dt><dt><a href="#id2915261">Installing the PostScript Driver on a Client</a></dt><dt><a href="#id2915425">Avoiding critical PostScript Driver Settings on the Client</a></dt></dl></dd><dt><a href="#id2915559">Installing PostScript Driver Files manually (using rpcclient)</a></dt><dd><dl><dt><a href="#id2915762">A Check of the rpcclient man Page</a></dt><dt><a href="#id2915876">Understanding the rpcclient man page</a></dt><dt><a href="#id2915981">Producing an Example by querying a Windows Box</a></dt><dt><a href="#id2916147">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="#id2916361">Manual Driver Installation in 15 Steps</a></dt><dt><a href="#id2917432">Troubleshooting revisited</a></dt></dl></dd><dt><a href="#id2917593">The printing *.tdb Files</a></dt><dd><dl><dt><a href="#id2917838">Trivial DataBase Files</a></dt><dt><a href="#id2917930">Binary Format</a></dt><dt><a href="#id2917994">Losing *.tdb Files</a></dt><dt><a href="#id2918053">Using tdbbackup</a></dt></dl></dd><dt><a href="#id2918189">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="#id2918345">foomatic-rip and Foomatic explained</a></dt><dt><a href="#id2919115">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="#id2919616">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="#id2919667">Setting up Quotas</a></dt><dt><a href="#id2919734">Correct and incorrect Accounting</a></dt><dt><a href="#id2919778">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="#id2919874">The page_log File Syntax</a></dt><dt><a href="#id2919991">Possible Shortcomings</a></dt><dt><a href="#id2920067">Future Developments</a></dt><dt><a href="#id2920123">Other Accounting Tools</a></dt></dl></dd><dt><a href="#id2920136">Additional Material</a></dt><dt><a href="#id2920387">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="#id2920450">CUPS Configuration Settings explained</a></dt><dt><a href="#id2920543">Pre-conditions</a></dt><dt><a href="#id2920702">Manual Configuration</a></dt></dl></dd><dt><a href="#id2920760">In Case of Trouble.....</a></dt><dt><a href="#id2920832">Printing from CUPS to Windows attached Printers</a></dt><dt><a href="#id2921130">More CUPS filtering Chains</a></dt><dt><a href="#id2921233">Common Errors</a></dt><dd><dl><dt><a href="#id2921241">Win9x client can't install driver</a></dt><dt><a href="#id2921263">"cupsaddsmb" keeps asking for root password in neverending loop</a></dt><dt><a href="#id2921311">"cupsaddsmb" gives "No PPD file for printer..." message while PPD file is present</a></dt><dt><a href="#id2921368">Client can't connect to Samba printer</a></dt><dt><a href="#id2921397">Can't reconnect to Samba under new account from Win2K/XP</a></dt><dt><a href="#id2921624">Avoid being connected to the Samba server as the "wrong" user</a></dt><dt><a href="#id2921678">Upgrading to CUPS drivers from Adobe drivers on NT/2K/XP clients gives problems</a></dt><dt><a href="#id2921695">Can't use "cupsaddsmb" on Samba server which is a PDC</a></dt><dt><a href="#id2921726">Deleted Win2K printer driver is still shown</a></dt><dt><a href="#id2921734">Win2K/XP "Local Security Policies"</a></dt><dt><a href="#id2921774">WinXP clients: "Administrator can not install printers for all local users"</a></dt><dt><a href="#id2921808">"Print Change Notify" functions on NT-clients</a></dt><dt><a href="#id2921830">WinXP-SP1</a></dt><dt><a href="#id2921875">Print options for all users can't be set on Win2K/XP</a></dt><dt><a href="#id2922164">Most common blunders in driver settings on Windows clients</a></dt><dt><a href="#id2922210">cupsaddsmb does not work with newly installed printer</a></dt><dt><a href="#id2922272">Permissions on /var/spool/samba/ get reset after each reboot</a></dt><dt><a href="#id2922380">Printer named "lp" intermittently swallows jobs and spits out completely different ones</a></dt><dt><a href="#id2922428">Location of Adobe PostScript driver files necessary for "cupsaddsmb"</a></dt></dl></dd><dt><a href="#id2922484">An Overview of the CUPS Printing Processes</a></dt></dl></dd><dt>20. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2922653">Features and Benefits</a></dt><dt><a href="#id2922671">Discussion</a></dt><dt><a href="#id2922900">Included modules</a></dt><dd><dl><dt><a href="#id2922907">audit</a></dt><dt><a href="#id2922950">extd_audit</a></dt><dt><a href="#id2923080">fake_perms</a></dt><dt><a href="#id2923099">recycle</a></dt><dt><a href="#id2923274">netatalk</a></dt></dl></dd><dt><a href="#id2923320">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2923342">DatabaseFS</a></dt><dt><a href="#id2923396">vscan</a></dt></dl></dd></dl></dd><dt>21. <a href="#winbind">Winbind: Use of Domain Accounts</a></dt><dd><dl><dt><a href="#id2923626">Features and Benefits</a></dt><dt><a href="#id2923721">Introduction</a></dt><dt><a href="#id2923799">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2923876">Target Uses</a></dt></dl></dd><dt><a href="#id2923906">How Winbind Works</a></dt><dd><dl><dt><a href="#id2923935">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2923968">Microsoft Active Directory Services</a></dt><dt><a href="#id2923991">Name Service Switch</a></dt><dt><a href="#id2924127">Pluggable Authentication Modules</a></dt><dt><a href="#id2924199">User and Group ID Allocation</a></dt><dt><a href="#id2924232">Result Caching</a></dt></dl></dd><dt><a href="#id2924260">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2924268">Introduction</a></dt><dt><a href="#id2924335">Requirements</a></dt><dt><a href="#id2924429">Testing Things Out</a></dt></dl></dd><dt><a href="#id2926036">Conclusion</a></dt><dt><a href="#id2926054">Common Errors</a></dt><dd><dl><dt><a href="#id2926108">NSCD Problem Warning</a></dt></dl></dd></dl></dd><dt>22. <a href="#AdvancedNetworkManagement">Advanced Network Management</a></dt><dd><dl><dt><a href="#id2926216">Features and Benefits</a></dt><dt><a href="#id2926247">Remote Server Administration</a></dt><dt><a href="#id2926346">Remote Desktop Management</a></dt><dd><dl><dt><a href="#id2926363">Remote Management from NoMachines.Com</a></dt></dl></dd><dt><a href="#id2926605">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2926843">Adding printers without user intervention</a></dt></dl></dd><dt><a href="#id2926877">Common Errors</a></dt></dl></dd><dt>23. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2926955">Features and Benefits</a></dt><dt><a href="#id2927014">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2927128">Windows 9x/Me Policies</a></dt><dt><a href="#id2927223">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2927356">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2927608">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2927714">Samba Editreg Toolset</a></dt><dt><a href="#id2927753">Windows NT4/200x</a></dt><dt><a href="#id2927776">Samba PDC</a></dt></dl></dd><dt><a href="#id2927822">System Startup and Logon Processing Overview</a></dt><dt><a href="#id2927973">Common Errors</a></dt><dd><dl><dt><a href="#id2927986">Policy Does Not Work</a></dt></dl></dd></dl></dd><dt>24. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2928087">Features and Benefits</a></dt><dt><a href="#id2928120">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2928161">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2928652">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2929902">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2929987">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2930246">Mandatory profiles</a></dt><dt><a href="#id2930304">Creating/Managing Group Profiles</a></dt><dt><a href="#id2930349">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2930369">MS Windows 9x/Me</a></dt><dt><a href="#id2930521">MS Windows NT4 Workstation</a></dt><dt><a href="#id2931076">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="#id2931594">Common Errors</a></dt><dd><dl><dt><a href="#id2931607">Setting up roaming profiles for just a few user's or group's?</a></dt><dt><a href="#id2931676">Can NOT use Roaming Profiles</a></dt><dt><a href="#id2931889">Changing the default profile</a></dt></dl></dd></dl></dd><dt>25. <a href="#pam">PAM based Distributed Authentication</a></dt><dd><dl><dt><a href="#id2932170">Features and Benefits</a></dt><dt><a href="#id2932418">Technical Discussion</a></dt><dd><dl><dt><a href="#id2932435">PAM Configuration Syntax</a></dt><dt><a href="#id2933099">Example System Configurations</a></dt><dt><a href="#id2933403">smb.conf PAM Configuration</a></dt><dt><a href="#id2933482">Remote CIFS Authentication using winbindd.so</a></dt><dt><a href="#id2933565">Password Synchronization using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2933949">Common Errors</a></dt><dd><dl><dt><a href="#id2933962">pam_winbind problem</a></dt><dt><a href="#id2934050">Winbind is not resolving users and groups</a></dt></dl></dd></dl></dd><dt>26. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2934288">Features and Benefits</a></dt><dt><a href="#id2934312">Background Information</a></dt><dt><a href="#id2934378">Name Resolution in a pure UNIX/Linux world</a></dt><dd><dl><dt><a href="#id2934434">/etc/hosts</a></dt><dt><a href="#id2934584">/etc/resolv.conf</a></dt><dt><a href="#id2934626">/etc/host.conf</a></dt><dt><a href="#id2934679">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2934793">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2935103">The NetBIOS Name Cache</a></dt><dt><a href="#id2935167">The LMHOSTS file</a></dt><dt><a href="#id2935329">HOSTS file</a></dt><dt><a href="#id2935361">DNS Lookup</a></dt><dt><a href="#id2935393">WINS Lookup</a></dt></dl></dd><dt><a href="#id2935511">Common Errors</a></dt><dd><dl><dt><a href="#id2935527">Pinging works only in one way</a></dt><dt><a href="#id2935562">Very Slow Network Connections</a></dt><dt><a href="#id2935612">Samba server name change problem</a></dt></dl></dd></dl></dd><dt>27. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2935816">Features and Benefits</a></dt><dt><a href="#id2935861">What are charsets and unicode?</a></dt><dt><a href="#id2935930">Samba and charsets</a></dt><dt><a href="#id2936058">Conversion from old names</a></dt><dt><a href="#id2936088">Japanese charsets</a></dt><dt><a href="#id2936225">Common errors</a></dt><dd><dl><dt><a href="#id2936232">CP850.so can't be found</a></dt></dl></dd></dl></dd><dt>28. <a href="#Backup">Samba Backup Techniques</a></dt><dd><dl><dt><a href="#id2936346">Note</a></dt><dt><a href="#id2936359">Features and Benefits</a></dt></dl></dd><dt>29. <a href="#SambaHA">High Availability Options</a></dt><dd><dl><dt><a href="#id2936430">Note</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter�10.�Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2876401">Features and Benefits</a></dt><dt><a href="#id2876490">What is Browsing?</a></dt><dt><a href="#id2876803">Discussion</a></dt><dd><dl><dt><a href="#id2876818">NetBIOS over TCP/IP</a></dt><dt><a href="#id2877054">TCP/IP - without NetBIOS</a></dt><dt><a href="#id2877219">DNS and Active Directory</a></dt></dl></dd><dt><a href="#id2877367">How Browsing Functions</a></dt><dd><dl><dt><a href="#DMB">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2877916">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing Samba to be the master</a></dt><dt><a href="#id2878314">Making Samba the domain master</a></dt><dt><a href="#id2878491">Note about broadcast addresses</a></dt><dt><a href="#id2878515">Multiple interfaces</a></dt><dt><a href="#id2878551">Use of the Remote Announce parameter</a></dt><dt><a href="#id2878708">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2878786">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2878975">Setting up a WINS server</a></dt><dt><a href="#id2879231">WINS Replication</a></dt><dt><a href="#id2879256">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2879345">Helpful Hints</a></dt><dd><dl><dt><a href="#id2879358">Windows Networking Protocols</a></dt><dt><a href="#id2879437">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2879603">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2879656">Browsing support in Samba</a></dt><dt><a href="#id2879778">Problem resolution</a></dt><dt><a href="#id2879866">Browsing across subnets</a></dt></dl></dd><dt><a href="#id2880547">Common Errors</a></dt><dd><dl><dt><a href="#id2880562">How can one flush the Samba NetBIOS name cache without restarting Samba?</a></dt><dt><a href="#id2880591">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="#id2880635">I get an Unable to browse the network error</a></dt></dl></dd></dl></div><p> This document contains detailed information as well as a fast track guide to implementing browsing across subnets and / or across workgroups (or domains). WINS is the best tool for resolution of NetBIOS names to IP addresses. WINS is 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><div><h2 class="title" style="clear: both"><a name="id2876401"></a>Features and Benefits</h2></div></div><div></div></div><p> Someone once referred to the past in terms of: <span class="emphasis"><em>They were the worst of times, they were the best of times. The more we look back, them more we long for what was and hope it never returns!</em></span>. </p><a class="indexterm" name="id2876422"></a><p> For many MS Windows network administrators, that statement sums up their feelings about NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle nature was just par for the course. For those who never quite managed to tame its lusty features, NetBIOS is like Paterson's Curse. </p><p> For those not familiar with botanical problems in Australia: Paterson's curse, Echium plantagineum, was introduced to Australia from Europe during the mid-nineteenth century. Since then it has spread rapidly. The high seed production, with densities of thousands of seeds per square metre, a seed longevity of more than seven years, and an ability to germinate at any time of year, given the right conditions, are some of the features which make it such a persistent weed. </p><p> In this chapter we explore vital aspects of SMB (Server Message Block) networking with a particular focus on SMB as implemented through running NetBIOS (Network Basic Input / Output System) over TCP/IP. Since Samba does NOT implement SMB or NetBIOS over any other protocols we need to know how to configure our network environment and simply remember to use nothing but TCP/IP on all our MS Windows network clients. </p><p> Samba provides the ability to implement a WINS (Windows Internetworking Name Server) and implements extensions to Microsoft's implementation of WINS. These extensions help Samba to affect stable WINS operations beyond the normal scope of MS WINS. </p><p> Please note that WINS is exclusively a service that applies only to those systems that run NetBIOS over TCP/IP. MS Windows 200x / XP have the capacity to turn off support for NetBIOS, in which case WINS is of no relevance. Samba supports this also. </p><p> For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) the use of DNS is necessary for host name resolution. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876490"></a>What is Browsing?</h2></div></div><div></div></div><p> To most people browsing means that they can see the MS Windows and Samba servers in the Network Neighborhood, and when the computer icon for a particular server is clicked, it opens up and shows the shares and printers available on the target server. </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><div class="itemizedlist"><ul type="disc"><li><p>MS Windows machines register their presence to the network</p></li><li><p>Machines announce themselves to other machines on the network</p></li><li><p>One or more machine on the network collates the local announcements</p></li><li><p>The client machine finds the machine that has the collated list of machines</p></li><li><p>The client machine is able to resolve the machine names to IP addresses</p></li><li><p>The client machine is able to connect to a target machine</p></li></ul></div><p> The Samba application that controls browse list management and name resolution is called <tt class="filename">nmbd</tt>. The configuration parameters involved in nmbd's operation are: </p><p>Browsing options: <a class="indexterm" name="id2876574"></a><i class="parameter"><tt>os level</tt></i>(*), <a class="indexterm" name="id2876588"></a><i class="parameter"><tt>lm announce</tt></i>, <a class="indexterm" name="id2876602"></a><i class="parameter"><tt>lm interval</tt></i>, <a class="indexterm" name="id2876615"></a><i class="parameter"><tt>preferred master</tt></i>(*), <a class="indexterm" name="id2876630"></a><i class="parameter"><tt>local master</tt></i>(*), <a class="indexterm" name="id2876644"></a><i class="parameter"><tt>domain master</tt></i>(*), <a class="indexterm" name="id2876658"></a><i class="parameter"><tt>browse list</tt></i>, <a class="indexterm" name="id2876671"></a><i class="parameter"><tt>enhanced browsing</tt></i>. </p><p>Name Resolution Method: <a class="indexterm" name="id2876689"></a><i class="parameter"><tt>name resolve order</tt></i>(*). </p><p>WINS options: <a class="indexterm" name="id2876708"></a><i class="parameter"><tt>dns proxy</tt></i>, <a class="indexterm" name="id2876721"></a><i class="parameter"><tt>wins proxy</tt></i>, <a class="indexterm" name="id2876735"></a><i class="parameter"><tt>wins server</tt></i>(*), <a class="indexterm" name="id2876749"></a><i class="parameter"><tt>wins support</tt></i>(*), <a class="indexterm" name="id2876763"></a><i class="parameter"><tt>wins hook</tt></i>. </p><a class="indexterm" name="id2876778"></a><p> For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are the only options that commonly MAY need to be modified. Even if not one of these parameters is set <tt class="filename">nmbd</tt> will still do it's job. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2876803"></a>Discussion</h2></div></div><div></div></div><p> Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging. SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft is intent on phasing out NetBIOS support. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2876818"></a>NetBIOS over TCP/IP</h3></div></div><div></div></div><p> Samba implements NetBIOS, as does MS Windows NT / 200x / XP, by encapsulating it over TCP/IP. MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to affect browse list management. When running NetBIOS over TCP/IP, this uses UDP based messaging. UDP messages can be broadcast or unicast. </p><a class="indexterm" name="id2876837"></a><p> Normally, only unicast UDP messaging can be forwarded by routers. The <a class="indexterm" name="id2876849"></a><i class="parameter"><tt>remote announce</tt></i> parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP. Similarly, the <a class="indexterm" name="id2876865"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of <tt class="filename">smb.conf</tt> implements browse list collation using unicast UDP. </p><p> Secondly, in those networks where Samba is the only SMB server technology, wherever possible <tt class="filename">nmbd</tt> should be configured on one (1) machine as the WINS server. This makes it easy to manage the browsing environment. If each network segment is configured with it's own Samba WINS server, then the only way to get cross segment browsing to work is by using the <a class="indexterm" name="id2876904"></a><i class="parameter"><tt>remote announce</tt></i> and the <a class="indexterm" name="id2876918"></a><i class="parameter"><tt>remote browse sync</tt></i> parameters to your <tt class="filename">smb.conf</tt> file. </p><p> <a class="indexterm" name="id2876944"></a> If only one WINS server is used for an entire multi-segment network then the use of the <a class="indexterm" name="id2876954"></a><i class="parameter"><tt>remote announce</tt></i> and the <a class="indexterm" name="id2876966"></a><i class="parameter"><tt>remote browse sync</tt></i> parameters should NOT be necessary. </p><p> As of Samba 3 WINS replication is being worked on. The bulk of the code has been committed, but it still needs maturation. This is NOT a supported feature of the Samba-3.0.0 release. Hopefully, this will become a supported feature of one of the Samba-3 release series. </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 class="filename">nmbd</tt> configured as a WINS server on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used <a class="indexterm" name="id2877008"></a><i class="parameter"><tt>remote browse sync</tt></i> and <a class="indexterm" name="id2877022"></a><i class="parameter"><tt>remote announce</tt></i> to affect browse list collation across all segments. Note that this means clients will only resolve local names, and must be configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers they can see 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="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877054"></a>TCP/IP - without NetBIOS</h3></div></div><div></div></div><p> <a class="indexterm" name="id2877066"></a> <a class="indexterm" name="id2877074"></a> <a class="indexterm" name="id2877083"></a> All TCP/IP using systems use various forms of host name resolution. The primary methods for TCP/IP hostname resolutions involves either a static file (<tt class="filename">/etc/hosts </tt>) or DNS (the Domain Name System). DNS is the technology that makes the Internet usable. DNS based host name resolution is supported by nearly all TCP/IP enabled systems. Only a few embedded TCP/IP systems do not support DNS. </p><p> When an MS Windows 200x / XP system attempts to resolve a host name to an IP address it follows a defined path: </p><div class="orderedlist"><ol type="1"><li><p> Checks the <tt class="filename">hosts</tt> file. It is located in <tt class="filename">C:\WinNT\System32\Drivers\etc</tt>. </p></li><li><p> Does a DNS lookup </p></li><li><p> Checks the NetBIOS name cache </p></li><li><p> Queries the WINS server </p></li><li><p> Does a broadcast name lookup over UDP </p></li><li><p> Looks up entries in LMHOSTS. It is located in <tt class="filename">C:\WinNT\System32\Drivers\etc</tt>. </p></li></ol></div><a class="indexterm" name="id2877180"></a><p> Windows 200x / XP can register it's host name with a Dynamic DNS server. You can force register with a Dynamic DNS server in Windows 200x / XP using: <b class="command">ipconfig /registerdns</b> </p><p> With Active Directory (ADS), a correctly functioning DNS server is absolutely essential. In the absence of a working DNS server that has been correctly configured, MS Windows clients and servers will be totally unable to locate each other, consequently network services will be severely impaired. </p><p> The use of Dynamic DNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for it's ability to adequately support the SRV (service) records that are needed for Active Directory. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877219"></a>DNS and Active Directory</h3></div></div><div></div></div><a class="indexterm" name="id2877228"></a><p> Occasionally we hear from UNIX network administrators who want to use a UNIX based Dynamic DNS server in place of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost certainly be necessary to create service records so that MS Active Directory clients can resolve host names to locate essential network services. The following are some of the default service records that Active Directory requires: </p><div class="itemizedlist"><ul type="disc"><li><p>_ldap._tcp.pdc.ms-dcs.<span class="emphasis"><em>Domain</em></span></p><p> This provides the address of the Windows NT PDC for the Domain. </p></li><li><p>_ldap._tcp.pdc.ms-dcs.<span class="emphasis"><em>DomainTree</em></span></p><p> Resolves the addresses of Global Catalog servers in the domain. </p></li><li><p>_ldap._tcp.<span class="emphasis"><em>site</em></span>.sites.writable.ms-dcs.<span class="emphasis"><em>Domain</em></span></p><p> Provides list of domain controllers based on sites. </p></li><li><p>_ldap._tcp.writable.ms-dcs.<span class="emphasis"><em>Domain</em></span></p><p> Enumerates list of domain controllers that have the writable copies of the Active Directory data store. </p></li><li><p>_ldap._tcp.<span class="emphasis"><em>GUID</em></span>.domains.ms-dcs.<span class="emphasis"><em>DomainTree</em></span></p><p> Entry used by MS Windows clients to locate machines using the Global Unique Identifier. </p></li><li><p>_ldap._tcp.<span class="emphasis"><em>Site</em></span>.gc.ms-dcs.<span class="emphasis"><em>DomainTree</em></span></p><p> Used by MS Windows clients to locate site configuration dependent Global Catalog server. </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2877367"></a>How Browsing Functions</h2></div></div><div></div></div><p> MS Windows machines register their NetBIOS names (ie: the machine name for each service type in operation) on start up. The exact method by which this name registration 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 <a class="indexterm" name="id2877403"></a><i class="parameter"><tt>remote announce</tt></i> parameter). </p><p> Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such packets can be routed 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 synchronisation of browse lists across routed networks using the <a class="indexterm" name="id2877466"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS based name resolution, but it should be noted that the <a class="indexterm" name="id2877495"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, for cross subnet browsing to function correctly it is essential that a name to address resolution mechanism be provided. This mechanism could be via DNS, <tt class="filename">/etc/hosts</tt>, and so on. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="DMB"></a>Setting up WORKGROUP Browsing</h3></div></div><div></div></div><p> To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one Samba server to be the Domain Master Browser (note that this is *NOT* 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 presence of a domain master browser that makes cross subnet browsing possible for a workgroup. </p><p> In an WORKGROUP environment the domain master browser must be a Samba server, and there must only be one domain master browser per workgroup name. To set up a Samba server as a domain master browser, set the following option in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr></table><p> </p><p> The domain master browser should also preferably be the local master browser for its own subnet. In order to achieve this set the following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><div class="example"><a name="id2877630"></a><p class="title"><b>Example�10.1.�Domain master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p> </p><p> The domain master browser may be the same machine as the WINS server, if you require. </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 <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><div class="example"><a name="id2877721"></a><p class="title"><b>Example�10.2.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p> </p><p> Do not do this for more than one Samba server on each subnet, or they will war with each other over which is to be the local master browser. </p><p> The <a class="indexterm" name="id2877787"></a><i class="parameter"><tt>local master</tt></i> parameter allows Samba to act as a local master browser. The <a class="indexterm" name="id2877804"></a><i class="parameter"><tt>preferred master</tt></i> causes nmbd to force a browser election on startup and the <a class="indexterm" name="id2877819"></a><i class="parameter"><tt>os level</tt></i> parameter sets Samba high enough so that it should win any browser elections. </p><p> If you have an NT machine on the subnet that you wish to be the local master browser then you can disable Samba from becoming a local master browser by setting the following options in the <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><div class="example"><a name="id2877859"></a><p class="title"><b>Example�10.3.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2877916"></a>Setting up DOMAIN Browsing</h3></div></div><div></div></div><p> If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a domain is also the Domain master browser for that domain, and many things will break if a Samba server registers the Domain master browser NetBIOS name (<i class="replaceable"><tt>DOMAIN</tt></i><1B>) with WINS instead of the PDC. </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 <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><div class="example"><a name="id2877965"></a><p class="title"><b>Example�10.4.�Local master browser smb.conf</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 65</tt></i></td></tr></table></div><p> </p><p> If you wish to have a Samba server fight the election with machines on the same subnet you may set the <a class="indexterm" name="id2878026"></a><i class="parameter"><tt>os level</tt></i> parameter to lower levels. By doing this you can tune the order of machines that will become local master browsers if they are running. For more details on this see the section <a href="#browse-force-master" title="Forcing Samba to be the master"> 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 <i class="parameter"><tt>[global]</tt></i> section of the <tt class="filename">smb.conf</tt> file : </p><p> </p><div class="example"><a name="id2878082"></a><p class="title"><b>Example�10.5.�smb.conf for not being a master browser</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>domain master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>local master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>preferred master = no</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 0</tt></i></td></tr></table></div><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="browse-force-master"></a>Forcing Samba to be the master</h3></div></div><div></div></div><p> Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else. </p><p> If you want Samba to win elections then just set the <a class="indexterm" name="id2878164"></a><i class="parameter"><tt>os level</tt></i> global option in <tt class="filename">smb.conf</tt> to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!) </p><p> A <a class="indexterm" name="id2878192"></a><i class="parameter"><tt>os level</tt></i> of 2 would make it beat WfWg and Win95, but not MS Windows NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. </p><p>The maximum os level is 255</p><p> If you want Samba to force an election on startup, then set the <a class="indexterm" name="id2878218"></a><i class="parameter"><tt>preferred master</tt></i> global option in <tt class="filename">smb.conf</tt> to <tt class="constant">yes</tt>. Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with care, as if you have two hosts (whether they are Windows 95 or NT or Samba) on the same local subnet both set with <a class="indexterm" name="id2878248"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, then periodically and continually they will force an election in order to become the local master browser. </p><p> If you want Samba to be a <span class="emphasis"><em>domain master browser</em></span>, then it is recommended that you also set <a class="indexterm" name="id2878277"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, because Samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet. </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><div><h3 class="title"><a name="id2878314"></a>Making Samba the domain master</h3></div></div><div></div></div><p> The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can make Samba act as the domain master by setting <a class="indexterm" name="id2878327"></a><i class="parameter"><tt>domain master</tt></i> = yes in <tt class="filename">smb.conf</tt>. By default it will not be a domain master. </p><p> Note that you should <span class="emphasis"><em>not</em></span> set Samba to be the domain master for a 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 <a class="indexterm" name="id2878374"></a><i class="parameter"><tt>os level</tt></i> high enough to make sure it wins elections, and set <a class="indexterm" name="id2878389"></a><i class="parameter"><tt>preferred master</tt></i> to <tt class="constant">yes</tt>, to get Samba to force an election on startup. </p><p> Note that all your servers (including Samba) and clients should be 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><div><h3 class="title"><a name="id2878491"></a>Note about broadcast addresses</h3></div></div><div></div></div><p> If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups does not seem to support a 0's broadcast and you will probably find that browsing and name lookups won't work. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878515"></a>Multiple interfaces</h3></div></div><div></div></div><p> Samba now supports machines with multiple network interfaces. If you have multiple interfaces then you will need to use the <a class="indexterm" name="id2878527"></a><i class="parameter"><tt>interfaces</tt></i> option in <tt class="filename">smb.conf</tt> to configure them. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878551"></a>Use of the Remote Announce parameter</h3></div></div><div></div></div><p> The <a class="indexterm" name="id2878560"></a><i class="parameter"><tt>remote announce</tt></i> parameter of <tt class="filename">smb.conf</tt> can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. The syntax of the <a class="indexterm" name="id2878585"></a><i class="parameter"><tt>remote announce</tt></i> parameter is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote announce = a.b.c.d [e.f.g.h] ...</tt></i></td></tr></table><p> <span class="emphasis"><em>or</em></span> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</tt></i></td></tr></table><p> where: </p><div class="variablelist"><dl><dt><span class="term"><i class="replaceable"><tt>a.b.c.d</tt></i> and <i class="replaceable"><tt>e.f.g.h</tt></i></span></dt><dd><p> <a class="indexterm" name="id2878655"></a> <a class="indexterm" name="id2878666"></a> is either the LMB (Local Master Browser) IP address or the broadcast address of the remote network. ie: the LMB is at 192.168.1.10, or the address could be given as 192.168.1.255 where the netmask is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast address of the remote network, every host will receive our announcements. This is noisy and therefore undesirable but may be necessary if we do NOT know the IP address of the remote LMB.</p></dd><dt><span class="term"><i class="replaceable"><tt>WORKGROUP</tt></i></span></dt><dd><p>is optional and can be either our own workgroup 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><div><h3 class="title"><a name="id2878708"></a>Use of the Remote Browse Sync parameter</h3></div></div><div></div></div><p> The <a class="indexterm" name="id2878719"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter of <tt class="filename">smb.conf</tt> is used to announce to another LMB that it must synchronise its NetBIOS name list with our Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on its network segment. </p><p> The syntax of the <a class="indexterm" name="id2878748"></a><i class="parameter"><tt>remote browse sync</tt></i> parameter is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>remote browse sync = a.b.c.d</tt></i></td></tr></table><p> where <i class="replaceable"><tt>a.b.c.d</tt></i> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2878786"></a>WINS - The Windows Internetworking Name Server</h2></div></div><div></div></div><p> Use of WINS (either Samba WINS <span class="emphasis"><em>or</em></span> MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. eg: It registers its name directly as a unique (the type 0x03) name. It also registers its name if it is running the LanManager compatible 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 <span class="emphasis"><em>or</em></span> via statically configured <tt class="filename">lmhosts</tt> files that must reside on all clients in the absence of WINS. </p><p> 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 <a class="indexterm" name="id2878876"></a><i class="parameter"><tt>wins support</tt></i> = yes to the <tt class="filename">smb.conf</tt> file [global] section. </p><p> To configure Samba to register with a WINS server just add <a class="indexterm" name="id2878904"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d to your <tt class="filename">smb.conf</tt> file <i class="parameter"><tt>[global]</tt></i> section. </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p> Never use both <a class="indexterm" name="id2878936"></a><i class="parameter"><tt>wins support</tt></i> = yes together with <a class="indexterm" name="id2878952"></a><i class="parameter"><tt>wins server</tt></i> = a.b.c.d particularly not using it's own IP address. Specifying both will cause <span class="application">nmbd</span> to refuse to start! </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2878975"></a>Setting up a WINS server</h3></div></div><div></div></div><p> Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must add the following option to the <tt class="filename">smb.conf</tt> file on the selected machine : in the <i class="parameter"><tt>[global]</tt></i> section add the line </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>wins support = yes</tt></i></td></tr></table><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 <a class="indexterm" name="id2879034"></a><i class="parameter"><tt>wins support</tt></i> = yes will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names. </p><p> You should set up only ONE WINS server. Do NOT set the <a class="indexterm" name="id2879056"></a><i class="parameter"><tt>wins support</tt></i> = yes option on more than one Samba server. </p><p> To set up a Windows NT Server as a WINS server you need to set up 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 refuses to document these replication protocols, Samba cannot currently participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server but currently only one Samba server should have the <a class="indexterm" name="id2879091"></a><i class="parameter"><tt>wins support</tt></i> = yes parameter set. </p><p> After the WINS server has been configured you must ensure that all machines participating on the network are configured with the address of this WINS server. If your WINS server is a Samba machine, fill in the Samba machine IP address in the <span class="guilabel">Primary WINS Server</span> field of the <span class="guilabel">Control Panel->Network->Protocols->TCP->WINS Server</span> 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 <i class="parameter"><tt>[global]</tt></i> section of all <tt class="filename">smb.conf</tt> files : </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>wins server = <name or IP address></tt></i></td></tr></table><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 class="filename">smb.conf</tt> file of the Samba server acting as the WINS server itself. If you set both the <a class="indexterm" name="id2879189"></a><i class="parameter"><tt>wins support</tt></i> = yes option and the <a class="indexterm" name="id2879204"></a><i class="parameter"><tt>wins server</tt></i> = <name> 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><div><h3 class="title"><a name="id2879231"></a>WINS Replication</h3></div></div><div></div></div><p> Samba-3 permits WINS replication through the use of the <tt class="filename">wrepld</tt> utility. This tool is not currently capable of being used as it is still in active development. As soon as this tool becomes moderately functional we will prepare man pages and enhance this section of the documentation to provide usage and technical details. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879256"></a>Static WINS Entries</h3></div></div><div></div></div><p> Adding static entries to your Samba WINS server is actually fairly easy. All you have to do is add a line to <tt class="filename">wins.dat</tt>, typically located in <tt class="filename">/usr/local/samba/var/locks</tt>. </p><p> Entries in <tt class="filename">wins.dat</tt> take the form of </p><pre class="programlisting"> "NAME#TYPE" TTL ADDRESS+ FLAGS </pre><p> where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the time-to-live as an absolute time in seconds, ADDRESS+ is one or more addresses corresponding to the registration and FLAGS are the NetBIOS flags for the registration. </p><p> A typical dynamic entry looks like: </p><pre class="programlisting"> "MADMAN#03" 1055298378 192.168.1.2 66R </pre><p> To make it static, all that has to be done is set the TTL to 0: </p><pre class="programlisting"> "MADMAN#03" 0 192.168.1.2 66R </pre><p> </p><p> Though this method works with early Samba-3 versions, there's a possibility that it may change in future versions if WINS replication is added. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879345"></a>Helpful Hints</h2></div></div><div></div></div><p> The following hints should be carefully considered as they are stumbling points for many new network administrators. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879358"></a>Windows Networking Protocols</h3></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Do NOT use more than one (1) protocol on MS Windows machines </p></div><p> A very common cause of browsing problems results from installing more than 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 precedence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably win and thus retain it's role. </p><p> 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><div><h3 class="title"><a name="id2879437"></a>Name Resolution Order</h3></div></div><div></div></div><p> Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information are: </p><div class="itemizedlist"><ul type="disc"><li><p>WINS: the best tool!</p></li><li><p>LMHOSTS: is static and hard to maintain.</p></li><li><p>Broadcast: uses UDP and can not resolve names across remote segments.</p></li></ul></div><p> Alternative means of name resolution includes: </p><div class="itemizedlist"><ul type="disc"><li><p><tt class="filename">/etc/hosts</tt>: is static, hard to maintain, and lacks name_type info</p></li><li><p>DNS: is a good choice but lacks essential name_type info.</p></li></ul></div><p> Many sites want to restrict DNS lookups and want to avoid broadcast name resolution traffic. The <i class="parameter"><tt>name resolve order</tt></i> parameter is of great help here. The syntax of the <i class="parameter"><tt>name resolve order</tt></i> parameter is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>name resolve order = wins lmhosts bcast host</tt></i></td></tr></table><p> <span class="emphasis"><em>or</em></span> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>name resolve order = wins lmhosts (eliminates bcast and host)</tt></i></td></tr></table><p> The default is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>name resolve order = host lmhost wins bcast</tt></i></td></tr></table><p> where "host" refers to the native methods used by the UNIX system to implement the gethostbyname() function call. This is normally controlled by <tt class="filename">/etc/host.conf</tt>, <tt class="filename">/etc/nsswitch.conf</tt> and <tt class="filename">/etc/resolv.conf</tt>. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2879603"></a>Technical Overview of browsing</h2></div></div><div></div></div><p> SMB networking provides a mechanism by which clients can access a list of machines in a network, a so-called <a class="indexterm" name="id2879615"></a><i class="parameter"><tt>browse list</tt></i>. This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse 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><div><h3 class="title"><a name="id2879656"></a>Browsing support in Samba</h3></div></div><div></div></div><p> Samba facilitates browsing. The browsing is supported by <span class="application">nmbd</span> and is also controlled by options in the <tt class="filename">smb.conf</tt> file. Samba can act as a local browse master for a workgroup and the ability 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 <a class="indexterm" name="id2879724"></a><i class="parameter"><tt>workgroup</tt></i> option in <tt class="filename">smb.conf</tt> to control what workgroup Samba becomes a part of. </p><p> Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is recommended that this option is only used for 'unusual' purposes: announcements over the internet, for example. See <a class="indexterm" name="id2879754"></a><i class="parameter"><tt>remote announce</tt></i> in the <tt class="filename">smb.conf</tt> man page. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879778"></a>Problem resolution</h3></div></div><div></div></div><p> If something doesn't work then hopefully the log.nmbd file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored in text form in a file called <tt class="filename">browse.dat</tt>. </p><p> Note that if it doesn't work for you, then you should still be able to type the server name as <tt class="filename">\\SERVER</tt> in filemanager then hit enter and filemanager should display the list of available shares. </p><p> Some people find browsing fails because they don't have the global <a class="indexterm" name="id2879819"></a><i class="parameter"><tt>guest account</tt></i> set to a valid account. Remember that the IPC$ connection that lists the shares is done as guest, and thus you must have a valid guest account. </p><p><span class="emphasis"><em> 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 class="filename">smb.conf</tt>) </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2879866"></a>Browsing across subnets</h3></div></div><div></div></div><p> Since the release of Samba 1.9.17(alpha1), Samba has supported the replication of browse lists across subnet boundaries. This section describes how to set this feature up in different settings. </p><p> To see browse lists that span TCP/IP subnets (ie. networks separated by routers that don't pass broadcast traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing NetBIOS name to IP address translation to be done by doing a direct query of the WINS server. This is done via a directed UDP packet on port 137 to the WINS server machine. The reason for a WINS server is that by default, all NetBIOS name to IP address translation is done by broadcasts from the querying machine. This means that machines on one subnet will not be able to resolve the names of machines on another subnet without using a WINS server. </p><p> Remember, for browsing across subnets to work correctly, all machines, be they Windows 95, Windows NT, or Samba servers must have the IP address of a WINS server given to them by a DHCP server, or by manual configuration (for Win95 and WinNT, this is in the TCP/IP Properties, under Network settings) for Samba this is in the <tt class="filename">smb.conf</tt> file. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2879915"></a>How does cross subnet browsing work ?</h4></div></div><div></div></div><p> Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. Samba is capable of cross subnet browsing when configured correctly. </p><p> Consider a network set up as <a href="#browsing1" title="Figure�10.1.�Cross subnet browsing example">in the diagram below</a>. </p><div class="figure"><a name="browsing1"></a><p class="title"><b>Figure�10.1.�Cross subnet browsing example</b></p><div class="mediaobject"><img src="projdoc/imagefiles/browsing1.png" width="270" alt="Cross subnet browsing example"></div></div><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 simplicity's 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><div class="table"><a name="id2880049"></a><p class="title"><b>Table�10.1.�Browse subnet example 1</b></p><table summary="Browse subnet example 1" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="left">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="left">N1_A, N1_B, N1_C, N1_D, N1_E</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="left">N2_A, N2_B, N2_C, N2_D</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="left">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p> </p><p> Note that at this point all the subnets are separate, no machine is seen across any of the subnets. </p><p> 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 registered 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><div class="table"><a name="id2880162"></a><p class="title"><b>Table�10.2.�Browse subnet example 2</b></p><table summary="Browse subnet example 2" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. </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 occurred 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><div class="table"><a name="id2880274"></a><p class="title"><b>Table�10.3.�Browse subnet example 3</b></p><table summary="Browse subnet example 3" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. </p><p> At this point users looking in their network neighborhood on subnets 1 or 3 will see all the servers on all subnets, users on subnet 2 will still only see the servers on subnets 1 and 2, but not 3. </p><p> Finally, the local master browser for subnet 2 (N2_B) will sync again with the domain master browser (N1_C) and will receive the missing server entries. Finally - and as a steady state (if no machines are removed or shut off) the browse lists will look like : </p><p> </p><div class="table"><a name="id2880391"></a><p class="title"><b>Table�10.4.�Browse subnet example 4</b></p><table summary="Browse subnet example 4" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Subnet</th><th align="left">Browse Master</th><th align="justify">List</th></tr></thead><tbody><tr><td align="left">Subnet1</td><td align="left">N1_C</td><td align="justify">N1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">N3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr></tbody></table></div><p> Servers with a (*) after them are non-authoritative names. </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 class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880547"></a>Common Errors</h2></div></div><div></div></div><p> Many questions are asked on the mailing lists regarding browsing. The majority of browsing problems originate out of incorrect configuration of NetBIOS name resolution. Some are of particular note. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880562"></a>How can one flush the Samba NetBIOS name cache without restarting Samba?</h3></div></div><div></div></div><p> Samba's nmbd process controls all browse list handling. Under normal circumstances it is safe to restart nmbd. This will effectively flush the Samba NetBIOS name cache and cause it to be rebuilt. Note that this does NOT make certain that a rogue machine name will not re-appear in the browse list. When nmbd is taken out of service another machine on the network will become the browse master. This new list may still have the rogue entry in it. If you really want to clear a rogue machine from the list then every machine on the network will need to be shut down and restarted at after all machines are down. Failing a complete restart, the only other thing you can do is wait until the entry times out and is then flushed from the list. This may take a long time on some networks (months). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880591"></a>My client reports "This server is not configured to list shared resources"</h3></div></div><div></div></div><p> Your guest account is probably invalid for some reason. Samba uses the guest account for browsing in smbd. Check that your guest account is valid. </p><p>See also <a class="indexterm" name="id2880612"></a><i class="parameter"><tt>guest account</tt></i> in the <tt class="filename">smb.conf</tt> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880635"></a>I get an <span class="errorname">Unable to browse the network</span> error</h3></div></div><div></div></div><p>This error can have multiple causes:</p><div class="itemizedlist"><ul type="disc"><li><p>There is no local master browser. Configure <span class="application">nmbd</span> or any other machine to serve as local master browser.</p></li><li><p>You can not log onto the machine that is the local master browser. Can you logon to it as guest user? </p></li><li><p>There is no IP connectivity to the local master browser. Can you reach it by broadcast?</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter�11.�Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><tt class="email"><<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></tt></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2880915">Features and Benefits</a></dt><dd><dl><dt><a href="#id2880929">Backwards Compatibility Backends</a></dt><dt><a href="#id2881032">New Backends</a></dt></dl></dd><dt><a href="#id2881219">Technical Information</a></dt><dd><dl><dt><a href="#id2881344">Important Notes About Security</a></dt><dt><a href="#id2881634">Mapping User Identifiers between MS Windows and UNIX</a></dt><dt><a href="#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></dt></dl></dd><dt><a href="#acctmgmttools">Account Management Tools</a></dt><dd><dl><dt><a href="#id2881821">The smbpasswd Command</a></dt><dt><a href="#id2882092">The pdbedit Command</a></dt></dl></dd><dt><a href="#id2882329">Password Backends</a></dt><dd><dl><dt><a href="#id2882371">Plain Text</a></dt><dt><a href="#id2882412">smbpasswd - Encrypted Password Database</a></dt><dt><a href="#id2882525">tdbsam</a></dt><dt><a href="#id2882559">ldapsam</a></dt><dt><a href="#id2884412">MySQL</a></dt><dt><a href="#XMLpassdb">XML</a></dt></dl></dd><dt><a href="#id2885260">Common Errors</a></dt><dd><dl><dt><a href="#id2885267">Users can not logon</a></dt><dt><a href="#id2885312">Users being added to wrong backend database</a></dt><dt><a href="#id2885422">auth methods does not work</a></dt></dl></dd></dl></div><p> Samba 3 implements a new capability to work concurrently with multiple account backends. The possible new combinations of password backends allows Samba 3 a degree of flexibility and scalability that previously could be achieved only with MS Windows Active Directory. This chapter describes the new functionality and how to get the most out of it. </p><p> In the course of development of Samba-3, a number of requests were received to provide the ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide matching UNIX/Linux accounts. We called this the <span class="emphasis"><em>Non UNIX Accounts (NUA)</em></span> capability. The intent was that an administrator could decide to use the <span class="emphasis"><em>tdbsam</em></span> backend and by simply specifying <a class="indexterm" name="id2880884"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam_nua this would allow Samba-3 to implement a solution that did not use UNIX accounts per se. Late in the development cycle, the team doing this work hit upon some obstacles that prevents this solution from being used. Given the delays with Samba-3 release a decision was made to NOT deliver this functionality until a better method of recognising NT Group SIDs from NT User SIDs could be found. This feature may thus return during the life cycle for the Samba-3 series. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Samba-3 does NOT support Non-UNIX Account (NUA) operation for user accounts. Samba-3 does support NUA operation for machine accounts. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2880915"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality as follows: </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2880929"></a>Backwards Compatibility Backends</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Plain Text:</span></dt><dd><p> This option uses nothing but the UNIX/Linux <tt class="filename">/etc/passwd</tt> style back end. On systems that have PAM (Pluggable Authentication Modules) support all PAM modules are supported. The behaviour is just as it was with Samba-2.2.x, and the protocol limitations imposed by MS Windows clients apply likewise. </p></dd><dt><span class="term">smbpasswd:</span></dt><dd><p> This option allows continues use of the <tt class="filename">smbpasswd</tt> file that maintains a plain ASCII (text) layout that includes the MS Windows LanMan and NT encrypted passwords as well as a field that stores some account information. This form of password backend does NOT store any of the MS Windows NT/200x SAM (Security Account Manager) information needed to provide the extended controls that are needed for more comprehensive interoperation with MS Windows NT4 / 200x servers. </p><p> This backend should be used only for backwards compatibility with older versions of Samba. It may be deprecated in future releases. </p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility):</span></dt><dd><p> There is a password backend option that allows continued operation with a existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension. This option is provided primarily as a migration tool, although there is no reason to force migration at this time. Note that this tool will eventually be deprecated. </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881032"></a>New Backends</h3></div></div><div></div></div><p> Samba-3 introduces the following new password backend capabilities: </p><div class="variablelist"><dl><dt><span class="term">tdbsam:</span></dt><dd><p> This backend provides a rich database backend for local servers. This backend is NOT suitable for multiple domain controller (ie: PDC + one or more BDC) installations. </p><p> The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em> smbpasswd</em></span> information PLUS the extended MS Windows NT / 200x SAM information into a binary format TDB (trivial database) file. The inclusion of the extended information makes it possible for Samba-3 to implement the same account and system access controls that are possible with MS Windows NT4 and MS Windows 200x based systems. </p><p> The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct response to user requests to allow simple site operation without the overhead of the complexities of running OpenLDAP. It is recommended to use this only for sites that have fewer than 250 users. For larger sites or implementations the use of OpenLDAP or of Active Directory integration is strongly recommended. </p></dd><dt><span class="term">ldapsam:</span></dt><dd><p> This provides a rich directory backend for distributed account installation. </p><p> Samba-3 has a new and extended LDAP implementation that requires configuration of OpenLDAP with a new format samba schema. The new format schema file is included in the <tt class="filename">examples/LDAP</tt> directory of the Samba distribution. </p><p> The new LDAP implementation significantly expands the control abilities that were possible with prior versions of Samba. It is now possible to specify "per user" profile settings, home directories, account access controls, and much more. Corporate sites will see that the Samba-Team has listened to their requests both for capability and to allow greater scalability. </p></dd><dt><span class="term">mysqlsam (MySQL based backend):</span></dt><dd><p> It is expected that the MySQL based SAM will be very popular in some corners. This database backend will be on considerable interest to sites that want to leverage existing MySQL technology. </p></dd><dt><span class="term">xmlsam (XML based datafile):</span></dt><dd><p> Allows the account and password data to be stored in an XML format data file. This backend can not be used for normal operation, it can only be used in conjunction with <b class="command">pdbedit</b>'s pdb2pdb functionality. The DTD that is used might be subject to changes in the future. </p><p> The xmlsam option can be useful for account migration between database backends or backups. Use of this tool will allow the data to be edited before migration into another backend format. </p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2881219"></a>Technical Information</h2></div></div><div></div></div><p> Old windows clients send plain text passwords over the wire. Samba can check these passwords by crypting them and comparing them to the hash stored in the unix user database. </p><p> Newer windows clients send encrypted passwords (so-called Lanman and NT hashes) over the wire, instead of plain text passwords. The newest clients will send only encrypted passwords and refuse to send plain text passwords, unless their registry is tweaked. </p><p> These passwords can't be converted to unix style encrypted passwords. Because of that, you can't use the standard unix user database, and you have to store the Lanman and NT hashes somewhere else. </p><p> In addition to differently encrypted passwords, windows also stores certain data for each user that is not stored in a unix user database. e.g: workstations the user may logon from, the location where the users' profile is stored, and so on. Samba retrieves and stores this information using a <a class="indexterm" name="id2881258"></a><i class="parameter"><tt>passdb backend</tt></i>. Commonly available backends are LDAP, plain text file, MySQL and nisplus. For more information, see the man page for <tt class="filename">smb.conf</tt> regarding the <a class="indexterm" name="id2881282"></a><i class="parameter"><tt>passdb backend</tt></i> parameter. </p><div class="figure"><a name="idmap-diag"></a><p class="title"><b>Figure�11.1.�IDMAP</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap.png" width="270" alt="IDMAP"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881344"></a>Important Notes About Security</h3></div></div><div></div></div><p> The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix scheme typically sends clear text passwords over the network when logging in. This is bad. The SMB encryption scheme never sends the cleartext password over the network but it does store the 16 byte hashed values on disk. This is also bad. Why? Because the 16 byte hashed values are a "password equivalent". You cannot derive the user's password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. You should thus treat the data stored in whatever passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the cleartext passwords of all your users. Its contents must be kept secret, and the file should be protected accordingly. </p><p> Ideally we would like a password scheme that involves neither plain text passwords on the net nor on disk. Unfortunately this is not available as Samba is stuck with having to be compatible with other SMB systems (WinNT, WfWg, Win95 etc). </p><p> Windows NT 4.0 Service pack 3 changed the default setting so that plaintext passwords are disabled from being sent over the wire. This mandates either the use of encrypted password support or edit the Windows NT registry to re-enable plaintext passwords. </p><p> The following versions of MS Windows do not support full domain security protocols, although they may log onto a domain environment: </p><div class="itemizedlist"><ul type="disc"><li><p>MS DOS Network client 3.0 with the basic network redirector installed</p></li><li><p>Windows 95 with the network redirector update installed</p></li><li><p>Windows 98 [se]</p></li><li><p>Windows Me</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> MS Windows XP Home does not have facilities to become a domain member and it can not participate in domain logons. </p></div><p> The following versions of MS Windows fully support domain security protocols. </p><div class="itemizedlist"><ul type="disc"><li><p>Windows NT 3.5x</p></li><li><p>Windows NT 4.0</p></li><li><p>Windows 2000 Professional</p></li><li><p>Windows 200x Server/Advanced Server</p></li><li><p>Windows XP Professional</p></li></ul></div><p> All current release of Microsoft SMB/CIFS clients support authentication via the SMB Challenge/Response mechanism described here. Enabling clear text authentication does not disable the ability of the client to participate in encrypted authentication. Instead, it allows the client to negotiate either plain text _or_ encrypted password handling. </p><p> MS Windows clients will cache the encrypted password alone. Where plain text passwords are re-enabled, through the appropriate registry change, the plain text password is NEVER cached. This means that in the event that a network connections should become disconnected (broken) only the cached (encrypted) password will be sent to the resource server to affect a auto-reconnect. If the resource server does not support encrypted passwords the auto-reconnect will fail. <span class="emphasis"><em>USE OF ENCRYPTED PASSWORDS IS STRONGLY ADVISED.</em></span> </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881537"></a>Advantages of Encrypted Passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server.</p></li><li><p>Plain text passwords are not stored anywhere in memory or on disk.</p></li><li><p>WinNT doesn't like talking to a server that does not support encrypted passwords. It will refuse to browse the server if the server is also in user level security mode. It will insist on prompting the user for the password on each connection, which is very annoying. The only things you can do to stop this is to use SMB encryption. </p></li><li><p>Encrypted password support allows automatic share (resource) reconnects.</p></li><li><p>Encrypted passwords are essential for PDC/BDC operation.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2881599"></a>Advantages of non-encrypted passwords</h4></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Plain text passwords are not kept on disk, and are NOT cached in memory. </p></li><li><p>Uses same password file as other unix services such as login and ftp</p></li><li><p>Use of other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB isn't such a big deal.</p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881634"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div><div></div></div><p> Every operation in UNIX/Linux requires a user identifier (UID), just as in MS Windows NT4 / 200x this requires a Security Identifier (SID). Samba provides two means for mapping an MS Windows user to a UNIX/Linux UID. </p><p> Firstly, all Samba SAM (Security Account Manager database) accounts require a UNIX/Linux UID that the account will map to. As users are added to the account information database, Samba will call the <a class="indexterm" name="id2881658"></a><i class="parameter"><tt>add user script</tt></i> interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local user account. </p><p> The second way to affect Windows SID to UNIX UID mapping is via the <span class="emphasis"><em>idmap uid, idmap gid</em></span> parameters in <tt class="filename">smb.conf</tt>. Please refer to the man page for information about these parameters. These parameters are essential when mapping users from a remote SAM server. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div><div></div></div><p> Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs on all servers in a distributed network. A distributed network is one where there exists a PDC, one or more BDCs and/or one or more domain member servers. Why is this important? This is important if files are being shared over more than one protocol (eg: NFS) and where users are copying files across UNIX/Linux systems using tools such as <b class="command">rsync</b>. </p><p> The special facility is enabled using a parameter called <i class="parameter"><tt>idmap backend</tt></i>. The default setting for this parameter is an empty string. Administrators should NOT set this parameter except when an LDAP based passdb backend is in use. An example of use is: </p><p> </p><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example�11.1.�</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>idmap backend = ldapsam://ldap-server.quenya.org:636</tt></i></td></tr></table></div><p> </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acctmgmttools"></a>Account Management Tools</h2></div></div><div></div></div><p> Samba provides two (2) tools for management of User and machine accounts. These tools are called <b class="command">smbpasswd</b> and <b class="command">pdbedit</b>. A third tool is under development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will be announced in time for the Samba-3.0.1 release. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2881821"></a>The <span class="emphasis"><em>smbpasswd</em></span> Command</h3></div></div><div></div></div><p> The smbpasswd utility is a utility similar to the <b class="command">passwd</b> or <b class="command">yppasswd</b> programs. It maintains the two 32 byte password fields in the passdb backend. </p><p> <b class="command">smbpasswd</b> works in a client-server mode where it contacts the local smbd to change the user's password on its behalf. This has enormous benefits as follows: </p><p> <b class="command">smbpasswd</b> has the capability to change passwords on Windows NT servers (this only works when the request is sent to the NT Primary Domain Controller if changing an NT Domain user's password). </p><p> <b class="command">smbpasswd</b> can be used to: </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>add</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>delete</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>enable</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>disable</em></span> user or machine accounts</p></li><li><p><span class="emphasis"><em>set to NULL</em></span> user passwords</p></li><li><p><span class="emphasis"><em>manage interdomain trust accounts</em></span></p></li></ul></div><p> To run smbpasswd as a normal user just type: </p><p> </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>smbpasswd</tt></b> <tt class="prompt">Old SMB password: </tt><b class="userinput"><tt><i class="replaceable"><tt>secret</tt></i></tt></b> </pre><p> For <i class="replaceable"><tt>secret</tt></i> type old value here - or hit return if there was no old password </p><pre class="screen"> <tt class="prompt">New SMB Password: </tt><b class="userinput"><tt><i class="replaceable"><tt>new secret</tt></i></tt></b> <tt class="prompt">Repeat New SMB Password: </tt><b class="userinput"><tt><i class="replaceable"><tt>new secret</tt></i></tt></b> </pre><p> </p><p> If the old value does not match the current value stored for that user, or the two new values do not match each other, then the password will not be changed. </p><p> When invoked by an ordinary user it will only allow change of their own SMB password. </p><p> When run by root smbpasswd may take an optional argument, specifying the user name whose SMB password you wish to change. When run as root, smbpasswd does not prompt for or check the old password value, thus allowing root to set passwords for users who have forgotten their passwords. </p><p> <b class="command">smbpasswd</b> is designed to work in the way familiar to UNIX users who use the <b class="command">passwd</b> or <b class="command">yppasswd</b> commands. While designed for administrative use, this tool provides essential user level password change capabilities. </p><p> For more details on using <b class="command">smbpasswd</b> refer to the man page (the definitive reference). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882092"></a>The <span class="emphasis"><em>pdbedit</em></span> Command</h3></div></div><div></div></div><p> <b class="command">pdbedit</b> is a tool that can be used only by root. It is used to manage the passdb backend. <b class="command">pdbedit</b> can be used to: </p><div class="itemizedlist"><ul type="disc"><li><p>add, remove or modify user accounts</p></li><li><p>listing user accounts</p></li><li><p>migrate user accounts</p></li></ul></div><p> The <b class="command">pdbedit</b> tool is the only one that can manage the account security and policy settings. It is capable of all operations that smbpasswd can do as well as a super set of them. </p><p> One particularly important purpose of the <b class="command">pdbedit</b> is to allow the migration of account information from one passdb backend to another. See the <a href="#XMLpassdb" title="XML">XML</a> password backend section of this chapter. </p><p> The following is an example of the user account information that is stored in a tdbsam password backend. This listing was produced by running: </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>pdbedit -Lv met</tt></b> UNIX username: met NT username: Account Flags: [UX ] User SID: S-1-5-21-1449123459-1407424037-3116680435-2004 Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201 Full Name: Melissa E Terpstra Home Directory: \\frodo\met\Win9Profile HomeDir Drive: H: Logon Script: scripts\logon.bat Profile Path: \\frodo\Profiles\met Domain: MIDEARTH Account desc: Workstations: melbelle Munged dial: Logon time: 0 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT Password last set: Sat, 14 Dec 2002 14:37:03 GMT Password can change: Sat, 14 Dec 2002 14:37:03 GMT Password must change: Mon, 18 Jan 2038 20:14:07 GMT </pre><p> The <b class="command">pdbedit</b> tool allows migration of authentication (account) databases from one backend to another. For example: To migrate accounts from an old <tt class="filename">smbpasswd</tt> database to a <i class="parameter"><tt>tdbsam</tt></i> backend: </p><div class="procedure"><ol type="1"><li><p> Set the <a class="indexterm" name="id2882260"></a><i class="parameter"><tt>passdb backend</tt></i> = tdbsam, smbpasswd. </p></li><li><p> Execute: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>pdbedit -i smbpassed -e tdbsam</tt></b> </pre><p> </p></li><li><p> Now remove the <i class="parameter"><tt>smbpasswd</tt></i> from the passdb backend configuration in <tt class="filename">smb.conf</tt>. </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2882329"></a>Password Backends</h2></div></div><div></div></div><p> Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server technology available today. The flexibility is immediately obvious as one begins to explore this capability. </p><p> It is possible to specify not only multiple different password backends, but even multiple backends of the same type. For example, to use two different tdbsam databases: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>passdb backend = tdbsam:/etc/samba/passdb.tdb, tdbsam:/etc/samba/old-passdb.tdb</tt></i></td></tr></table><p> </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882371"></a>Plain Text</h3></div></div><div></div></div><p> Older versions of Samba retrieved user information from the unix user database and eventually some other fields from the file <tt class="filename">/etc/samba/smbpasswd</tt> or <tt class="filename">/etc/smbpasswd</tt>. When password encryption is disabled, no SMB specific data is stored at all. Instead all operations are conducted via the way that the Samba host OS will access its <tt class="filename">/etc/passwd</tt> database. eg: On Linux systems that is done via PAM. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882412"></a>smbpasswd - Encrypted Password Database</h3></div></div><div></div></div><p> Traditionally, when configuring <a class="indexterm" name="id2882422"></a><i class="parameter"><tt>encrypt passwords</tt></i> = yes in Samba's <tt class="filename">smb.conf</tt> file, user account information such as username, LM/NT password hashes, password change times, and account flags have been stored in the <tt class="filename">smbpasswd(5)</tt> file. There are several disadvantages to this approach for sites with very large numbers of users (counted in the thousands). </p><div class="itemizedlist"><ul type="disc"><li><p> The first is that all lookups must be performed sequentially. Given that there are approximately two lookups per domain logon (one for a normal session connection such as when mapping a network drive or printer), this is a performance bottleneck for large sites. What is needed is an indexed approach such as is used in databases. </p></li><li><p> The second problem is that administrators who desire to replicate a smbpasswd file to more than one Samba server were left to use external tools such as <b class="command">rsync(1)</b> and <b class="command">ssh(1)</b> and wrote custom, in-house scripts. </p></li><li><p> And finally, the amount of information which is stored in an smbpasswd entry leaves no room for additional attributes such as a home directory, password expiration time, or even a Relative Identifier (RID). </p></li></ul></div><p> As a result of these deficiencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts is commonly referred to as the samdb interface (previously this was called the passdb API, and is still so named in the Samba CVS trees). </p><p> Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam. Of these ldapsam will be of most interest to large corporate or enterprise sites. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882525"></a>tdbsam</h3></div></div><div></div></div><p>Samba can store user and machine account data in a "TDB" (Trivial Database). Using this backend doesn't require any additional configuration. This backend is recommended for new installations that do not require LDAP. </p><p> As a general guide the Samba-Team does NOT recommend using the tdbsam backend for sites that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that requires replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2882559"></a>ldapsam</h3></div></div><div></div></div><p> There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in the this documentation does not include: </p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from an Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p> The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from PADL Software (<a href="http://www.padl.com/" target="_top">http://www.padl.com/</a>). More information about the configuration of these packages may be found at "LDAP, System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". Refer to <a href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top"> http://safari.oreilly.com/?XmlId=1-56592-491-6</a> for those who might wish to know more about configuration and administration of an OpenLDAP server. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> This section is outdated for Samba-3 schema. Samba-3 introduces a new schema that has not been documented at the time of this publication. </p></div><p> This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is assumed that the reader already has a basic understanding of LDAP concepts and has a working directory server already installed. For more information on LDAP architectures and Directories, please refer to the following sites. </p><div class="itemizedlist"><ul type="disc"><li><p>OpenLDAP - <a href="http://www.openldap.org/" target="_top">http://www.openldap.org/</a></p></li><li><p>iPlanet Directory Server - <a href="http://iplanet.netscape.com/directory" target="_top">http://iplanet.netscape.com/directory</a></p></li></ul></div><p> Two additional Samba resources which may prove to be helpful are </p><div class="itemizedlist"><ul type="disc"><li><p>The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a> maintained by Ignacio Coupeau.</p></li><li><p>The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are geared to manage users and group in such a Samba-LDAP Domain Controller configuration. </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882714"></a>Supported LDAP Servers</h4></div></div><div></div></div><p> The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and client libraries. The same code should work with Netscape's Directory Server and client SDK. However, there are bound to be compile errors and bugs. These should not be hard to fix. Please submit fixes via <a href="#bugreport" title="Chapter�35.�Reporting Bugs">Bug reporting facility</a>. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882739"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div><div></div></div><p> Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in <tt class="filename">examples/LDAP/samba.schema</tt>. The sambaSamAccount objectclass is given here: </p><p> </p><pre class="programlisting"> objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY DESC 'Samba 3.0 Auxiliary SAM Account' MUST ( uid $ sambaSID ) MAY ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $ sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $ sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $ displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $ sambaProfilePath $ description $ sambaUserWorkstations $ sambaPrimaryGroupSID $ sambaDomainName )) </pre><p> </p><p> The <tt class="filename">samba.schema</tt> file has been formatted for OpenLDAP 2.0/2.1. The OID's are owned by the Samba Team and as such is legal to be openly published. If you translate the schema to be used with Netscape DS, please submit the modified schema file as a patch to <a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>. </p><p> Just as the smbpasswd file is meant to store information which supplements a user's <tt class="filename">/etc/passwd</tt> entry, so is the sambaSamAccount object meant to supplement the UNIX user account information. A sambaSamAccount is a <tt class="constant">STRUCTURAL</tt> objectclass so it can be stored individually in the directory. However, there are several fields (e.g. uid) which overlap with the posixAccount objectclass outlined in RFC2307. This is by design. </p><p> In order to store all user account information (UNIX and Samba) in the directory, it is necessary to use the sambaSamAccount and posixAccount objectclasses in combination. However, smbd will still obtain the user's UNIX account information via the standard C library calls (e.g. getpwnam(), et. al.). This means that the Samba server must also have the LDAP NSS library installed and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account information in NIS while the network is transitioning to a full LDAP infrastructure. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2882851"></a>OpenLDAP configuration</h4></div></div><div></div></div><p> To include support for the sambaSamAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory. The samba.schema file can be found in the directory <tt class="filename">examples/LDAP</tt> in the samba source distribution. </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>cp samba.schema /etc/openldap/schema/</tt></b> </pre><p> </p><p> Next, include the <tt class="filename">samba.schema</tt> file in <tt class="filename">slapd.conf</tt>. The sambaSamAccount object contains two attributes which depend upon other schema files. The 'uid' attribute is defined in <tt class="filename">cosine.schema</tt> and the 'displayName' attribute is defined in the <tt class="filename">inetorgperson.schema</tt> file. Both of these must be included before the <tt class="filename">samba.schema</tt> file. </p><p> </p><pre class="programlisting"> ## /etc/openldap/slapd.conf ## schema files (core.schema is required by default) include /etc/openldap/schema/core.schema ## needed for sambaSamAccount include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/samba.schema include /etc/openldap/schema/nis.schema .... </pre><p> </p><p> It is recommended that you maintain some indices on some of the most useful attributes, like in the following example, to speed up searches made on sambaSamAccount objectclasses (and possibly posixAccount and posixGroup as well). </p><p> </p><pre class="programlisting"> # Indices to maintain ## required by OpenLDAP index objectclass eq index cn pres,sub,eq index sn pres,sub,eq ## required to support pdb_getsampwnam index uid pres,sub,eq ## required to support pdb_getsambapwrid() index displayName pres,sub,eq ## uncomment these if you are storing posixAccount and ## posixGroup entries in the directory as well ##index uidNumber eq ##index gidNumber eq ##index memberUid eq index sambaSID eq index sambaPrimaryGroupSID eq index sambaDomainName eq index default sub </pre><p> </p><p> Create the new index by executing: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt>./sbin/slapindex -f slapd.conf </pre><p> </p><p> Remember to restart slapd after making these changes: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>/etc/init.d/slapd restart</tt></b> </pre><p> </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883046"></a>Initialise the LDAP database</h4></div></div><div></div></div><p> Before you can add accounts to the LDAP database you must create the account containers that they will be stored in. The following LDIF file should be modified to match your needs (ie: Your DNS entries, etc.). </p><p> </p><pre class="programlisting"> # Organization for Samba Base dn: dc=quenya,dc=org objectclass: dcObject objectclass: organization dc: quenya o: Quenya Org Network description: The Samba-3 Network LDAP Example # Organizational Role for Directory Management dn: cn=Manager,dc=quenya,dc=org objectclass: organizationalRole cn: Manager description: Directory Manager # Setting up container for users dn: ou=People,dc=quenya,dc=org objectclass: top objectclass: organizationalUnit ou: People # Setting up admin handle for People OU dn: cn=admin,ou=People,dc=quenya,dc=org cn: admin objectclass: top objectclass: organizationalRole objectclass: simpleSecurityObject userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz </pre><p> </p><p> The userPassword shown above should be generated using <b class="command">slappasswd</b>. </p><p> The following command will then load the contents of the LDIF file into the LDAP database. </p><p> </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>slapadd -v -l initldap.dif</tt></b> </pre><p> </p><p> Do not forget to secure your LDAP server with an adequate access control list, as well as an admin password. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Before Samba can access the LDAP server you need to store the LDAP admin password into the Samba-3 <tt class="filename">secrets.tdb</tt> database by: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbpasswd -w <i class="replaceable"><tt>secret</tt></i></tt></b> </pre><p> </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883174"></a>Configuring Samba</h4></div></div><div></div></div><p> The following parameters are available in smb.conf only if your version of samba was built with LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. </p><p>LDAP related smb.conf options: <a class="indexterm" name="id2883191"></a><i class="parameter"><tt>passdb backend</tt></i> = ldapsam:url, <a class="indexterm" name="id2883207"></a><i class="parameter"><tt>ldap ssl</tt></i>, <a class="indexterm" name="id2883220"></a><i class="parameter"><tt>ldap admin dn</tt></i>, <a class="indexterm" name="id2883234"></a><i class="parameter"><tt>ldap suffix</tt></i>, <a class="indexterm" name="id2883248"></a><i class="parameter"><tt>ldap filter</tt></i>, <a class="indexterm" name="id2883262"></a><i class="parameter"><tt>ldap machine suffix</tt></i>, <a class="indexterm" name="id2883276"></a><i class="parameter"><tt>ldap user suffix</tt></i>, <a class="indexterm" name="id2883290"></a><i class="parameter"><tt>ldap delete dn</tt></i>, <a class="indexterm" name="id2883304"></a><i class="parameter"><tt>ldap passwd sync</tt></i>, <a class="indexterm" name="id2883318"></a><i class="parameter"><tt>ldap trust ids</tt></i>. </p><p> These are described in the <tt class="filename">smb.conf</tt> man page and so will not be repeated here. However, a sample smb.conf file for use with an LDAP directory could appear as </p><p> </p><div class="example"><a name="id2883349"></a><p class="title"><b>Example�11.2.�Configuration with LDAP</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr><tr><td><i class="parameter"><tt>encrypt passwords = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = TASHTEGO</tt></i></td></tr><tr><td><i class="parameter"><tt>workgroup = NARNIA</tt></i></td></tr><tr><td># ldap related parameters</td></tr><tr><td># define the DN to use when binding to the directory servers</td></tr><tr><td># The password for this DN is not stored in smb.conf. Rather it</td></tr><tr><td># must be set by using 'smbpasswd -w <i class="replaceable"><tt>secretpw</tt></i>' to store the</td></tr><tr><td># passphrase in the secrets.tdb file. If the "ldap admin dn" values</td></tr><tr><td># change, this password will need to be reset.</td></tr><tr><td><i class="parameter"><tt>ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td># Define the SSL option when connecting to the directory</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><i class="parameter"><tt>ldap ssl = start tls</tt></i></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><i class="parameter"><tt>passdb backend = ldapsam:ldap://funball.samba.org</tt></i></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><i class="parameter"><tt>ldap delete dn = no</tt></i></td></tr><tr><td># the machine and user suffix added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><i class="parameter"><tt>ldap user suffix = ou=People</tt></i></td></tr><tr><td><i class="parameter"><tt>ldap machine suffix = ou=Systems</tt></i></td></tr><tr><td># Trust unix account information in LDAP</td></tr><tr><td># (see the smb.conf manpage for details)</td></tr><tr><td><i class="parameter"><tt>ldap trust ids = Yes</tt></i></td></tr><tr><td># specify the base DN to use when searching the directory</td></tr><tr><td><i class="parameter"><tt>ldap suffix = "ou=people,dc=samba,dc=org"</tt></i></td></tr><tr><td># generally the default ldap search filter is ok</td></tr><tr><td><i class="parameter"><tt>ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"</tt></i></td></tr></table></div><p> </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883574"></a>Accounts and Groups management</h4></div></div><div></div></div><p> As users accounts are managed through the sambaSamAccount objectclass, you should modify your existing administration tools to deal with sambaSamAccount attributes. </p><p> Machines accounts are managed with the sambaSamAccount objectclass, just like users accounts. However, it's up to you to store those accounts in a different tree of your LDAP namespace: you should use "ou=Groups,dc=quenya,dc=org" to store groups and "ou=People,dc=quenya,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration file). </p><p> In Samba release 3.0, the group management system is based on POSIX groups. This means that Samba makes use of the posixGroup objectclass. For now, there is no NT-like group system management (global and local groups). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883611"></a>Security and sambaSamAccount</h4></div></div><div></div></div><p> There are two important points to remember when discussing the security of sambaSamAccount entries in the directory. </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the lmPassword or ntPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to view the lmPassword or ntPassword attribute values.</p></li></ul></div><p> These password hashes are clear text equivalents and can be used to impersonate the user without deriving the original clear text strings. For more information on the details of LM/NT password hashes, refer to the <a href="#passdb" title="Chapter�11.�Account Information Databases">Account Information Database</a> section of this chapter. </p><p> To remedy the first security issue, the <a class="indexterm" name="id2883671"></a><i class="parameter"><tt>ldap ssl</tt></i> <tt class="filename">smb.conf</tt> parameter defaults to require an encrypted session (<a class="indexterm" name="id2883693"></a><i class="parameter"><tt>ldap ssl</tt></i> = on) using the default port of <tt class="constant">636</tt> when contacting the directory server. When using an OpenLDAP server, it is possible to use the use the StartTLS LDAP extended operation in the place of LDAPS. In either case, you are strongly discouraged to disable this security (<a class="indexterm" name="id2883715"></a><i class="parameter"><tt>ldap ssl</tt></i> = off). </p><p> Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS extended operation. However, the OpenLDAP library still provides support for the older method of securing communication between clients and servers. </p><p> The second security precaution is to prevent non-administrative users from harvesting password hashes from the directory. This can be done using the following ACL in <tt class="filename">slapd.conf</tt>: </p><p> </p><pre class="programlisting"> ## allow the "ldap admin dn" access, but deny everyone else access to attrs=lmPassword,ntPassword by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write by * none </pre><p> </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2883771"></a>LDAP special attributes for sambaSamAccounts</h4></div></div><div></div></div><p> The sambaSamAccount objectclass is composed of the following attributes: </p><p> </p><div class="table"><a name="id2883788"></a><p class="title"><b>Table�11.1.�Attributes in the sambaSamAccount objectclass (LDAP)</b></p><table summary="Attributes in the sambaSamAccount objectclass (LDAP)" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><tt class="constant">sambaLMPassword</tt></td><td align="justify">the LANMAN password 16-byte hash stored as a character representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">sambaNTPassword</tt></td><td align="justify">the NT password hash 16-byte stored as a character representation of a hexadecimal string.</td></tr><tr><td align="left"><tt class="constant">sambaPwdLastSet</tt></td><td align="justify">The integer time in seconds since 1970 when the <tt class="constant">sambaLMPassword</tt> and <tt class="constant">sambaNTPassword</tt> attributes were last set. </td></tr><tr><td align="left"><tt class="constant">sambaAcctFlags</tt></td><td align="justify">string of 11 characters surrounded by square brackets [] representing account flags such as U (user), W(workstation), X(no password expiration), I(Domain trust account), H(Home dir required), S(Server trust account), and D(disabled).</td></tr><tr><td align="left"><tt class="constant">sambaLogonTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaLogoffTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaKickoffTime</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaPwdCanChange</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaPwdMustChange</tt></td><td align="justify">Integer value currently unused</td></tr><tr><td align="left"><tt class="constant">sambaHomeDrive</tt></td><td align="justify">specifies the drive letter to which to map the UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" where X is the letter of the drive to map. Refer to the "logon drive" parameter in the smb.conf(5) man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaLogonScript</tt></td><td align="justify">The sambaLogonScript property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path is relative to the netlogon share. Refer to the <a class="indexterm" name="id2883963"></a><i class="parameter"><tt>logon script</tt></i> parameter in the <tt class="filename">smb.conf</tt> man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaProfilePath</tt></td><td align="justify">specifies a path to the user's profile. This value can be a null string, a local absolute path, or a UNC path. Refer to the <a class="indexterm" name="id2883998"></a><i class="parameter"><tt>logon path</tt></i> parameter in the <tt class="filename">smb.conf</tt> man page for more information.</td></tr><tr><td align="left"><tt class="constant">sambaHomePath</tt></td><td align="justify">The sambaHomePath property specifies the path of the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies a drive letter, sambaHomePath should be a UNC path. The path must be a network UNC path of the form <tt class="filename">\\server\share\directory</tt>. This value can be a null string. Refer to the <b class="command">logon home</b> parameter in the <tt class="filename">smb.conf</tt> man page for more information. </td></tr><tr><td align="left"><tt class="constant">sambaUserWorkstations</tt></td><td align="justify">character string value currently unused. </td></tr><tr><td align="left"><tt class="constant">sambaSID</tt></td><td align="justify">The security identifier(SID) of the user. The windows equivalent of unix uid's.</td></tr><tr><td align="left"><tt class="constant">sambaPrimaryGroupSID</tt></td><td align="justify">the relative identifier (RID) of the primary group of the user.</td></tr><tr><td align="left"><tt class="constant">sambaDomainName</tt></td><td align="justify">domain the user is part of.</td></tr></tbody></table></div><p> </p><p> The majority of these parameters are only used when Samba is acting as a PDC of a domain (refer to the <a href="#samba-pdc" title="Chapter�5.�Domain Control">Samba as a primary domain controller</a> chapter for details on how to configure Samba as a Primary Domain Controller). The following four attributes are only stored with the sambaSamAccount entry if the values are non-default values: </p><div class="itemizedlist"><ul type="disc"><li><p>sambaHomePath</p></li><li><p>sambaLogonScript</p></li><li><p>sambaProfilePath</p></li><li><p>sambaHomeDrive</p></li></ul></div><p> These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume TASHTEGO has now been configured as a PDC and that <a class="indexterm" name="id2884154"></a><i class="parameter"><tt>logon home</tt></i> = \\%L\%u was defined in its <tt class="filename">smb.conf</tt> file. When a user named "becky" logons to the domain, the <a class="indexterm" name="id2884178"></a><i class="parameter"><tt>logon home</tt></i> string is expanded to \\TASHTEGO\becky. If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value of the <a class="indexterm" name="id2884202"></a><i class="parameter"><tt>logon home</tt></i> parameter is used in its place. Samba will only write the attribute value to the directory entry if the value is something other than the default (e.g. <tt class="filename">\\MOBY\becky</tt>). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884228"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div><div></div></div><p> The following is a working LDIF with the inclusion of the posixAccount objectclass: </p><p> </p><pre class="programlisting"> dn: uid=guest2, ou=people,dc=quenya,dc=org sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 sambaPwdMustChange: 2147483647 sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513 sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE sambaPwdLastSet: 1010179124 sambaLogonTime: 0 objectClass: sambaSamAccount uid: guest2 sambaKickoffTime: 2147483647 sambaAcctFlags: [UX ] sambaLogoffTime: 2147483647 sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006 sambaPwdCanChange: 0 </pre><p> </p><p> The following is an LDIF entry for using both the sambaSamAccount and posixAccount objectclasses: </p><p> </p><pre class="programlisting"> dn: uid=gcarter, ou=people,dc=quenya,dc=org sambaLogonTime: 0 displayName: Gerald Carter sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201 objectClass: posixAccount objectClass: sambaSamAccount sambaAcctFlags: [UX ] userPassword: {crypt}BpM2ej8Rkzogo uid: gcarter uidNumber: 9000 cn: Gerald Carter loginShell: /bin/bash logoffTime: 2147483647 gidNumber: 100 sambaKickoffTime: 2147483647 sambaPwdLastSet: 1010179230 sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004 homeDirectory: /home/tashtego/gcarter sambaPwdCanChange: 0 sambaPwdMustChange: 2147483647 sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 </pre><p> </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884294"></a>Password synchronisation</h4></div></div><div></div></div><p> Since version 3.0 samba can update the non-samba (LDAP) password stored with an account. When using pam_ldap, this allows changing both unix and windows passwords at once. </p><p>The <a class="indexterm" name="id2884312"></a><i class="parameter"><tt>ldap passwd sync</tt></i> options can have the following values:</p><div class="variablelist"><dl><dt><span class="term">yes</span></dt><dd><p>When the user changes his password, update <tt class="constant">ntPassword</tt>, <tt class="constant">lmPassword</tt> and the <tt class="constant">password</tt> fields.</p></dd><dt><span class="term">no</span></dt><dd><p>Only update <tt class="constant">ntPassword</tt> and <tt class="constant">lmPassword</tt>.</p></dd><dt><span class="term">only</span></dt><dd><p>Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers. <sup>[<a name="id2884396" href="#ftn.id2884396">3</a>]</sup></p></dd></dl></div><p>More information can be found in the smb.conf manpage. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2884412"></a>MySQL</h3></div></div><div></div></div><p> Every so often someone will come along with a great new idea. Storing of user accounts in an SQL backend is one of them. Those who want to do this are in the best position to know what the specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt to document every nitty little detail why certain things of marginal utility to the bulk of Samba users might make sense to the rest. In any case, the following instructions should help the determined SQL user to implement a working system. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884433"></a>Creating the database</h4></div></div><div></div></div><p> You either can set up your own table and specify the field names to pdb_mysql (see below for the column names) or use the default table. The file <tt class="filename">examples/pdb/mysql/mysql.dump</tt> contains the correct queries to create the required tables. Use the command : </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>mysql -u<i class="replaceable"><tt>username</tt></i> -h<i class="replaceable"><tt>hostname</tt></i> -p<i class="replaceable"><tt>password</tt></i> \ <i class="replaceable"><tt>databasename</tt></i> < <tt class="filename">/path/to/samba/examples/pdb/mysql/mysql.dump</tt></tt></b> </pre><p> </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2884501"></a>Configuring</h4></div></div><div></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><p>Add a the following to the <a class="indexterm" name="id2884517"></a><i class="parameter"><tt>passdb backend</tt></i> variable in your <tt class="filename">smb.conf</tt>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>passdb backend = [other-plugins] mysql:identifier [other-plugins]</tt></i></td></tr></table><p> </p><p>The identifier can be any string you like, as long as it doesn't collide with the identifiers of other plugins or other instances of pdb_mysql. If you specify multiple pdb_mysql.so entries in <a class="indexterm" name="id2884560"></a><i class="parameter"><tt>passdb backend</tt></i>, you also need to use different identifiers! </p><p> Additional options can be given through the <tt class="filename">smb.conf</tt> file in the <i class="parameter"><tt>[global]</tt></i> section. </p><p> </p><div class="table"><a name="id2884599"></a><p class="title"><b>Table�11.2.�Basic smb.conf options for MySQL passdb backend</b></p><table summary="Basic smb.conf options for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">mysql host</td><td align="justify">host name, defaults to 'localhost'</td></tr><tr><td align="left">mysql password</td><td align="justify">�</td></tr><tr><td align="left">mysql user</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql database</td><td align="justify">defaults to 'samba'</td></tr><tr><td align="left">mysql port</td><td align="justify">defaults to 3306</td></tr><tr><td align="left">table</td><td align="justify">Name of the table containing users</td></tr></tbody></table></div><p> </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Since the password for the MySQL user is stored in the <tt class="filename">smb.conf</tt> file, you should make the <tt class="filename">smb.conf</tt> file readable only to the user that runs Samba This is considered a security bug and will be fixed soon. </p></div><p>Names of the columns in this table (I've added column types those columns should have first):</p><p> </p><div class="table"><a name="id2884730"></a><p class="title"><b>Table�11.3.�MySQL field names for MySQL passdb backend</b></p><table summary="MySQL field names for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="left">Type</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">logon time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">logoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">kickoff time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass last set time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass can change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">pass must change time column</td><td align="left">int(9)</td><td align="justify">�</td></tr><tr><td align="left">username column</td><td align="left">varchar(255)</td><td align="justify">unix username</td></tr><tr><td align="left">domain column</td><td align="left">varchar(255)</td><td align="justify">NT domain user is part of</td></tr><tr><td align="left">nt username column</td><td align="left">varchar(255)</td><td align="justify">NT username</td></tr><tr><td align="left">fullname column</td><td align="left">varchar(255)</td><td align="justify">Full name of user</td></tr><tr><td align="left">home dir column</td><td align="left">varchar(255)</td><td align="justify">UNIX homedir path</td></tr><tr><td align="left">dir drive column</td><td align="left">varchar(2)</td><td align="justify">Directory drive path (eg: 'H:')</td></tr><tr><td align="left">logon script column</td><td align="left">varchar(255)</td><td align="justify">Batch file to run on client side when logging on</td></tr><tr><td align="left">profile path column</td><td align="left">varchar(255)</td><td align="justify">Path of profile</td></tr><tr><td align="left">acct desc column</td><td align="left">varchar(255)</td><td align="justify">Some ASCII NT user data</td></tr><tr><td align="left">workstations column</td><td align="left">varchar(255)</td><td align="justify">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="left">unknown string column</td><td align="left">varchar(255)</td><td align="justify">unknown string</td></tr><tr><td align="left">munged dial column</td><td align="left">varchar(255)</td><td align="justify">?</td></tr><tr><td align="left">user sid column</td><td align="left">varchar(255)</td><td align="justify">NT user SID</td></tr><tr><td align="left">group sid column</td><td align="left">varchar(255)</td><td align="justify">NT group ID</td></tr><tr><td align="left">lanman pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted lanman password</td></tr><tr><td align="left">nt pass column</td><td align="left">varchar(255)</td><td align="justify">encrypted nt passwd</td></tr><tr><td align="left">plain pass column</td><td align="left">varchar(255)</td><td align="justify">plaintext password</td></tr><tr><td align="left">acct control column</td><td align="left">int(9)</td><td align="justify">nt user data</td></tr><tr><td align="left">unknown 3 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">logon divs column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">hours len column</td><td align="left">int(9)</td><td align="justify">?</td></tr><tr><td align="left">unknown 5 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr><tr><td align="left">unknown 6 column</td><td align="left">int(9)</td><td align="justify">unknown</td></tr></tbody></table></div><p> </p><p> Eventually, you can put a colon (:) after the name of each column, which should specify the column to update when updating the table. You can also specify nothing behind the colon - then the data from the field will not be updated. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885120"></a>Using plaintext passwords or encrypted password</h4></div></div><div></div></div><p> I strongly discourage the use of plaintext passwords, however, you can use them: </p><p> If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. </p><p> If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2885150"></a>Getting non-column data from the table</h4></div></div><div></div></div><p> It is possible to have not all data in the database and making some 'constant'. </p><p> For example, you can set 'identifier:fullname column' to : <b class="command">CONCAT(First_name,' ',Sur_name)</b> </p><p> Or, set 'identifier:workstations column' to : <b class="command">NULL</b></p><p>See the MySQL documentation for more language constructs.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="XMLpassdb"></a>XML</h3></div></div><div></div></div><p>This module requires libxml2 to be installed.</p><p>The usage of pdb_xml is pretty straightforward. To export data, use: </p><p> <tt class="prompt">$ </tt> <b class="userinput"><tt>pdbedit -e xml:filename</tt></b> </p><p> (where filename is the name of the file to put the data in) </p><p> To import data, use: <tt class="prompt">$ </tt> <b class="userinput"><tt>pdbedit -i xml:filename</tt></b> </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885260"></a>Common Errors</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885267"></a>Users can not logon</h3></div></div><div></div></div><p>“<span class="quote">I've installed samba, but now I can't log on with my unix account!</span>”</p><p>Make sure your user has been added to the current samba <a class="indexterm" name="id2885285"></a><i class="parameter"><tt>passdb backend</tt></i>. Read the section <a href="#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885312"></a>Users being added to wrong backend database</h3></div></div><div></div></div><p> A few complaints have been received from users that just moved to Samba-3. The following <tt class="filename">smb.conf</tt> file entries were causing problems, new accounts were being added to the old smbpasswd file, not to the tdbsam passdb.tdb file: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>passdb backend = smbpasswd, tdbsam</tt></i></td></tr><tr><td>...</td></tr></table><p> </p><p> Samba will add new accounts to the first entry in the <span class="emphasis"><em>passdb backend</em></span> parameter entry. If you want to update to the tdbsam, then change the entry to: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[globals]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>passdb backend = tdbsam, smbpasswd</tt></i></td></tr><tr><td>...</td></tr></table><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2885422"></a>auth methods does not work</h3></div></div><div></div></div><p> If you explicitly set an <a class="indexterm" name="id2885433"></a><i class="parameter"><tt>auth methods</tt></i> parameter, guest must be specified as the first entry on the line. Eg: <a class="indexterm" name="id2885450"></a><i class="parameter"><tt>auth methods</tt></i> = guest sam. </p><p> This is the exact opposite of the requirement for the <a class="indexterm" name="id2885469"></a><i class="parameter"><tt>passdb backend</tt></i> option, where it must be the <span class="emphasis"><em>LAST</em></span> parameter on the line. </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2884396" href="#id2884396">3</a>] </sup>Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter�12.�Mapping MS Windows and UNIX Groups</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jean Fran�ois</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2885652">Features and Benefits</a></dt><dt><a href="#id2885887">Discussion</a></dt><dd><dl><dt><a href="#id2886122">Example Configuration</a></dt></dl></dd><dt><a href="#id2886189">Configuration Scripts</a></dt><dd><dl><dt><a href="#id2886202">Sample smb.conf add group script</a></dt><dt><a href="#id2886288">Script to configure Group Mapping</a></dt></dl></dd><dt><a href="#id2886372">Common Errors</a></dt><dd><dl><dt><a href="#id2886386">Adding Groups Fails</a></dt><dt><a href="#id2886455">Adding MS Windows Groups to MS Windows Groups Fails</a></dt><dt><a href="#id2886481">Adding Domain Users to the Power Users group</a></dt></dl></dd></dl></div><a class="indexterm" name="id2885580"></a><p> Starting with Samba-3, new group mapping functionality is available to create associations between Windows group SIDs and UNIX groups. The <b class="command">groupmap</b> subcommand included with the <span class="application">net</span> tool can be used to manage these associations. </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> The first immediate reason to use the group mapping on a Samba PDC, is that <a class="indexterm" name="id2885620"></a> the <i class="parameter"><tt>domain admin group</tt></i> has been removed and should no longer be specified in <tt class="filename">smb.conf</tt>. This parameter was used to give the listed users membership in the <tt class="constant">Domain Admins</tt> Windows group which gave local admin rights on their workstations (in default configurations). </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885652"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba allows the administrator to create MS Windows NT4 / 200x group accounts and to arbitrarily associate them with UNIX/Linux group accounts. </p><a class="indexterm" name="id2885667"></a><a class="indexterm" name="id2885676"></a><p> Group accounts can be managed using the MS Windows NT4 or MS Windows 200x / XP Professional MMC tools. Appropriate interface scripts should be provided in <tt class="filename">smb.conf</tt> if it is desired that UNIX / Linux system accounts should be automatically created when these tools are used. In the absence of these scripts, and so long as winbind is running, Samba accounts group accounts that are created using these tools will be allocated UNIX UIDs/GIDs from the parameters set by the <a class="indexterm" name="id2885702"></a><i class="parameter"><tt>idmap uid</tt></i>/<a class="indexterm" name="id2885715"></a><i class="parameter"><tt>idmap gid</tt></i> settings in the <tt class="filename">smb.conf</tt> file. </p><div class="figure"><a name="idmap-group-diag"></a><p class="title"><b>Figure�12.1.�IDMAP groups</b></p><div class="mediaobject"><img src="projdoc/imagefiles/idmap-groups.png" width="270" alt="IDMAP groups"></div></div><a class="indexterm" name="id2885785"></a><a class="indexterm" name="id2885792"></a><p> Administrators should be aware that where <tt class="filename">smb.conf</tt> group interface scripts make direct calls to the UNIX/Linux system tools (eg: the shadow utilities, <b class="command">groupadd</b>, <b class="command">groupdel</b>, <b class="command">groupmod</b>) then the resulting UNIX/Linux group names will be subject to any limits imposed by these tools. If the tool does NOT allow upper case characters or space characters, then the creation of an MS Windows NT4 / 200x style group of <span class="emphasis"><em>Engineering Managers</em></span> will attempt to create an identically named UNIX/Linux group, an attempt that will of course fail! </p><a class="indexterm" name="id2885845"></a><a class="indexterm" name="id2885853"></a><p> There are several possible work-arounds for the operating system tools limitation. One method is to use a script that generates a name for the UNIX/Linux system group that fits the operating system limits, and that then just passes the UNIX/Linux group id (GID) back to the calling Samba interface. This will provide a dynamic work-around solution. </p><p> Another work-around is to manually create a UNIX/Linux group, then manually create the MS Windows NT4 / 200x group on the Samba server and then use the <b class="command">net groupmap</b> tool to connect the two to each other. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2885887"></a>Discussion</h2></div></div><div></div></div><p> When installing <span class="application">MS Windows NT4 / 200x</span> on a computer, the installation program creates default users and groups, notably the <tt class="constant">Administrators</tt> group, and gives that group privileges necessary privileges to perform essential system tasks. eg: Ability to change the date and time or to kill (or close) any process running on the local machine. </p><a class="indexterm" name="id2885916"></a><p> The 'Administrator' user is a member of the 'Administrators' group, and thus inherits 'Administrators' group privileges. If a 'joe' user is created to be a member of the 'Administrator' group, 'joe' has exactly the same rights as 'Administrator'. </p><p> When an MS Windows NT4 / W200x is made a domain member, the "Domain Admins" group of the PDC is added to the local 'Administrators' group of the workstation. Every member of the 'Domain Administrators' group inherits the rights of the local 'Administrators' group when logging on the workstation. </p><p> The following steps describe how to make Samba PDC users members of the 'Domain Admins' group? </p><div class="orderedlist"><ol type="1"><li><p> create a unix group (usually in <tt class="filename">/etc/group</tt>), let's call it domadm </p></li><li><p>add to this group the users that must be Administrators. For example if you want joe, john and mary, your entry in <tt class="filename">/etc/group</tt> will look like: </p><pre class="programlisting"> domadm:x:502:joe,john,mary </pre><p> </p></li><li><p> Map this domadm group to the "Domain Admins" group by running the command: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</tt></b> </pre><p> </p><a class="indexterm" name="id2886039"></a><p> The quotes around "Domain Admins" are necessary due to the space in the group name. Also make sure to leave no whitespace surrounding the equal character (=). </p></li></ol></div><p> Now joe, john and mary are domain administrators! </p><a class="indexterm" name="id2886065"></a><p> It is possible to map any arbitrary UNIX group to any Windows NT4 / 200x group as well as making any UNIX group a Windows domain group. For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine, you would flag that group as a domain group by running the following on the Samba PDC: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</tt></b> </pre><p> </p><p> Be aware that the RID parameter is a unsigned 32 bit integer that should normally start at 1000. However, this rid must not overlap with any RID assigned to a user. Verifying this is done differently depending on the passdb backend you are using. Future versions of the tools may perform the verification automatically, but for now the burden is on you. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886122"></a>Example Configuration</h3></div></div><div></div></div><p> You can list the various groups in the mapping database by executing <b class="command">net groupmap list</b>. Here is an example: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt> <b class="userinput"><tt>net groupmap list</tt></b> System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest </pre><p> </p><p> For complete details on <b class="command">net groupmap</b>, refer to the net(8) man page. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886189"></a>Configuration Scripts</h2></div></div><div></div></div><p> Everyone needs tools. Some of us like to create our own, others prefer to use canned tools (ie: prepared by someone else for general use). </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886202"></a>Sample <tt class="filename">smb.conf</tt> add group script</h3></div></div><div></div></div><p> A script to create complying group names for use by the Samba group interfaces: </p><p> </p><div class="example"><a name="id2886226"></a><p class="title"><b>Example�12.1.�smbgrpadd.sh</b></p><pre class="programlisting"> #!/bin/bash # Add the group using normal system groupadd tool. groupadd smbtmpgrp00 thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3` # Now change the name to what we want for the MS Windows networking end cp /etc/group /etc/group.bak cat /etc/group.bak | sed s/smbtmpgrp00/$1/g > /etc/group # Now return the GID as would normally happen. echo $thegid exit 0 </pre></div><p> </p><p> The <tt class="filename">smb.conf</tt> entry for the above script would look like: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>add group script = /path_to_tool/smbgrpadd.sh %g</tt></i></td></tr></table><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886288"></a>Script to configure Group Mapping</h3></div></div><div></div></div><p> In our example we have created a UNIX/Linux group called <span class="emphasis"><em>ntadmin</em></span>. Our script will create the additional groups <span class="emphasis"><em>Orks</em></span>, <span class="emphasis"><em>Elves</em></span>, <span class="emphasis"><em>Gnomes</em></span>: </p><p> </p><pre class="programlisting"> #!/bin/bash net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin net groupmap modify ntgroup="Domain Users" unixgroup=users net groupmap modify ntgroup="Domain Guests" unixgroup=nobody net groupmap modify ntgroup="Administrators" unixgroup=root net groupmap modify ntgroup="Users" unixgroup=users net groupmap modify ntgroup="Guests" unixgroup=nobody net groupmap modify ntgroup="System Operators" unixgroup=sys net groupmap modify ntgroup="Account Operators" unixgroup=root net groupmap modify ntgroup="Backup Operators" unixgroup=bin net groupmap modify ntgroup="Print Operators" unixgroup=lp net groupmap modify ntgroup="Replicators" unixgroup=daemon net groupmap modify ntgroup="Power Users" unixgroup=sys groupadd Orks groupadd Elves groupadd Gnomes net groupmap add ntgroup="Orks" unixgroup=Orks type=d net groupmap add ntgroup="Elves" unixgroup=Elves type=d net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d </pre><p> </p><p> Of course it is expected that the administrator will modify this to suit local needs. For information regarding the use of the <b class="command">net groupmap</b> tool please refer to the man page. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886372"></a>Common Errors</h2></div></div><div></div></div><p> At this time there are many little surprises for the unwary administrator. In a real sense it is imperative that every step of automated control scripts must be carefully tested manually before putting them into active service. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886386"></a>Adding Groups Fails</h3></div></div><div></div></div><p> This is a common problem when the <b class="command">groupadd</b> is called directly by the Samba interface script for the <a class="indexterm" name="id2886406"></a><i class="parameter"><tt>add group script</tt></i> in the <tt class="filename">smb.conf</tt> file. </p><p> The most common cause of failure is an attempt to add an MS Windows group account that has either an upper case character and/or a space character in it. </p><p> There are three possible work-arounds. Firstly, use only group names that comply with the limitations of the UNIX/Linux <b class="command">groupadd</b> system tool. The second involves use of the script mentioned earlier in this chapter, and the third option is to manually create a UNIX/Linux group account that can substitute for the MS Windows group name, then use the procedure listed above to map that group to the MS Windows group. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886455"></a>Adding MS Windows Groups to MS Windows Groups Fails</h3></div></div><div></div></div><a class="indexterm" name="id2886463"></a><p> Samba-3 does NOT support nested groups from the MS Windows control environment. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886481"></a>Adding <span class="emphasis"><em>Domain Users</em></span> to the <span class="emphasis"><em>Power Users</em></span> group</h3></div></div><div></div></div><p>“<span class="quote"> What must I do to add Domain Users to the Power Users group? </span>”</p><p> The Power Users group is a group that is local to each Windows 200x / XP Professional workstation. You can not add the Domain Users group to the Power Users group automatically, this must be done on each workstation by logging in as the local workstation <span class="emphasis"><em>administrator</em></span> and then using click on Start / Control Panel / Users and Passwords now click on the 'Advanced' tab, then on the 'Advanced' Button. </p><a class="indexterm" name="id2886519"></a><p> Now click on 'Groups', then double click on 'Power Users'. This will launch the panel to add users or groups to the local machine 'Power Uses' group. Click on the 'Add' button, select the domain from which the 'Domain Users' group is to be added, double click on the 'Domain Users' group, then click on the 'Ok' button. Note: If a logon box is presented during this process please remember to enter the connect as DOMAIN\UserName. ie: For the domain MIDEARTH and the user 'root' enter MIDEARTH\root. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="AccessControls"></a>Chapter�13.�File, Directory and Share Access Controls</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">May 10, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2886736">Features and Benefits</a></dt><dt><a href="#id2886866">File System Access Controls</a></dt><dd><dl><dt><a href="#id2886902">MS Windows NTFS Comparison with UNIX File Systems</a></dt><dt><a href="#id2887207">Managing Directories</a></dt><dt><a href="#id2887301">File and Directory Access Control</a></dt></dl></dd><dt><a href="#id2887513">Share Definition Access Controls</a></dt><dd><dl><dt><a href="#id2887541">User and Group Based Controls</a></dt><dt><a href="#id2887963">File and Directory Permissions Based Controls</a></dt><dt><a href="#id2888342">Miscellaneous Controls</a></dt></dl></dd><dt><a href="#id2888722">Access Controls on Shares</a></dt><dd><dl><dt><a href="#id2888794">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2889094">MS Windows Access Control Lists and UNIX Interoperability</a></dt><dd><dl><dt><a href="#id2889102">Managing UNIX permissions Using NT Security Dialogs</a></dt><dt><a href="#id2889146">Viewing File Security on a Samba Share</a></dt><dt><a href="#id2889226">Viewing file ownership</a></dt><dt><a href="#id2889358">Viewing File or Directory Permissions</a></dt><dt><a href="#id2889603">Modifying file or directory permissions</a></dt><dt><a href="#id2889768">Interaction with the standard Samba create mask parameters</a></dt><dt><a href="#id2890164">Interaction with the standard Samba file attribute mapping</a></dt></dl></dd><dt><a href="#id2890260">Common Errors</a></dt><dd><dl><dt><a href="#id2890274">Users can not write to a public share</a></dt><dt><a href="#id2890703">I have set force user but Samba still makes root the owner of all the files I touch!</a></dt><dt><a href="#id2890755">MS Word with Samba changes owner of file</a></dt></dl></dd></dl></div><a class="indexterm" name="id2886659"></a><p> Advanced MS Windows users are frequently perplexed when file, directory and share manipulation of resources shared via Samba do not behave in the manner they might expect. MS Windows network administrators are often confused regarding network access controls and how to provide users with the access they need while protecting resources from unauthorised access. </p><p> Many UNIX administrators are unfamiliar with the MS Windows environment and in particular have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file and directory access permissions. </p><p> The problem lies in the differences in how file and directory permissions and controls work between the two environments. This difference is one that Samba can not completely hide, even though it does try to bridge the chasm to a degree. </p><a class="indexterm" name="id2886695"></a><p> POSIX Access Control List technology has been available (along with Extended Attributes) for UNIX for many years, yet there is little evidence today of any significant use. This explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows administrators are astounded at this given that ACLs were a foundational capability of the now decade old MS Windows NT operating system. </p><p> The purpose of this chapter is to present each of the points of control that are possible with Samba-3 in the hope that this will help the network administrator to find the optimum method for delivering the best environment for MS Windows desktop users. </p><p> This is an opportune point to mention that Samba was created to provide a means of interoperability and interchange of data between differing operating environments. Samba has no intent change UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient level of exchange of data between the two environments. What is available today extends well beyond early plans and expectations, yet the gap continues to shrink. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886736"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba offers a lot of flexibility in file system access management. These are the key access control facilities present in Samba today: </p><div class="itemizedlist"><p class="title"><b>Samba Access Control Facilities</b></p><ul type="disc"><li><p> <span class="emphasis"><em>UNIX File and Directory Permissions</em></span> </p><p> Samba honours and implements UNIX file system access controls. Users who access a Samba server will do so as a particular MS Windows user. This information is passed to the Samba server as part of the logon or connection setup process. Samba uses this user identity to validate whether or not the user should be given access to file system resources (files and directories). This chapter provides an overview for those to whom the UNIX permissions and controls are a little strange or unknown. </p></li><li><p> <span class="emphasis"><em>Samba Share Definitions</em></span> </p><p> In configuring share settings and controls in the <tt class="filename">smb.conf</tt> file the network administrator can exercise over-rides to native file system permissions and behaviours. This can be handy and convenient to affect behaviour that is more like what MS Windows NT users expect but it is seldom the <span class="emphasis"><em>best</em></span> way to achieve this. The basic options and techniques are described herein. </p></li><li><p> <span class="emphasis"><em>Samba Share ACLs</em></span> </p><p> Just like it is possible in MS Windows NT to set ACLs on shares themselves, so it is possible to do this in Samba. Very few people make use of this facility, yet it remains on of the easiest ways to affect access controls (restrictions) and can often do so with minimum invasiveness compared with other methods. </p></li><li><p> <span class="emphasis"><em>MS Windows ACLs through UNIX POSIX ACLs</em></span> </p><p> The use of POSIX ACLs on UNIX/Linux is possible ONLY if the underlying operating system supports them. If not, then this option will not be available to you. Current UNIX technology platforms have native support for POSIX ACLs. There are patches for the Linux kernel that provide this also. Sadly, few Linux platforms ship today with native ACLs and Extended Attributes enabled. This chapter has pertinent information for users of platforms that support them. </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2886866"></a>File System Access Controls</h2></div></div><div></div></div><p> Perhaps the most important recognition to be made is the simple fact that MS Windows NT4 / 200x / XP implement a totally divergent file system technology from what is provided in the UNIX operating system environment. Firstly we should consider what the most significant differences are, then we shall look at how Samba helps to bridge the differences. </p><a class="indexterm" name="id2886885"></a><a class="indexterm" name="id2886894"></a><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2886902"></a>MS Windows NTFS Comparison with UNIX File Systems</h3></div></div><div></div></div><p> Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions and permissions. It also means that if the MS Windows networking environment requires file system behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating that in a transparent and consistent manner. </p><p> It is good news that Samba does this to a very large extent and on top of that provides a high degree of optional configuration to over-ride the default behaviour. We will look at some of these over-rides, but for the greater part we will stay within the bounds of default behaviour. Those wishing to explore to depths of control ability should review the <tt class="filename">smb.conf</tt> man page. </p><div class="variablelist"><p class="title"><b>File System Feature Comparison</b></p><dl><dt><span class="term">Name Space</span></dt><dd><p> MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, UNIX file names may be 1023 characters long. In MS Windows file extensions indicate particular file types, in UNIX this is not so rigorously observed as all names are considered arbitrary. </p><p> What MS Windows calls a Folder, UNIX calls a directory. </p></dd><dt><span class="term">Case Sensitivity</span></dt><dd><p> <a class="indexterm" name="id2886988"></a> MS Windows file names are generally upper case if made up of 8.3 (ie: 8 character file name and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case Insensitive. </p><p> UNIX file and directory names are case sensitive and case preserving. Samba implements the MS Windows file name behaviour, but it does so as a user application. The UNIX file system provides no mechanism to perform case insensitive file name lookups. MS Windows does this by default. This means that Samba has to carry the processing overhead to provide features that are NOT native to the UNIX operating system environment. </p><p> Consider the following, all are unique UNIX names but one single MS Windows file name: <tt class="computeroutput"> MYFILE.TXT MyFile.txt myfile.txt </tt> So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in UNIX they can. So what should Samba do if all three are present? Answer, the one that is lexically first will be accessible to MS Windows users, the others are invisible and unaccessible - any other solution would be suicidal. </p></dd><dt><span class="term">Directory Separators</span></dt><dd><p> MS Windows and DOS uses the back-slash '\' as a directory delimiter, UNIX uses the forward-slash '/' as it's directory delimiter. This is transparently handled by Samba. </p></dd><dt><span class="term">Drive Identification</span></dt><dd><p> MS Windows products support a notion of drive letters, like <b class="command">C:</b> to represent disk partitions. UNIX has NO concept if separate identifiers for file partitions since each such file system is <tt class="filename">mounted</tt> to become part of the over-all directory tree. The UNIX directory tree begins at '/', just like the root of a DOS drive is specified like <b class="command">C:\</b>. </p></dd><dt><span class="term">File Naming Conventions</span></dt><dd><p> MS Windows generally never experiences file names that begin with a '.', while in UNIX these are commonly found in a user's home directory. Files that begin with a '.' are typically either start up files for various UNIX applications, or they may be files that contain start-up configuration data. </p></dd><dt><span class="term">Links and Short-Cuts</span></dt><dd><p> <a class="indexterm" name="id2887139"></a> <a class="indexterm" name="id2887150"></a> <a class="indexterm" name="id2887161"></a> MS Windows make use of "links and Short-Cuts" that are actually special types of files that will redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory links, but they are entirely different from what MS Windows users are used to. </p><p> Symbolic links are files in UNIX that contain the actual location of the data (file OR directory). An operation (like read or write) will operate directly on the file referenced. Symbolic links are also referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows one physical file to be known simultaneously by more than one file name. </p></dd></dl></div><p> There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the purpose of UNIX/Linux training/education. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887207"></a>Managing Directories</h3></div></div><div></div></div><p> There are three basic operations for managing directories, <b class="command">create, delete, rename</b>. </p><div class="table"><a name="id2887226"></a><p class="title"><b>Table�13.1.�Managing directories with unix and windows</b></p><table summary="Managing directories with unix and windows" border="1"><colgroup><col><col><col></colgroup><thead><tr><th align="center">Action</th><th align="center">MS Windows Command</th><th align="center">UNIX Command</th></tr></thead><tbody><tr><td align="center">create</td><td align="center">md folder</td><td align="center">mkdir folder</td></tr><tr><td align="center">delete</td><td align="center">rd folder</td><td align="center">rmdir folder</td></tr><tr><td align="center">rename</td><td align="center">rename oldname newname</td><td align="center">mv oldname newname</td></tr></tbody></table></div><p> </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887301"></a>File and Directory Access Control</h3></div></div><div></div></div><p> The network administrator is strongly advised to read foundational training manuals and reference materials regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions without having to resort to more complex facilities like POSIX Access Control Lists (ACLs) or Extended Attributes (EAs). </p><p> UNIX/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. A UNIX file listing looks as follows:- </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>ls -la</tt></b> total 632 drwxr-xr-x 13 maryo gnomes 816 2003-05-12 22:56 . drwxrwxr-x 37 maryo gnomes 3800 2003-05-12 22:29 .. dr-xr-xr-x 2 maryo gnomes 48 2003-05-12 22:29 muchado02 drwxrwxrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado03 drw-rw-rw- 2 maryo gnomes 48 2003-05-12 22:29 muchado04 d-w--w--w- 2 maryo gnomes 48 2003-05-12 22:29 muchado05 dr--r--r-- 2 maryo gnomes 48 2003-05-12 22:29 muchado06 drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 ---------- 1 maryo gnomes 1242 2003-05-12 22:31 mydata00.lst --w--w--w- 1 maryo gnomes 7754 2003-05-12 22:33 mydata02.lst -r--r--r-- 1 maryo gnomes 21017 2003-05-12 22:32 mydata04.lst -rw-rw-rw- 1 maryo gnomes 41105 2003-05-12 22:32 mydata06.lst <tt class="prompt">$ </tt> </pre><p> </p><p> The columns above represent (from left to right): permissions, number of hard links to file, owner, group, size (bytes), access date, access time, file name. </p><p> An overview of the permissions field can be found in <a href="#access1" title="Figure�13.1.�Overview of unix permissions field">the image below</a>. </p><div class="figure"><a name="access1"></a><p class="title"><b>Figure�13.1.�Overview of unix permissions field</b></p><div class="mediaobject"><img src="projdoc/imagefiles/access1.png" width="270" alt="Overview of unix permissions field"></div></div><p> Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character. </p><div class="example"><a name="id2887436"></a><p class="title"><b>Example�13.1.�Example File</b></p><pre class="programlisting"> -rwxr-x--- Means: The owner (user) can read, write, execute the group can read and execute everyone else can NOT do anything with it </pre></div><p> </p><p> Additional possibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = UNIX Domain Socket. </p><p> The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x), execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s), sticky (t). </p><p> When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner. Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as /tmp, that are world-writable. </p><p> When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or group whose 'set user or group' bit is set. This can be very helpful in setting up directories that for which it is desired that all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file to be exclusively owned by a user who's primary group is not the group that all such users belong to. </p><p> When a directory is set <tt class="constant">drw-r-----</tt> this means that the owner can read and create (write) files in it, but because the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the directory but can NOT create new files. NOTE: If files in the directory are set to be readable and writable for the group, then group members will be able to write to (or delete) them. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2887513"></a>Share Definition Access Controls</h2></div></div><div></div></div><p> The following parameters in the <tt class="filename">smb.conf</tt> file sections that define a share control or affect access controls. Before using any of the following options please refer to the man page for <tt class="filename">smb.conf</tt>. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887541"></a>User and Group Based Controls</h3></div></div><div></div></div><p> User and group based controls can prove very useful. In some situations it is distinctly desirable to affect all file system operations as if a single user is doing this, the use of the <a class="indexterm" name="id2887556"></a><i class="parameter"><tt>force user</tt></i> and <a class="indexterm" name="id2887569"></a><i class="parameter"><tt>force group</tt></i> behaviour will achieve this. In other situations it may be necessary to affect a paranoia level of control to ensure that only particular authorised persons will be able to access a share or it's contents, here the use of the <a class="indexterm" name="id2887587"></a><i class="parameter"><tt>valid users</tt></i> or the <a class="indexterm" name="id2887600"></a><i class="parameter"><tt>invalid users</tt></i> may be most useful. </p><p> As always, it is highly advisable to use the least difficult to maintain and the least ambiguous method for controlling access. Remember, that when you leave the scene someone else will need to provide assistance and if that person finds too great a mess, or if they do not understand what you have done then there is risk of Samba being removed and an alternative solution being adopted. </p><div class="table"><a name="id2887628"></a><p class="title"><b>Table�13.2.�User and Group Based Controls</b></p><table summary="User and Group Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2887684"></a><i class="parameter"><tt>admin users</tt></i></td><td align="justify"><p> List of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). Any user in this list will be able to do anything they like on the share, irrespective of file permissions. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887715"></a><i class="parameter"><tt>force group</tt></i></td><td align="justify"><p> Specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887742"></a><i class="parameter"><tt>force user</tt></i></td><td align="justify"><p> Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. Incorrect use can cause security problems. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887770"></a><i class="parameter"><tt>guest ok</tt></i></td><td align="justify"><p> If this parameter is set for a service, then no password is required to connect to the service. Privileges will be those of the guest account. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887798"></a><i class="parameter"><tt>invalid users</tt></i></td><td align="justify"><p> List of users that should not be allowed to login to this service. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887824"></a><i class="parameter"><tt>only user</tt></i></td><td align="justify"><p> Controls whether connections with usernames not in the user list will be allowed. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887850"></a><i class="parameter"><tt>read list</tt></i></td><td align="justify"><p> List of users that are given read-only access to a service. Users in this list will not be given write access, no matter what the read only option is set to. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887878"></a><i class="parameter"><tt>username</tt></i></td><td align="justify"><p> Refer to the <tt class="filename">smb.conf</tt> man page for more information - this is a complex and potentially misused parameter. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887912"></a><i class="parameter"><tt>valid users</tt></i></td><td align="justify"><p> List of users that should be allowed to login to this service. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2887938"></a><i class="parameter"><tt>write list</tt></i></td><td align="justify"><p> List of users that are given read-write access to a service. </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2887963"></a>File and Directory Permissions Based Controls</h3></div></div><div></div></div><p> The following file and directory permission based controls, if misused, can result in considerable difficulty to diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually re-introduce them in a controlled fashion. </p><div class="table"><a name="id2887984"></a><p class="title"><b>Table�13.3.�File and Directory Permission Based Controls</b></p><table summary="File and Directory Permission Based Controls" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2888039"></a><i class="parameter"><tt>create mask</tt></i></td><td align="justify"><p> Refer to the <tt class="filename">smb.conf</tt> man page. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888071"></a><i class="parameter"><tt>directory mask</tt></i></td><td align="justify"><p> The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories. See also: directory security mask. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888097"></a><i class="parameter"><tt>dos filemode</tt></i></td><td align="justify"><p> Enabling this parameter allows a user who has write access to the file to modify the permissions on it. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888124"></a><i class="parameter"><tt>force create mode</tt></i></td><td align="justify"><p> This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888151"></a><i class="parameter"><tt>force directory mode</tt></i></td><td align="justify"><p> This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888179"></a><i class="parameter"><tt>force directory security mode</tt></i></td><td align="justify"><p> Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888207"></a><i class="parameter"><tt>force security mode</tt></i></td><td align="justify"><p> Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888233"></a><i class="parameter"><tt>hide unreadable</tt></i></td><td align="justify"><p> Prevents clients from seeing the existence of files that cannot be read. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888260"></a><i class="parameter"><tt>hide unwriteable files</tt></i></td><td align="justify"><p> Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888288"></a><i class="parameter"><tt>nt acl support</tt></i></td><td align="justify"><p> This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists. </p></td></tr><tr><td align="left"><a class="indexterm" name="id2888314"></a><i class="parameter"><tt>security mask</tt></i></td><td align="justify"><p> Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file. </p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888342"></a>Miscellaneous Controls</h3></div></div><div></div></div><p> The following are documented because of the prevalence of administrators creating inadvertent barriers to file access by not understanding the full implications of <tt class="filename">smb.conf</tt> file settings. </p><div class="table"><a name="id2888364"></a><p class="title"><b>Table�13.4.�Other Controls</b></p><table summary="Other Controls" border="1"><colgroup><col align="justify"><col align="justify"></colgroup><thead><tr><th align="center">Control Parameter</th><th align="center">Description - Action - Notes</th></tr></thead><tbody><tr><td align="justify"><a class="indexterm" name="id2888419"></a><i class="parameter"><tt>case sensitive</tt></i>, <a class="indexterm" name="id2888433"></a><i class="parameter"><tt>default case</tt></i>, <a class="indexterm" name="id2888447"></a><i class="parameter"><tt>short preserve case</tt></i></td><td align="justify"><p> This means that all file name lookup will be done in a case sensitive manner. Files will be created with the precise filename Samba received from the MS Windows client. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888474"></a><i class="parameter"><tt>csc policy</tt></i></td><td align="justify"><p> Client Side Caching Policy - parallels MS Windows client side file caching capabilities. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888502"></a><i class="parameter"><tt>dont descend</tt></i></td><td align="justify"><p> Allows to specify a comma-delimited list of directories that the server should always show as empty. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888529"></a><i class="parameter"><tt>dos filetime resolution</tt></i></td><td align="justify"><p> This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888555"></a><i class="parameter"><tt>dos filetimes</tt></i></td><td align="justify"><p> DOS and Windows allows users to change file time stamps if they can write to the file. POSIX semantics prevent this. This options allows DOS and Windows behaviour. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888584"></a><i class="parameter"><tt>fake oplocks</tt></i></td><td align="justify"><p> Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888614"></a><i class="parameter"><tt>hide dot files</tt></i>, <a class="indexterm" name="id2888629"></a><i class="parameter"><tt>hide files</tt></i>, <a class="indexterm" name="id2888642"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p> Note: MS Windows Explorer allows over-ride of files marked as hidden so they will still be visible. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888669"></a><i class="parameter"><tt>read only</tt></i></td><td align="justify"><p> If this parameter is yes, then users of a service may not create or modify files in the service's directory. </p></td></tr><tr><td align="justify"><a class="indexterm" name="id2888696"></a><i class="parameter"><tt>veto files</tt></i></td><td align="justify"><p> List of files and directories that are neither visible nor accessible. </p></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2888722"></a>Access Controls on Shares</h2></div></div><div></div></div><p> This section deals with how to configure Samba per share access control restrictions. By default, Samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can connect to a share. In the absence of specific restrictions the default setting is to allow the global user <tt class="constant">Everyone</tt> Full Control (ie: Full control, Change and Read). </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 class="filename">share_info.tdb</tt>. The location of this file on your system will depend on how samba was compiled. The default location for Samba's tdb files is under <tt class="filename">/usr/local/samba/var</tt>. If the <tt class="filename">tdbdump</tt> utility has been compiled and installed on your system, then you can examine the contents of this file by: <b class="userinput"><tt>tdbdump share_info.tdb</tt></b>. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2888794"></a>Share Permissions Management</h3></div></div><div></div></div><p> The best tool for the task is platform dependant. Choose the best tool for your environment. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888808"></a>Windows NT4 Workstation/Server</h4></div></div><div></div></div><p> The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below. </p><div class="procedure"><p class="title"><b>Procedure�13.1.�Instructions</b></p><ol type="1"><li><p> Launch the <span class="application">NT4 Server Manager</span>, click on the Samba server you want to administer, then from the menu select <span class="guimenu">Computer</span>, then click on the <span class="guimenuitem">Shared Directories</span> entry. </p></li><li><p> Now click on the share that you wish to manage, then click on the <span class="guilabel">Properties</span> tab, next click on the <span class="guilabel">Permissions</span> tab. Now you can add or change access control settings as you wish. </p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2888891"></a>Windows 200x/XP</h4></div></div><div></div></div><p> On <span class="application">MS Windows NT4/200x/XP</span> system access control lists on the share itself are set using native tools, usually from file manager. For example, in Windows 200x: right click on the shared folder, then select <span class="guimenuitem">Sharing</span>, then click on <span class="guilabel">Permissions</span>. The default 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 <span class="application">Computer Management</span> snap-in for the Microsoft Management Console (MMC). This tool is located by clicking on <tt class="filename">Control Panel -> Administrative Tools -> Computer Management</tt>. </p><div class="procedure"><p class="title"><b>Procedure�13.2.�Instructions</b></p><ol type="1"><li><p> After launching the MMC with the Computer Management snap-in, click on the menu item <span class="guimenuitem">Action</span>, select <span class="guilabel">Connect to another computer</span>. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. If you where already logged in with administrative privilege this step is not offered. </p></li><li><p> If the Samba server is not shown in the <span class="guilabel">Select Computer</span> box, then type in the name of the target Samba server in the field <span class="guilabel">Name:</span>. Now click on the <span class="guibutton">[+]</span> next to <span class="guilabel">System Tools</span>, then on the <span class="guibutton">[+]</span> next to <span class="guilabel">Shared Folders</span> 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 <span class="guilabel">Share Permissions</span>. 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 <tt class="constant">Everyone</tt> 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 precedence. ie: Everyone with <span class="emphasis"><em>no access</em></span> means that MaryK who is part of the group <tt class="constant">Everyone</tt> will have no access even if this user is given explicit full control access. </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2889094"></a>MS Windows Access Control Lists and UNIX Interoperability</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889102"></a>Managing UNIX permissions Using NT Security Dialogs</h3></div></div><div></div></div><p> Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions. </p><p> Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba administrator can set. </p><p> Samba does not attempt to go beyond POSIX ACLs, so that the various finer-grained access control options provided in Windows are actually ignore. </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 files via Samba is controlled by the operating system file access controls. When trying to figure out file access problems it is vitally important to find the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889146"></a>Viewing File Security on a Samba Share</h3></div></div><div></div></div><p> From an NT4/2000/XP client, single-click with the right mouse button on any file or directory in a Samba mounted drive letter or UNC path. When the menu pops-up, click on the <span class="guilabel">Properties</span> entry at the bottom of the menu. This brings up the file properties dialog box. Click on the tab <span class="guilabel">Security</span> and you will see three buttons, <span class="guibutton">Permissions</span>, <span class="guibutton">Auditing</span>, and <span class="guibutton">Ownership</span>. The <span class="guibutton">Auditing</span> button will cause either an error message <span class="errorname">A requested privilege is not held by the client</span> to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is non-functional with a Samba share at this time, as the only useful button, the <span class="guibutton">Add</span> button will not currently allow a list of users to be seen. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889226"></a>Viewing file ownership</h3></div></div><div></div></div><p> Clicking on the <span class="guibutton">Ownership</span> button brings up a dialog box telling you who owns the given file. The owner name will be of the form: </p><p> <b class="command">"SERVER\user (Long name)"</b> </p><p> Where <i class="replaceable"><tt>SERVER</tt></i> is the NetBIOS name of the Samba server, <i class="replaceable"><tt>user</tt></i> is the user name of the UNIX user who owns the file, and <i class="replaceable"><tt>(Long name)</tt></i> is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). Click on the <span class="guibutton">Close </span> button to remove this dialog. </p><p> If the parameter <a class="indexterm" name="id2889290"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt> then the file owner will be shown as the NT user <tt class="constant">"Everyone"</tt>. </p><p> The <span class="guibutton">Take Ownership</span> button will not allow you to change the ownership of this file to 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="application">Seclib</span> NT security library written by Jeremy Allison of the Samba-Team, available from the main Samba FTP site.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889358"></a>Viewing File or Directory Permissions</h3></div></div><div></div></div><p> The third button is the <span class="guibutton">Permissions</span> button. Clicking on this brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed in the form: </p><p><b class="command">"<i class="replaceable"><tt>SERVER</tt></i>\ <i class="replaceable"><tt>user</tt></i> <i class="replaceable"><tt>(Long name)</tt></i>"</b></p><p>Where <i class="replaceable"><tt>SERVER</tt></i> is the NetBIOS name of the Samba server, <i class="replaceable"><tt>user</tt></i> is the user name of the UNIX user who owns the file, and <i class="replaceable"><tt>(Long name)</tt></i> is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).</p><p> If the parameter <a class="indexterm" name="id2889424"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt> then the file owner will be shown as the NT user <tt class="constant">"Everyone"</tt> and the permissions will be shown as NT "Full Control". </p><p> The permissions field is displayed differently for files and directories, so I'll describe the way file permissions are displayed first. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2889458"></a>File Permissions</h4></div></div><div></div></div><p>The standard UNIX user/group/world triplet and the corresponding "read", "write", "execute" permissions triplets are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into the global NT group <tt class="constant">Everyone</tt>, followed by the list of permissions allowed for UNIX world. The UNIX owner and group permissions are displayed as an NT <span class="guiicon">user</span> icon and an NT <span class="guiicon">local group</span> 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 <tt class="constant">read</tt>, <tt class="constant"> "change"</tt> or <tt class="constant">full control</tt> then usually the permissions will be prefixed by the words <tt class="constant"> "Special Access"</tt> in the NT display list.</p><p>But what happens if the file has no permissions allowed for a particular UNIX user group or world component? In order to allow "no permissions" to be seen and modified then Samba overloads the NT <b class="command">"Take Ownership"</b> ACL attribute (which has no meaning in UNIX) and reports a component with no permissions as having the NT <b class="command">"O"</b> bit set. This was chosen of course to make it look like a zero, meaning zero permissions. More details on the decision behind this will be given below.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2889560"></a>Directory Permissions</h4></div></div><div></div></div><p>Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed in the first set of parentheses in the normal <tt class="constant">"RW"</tt> 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 <tt class="constant"> inherited</tt> permissions that any file created within this directory would inherit.</p><p>Samba synthesises these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file created by Samba on this share would receive.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889603"></a>Modifying file or directory permissions</h3></div></div><div></div></div><p>Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and clicking the <span class="guibutton">OK</span> button. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS attributes that need to also be taken into account.</p><p>If the parameter <a class="indexterm" name="id2889632"></a><i class="parameter"><tt>nt acl support</tt></i> is set to <tt class="constant">false</tt> then any attempt to set security permissions will fail with an <span class="errorname">"Access Denied" </span> message.</p><p>The first thing to note is that the <span class="guibutton">"Add"</span> button will not return a list of users in Samba (it will give an error message of <span class="errorname">The remote procedure call failed and did not execute</span>). This means that you can only manipulate the current user/group/world permissions listed in the dialog box. This actually works quite well as these are the only permissions that UNIX actually has.</p><p>If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT dialog box, then when the <span class="guibutton">OK</span> button is pressed it will be applied as "no permissions" on the UNIX side. If you then view the permissions again the "no permissions" entry will appear as the NT <b class="command">"O"</b> flag, as described above. This allows you to add permissions back to a file or directory once you have removed them from a triplet component.</p><p>As UNIX supports only the "r", "w" and "x" bits of an NT ACL then if other NT security attributes such as "Delete access" are selected then they will be ignored when applied on the Samba server.</p><p>When setting permissions on a directory the second 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 <span class="guilabel">Replace permissions on existing files</span> checkbox in the NT dialog before clicking <span class="guibutton">OK</span>.</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 <span class="guibutton">Remove</span> button, or set the component to only have the special <tt class="constant">Take Ownership</tt> permission (displayed as <b class="command">"O" </b>) highlighted.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2889768"></a>Interaction with the standard Samba create mask parameters</h3></div></div><div></div></div><p>There are four parameters to control interaction with the standard Samba create mask parameters. These are : </p><div class="itemizedlist"><ul type="disc"><li><p><a class="indexterm" name="id2889788"></a><i class="parameter"><tt>security mask</tt></i></p></li><li><p><a class="indexterm" name="id2889805"></a><i class="parameter"><tt>force security mode</tt></i></p></li><li><p><a class="indexterm" name="id2889821"></a><i class="parameter"><tt>directory security mask</tt></i></p></li><li><p><a class="indexterm" name="id2889838"></a><i class="parameter"><tt>force directory security mode</tt></i></p></li></ul></div><p> </p><p>Once a user clicks <span class="guibutton">OK</span> to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triplet set, and then will check the changed permissions for a file against the bits set in the <a class="indexterm" name="id2889868"></a><i class="parameter"><tt>security mask</tt></i> parameter. Any bits that were changed that are not set to '1' in this parameter are left alone in the file permissions.</p><p>Essentially, zero bits in the <a class="indexterm" name="id2889888"></a><i class="parameter"><tt>security mask</tt></i> mask may be treated as a set of bits the user is <span class="emphasis"><em>not</em></span> allowed to change, and one bits are those the user is allowed to change. </p><p>If not set explicitly this parameter is set to the same value as the <a class="indexterm" name="id2889915"></a><i class="parameter"><tt>create mask</tt></i> parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter to 0777.</p><p>Next Samba checks the changed permissions for a file against the bits set in the <a class="indexterm" name="id2889937"></a><i class="parameter"><tt>force security mode</tt></i> parameter. Any bits that were changed that correspond to bits set to '1' in this parameter are forced to be set.</p><p>Essentially, bits set in the <i class="parameter"><tt>force security mode </tt></i> parameter may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is set to the same value as the <a class="indexterm" name="id2889972"></a><i class="parameter"><tt>force create mode</tt></i> parameter. To allow a user to modify all the user/group/world permissions on a file with no restrictions set this parameter to 000.</p><p>The <a class="indexterm" name="id2889993"></a><i class="parameter"><tt>security mask</tt></i> and <i class="parameter"><tt>force security mode</tt></i> parameters are applied to the change request in that order.</p><p>For a directory Samba will perform the same operations as described above for a file except using the parameter <i class="parameter"><tt> directory security mask</tt></i> instead of <i class="parameter"><tt>security mask</tt></i>, and <i class="parameter"><tt>force directory security mode </tt></i> parameter instead of <i class="parameter"><tt>force security mode </tt></i>.</p><p>The <a class="indexterm" name="id2890054"></a><i class="parameter"><tt>directory security mask</tt></i> parameter by default is set to the same value as the <i class="parameter"><tt>directory mask </tt></i> parameter and the <i class="parameter"><tt>force directory security mode</tt></i> parameter by default is set to the same value as the <a class="indexterm" name="id2890085"></a><i class="parameter"><tt>force directory mode</tt></i> parameter. </p><p>In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users to modify the permission bits within that restriction.</p><p>If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't force any particular bits to be set 'on', then set the following parameters in the <tt class="filename">smb.conf</tt> file in that share specific section : </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force security mode = 0</tt></i></td></tr><tr><td><i class="parameter"><tt>directory security mask = 0777</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory security mode = 0</tt></i></td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890164"></a>Interaction with the standard Samba file attribute mapping</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Samba maps some of the DOS attribute bits (such as "read only") into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security dialog and the permission bits set by the file attribute mapping. </p></div><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 <span class="guibutton">OK</span> to get back to the standard attributes tab dialog, and then clicks <span class="guibutton">OK</span> 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 <span class="guibutton">OK</span> to get back to the attributes dialog you should always hit <span class="guibutton">Cancel</span> rather than <span class="guibutton">OK</span> to ensure that your changes are not overridden.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2890260"></a>Common Errors</h2></div></div><div></div></div><p> File, Directory and Share access problems are very common on the mailing list. The following are examples taken from the mailing list in recent times. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890274"></a>Users can not write to a public share</h3></div></div><div></div></div><p> “<span class="quote"> We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root), and there's a public share, on which everyone needs to have permission to create / modify files, but only root can change the file, no one else can. We need to constantly go to server to <b class="userinput"><tt>chgrp -R users *</tt></b> and <b class="userinput"><tt>chown -R nobody *</tt></b> to allow others users to change the file. </span>” </p><p> There are many ways to solve this problem, here are a few hints: </p><div class="procedure"><ol type="1"><li><p> Go to the top of the directory that is shared </p></li><li><p> Set the ownership to what ever public owner and group you want </p><pre class="screen"> <tt class="prompt">$ </tt>find 'directory_name' -type d -exec chown user.group {}\; <tt class="prompt">$ </tt>find 'directory_name' -type d -exec chmod 6775 'directory_name' <tt class="prompt">$ </tt>find 'directory_name' -type f -exec chmod 0775 {} \; <tt class="prompt">$ </tt>find 'directory_name' -type f -exec chown user.group {}\; </pre><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above will set the 'sticky bit' on all directories. Read your UNIX/Linux man page on what that does. It causes the OS to assign to all files created in the directories the ownership of the directory. </p></div></li><li><p> Directory is: <i class="replaceable"><tt>/foodbar</tt></i> </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chown jack.engr /foodbar</tt></b> </pre><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This is the same as doing:</p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chown jack /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>chgrp engr /foodbar</tt></b> </pre></div></li><li><p>Now do: </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>chmod 6775 /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>ls -al /foodbar/..</tt></b> </pre><p> </p><p>You should see: </p><pre class="screen"> drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar </pre><p> </p></li><li><p>Now do: </p><pre class="screen"> <tt class="prompt">$ </tt><b class="userinput"><tt>su - jill</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>cd /foodbar</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>touch Afile</tt></b> <tt class="prompt">$ </tt><b class="userinput"><tt>ls -al</tt></b> </pre><p> </p><p> You should see that the file <tt class="filename">Afile</tt> created by Jill will have ownership and permissions of Jack, as follows: </p><pre class="screen"> -rw-r--r-- 1 jack engr 0 2003-02-04 09:57 Afile </pre><p> </p></li><li><p> Now in your <tt class="filename">smb.conf</tt> for the share add: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>force create mode = 0775</tt></i></td></tr><tr><td><i class="parameter"><tt>force direcrtory mode = 6775</tt></i></td></tr></table><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The above are only needed <span class="emphasis"><em>if</em></span> your users are <span class="emphasis"><em>not</em></span> members of the group you have used. ie: Within the OS do not have write permission on the directory. </p></div><p> An alternative is to set in the <tt class="filename">smb.conf</tt> entry for the share: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>force user = jack</tt></i></td></tr><tr><td><i class="parameter"><tt>force group = engr</tt></i></td></tr></table><p> </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890703"></a>I have set force user but Samba still makes <span class="emphasis"><em>root</em></span> the owner of all the files I touch!</h3></div></div><div></div></div><p> When you have a user in <a class="indexterm" name="id2890720"></a><i class="parameter"><tt>admin users</tt></i>, samba will always do file operations for this user as <span class="emphasis"><em>root</em></span>, even if <a class="indexterm" name="id2890739"></a><i class="parameter"><tt>force user</tt></i> has been set. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2890755"></a>MS Word with Samba changes owner of file</h3></div></div><div></div></div><p> <span class="emphasis"><em>Question:</em></span> “<span class="quote">When userB saves a word document that is owned by userA the updated file is now owned by userB. Why is Samba doing this? How do I fix this?</span>” </p><p> <span class="emphasis"><em>Answer:</em></span> Word does the following when you modify/change a Word document: Word Creates a NEW document with a temporary name, Word then closes the old document and deletes it, Word then renames the new document to the original document name. There is NO mechanism by which Samba CAN IN ANY WAY know that the new document really should be owned by the owners of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able to tell, the file that gets created is a NEW file, not one that the application (Word) is updating. </p><p> There is a work-around to solve the permissions problem. That work-around involves understanding how you can manage file system behaviour from within the <tt class="filename">smb.conf</tt> file, as well as understanding how Unix file systems work. Set on the directory in which you are changing word documents: <b class="command">chmod g+s 'directory_name'</b> This ensures that all files will be created with the group that owns the directory. In smb.conf share declaration section set: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>force create mode = 0660</tt></i></td></tr><tr><td><i class="parameter"><tt>force directory mode = 0770</tt></i></td></tr></table><p> </p><p> These two settings will ensure that all directories and files that get created in the share will be read/writable by the owner and group set on the directory itself. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="locking"></a>Chapter�14.�File and Record Locking</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Roseme</span></h3><div class="affiliation"><span class="orgname">HP Oplocks Usage Recommendations Whitepaper<br></span><div class="address"><p><tt class="email"><<a href="mailto:eric.roseme@hp.com">eric.roseme@hp.com</a>></tt></p></div></div></div></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2891003">Features and Benefits</a></dt><dt><a href="#id2891060">Discussion</a></dt><dd><dl><dt><a href="#id2891204">Opportunistic Locking Overview</a></dt></dl></dd><dt><a href="#id2891921">Samba Opportunistic Locking Control</a></dt><dd><dl><dt><a href="#id2892041">Example Configuration</a></dt></dl></dd><dt><a href="#id2892456">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2892680">Workstation Service Entries</a></dt><dt><a href="#id2892709">Server Service Entries</a></dt></dl></dd><dt><a href="#id2892788">Persistent Data Corruption</a></dt><dt><a href="#id2892817">Common Errors</a></dt><dd><dl><dt><a href="#id2892891">locking.tdb error messages</a></dt><dt><a href="#id2892930">Problems saving files in MS Office on Windows XP</a></dt><dt><a href="#id2892952">Long delays deleting files over network with XP SP1</a></dt></dl></dd><dt><a href="#id2892983">Additional Reading</a></dt></dl></div><p> One area which causes trouble for many network administrators is locking. The extent of the problem is readily evident from searches over the internet. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891003"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba provides all the same locking semantics that MS Windows clients expect and that MS Windows NT4 / 200x servers provide also. </p><p> The term <span class="emphasis"><em>locking</em></span> has exceptionally broad meaning and covers a range of functions that are all categorized under this one term. </p><p> Opportunistic locking is a desirable feature when it can enhance the perceived performance of applications on a networked client. However, the opportunistic locking protocol is not robust, and therefore can encounter problems when invoked beyond a simplistic configuration, or on extended, slow, or faulty networks. In these cases, operating system management of opportunistic locking and/or recovering from repetitive errors can offset the perceived performance advantage that it is intended to provide. </p><p> The MS Windows network administrator needs to be aware that file and record locking semantics (behaviour) can be controlled either in Samba or by way of registry settings on the MS Windows client. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Sometimes it is necessary to disable locking control settings BOTH on the Samba server as well as on each MS Windows client! </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891060"></a>Discussion</h2></div></div><div></div></div><p> There are two types of locking which need to be performed by a SMB server. The first is <span class="emphasis"><em>record locking</em></span> which allows a client to lock a range of bytes in a open file. The second is the <span class="emphasis"><em>deny modes</em></span> that are specified when a file is open. </p><p> Record locking semantics under UNIX are very different from record locking under Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix system call to implement proper record locking between different Samba clients. This can not be fully correct due to several reasons. The simplest is the fact that a Windows client is allowed to lock a byte range up to 2^32 or 2^64, depending on the client OS. The unix locking only supports byte ranges up to 2^31. So it is not possible to correctly satisfy a lock request above 2^31. There are many more differences, too many to be listed here. </p><p> Samba 2.2 and above implements record locking completely independent of the underlying unix system. If a byte range lock that the client requests happens to fall into the range 0-2^31, Samba hands this request down to the UNIX system. All other locks can not be seen by unix anyway. </p><p> Strictly an SMB server should check for locks before every read and write call on a file. Unfortunately with the way fcntl() works this can be slow and may over-stress the <b class="command">rpc.lockd</b>. It is also almost always unnecessary as clients are supposed to independently make locking calls before reads and writes anyway if locking is important to them. By default Samba only makes locking calls when explicitly asked to by a client, but if you set <a class="indexterm" name="id2891128"></a><i class="parameter"><tt>strict locking</tt></i> = yes then it will make lock checking calls on every read and write. </p><p> You can also disable byte range locking completely using <a class="indexterm" name="id2891148"></a><i class="parameter"><tt>locking</tt></i> = no. This is useful for those shares that don't support locking or don't need it (such as cdroms). In this case Samba fakes the return codes of locking calls to tell clients that everything is OK. </p><p> The second class of locking is the <span class="emphasis"><em>deny modes</em></span>. These are set by an application when it opens a file to determine what types of access should be allowed simultaneously with its open. A client may ask for <tt class="constant">DENY_NONE</tt>, <tt class="constant">DENY_READ</tt>, <tt class="constant">DENY_WRITE</tt> or <tt class="constant">DENY_ALL</tt>. There are also special compatibility modes called <tt class="constant">DENY_FCB</tt> and <tt class="constant">DENY_DOS</tt>. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2891204"></a>Opportunistic Locking Overview</h3></div></div><div></div></div><p> Opportunistic locking (Oplocks) is invoked by the Windows file system (as opposed to an API) via registry entries (on the server AND client) for the purpose of enhancing network performance when accessing a file residing on a server. Performance is enhanced by caching the file locally on the client which allows: </p><div class="variablelist"><dl><dt><span class="term">Read-ahead:</span></dt><dd><p> The client reads the local copy of the file, eliminating network latency </p></dd><dt><span class="term">Write caching:</span></dt><dd><p> The client writes to the local copy of the file, eliminating network latency </p></dd><dt><span class="term">Lock caching:</span></dt><dd><p> The client caches application locks locally, eliminating network latency </p></dd></dl></div><p> The performance enhancement of oplocks is due to the opportunity of exclusive access to the file - even if it is opened with deny-none - because Windows monitors the file's status for concurrent access from other processes. </p><div class="variablelist"><p class="title"><b>Windows defines 4 kinds of Oplocks:</b></p><dl><dt><span class="term">Level1 Oplock:</span></dt><dd><p> The redirector sees that the file was opened with deny none (allowing concurrent access), verifies that no other process is accessing the file, checks that oplocks are enabled, then grants deny-all/read-write/exclusive access to the file. The client now performs operations on the cached local file. </p><p> If a second process attempts to open the file, the open is deferred while the redirector "breaks" the original oplock. The oplock break signals the caching client to write the local file back to the server, flush the local locks, and discard read-ahead data. The break is then complete, the deferred open is granted, and the multiple processes can enjoy concurrent file access as dictated by mandatory or byte-range locking options. However, if the original opening process opened the file with a share mode other than deny-none, then the second process is granted limited or no access, despite the oplock break. </p></dd><dt><span class="term">Level2 Oplock:</span></dt><dd><p> Performs like a level1 oplock, except caching is only operative for reads. All other operations are performed on the server disk copy of the file. </p></dd><dt><span class="term">Filter Oplock:</span></dt><dd><p> Does not allow write or delete file access </p></dd><dt><span class="term">Batch Oplock:</span></dt><dd><p> Manipulates file openings and closings - allows caching of file attributes </p></dd></dl></div><p> An important detail is that oplocks are invoked by the file system, not an application API. Therefore, an application can close an oplocked file, but the file system does not relinquish the oplock. When the oplock break is issued, the file system then simply closes the file in preparation for the subsequent open by the second process. </p><p> <span class="emphasis"><em>Opportunistic Locking</em></span> is actually an improper name for this feature. The true benefit of this feature is client-side data caching, and oplocks is merely a notification mechanism for writing data back to the networked storage disk. The limitation of opportunistic locking is the reliability of the mechanism to process an oplock break (notification) between the server and the caching client. If this exchange is faulty (usually due to timing out for any number of reasons) then the client-side caching benefit is negated. </p><p> The actual decision that a user or administrator should consider is whether it is sensible to share amongst multiple users data that will be cached locally on a client. In many cases the answer is no. Deciding when to cache or not cache data is the real question, and thus "opportunistic locking" should be treated as a toggle for client-side caching. Turn it "ON" when client-side caching is desirable and reliable. Turn it "OFF" when client-side caching is redundant, unreliable, or counter-productive. </p><p> Opportunistic locking is by default set to "on" by Samba on all configured shares, so careful attention should be given to each case to determine if the potential benefit is worth the potential for delays. The following recommendations will help to characterize the environment where opportunistic locking may be effectively configured. </p><p> Windows Opportunistic Locking is a lightweight performance-enhancing feature. It is not a robust and reliable protocol. Every implementation of Opportunistic Locking should be evaluated as a tradeoff between perceived performance and reliability. Reliability decreases as each successive rule above is not enforced. Consider a share with oplocks enabled, over a wide area network, to a client on a South Pacific atoll, on a high-availability server, serving a mission-critical multi-user corporate database, during a tropical storm. This configuration will likely encounter problems with oplocks. </p><p> Oplocks can be beneficial to perceived client performance when treated as a configuration toggle for client-side data caching. If the data caching is likely to be interrupted, then oplock usage should be reviewed. Samba enables opportunistic locking by default on all shares. Careful attention should be given to the client usage of shared data on the server, the server network reliability, and the opportunistic locking configuration of each share. n mission critical high availability environments, data integrity is often a priority. Complex and expensive configurations are implemented to ensure that if a client loses connectivity with a file server, a failover replacement will be available immediately to provide continuous data availability. </p><p> Windows client failover behavior is more at risk of application interruption than other platforms because it is dependant upon an established TCP transport connection. If the connection is interrupted - as in a file server failover - a new session must be established. It is rare for Windows client applications to be coded to recover correctly from a transport connection loss, therefore most applications will experience some sort of interruption - at worst, abort and require restarting. </p><p> If a client session has been caching writes and reads locally due to opportunistic locking, it is likely that the data will be lost when the application restarts, or recovers from the TCP interrupt. When the TCP connection drops, the client state is lost. When the file server recovers, an oplock break is not sent to the client. In this case, the work from the prior session is lost. Observing this scenario with oplocks disabled, and the client was writing data to the file server real-time, then the failover will provide the data on disk as it existed at the time of the disconnect. </p><p> In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891533"></a>Exclusively Accessed Shares</h4></div></div><div></div></div><p> Opportunistic locking is most effective when it is confined to shares that are exclusively accessed by a single user, or by only one user at a time. Because the true value of opportunistic locking is the local client caching of data, any operation that interrupts the caching mechanism will cause a delay. </p><p> Home directories are the most obvious examples of where the performance benefit of opportunistic locking can be safely realized. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891558"></a>Multiple-Accessed Shares or Files</h4></div></div><div></div></div><p> As each additional user accesses a file in a share with opportunistic locking enabled, the potential for delays and resulting perceived poor performance increases. When multiple users are accessing a file on a share that has oplocks enabled, the management impact of sending and receiving oplock breaks, and the resulting latency while other clients wait for the caching client to flush data, offset the performance gains of the caching user. </p><p> As each additional client attempts to access a file with oplocks set, the potential performance improvement is negated and eventually results in a performance bottleneck. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891587"></a>UNIX or NFS Client Accessed Files</h4></div></div><div></div></div><p> Local UNIX and NFS clients access files without a mandatory file locking mechanism. Thus, these client platforms are incapable of initiating an oplock break request from the server to a Windows client that has a file cached. Local UNIX or NFS file access can therefore write to a file that has been cached by a Windows client, which exposes the file to likely data corruption. </p><p> If files are shared between Windows clients, and either local UNIX or NFS users, then turn opportunistic locking off. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891613"></a>Slow and/or Unreliable Networks</h4></div></div><div></div></div><p> The biggest potential performance improvement for opportunistic locking occurs when the client-side caching of reads and writes delivers the most differential over sending those reads and writes over the wire. This is most likely to occur when the network is extremely slow, congested, or distributed (as in a WAN). However, network latency also has a very high impact on the reliability of the oplock break mechanism, and thus increases the likelihood of encountering oplock problems that more than offset the potential perceived performance gain. Of course, if an oplock break never has to be sent, then this is the most advantageous scenario to utilize opportunistic locking. </p><p> If the network is slow, unreliable, or a WAN, then do not configure opportunistic locking if there is any chance of multiple users regularly opening the same file. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891646"></a>Multi-User Databases</h4></div></div><div></div></div><p> Multi-user databases clearly pose a risk due to their very nature - they are typically heavily accessed by numerous users at random intervals. Placing a multi-user database on a share with opportunistic locking enabled will likely result in a locking management bottleneck on the Samba server. Whether the database application is developed in-house or a commercially available product, ensure that the share has opportunistic locking disabled. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891676"></a>PDM Data Shares</h4></div></div><div></div></div><p> Process Data Management (PDM) applications such as IMAN, Enovia, and Clearcase, are increasing in usage with Windows client platforms, and therefore SMB data stores. PDM applications manage multi-user environments for critical data security and access. The typical PDM environment is usually associated with sophisticated client design applications that will load data locally as demanded. In addition, the PDM application will usually monitor the data-state of each client. In this case, client-side data caching is best left to the local application and PDM server to negotiate and maintain. It is appropriate to eliminate the client OS from any caching tasks, and the server from any oplock management, by disabling opportunistic locking on the share. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891703"></a>Beware of Force User</h4></div></div><div></div></div><p> Samba includes an <tt class="filename">smb.conf</tt> parameter called <a class="indexterm" name="id2891722"></a><i class="parameter"><tt>force user</tt></i> that changes the user accessing a share from the incoming user to whatever user is defined by the smb.conf variable. If opportunistic locking is enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the user has not explicitly loaded a file. In cases where the network is slow or unreliable, an oplock break can become lost without the user even accessing a file. This can cause apparent performance degradation as the client continually reconnects to overcome the lost oplock break. </p><p> Avoid the combination of the following: </p><div class="itemizedlist"><ul type="disc"><li><p> <a class="indexterm" name="id2891758"></a><i class="parameter"><tt>force user</tt></i> in the <tt class="filename">smb.conf</tt> share configuration. </p></li><li><p> Slow or unreliable networks </p></li><li><p> Opportunistic Locking Enabled </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891795"></a>Advanced Samba Opportunistic Locking Parameters</h4></div></div><div></div></div><p> Samba provides opportunistic locking parameters that allow the administrator to adjust various properties of the oplock mechanism to account for timing and usage levels. These parameters provide good versatility for implementing oplocks in environments where they would likely cause problems. The parameters are: <a class="indexterm" name="id2891812"></a><i class="parameter"><tt>oplock break wait time</tt></i>, <a class="indexterm" name="id2891827"></a><i class="parameter"><tt>oplock contention limit</tt></i>. </p><p> For most users, administrators, and environments, if these parameters are required, then the better option is to simply turn oplocks off. The samba SWAT help text for both parameters reads "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." This is good advice. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2891854"></a>Mission Critical High Availability</h4></div></div><div></div></div><p> In mission critical high availability environments, data integrity is often a priority. Complex and expensive configurations are implemented to ensure that if a client loses connectivity with a file server, a failover replacement will be available immediately to provide continuous data availability. </p><p> Windows client failover behavior is more at risk of application interruption than other platforms because it is dependant upon an established TCP transport connection. If the connection is interrupted - as in a file server failover - a new session must be established. It is rare for Windows client applications to be coded to recover correctly from a transport connection loss, therefore most applications will experience some sort of interruption - at worst, abort and require restarting. </p><p> If a client session has been caching writes and reads locally due to opportunistic locking, it is likely that the data will be lost when the application restarts, or recovers from the TCP interrupt. When the TCP connection drops, the client state is lost. When the file server recovers, an oplock break is not sent to the client. In this case, the work from the prior session is lost. Observing this scenario with oplocks disabled, and the client was writing data to the file server real-time, then the failover will provide the data on disk as it existed at the time of the disconnect. </p><p> In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2891921"></a>Samba Opportunistic Locking Control</h2></div></div><div></div></div><p> Opportunistic Locking is a unique Windows file locking feature. It is not really file locking, but is included in most discussions of Windows file locking, so is considered a de facto locking feature. Opportunistic Locking is actually part of the Windows client file caching mechanism. It is not a particularly robust or reliable feature when implemented on the variety of customized networks that exist in enterprise computing. </p><p> Like Windows, Samba implements Opportunistic Locking as a server-side component of the client caching mechanism. Because of the lightweight nature of the Windows feature design, effective configuration of Opportunistic Locking requires a good understanding of its limitations, and then applying that understanding when configuring data access for each particular customized network and client usage state. </p><p> Opportunistic locking essentially means that the client is allowed to download and cache a file on their hard drive while making changes; if a second client wants to access the file, the first client receives a break and must synchronise the file back to the server. This can give significant performance gains in some cases; some programs insist on synchronising the contents of the entire file back to the server for a single change. </p><p> Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. </p><p> Level2 Oplocks provides opportunistic locking for a file that will be treated as <span class="emphasis"><em>read only</em></span>. Typically this is used on files that are read-only or on files that the client has no initial intention to write to at time of opening the file. </p><p> Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with Samba's oplocked files, although this has provided better integration of MS Windows network file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are oplock aware at this time. </p><p> Unless your system supports kernel oplocks, you should disable oplocks if you are accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should always be disabled if you are sharing a database file (e.g., Microsoft Access) between multiple clients, as any break the first client receives will affect synchronisation of the entire file (not just the single record), which will result in a noticeable performance impairment and, more likely, problems accessing the database in the first place. Notably, Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt, disable oplocks and tune your system from that point. </p><p> If client-side caching is desirable and reliable on your network, you will benefit from turning on oplocks. If your network is slow and/or unreliable, or you are sharing your files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people will be accessing the same files frequently, you probably will not benefit from the overhead of your client sending oplock breaks and will instead want to disable oplocks for the share. </p><p> Another factor to consider is the perceived performance of file access. If oplocks provide no measurable speed benefit on your network, it might not be worth the hassle of dealing with them. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892041"></a>Example Configuration</h3></div></div><div></div></div><p> In the following we examine two distinct aspects of Samba locking controls. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2892054"></a>Disabling Oplocks</h4></div></div><div></div></div><p> You can disable oplocks on a per-share basis with the following: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[acctdata]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplocks = False</tt></i></td></tr><tr><td><i class="parameter"><tt>level2 oplocks = False</tt></i></td></tr></table><p> </p><p> The default oplock type is Level1. Level2 Oplocks are enabled on a per-share basis in the <tt class="filename">smb.conf</tt> file. </p><p> Alternately, you could disable oplocks on a per-file basis within the share: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/</tt></i></td></tr></table><p> </p><p> If you are experiencing problems with oplocks as apparent from Samba's log entries, you may want to play it safe and disable oplocks and level2 oplocks. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2892152"></a>Disabling Kernel OpLocks</h4></div></div><div></div></div><p> Kernel OpLocks is an <tt class="filename">smb.conf</tt> parameter that notifies Samba (if the UNIX kernel has the capability to send a Windows client an oplock break) when a UNIX process is attempting to open the file that is cached. This parameter addresses sharing files between UNIX and Windows with Oplocks enabled on the Samba server: the UNIX process can open the file that is Oplocked (cached) by the Windows client and the smbd process will not send an oplock break, which exposes the file to the risk of data corruption. If the UNIX kernel has the ability to send an oplock break, then the kernel oplocks parameter enables Samba to send the oplock break. Kernel oplocks are enabled on a per-server basis in the <tt class="filename">smb.conf</tt> file. </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>kernel oplocks = yes</tt></i></td></tr></table><p> The default is "no". </p><p> Veto OpLocks is an <tt class="filename">smb.conf</tt> parameter that identifies specific files for which Oplocks are disabled. When a Windows client opens a file that has been configured for veto oplocks, the client will not be granted the oplock, and all operations will be executed on the original file on disk instead of a client-cached file copy. By explicitly identifying files that are shared with UNIX processes, and disabling oplocks for those files, the server-wide Oplock configuration can be enabled to allow Windows clients to utilize the performance benefit of file caching without the risk of data corruption. Veto Oplocks can be enabled on a per-share basis, or globally for the entire server, in the <tt class="filename">smb.conf</tt> file: </p><p> </p><div class="example"><a name="id2892244"></a><p class="title"><b>Example�14.1.�Share with some files oplocked</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /filename.htm/*.txt/</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>veto oplock files = /*.exe/filename.ext/</tt></i></td></tr></table></div><p> </p><p> <a class="indexterm" name="id2892299"></a><i class="parameter"><tt>oplock break wait time</tt></i> is an <tt class="filename">smb.conf</tt> parameter that adjusts the time interval for Samba to reply to an oplock break request. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Wait Time can only be configured globally in the <tt class="filename">smb.conf</tt> file: </p><p> </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>oplock break wait time = 0 (default)</tt></i></td></tr></table><p> </p><p> <span class="emphasis"><em>Oplock break contention limit</em></span> is an <tt class="filename">smb.conf</tt> parameter that limits the response of the Samba server to grant an oplock if the configured number of contending clients reaches the limit specified by the parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Contention Limit can be enable on a per-share basis, or globally for the entire server, in the <tt class="filename">smb.conf</tt> file: </p><p> </p><div class="example"><a name="id2892403"></a><p class="title"><b>Example�14.2.�</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit = 2 (default)</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[share_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>oplock break contention limit = 2 (default)</tt></i></td></tr></table></div><p> </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892456"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><div></div></div><p> There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP workstation computer that can affect any application attempting to access shared database files across a network. This is a result of a default setting configured in the Windows 2000/XP operating system known as <span class="emphasis"><em>Opportunistic Locking</em></span>. When a workstation attempts to access shared data files located on another Windows 2000/XP computer, the Windows 2000/XP operating system will attempt to increase performance by locking the files and caching information locally. When this occurs, the application is unable to properly function, which results in an <span class="errorname">Access Denied</span> error message being displayed during network operations. </p><p> All Windows operating systems in the NT family that act as database servers for data files (meaning that data files are stored there and accessed by other Windows PCs) may need to have opportunistic locking disabled in order to minimize the risk of data file corruption. This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP. </p><p> If you are using a Windows NT family workstation in place of a server, you must also disable opportunistic locking (oplocks) on that workstation. For example, if you use a PC with the Windows NT Workstation operating system instead of Windows NT Server, and you have data files located on it that are accessed from other Windows PCs, you may need to disable oplocks on that system. </p><p> The major difference is the location in the Windows registry where the values for disabling oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location may be used. </p><p> You can verify (or change or add, if necessary) this Registry value using the Windows Registry Editor. When you change this registry value, you will have to reboot the PC to ensure that the new setting goes into effect. </p><p> The location of the client registry entry for opportunistic locking has changed in Windows 2000 from the earlier location in Microsoft Windows NT. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks in earlier versions of Windows. </p></div><p> You can also deny the granting of opportunistic locks by changing the following registry entries: </p><p> </p><pre class="programlisting"> HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\MRXSmb\Parameters\ OplocksDisabled REG_DWORD 0 or 1 Default: 0 (not disabled) </pre><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The OplocksDisabled registry value configures Windows clients to either request or not request opportunistic locks on a remote file. To disable oplocks, the value of OplocksDisabled must be set to 1. </p></div><p> </p><pre class="programlisting"> HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanServer\Parameters EnableOplocks REG_DWORD 0 or 1 Default: 1 (Enabled by Default) EnableOpLockForceClose REG_DWORD 0 or 1 Default: 0 (Disabled by Default) </pre><p> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The EnableOplocks value configures Windows-based servers (including Workstations sharing files) to allow or deny opportunistic locks on local files. </p></div><p> To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1. </p><p> An illustration of how level II oplocks work: </p><div class="itemizedlist"><ul type="disc"><li><p> Station 1 opens the file, requesting oplock. </p></li><li><p> Since no other station has the file open, the server grants station 1 exclusive oplock. </p></li><li><p> Station 2 opens the file, requesting oplock. </p></li><li><p> Since station 1 has not yet written to the file, the server asks station 1 to Break to Level II Oplock. </p></li><li><p> Station 1 complies by flushing locally buffered lock information to the server. </p></li><li><p> Station 1 informs the server that it has Broken to Level II Oplock (alternatively, station 1 could have closed the file). </p></li><li><p> The server responds to station 2's open request, granting it level II oplock. Other stations can likewise open the file and obtain level II oplock. </p></li><li><p> Station 2 (or any station that has the file open) sends a write request SMB. The server returns the write response. </p></li><li><p> The server asks all stations that have the file open to Break to None, meaning no station holds any oplock on the file. Because the workstations can have no cached writes or locks at this point, they need not respond to the break-to-none advisory; all they need do is invalidate locally cashed read-ahead data. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892680"></a>Workstation Service Entries</h3></div></div><div></div></div><pre class="programlisting"> \HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanWorkstation\Parameters UseOpportunisticLocking REG_DWORD 0 or 1 Default: 1 (true) </pre><p> Indicates whether the redirector should use opportunistic-locking (oplock) performance enhancement. This parameter should be disabled only to isolate problems. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892709"></a>Server Service Entries</h3></div></div><div></div></div><pre class="programlisting"> \HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services\LanmanServer\Parameters EnableOplocks REG_DWORD 0 or 1 Default: 1 (true) </pre><p> Specifies whether the server allows clients to use oplocks on files. Oplocks are a significant performance enhancement, but have the potential to cause lost cached data on some networks, particularly wide-area networks. </p><pre class="programlisting"> MinLinkThroughput REG_DWORD 0 to infinite bytes per second Default: 0 </pre><p> Specifies the minimum link throughput allowed by the server before it disables raw and opportunistic locks for this connection. </p><pre class="programlisting"> MaxLinkDelay REG_DWORD 0 to 100,000 seconds Default: 60 </pre><p> Specifies the maximum time allowed for a link delay. If delays exceed this number, the server disables raw I/O and opportunistic locking for this connection. </p><pre class="programlisting"> OplockBreakWait REG_DWORD 10 to 180 seconds Default: 35 </pre><p> Specifies the time that the server waits for a client to respond to an oplock break request. Smaller values can allow detection of crashed clients more quickly but can potentially cause loss of cached data. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892788"></a>Persistent Data Corruption</h2></div></div><div></div></div><p> If you have applied all of the settings discussed in this chapter but data corruption problems and other symptoms persist, here are some additional things to check out: </p><p> We have credible reports from developers that faulty network hardware, such as a single faulty network card, can cause symptoms similar to read caching and data corruption. If you see persistent data corruption even after repeated reindexing, you may have to rebuild the data files in question. This involves creating a new data file with the same definition as the file to be rebuilt and transferring the data from the old file to the new one. There are several known methods for doing this that can be found in our Knowledge Base. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892817"></a>Common Errors</h2></div></div><div></div></div><p> In some sites locking problems surface as soon as a server is installed, in other sites locking problems may not surface for a long time. Almost without exception, when a locking problem does surface it will cause embarrassment and potential data corruption. </p><p> Over the past few years there have been a number of complaints on the samba mailing lists that have claimed that samba caused data corruption. Three causes have been identified so far: </p><div class="itemizedlist"><ul type="disc"><li><p> Incorrect configuration of opportunistic locking (incompatible with the application being used. This is a VERY common problem even where MS Windows NT4 or MS Windows 200x based servers were in use. It is imperative that the software application vendors' instructions for configuration of file locking should be followed. If in doubt, disable oplocks on both the server and the client. Disabling of all forms of file caching on the MS Windows client may be necessary also. </p></li><li><p> Defective network cards, cables, or HUBs / Switched. This is generally a more prevalent factor with low cost networking hardware, though occasionally there have been problems with incompatibilities in more up market hardware also. </p></li><li><p> There have been some random reports of samba log files being written over data files. This has been reported by very few sites (about 5 in the past 3 years) and all attempts to reproduce the problem have failed. The Samba-Team has been unable to catch this happening and thus has NOT been able to isolate any particular cause. Considering the millions of systems that use samba, for the sites that have been affected by this as well as for the Samba-Team this is a frustrating and a vexing challenge. If you see this type of thing happening please create a bug report on https://bugzilla.samba.org without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow reproduction of the problem (an essential step in problem isolation and correction). </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892891"></a>locking.tdb error messages</h3></div></div><div></div></div><p> “<span class="quote"> We are seeing lots of errors in the samba logs like: </span>” </p><pre class="programlisting"> tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic 0x4d6f4b61 at offset=36116 </pre><p> “<span class="quote"> What do these mean? </span>” </p><p> Corrupted tdb. Stop all instances of smbd, delete locking.tdb, restart smbd. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892930"></a>Problems saving files in MS Office on Windows XP</h3></div></div><div></div></div><p>This is a bug in Windows XP. More information can be found in <a href="http://support.microsoft.com/?id=812937" target="_top">Microsoft Knowledge Base article 812937</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2892952"></a>Long delays deleting files over network with XP SP1</h3></div></div><div></div></div><p>“<span class="quote">It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied</span>”</p><p>This is a bug in Windows XP. More information can be found in <a href="http://support.microsoft.com/?id=811492" target="_top"> Microsoft Knowledge Base article 811492</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2892983"></a>Additional Reading</h2></div></div><div></div></div><p> You may want to check for an updated version of this white paper on our Web site from time to time. Many of our white papers are updated as information changes. For those papers, the Last Edited date is always at the top of the paper. </p><p> Section of the Microsoft MSDN Library on opportunistic locking: </p><p> Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development > Windows Base Services > Files and I/O > SDK Documentation > File Storage > File Systems > About File Systems > Opportunistic Locks, Microsoft Corporation. <a href="http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp" target="_top">http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp</a> </p><p> Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", Microsoft Corporation, April 1999, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992</a>. </p><p> Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264</a>. </p><p> Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", Microsoft Corporation, April 1995, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</a>. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="securing-samba"></a>Chapter�15.�Securing Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">May 26, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2893158">Introduction</a></dt><dt><a href="#id2893195">Features and Benefits</a></dt><dt><a href="#id2893269">Technical Discussion of Protective Measures and Issues</a></dt><dd><dl><dt><a href="#id2893288">Using host based protection</a></dt><dt><a href="#id2893387">User based protection</a></dt><dt><a href="#id2893447">Using interface protection</a></dt><dt><a href="#id2893515">Using a firewall</a></dt><dt><a href="#id2893572">Using a IPC$ share deny</a></dt><dt><a href="#id2893660">NTLMv2 Security</a></dt></dl></dd><dt><a href="#id2893719">Upgrading Samba</a></dt><dt><a href="#id2893743">Common Errors</a></dt><dd><dl><dt><a href="#id2893761">Smbclient works on localhost, but the network is dead</a></dt><dt><a href="#id2893786">Why can users access home directories of other users?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893158"></a>Introduction</h2></div></div><div></div></div><p> This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba installations in general. </p><p> A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning on it!" </p><p> Security concerns are just like that: You need to know a little about the subject to appreciate how obvious most of it really is. The challenge for most of us is to discover that first morsel of knowledge with which we may unlock the secrets of the masters. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893195"></a>Features and Benefits</h2></div></div><div></div></div><p> There are three level at which security principals must be observed in order to render a site at least moderately secure. These are: the perimeter firewall, the configuration of the host server that is running Samba, and Samba itself. </p><p> Samba permits a most flexible approach to network security. As far as possible Samba implements the latest protocols to permit more secure MS Windows file and print operations. </p><p> Samba may be secured from connections that originate from outside the local network. This may be done using <span class="emphasis"><em>host based protection</em></span> (using samba's implementation of a technology known as "tcpwrappers", or it may be done be using <span class="emphasis"><em>interface based exclusion</em></span> so that <span class="application">smbd</span> will bind only to specifically permitted interfaces. It is also possible to set specific share or resource based exclusions, eg: on the <i class="parameter"><tt>[IPC$]</tt></i> auto-share. The <i class="parameter"><tt>[IPC$]</tt></i> share is used for browsing purposes as well as to establish TCP/IP connections. </p><p> Another method by which Samba may be secured is by way of setting Access Control Entries in an Access Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access Control. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893269"></a>Technical Discussion of Protective Measures and Issues</h2></div></div><div></div></div><p> The key challenge of security is the fact that protective measures suffice at best only to close the door on known exploits and breach techniques. Never assume that because you have followed these few measures that the Samba server is now an impenetrable fortress! Given the history of information systems so far, it is only a matter of time before someone will find yet another vulnerability. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893288"></a>Using host based protection</h3></div></div><div></div></div><p> In many installations of Samba the greatest threat comes for outside your immediate network. By default Samba will accept connections from any host, which means that if you run an insecure version of Samba on a host that is directly connected to the Internet you can be especially vulnerable. </p><p> One of the simplest fixes in this case is to use the <a class="indexterm" name="id2893310"></a><i class="parameter"><tt>hosts allow</tt></i> and <a class="indexterm" name="id2893324"></a><i class="parameter"><tt>hosts deny</tt></i> options in the Samba <tt class="filename">smb.conf</tt> configuration file to only allow access to your server from a specific range of hosts. An example might be: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0/0</tt></i></td></tr></table><p> The above will only allow SMB connections from 'localhost' (your own computer) and from the two private networks 192.168.2 and 192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as a <span class="errorname">not listening on called name</span> error. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893387"></a>User based protection</h3></div></div><div></div></div><p> If you want to restrict access to your server to valid users only then the following method may be of use. In the <tt class="filename">smb.conf</tt> <i class="parameter"><tt>[global]</tt></i> section put: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>valid users = @smbusers, jacko</tt></i></td></tr></table><p> What this does is, it restricts all server access to either the user <span class="emphasis"><em>jacko</em></span> or to members of the system group <span class="emphasis"><em>smbusers</em></span>. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893447"></a>Using interface protection</h3></div></div><div></div></div><p> By default Samba will accept connections on any network interface that it finds on your system. That means if you have a ISDN line or a PPP connection to the Internet then Samba will accept connections on those links. This may not be what you want. </p><p> You can change this behaviour using options like the following: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>interfaces = eth* lo</tt></i></td></tr><tr><td><i class="parameter"><tt>bind interfaces only = yes</tt></i></td></tr></table><p> This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what OS you are using, in the above I used the common name for Ethernet adapters on Linux. </p><p> If you use the above and someone tries to make a SMB connection to your host over a PPP interface called 'ppp0' then they will get a TCP connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that interface to any samba process. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893515"></a>Using a firewall</h3></div></div><div></div></div><p> Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above methods so that you are protected even if your firewall is not active for some reason. </p><p> If you are setting up a firewall then you need to know what TCP and UDP ports to allow and block. Samba uses the following: </p><table class="simplelist" border="0" summary="Simple list"><tr><td>UDP/137 - used by nmbd</td></tr><tr><td>UDP/138 - used by nmbd</td></tr><tr><td>TCP/139 - used by smbd</td></tr><tr><td>TCP/445 - used by smbd</td></tr></table><p> The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893572"></a>Using a IPC$ share deny</h3></div></div><div></div></div><p> If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that is used in the recently discovered security hole. This allows you to offer access to other shares while denying access to IPC$ from potentially untrustworthy hosts. </p><p> To do that you could use: </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[ipc$]</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = 192.168.115.0/24 127.0.0.1</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = 0.0.0.0/0</tt></i></td></tr></table><p> this would tell Samba that IPC$ connections are not allowed from anywhere but the two listed places (localhost and a local subnet). Connections to other shares would still be allowed. As the IPC$ share is the only share that is always accessible anonymously this provides some level of protection against attackers that do not know a username/password for your host. </p><p> If you use this method then clients will be given a <span class="errorname">access denied</span> reply when they try to access the IPC$ share. That means that those clients will not be able to browse shares, and may also be unable to access some other resources. </p><p> This is not recommended unless you cannot use one of the other methods listed above for some reason. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893660"></a>NTLMv2 Security</h3></div></div><div></div></div><p> To configure NTLMv2 authentication the following registry keys are worth knowing about: </p><p> </p><pre class="screen"> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "lmcompatibilitylevel"=dword:00000003 </pre><p> </p><p> 0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication, use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM and NTLMv2 authentication. </p><p> </p><pre class="screen"> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] "NtlmMinClientSec"=dword:00080000 </pre><p> </p><p> 0x80000 - NTLMv2 session security. If either NtlmMinClientSec or NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2 session security is not negotiated. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893719"></a>Upgrading Samba</h2></div></div><div></div></div><p> Please check regularly on <a href="http://www.samba.org/" target="_top">http://www.samba.org/</a> for updates and important announcements. Occasionally security releases are made and it is highly recommended to upgrade Samba when a security vulnerability is discovered. Check with your OS vendor for OS specific upgrades. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2893743"></a>Common Errors</h2></div></div><div></div></div><p> If all of samba and host platform configuration were really as intuitive as one might like then this section would not be necessary. Security issues are often vexing for a support person to resolve, not because of the complexity of the problem, but for reason that most administrators who post what turns out to be a security problem request are totally convinced that the problem is with Samba. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893761"></a>Smbclient works on localhost, but the network is dead</h3></div></div><div></div></div><p> This is a very common problem. Red Hat Linux (as do others) will install a default firewall. With the default firewall in place only traffic on the loopback adapter (IP address 127.0.0.1) will be allowed through the firewall. </p><p> The solution is either to remove the firewall (stop it) or to modify the firewall script to allow SMB networking traffic through. See section above in this chapter. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2893786"></a>Why can users access home directories of other users?</h3></div></div><div></div></div><p> “<span class="quote"> We are unable to keep individual users from mapping to any other user's home directory once they have supplied a valid password! They only need to enter their own password. I have not found *any* method that I can use to configure samba to enforce that only a user may map their own home directory. </span>” </p><p>“<span class="quote"> User xyzzy can map his home directory. Once mapped user xyzzy can also map *anyone* else's home directory! </span>”</p><p> This is not a security flaw, it is by design. Samba allows users to have *exactly* the same access to the UNIX filesystem as they would if they were logged onto the UNIX box, except that it only allows such views onto the file system as are allowed by the defined shares. </p><p> This means that if your UNIX home directories are set up such that one user can happily cd into another users directory and do an ls, the UNIX security solution is to change the UNIX file permissions on the users home directories such that the cd and ls would be denied. </p><p> Samba tries very hard not to second guess the UNIX administrators security policies, and trusts the UNIX admin to set the policies and permissions he or she desires. </p><p> Samba does allow the setup you require when you have set the <a class="indexterm" name="id2893846"></a><i class="parameter"><tt>only user</tt></i> = yes option on the share, is that you have not set the valid users list for the share. </p><p> Note that only user works in conjunction with the users= list, so to get the behavior you require, add the line : </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>users = %S</tt></i></td></tr></table><p> this is equivalent to: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>valid users = %S</tt></i></td></tr></table><p> to the definition of the <i class="parameter"><tt>[homes]</tt></i> share, as recommended in the <tt class="filename">smb.conf</tt> man page. </p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter�16.�Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Rafal</span> <span class="surname">Szczesniak</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:mimir@samba.org">mimir@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawing</span><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><tt class="email"><<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2894077">Features and Benefits</a></dt><dt><a href="#id2894106">Trust Relationship Background</a></dt><dt><a href="#id2894193">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2894221">Creating an NT4 Domain Trust</a></dt><dt><a href="#id2894294">Completing an NT4 Domain Trust</a></dt><dt><a href="#id2894341">Inter-Domain Trust Facilities</a></dt></dl></dd><dt><a href="#id2894518">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#samba-trusted-domain">Samba as the Trusted Domain</a></dt><dt><a href="#id2894704">Samba as the Trusting Domain</a></dt></dl></dd><dt><a href="#id2894842">NT4-style Domain Trusts with Windows 2000</a></dt><dt><a href="#id2894948">Common Errors</a></dt></dl></div><a class="indexterm" name="id2894056"></a><p> Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba3-to-Samba3 trusts. </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894077"></a>Features and Benefits</h2></div></div><div></div></div><p> Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4 style trust relationships. This imparts to Samba similar scalability as is possible with MS Windows NT4. </p><p> Given that Samba-3 has the capability to function with a scalable backend authentication database such as LDAP, and given it's ability to run in Primary as well as Backup Domain control modes, the administrator would be well advised to consider alternatives to the use of Interdomain trusts simply because by the very nature of how this works it is fragile. That was, after all, a key reason for the development and adoption of Microsoft Active Directory. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894106"></a>Trust Relationship Background</h2></div></div><div></div></div><p> MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking in large organisations is well known. Additionally, the flat namespace that results from 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><div><h2 class="title" style="clear: both"><a name="id2894193"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><div></div></div><p> There are two steps to creating an interdomain trust relationship. To effect a two-way trust relationship it is necessary for each domain administrator to create a trust account for the other domain to use in verifying security credentials. <a class="indexterm" name="id2894210"></a> </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894221"></a>Creating an NT4 Domain Trust</h3></div></div><div></div></div><p> For MS Windows NT4, all domain trust relationships are configured using the <span class="application">Domain User Manager</span>. This is done from the Domain User Manager Policies entry on the menu bar. From the <span class="guimenu">Policy</span> menu, select <span class="guimenuitem">Trust Relationships</span>. Next to the lower box labelled <span class="guilabel">Permitted to Trust this Domain</span> are two buttons, <span class="guibutton">Add</span> and <span class="guibutton">Remove</span>. The <span class="guibutton">Add</span> button will open a panel in which to enter the name of the remote domain that will be able to assign access rights to users in your domain. You will also need to enter a password for this trust relationship, which the trusting domain will use when authenticating users from the trusted domain. The password needs to be typed twice (for standard confirmation). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894294"></a>Completing an NT4 Domain Trust</h3></div></div><div></div></div><p> <a class="indexterm" name="id2894305"></a> A trust relationship will work only when the other (trusting) domain makes the appropriate connections with the trusted domain. To consummate the trust relationship the administrator will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the <span class="guibutton">Add</span> button that is next to the box that is labelled <span class="guilabel">Trusted Domains</span>. A panel will open in which must be entered the name of the remote domain as well as the password assigned to that trust. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894341"></a>Inter-Domain Trust Facilities</h3></div></div><div></div></div><a class="indexterm" name="id2894348"></a><p> A two-way trust relationship is created when two one-way trusts are created, one in each direction. Where a one-way trust has been established between two MS Windows NT4 domains (let's call them DomA and DomB) the following facilities are created: </p><div class="figure"><a name="trusts1"></a><p class="title"><b>Figure�16.1.�Trusts overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/trusts1.png" width="270" alt="Trusts overview"></div></div><div class="itemizedlist"><ul type="disc"><li><p> DomA (completes the trust connection) Trusts DomB </p></li><li><p> DomA is the Trusting domain </p></li><li><p> DomB is the Trusted domain (originates the trust account) </p></li><li><p> Users in DomB can access resources in DomA </p></li><li><p> Users in DomA can NOT access resources in DomB </p></li><li><p> Global groups from DomB CAN be used in DomA </p></li><li><p> Global groups from DomA can NOT be used in DomB </p></li><li><p> DomB DOES appear in the logon dialog box on client workstations in DomA </p></li><li><p> DomA does NOT appear in the logon dialog box on client workstations in DomB </p></li></ul></div><div class="itemizedlist"><ul type="disc"><li><p> Users / Groups in a trusting domain can NOT be granted rights, permissions or access to a trusted domain. </p></li><li><p> The trusting domain CAN access and use accounts (Users / Global Groups) in the trusted domain. </p></li><li><p> Administrators of the trusted domain CAN be granted admininstrative rights in the trusting domain. </p></li><li><p> Users in a trusted domain CAN be given rights and privileges in the trusting domain. </p></li><li><p> Trusted domain Global Groups CAN be given rights and permissions in the trusting domain. </p></li><li><p> Global Groups from the trusted domain CAN be made members in Local Groups on MS Windows domain member machines. </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894518"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><div></div></div><p> This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba is in its early stage, so lot of things don't work yet. </p><p> Each of the procedures described below assumes the peer domain in the trust relationship is controlled by a Windows NT4 server. However, 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 a purely Samba environment. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="samba-trusted-domain"></a>Samba as the Trusted Domain</h3></div></div><div></div></div><p> In order to set the Samba PDC to be the trusted party of the relationship you first need to create a 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 similar to creating a trusted machine account. Suppose, your domain is called SAMBA, and the remote domain is called RUMBA. The first step will be to issue this command from your favourite shell: </p><p> </p><pre class="screen"> <tt class="prompt">root# </tt> <b class="userinput"><tt>smbpasswd -a -i rumba</tt></b> New SMB password: <b class="userinput"><tt>XXXXXXXX</tt></b> Retype SMB password: <b class="userinput"><tt>XXXXXXXX</tt></b> Added user rumba$ </pre><p> where <tt class="option">-a</tt> means to add a new account into the passdb database and <tt class="option">-i</tt> means: ''create this account with the InterDomain trust flag'' </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 standard way as appropriate for your configuration) and see that account's name is really RUMBA$ and it has the 'I' flag set in the flags field. Now you're ready to confirm the trust by establishing it from Windows NT Server. </p><a class="indexterm" name="id2894642"></a><p> Open <span class="application">User Manager for Domains</span> and from the <span class="guimenu">Policies</span> menu, select <span class="guimenuitem">Trust Relationships...</span>. Right beside the <span class="guilabel">Trusted domains</span> list box press the <span class="guimenu">Add...</span> button. You will be prompted for the trusted domain name and the relationship password. Type in SAMBA, as this is the name of the remote domain, and the password used at the time of account creation. Press OK and, if everything went without incident, you will see <tt class="computeroutput">Trusted domain relationship successfully established</tt> message. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2894704"></a>Samba as the Trusting Domain</h3></div></div><div></div></div><p> This time activities are somewhat reversed. Again, we'll assume that your domain controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA. </p><p> The very first step is to add an account for the SAMBA domain on RUMBA's PDC. </p><a class="indexterm" name="id2894724"></a><p> Launch the <span class="application">Domain User Manager</span>, then from the menu select <span class="guimenu">Policies</span>, <span class="guimenuitem">Trust Relationships</span>. Now, next to the <span class="guilabel">Trusted Domains</span> box press the <span class="guibutton">Add</span> button, and type in the name of the trusted domain (SAMBA) and the password to use in 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 class="prompt">root# </tt><b class="userinput"><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 return 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), but eventually you should see the <tt class="computeroutput">Success</tt> 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 class="filename">secrets.tdb</tt> file. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894842"></a>NT4-style Domain Trusts with Windows 2000</h2></div></div><div></div></div><p> Although <span class="application">Domain User Manager</span> is not present in Windows 2000, it is also possible to establish an NT4-style trust relationship with a Windows 2000 domain controller running in mixed mode as the trusting server. It should also be possible for Samba to trust a Windows 2000 server, however, more testing is still needed in this area. </p><p> After <a href="#samba-trusted-domain" title="Samba as the Trusted Domain">creating the interdomain trust account on the Samba server</a> as described above, open <span class="application">Active Directory Domains and Trusts</span> on the AD controller of the domain whose resources you wish Samba users to have access to. Remember that since NT4-style trusts are not transitive, if you want your users to have access to multiple mixed-mode domains in your AD forest, you will need to repeat this process for each of those domains. With <span class="application">Active Directory Domains and Trusts</span> open, right-click on the name of the Active Directory domain that will trust our Samba domain and choose <span class="guimenuitem">Properties</span>, then click on the <span class="guilabel">Trusts</span> tab. In the upper part of the panel, you will see a list box labelled <span class="guilabel">Domains trusted by this domain:</span>, and an <span class="guilabel">Add...</span> button next to it. Press this button, and just as with NT4, you will be prompted for the trusted domain name and the relationship password. Press OK, and after a moment, Active Directory will respond with <tt class="computeroutput">The trusted domain has been added and the trust has been verified.</tt> Your Samba users can now be granted acess to resources in the AD domain. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2894948"></a>Common Errors</h2></div></div><div></div></div><p> Interdomain trust relationships should NOT be attempted on networks that are unstable or that suffer regular outages. Network stability and integrity are key concerns with distributed trusted domains. </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="msdfs"></a>Chapter�17.�Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Shirish</span> <span class="surname">Kalele</span></h3><div class="affiliation"><span class="orgname">Samba Team & Veritas Software<br></span><div class="address"><p><br> <tt class="email"><<a href="mailto:samba@samba.org">samba@samba.org</a>></tt><br> </p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2895017">Features and Benefits</a></dt><dt><a href="#id2895292">Common Errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895017"></a>Features and Benefits</h2></div></div><div></div></div><p> The Distributed File System (or DFS) provides a means of separating the logical view of files and directories that users see from the actual physical locations of these resources on the network. It allows for higher availability, smoother storage expansion, load balancing etc. </p><p> For information about DFS, refer to the <a href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top">Microsoft documentation</a>. </p><p> This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients to browse) using Samba. </p><p> To enable SMB-based DFS for Samba, configure it with the <tt class="option">--with-msdfs</tt> option. Once built, a Samba server can be made a DFS server by setting the global boolean <a class="indexterm" name="id2895064"></a><i class="parameter"><tt>host msdfs</tt></i> parameter in the <tt class="filename">smb.conf</tt> file. You designate a share as a DFS root using the share level boolean <a class="indexterm" name="id2895086"></a><i class="parameter"><tt>msdfs root</tt></i> parameter. A DFS root directory on Samba hosts DFS links in the form of symbolic links that point to other servers. For example, a symbolic link <tt class="filename">junction->msdfs:storage1\share1</tt> in the share directory acts as the DFS junction. When DFS-aware clients attempt to access the junction link, they are redirected to the storage location (in this case, \\storage1\share1). </p><p> DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x. </p><p> Here's an example of setting up a DFS tree on a Samba server. </p><div class="example"><a name="id2895128"></a><p class="title"><b>Example�17.1.�smb.conf with DFS configured</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>netbios name = GANDALF</tt></i></td></tr><tr><td><i class="parameter"><tt>host msdfs = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[dfs]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /export/dfsroot</tt></i></td></tr><tr><td><i class="parameter"><tt>msdfs root = yes</tt></i></td></tr></table></div><p>In the /export/dfsroot directory we set up our DFS links to other servers on the network.</p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>cd /export/dfsroot</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>chown root /export/dfsroot</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>chmod 755 /export/dfsroot</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>ln -s msdfs:storageA\\shareA linka</tt></b> <tt class="prompt">root# </tt><b class="userinput"><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b> </pre><p>You should set up the permissions and ownership of the directory acting as the DFS root such that only designated users can create, delete or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link name. Finally set up the symbolic links to point to the network shares you want, and start Samba.</p><p>Users on DFS-aware clients can now browse the DFS tree on the Samba server at \\samba\dfs. Accessing links linka or linkb (which appear as directories to the client) takes users directly to the appropriate shares on the network.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895292"></a>Common Errors</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted if a previously mounted non-dfs share is made a DFS root or vice versa. A better way is to introduce a new share and make it the DFS root.</p></li><li><p>Currently there's a restriction that msdfs symlink names should all be lowercase.</p></li><li><p>For security purposes, the directory acting as the root of the DFS tree should have ownership and permissions set so that only designated users can modify the symbolic links in the directory.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="printing"></a>Chapter�18.�Classical Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname"> Danka Deutschland GmbH <br></span><div class="address"><p><tt class="email"><<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2895411">Features and Benefits</a></dt><dt><a href="#id2895517">Technical Introduction</a></dt><dd><dl><dt><a href="#id2895555">What happens if you send a Job from a Client</a></dt><dt><a href="#id2895627">Printing Related Configuration Parameters</a></dt><dt><a href="#id2895722">Parameters Recommended for Use</a></dt></dl></dd><dt><a href="#id2896188">A simple Configuration to Print</a></dt><dd><dl><dt><a href="#id2896354">Verification of "Settings in Use" with testparm</a></dt><dt><a href="#id2896481">A little Experiment to warn you</a></dt></dl></dd><dt><a href="#id2896843">Extended Sample Configuration to Print</a></dt><dt><a href="#id2897173">Detailed Explanation of the Example's Settings</a></dt><dd><dl><dt><a href="#id2897186">The [global] Section</a></dt><dt><a href="#id2897717">The [printers] Section</a></dt><dt><a href="#id2898177">Any [my_printer_name] Section</a></dt><dt><a href="#id2898498">Print Commands</a></dt><dt><a href="#id2898580">Default Print Commands for various UNIX Print Subsystems</a></dt><dt><a href="#id2899263">Setting up your own Print Commands</a></dt></dl></dd><dt><a href="#id2899603">Innovations in Samba Printing since 2.2</a></dt><dd><dl><dt><a href="#id2899763">Client Drivers on Samba Server for Point'n'Print</a></dt><dt><a href="#id2899925">The [printer$] Section is removed from Samba 3</a></dt><dt><a href="#id2900037">Creating the [print$] Share</a></dt><dt><a href="#id2900227">Parameters in the [print$] Section</a></dt><dt><a href="#id2900537">Subdirectory Structure in [print$]</a></dt></dl></dd><dt><a href="#id2900710">Installing Drivers into [print$]</a></dt><dd><dl><dt><a href="#id2900805">Setting Drivers for existing Printers with a Client GUI</a></dt><dt><a href="#id2901002">Setting Drivers for existing Printers with rpcclient</a></dt></dl></dd><dt><a href="#id2902712">Client Driver Install Procedure</a></dt><dd><dl><dt><a href="#id2902731">The first Client Driver Installation</a></dt><dt><a href="#id2902934">IMPORTANT! Setting Device Modes on new Printers</a></dt><dt><a href="#id2903234">Further Client Driver Install Procedures</a></dt><dt><a href="#id2903328">Always make first Client Connection as root or "printer admin"</a></dt></dl></dd><dt><a href="#id2903500">Other Gotchas</a></dt><dd><dl><dt><a href="#id2903534">Setting Default Print Options for the Client Drivers</a></dt><dt><a href="#id2904001">Supporting large Numbers of Printers</a></dt><dt><a href="#id2904312">Adding new Printers with the Windows NT APW</a></dt><dt><a href="#id2904606">Weird Error Message Cannot connect under a different Name</a></dt><dt><a href="#id2904706">Be careful when assembling Driver Files</a></dt><dt><a href="#id2905065">Samba and Printer Ports</a></dt><dt><a href="#id2905158">Avoiding the most common Misconfigurations of the Client Driver</a></dt></dl></dd><dt><a href="#id2905183">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2905239">What is Imprints?</a></dt><dt><a href="#id2905280">Creating Printer Driver Packages</a></dt><dt><a href="#id2905299">The Imprints Server</a></dt><dt><a href="#id2905323">The Installation Client</a></dt></dl></dd><dt><a href="#id2905478">Add Network Printers at Logon without User Interaction</a></dt><dt><a href="#id2905813">The addprinter command</a></dt><dt><a href="#id2905859">Migration of "Classical" printing to Samba</a></dt><dt><a href="#id2906032">Publishing Printer Information in Active Directory or LDAP</a></dt><dt><a href="#id2906044">Common Errors</a></dt><dd><dl><dt><a href="#id2906050">I give my root password but I don't get access</a></dt><dt><a href="#id2906085">My printjobs get spooled into the spooling directory, but then get lost</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895411"></a>Features and Benefits</h2></div></div><div></div></div><p> Printing is often a mission-critical service for the users. Samba can provide this service reliably and seamlessly for a client network consisting of Windows workstations. </p><p> A Samba print service may be run on a Standalone or a Domain member server, side by side with file serving functions, or on a dedicated print server. It can be made as tight or as loosely secured as needs dictate. Configurations may be simple or complex. Available authentication schemes are essentially the same as described for file services in previous chapters. Overall, Samba's printing support is now able to replace an NT or Windows 2000 print server full-square, with additional benefits in many cases. Clients may download and install drivers and printers through their familiar "Point'n'Print" mechanism. Printer installations executed by "Logon Scripts" are no problem. Administrators can upload and manage drivers to be used by clients through the familiar "Add Printer Wizard". As an additional benefit, driver and printer management may be run from the command line or through scripts, making it more efficient in case of large numbers of printers. If a central accounting of print jobs (tracking every single page and supplying the raw data for all sorts of statistical reports) is required, this is best supported by CUPS as the print subsystem underneath the Samba hood. </p><p> This chapter deals with the foundations of Samba printing, as they implemented by the more traditional UNIX (BSD- and System V-style) printing systems. Many things apply to CUPS, the newer Common UNIX Printing System, too; so if you use CUPS, you might be tempted to jump to the next chapter -- but you will certainly miss a few things if you do so. Better to read this chapter too. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Most of the given examples have been verified on Windows XP Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 2000 clients are very similar, but may differ in details. Windows NT is somewhat different again. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2895517"></a>Technical Introduction</h2></div></div><div></div></div><p> Samba's printing support always relies on the installed print subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes printfiles from Windows (or other SMB) clients and passes them to the real printing system for further processing. Therefore it needs to "talk" to two sides: to the Windows print clients and to the UNIX printing system. Hence we must differentiate between the various client OS types each of which behave differently, as well as the various UNIX print subsystems, which themselves have different features and are accessed differently. This part of the Samba HOWTO Collection deals with the "traditional" way of UNIX printing first; the next chapter covers in great detail the more modern <span class="emphasis"><em>Common UNIX Printing System</em></span> (CUPS). </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>CUPS users, be warned: don't just jump on to the next chapter. You might miss important information contained only here!</p></div><p> </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895555"></a>What happens if you send a Job from a Client</h3></div></div><div></div></div><p> To successfully print a job from a Windows client via a Samba print server to a UNIX printer, there are 6 (potentially 7) stages: </p><div class="orderedlist"><ol type="1"><li><p>Windows opens a connection to the printer share</p></li><li><p>Samba must authenticate the user</p></li><li><p>Windows sends a copy of the printfile over the network into Samba's spooling area</p></li><li><p>Windows closes the connection again</p></li><li><p>Samba invokes the print command to hand the file over to the UNIX print subsystem's spooling area</p></li><li><p>The UNIX print subsystem processes the print job</p></li><li><p>The printfile may need to be explicitly deleted from the Samba spooling area.</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895627"></a>Printing Related Configuration Parameters</h3></div></div><div></div></div><p> There are a number of configuration parameters in controlling Samba's printing behaviour. Please also refer to the man page for smb.conf to acquire an overview about these. As with other parameters, there are Global Level (tagged with a "<span class="emphasis"><em>G</em></span>" in the listings) and Service Level ("<span class="emphasis"><em>S</em></span>") parameters. </p><div class="variablelist"><dl><dt><span class="term">Service Level Parameters</span></dt><dd><p>These <span class="emphasis"><em>may</em></span> go into the <i class="parameter"><tt>[global]</tt></i> section of <tt class="filename">smb.conf</tt>. In this case they define the default behaviour of all individual or service level shares (provided those don't have a different setting defined for the same parameter, thus overriding the global default).</p></dd><dt><span class="term">Global Parameters</span></dt><dd><p>These <span class="emphasis"><em>may not</em></span> go into individual shares. If they go in by error, the "testparm" utility can discover this (if you run it) and tell you so.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2895722"></a>Parameters Recommended for Use</h3></div></div><div></div></div><p>The following <tt class="filename">smb.conf</tt> parameters directly related to printing are used in Samba. See also the <tt class="filename">smb.conf</tt> man page for detailed explanations: </p><p>Global level parameters: <a class="indexterm" name="id2895752"></a><i class="parameter"><tt>addprinter command</tt></i>, <a class="indexterm" name="id2895767"></a><i class="parameter"><tt>deleteprinter command</tt></i>, <a class="indexterm" name="id2895781"></a><i class="parameter"><tt>disable spoolss</tt></i>, <a class="indexterm" name="id2895794"></a><i class="parameter"><tt>enumports command</tt></i>, <a class="indexterm" name="id2895809"></a><i class="parameter"><tt>load printers</tt></i>, <a class="indexterm" name="id2895823"></a><i class="parameter"><tt>lpq cache time</tt></i>, <a class="indexterm" name="id2895837"></a><i class="parameter"><tt>os2 driver map</tt></i>, <a class="indexterm" name="id2895851"></a><i class="parameter"><tt>printcap name</tt></i>, <a class="indexterm" name="id2895865"></a><i class="parameter"><tt>printcap</tt></i>, <a class="indexterm" name="id2895878"></a><i class="parameter"><tt>show add printer wizard</tt></i>, <a class="indexterm" name="id2895893"></a><i class="parameter"><tt>total print jobs</tt></i>, <a class="indexterm" name="id2895907"></a><i class="parameter"><tt>use client driver</tt></i>. </p><p>Service level parameters: <a class="indexterm" name="id2895925"></a><i class="parameter"><tt>hosts allow</tt></i>, <a class="indexterm" name="id2895939"></a><i class="parameter"><tt>hosts deny</tt></i>, <a class="indexterm" name="id2895953"></a><i class="parameter"><tt>lppause command</tt></i>, <a class="indexterm" name="id2895967"></a><i class="parameter"><tt>lpq command</tt></i>, <a class="indexterm" name="id2895980"></a><i class="parameter"><tt>lpresume command</tt></i>, <a class="indexterm" name="id2895995"></a><i class="parameter"><tt>lprm command</tt></i>, <a class="indexterm" name="id2896009"></a><i class="parameter"><tt>max print jobs</tt></i>, <a class="indexterm" name="id2896023"></a><i class="parameter"><tt>min print space</tt></i>, <a class="indexterm" name="id2896037"></a><i class="parameter"><tt>print command</tt></i>, <a class="indexterm" name="id2896051"></a><i class="parameter"><tt>printable</tt></i>, <a class="indexterm" name="id2896064"></a><i class="parameter"><tt>print ok </tt></i>, <a class="indexterm" name="id2896078"></a><i class="parameter"><tt>printer name</tt></i>, <a class="indexterm" name="id2896092"></a><i class="parameter"><tt>printer</tt></i>, <a class="indexterm" name="id2896105"></a><i class="parameter"><tt>printer admin</tt></i>, <a class="indexterm" name="id2896120"></a><i class="parameter"><tt>printing</tt></i> = [cups|bsd|lprng...], <a class="indexterm" name="id2896134"></a><i class="parameter"><tt>queuepause command</tt></i>, <a class="indexterm" name="id2896148"></a><i class="parameter"><tt>queueresume command</tt></i>, <a class="indexterm" name="id2896162"></a><i class="parameter"><tt>total print jobs</tt></i>. </p><p> Samba's printing support implements the Microsoft Remote Procedure Calls (MS-RPC) methods for printing. These are used by Windows NT (and later) print servers. The old "LanMan" protocol is still supported as a fallback resort, and for older clients to use. More details will follow further beneath. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896188"></a>A simple Configuration to Print</h2></div></div><div></div></div><p> Here is a very simple example configuration for print related settings in the file. If you compare it with your own system's , you probably find some additional parameters included there (as pre-configured by your OS vendor). Further below is a discussion and explanation of the parameters. Note, that this example doesn't use many parameters. However, in many environments these are enough to provide a valid <tt class="filename">smb.conf</tt> file which enables all clients to print. </p><div class="example"><a name="id2896217"></a><p class="title"><b>Example�18.1.�Simple configuration with BSD printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = bsd</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no</tt></i></td></tr></table></div><p> This is only an example configuration. Samba assigns default values to all configuration parameters. On the whole the defaults are conservative and sensible. When a parameter is specified in the <tt class="filename">smb.conf</tt> file this overwrites the default value. The <b class="command">testparm</b> utility when run as root is capable of reporting all setting, both default as well as <tt class="filename">smb.conf</tt> file settings. <b class="command">Testparm</b> gives warnings for all mis-configured settings. The complete output is easily 340 lines and more, so you may want to pipe it through a pager program. </p><p> The syntax for the configuration file is easy to grasp. You should know that is not very picky about its syntax. It has been explained elsewhere in this document. A short reminder: It even tolerates some spelling errors (like "browsable" instead of "browseable"). Most spelling is case-insensitive. Also, you can use "Yes|No" or "True|False" for boolean settings. Lists of names may be separated by commas, spaces or tabs. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896354"></a>Verification of "Settings in Use" with <b class="command">testparm</b></h3></div></div><div></div></div><p> To see all (or at least most) printing related settings in Samba, including the implicitly used ones, try the command outlined below (hit "ENTER" twice!). It greps for all occurrences of "lp", "print", "spool", "driver", "ports" and "[" in testparm's output and gives you a nice overview about the running smbd's print configuration. (Note that this command does not show individually created printer shares, or the spooling paths in each case). Here is the output of my Samba setup, with exactly the same settings in as shown above: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v | egrep "(lp|print|spool|driver|ports|\[)"</tt></b> Load smb config files from /etc/samba/smb.conf.simpleprinting Processing section "[homes]" Processing section "[printers]" [global] smb ports = 445 139 lpq cache time = 10 total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = printer admin = min print space = 0 max print jobs = 1000 printable = No printing = bsd print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j lppause command = lpresume command = printer name = use client driver = No [homes] [printers] path = /var/spool/samba printable = Yes </pre><p> You can easily verify which settings were implicitly added by Samba's default behaviour. <span class="emphasis"><em>Don't forget about this point: it may be important in your future dealings with Samba.</em></span> </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> testparm in samba 3 behaves differently from 2.2.x: used without the "-v" switch it only shows you the settings actually written into ! To see the complete configuration used, add the "-v" parameter to testparm.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2896481"></a>A little Experiment to warn you</h3></div></div><div></div></div><p> Should you need to troubleshoot at any stage, please always come back to this point first and verify if "testparm" shows the parameters you expect! To give you an example from personal experience as a warning, try to just "comment out" the <a class="indexterm" name="id2896492"></a><i class="parameter"><tt>load printers</tt></i>" parameter. If your 2.2.x system behaves like mine, you'll see this: </p><pre class="screen"> <tt class="prompt">root# </tt>grep "load printers" /etc/samba/smb.conf # load printers = Yes # This setting is commented ooouuuuut!! <tt class="prompt">root# </tt>testparm -v /etc/samba/smb.conf | egrep "(load printers)" load printers = Yes </pre><p> Despite my imagination that the commenting out of this setting should prevent Samba from publishing my printers, it still did! Oh Boy -- it cost me quite some time to find out the reason. But I am not fooled any more... at least not by this ;-) </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>grep -A1 "load printers" /etc/samba/smb.conf</tt></b> load printers = No # This setting is what I mean!! # load printers = Yes # This setting is commented ooouuuuut!! <tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v smb.conf.simpleprinting | egrep "(load printers)"</tt></b> load printers = No </pre><p> Only when setting the parameter explicitly to "<a class="indexterm" name="id2896606"></a><i class="parameter"><tt>load printers</tt></i> = No" would Samba recognize my intentions. So my strong advice is: </p><div class="itemizedlist"><ul type="disc"><li><p>Never rely on "commented out" parameters!</p></li><li><p>Always set it up explicitly as you intend it to behave.</p></li><li><p>Use <b class="command">testparm</b> to uncover hidden settings which might not reflect your intentions.</p></li></ul></div><p> You can have a working Samba print configuration with this minimal : </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>cat /etc/samba/smb.conf-minimal</tt></b> [printers] </pre><p> This example should show you that you can use testparm to test any filename for fitness as a Samba configuration. Actually, we want to encourage you <span class="emphasis"><em>not</em></span> to change your on a working system (unless you know exactly what you are doing)! Don't rely on an assumption that changes will only take effect after you re-start smbd! This is not the case. Samba re-reads its every 60 seconds and on each new client connection. You might have to face changes for your production clients that you didn't intend to apply at this time! You will now note a few more interesting things. Let's now ask <b class="command">testparm</b> what the Samba print configuration would be, if you used this minimalistic file as your real : </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"</tt></b> Processing section "[printers]" WARNING: [printers] service MUST be printable! No path in service printers - using /tmp lpq cache time = 10 total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = printer admin = min print space = 0 max print jobs = 1000 printable = No printing = bsd print command = lpr -r -P%p %s lpq command = lpq -P%p printer name = use client driver = No [printers] printable = Yes </pre><p> testparm issued 2 warnings: </p><div class="itemizedlist"><ul type="disc"><li><p>because we didn't specify the <i class="parameter"><tt>[printers]</tt></i> section as printable, and</p></li><li><p>because we didn't tell it which spool directory to use.</p></li></ul></div><p> However, this was not fatal, and samba will default to values that will work here. Please, don't rely on this and don't use this example! This was only meant to make you careful to design and specify your setup to be what you really want it to be. The outcome on your system may vary for some parameters, since you may have a Samba built with a different compile-time configuration. <span class="emphasis"><em>Warning:</em></span> don't put a comment sign <span class="emphasis"><em>at the end</em></span> of a valid line. It will cause the parameter to be ignored (just as if you had put the comment sign at the front). At first I regarded this as a bug in my Samba version(s). But the man page states: “<span class="quote">Internal whitespace in a parameter value is retained verbatim.</span>” This means that a line consisting of, for example, </p><table class="simplelist" border="0" summary="Simple list"><tr><td># This defines LPRng as the printing system"</td></tr><tr><td><i class="parameter"><tt>printing = lprng</tt></i></td></tr></table><p> will regard the whole of the string after the "=" sign as the value you want to define. And this is an invalid value that will be ignored, and a default value used instead.] </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2896843"></a>Extended Sample Configuration to Print</h2></div></div><div></div></div><p> In <a href="#extbsdpr" title="Example�18.2.�Extended configuration with BSD printing">the extended BSD configuration example</a> we show a more verbose example configuration for print related settings in BSD-printing style environment . Below is a discussion and explanation of the various parameters. We chose to use BSD-style printing here, because we guess it is still the most commonly used system on legacy Linux installations (new installs now predominantly have CUPS, which is discussed entirely in the next chapter of this document). Note, that this example explicitly names many parameters which don't need to be specified because they are set by default. You might be able to do with a leaner <tt class="filename">smb.conf</tt> file.</p><div class="example"><a name="extbsdpr"></a><p class="title"><b>Example�18.2.�Extended configuration with BSD printing</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td><i class="parameter"><tt>printing = bsd</tt></i></td></tr><tr><td><i class="parameter"><tt>load printers = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>show add printer wizard = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printcap name = /etc/printcap</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = @ntadmin, root</tt></i></td></tr><tr><td><i class="parameter"><tt>total print jobs = 100</tt></i></td></tr><tr><td><i class="parameter"><tt>lpq cache time = 20</tt></i></td></tr><tr><td><i class="parameter"><tt>use client driver = no</tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = All Printers</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>public = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writable = no </tt></i></td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[my_printer_name]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer with Restricted Access</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /var/spool/samba_my_printer</tt></i></td></tr><tr><td><i class="parameter"><tt>printer admin = kurt</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>printable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>writeable = no</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts allow = 0.0.0.0</tt></i></td></tr><tr><td><i class="parameter"><tt>hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = no</tt></i></td></tr></table></div><p> This <span class="emphasis"><em>also</em></span> is only an example configuration. You may not find all the settings in your own (as pre-configured by your OS vendor). Many configuration parameters, if not explicitly set to a specific value, are used and set by Samba implicitly to its own default, because these have been compiled in. To see all settings, let root use the <b class="command">testparm</b> utility. <b class="command">testparm</b> also gives warnings if you have mis-configured certain things.. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2897173"></a>Detailed Explanation of the Example's Settings</h2></div></div><div></div></div><p> Following is a discussion of the settings from above shown example. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897186"></a>The [global] Section</h3></div></div><div></div></div><p> The <i class="parameter"><tt>[global]</tt></i> section is one of 4 special sections (along with [<i class="parameter"><tt>[homes]</tt></i>, <i class="parameter"><tt>[printers]</tt></i> and <i class="parameter"><tt>[print$]</tt></i>...) It contains all parameters which apply to the server as a whole. It is the place for parameters which have only a "global" meaning. It may also contain service level parameters which then define default settings for all other sections and shares. This way you can simplify the configuration and avoid setting the same value repeatedly. (Within each individual section or share you may however override these globally set "share level" settings and specify other values). </p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2897253"></a><i class="parameter"><tt>printing</tt></i> = bsd</span></dt><dd><p> this causes Samba to use default print commands applicable for the BSD (a.k.a. RFC 1179 style or LPR/LPD) printing system. In general, the "printing" parameter informs Samba about the print subsystem it should expect. Samba supports CUPS, LPD, LPRNG, SYSV, HPUX, AIX, QNX and PLP. Each of these systems defaults to a different <a class="indexterm" name="id2897272"></a><i class="parameter"><tt>print command</tt></i> (and other queue control commands).</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>The <a class="indexterm" name="id2897310"></a><i class="parameter"><tt>printing</tt></i> parameter is normally a service level parameter. Since it is included here in the <i class="parameter"><tt>[global]</tt></i> section, it will take effect for all printer shares that are not defined differently. Samba 3 no longer supports the SOFTQ printing system.</p></div></dd><dt><span class="term"><a class="indexterm" name="id2897340"></a><i class="parameter"><tt>load printers</tt></i> = yes</span></dt><dd><p> this tells Samba to create automatically all available printer shares. "Available" printer shares are discovered by scanning the printcap file. All created printer shares are also loaded for browsing. If you use this parameter, you do not need to specify separate shares for each printer. Each automatically created printer share will clone the configuration options found in the <i class="parameter"><tt>[printers]</tt></i> section. (A <i class="parameter"><tt>load printers = no</tt></i> setting will allow you to specify each UNIX printer you want to share separately, leaving out some you don't want to be publicly visible and available). </p></dd><dt><span class="term"><a class="indexterm" name="id2897399"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes </span></dt><dd><p> this setting is normally enabled by default (even if the parameter is not written into the ). It makes the <span class="guiicon">Add Printer Wizard</span> icon show up in the <span class="guiicon">Printers</span> folder of the Samba host's share listing (as shown in <span class="guiicon">Network Neighbourhood</span> or by the <b class="command">net view</b> command). To disable it, you need to explicitly set it to <tt class="constant">no</tt> (commenting it out will not suffice!). The Add Printer Wizard lets you upload printer drivers to the <i class="parameter"><tt>[print$]</tt></i> share and associate it with a printer (if the respective queue exists there before the action), or exchange a printer's driver against any other previously uploaded driver. </p></dd><dt><span class="term"><a class="indexterm" name="id2897468"></a><i class="parameter"><tt>total print jobs</tt></i> = 100</span></dt><dd><p> this setting sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client submit a job which exceeds this number, a “<span class="quote">no more space available on server</span>” type of error message will be returned by Samba to the client. A setting of "0" (the default) means there is <span class="emphasis"><em>no</em></span> limit at all! </p></dd><dt><span class="term"><a class="indexterm" name="id2897507"></a><i class="parameter"><tt>printcap name</tt></i> = /etc/printcap</span></dt><dd><p> this tells Samba where to look for a list of available printer names. (If you use CUPS, make sure that a printcap file is written: this is controlled by the "Printcap" directive of <tt class="filename">cupsd.conf</tt>). </p></dd><dt><span class="term"><a class="indexterm" name="id2897544"></a><i class="parameter"><tt>printer admin</tt></i> = @ntadmin</span></dt><dd><p> members of the ntadmin group should be able to add drivers and set printer properties ("ntadmin" is only an example name, it needs to be a valid UNIX group name); root is implicitly always a <a class="indexterm" name="id2897563"></a><i class="parameter"><tt>printer admin</tt></i>. The "@" sign precedes group names in . A printer admin can do anything to printers via the remote administration interfaces offered by MS-RPC (see below). Note that the <a class="indexterm" name="id2897596"></a><i class="parameter"><tt>printer admin</tt></i> parameter is normally a share level parameter, so you may associate different groups to different printer shares in larger installations, if you use the <a class="indexterm" name="id2897613"></a><i class="parameter"><tt>printer admin</tt></i> parameter on the share levels). </p></dd><dt><span class="term"><a class="indexterm" name="id2897631"></a><i class="parameter"><tt>lpq cache time</tt></i> = 20</span></dt><dd><p> this controls the cache time for the results of the lpq command. It prevents the lpq command being called too often and reduces load on a heavily used print server. </p></dd><dt><span class="term"><a class="indexterm" name="id2897657"></a><i class="parameter"><tt>use client driver</tt></i> = no</span></dt><dd><p> if set to <tt class="constant">yes</tt>, this setting only takes effect for Win NT/2k/XP clients (and not for Win 95/98/ME). Its default value is <tt class="constant">No</tt> (or <tt class="constant">False</tt>). It must <span class="emphasis"><em>not</em></span> be enabled on print shares (with a <tt class="constant">yes</tt> or <tt class="constant">true</tt> setting) which have valid drivers installed on the Samba server! For more detailed explanations see the man page of <tt class="filename">smb.conf</tt>. </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2897717"></a>The [printers] Section</h3></div></div><div></div></div><p> This is the second special section. If a section with this name appears in the <tt class="filename">smb.conf</tt>, users are able to connect to any printer specified in the Samba host's printcap file, because Samba on startup then creates a printer share for every printername it finds in the printcap file. You could regard this section as a general convenience shortcut to share all printers with minimal configuration. It is also a container for settings which should apply as default to all printers. (For more details see the <tt class="filename">smb.conf</tt> man page.) Settings inside this container must be share level parameters. </p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2897759"></a><i class="parameter"><tt>comment</tt></i> = All printers</span></dt><dd><p> the <a class="indexterm" name="id2897778"></a><i class="parameter"><tt>comment</tt></i> is shown next to the share if a client queries the server, either via <span class="guiicon">Network Neighbourhood</span> or with the <b class="command">net view</b> command to list available shares. </p></dd><dt><span class="term"><a class="indexterm" name="id2897812"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p> please note well, that the <i class="parameter"><tt>[printers]</tt></i> service <span class="emphasis"><em>must</em></span> be declared as printable. If you specify otherwise, smbd will refuse to load at startup. This parameter allows connected clients to open, write to and submit spool files into the directory specified with the <a class="indexterm" name="id2897846"></a><i class="parameter"><tt>path</tt></i> parameter for this service. It is used by Samba to differentiate printer shares from file shares. </p></dd><dt><span class="term"><a class="indexterm" name="id2897866"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba</span></dt><dd><p>this must point to a directory used by Samba to spool incoming print files. <span class="emphasis"><em>It must not be the same as the spool directory specified in the configuration of your UNIX print subsystem!</em></span> The path would typically point to a directory which is world writeable, with the "sticky" bit set to it. </p></dd><dt><span class="term"><a class="indexterm" name="id2897900"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this is always set to <tt class="constant">no</tt> if <a class="indexterm" name="id2897923"></a><i class="parameter"><tt>printable</tt></i> = yes. It makes the <i class="parameter"><tt>[printer]</tt></i> share itself invisible in the list of available shares in a <b class="command">net view</b> command or in the Explorer browse list. (Note that you will of course see the individual printers). </p></dd><dt><span class="term"><a class="indexterm" name="id2897959"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p> if set to <tt class="constant">yes</tt>, then no password is required to connect to the printers service. Access will be granted with the privileges of the <a class="indexterm" name="id2897985"></a><i class="parameter"><tt>guest account</tt></i>. On many systems the guest account will map to a user named "nobody". This user is in the UNIX passwd file with an empty password, but with no valid UNIX login. (Note: on some systems the guest account might not have the privilege to be able to print. Test this by logging in as your guest user using <b class="command">su - guest</b> and run a system print command like </p><p><b class="userinput"><tt>lpr -P printername /etc/motd</tt></b></p></dd><dt><span class="term"><a class="indexterm" name="id2898034"></a><i class="parameter"><tt>public</tt></i> = yes</span></dt><dd><p> this is a synonym for <a class="indexterm" name="id2898054"></a><i class="parameter"><tt>guest ok</tt></i> = yes. Since we have <a class="indexterm" name="id2898068"></a><i class="parameter"><tt>guest ok</tt></i> = yes, it really doesn't need to be here! (This leads to the interesting question: “<span class="quote">What, if I by accident have to contradictory settings for the same share?</span>” The answer is: the last one encountered by Samba wins. The "winner" is shown by testparm. Testparm doesn't complain about different settings of the same parameter for the same share! You can test this by setting up multiple lines for the "guest account" parameter with different usernames, and then run testparm to see which one is actually used by Samba.) </p></dd><dt><span class="term"><a class="indexterm" name="id2898104"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>this normally (for other types of shares) prevents users creating or modifying files in the service's directory. However, in a "printable" service, it is <span class="emphasis"><em>always</em></span> allowed to write to the directory (if user privileges allow the connection), but only via print spooling operations. "Normal" write operations are not allowed. </p></dd><dt><span class="term"><a class="indexterm" name="id2898141"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p> synonym for <a class="indexterm" name="id2898159"></a><i class="parameter"><tt>read only</tt></i> = yes </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898177"></a>Any [my_printer_name] Section</h3></div></div><div></div></div><p> If a section appears in the , which is tagged as <a class="indexterm" name="id2898189"></a><i class="parameter"><tt>printable</tt></i> = yes, Samba presents it as a printer share to its clients. Note, that Win95/98/ME clients may have problems with connecting or loading printer drivers if the share name has more than 8 characters! Also be very careful if you give a printer the same name as an existing user or file share name: upon a client's connection request to a certain sharename, Samba always tries to find file shares with that name first; if it finds one, it will connect to this and will never ultimately connect to a printer with the same name! </p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2898219"></a><i class="parameter"><tt>comment</tt></i> = Printer with Restricted Access</span></dt><dd><p> the comment says it all. </p></dd><dt><span class="term"><a class="indexterm" name="id2898243"></a><i class="parameter"><tt>path</tt></i> = /var/spool/samba_my_printer</span></dt><dd><p> here we set the spooling area for this printer to another directory than the default. It is not a requirement to set it differently, but the option is available. </p></dd><dt><span class="term"><a class="indexterm" name="id2898271"></a><i class="parameter"><tt>printer admin</tt></i> = kurt</span></dt><dd><p> the printer admin definition is different for this explicitly defined printer share from the general <i class="parameter"><tt>[printers]</tt></i> share. It is not a requirement; we did it to show that it is possible if you want it. </p></dd><dt><span class="term"><a class="indexterm" name="id2898304"></a><i class="parameter"><tt>browseable</tt></i> = yes</span></dt><dd><p> we also made this printer browseable (so that the clients may conveniently find it when browsing the <span class="guiicon">Network Neighbourhood</span>). </p></dd><dt><span class="term"><a class="indexterm" name="id2898337"></a><i class="parameter"><tt>printable</tt></i> = yes</span></dt><dd><p>see explanation in last subsection. </p></dd><dt><span class="term"><a class="indexterm" name="id2898361"></a><i class="parameter"><tt>writeable</tt></i> = no</span></dt><dd><p>see explanation in last subsection. </p></dd><dt><span class="term"><a class="indexterm" name="id2898385"></a><i class="parameter"><tt>hosts allow</tt></i> = 10.160.50.,10.160.51.</span></dt><dd><p>here we exercise a certain degree of access control by using the <a class="indexterm" name="id2898407"></a><i class="parameter"><tt>hosts allow</tt></i> and <a class="indexterm" name="id2898420"></a><i class="parameter"><tt>hosts deny</tt></i> parameters. Note, that this is not by any means a safe bet. It is not a way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of access control </p></dd><dt><span class="term"><a class="indexterm" name="id2898442"></a><i class="parameter"><tt>hosts deny</tt></i> = turbo_xp,10.160.50.23,10.160.51.60</span></dt><dd><p>all listed hosts are not allowed here (even if they belong to the "allowed subnets"). As you can see, you could name IP addresses as well as NetBIOS hostnames here. </p></dd><dt><span class="term"><a class="indexterm" name="id2898473"></a><i class="parameter"><tt>guest ok</tt></i> = no</span></dt><dd><p>this printer is not open for the guest account! </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898498"></a>Print Commands</h3></div></div><div></div></div><p> In each section defining a printer (or in the <i class="parameter"><tt>[printers]</tt></i> section), a <i class="parameter"><tt>print command</tt></i> parameter may be defined. It sets a command to process the files which have been placed into the Samba print spool directory for that printer. (That spool directory was, if you remember, set up with the <a class="indexterm" name="id2898526"></a><i class="parameter"><tt>path</tt></i> parameter). Typically, this command will submit the spool file to the Samba host's print subsystem, using the suitable system print command. But there is no requirement that this needs to be the case. For debugging purposes or some other reason you may want to do something completely different than "print" the file. An example is a command that just copies the print file to a temporary location for further investigation when you need to debug printing. If you craft your own print commands (or even develop print command shell scripts), make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise your hard disk may soon suffer from shortage of free space. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2898580"></a>Default Print Commands for various UNIX Print Subsystems</h3></div></div><div></div></div><p> You learned earlier on, that Samba in most cases uses its built-in settings for many parameters if it can not find an explicitly stated one in its configuration file. The same is true for the <a class="indexterm" name="id2898594"></a><i class="parameter"><tt>print command</tt></i>. The default print command varies depending on the <a class="indexterm" name="id2898610"></a><i class="parameter"><tt>printing</tt></i> parameter setting. In the commands listed below, you will notice some parameters of the form <span class="emphasis"><em>%X</em></span> where <span class="emphasis"><em>X</em></span> is <span class="emphasis"><em>p, s, J</em></span> etc. These letters stand for "printername", "spoolfile" and "job ID" respectively. They are explained in more detail further below. Here is an overview (excluding the special case of CUPS, which is discussed in the next chapter): </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th align="left">If this setting is active...</th><th align="left">...this is used in lieu of an explicit command:</th></tr></thead><tbody><tr><td align="left"><a class="indexterm" name="id2898695"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">print command is <b class="command">lpr -r -P%p %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898726"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">print command is <b class="command">lp -c -P%p %s; rm %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898758"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">print command is <b class="command">lp -r -P%p -s %s</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898788"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898819"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpq command is <b class="command">lpstat -o%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898850"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpq command is <b class="command">lpq -P%p</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898880"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lprm command is <b class="command">lprm -P%p %j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898911"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898941"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lprm command is <b class="command">cancel %p-%j</b></td></tr><tr><td align="left"><a class="indexterm" name="id2898972"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lppause command is <b class="command">lp -i %p-%j -H hold</b></td></tr><tr><td align="left"><a class="indexterm" name="id2899003"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lppause command (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2899027"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lppause command (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2899053"></a><i class="parameter"><tt>printing</tt></i> = bsd|aix|lprng|plp</td><td align="left">lpresume command is <b class="command">lp -i %p-%j -H resume</b></td></tr><tr><td align="left"><a class="indexterm" name="id2899084"></a><i class="parameter"><tt>printing</tt></i> = sysv|hpux</td><td align="left">lpresume command (...is empty)</td></tr><tr><td align="left"><a class="indexterm" name="id2899109"></a><i class="parameter"><tt>printing</tt></i> = qnx</td><td align="left">lpresume command (...is empty)</td></tr></tbody></table></div><p> We excluded the special CUPS case here, because it is discussed in the next chapter. Just a short summary. For <i class="parameter"><tt>printing = CUPS</tt></i>: If SAMBA is compiled against libcups, it uses the CUPS API to submit jobs, etc. (It is a good idea also to set <a class="indexterm" name="id2899148"></a><i class="parameter"><tt>printcap</tt></i> = cups in case your <tt class="filename">cupsd.conf</tt> is set to write its autogenerated printcap file to an unusual place). Otherwise Samba maps to the System V printing commands with the -oraw option for printing, i.e. it uses <b class="command">lp -c -d%p -oraw; rm %s</b> With <i class="parameter"><tt>printing = cups</tt></i> , and if SAMBA is compiled against libcups, any manually set print command will be ignored! </p><p> Having listed the above mappings here, you should note that there used to be a <span class="emphasis"><em>bug</em></span> in recent 2.2.x versions which prevented the mapping from taking effect. It lead to the "bsd|aix|lprng|plp" settings taking effect for all other systems, for the most important commands (the <b class="command">print</b> command, the <b class="command">lpq</b> command and the <b class="command">lprm</b> command). The <b class="command">lppause</b> command and the <b class="command">lpresume</b> command remained empty. Of course, these commands worked on bsd|aix|lprng|plp but they didn't work on sysv|hpux|qnx systems. To work around this bug, you need to explicitly set the commands. Use <b class="command">testparm -v</b> to check which command takes effect. Then check that this command is adequate and actually works for your installed print subsystem. It is always a good idea to explicitly set up your configuration files the way you want them to work and not rely on any built-in defaults. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899263"></a>Setting up your own Print Commands</h3></div></div><div></div></div><p> After a print job has finished spooling to a service, the <a class="indexterm" name="id2899273"></a><i class="parameter"><tt>print command</tt></i> will be used by Samba via a <span class="emphasis"><em>system()</em></span> call to process the spool file. Usually the command specified will submit the spool file to the host's printing subsystem. But there is no requirement at all that this must be the case. The print subsystem will probably not remove the spool file on its own. So whatever command you specify on your own you should ensure that the spool file is deleted after it has been processed. </p><p> There is no difficulty with using your own customized print commands with the traditional printing systems. However, if you don't wish to "roll your own", you should be well informed about the default built-in commands that Samba uses for each printing subsystem (see the table above). In all the commands listed in the last paragraphs you see parameters of the form <span class="emphasis"><em>%X</em></span> These are <span class="emphasis"><em>macros</em></span>, or shortcuts, used as place holders for the names of real objects. At the time of running a command with such a placeholder, Samba will insert the appropriate value automatically. Print commands can handle all Samba macro substitutions. In regard to printing, the following ones do have special relevance: </p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>%s, %f</tt></i> - the path to the spool file name</p></li><li><p><i class="parameter"><tt>%p</tt></i> - the appropriate printer name</p></li><li><p><i class="parameter"><tt>%J</tt></i> - the job name as transmitted by the client.</p></li><li><p><i class="parameter"><tt>%c</tt></i> - the number of printed pages of the spooled job (if known).</p></li><li><p><i class="parameter"><tt>%z</tt></i> - the size of the spooled print job (in bytes)</p></li></ul></div><p> The print command MUST contain at least one occurrence of <i class="parameter"><tt>%s</tt></i> or <i class="parameter"><tt>%f</tt></i>. -- The <i class="parameter"><tt>%p</tt></i> is optional. If no printer name is supplied, the <i class="parameter"><tt>%p</tt></i> will be silently removed from the print command. In this case the job is sent to the default printer. </p><p> If specified in the <i class="parameter"><tt>[global]</tt></i> section, the print command given will be used for any printable service that does not have its own print command specified. If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed! And (most importantly): print files will not be removed, so they will start filling your Samba hard disk. </p><p> Note that printing may fail on some UNIXes from the "nobody" account. If this happens, create an alternative guest account and supply it with the privilege to print. Set up this guest account in the <i class="parameter"><tt>[global]</tt></i> section with the <i class="parameter"><tt>guest account</tt></i> parameter. </p><p> You can form quite complex print commands. You need to realize that print commands are just passed to a UNIX shell. The shell is able to expand the included environment variables as usual. (The syntax to include a UNIX environment variable <i class="parameter"><tt>$variable</tt></i> in or in the Samba print command is <i class="parameter"><tt>%$variable</tt></i>.) To give you a working <a class="indexterm" name="id2899504"></a><i class="parameter"><tt>print command</tt></i> example, the following will log a print job to <tt class="filename">/tmp/print.log</tt>, print the file, then remove it. Note that ';' is the usual separator for commands in shell scripts: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s</tt></i></td></tr></table><p> You may have to vary your own command considerably from this example depending on how you normally print files on your system. The default for the <a class="indexterm" name="id2899553"></a><i class="parameter"><tt>print command</tt></i> parameter varies depending on the setting of the <a class="indexterm" name="id2899570"></a><i class="parameter"><tt>printing</tt></i> parameter. Another example is: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>print command = /usr/local/samba/bin/myprintscript %p %s</tt></i></td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2899603"></a>Innovations in Samba Printing since 2.2</h2></div></div><div></div></div><p> Before version 2.2.0, Samba's print server support for Windows clients was limited to the level of <span class="emphasis"><em>LanMan</em></span> printing calls. This is the same protocol level as Windows 9x PCs offer when they share printers. Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These are implemented via <span class="emphasis"><em>MS-RPC</em></span> (RPC = <span class="emphasis"><em>Remote Procedure Calls</em></span> ). MS-RPCs use the <span class="emphasis"><em>SPOOLSS</em></span> named pipe for all printing. </p><p> The additional functionality provided by the new SPOOLSS support includes: </p><div class="itemizedlist"><ul type="disc"><li><p>Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon demand (<span class="emphasis"><em>Point'n'Print</em></span>); </p></li><li><p>Uploading of printer drivers via the Windows NT <span class="emphasis"><em>Add Printer Wizard</em></span> (APW) or the <a href="http://imprints.sourceforge.net/" target="_top">Imprints</a> tool set. </p></li><li><p>Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), etc... (See the <a href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a> for more information on the Win32 printing API);</p></li><li><p>Support for NT <span class="emphasis"><em>Access Control Lists</em></span> (ACL) on printer objects;</p></li><li><p>Improved support for printer queue manipulation through the use of internal databases for spooled job information (implemented by various <tt class="filename">*.tdb</tt> files).</p></li></ul></div><p> One other benefit of an update is this: Samba 3 is able to publish all its printers in Active Directory (or LDAP)! </p><p> One slight difference is here: it is possible on a Windows NT print server to have printers listed in the Printers folder which are <span class="emphasis"><em>not</em></span> shared. Samba does not make this distinction. By definition, the only printers of which Samba is aware are those which are specified as shares in . The reason is that Windows NT/200x/XP Professional clients do not normally need to use the standard SMB printer share; rather they can print directly to any printer on another Windows NT host using MS-RPC. This of course assumes that the printing client has the necessary privileges on the remote host serving the printer. The default permissions assigned by Windows NT to a printer gives the "Print" permissions to the well-known <span class="emphasis"><em>Everyone</em></span> group. (The older clients of type Win9x can only print to "shared" printers). </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899763"></a>Client Drivers on Samba Server for <span class="emphasis"><em>Point'n'Print</em></span></h3></div></div><div></div></div><p> There is still confusion about what all this means: <span class="emphasis"><em>Is it or is it not a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients?</em></span> The answer to this is: No, it is not a <span class="emphasis"><em>requirement</em></span>. Windows NT/2000 clients can, of course, also run their APW to install drivers <span class="emphasis"><em>locally</em></span> (which then connect to a Samba served print queue). This is the same method as used by Windows 9x clients. (However, a <span class="emphasis"><em>bug</em></span> existed in Samba 2.2.0 which made Windows NT/2000 clients require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1). </p><p> But it is a new <span class="emphasis"><em>option</em></span> to install the printer drivers into the <i class="parameter"><tt>[print$]</tt></i> share of the Samba server, and a big convenience too. Then <span class="emphasis"><em>all</em></span> clients (including 95/98/ME) get the driver installed when they first connect to this printer share. The <span class="emphasis"><em>uploading</em></span> or <span class="emphasis"><em>depositing</em></span> of the driver into this <i class="parameter"><tt>[print$]</tt></i> share, and the following binding of this driver to an existing Samba printer share can be achieved by different means: </p><div class="itemizedlist"><ul type="disc"><li><p>running the <span class="emphasis"><em>APW</em></span> on an NT/200x/XP Professional client (this doesn't work from 95/98/ME clients);</p></li><li><p>using the <span class="emphasis"><em>Imprints</em></span> toolset;</p></li><li><p>using the <span class="emphasis"><em>smbclient</em></span> and <span class="emphasis"><em>rpcclient</em></span> commandline tools;</p></li><li><p>using <span class="emphasis"><em>cupsaddsmb</em></span>(only works for the CUPS printing system, not for LPR/LPD, LPRng etc.).</p></li></ul></div><p> Please take additional note of the following fact: <span class="emphasis"><em>Samba does not use these uploaded drivers in any way to process spooled files</em></span>. Drivers are utilized entirely by the clients, who download and install them via the "Point'n'Print" mechanism supported by Samba. The clients use these drivers to generate print files in the format the printer (or the UNIX print system) requires. Print files received by Samba are handed over to the UNIX printing system, which is responsible for all further processing, if needed. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2899925"></a>The [printer$] Section is removed from Samba 3</h3></div></div><div></div></div><p><b> <i class="parameter"><tt>[print$]</tt></i> vs. <i class="parameter"><tt>[printer$]</tt></i> .�</b> Versions of Samba prior to 2.2 made it possible to use a share named <span class="emphasis"><em>[printer$]</em></span>. This name was taken from the same named service created by Windows 9x clients when a printer was shared by them. Windows 9x printer servers always have a <i class="parameter"><tt>[printer$]</tt></i> service which provides read-only access (with no password required) in order to support printer driver downloads. However, Samba's initial implementation allowed for a parameter named <i class="parameter"><tt>printer driver location</tt></i> to be used on a per share basis. This specified the location of the driver files associated with that printer. Another parameter named <i class="parameter"><tt>printer driver</tt></i> provided a means of defining the printer driver name to be sent to the client. These parameters, including the <i class="parameter"><tt>printer driver file</tt></i> parameter, are now removed and can not be used in installations of samba-3. Now the share name <i class="parameter"><tt>[print$]</tt></i> is used for the location of downloadable printer drivers. It is taken from the <i class="parameter"><tt>[print$]</tt></i> service created by Windows NT PCs when a printer is shared by them. Windows NT print servers always have a <i class="parameter"><tt>[print$]</tt></i> service which provides read-write access (in the context of its ACLs) in order to support printer driver down- and uploads. Don't fear -- this does not mean Windows 9x clients are thrown aside now. They can use Samba's <i class="parameter"><tt>[print$]</tt></i> share support just fine. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900037"></a>Creating the [print$] Share</h3></div></div><div></div></div><p> In order to support the up- and downloading of printer driver files, you must first configure a file share named <i class="parameter"><tt>[print$]</tt></i>. The "public" name of this share is hard coded in Samba's internals (because it is hard coded in the MS Windows clients too). It cannot be renamed since Windows clients are programmed to search for a service of exactly this name if they want to retrieve printer driver files. </p><p> You should modify the server's file to add the global parameters and create the <i class="parameter"><tt>[print$]</tt></i> file share (of course, some of the parameter values, such as 'path' are arbitrary and should be replaced with appropriate values for your site): </p><div class="example"><a name="id2900085"></a><p class="title"><b>Example�18.3.�[print\$] example</b></p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td># members of the ntadmin group should be able to add drivers and set</td></tr><tr><td># printer properties. root is implicitly always a 'printer admin'.</td></tr><tr><td><i class="parameter"><tt>printer admin = @ntadmin</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[printers]</tt></i></td></tr><tr><td>...</td></tr><tr><td> </td></tr><tr><td><i class="parameter"><tt>[print$]</tt></i></td></tr><tr><td><i class="parameter"><tt>comment = Printer Driver Download Area</tt></i></td></tr><tr><td><i class="parameter"><tt>path = /etc/samba/drivers</tt></i></td></tr><tr><td><i class="parameter"><tt>browseable = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>guest ok = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>read only = yes</tt></i></td></tr><tr><td><i class="parameter"><tt>write list = @ntadmin, root</tt></i></td></tr></table></div><p> Of course, you also need to ensure that the directory named by the <a class="indexterm" name="id2900210"></a><i class="parameter"><tt>path</tt></i> parameter exists on the UNIX file system. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900227"></a>Parameters in the [print$] Section</h3></div></div><div></div></div><p> <i class="parameter"><tt>[print$]</tt></i> is a special section in . It contains settings relevant to potential printer driver download and local installation by clients. </p><div class="variablelist"><dl><dt><span class="term"><a class="indexterm" name="id2900255"></a><i class="parameter"><tt>comment</tt></i> = Printer Driver Download Area</span></dt><dd><p> the comment appears next to the share name if it is listed in a share list (usually Windows clients won't see it often but it will also appear up in a <b class="command">smbclient -L sambaserver </b> output). </p></dd><dt><span class="term"><a class="indexterm" name="id2900290"></a><i class="parameter"><tt>path</tt></i> = /etc/samba/printers</span></dt><dd><p> this is the path to the location of the Windows driver file deposit from the UNIX point of view.</p></dd><dt><span class="term"><a class="indexterm" name="id2900315"></a><i class="parameter"><tt>browseable</tt></i> = no</span></dt><dd><p> this makes the <i class="parameter"><tt>[print$]</tt></i> share "invisible" in Network Neighbourhood to clients. However, you can still "mount" it from any client using the <b class="command">net use g:\\sambaserver\print$</b> command in a "DOS box" or the "Connect network drive" menu from Windows Explorer.</p></dd><dt><span class="term"><a class="indexterm" name="id2900360"></a><i class="parameter"><tt>guest ok</tt></i> = yes</span></dt><dd><p>this gives read only access to this share for all guest users. Access may be used to download and install printer drivers on clients. The requirement for <i class="parameter"><tt>guest ok = yes</tt></i> depends upon how your site is configured. If users will be guaranteed to have an account on the Samba host, then this is a non-issue.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The non-issue is this: if all your Windows NT users are guaranteed to be authenticated by the Samba server (for example if Samba authenticates via an NT domain server and the NT user has already been validated by the Domain Controller in order to logon to the Windows NT session), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share for guest access. You'll probably want to add <a class="indexterm" name="id2900407"></a><i class="parameter"><tt>map to guest</tt></i> = Bad User in the <i class="parameter"><tt>[global]</tt></i> section as well. Make sure you understand what this parameter does before using it. </p></div></dd><dt><span class="term"><a class="indexterm" name="id2900434"></a><i class="parameter"><tt>read only</tt></i> = yes</span></dt><dd><p>as we don't want everybody to upload driver files (or even change driver settings) we tagged this share as not writeable.</p></dd><dt><span class="term"><a class="indexterm" name="id2900461"></a><i class="parameter"><tt>write list</tt></i> = @ntadmin,root</span></dt><dd><p>since the <i class="parameter"><tt>[print$]</tt></i> was made read only by the previous setting, we need to create a "write list" also. UNIX groups (denoted with a leading "@" character) and users listed here are allowed write access (as an exception to the general public's "read-only" access), which they need to update files on the share. Normally you will want to only name administrative level user accounts in this setting. Check the file system permissions to make sure these accounts can copy files to the share. If this is a non-root account, then the account should also be mentioned in the global <a class="indexterm" name="id2900517"></a><i class="parameter"><tt>printer admin </tt></i> parameter. See the man page for more information on configuring file shares. </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900537"></a>Subdirectory Structure in [print$]</h3></div></div><div></div></div><p> In order for a Windows NT print server to support the downloading of driver files by multiple client architectures, you must create several subdirectories within the <i class="parameter"><tt>[print$]</tt></i> service (i.e. the UNIX directory named by the <a class="indexterm" name="id2900557"></a><i class="parameter"><tt>path</tt></i> parameter). These correspond to each of the supported client architectures. Samba follows this model as well. Just like the name of the <i class="parameter"><tt>[print$]</tt></i> share itself, the subdirectories *must* be exactly the names listed below (you may leave out the subdirectories of architectures you don't want to support). </p><p> Therefore, create a directory tree below the <i class="parameter"><tt>[print$]</tt></i> share for each architecture you wish to support. </p><pre class="programlisting"> [print$]--+-- |--W32X86 # serves drivers to "Windows NT x86" |--WIN40 # serves drivers to "Windows 95/98" |--W32ALPHA # serves drivers to "Windows NT Alpha_AXP" |--W32MIPS # serves drivers to "Windows NT R4000" |--W32PPC # serves drivers to "Windows NT PowerPC" </pre><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Required permissions</h3><p> In order to add a new driver to your Samba host, one of two conditions must hold true: </p><div class="itemizedlist"><ul type="disc"><li><p>The account used to connect to the Samba host must have a UID of 0 (i.e. a root account)</p></li><li><p>The account used to connect to the Samba host must be named in the <span class="emphasis"><em>printer admin</em></span>list.</p></li></ul></div><p> Of course, the connected account must still possess access to add files to the subdirectories beneath <i class="parameter"><tt>[print$]</tt></i>. Remember that all file shares are set to 'read only' by default. </p></div><p> Once you have created the required <i class="parameter"><tt>[print$]</tt></i> service and associated subdirectories, go to a Windows NT 4.0/2k/XP client workstation. Open <span class="guiicon">Network Neighbourhood</span> or <span class="guiicon">My Network Places</span> and browse for the Samba host. Once you have located the server, navigate to its <span class="guiicon">Printers and Faxes</span> folder. You should see an initial listing of printers that matches the printer shares defined on your Samba host. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2900710"></a>Installing Drivers into [print$]</h2></div></div><div></div></div><p> You have successfully created the <i class="parameter"><tt>[print$]</tt></i> share in ? And Samba has re-read its configuration? Good. But you are not yet ready to take off. The <span class="emphasis"><em>driver files</em></span> need to be present in this share, too! So far it is still an empty share. Unfortunately, it is not enough to just copy the driver files over. They need to be <span class="emphasis"><em>set up</em></span> too. And that is a bit tricky, to say the least. We will now discuss two alternative ways to install the drivers into <i class="parameter"><tt>[print$]</tt></i>: </p><div class="itemizedlist"><ul type="disc"><li><p>using the Samba commandline utility <b class="command">rpcclient</b> with its various subcommands (here: <b class="command">adddriver</b> and <b class="command">setdriver</b>) from any UNIX workstation;</p></li><li><p>running a GUI (<span class="emphasis"><em>Printer Properties</em></span> and <span class="emphasis"><em>Add Printer Wizard</em></span>) from any Windows NT/2k/XP client workstation.</p></li></ul></div><p> The latter option is probably the easier one (even if the only entrance to this realm seems a little bit weird at first). </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2900805"></a>Setting Drivers for existing Printers with a Client GUI</h3></div></div><div></div></div><p> The initial listing of printers in the Samba host's <span class="guiicon">Printers</span> folder accessed from a client's Explorer will have no real printer driver assigned to them. By default this driver name is set to a NULL string. This must be changed now. The local <span class="emphasis"><em>Add Printer Wizard</em></span>, run from NT/2000/XP clients, will help us in this task. </p><p> However, the job to set a valid driver for the printer is not a straightforward one: You must attempt to view the printer properties for the printer to which you want the driver assigned. Open the Windows Explorer, open Network Neighbourhood, browse to the Samba host, open Samba's <span class="guiicon">Printers</span> folder, right-click the printer icon and select <span class="guimenu">Properties...</span>. You are now trying to view printer and driver properties for a queue which has this default <tt class="constant">NULL</tt> driver assigned. This will result in an error message (this is normal here): </p><p><span class="errorname"> Device settings cannot be displayed. The driver for the specified printer is not installed, only spooler properties will be displayed. Do you want to install the driver now?</span></p><p> <span class="emphasis"><em>Important:</em></span>Don't click <span class="guibutton">Yes</span>! Instead, <span class="emphasis"><em>click <span class="guibutton">No</span></em></span> in the error dialog. Only now you will be presented with the printer properties window. From here, the way to assign a driver to a printer is open to us. You have now the choice either: </p><div class="itemizedlist"><ul type="disc"><li><p>select a driver from the pop-up list of installed drivers. <span class="emphasis"><em>Initially this list will be empty.</em></span> Or</p></li><li><p>use the <span class="guibutton">New Driver...</span> button to install a new printer driver (which will in fact start up the APW).</p></li></ul></div><p> Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure your connection is in fact setup as a user with <a class="indexterm" name="id2900939"></a><i class="parameter"><tt>printer admin</tt></i> privileges (if in doubt, use <b class="command">smbstatus</b> to check for this). If you wish to install printer drivers for client operating systems other than <span class="application">Windows NT x86</span>, you will need to use the <span class="guilabel">Sharing</span> tab of the printer properties dialog. </p><p> Assuming you have connected with an administrative (or root) account (as named by the <a class="indexterm" name="id2900981"></a><i class="parameter"><tt>printer admin</tt></i> parameter), you will also be able to modify other printer properties such as ACLs and default device settings using this dialog. For the default device settings, please consider the advice given further below. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2901002"></a>Setting Drivers for existing Printers with <b class="command">rpcclient</b></h3></div></div><div></div></div><p> The second way to install printer drivers into <i class="parameter"><tt>[print$]</tt></i> and set them up in a valid way can be done from the UNIX command line. This involves four distinct steps: </p><div class="orderedlist"><ol type="1"><li><p>gathering the info about the required driver files and collecting the files together;</p></li><li><p>deposit the driver files into the <i class="parameter"><tt>[print$]</tt></i> share's correct subdirectories (possibly by using <b class="command">smbclient</b>);</p></li><li><p>running the <b class="command">rpcclient</b> commandline utility once with the <b class="command">adddriver</b> subcommand,</p></li><li><p>running <b class="command">rpcclient</b> a second time with the <b class="command">setdriver</b> subcommand.</p></li></ol></div><p> We will provide detailed hints for each of these steps in the next few paragraphs. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901111"></a>Identifying the Driver Files</h4></div></div><div></div></div><p> To find out about the driver files, you have two options: you could investigate the driver CD which comes with your printer. Study the <tt class="filename">*.inf</tt> file on the CD, if it is contained. This may not be the possible, since the *.inf file might be missing. Unfortunately, many vendors have now started to use their own installation programs. These installations packages are often some sort of Windows platform archive format, plus, the files may get re-named during the installation process. This makes it extremely difficult to identify the driver files you need. </p><p> Then you only have the second option: install the driver first on a Windows client *locally* and investigate which file names and paths it uses after they are installed. (Note, that you need to repeat this procedure for every client platform you want to support. We are going to show it here for the <span class="application">W32X86</span> platform only, a name used by Microsoft for all WinNT/2k/XP clients...) </p><p> A good method to recognize the driver files this is to print the test page from the driver's <span class="guilabel">Properties</span> Dialog (<span class="guilabel">General</span> tab). Then look at the list of driver files named on the printout. You'll need to recognize what Windows (and Samba) are calling the <span class="guilabel">Driver File</span> , the <span class="guilabel">Data File</span>, the <span class="guilabel">Config File</span>, the <span class="guilabel">Help File</span> and (optionally) the <span class="guilabel">Dependent Driver Files</span> (this may vary slightly for Windows NT). You need to remember all names (or better take a note) for the next steps. </p><p> Another method to quickly test the driver filenames and related paths is provided by the <b class="command">rpcclient</b> utility. Run it with <b class="command">enumdrivers</b> or with the <b class="command">getdriver</b> subcommand, each in the <span class="emphasis"><em>3</em></span> level. In the following example, <span class="emphasis"><em>TURBO_XP</em></span> is the name of the Windows PC (in this case it was a Windows XP Professional laptop, BTW). I had installed the driver locally to TURBO_XP while <span class="emphasis"><em>kde-bitshop</em></span> is the name of the Linux host from which I am working. We could run an <span class="emphasis"><em>interactive</em></span> <b class="command">rpcclient</b> session; then we'd get an <span class="emphasis"><em>rpcclient /></em></span> prompt and would type the subcommands at this prompt. This is left as a good exercise to the reader. For now we use <b class="command">rpcclient</b> with the <tt class="option">-c</tt> parameter to execute a single subcommand line and exit again. This is the method you would use if you want to create scripts to automate the procedure for a large number of printers and drivers. Note the different quotes used to overcome the different spaces in between words: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'Danka%xxxx' -c \ 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP</tt></b> cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3 [Windows NT x86] Printer Driver Info 3: Version: [2] Driver Name: [Heidelberg Digimaster 9110 (PS)] Architecture: [Windows NT x86] Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL] Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd] Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL] Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll] Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF] Monitorname: [] Defaultdatatype: [] </pre><p> You may notice, that this driver has quite a big number of <span class="guilabel">Dependentfiles</span> (I know worse cases however). Also, strangely, the <span class="guilabel">Driver File</span> is here tagged as <span class="guilabel">Driver Path</span>.... oh, well. Here we don't have yet support for the so-called <span class="application">WIN40</span> architecture installed. This name is used by Microsoft for the Win95/98/ME platforms. If we want to support these, we need to install the Win95/98/ME driver files in addition to those for <span class="application">W32X86</span> (i.e. the WinNT72000/XP clients) onto a Windows PC. This PC can also host the Win9x drivers, even if itself runs on Windows NT, 2000 or XP. </p><p> Since the <i class="parameter"><tt>[print$]</tt></i> share is usually accessible through the <span class="guiicon">Network Neighbourhood</span>, you can also use the UNC notation from Windows Explorer to poke at it. The Win9x driver files will end up in subdirectory "0" of the "WIN40" directory. The full path to access them will be <tt class="filename">\\WINDOWSHOST\print$\WIN40\0\</tt>. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> more recent drivers on Windows 2000 and Windows XP are installed into the "3" subdirectory instead of the "2". The version 2 of drivers, as used in Windows NT, were running in Kernel Mode. Windows 2000 changed this. While it still can use the Kernel Mode drivers (if this is enabled by the Admin), its native mode for printer drivers is User Mode execution. This requires drivers designed for this. These type of drivers install into the "3" subdirectory. </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901474"></a>Collecting the Driver Files from a Windows Host's [print$] Share</h4></div></div><div></div></div><p> Now we need to collect all the driver files we identified. in our previous step. Where do we get them from? Well, why not retrieve them from the very PC and the same <i class="parameter"><tt>[print$]</tt></i> share which we investigated in our last step to identify the files? We can use <b class="command">smbclient</b> to do this. We will use the paths and names which were leaked to us by <b class="command">getdriver</b>. The listing is edited to include linebreaks for readability: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \ -c 'cd W32X86/2;mget HD*_de.* \ hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL'</tt></b> added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] <tt class="prompt">Get file Hddm91c1_de.ABD? </tt><b class="userinput"><tt>n</tt></b> <tt class="prompt">Get file Hddm91c1_de.def? </tt><b class="userinput"><tt>y</tt></b> getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def <tt class="prompt">Get file Hddm91c1_de.DLL? </tt><b class="userinput"><tt>y</tt></b> getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL [...] </pre><p> After this command is complete, the files are in our current local directory. You probably have noticed that this time we passed several commands to the <tt class="option">-c</tt> parameter, separated by semi-colons. This effects that all commands are executed in sequence on the remote Windows server before smbclient exits again. </p><p> Don't forget to repeat the procedure for the <span class="application">WIN40</span> architecture should you need to support Win95/98/XP clients. Remember, the files for these architectures are in the WIN40/0/ subdir. Once we are complete, we can run <b class="command">smbclient ... put</b> to store the collected files on the Samba server's <i class="parameter"><tt>[print$]</tt></i> share. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901624"></a>Depositing the Driver Files into [print$]</h4></div></div><div></div></div><p> So, now we are going to put the driver files into the <i class="parameter"><tt>[print$]</tt></i> share. Remember, the UNIX path to this share has been defined previously in your . You also have created subdirectories for the different Windows client types you want to support. Supposing your <i class="parameter"><tt>[print$]</tt></i> share maps to the UNIX path <tt class="filename">/etc/samba/drivers/</tt>, your driver files should now go here: </p><div class="itemizedlist"><ul type="disc"><li><p>for all Windows NT, 2000 and XP clients into <tt class="filename">/etc/samba/drivers/W32X86/</tt> <span class="emphasis"><em>but *not*(yet) into the "2" subdir</em></span>!</p></li><li><p>for all Windows 95, 98 and ME clients into <tt class="filename">/etc/samba/drivers/WIN40/</tt> -- <span class="emphasis"><em>but *not* (yet) into the "0" subdir</em></span>!</p></li></ul></div><p> We again use smbclient to transfer the driver files across the network. We specify the same files and paths as were leaked to us by running <b class="command">getdriver</b> against the original <span class="emphasis"><em>Windows</em></span> install. However, now we are going to store the files into a <span class="emphasis"><em>Samba/UNIX</em></span> print server's <i class="parameter"><tt>[print$]</tt></i> share... </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \ 'cd W32X86; put HDNIS01_de.DLL; \ put Hddm91c1_de.ppd; put HDNIS01U_de.DLL; \ put HDNIS01U_de.HLP; put Hddm91c1_de.DLL; \ put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL; \ put Hddm91c1_de.dat; put Hddm91c1_de.dat; \ put Hddm91c1_de.def; put Hddm91c1_de.hre; \ put Hddm91c1_de.vnd; put Hddm91c1_de.hlp; \ put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll; \ put HDNIS01_de.NTF'</tt></b> added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 Got a positive name query response from 10.160.51.162 ( 10.160.51.162 ) Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF </pre><p> Phewww -- that was a lot of typing! Most drivers are a lot smaller -- many only having 3 generic PostScript driver files plus 1 PPD. Note, that while we did retrieve the files from the "2" subdirectory of the "W32X86" directory from the Windows box, we <span class="emphasis"><em>don't</em></span> put them (for now) in this same subdirectory of the Samba box! This re-location will automatically be done by the <b class="command">adddriver</b> command which we will run shortly (and don't forget to also put the files for the Win95/98/ME architecture into the <tt class="filename">WIN40/</tt> subdirectory should you need them). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901819"></a>Check if the Driver Files are there (with smbclient)</h4></div></div><div></div></div><p> For now we verify that our files are there. This can be done with <b class="command">smbclient</b> too (but of course you can log in via SSH also and do this through a standard UNIX shell access too): </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \ -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'</tt></b> added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 Got a positive name query response from 10.160.51.162 ( 10.160.51.162 ) Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] Current directory is \\SAMBA-CUPS\print$\W32X86\ . D 0 Sun May 4 03:56:35 2003 .. D 0 Thu Apr 10 23:47:40 2003 2 D 0 Sun May 4 03:56:18 2003 HDNIS01Aux.dll A 15356 Sun May 4 03:58:59 2003 Hddm91c1KMMin.DLL A 46966 Sun May 4 03:58:59 2003 HDNIS01_de.DLL A 434400 Sun May 4 03:58:59 2003 HDNIS01_de.NTF A 790404 Sun May 4 03:56:35 2003 Hddm91c1_de.DLL A 876544 Sun May 4 03:58:59 2003 Hddm91c1_de.INI A 101 Sun May 4 03:58:59 2003 Hddm91c1_de.dat A 5044 Sun May 4 03:58:59 2003 Hddm91c1_de.def A 428 Sun May 4 03:58:59 2003 Hddm91c1_de.hlp A 37699 Sun May 4 03:58:59 2003 Hddm91c1_de.hre A 323584 Sun May 4 03:58:59 2003 Hddm91c1_de.ppd A 26373 Sun May 4 03:58:59 2003 Hddm91c1_de.vnd A 45056 Sun May 4 03:58:59 2003 HDNIS01U_de.DLL A 165888 Sun May 4 03:58:59 2003 HDNIS01U_de.HLP A 19770 Sun May 4 03:58:59 2003 Hddm91c1_de_reg.HLP A 228417 Sun May 4 03:58:59 2003 40976 blocks of size 262144. 709 blocks available Current directory is \\SAMBA-CUPS\print$\W32X86\2\ . D 0 Sun May 4 03:56:18 2003 .. D 0 Sun May 4 03:56:35 2003 ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003 laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003 ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003 ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003 PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003 40976 blocks of size 262144. 709 blocks available </pre><p> Notice that there are already driver files present in the <tt class="filename">2</tt> subdir (probably from a previous installation). Once the files for the new driver are there too, you are still a few steps away from being able to use them on the clients. The only thing you could do *now* is to retrieve them from a client just like you retrieve ordinary files from a file share, by opening print$ in Windows Explorer. But that wouldn't install them per Point'n'Print. The reason is: Samba doesn't know yet that these files are something special, namely <span class="emphasis"><em>printer driver files</em></span> and it doesn't know yet to which print queue(s) these driver files belong. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2901935"></a>Running <b class="command">rpcclient</b> with <b class="command">adddriver</b></h4></div></div><div></div></div><p> So, next you must tell Samba about the special category of the files you just uploaded into the <i class="parameter"><tt>[print$]</tt></i> share. This is done by the <b class="command">adddriver</b> command. It will prompt Samba to register the driver files into its internal TDB database files. The following command and its output has been edited, again, for readability: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \ "dm9110:HDNIS01_de.DLL: \ Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \ NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ HDNIS01Aux.dll,HDNIS01_de.NTF, \ Hddm91c1_de_reg.HLP' SAMBA-CUPS</tt></b> cmd = adddriver "Windows NT x86" \ "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL: \ HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP" Printer Driver dm9110 successfully installed. </pre><p> After this step the driver should be recognized by Samba on the print server. You need to be very careful when typing the command. Don't exchange the order of the fields. Some changes would lead to a <tt class="computeroutput">NT_STATUS_UNSUCCESSFUL</tt> error message. These become obvious. Other changes might install the driver files successfully, but render the driver unworkable. So take care! Hints about the syntax of the adddriver command are in the man page. The CUPS printing chapter of this HOWTO collection provides a more detailed description, if you should need it. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902049"></a>Check how Driver Files have been moved after <b class="command">adddriver</b> finished</h4></div></div><div></div></div><p> One indication for Samba's recognition of the files as driver files is the <tt class="computeroutput">successfully installed</tt> message. Another one is the fact, that our files have been moved by the <b class="command">adddriver</b> command into the <tt class="filename">2</tt> subdirectory. You can check this again with <b class="command">smbclient</b>: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>smbclient //SAMBA-CUPS/print\$ -Uroot%xx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'</tt></b> added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0 Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a] Current directory is \\SAMBA-CUPS\print$\W32X86\ . D 0 Sun May 4 04:32:48 2003 .. D 0 Thu Apr 10 23:47:40 2003 2 D 0 Sun May 4 04:32:48 2003 40976 blocks of size 262144. 731 blocks available Current directory is \\SAMBA-CUPS\print$\W32X86\2\ . D 0 Sun May 4 04:32:48 2003 .. D 0 Sun May 4 04:32:48 2003 DigiMaster.PPD A 148336 Thu Apr 24 01:07:00 2003 ADOBEPS5.DLL A 434400 Sat May 3 23:18:45 2003 laserjet4.ppd A 9639 Thu Apr 24 01:05:32 2003 ADOBEPSU.DLL A 109568 Sat May 3 23:18:45 2003 ADOBEPSU.HLP A 18082 Sat May 3 23:18:45 2003 PDFcreator2.PPD A 15746 Sun Apr 20 22:24:07 2003 HDNIS01Aux.dll A 15356 Sun May 4 04:32:18 2003 Hddm91c1KMMin.DLL A 46966 Sun May 4 04:32:18 2003 HDNIS01_de.DLL A 434400 Sun May 4 04:32:18 2003 HDNIS01_de.NTF A 790404 Sun May 4 04:32:18 2003 Hddm91c1_de.DLL A 876544 Sun May 4 04:32:18 2003 Hddm91c1_de.INI A 101 Sun May 4 04:32:18 2003 Hddm91c1_de.dat A 5044 Sun May 4 04:32:18 2003 Hddm91c1_de.def A 428 Sun May 4 04:32:18 2003 Hddm91c1_de.hlp A 37699 Sun May 4 04:32:18 2003 Hddm91c1_de.hre A 323584 Sun May 4 04:32:18 2003 Hddm91c1_de.ppd A 26373 Sun May 4 04:32:18 2003 Hddm91c1_de.vnd A 45056 Sun May 4 04:32:18 2003 HDNIS01U_de.DLL A 165888 Sun May 4 04:32:18 2003 HDNIS01U_de.HLP A 19770 Sun May 4 04:32:18 2003 Hddm91c1_de_reg.HLP A 228417 Sun May 4 04:32:18 2003 40976 blocks of size 262144. 731 blocks available </pre><p> Another verification is that the timestamp of the printing TDB files is now updated (and possibly their filesize has increased). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902217"></a>Check if the Driver is recognized by Samba</h4></div></div><div></div></div><p> Now the driver should be registered with Samba. We can easily verify this, and will do so in a moment. However, this driver is <span class="emphasis"><em>not yet</em></span> associated with a particular <span class="emphasis"><em>printer</em></span>. We may check the driver status of the files by at least three methods: </p><div class="itemizedlist"><ul type="disc"><li><p>from any Windows client browse Network Neighbourhood, find the Samba host and open the Samba <span class="guiicon">Printers and Faxes</span> folder. Select any printer icon, right-click and select the printer <span class="guimenuitem">Properties</span>. Click on the <span class="guilabel">Advanced</span> tab. Here is a field indicating the driver for that printer. A drop down menu allows you to change that driver (be careful to not do this unwittingly.). You can use this list to view all drivers know to Samba. Your new one should be amongst them. (Each type of client will only see his own architecture's list. If you don't have every driver installed for each platform, the list will differ if you look at it from Windows95/98/ME or WindowsNT/2000/XP.)</p></li><li><p>from a Windows 2000 or XP client (not WinNT) browse <span class="guiicon">Network Neighbourhood</span>, search for the Samba server and open the server's <span class="guiicon">Printers</span> folder, right-click the white background (with no printer highlighted). Select <span class="guimenuitem">Server Properties</span>. On the <span class="guilabel">Drivers</span> tab you will see the new driver listed now. This view enables you to also inspect the list of files belonging to that driver<span class="emphasis"><em> (this doesn't work on Windows NT, but only on Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" tab).</em></span>. An alternative, much quicker method for Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the name to your Samba server instead of <i class="replaceable"><tt>SAMBA-CUPS</tt></i>): </p><p><b class="userinput"><tt> rundll32 printui.dll,PrintUIEntry /s /t2 /n\\<i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b></p></li><li><p>from a UNIX prompt run this command (or a variant thereof), where <i class="replaceable"><tt>SAMBA-CUPS</tt></i> is the name of the Samba host and "xxxx" represents the actual Samba password assigned to root: </p><p><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'enumdrivers' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b></p><p> You will see a listing of all drivers Samba knows about. Your new one should be amongst them. But it is only listed under the <i class="parameter"><tt>[Windows NT x86]</tt></i> heading, not under <i class="parameter"><tt>[Windows 4.0]</tt></i>, since we didn't install that part. Or did *you*? -- You will see a listing of all drivers Samba knows about. Your new one should be amongst them. In our example it is named <span class="emphasis"><em>dm9110</em></span>. Note that the 3rd column shows the other installed drivers twice, for each supported architecture one time. Our new driver only shows up for <span class="application">Windows NT 4.0 or 2000</span>. To have it present for <span class="application">Windows 95, 98 and ME</span> you'll have to repeat the whole procedure with the WIN40 architecture and subdirectory. </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902426"></a>A side note: you are not bound to specific driver names</h4></div></div><div></div></div><p> You can name the driver as you like. If you repeat the <b class="command">adddriver</b> step, with the same files as before, but with a different driver name, it will work the same: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -Uroot%xxxx \ -c 'adddriver "Windows NT x86" \ "myphantasydrivername:HDNIS01_de.DLL: \ Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP: \ NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS </tt></b> cmd = adddriver "Windows NT x86" "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\ HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre, \ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP" Printer Driver myphantasydrivername successfully installed. </pre><p> You will also be able to bind that driver to any print queue (however, you are responsible yourself that you associate drivers to queues which make sense to the target printer). Note, that you can't run the <b class="command">rpcclient</b> <b class="command">adddriver</b> command repeatedly. Each run "consumes" the files you had put into the <i class="parameter"><tt>[print$]</tt></i> share by moving them into the respective subdirectories. So you <span class="emphasis"><em>must</em></span> precede an <b class="command">smbclient ... put</b> command before each <b class="command">rpcclient ... adddriver</b>" command. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2902559"></a>Running <b class="command">rpcclient</b> with <b class="command">setdriver</b></h4></div></div><div></div></div><p> Samba still needs to know <span class="emphasis"><em>which</em></span> printer's driver this is. It needs to create a mapping of the driver to a printer, and store this info in its "memory", the TDB files. The <b class="command">rpcclient setdriver</b> command achieves exactly this: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'setdriver dm9110 myphantasydrivername' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b> cmd = setdriver dm9110 myphantasydrivername Successfully set dm9110 to driver myphantasydrivername. </pre><p> Ahhhhh -- no, I didn't want to do that. Repeat, this time with the name I intended: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U'root%xxxx' -c 'setdriver dm9110 dm9110' <i class="replaceable"><tt>SAMBA-CUPS</tt></i></tt></b> cmd = setdriver dm9110 dm9110 Successfully set dm9110 to driver dm9110. </pre><p> The syntax of the command is <b class="userinput"><tt>rpcclient -U'root%<i class="replaceable"><tt>sambapassword</tt></i>' -c 'setdriver "<i class="replaceable"><tt>printername</tt></i>" "<i class="replaceable"><tt>drivername</tt></i>' <i class="replaceable"><tt>SAMBA-Hostname</tt></i></tt></b> . -- Now we have done *most* of the work. But not yet all.... </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> the <b class="command">setdriver</b> command will only succeed if the printer is known to Samba already. A bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba, or at least send a HUP signal to all running smbd processes to work around this: <b class="userinput"><tt>kill -HUP `pidof smbd`</tt></b>. </p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2902712"></a>Client Driver Install Procedure</h2></div></div><div></div></div><p> A famous philosopher said once: “<span class="quote">The Proof of the Pudding lies in the Eating</span>”. The proof for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is not as straightforward as it may seem. Read on. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902731"></a>The first Client Driver Installation</h3></div></div><div></div></div><p> Especially important is the installation onto the first client PC (for each architectural platform separately). Once this is done correctly, all further clients are easy to setup and shouldn't need further attention. What follows is a description for the recommended first procedure. You work now from a client workstation. First you should guarantee that your connection is not unwittingly mapped to <span class="emphasis"><em>bad user</em></span> "nobody". In a DOS box type: </p><p><b class="userinput"><tt>net use \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\print$ /user:root</tt></b></p><p> Replace root, if needed, by another valid <i class="replaceable"><tt>printer admin</tt></i> user as given in the definition. Should you already be connected as a different user, you'll get an error message. There is no easy way to get rid of that connection, because Windows doesn't seem to know a concept of "logging off" from a share connection (don't confuse this with logging off from the local workstation; that is a different matter). You can try to close <span class="emphasis"><em>all</em></span> Windows file explorer and Internet Explorer windows. As a last resort, you may have to reboot. Make sure there is no automatic re-connection set up. It may be easier to go to a different workstation and try from there. After you have made sure you are connected as a printer admin user (you can check this with the <b class="command">smbstatus</b> command on Samba) do this from the Windows workstation: </p><div class="itemizedlist"><ul type="disc"><li><p>Open <span class="guiicon">Network Neighbourhood</span></p></li><li><p>Browse to Samba server</p></li><li><p>Open its <span class="guiicon">Printers and Faxes</span> folder</p></li><li><p>Highlight and right-click the printer</p></li><li><p>Select <span class="guimenuitem">Connect...</span> (for WinNT4/2K it is possibly <span class="guimenuitem">Install...</span>)</p></li></ul></div><p> A new printer (named <i class="replaceable"><tt>printername</tt></i> on samba-server) should now have appeared in your <span class="emphasis"><em>local</em></span> Printer folder (check <span class="guimenu">Start</span> -- <span class="guimenuitem">Settings</span> -- <span class="guimenuitem">Control Panel</span> -- <span class="guiicon">Printers and Faxes</span>). </p><p> Most likely you are now tempted to try and print a test page. After all, you now can open the printer properties and on the "General" tab, there is a button offering to do just that. But chances are that you get an error message saying <span class="errorname">Unable to print Test Page</span>. The reason might be that there is not yet a valid Device Mode set for the driver, or that the "Printer Driver Data" set is still incomplete. </p><p> You must now make sure that a valid "Device Mode" is set for the driver. Don't fear -- we will explain now what that means. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2902934"></a>IMPORTANT! Setting Device Modes on new Printers</h3></div></div><div></div></div><p> In order for a printer to be truly usable by a Windows NT/2K/XP client, it must possess: </p><div class="itemizedlist"><ul type="disc"><li><p>a valid <span class="emphasis"><em>Device Mode</em></span> generated by the driver for the printer (defining things like paper size, orientation and duplex settings), and</p></li><li><p>a complete set of <span class="emphasis"><em>Printer Driver Data</em></span> generated by the driver.</p></li></ul></div><p> If either one of these is incomplete, the clients can produce less than optimal output at best. In the worst cases, unreadable garbage or nothing at all comes from the printer or they produce a harvest of error messages when attempting to print. Samba stores the named values and all printing related info in its internal TDB database files <tt class="filename">(ntprinters.tdb</tt>, <tt class="filename">ntdrivers.tdb</tt>, <tt class="filename">printing.tdb</tt> and <tt class="filename">ntforms.tdb</tt>). </p><p> What do these two words stand for? Basically, the Device Mode and the set of Printer Driver Data is a collection of settings for all print queue properties, initialized in a sensible way. Device Modes and Printer Driver Data should initially be set on the print server (that is here: the Samba host) to healthy values so that the clients can start to use them immediately. How do we set these initial healthy values? This can be achieved by accessing the drivers remotely from an NT (or 2k/XP) client, as is discussed in the next paragraphs. </p><p> Be aware, that a valid Device Mode can only be initiated by a <a class="indexterm" name="id2903030"></a><i class="parameter"><tt>printer admin</tt></i>, or root (the reason should be obvious). Device Modes can only correctly be set by executing the printer driver program itself. Since Samba can not execute this Win32 platform driver code, it sets this field initially to NULL (which is not a valid setting for clients to use). Fortunately, most drivers generate themselves the Printer Driver Data that is needed, when they are uploaded to the <i class="parameter"><tt>[print$]</tt></i> share with the help of the APW or rpcclient. </p><p> The generation and setting of a first valid Device Mode however requires some "tickling" from a client, to set it on the Samba server. The easiest means of doing so is to simply change the page orientation on the server's printer. This "executes" enough of the printer driver program on the client for the desired effect to happen, and feeds back the new Device Mode to our Samba server. You can use the native Windows NT/2K/XP printer properties page from a Window client for this: </p><div class="itemizedlist"><ul type="disc"><li><p>Browse the <span class="guiicon">Network Neighbourhood</span></p></li><li><p>Find the Samba server</p></li><li><p>Open the Samba server's <span class="guiicon">Printers and Faxes</span> folder</p></li><li><p>Highlight the shared printer in question</p></li><li><p>Right-click the printer (you may already be here, if you followed the last section's description)</p></li><li><p>At the bottom of the context menu select <span class="guimenu">Properties....</span> (if the menu still offers the <span class="guimenuitem">Connect...</span> entry further above, you need to click that one first to achieve the driver installation as shown in the last section)</p></li><li><p>Go to the <span class="guilabel">Advanced</span> tab; click on <span class="guibutton">Printing Defaults...</span></p></li><li><p>Change the "Portrait" page setting to "Landscape" (and back)</p></li><li><p>(Oh, and make sure to <span class="emphasis"><em>apply</em></span> changes between swapping the page orientation to cause the change to actually take effect...).</p></li><li><p>While you're at it, you may optionally also want to set the desired printing defaults here, which then apply to all future client driver installations on the remaining from now on.</p></li></ul></div><p> This procedure has executed the printer driver program on the client platform and fed back the correct Device Mode to Samba, which now stored it in its TDB files. Once the driver is installed on the client, you can follow the analogous steps by accessing the <span class="emphasis"><em>local</em></span> <span class="guiicon">Printers</span> folder too if you are a Samba printer admin user. From now on printing should work as expected. </p><p> Samba also includes a service level parameter name <i class="parameter"><tt>default devmode</tt></i> for generating a default Device Mode for a printer. Some drivers will function well with Samba's default set of properties. Others may crash the client's spooler service. So use this parameter with caution. It is always better to have the client generate a valid device mode for the printer and store it on the server for you. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903234"></a>Further Client Driver Install Procedures</h3></div></div><div></div></div><p> Every further driver may be done by any user, along the lines described above: Browse network, open printers folder on Samba server, right-click printer and choose <span class="guimenuitem">Connect...</span>. Once this completes (should be not more than a few seconds, but could also take a minute, depending on network conditions), you should find the new printer in your client workstation local <span class="guiicon">Printers and Faxes</span> folder. </p><p> You can also open your local <span class="guiicon">Printers and Faxes</span> folder by using this command on Windows 2000 and Windows XP Professional workstations: </p><p><b class="userinput"><tt>rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder </tt></b></p><p> or this command on Windows NT 4.0 workstations: </p><p><b class="userinput"><tt> rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2 </tt></b></p><p> You can enter the commands either inside a <span class="guilabel">DOS box</span> window or in the <span class="guimenuitem">Run command...</span> field from the <span class="guimenu">Start</span> menu. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903328"></a>Always make first Client Connection as root or "printer admin"</h3></div></div><div></div></div><p> After you installed the driver on the Samba server (in its <i class="parameter"><tt>[print$]</tt></i> share, you should always make sure that your first client installation completes correctly. Make it a habit for yourself to build that the very first connection from a client as <a class="indexterm" name="id2903350"></a><i class="parameter"><tt>printer admin</tt></i>. This is to make sure that: </p><div class="itemizedlist"><ul type="disc"><li><p> a first valid <span class="emphasis"><em>Device Mode</em></span> is really initialized (see above for more explanation details), and that</p></li><li><p> the default print settings of your printer for all further client installations are as you want them</p></li></ul></div><p> Do this by changing the orientation to landscape, click <span class="emphasis"><em>Apply</em></span>, and then change it back again. Then modify the other settings (for example, you don't want the default media size set to <span class="emphasis"><em>Letter</em></span>, when you are all using <span class="emphasis"><em>A4</em></span>, right? You may want to set the printer for <span class="emphasis"><em>duplex</em></span> as the default; etc.). </p><p> To connect as root to a Samba printer, try this command from a Windows 2K/XP DOS box command prompt: </p><pre class="screen"> <tt class="prompt">C:\> </tt><b class="userinput"><tt>runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printername</tt></i>"</tt></b> </pre><p> </p><p> You will be prompted for root's Samba-password; type it, wait a few seconds, click on <span class="guibutton">Printing Defaults...</span> and proceed to set the job options as should be used as defaults by all clients. Alternatively, instead of root you can name one other member of the <a class="indexterm" name="id2903470"></a><i class="parameter"><tt>printer admin</tt></i> from the setting. </p><p> Now all the other users downloading and installing the driver the same way (called <span class="emphasis"><em>Point'n'Print</em></span>) will have the same defaults set for them. If you miss this step you'll get a lot of helpdesk calls from your users. But maybe you like to talk to people.... ;-) </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2903500"></a>Other Gotchas</h2></div></div><div></div></div><p> Your driver is installed. It is ready for <span class="emphasis"><em>Point'n'Print</em></span> installation by the clients now. You <span class="emphasis"><em>may</em></span> have tried to download and use it onto your first client machine now. But wait... let's make you acquainted first with a few tips and tricks you may find useful. For example, suppose you didn't manage to "set the defaults" on the printer, as advised in the preceding paragraphs? And your users complain about various issues (such as “<span class="quote">We need to set the paper size for each job from Letter to A4 and it won't store it!</span>”) </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2903534"></a>Setting Default Print Options for the Client Drivers</h3></div></div><div></div></div><p> The last sentence might be viewed with mixed feelings by some users and admins. They have struggled for hours and hours and couldn't arrive at a point were their settings seemed to be saved. It is not their fault. The confusing thing is this: in the multi-tabbed dialog that pops up when you right-click the printer name and select <span class="guimenuitem">Properties...</span>, you can arrive at two identically looking dialogs, each claiming that they help you to set printer options, in three different ways. Here is the definite answer to the "Samba Default Driver Setting FAQ": </p><p><b>“<span class="quote">I can't set and save default print options for all users on Win2K/XP! Why not?</span>”�</b> How are you doing it? I bet the wrong way.... (it is not very easy to find out, though). There are 3 different ways to bring you to a dialog that <span class="emphasis"><em>seems</em></span> to set everything. All three dialogs <span class="emphasis"><em>look</em></span> the same. Only one of them <span class="emphasis"><em>does</em></span> what you intend. <span class="emphasis"><em>Important:</em></span> you need to be Administrator or Print Administrator to do this for all users. Here is how I reproduce it in on XP Professional: </p><div class="orderedlist"><ol type="A"><li><p>The first "wrong" way: </p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guiicon">Printers</span> folder.</p></li><li><p>Right-click on the printer (<span class="emphasis"><em>remoteprinter on cupshost</em></span>) and select in context menu <span class="guimenu">Printing Preferences...</span></p></li><li><p>Look at this dialog closely and remember what it looks like.</p></li></ol></div><p> </p></li><li><p>The second "wrong" way: </p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="guimenu">Printers</span> folder.</p></li><li><p>Right-click on the printer (<span class="emphasis"><em>remoteprinter on cupshost</em></span>) and select in the context menu <span class="guimenuitem">Properties</span></p></li><li><p>Click on the <span class="guilabel">General</span> tab</p></li><li><p>Click on the button <span class="guibutton">Printing Preferences...</span></p></li><li><p>A new dialog opens. Keep this dialog open and go back to the parent dialog.</p></li></ol></div><p> </p></li><li><p>The third, the "correct" way: (should you do this from the beginning, just carry out steps 1. and 2. from second "way" above) </p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="guilabel">Advanced</span> tab. (Hmmm... if everything is "Grayed Out", then you are not logged in as a user with enough privileges).</p></li><li><p>Click on the <span class="guibutton">Printing Defaults...</span> button.</p></li><li><p>On any of the two new tabs, click on the <span class="guilabel">Advanced...</span> button.</p></li><li><p>A new dialog opens. Compare this one to the other, identical looking one from "B.5" or A.3".</p></li></ol></div><p> </p></li></ol></div><p> Do you see any difference in the two settings dialogs? I don't either. However, only the last one, which you arrived at with steps C.1.-6. will permanently save any settings which will then become the defaults for new users. If you want all clients to have the same defaults, you need to conduct these steps as administrator (<a class="indexterm" name="id2903830"></a><i class="parameter"><tt>printer admin</tt></i> in ) <span class="emphasis"><em>before</em></span> a client downloads the driver (the clients can later set their own <span class="emphasis"><em>per-user defaults</em></span> by following the procedures <span class="emphasis"><em>A.</em></span> or <span class="emphasis"><em>B.</em></span> above...). (This is new: Windows 2000 and Windows XP allow <span class="emphasis"><em>per-user</em></span> default settings and the ones the administrator gives them, before they set up their own). The "parents" of the identically looking dialogs have a slight difference in their window names: one is called <tt class="computeroutput">Default Print Values for Printer Foo on Server Bar"</tt> (which is the one you need) and the other is called "<tt class="computeroutput">Print Settings for Printer Foo on Server Bar</tt>". The last one is the one you arrive at when you right-click on the printer and select <span class="guimenuitem">Print Settings...</span>. This is the one what you were taught to use back in the days of Windows NT! So it is only natural to try the same way with Win2k or WinXP. You wouldn't dream that there is now a different "clicking path" to arrive at an identically looking, but functionally different dialog to set defaults for all users! </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>Try (on Win2000 and WinXP) to run this command (as a user with the right privileges): </p><p><b class="userinput"><tt> rundll32 printui.dll,PrintUIEntry /p /t3 /n\\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printersharename</tt></i> </tt></b></p><p> to see the tab with the <span class="guilabel">Printing Defaults...</span> button (the one you need). Also run this command: </p><p><b class="userinput"><tt> rundll32 printui.dll,PrintUIEntry /p /t0 /n\\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printersharename</tt></i> </tt></b></p><p> to see the tab with the <span class="guilabel">Printing Preferences...</span> button (the one which doesn't set system-wide defaults). You can start the commands from inside a DOS box" or from the <span class="guimenu">Start</span> -- <span class="guimenuitem">Run...</span> menu. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904001"></a>Supporting large Numbers of Printers</h3></div></div><div></div></div><p> One issue that has arisen during the recent development phase of Samba is the need to support driver downloads for 100's of printers. Using Windows NT APW here is somewhat awkward (to say the least). If you don't want to acquire RSS pains from such the printer installation clicking orgy alone, you need to think about a non-interactive script. </p><p> If more than one printer is using the same driver, the <b class="command">rpcclient setdriver</b> command can be used to set the driver associated with an installed queue. If the driver is uploaded to <i class="parameter"><tt>[print$]</tt></i> once and registered with the printing TDBs, it can be used by multiple print queues. In this case you just need to repeat the <b class="command">setprinter</b> subcommand of <b class="command">rpcclient</b> for every queue (without the need to conduct the <b class="command">adddriver</b> again and again). The following is an example of how this could be accomplished: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumdrivers'</tt></b> cmd = enumdrivers [Windows NT x86] Printer Driver Info 1: Driver Name: [infotec IS 2075 PCL 6] Printer Driver Info 1: Driver Name: [DANKA InfoStream] Printer Driver Info 1: Driver Name: [Heidelberg Digimaster 9110 (PS)] Printer Driver Info 1: Driver Name: [dm9110] Printer Driver Info 1: Driver Name: [myphantasydrivername] [....] </pre><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] description:[\\SAMBA-CUPS\dm9110,,110ppm HiVolume DANKA Stuttgart] comment:[110 ppm HiVolume DANKA Stuttgart] [....] </pre><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c \ 'setdriver <i class="replaceable"><tt>dm9110</tt></i> "<i class="replaceable"><tt>Heidelberg Digimaster 9110 (PS)</tt></i>"'</tt></b> cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD) Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS). </pre><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\ 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....] </pre><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'setdriver <i class="replaceable"><tt>dm9110</tt></i> <i class="replaceable"><tt>myphantasydrivername</tt></i>'</tt></b> cmd = setdriver dm9110 myphantasydrivername Successfully set dm9110 to myphantasydrivername. </pre><p> </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient <i class="replaceable"><tt>SAMBA-CUPS</tt></i> -U root%<i class="replaceable"><tt>secret</tt></i> -c 'enumprinters'</tt></b> cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,\ 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....] </pre><p> It may be not easy to recognize: but the first call to <b class="command">enumprinters</b> showed the "dm9110" printer with an empty string where the driver should have been listed (between the 2 commas in the "description" field). After the <b class="command">setdriver</b> command succeeded, all is well. (The CUPS Printing chapter has more info about the installation of printer drivers with the help of <b class="command">rpcclient</b>). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904312"></a>Adding new Printers with the Windows NT APW</h3></div></div><div></div></div><p> By default, Samba exhibits all printer shares defined in <tt class="filename">smb.conf</tt> in the <span class="guiicon">Printers...</span> folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if: </p><div class="itemizedlist"><ul type="disc"><li><p>...the connected user is able to successfully execute an <b class="command">OpenPrinterEx(\\server)</b> with administrative privileges (i.e. root or <a class="indexterm" name="id2904358"></a><i class="parameter"><tt>printer admin</tt></i>). </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Try this from a Windows 2K/XP DOS box command prompt: </p><p><b class="userinput"><tt> runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\<i class="replaceable"><tt>SAMBA-SERVER</tt></i>\<i class="replaceable"><tt>printersharename</tt></i> </tt></b></p><p> and click on <span class="guibutton">Printing Preferences...</span> </p></div></li><li><p>... contains the setting <a class="indexterm" name="id2904413"></a><i class="parameter"><tt>show add printer wizard</tt></i> = yes (the default).</p></li></ul></div><p> The APW can do various things: </p><div class="itemizedlist"><ul type="disc"><li><p>upload a new driver to the Samba <i class="parameter"><tt>[print$]</tt></i> share;</p></li><li><p>associate an uploaded driver with an existing (but still "driverless") print queue;</p></li><li><p>exchange the currently used driver for an existing print queue with one that has been uploaded before;</p></li><li><p>add an entirely new printer to the Samba host (only in conjunction with a working <a class="indexterm" name="id2904471"></a><i class="parameter"><tt>add printer command</tt></i>; a corresponding <a class="indexterm" name="id2904486"></a><i class="parameter"><tt>delete printer command</tt></i> for removing entries from the <span class="guiicon">Printers...</span> folder may be provided too)</p></li></ul></div><p> The last one (add a new printer) requires more effort than the previous ones. In order to use the APW to successfully add a printer to a Samba server, the <a class="indexterm" name="id2904516"></a><i class="parameter"><tt>add printer command</tt></i> must have a defined value. The program hook must successfully add the printer to the UNIX print system (i.e. to <tt class="filename">/etc/printcap</tt>, <tt class="filename">/etc/cups/printers.conf</tt> or other appropriate files) and to if necessary. </p><p> When using the APW from a client, if the named printer share does not exist, smbd will execute the <i class="parameter"><tt>add printer command</tt></i> and reparse to the to attempt to locate the new printer share. If the share is still not defined, an error of <span class="errorname">Access Denied</span> is returned to the client. Note that the <a class="indexterm" name="id2904566"></a><i class="parameter"><tt>add printer command</tt></i> is executed under the context of the connected user, not necessarily a root account. A <a class="indexterm" name="id2904582"></a><i class="parameter"><tt>map to guest</tt></i> = bad user may have connected you unwittingly under the wrong privilege; you should check it by using the <b class="command">smbstatus</b> command. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904606"></a>Weird Error Message <span class="errorname">Cannot connect under a different Name</span></h3></div></div><div></div></div><p> Once you are connected with the wrong credentials, there is no means to reverse the situation other than to close all Explorer windows, and perhaps reboot. </p><div class="itemizedlist"><ul type="disc"><li><p>The <b class="command">net use \\SAMBA-SERVER\sharename /user:root</b> gives you an error message: <tt class="computeroutput">Multiple connections to a server or a shared resource by the same user utilizing the several user names are not allowed. Disconnect all previous connections to the server, resp. the shared resource, and try again.</tt></p></li><li><p>Every attempt to "connect a network drive" to <tt class="filename">\\SAMBASERVER\\print$</tt> to z: is countered by the pertinacious message. <tt class="computeroutput">This network folder is currently connected under different credentials (username and password). Disconnect first any existing connection to this network share in order to connect again under a different username and password</tt>.</p></li></ul></div><p> So you close all connections. You try again. You get the same message. You check from the Samba side, using <b class="command">smbstatus</b>. Yes, there are some more connections. You kill them all. The client still gives you the same error message. You watch the smbd.log file on a very high debug level and try re-connect. Same error message, but not a single line in the log. You start to wonder if there was a connection attempt at all. You run ethereal and tcpdump while you try to connect. Result: not a single byte goes on the wire. Windows still gives the error message. You close all Explorer Windows and start it again. You try to connect - and this times it works! Windows seems to cache connection info somewhere and doesn't keep it up to date (if you are unlucky you might need to reboot to get rid of the error message). </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2904706"></a>Be careful when assembling Driver Files</h3></div></div><div></div></div><p> You need to be very careful when you take notes about the files and belonging to a particular driver. Don't confuse the files for driver version "0" (for Win95/98/ME, going into <tt class="filename">[print$]/WIN/0/</tt>), driver version "2" (Kernel Mode driver for WinNT, going into <tt class="filename">[print$]/W32X86/2/</tt> <span class="emphasis"><em>may</em></span> be used on Win2K/XP too), and driver version "3" (non-Kernel Mode driver going into <tt class="filename">[print$]/W32X86/3/</tt> <span class="emphasis"><em>can not</em></span> be used on WinNT). Very often these different driver versions contain files carrying the same name; but still the files are very different! Also, if you look at them from the Windows Explorer (they reside in <tt class="filename">%WINDOWS%\system32\spool\drivers\W32X86\</tt>) you will probably see names in capital letters, while an "enumdrivers" command from Samba would show mixed or lower case letters. So it is easy to confuse them. If you install them manually using <b class="command">rpcclient</b> and subcommands, you may even succeed without an error message. Only later, when you try install on a client, you will encounter error messages like <tt class="computeroutput">This server has no appropriate driver for the printer</tt>. </p><p> Here is an example. You are invited to look very closely at the various files, compare their names and their spelling, and discover the differences in the composition of the version-2 and -3 sets Note: the version-0 set contained 40 (!) <i class="parameter"><tt>Dependentfiles</tt></i>, so I left it out for space reasons: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>rpcclient -U 'Administrator%<i class="replaceable"><tt>secret</tt></i>' -c 'enumdrivers 3' 10.160.50.8 </tt></b> Printer Driver Info 3: Version: [3] Driver Name: [Canon iR8500 PS3] Architecture: [Windows NT x86] Driver Path: [\\10.160.50.8\print$\W32X86\3\cns3g.dll] Datafile: [\\10.160.50.8\print$\W32X86\3\iR8500sg.xpd] Configfile: [\\10.160.50.8\print$\W32X86\3\cns3gui.dll] Helpfile: [\\10.160.50.8\print$\W32X86\3\cns3g.hlp] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aucplmNT.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\ucs32p.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\tnl32.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussdrv.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cnspdc.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\aussapi.dat] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3407.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\CnS3G.cnt] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBAPI.DLL] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\NBIPC.DLL] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcview.exe] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcdspl.exe] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcedit.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm.exe] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcspl.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cfine32.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcr407.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\Cpcqm407.hlp] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cpcqm407.cnt] Dependentfiles: [\\10.160.50.8\print$\W32X86\3\cns3ggr.dll] Monitorname: [] Defaultdatatype: [] Printer Driver Info 3: Version: [2] Driver Name: [Canon iR5000-6000 PS3] Architecture: [Windows NT x86] Driver Path: [\\10.160.50.8\print$\W32X86\2\cns3g.dll] Datafile: [\\10.160.50.8\print$\W32X86\2\IR5000sg.xpd] Configfile: [\\10.160.50.8\print$\W32X86\2\cns3gui.dll] Helpfile: [\\10.160.50.8\print$\W32X86\2\cns3g.hlp] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\AUCPLMNT.DLL] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussdrv.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cnspdc.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\aussapi.dat] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3407.dll] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\CnS3G.cnt] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBAPI.DLL] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\NBIPC.DLL] Dependentfiles: [\\10.160.50.8\print$\W32X86\2\cns3gum.dll] Monitorname: [CPCA Language Monitor2] Defaultdatatype: [] </pre><p> If we write the "version 2" files and the "version 3" files into different text files and compare the result, we see this picture: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>sdiff 2-files 3-files</tt></b> cns3g.dll cns3g.dll iR8500sg.xpd iR8500sg.xpd cns3gui.dll cns3gui.dll cns3g.hlp cns3g.hlp AUCPLMNT.DLL | aucplmNT.dll > ucs32p.dll > tnl32.dll aussdrv.dll aussdrv.dll cnspdc.dll cnspdc.dll aussapi.dat aussapi.dat cns3407.dll cns3407.dll CnS3G.cnt CnS3G.cnt NBAPI.DLL NBAPI.DLL NBIPC.DLL NBIPC.DLL cns3gum.dll | cpcview.exe > cpcdspl.exe > cpcqm.exe > cpcspl.dll > cfine32.dll > cpcr407.dll > Cpcqm407.hlp > cpcqm407.cnt > cns3ggr.dll </pre><p> Don't be fooled though! Driver files for each version with identical names may be different in their content, as you can see from this size comparison: </p><pre class="screen"> <tt class="prompt">root# </tt><b class="userinput"><tt>for i in cns3g.hlp cns3gui.dll cns3g.dll; do \ smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \ -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i"; \ done</tt></b> CNS3G.HLP A 122981 Thu May 30 02:31:00 2002 CNS3G.HLP A 99948 Thu May 30 02:31:00 2002 CNS3GUI.DLL A 1805824 Thu May 30 02:31:00 2002 CNS3GUI.DLL A 1785344 Thu May 30 02:31:00 2002 CNS3G.DLL A 1145088 Thu May 30 02:31:00 2002 CNS3G.DLL A 15872 Thu May 30 02:31:00 2002 </pre><p> In my example were even more differences than shown here. Conclusion: you must be very careful to select the correct driver files for each driver version. Don't rely on the names alone. Don't interchange files belonging to different driver versions. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905065"></a>Samba and Printer Ports</h3></div></div><div></div></div><p> Windows NT/2000 print servers associate a port with each printer. These normally take the form of <tt class="filename">LPT1:</tt>, <tt class="filename">COM1:</tt>, <tt class="filename">FILE:</tt>, etc. Samba must also support the concept of ports associated with a printer. By default, only one printer port, named "Samba Printer Port", exists on a system. Samba does not really need such a "port" in order to print; it rather is a requirement of Windows clients. They insist on being told about an available port when they request this info, otherwise they throw an error message at you. So Samba fakes the port information to keep the Windows clients happy. </p><p> Note that Samba does not support the concept of "Printer Pooling" internally either. Printer Pooling assigns a logical printer to multiple ports as a form of load balancing or fail over. </p><p> If you require that multiple ports be defined for some reason or another (“<span class="quote">My users and my Boss should not know that they are working with Samba</span>”), possesses a <a class="indexterm" name="id2905140"></a><i class="parameter"><tt>enumports command</tt></i> which can be used to define an external program that generates a listing of ports on a system. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905158"></a>Avoiding the most common Misconfigurations of the Client Driver</h3></div></div><div></div></div><p> So - printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, which don't look good at all. Some jobs print fast, and some are dead-slow. We can't cover it all; but we want to encourage you to read the little paragraph about "Avoiding the wrong PostScript Driver Settings" in the CUPS Printing part of this document. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905183"></a>The Imprints Toolset</h2></div></div><div></div></div><p> The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please refer to the Imprints web site at <a href="http://imprints.sourceforge.net/" target="_top">http://imprints.sourceforge.net/</a> as well as the documentation included with the imprints source distribution. This section will only provide a brief introduction to the features of Imprints. </p><p><b>Attention! Maintainer required.�</b> Unfortunately, the Imprints toolset is no longer maintained. As of December, 2000, the project is in need of a new maintainer. The most important skill to have is decent perl coding and an interest in MS-RPC based printing using Samba. If you wish to volunteer, please coordinate your efforts on the samba-technical mailing list. The toolset is still in usable form; but only for a series of older printer models, where there are prepared packages to use. Packages for more up to date print devices are needed if Imprints should have a future.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905239"></a>What is Imprints?</h3></div></div><div></div></div><p> Imprints is a collection of tools for supporting these goals: </p><div class="itemizedlist"><ul type="disc"><li><p>Providing a central repository information regarding Windows NT and 95/98 printer driver packages</p></li><li><p>Providing the tools necessary for creating the Imprints printer driver packages.</p></li><li><p>Providing an installation client which will obtain printer drivers from a central internet (or intranet) Imprints Server repository and install them on remote Samba and Windows NT4 print servers.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905280"></a>Creating Printer Driver Packages</h3></div></div><div></div></div><p> The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included with the Samba distribution for more information). In short, an Imprints driver package is a gzipped tarball containing the driver files, related INF files, and a control file needed by the installation client. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905299"></a>The Imprints Server</h3></div></div><div></div></div><p> The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer entry in the database has an associated URL for the actual downloading of the package. Each package is digitally signed via GnuPG which can be used to verify that package downloaded is actually the one referred in the Imprints database. It is strongly recommended that this security check <span class="emphasis"><em>not</em></span> be disabled. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2905323"></a>The Installation Client</h3></div></div><div></div></div><p> More information regarding the Imprints installation client is available in the <tt class="filename">Imprints-Client-HOWTO.ps</tt> file included with the imprints source package. </p><p> The Imprints installation client comes in two forms. </p><div class="itemizedlist"><ul type="disc"><li><p>a set of command line Perl scripts</p></li><li><p>a GTK+ based graphical interface to the command line Perl scripts</p></li></ul></div><p> The installation client (in both forms) provides a means of querying the Imprints database server for a matching list of known printer model names as well as a means to download and install the drivers on remote Samba and Windows NT print servers. </p><p> The basic installation process is in four steps and perl code is wrapped around smbclient and rpcclient </p><div class="itemizedlist"><ul type="disc"><li><p> foreach (supported architecture for a given driver) </p><div class="orderedlist"><ol type="1"><li><p>rpcclient: Get the appropriate upload directory on the remote server</p></li><li><p>smbclient: Upload the driver files</p></li><li><p>rpcclient: Issues an AddPrinterDriver() MS-RPC</p></li></ol></div><p> </p></li><li><p>rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer</p></li></ul></div><p> One of the problems encountered when implementing the Imprints tool set was the name space issues between various supported client architectures. For example, Windows NT includes a driver named "Apple LaserWriter II NTX v51.8" and Windows 95 calls its version of this driver "Apple LaserWriter II NTX" </p><p> The problem is how to know what client drivers have been uploaded for a printer. An astute reader will remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A quick look in the Windows NT 4.0 system registry at </p><p><tt class="filename"> HKLM\System\CurrentControlSet\Control\Print\Environment </tt></p><p> will reveal that Windows NT always uses the NT driver name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not already been installed? </p><p> The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that NT driver is installed first. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905478"></a>Add Network Printers at Logon without User Interaction</h2></div></div><div></div></div><p> The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients: <span class="emphasis"><em>How to Add Printers with No User Interaction in Windows 2000.</em></span> ( <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;189105" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;189105</a> ). It also applies to Windows XP Professional clients. </p><p> The ideas sketched out below are inspired by this article. It describes a commandline method which can be applied to install network and local printers and their drivers. This is most useful if integrated in Logon Scripts. You can see what options are available by typing in a command prompt ("DOS box") this: </p><p><b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /?</tt></b></p><p> A window pops up which shows you all of the commandline switches available. An extensive list of examples is also provided. This is only for Win 2k/XP. It doesn't work on WinNT. WinNT has probably some other tools in the respective Resource Kit. Here is a suggestion about what a client logon script might contain, with a short explanation of what the lines actually do (it works if 2k/XP Windows clients access printers via Samba, but works for Windows-based print servers too): </p><pre class="screen"> <b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q</tt></b> <b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"</tt></b> <b class="userinput"><tt>rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"</tt></b> </pre><p> Here is a list of the used commandline parameters: </p><div class="variablelist"><dl><dt><span class="term">/dn</span></dt><dd><p>deletes a network printer</p></dd><dt><span class="term">/q</span></dt><dd><p>quiet modus</p></dd><dt><span class="term">/n</span></dt><dd><p>names a printer</p></dd><dt><span class="term">/in</span></dt><dd><p>adds a network printer connection</p></dd><dt><span class="term">/y</span></dt><dd><p>sets printer as default printer</p></dd></dl></div><div class="itemizedlist"><ul type="disc"><li><p>Line 1 deletes a possibly existing previous network printer <span class="emphasis"><em>infotec2105-IPDS</em></span> (which had used native Windows drivers with LPRng that were removed from the server which was converted to CUPS). The <b class="command">/q</b> at the end eliminates "Confirm" or error dialog boxes popping up. They should not be presented to the user logging on.</p></li><li><p>Line 2 adds the new printer <span class="emphasis"><em>infotec2105-PS</em></span> (which actually is same physical device but is now run by the new CUPS printing system and associated with the CUPS/Adobe PS drivers). The printer and its driver <span class="emphasis"><em>must</em></span> have been added to Samba prior to the user logging in (e.g. by a procedure as discussed earlier in this chapter, or by running <b class="command">cupsaddsmb</b>). The driver is now auto-downloaded to the client PC where the user is about to log in.</p></li><li><p>Line 3 sets the default printer to this new network printer (there might be several other printers installed with this same method and some may be local as well -- so we decide for a default printer). The default printer selection may of course be different for different users.</p></li></ul></div><p> Note that the second line only works if the printer <span class="emphasis"><em>infotec2105-PS</em></span> has an already working print queue on "sambacupsserver", and if the printer drivers have successfully been uploaded (via <b class="command">APW</b> , <b class="command">smbclient/rpcclient</b> or <b class="command">cupsaddsmb</b>) into the <i class="parameter"><tt>[print$]</tt></i> driver repository of Samba. Also, some Samba versions prior to version 3.0 required a re-start of smbd after the printer install and the driver upload, otherwise the script (or any other client driver download) would fail. </p><p> Since there no easy way to test for the existence of an installed network printer from the logon script, the suggestion is: don't bother checking and just allow the deinstallation/reinstallation to occur every time a user logs in; it's really quick anyway (1 to 2 seconds). </p><p> The additional benefits for this are: </p><div class="itemizedlist"><ul type="disc"><li><p>It puts in place any printer default setup changes automatically at every user logon.</p></li><li><p>It allows for "roaming" users' login into the domain from different workstations.</p></li></ul></div><p> Since network printers are installed per user this much simplifies the process of keeping the installation up-to-date. The extra few seconds at logon time will not really be noticeable. Printers can be centrally added, changed, and deleted at will on the server with no user intervention required on the clients (you just need to keep the logon scripts up to date). </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2905813"></a>The <b class="command">addprinter</b> command</h2></div></div><div></div></div><p> The <b class="command">addprinter</b> command can be configured to be a shell script or program executed by Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks the user to fill in several fields (such as printer name, driver to be used, comment, port monitor, etc.). These parameters are passed on to


context:
space:
mode: